[SOLVED]![H870]Device keeps going into download mode after interupted Uppercut flash - LG G6 Questions and Answers

Hello there.
I unlocked the BL yesterday and flashed TWRP and then AEX latest Oreo based ROM. It was fine, but since I came from Oreo, I did not have fingerprint sensor working.
So I wanted to go back to Nougat and then flash the AEX from there. Uppercut didn't recognize the phone so I installed a stock based rooted Oreo from TWRP.
I started the Uppercut flash with a stock Nougat system, but it was interrupted (in upgrade mode, refurbish mode doesn't work at all) referring to: error 0x2bc invalid command response code.
Later with another kdz file it gave me: error 0x2bc crc checksum error
From then on I cannot get into anything else, just download mode (in there, wildly short-pressing the Vol- and Power buttons gets me into a menu where I can turn the phone off, and I can boot into Fastboot mode. )
In fastboot mode I flash twrp and then when I try to boot into twrp by selecting the usual reset system options, it just gets into download mode again.
I could not get any kdz to install on it so far. I tried H87020C, 10D, 20A.
So now I have download mode, which fails and fastboot mode, in which I don't really know what can I do.
LG Bridge doesn't help, LG Flash Tool stops at extracting all the kdz files I gave it and LG UP also doesn't work.
The bootloader is still unlocked.
Please help me with this.

All of a sudden for the fifth trial, LG Bridge somehow succeeded to install and boot the phone via Update Recovery Error method.

Related

[Q] LG G2(F320L) not booting after OTA with stock recovery with TWRP aboot

Hi,
First of all i committed a mistake of thinking that with TWRP aboot + stock Recovery i will be able to do OTA upgrade, which made my phone not booting, undetectable by computer and majorly not getting the LG Flash download mode by pressing any combination of keys., Stucks at LG logo.
Device: LG-G2(F320L)
KDZ stock: F320L21V_00.kdz
1. Flashed this kdz using LG Flash Tool 2014.
2. Flashed from F320L_AutoRec.apk, the images only aboot, and recovery.
3. From DorimanX project generated the boot.img with StockROM(F320L21V_00.kdz) version bootimage RAMDISK.
Everything was fine., till then.
After that, i got the OTA pop up., So, thought of installing OTA. As I had already faced the TWRP bootloop once and in some post i remember i read flashing OTA needs stock recovery image. Here is the place I commited the mistake. So, signed the stock recovery with aboot of TWRP using loki_flash. Accepted OTA. Thats it.
From then, no booting, no recovery, no adb, no fastboot, and unfortunately NO LG DOWNLOAD MODE also it goes.
When i try to go TWRP, it stucks up after the initial TWP message.
And pressing some key combination, the device goes to LG service mode, and showing the IMEI and some list of 3 options in korean which i dont understand. By pressing any of the option device reboots and stucks with LG logo.
Even my device is not shown up in the ubuntu, when i checked "dmesg".
Can anyone help to get the device into Either download mode or fixing the boot.
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
No solution yet?
The phone is still in the same state. Can anyone please suggest the solution to make the device working? Thanks in advance.

Strangely bricked D802

So, I did brick my D802 in some way.
After a long history from cloudy g2-g3, rr, cm12, cm13, lineage 14.1, I clicked by mistake on the OTA of the lineage.
I thought I could stop the update once in the recovery, but I got stucked in the recovery bootloop. I got rid of it via recovery terminal, but system didn't boot. I tried reflashing lineage, nothing happened, I tried restoring a cm13 full backup, nothing happened, so I got back in download mode to restock with lollipop kdz (the one I used every time I restocked to change rom). It did not work, and I had to download a different KDZ to get to stock again.
Now, all the methods always used to root + recovery didn't work, so I manually rooted, installed the proper AUTOREC, but it didn't work (as I understand after hours of searching because supersu had updated himself in the meantime).
So I tried to install the TWRP image using flashify, it didn't work and corrupted something in my recovery. So i tried to unroot everything and reinstall the original root + supersu without letting him autoupdate. Not working.
Well, now I can boot and I can get in original lollipop rom, but I have no recovery and download mode appears but doesn't work anymore (once I had 3 COM ports when connected in download mode, now I can see only one; kdz flash does not sense the phone connected). When I try to open recovery I got the error "boot certification verify, secureboot error" in the top left corner of the screen, then a white page opens with the message "critical error" "demigod crash handler", volume up to download mode (that opens but does not work), volume down to reboot.
Now, I am stucked, I cannot find any suggestion of what to do to get the recovery working or to get the download mode working again.
Any help will be highly appreciated.
Thank you very much guys.
Not sure will it help but you may give it a try:
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076

Stuck on Firmware update mode

Guys, I have a US996. It was rooted using DirtyElf method, had WETA rom installed. I had a problem when I was flashing kernel, and got stuck with a crashing screen or fastboot mode. After some different procedures, managed do flash kdz using LGUP tool. Now, I don't have the crashing screen anymore, but I'm still stuck on Firmware Update. I can access Fastboot mode, but when I try to fastboot reboot or fastboot reboot-recovery, I always end up on Firmware Update. Apparently, my bootloader is still unlocked, so it seems tha kdz flashing was not full,. Any ideas? Any help would be much apreciated!
need to reinstall twrp. then from twrp you need to reinstall a new rom.

A2017G only EDL mode available, need help with brick

Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.
Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.
Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data
I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.
xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english
Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.

Hard Bricked LGV20 US996 Bootloader Locked.

Hi All,
I have a LGV20 US 996, and I hard bricked it after installing Magisk on Lineage while doing the OTA update for MGAISK. I was on Lineage 17.
Things I Tried to fix:
Enter Download mode, attempt to install KDZ with UPPERCUT and LGUP.
Problem is that LG UP stops at 80%, and then displays Rebooting 40sec. Then it enters Fastboot mode, and doesn't boot the OS.
Next, I tried to unlock bootloader via fastboot mode, but says Failed Error (Possibly due to not enabling OEM unlocking) ..
SO, is there hope or is this Device gone for good?
Thank you.

Categories

Resources