Database Users

[Q] Stuck in fastboot mode after flashing wrong device image

Hey guys.
I wanted to update my LG G2 32GB from slimlat 7.4 to 7.6.
This time i was just too tired to notice, that i downloaded the wrong image for my device. I flashed the d800 (AT&T) image instead of the d802 (international). Now i am stuck at fastboot mode:
Code:
[690] Fastboot mode started
[740] udc_start()
Iam not able to access recovery mode (TWRP) by pressing power and volume down, but i can access download mode (power and volume up).
Question 1: Can is access TWRP on a different way than pressing power and volume down while starting? Because i made a backup..
This guy some how managed to get into recovery.
Question 2: If there is no way to access TWRP. Do i have to make tabula rasa using the guide recommended for "Stuck in Fastboot with Broken Download Mode" "HOW TO get back to stock when your phone stuck in fastboot mode" or is there a way to repair & access recovery?
Question 3: The Guide "Stuck in Fastboot with Broken Download Mode" confused me, because it says: "First in fastboot mode (refer to my previous post, I enter it by plugging USB into G2 with pressing the volume + )" When i press power and volume up (which is +, right?) i access "download mode", but not fastboot mode. It looks like this. Does this mean my "download mode" is still operational and i can skip this guide?
Question 4: When i can skip the latter guide, do i have to continue with this (LG G2 Stock Firmware (Go Back to Stock)) one? Do i need to go back to stock to access TWRP and restore my backup?
I hope i haven't confused you with too many questions. I really looking forward to your answers. Thanks in advance for your help!
greetings mellhen

mellhen said:
Hey guys.
I wanted to update my LG G2 32GB from slimlat 7.4 to 7.6.
This time i was just too tired to notice, that i downloaded the wrong image for my device. I flashed the d800 (AT&T) image instead of the d802 (international). Now i am stuck at fastboot mode:
Code:
[690] Fastboot mode started
[740] udc_start()
Iam not able to access recovery mode (TWRP) by pressing power and volume down, but i can access download mode (power and volume up).
Question 1: Can is access TWRP on a different way than pressing power and volume down while starting? Because i made a backup..
This guy some how managed to get into recovery.
Question 2: If there is no way to access TWRP. Do i have to make tabula rasa using the guide recommended for "Stuck in Fastboot with Broken Download Mode" "HOW TO get back to stock when your phone stuck in fastboot mode" or is there a way to repair & access recovery?
Question 3: The Guide "Stuck in Fastboot with Broken Download Mode" confused me, because it says: "First in fastboot mode (refer to my previous post, I enter it by plugging USB into G2 with pressing the volume + )" When i press power and volume up (which is +, right?) i access "download mode", but not fastboot mode. It looks like this. Does this mean my "download mode" is still operational and i can skip this guide?
Question 4: When i can skip the latter guide, do i have to continue with this (LG G2 Stock Firmware (Go Back to Stock)) one? Do i need to go back to stock to access TWRP and restore my backup?
I hope i haven't confused you with too many questions. I really looking forward to your answers. Thanks in advance for your help!
greetings mellhen
Click to expand...
Click to collapse
To access twrp try power + vol down then vol up + vol down. If that doesn't work then no you cannot access your recovery.
Your actually in a much better position than the guy in that guide. You've got download mode so you can skip to the easy part and just follow the back to stock guide.
You can also use fastboot mode to flash the correct partitions if you want by setting up adb and using fastboot commands with all the partition images. Its up to you.

Art Vanderlay said:
To access twrp try power + vol down then vol up + vol down. If that doesn't work then no you cannot access your recovery.
Your actually in a much better position than the guy in that guide. You've got download mode so you can skip to the easy part and just follow the back to stock guide.
You can also use fastboot mode to flash the correct partitions if you want by setting up adb and using fastboot commands with all the partition images. Its up to you.
Click to expand...
Click to collapse
Hey Vanderlay.
Thanks for your reply,
I tried to access recovery using your suggestion, but the time between turning the device on and "fastboot mode" is just to small to press key combinations.
You mentioned that i can use ADB commands to manually write on the G2 partitions. Honestly i don't know exactly what the problem is and therefore i have no clue which partitions have to be written on. What i understand is, that i cant boot because the kernel of the D800 is different from the D802. But i dont get, why i cant access recovery. Is TWRP somehow destroyed so i have to write a new one on the recovery partition or do i need the correct rom image to access recovery? If you could explain me this or have a link to a good explanation i would be very grateful.
[EDIT]
I have fast boot access. But as far as i know fastboot only allows to flash stock images (what a shame) as the commands are interpreted vendor specifc. Nevertheless i found that you can flash recovery by
Code:
fastboot flash recovery recovery.img
But as i don't know if the recovery is destroyed or the correct rom-image is needed to simply access recovery, i cant continue here.
Am I right assuming that there is know way to repair recovery, boot into it and simply restore from my backup? Do i realy have to go back to stock, re-root it and install custom recovery again, to be able to restore from my backup?

If you've got a system then just flash your original kernel
fastboot flash boot boot.img
and
fastboot flash aboot aboot.img
and
fastboot flash laf laf.img (download mode)
your original files please..

bender_007 said:
If you've got a system then just flash your original kernel
fastboot flash boot boot.img
and
fastboot flash aboot aboot.img
and
fastboot flash laf laf.img (download mode)
your original files please..
Click to expand...
Click to collapse
My backup is stored on the internal SD-card (as i was simply to lazy to transfer it to my PC). As i cant remove this card from my phone i don't know to flash the phone via fastboot.
Is there a way to command fastboot to acceess those files on the internal SD-card?
Or is there a way to transfer those files from the internal SD-card to my PC?

Download slimkat d802 kernel, extract boot.img and flash itcvia fastboot

bender_007 said:
Download slimkat d802 kernel, extract boot.img and flash itcvia fastboot
Click to expand...
Click to collapse
I downloaded the complete image for d802 and extracted the boot image. I connected the phone via fastboot and did
Code:
C:\Users\XX>fastboot flash boot boot.img
target reported max download size of 1862270976 bytes
sending 'boot' (6284 KB)...
OKAY [ 0.264s]
writing 'boot'...
OKAY [ 0.526s]
finished. total time: 0.797s
And then
Code:
C:\Users\hen>fastboot reboot
rebooting...
finished. total time: 0.104s
Now iam getting a secure boot error cause boot certification verify.
EDIT:
I cant access neither recovery, nor fastboot or download mode.

By "image" what exactly do you meanm

bender_007 said:
By "image" what exactly do you meanm
Click to expand...
Click to collapse
I downloaded the rom image. There i found boot.img and extracted it. I couldnt find a kernel file on the slimroms server. But should a complete rom also contain a kernel?
EDIT: As i cant access download-mode, fastboot or recovery i should continue here, right?

Exactly. I'll try to help you 2 out although I see you searched already

bender_007 said:
Exactly. I'll try to help you 2 out although I see you searched already
Click to expand...
Click to collapse
Ok, i continue with these instructions with my kubuntu laptop at home. This will be in about 1h.
[EDIT]
Ok back. My kubuntu was able to recognize my G2, i see all partitions. But i couldn't find the files for the 32GB Model, only 16GB. Some guys (Jilke, Ixan) had the same issue and bender_007 suggested to use the 16GB versions. But i couldnt find any confirmation, if the 16GB files worked for the 802.32GB. Have i overlooked a post, which confirmed this suggestion?

mellhen said:
Ok, i continue with these instructions with my kubuntu laptop at home. This will be in about 1h.
[EDIT]
Ok back. My kubuntu was able to recognize my G2, i see all partitions. But i couldn't find the files for the 32GB Model, only 16GB. Some guys (Jilke, Ixan) had the same issue and bender_007 suggested to use the 16GB versions. But i couldnt find any confirmation, if the 16GB files worked for the 802.32GB. Have i overlooked a post, which confirmed this suggestion?
Click to expand...
Click to collapse
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Do you need any further assistance ?

Hey bender_007 was it wrong to use the boot.img from the rom file instead of a kernel file?
bender_007 said:
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Click to expand...
Click to collapse
I used the files for the european 802 16GB device from here: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
The original thread says i should use 1- sbl1.img, 2- aboot.img, 3- rpm.img and 4- tz.img
Why do i not need slbl1, rpm and tz, but instead boot and laf? I dont get that (?).
[EDIT]
So i just started beginning with aboot. Which yours and the original instructions have in common. I didn't care about the bin-extension, as it usually makes no difference in linux.
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/4-aboot.bin of=/dev/sdb5
2048+0 Datensätze ein
2048+0 Datensätze aus
1048576 Bytes (1,0 MB) kopiert, 0,278651 s, 3,8 MB/s
Continued with boot. As you have recommended this (aboot, boot and laf) procedure to another guy in that thread, this seems to be an update to the original instruction?
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/6-boot.bin of=/dev/sdb7
21504+0 Datensätze ein
21504+0 Datensätze aus
11010048 Bytes (11 MB) kopiert, 2,97537 s, 3,7 MB/s
And finally laf
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/laf.bin of=/dev/sdb23
31744+0 Datensätze ein
31744+0 Datensätze aus
16252928 Bytes (16 MB) kopiert, 5,13812 s, 3,2 MB/s
So i will try to reboot in TWRP now.
[EDIT 2]
I cant access recovery. I see an LG logo without text and a blue-green pulsing LED. I can't turn the device of and it gets hot.
I had a lot nearly bricked devices, but now i get scared! How can i continue?
greetings

You can't get to twrp but tou can get to download mode. Turn the g2 off, disconnect it first. Then hold volume up and connect it to pc

bender_007 said:
You can't get to twrp but tou can get to download mode. Turn the g2 off, disconnect it first. Then hold volume up and connect it to pc
Click to expand...
Click to collapse
Ok, i really had cold sweat and have had to take a deep breath. It was the first time that i was really scared. In older devices you can pull the battery but this one is known to burn itself (or at least its screen).
I am now in download mode and it stopped heating. I had to first plug it in. Then turn it off and when it turned off press volume up. Shall i continue with the LG G2 Stock Firmware (Go Back to Stock)? Can i continue using linux?
OT: How far have you brought your devices to the abyss of death?

Yap. Use the flash tool 2014 . You're good to go

I followed the instructions and flashed "Europe OPEN D80220B_00". The process continued to 100% (both mobile and flash tool 2014). After this the phone rebooted, i could see the LG logo again and now it stays at the green droid "doing something" since 6 minutes. The phone is still connected to the Windows computer. Shall i wait a little longer? unplug the phone? reboot the phone?
[EDIT] i just took its time, it started finally! bender_007 how can i thank you for your patience(!)?

Np m8, you did all the work and research, that's the real way.

bender_007 said:
Np m8, you did all the work and research, that's the real way.
Click to expand...
Click to collapse

bender_007 said:
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Do you need any further assistance ?
Click to expand...
Click to collapse
Hi,
I need your help.
Flashed wrong kernel 16 g on 32 g
my G2 is now having below issues ,please help.
bootloop,touch screen problem,no recovery mode or fastboot mode,
download mode is working.
Couple of time it booted normally but touch is not working properly and then it goes for reboot.
I want to flash original kernel but i am not able to get into fastboot

[Help] I cannot get my zenfone 2 into recovery mode.

I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?

turdcannon said:
I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?
Click to expand...
Click to collapse
Tried adb?
Please press the thanks button if I helped you.
Sent from my C2305 using Tapatalk

turdcannon said:
I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?
Click to expand...
Click to collapse
It usually occurs simply because it cannot boot into recovery. This may be due to accidentally wiping the recovery partition, thus having no recovery to boot to at all, or that you flashed an incompatible recovery onto your device.
Fret not, just a few simple commands should get your phone back alive and kicking.
First, download the recovery.img (ZE550KL) at https://drive.google.com/open?id=0B6QXDUz9wzc9bUZaOHJsTzBhcVk
Then, boot your device into recovery mode.
Once done, type the command, in order,
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Do take note that you would need to have ADB tools installed, a reliable connection to your computer, ASUS drivers in order for your device to be detected, and some knowledge on where to place the recovery.img in order for the commands above to work. If you need any help, please feel free to ask. Also, since you did not state the variant of your device, I had put the ZE550KL recovery.img instead. If your device is of another variant, please inform me immediately and I will get the recovery.img up for you.

Rizzed said:
It usually occurs simply because it cannot boot into recovery. This may be due to accidentally wiping the recovery partition, thus having no recovery to boot to at all, or that you flashed an incompatible recovery onto your device.
Fret not, just a few simple commands should get your phone back alive and kicking.
First, download the recovery.img (ZE550KL) at
Then, boot your device into recovery mode.
Once done, type the command, in order,
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Do take note that you would need to have ADB tools installed, a reliable connection to your computer, ASUS drivers in order for your device to be detected, and some knowledge on where to place the recovery.img in order for the commands above to work. If you need any help, please feel free to ask. Also, since you did not state the variant of your device, I had put the ZE550KL recovery.img instead. If your device is of another variant, please inform me immediately and I will get the recovery.img up for you.
Click to expand...
Click to collapse
Thanks so much, this worked. I have a ze551ML but I had a stock recovery already on my drive. I've been trying to install the twrp recovery for the last two days but have been completely unable. Although the "fastboot oem reboot-recovery" failed as adb didn't recognize the OEM remote. Any idea why the most up to date twrp recovery has not worked in the least?

turdcannon said:
Thanks so much, this worked. I have a ze551ML but I had a stock recovery already on my drive. I've been trying to install the twrp recovery for the last two days but have been completely unable. Although the "fastboot oem reboot-recovery" failed as adb didn't recognize the OEM remote. Any idea why the most up to date twrp recovery has not worked in the least?
Click to expand...
Click to collapse
You need to unlock the bootloader first. There are plenty of guides online about how to do this, unofficial and officially. Also, there's a dedicated forum for your device variant, named "ASUS ZenFone 2"
This forum here is for the Laser variants.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

Bricked VS995 after Dirty Santa attempt - could use some help! :(

So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")

Kevin_xail said:
So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")
Click to expand...
Click to collapse
Use this thread https://forum.xda-developers.com/v20/development/vs995-kdz-t3527538
If you have verizon VS995
Follow the procedure in the thread https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
download these
VS99512A_06_1114_ARB00.kdz
lg-firmwares.com/download-file/?fileId=4889
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
LGUP_Store_Frame_Ver_1_14_3_3.msi http://downloads.codefi.re/autoprime/LG/LG_G5/LGUP
LGMobileDriver_WHQL_Ver_4.1.1.exe http://downloads.codefi.re/autoprime/LG/LG_G5/LGMobileDriver_WHQL_Ver_4.1.1.exe

I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!

Kevin_xail said:
I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!
Click to expand...
Click to collapse
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"

dwertz said:
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"
Click to expand...
Click to collapse
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!

Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
did you ever get any help? I would go directly to the dirty santa thread and make your issue known. I'm not sure how much help I could give you but if no one else is willing to help I can try.

Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
Did you flash the kdz using Uppercut?

imucarmen - I can't post in the dirty santa thread because I am a new member to XDA (been coming here for years just never made an account )
bond32 - Yes I was able to flash the .kdz using Uppercut+LGUP but my problem is not fixed. My phone still boots right to FastBoot Mode in the "Locked State" to where I can't issue any commands or alter any partitions.
This makes no sense to me if LGUP is able to 100% flash the stock firmware, WHY CAN'T I GET OUT OF FASTBOOT! Lol
Does anyone have any ideas as to what I could try to unbrick this thing?

I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5

Splinter 77 - Thank you for the suggestion. I have been trying to get this tool to work for a couple hours and everytime it hangs on the Downloading Firmware section. No matter what I try I can't get it to download the firmware....

Does anyone have some ideas I can try? I'm up for anything at this point!

Kevin_xail said:
Does anyone have some ideas I can try? I'm up for anything at this point!
Click to expand...
Click to collapse
Did you try pulling the battery, put the battery back in.
Hold the volume down and power button at same time. When the lg logo shows up let go of the power button but continue to hold the volume down and press the power button again. It will bring you to a screen tgat has 2 questions. Answer yes to both of them. Then reboot. I believe that resets the way the phone boots almost like resetting a cmos
Sent from my VS995 using XDA-Developers Legacy app

im in the same boat now... ugh
---------- Post added at 06:01 PM ---------- Previous post was at 05:56 PM ----------
ahh i got it man! @Kevin_xail
i dont know if this will help seince u relocked, but do the factory reset dance
hold the vol down and power and put in battery as soon as its on click the power button and re hold it. it will get to recovery, it took me hours but its there.

I had tried that a few times after reading about it but I'll try now for an extended period of time and see if I can activate it. I'll report back with what happens, thanks for the tip dwertz and Team DevDigitel

Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?

Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
When you have a unlocked boot loader and you do a factory reset, I believe it wipes the OS from the phone giving you no OS. If you can get back to recovery, flash this rom https://forum.xda-developers.com/v20/development/vs995-vzw-nrd90m-modded-notsostock-rom-t3525864
That will at least get you booted so you can flash the kdz.

I can't get into any kind of recovery to flash a rom though

Kevin_xail said:
I can't get into any kind of recovery to flash a rom though
Click to expand...
Click to collapse
How long ago did you get the phone?

Bricked with locked Bootloader on fastboot
Splinter77 said:
I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5
Click to expand...
Click to collapse
I was bout ready to give up, got it working with newest lg up and stock flash file from lg support website, I haven't seen a whole lot (any) solved posts so I thought I would share. At least got it working again, rooted is another story.

Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
Same problem here, did you ever fix it?

Videotron LG G2 Nightmare

I would like to thank this wonderful community for all the help I have gotten over the years, I think this should be my first post.
For technical details of all I have done and learned on recovering the damn phone, skip to below the line, the rest is more of an introduction + some history.
In the past I have had a Canadian (BELL) Samsung Galaxy S2.5 as I like to call it. Specs similar to the S3 but not quite.
That was fairly easy to root thanks to odin.
Anyways, I have an LG G2 that I inherited from my brother, so I have some emotional attachment given he passed away 2 years ago (Age 36)... Reason why it is critical that I fix it.
I feel it's a great phone with excellent specs, with some flaws.
Hardware wise, this phone's digitizer seems to fail after a few years and stops registering touches.
Failed on my brother after 8 months, he got it replaced by videotron.
8 months after my ownership, same issue. I replaced the screen, which is a pain.
I dropped it a year later and broke the screen, replaced again.
Replaced the battery twice (First replacement battery was DOA) and... The internals of this phone are a pain to work with... to my limited experience at least.
The get to the point line as stated above.
___________________________________________________________________________________________
I wanted to flash my 4 year old never reinstalled phone, give it new life.
Researched a bit everywhere, verified in the phone what version it is, even most google results tell me this and the replacement screen is all the same.
it's a D801
After some work and research being clueless about working with this model, I finally installed
Started with getting Dev powers by spamming a specific key, setting usb debugging...
Using some application manager.
Installed
D801_AutoRec.apk
Towelroot.apk
From autorec, I installed the twrp and... fastboot... had no idea what that was.
Here I learned how to recover my phone.
This guy... super helpful.
Youtube link removed to post
So in short Download all the necessary drivers to get the android device detected.
Download those
codefi re link removed
I erased and flashed so often now that I scripted it in a batch file
Notepad, save as (not as text) flash****.bat or whatever you want to call it.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot erase dbi
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase rpm
fastboot erase stl1
fastboot erase tz
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash recovery recovery.img
fastboot flash laf laf.img
fastboot flash dbi dbi.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash PrimaryGPT PrimaryGPT.img
fastboot flash rpm rpm.img
fastboot flash stl1 stl1.img
fastboot flash tz tz.img
Originally, I only did boot aboot recovery and iaf
After that, my phone rebooted to the LG logo and stuck, but the Download mode is working again.
At that point I did flash a twrp recovery and was able to run it using the command abd reboot recovery
I pushed different roms, but no matter what I do, always back to fastboot.
Found this video later on, originally found a thread here but for the life of me I can't find it anymore (too much history) (How to recover with LG Tools the original kdz
youtube link removed
Now... I could not find the correct firmware
I used this
T-Mobile KitKat D80120A_00
IT worked, my phone restarted as it was before my adventures, but under a tmobile d801
Here I am happy, I get the proper D803_AutoRec.apk
Install the recovery again...
Now I really broke my phone.
Retried the steps above of flashing aboot and so on...
Refuses to work.
So I figured, hey, I recovered it under D801 tmobile... I probably broke it with the D803 recovery.
Back to the download site, made another folder and downloaded all the D801 img's
Ran my script (well that's when I created it from being sick of typing it)
Now I boot Tmobile but it's stuck to All Auto Test - FTM Mode
SUrprisingly on wifi,, shows missed calls and picking up exchange emails...
When I try to Flash as I have before under download, it fails.
SO hey, it found a 300MB tmobile update... why the hell not at this point.
Can anyone link me the proper software I can try to recover the LG Tools ?
csmgdl link removed
and
csmgdl link removed
Don't seem to work
Did I mess it up beyond repair ?
Any recommendations ?
I am hoping for one of the following
If I get tmobile OS working
Retry the D801_AutoRec.apk given it matches the tmobile recovery that somewhat works and then attempt the original goal of setting up CloudyFlex_2.8, CloudyStock_2.7 or cm-12-20150325-UNOFFICIAL-d803
Pretty sure up there, most of those wont work, I just want a working twrp
All I want is this phone wiped with a clean efficient rom to use as a reliable daily.
All I do is phone, text, exchange, camera, some apps... nothing too fancy.
I am off to sleep

Whatever I do, I can't get out of All Auto Test = FTM Mode
Reboot, hold volume up
Down
Up and down
Power up
Power down
Power vol up and down...
Always to all auto test.
Swipe down, get to options, general, do a full factory rest...
Same thing. Grr

Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.

Turbine1991 said:
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Click to expand...
Click to collapse
I have gone to download mode before to recover an oem image.
Now, I can't get to download mode after trying a number of times.
Ill give it another go tonight. Yesterday I got tired from the research, trial and error.
Thanks for your reply

With a calm mind, I fixed my issue.
https://forum.xda-developers.com/showthread.php?t=2613404
Press and hold power + Vol up and tap normal boot.
Didn't understand that at first.
Now let's see if I will break it again.
Still unsure if I should root it using D801_AutoRec.apk or D803_AutoRec.apk
Reason why I hate this phone.
Videotron LG G2 writes that it's a D801 but I read in other sources that it's a D803.
Now however, it's been restored to a Tmobile Firmware...

Okay, take it really slow. I've just completely rooted, put a custom recovery on and am now on Android N. There's many things which can go wrong - requiring you to restart the process.
Treat it as a D801, as the T-Mobile firmware booted. AutoRec does not root the device. Are you on KitKat or Jellybean? If you're on KitKat, do the following.
You must use IORoot to root the device - it does it in such a way it'll accept custom recoveries.
(You already have the phone's USB drivers obviously)
1) Download IORoot V25 from here.
2) Extract the file.
3) We need to unlock USB debugging, so make sure the phone is not connected to the pc. Settings -> About -> Software -> Tap on "Build" like 8 times fast. Go back into settings and you'll see "Developer Options", tick USB debugging. Now if your device freezes up like mine did when tapping build, then download an app which lets you go directly to developer options.
4) Hook the phone up to the PC, make sure it's not in lock screen.
5) Double click "root.bat" normally (not as admin). Keep going through this process until it brings you to the stock recovery area where you can flash over ADB.
6) It'll walk you through the process where it boots back into Android.
7) Open SuperSU, which it installed.
8) In the settings somewhere, make the grant always accept rather than prompt. My device was bugged not allowing root unless it was forcefully granted like this.
AutoRec - Recovery Install
1) Copy the contents "bumpboot-v1.0-blastagator-signed.zip" and "busybox.apk" and "flashify.apk" onto your device. Download here.
2) Download TWRP for T-Mobile 2.8.6.0 from here, extract recovery.img and copy that onto your device.
3) Copy AutoRec KitKat for T-Mobile here.
4) So you should now have "D801_AutoRec.apk", "recovery.img", "busybox.apk", "flashify.apk", "bumpboot-v1.0-blastagator-signed.zip" on your phone.
5) Proceed to install "AutoRec.apk", ticking unknown sources. Let it boot into recovery. Now reboot.
6) As my recovery didn't stick, install and open "busybox.apk", click install in the program itself. Install and open "flashify.apk", flash recovery, browse using flashify to the location of "recovery.img", let it reboot into recovery. This is where I had to flash "bumpboot-v1.0-blastagator-signed.zip", otherwise I couldn't boot into the OS. So flash that file.
7) Reboot back into the OS. Until we flash lollipop, there wasn't any other way for me to reliably get into TWRP recovery without repeating step 6.
8) Copy over the Bootstack and Stock Rom from here. Don't worry about SuperSU or anything else.
9) Repeat step 6 to boot back into recovery.
10) Wipe everything except internal memory in TWRP.
11) Flash the lollipop bootloader.
12) Flash the lollipop stock rom.
13) Reboot.
14) Now you're able to get back into recovery any time by holding the power + volume down combo, releasing when the screen goes on - and holding it down again.
15) Feel free to flash LineageOS 14.1 or anything afterwards. Make sure to backup your EFS partition at some stage before this - just incase you can't connect to cell towers in the near future.
As you can see, I had to improvise a bit. No guide was good enough to just work in 2017 for my D800. These should work fine for your D801.

Thank you so much for such an amazing and detailed response !!!
After quite a bit more research and work, I got it rooted and got TWRP working.
Once done I uploaded cloudyflex 2.8
Installed it and of course, me being me, chose the wrong install when prompted. It asked Tmobile, other and Canadian 803.
I chose Canadian and after that got back to fast boot.
After that I simply erased boot, aboot and laf, getting ready to restart from scratch but it rebooted on a clean cloudyflex 2.8.
At this point, the phone is running better then stock and I am very happy with it
Your walkthrough is great and I will certainly redo my phone soon again.
For one, practice makes perfect and I certainly like that with your instructions, I will be able to call on the recovery when I want it instead of asking my way into it by adb command.
Thank you again for your time
This community rocks !

Feel free to thumb me. I also have a request for you, I'll PM.

Trying to flash TWRP but no success (stuck on Fastboot mode)

I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.

You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.

Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.

How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader

Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?

Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there

Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?

Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.

smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then

Curious did you have the twrp file in same folder as adb and fastboot?

smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply