Changed partition size, 2% stuck flashtool and other (not)funny things - G2 Q&A, Help & Troubleshooting

Hello, I was changing Inazuma ROM(LP) to MIUI v7 on kitkat. I used D802_PATCH_RETURN_KK_droidth.zip to do this. But unfortunately after I got "secure booting error". I tried lg flash tool (kdz and via tot options). In both case I have a error cuz system partition was changed. Indeed I was changing my partitions for more space in memory. And now I have a trouble. I tried to enter recovery but instead I did hard reset and lost secure error and qhsusb_bulk.
In download mode I got:
"COM 41
F USER S0.0 AS0.0 B87 UHS
S U LG-D802 04.2.2 Hrev_11
D80210F
D80210B
ROOTED"
Its a way to resize partition to restore system via kdz? I did it before but I needed adb and twrp. ( I set 2.0 GB for system)
@edit
I did a flash via LGFlashTool but I still got a bootloop. Of course I did hard reset but didnt help. I cannot enter recovery so Im not able to fix for flashtool.
What can I do now? Its a way to put custom recovery in download mode?

Related

D800 broken download mode

I once bricked my phone by installing a L01F ROM on my phone by accident, and had to manually reflash every partition in windows CMD prompt. I have been using my phone fine since I recovered from the brick but I was going to tot to stock and update to lollipop but my download mode says secure boot error and shows up as qhsusb_bulk in device manager and gives me a ton of partitions. I have been looking around for a solution but cannot find one. The only thing that is broke is my download mode. I have recovery and a booting ROM.
Link420able said:
I once bricked my phone by installing a L01F ROM on my phone by accident, and had to manually reflash every partition in windows CMD prompt. I have been using my phone fine since I recovered from the brick but I was going to tot to stock and update to lollipop but my download mode says secure boot error and shows up as qhsusb_bulk in device manager and gives me a ton of partitions. I have been looking around for a solution but cannot find one. The only thing that is broke is my download mode. I have recovery and a booting ROM.
Click to expand...
Click to collapse
Pm me, I'll help you.
Sent from my LG-D800 using Tapatalk
I have flashed a new laf.IMG but I still get the secure boot failure, boot certification error.
Repaired using skr tools. Wonderful set of tools

Need HelP - ODIN gets stucked while flashing

Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!

Is EMMC of my phone corrupted or not?

I am using Spice Dream UNO(Android One).
Bootloader: Unlocked
ROM: Marshmallow Stock ROM
Rooted: Yes
Recovery: TWRP
My phone suddenly started giving continuous Force closes so I restarted it and got stuck in a bootloop. Trying to Wipe any partitions failed with Error 1 and I was unable to copy or write to any partition from TWRP file manager. Nandroid backup and restore failed too.
So, I tried to flash Stock Lollipop ROM using SP Flash Tools and it flashed successfully but now all partitions show 0 MB size except Boot, IMEI and Recovery partitions.
Flashing ROM or restoring backup using TWRP still fails. Changing partition format, wiping, formatting fails too. Manual flashing using fastboot shows success but partition sizes still stay at 0MB. I have tried everything but I am not able to restore the partitions back to normal.
I haven't used the format feature of SP flash tools.
Now starting TWRP or fastboot turns the phone off and I am not able to access them.
Is EMMC of this phone corrupted or not? Can it be fixed?

[SOLVED] [Loop] Your device is corrupt it cannot be trusted and will not boot

Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
docizoc said:
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
Can you boot to TWRP?
Did you make a backup and have access to it? Especially the EFS partition? If you do, restore the EFS partition.
If you can boot to TWRP, try the following:
- wipe everything (the option where you have to type 'yes').
- download lineageOS and flash it. If this is working fine, install whatever ROM you want to install.
no access to twrp anymore , no backup , only access to download mode now
is there a way to flash back twrp or stock recovery from download mode ? boot into fastboot ?
(i know... i have no excuses , but made that so many times without issues ...)
thank you in advance
Maybe you should go in download mode and flash stock Rom with LGUP.
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Can you flash twrp through lgup or fastboot?
For those that could be in the same situation i finally succeed to flash with LGUP last version but without the 8894DLL
the error was probably coming from the dll.
Cheers and thanks all for the answers
docizoc said:
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
It's probably a problem with the DLL, try to extract it from the kdz and input it in Lgup folder (I don't remember where and I'm not home, check the main thread for that) and after that retry flashing
EDIT : well you were faster than my phone glad it worked for you.

[Solved] Lineageos downgrade to Stock Android7. Bricked, I can only see logo LGU+

Hello.
I got V20 F800L "rooted" with Lineageos. I wanted to restore the factory system. I downloaded the .kdz file and LGUP and LGFirmwareextract program and started flashing.
During the final phase of flashing, the smartphone resets, then less than a second I see a circle with the word "erasing", then a moment animated LG logo, then the static logo LGU+ and locks here.
Windows drivers and LGUP still recognize the device, I can flash different versions of f800l, I tried 10e and 20k and the program communicates that the flash was successful but nothing changes, the system does not boot.
I can enter the "power + vol + down" mode to do "factory data reset", after that appears for less than a second a circle with the word "erasing" , then logo "LG U +" logo and locks in place.
How to recover the device, please help.
Use LGUP patched, restore device with DL Mode option and select all partitions. When device rebooting, disconnect and reconnect the battery then do the factory reset. Your device will be fully restored to stock
khtr98 said:
....then do the factory reset. Your device will be fully restored to stock
Click to expand...
Click to collapse
Thank you for your response.
I tried to use the version with the LGUP patch.
I chose the PARTITION DL option and selected all partitions. While the LGUP program reset the device, I pulled out and inserted the battery, after the reset the program confirmed the success, but the device still can not start, and then all I have is the LGU + logo.
Did I do something wrong? do you have any other ideas?
I have no idea, maybe some partition is corrupted and cannot be restored.
But you can try this tricky way (if you have no choice)
Download us996 10f kdz, use PARTITION DL with all selected partition to crossflash your device to us996. LGUP will show a dialog box tell you want to repartition some partition layout. Click yes then wait to finish and hopefully it boots fine.
khtr98 said:
I have no idea..
Click to expand...
Click to collapse
I tried with different versions of ROM. Finally it boot. At the beginning I flashed with versions 10e (Android 7) and 20k (Android 8) with PARTITION DL mode, but it did not boot, but finally I was flashing the latest version 30e (Android 9) for F800L and the system started
Thank You khtr98. Problem solved
khtr98 said:
I have no idea, maybe some partition is corrupted and cannot be restored.
Click to expand...
Click to collapse
But option to enter the download mode (via usb+volume-up) has disappeared. I lost possibility for downgrade and root when I choose android 9 for f800l ?
after upgrade (official android 9 for f800L), when i try to go back to oreo or nougat i used a patched LGUP i get the message:
Error 0x ....., plaease use last DLL
LAF Protocol Version is not match DLL = 10 .......
Device = 14 ....
is downgrade possible?
ok. is possible
==================================================
For educational purposes, I again downgraded the version from the rooted line 17 to the factory Android 7.
This time it went smoothly because I did advanced cleaning in TWRP before.
I used the wrong version of the patched LGUP, this version is correct, it allows downgrade: https://forum.xda-developers.com/android/general/tecknights-aristo-2-tutorials-t3805141/page3

Categories

Resources