d801 boots to cm13 but no recovery and no download mode. - G2 Q&A, Help & Troubleshooting

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..

Related

[Q] Download mode stuck

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.

[Q] Ruined Fastboot mode, but regular boot works?

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.

[Q] Flashing rom/custom recovery using System Recovery 3e

Hi,
After trying to update my lg g2 (d800) using ota I bricked up my phone, following is the situation:
-- The phone keep restarting itself at lg logo (Bootloop)
-- No download mode is activated (using Volume Up + inserting usb cable) and instead it boots into system recovery 3e
-- I also believe the phone is still rooted as I did it before the phone bricked
-- No custom recovery was installed
-- Can't adb or fastboot, only sideload is available is system recovery 3e menu.
My question is can I
1. Flash any possible rom using adb sideload? (from system recovery 3e)
2. Flash TWRP or CWM using adb sideload?
3. Can I go to fastboot mode?
4. Can I flash any img files using abd sideload to get download mode?
I cant to stock using kdz or tot method.
Please give me any hints or ideas? Completely stuck right now
I posted another thread too:
http://forum.xda-developers.com/lg-g2/help/help-to-unbrick-g2-d800-t3135437

BOOTLOOP/Brick LG G2 (D802)

So here's what happened i was flashing the LLAMA Sweet Kernel for my D802 from RenderKernel (KK Bootsack loki signed, KK Bootloader) then i got stuck on LG Logo at first i thought it was fine but it hasn't move for like 30 mins. Then i tried to reboot and enter recovery mode. I can't enter recovery mode i tried it several times turned off first then Volume Down + Power button its not working anymore. But i can access DOWNLOAD MODE which is good i think.
Can someone please help me sort this thing out i just need to have TWRP recovery and i can handle the rest. How could i flash it using download mode. Thank you guys
LG G2 D802
16GB Version
Euphoria ROM
LLAMA Sweet Kernel
Try installing the stock LG Mobile Support Tool and USB drivers.
Open the support tool program, connect the phone in download mode, click on "Options" in the top right-hand corner, select upgrade recovery, and, hopefully, the program will download and install the correct firmware for your phone.
audit13 said:
Try installing the stock LG Mobile Support Tool and USB drivers.
Open the support tool program, connect the phone in download mode, click on "Options" in the top right-hand corner, select upgrade recovery, and, hopefully, the program will download and install the correct firmware for your phone.
Click to expand...
Click to collapse
Will this one completely delete everything? Or change the current ROM i've been using // Will this one also delete media files photos/music etc?
Is there any way that i can just flash TWRP on download mode so that i will just flash bootloader/bootstack or kernel thats causing this bootloop/brick.
Thanks
Yes, it will wipe everything.
audit13 said:
Yes, it will wipe everything.
Click to expand...
Click to collapse
So There's no other way to save my media files. i mean there's no other way to flash any recovery to my phone even though i can access download mode? Is that it sir?
have you tried re flashing twrp?
How can i re-flash it? ROM not loading stuck on Boot Logo, can't go to recovery. Only download mode working i already installed drivers and its been detected. I just dont know if there's a way to flash twrp on download mode.
I read some posts where it will delete data, others say it won't. I would just assume that flashing stock would return to stock and delete data.
Not sure how to flash twrp from download mode.

Unable to boot into twrp recovery after installing cm13 on t-mobile d801

I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
lg g2 bricked
hevydevy said:
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
Click to expand...
Click to collapse
does ur phone goes in download mode?
kalpesh patil said:
does ur phone goes in download mode?
Click to expand...
Click to collapse
It will give me the download mode message then goes to a black screen. My computer brings up 15 disc partitions with only one partition containing data, one folder called image with files include adsp, cmnlib, mc_v2, modem, playread, wcnss and widevine they all have duplicates with different file types b00-b26 and mdt .

Categories

Resources