I recently put TWRP on my LG G2 from Tmobile (D801). I then used it to flash CyanogenMod 10.2. It worked great. Then I decided to see if any other ROMS were available.
I downloaded AEON v3.zip (which I now realize was for D800) and tried to flash it from TWRP. It (obviously) didn't work as I expected, and now I can't get the phone into recovery mode. When I try to get it into the download mode (volume up+plugging in USB), the download mode screen flashes up for a second, but then it just goes to the Fastboot mode started /udc_start() screen.
It appears that I can use the fastboot utility on my computer to interact with the phone. fastboot devices -l results in a question mark (it says "? fastboot").
I've tried downloading openrecovery-twrp-2.6.3.2-g2tmo.img and flashing it to my device with:
fastboot flash recovery openrecovery-twrp-2.6.3.2-g2tmo.img
It indicates that it is successful ("OK") but I still cannot get into recovery mode.
Help?
Try downloading an app from The Play store called Quick Boot, it should let you reboot into recovery. Also, I'd imagine CM has a feature that allows you to boot into recovery from the power menu when you hold your power button down for a sec.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
solved
Thanks for the reply! I didn't have a working ROM to boot into, so I was just trying to get into Recovery mode to begin with.
Got some help from autoprime on #lg-g2 and found out that I was using the wrong timing on my recovery mode key presses to get into TWRP.
Related
Hi guys,
Long-time phone rooter/XDA reader, first time posting.
It seems I have finally come across a problem I can't fix by insane amounts of googling and trial&error.
I am currently on some Kitkat custom ROM variant with CWM 6.0.4.4
I'm looking to get back to stock, but my download mode refuses to open. Its stuck at the blue dots screen. (attached picture for clarity)
I've let it sit there overnight, with no change.
I've attempted to use the LGMobile Tool (even this method), but when it reboots my phone, the phone sits on the "LG" screen, and the LG tool eventually errors out ("communication error").
Recently, I managed to back myself into a corner after (incredibly idiotically) accepting an OWA, when my recovery was corrupt, and my download mode would not even open then - and i had to use some bizarre method of commands in Linux to be able to get TWRP on, then flashed CWM and them my ROM.
So what can I do now? I'm assuming my download mode is corrupt - is there a way to flash a good download mode onto the phone?
Any thoughts/input greatly appreciated.
edit:
Ok looks like I have understimated myself.
I used THIS tool to extract my KDZ, to get the LAF file (then renamed it to laf.img)
I then used the instructions from HERE to flash to the correct place.
It did not reboot into download like the thread said it would, but I did a manual download mode entry (while off, hold Volume Up + insert USB) and viola!
I am now currently using the LGMobile tool to go back to stock
Daveasaurus said:
Hi guys,
Long-time phone rooter/XDA reader, first time posting.
It seems I have finally come across a problem I can't fix by insane amounts of googling and trial&error.
I am currently on some Kitkat custom ROM variant with CWM 6.0.4.4
I'm looking to get back to stock, but my download mode refuses to open. Its stuck at the blue dots screen. (attached picture for clarity)
I've let it sit there overnight, with no change.
I've attempted to use the LGMobile Tool (even this method), but when it reboots my phone, the phone sits on the "LG" screen, and the LG tool eventually errors out ("communication error").
Recently, I managed to back myself into a corner after (incredibly idiotically) accepting an OWA, when my recovery was corrupt, and my download mode would not even open then - and i had to use some bizarre method of commands in Linux to be able to get TWRP on, then flashed CWM and them my ROM.
So what can I do now? I'm assuming my download mode is corrupt - is there a way to flash a good download mode onto the phone?
Any thoughts/input greatly appreciated.
edit:
Ok looks like I have understimated myself.
I used THIS tool to extract my KDZ, to get the LAF file (then renamed it to laf.img)
I then used the instructions from HERE to flash to the correct place.
It did not reboot into download like the thread said it would, but I did a manual download mode entry (while off, hold Volume Up + insert USB) and viola!
I am now currently using the LGMobile tool to go back to stock
Click to expand...
Click to collapse
Hey thanks for the post. My download mode will not go past the 5 blue dots screen. I am trying to return to stock but I get the same download mode error. I am rooted and have TWRP installed. This download mode error has happened before. I fixed it by flashing CM and then going into download mode and it worked! But my TWRP is getting an error when installing any rom. It fails and installation and says error executing updater binary. I just need to fix download mode or TWRP. Any help would be great.
Did you already have recovery installed when you were stuck at the 5 dots download mode screen?
How to Connect in ADB ?
Daveasaurus said:
Hi guys,
I used THIS tool to extract my KDZ, to get the LAF file (then renamed it to laf.img)
I then used the instructions from HERE to flash to the correct place.
It did not reboot into download like the thread said it would, but I did a manual download mode entry (while off, hold Volume Up + insert USB) and viola!
I am now currently using the LGMobile tool to go back to stock
Click to expand...
Click to collapse
My phone is also stucked same as yours, How you connect your phone is adb mode. My Phone just show download stuck screen and have no recovery. Any help would be really appreciated.
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
As I understand; If you're trying to boot it to recovery mode, it goes to fastboot mode, right?
If I understood right; you need just flash recovery to your device.
G2 has a different boot process from other devices. If bootloader failed to boot the thing you want to boot, it goes to fastboot mode. That's why it goes fastboot mode when you try to boot it to recovery.
Ah yeah, i just couldn't figure out how to get it out of Fastmode. I was a little confused about the difference between fastmode and recovery.
I seemed to have fixed the problem by AutoRec, for whatever that is worth. Now it boots into TWRP's recovery mode. Shouldn't be hard to get cyanogenmod now.
TheAmericannomad said:
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
Click to expand...
Click to collapse
if you want go back to stock and you can't enter in download mode you can try follow this but USE THE CORRECT FILES FOR YOUR DEVICE!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2477595
to extract laf.img from kdz.
http://forum.xda-developers.com/showthread.php?t=2600575
Give a thank to the OP of the threat.
Update: Flashed a ROM and the D801 laf.img as suggested and things are up and running normal again.
Alright, so I've tried going through a number of solutions but none of them seem to work for me at this point.
LG G2 D801 (T-mobile version, unlocked)
Rooted device with stump root
Installed TWRP with Autorec
Stupidly took an OTA at this point, it gave me the "secure boot error" once and now the device has a bootloop at the LG screen (without the "secure boot error" text, mind you)
Attempting to enter Download mode (Vol up + plug in usb) has the same bootloop (nothing even close to showing download mode nor fastboot)
I can access TWRP though, and the device is at least visible in adb once I'm in TWRP.
I considered flashing CM to it as is, but I wasn't sure how that would affect the issues with booting and download mode.
Also, before someone suggests this thread about reflashing the kdz/tot, I don't think I can, since I can't seem to enter download mode.
Suggestions? The goal was to get to BlissPop ROM, or CM12.1 if that didn't end up working well for me, although at this point I just want to get it working however I can.
joshery420 said:
Alright, so I've tried going through a number of solutions but none of them seem to work for me at this point.
LG G2 D801 (T-mobile version, unlocked)
Rooted device with stump root
Installed TWRP with Autorec
Stupidly took an OTA at this point, it gave me the "secure boot error" once and now the device has a bootloop at the LG screen (without the "secure boot error" text, mind you)
Attempting to enter Download mode (Vol up + plug in usb) has the same bootloop (nothing even close to showing download mode nor fastboot)
I can access TWRP though, and the device is at least visible in adb once I'm in TWRP.
I considered flashing CM to it as is, but I wasn't sure how that would affect the issues with booting and download mode.
Also, before someone suggests this thread about reflashing the kdz/tot, I don't think I can, since I can't seem to enter download mode.
Suggestions? The goal was to get to BlissPop ROM, or CM12.1 if that didn't end up working well for me, although at this point I just want to get it working however I can.
Click to expand...
Click to collapse
Flash a a ROM so that your phone is usable. Then you can flash download mode using flashify. Download laf.IMG for the d801 and then you can use flashify.
Sent from my LG-D800 using Tapatalk
xmayhemreturnsx said:
Flash a a ROM so that your phone is usable. Then you can flash download mode using flashify. Download laf.IMG for the d801 and then you can use flashify.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Great, that worked like a charm!
Thanks so much.
It feels like a dumb question now, it'd just been a year or two since I last flashed a ROM and wasn't sure if that was the right step to take next or not haha.
ROM is up and running well and laf.img got my download mode back, so all is well again.
I flashed to cm13 nightly 20160302 and my phone boots to cm with no problem but now I am unable to boot into recovery through any method with twrp 3.0.0.4 or any twrp version I tried inside of twrp manager or flashify, I am put into fastboot mode when trying to enter recovery with 3.0.0.4 and a few other I tried while other versions give me unsecured boot message. When trying to go into download mode I get the first download mode screen and then the screen goes blank and brings up 15 system partitions on my pc with only one partition containing a folder called image with a bunch of files. The phone is detectable through adb and as a storage device on my pc while booted into cm and while in fastboot mode the phone shows up as marshal london device- marshal london bootloader interface in device manager with no storage.
I planned on going to cloudyg2 but now I'm thinking about just going back to stock, would I be able to use the lg flash tool to get back to stock? Or possibly use adb recover to stock or use adb sideload to flash the default lg rom?
hevydevy said:
I flashed to cm13 nightly 20160302 and my phone boots to cm with no problem but now I am unable to boot into recovery through any method with twrp 3.0.0.4 or any twrp version I tried inside of twrp manager or flashify, I am put into fastboot mode when trying to enter recovery with 3.0.0.4 and a few other I tried while other versions give me unsecured boot message. When trying to go into download mode I get the first download mode screen and then the screen goes blank and brings up 15 system partitions on my pc with only one partition containing a folder called image with a bunch of files. The phone is detectable through adb and as a storage device on my pc while booted into cm and while in fastboot mode the phone shows up as marshal london device- marshal london bootloader interface in device manager with no storage.
I planned on going to cloudyg2 but now I'm thinking about just going back to stock, would I be able to use the lg flash tool to get back to stock? Or possibly use adb recover to stock or use adb sideload to flash the default lg rom?
Click to expand...
Click to collapse
I have the same problem. Any solution found?
stormrider2230 said:
I have the same problem. Any solution found?
Click to expand...
Click to collapse
if you can enter download mode. press vol up and connect usb.. then just go back to stock.. or see if srk tools would help..
Hey guys, I have a VS980 that was wrongly flashed with the wrong variant of CloudyG2 3.3, causing it to boot to Fastboot mode only. I used guides available on these forums that said I needed to flash the laf.img partition back to the phone to get it out of Fastboot mode but it now went back to Fastboot mode with a greyish-black screen, it did not even show the LG logo. I know it went to Fastboot mode because running the the "fastboot devices" command returned the phone identity. I then used SRKtook 2.1 to fix the Recovery, and this led to the phone going into QHSUSB 9006 mode. I then used the same SRKtool 2.1 to fix the QHSUSB 9006 issue. The tool successfully completed the process and even prompted me to flash the stock firmware, which I did using LGFlashTool 1.8, and one of the available TOT files (V26A). The flashing process completed successfully with a PASS. The phone powered on okay but with the same greyish-black screen as from before. I know the flashing process completed successfully because the the phone charges okay, the touchscreen works (even with the greyish-black screen I can unlock the screen, I can press the Home, Recents, and Back virtual buttons), and calls made to the SIM card inside the phone will ring). The PC recognizes the phone in MTP mode with Device Manager reporting it as being an LGE MTP Android Device, sometimes as a LG VS980 4G. My issues are these:
- What is it with the greyish-black screen? Anything I can do to rectify it? By the way it is not an LCD issue because I have repeatedly swapped screens from my other LS980 to the VS980 and from the VS980 to the LS980. On the LS980 both LCDs work perfectly.
- I can't get into Recovery mode. All the normal Volume Down+Power combo does is power on the phone. What can I do?
- I can't get into Fastboot mode. What can I do?
I am in the process of downloading every VS980 stock firmware I can find (10B, 11A, 26A, 39A, 24A, 27A). I will flash each to the phone, hopefully there'll be one that will fix my phone.