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
Related
Hello All,
I've been searching for hours. I had rooted my LG G2 weeks ago with no problems. I then un-rooted it and I thought reset it to factory. Today in Target I pulled it out of my pocket to make a call and it was black screened to Fastboot.
I have tried holding down Volume - and Power and entering recovery to reset to factory but it immediately goes to Fastboot loop.
I have tried holding down Volume + while plugging in USB for Download Mode but it immediately goes to Fastboot loop.
I have tried adb commands, error: device not found.
I have tried manually updating the Android drivers through Computer Management and selecting many of the Android Platform Sooner versions. My Win7 PC recognizes the phone as ADB Interface > Andriod Sooner Single ADB Interface in Device Manager.
I have tried this http://forum.xda-developers.com/showthread.php?t=2477595 and flashed both laf.img and I cannot get into Download Mode.
What else can I do? Does anyone have any other ideas?
Thanks for your time!
hey same exact thing just happened to me. i had it rooted from earlier, but ended up keeping the stock rom on my AT&T LG G2 D800. What I think happened was ATT just pushed out an OTA update (not sure about other carriers), supposedly some small 15mb update to prepare for upcoming releases and despite declining the install, the phone of course did it anyways.
No recovery, no download mode, factory reset doesn't do anything.
Thanks AT&T! :good:
Are we completely boned here?
This worked for me
http://forum.xda-developers.com/showthread.php?t=2451696
Follow this thread, I tried the TWRP terminal code and it worked. Let me know how it goes
Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.
sniffs said:
Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.
Click to expand...
Click to collapse
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/showthread.php?t=2582142
(actually kind of sounds like fun to me)
if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.
autoprime said:
if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.
Click to expand...
Click to collapse
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!
im onthe verizon variant and stuff like this just annoys me to no end you say no lg pushes it to your device anyway its wrong not even samsung stoops this low i am glad i have a custom rom
sniffs said:
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!
Click to expand...
Click to collapse
what site?
Sorry for comment this old post, but i need help with my D800 y cant unbrick it
Keep trying flashing the D800 file or what?
Hello friends to see if I draw from this setback. My situation is that I have no recovery or download, but when trying to get the img fastboot does not exceed by "erasing" or "writing" who knows how to solve this please !!
Thank you :good:
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Kybby said:
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Click to expand...
Click to collapse
that is because the download mode partition is broken because it is the wrong model; if you download the correct model of autorec you can use WinRAR/7zip to get the laf.img from the assets folder and then flash it using adb; I know the process to flash the images through fastboot as long as your device is recognized by your pc I can help
a new hope
XxZombiePikachu said:
that is because the download mode partition is broken because it is the wrong model; if you download the correct model of autorec you can use WinRAR/7zip to get the laf.img from the assets folder and then flash it using adb; I know the process to flash the images through fastboot as long as your device is recognized by your pc I can help
Click to expand...
Click to collapse
Very good files Extracted I see the laf I need to use. So are you saying if pc sees the device I can flash using fastboot but if it doesn't I will have to flash via ADB... right? I'm such a newbie.
Kybby said:
Very good files Extracted I see the laf I need to use. So are you saying if pc sees the device I can flash using fastboot but if it doesn't I will have to flash via ADB... right? I'm such a newbie.
Click to expand...
Click to collapse
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Awesome Just Awesome!!
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase boot
fastboot flash boot.img
fastboot erase laf
fastboot flash laf.img
fastboot erase recovery
fastboot flash recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
Dude, I read those instructions from all over the net but I guess I needed this divine intervention. You have no idea how greatful I am for your assistance. Current situation: Download mode is back and LGmobile support tool is doing its download thing for stock rom.
I have to add that I was receiving an error message from CMD prompt for command:
fastboot flash laf.img
I replaced that by:
fastboot flash laf laf.img
and was abble to finish the rest.
Good safe rooting to all the rooters!
Kybby
PS: too bad I can only thank you once on this one...
Kybby said:
Dude, I read those instructions from all over the net but I guess I needed this divine intervention. You have no idea how greatful I am for your assistance. Current situation: Download mode is back and LGmobile support tool is doing its download thing for stock rom.
I have to add that I was receiving an error message from CMD prompt for command:
fastboot flash laf.img
I replaced that by:
fastboot flash laf laf.img
and was abble to finish the rest.
Good safe rooting to all the rooters!
Kybby
PS: too bad I can only thank you once on this one...
Click to expand...
Click to collapse
Glad it all worked out and thanks for pointing that out for some reason I always forget that fastboot needs the partition name before the image name (trust me it isn't first time I make the mistake but we ain't perfect)
If you decide to go at it again make sure to use correct version of autorec and enjoy your device :high-five:
Sent from my Pikachu powered LG D800
Are you kidding me?!?!
XxZombiePikachu said:
Glad it all worked out and thanks for pointing that out for some reason I always forget that fastboot needs the partition name before the image name (trust me it isn't first time I make the mistake but we ain't perfect)
If you decide to go at it again make sure to use correct version of autorec and enjoy your device :high-five:
Sent from my Pikachu powered LG D800
Click to expand...
Click to collapse
You're not serious right? Tell me you're joking!
With ppl like you around I'm no longer worried. This was a learning experience.
Guess what.... G2 now rooted with correct autorec version... TWRP is enabled and BusyBox is in da house too. Next step... create a backup after deleting all these spying resources hungry LG default apps and then... ENABLE 4K video capture!
Amigo, I told you You just made this dude's week.
By the way if you think I forgot something importand pls advise. I read somewhere it was a good thing to save efs or something.
Kybby said:
You're not serious right? Tell me you're joking!
With ppl like you around I'm no longer worried. This was a learning experience.
Guess what.... G2 now rooted with correct autorec version... TWRP is enabled and BusyBox is in da house too. Next step... create a backup after deleting all these spying resources hungry LG default apps and then... ENABLE 4K video capture!
Amigo, I told you You just made this dude's week.
By the way if you think I forgot something importand pls advise. I read somewhere it was a good thing to save efs or something.
Click to expand...
Click to collapse
Yea backing up efs is important since that is where your imei is and if something happens to it you can restore it using efs backup, am not near pc right now to link the guide will update when home
update:
efs backup with ioroot
efs backup guide
Sent from my Pikachu powered LG D800
OK buddy. Was I supposed to do this before Root or its OK to do now?
Kybby said:
OK buddy. Was I supposed to do this before Root or its OK to do now?
Click to expand...
Click to collapse
It is okay to do it now; if I remember correctly it is something that can only be done while rooted
Sent from my Pikachu powered LG D800
Awesone... Friday evenings! I'll definitely do it later tonight and will update you on it. Thanks a bunch for all the kind help
Hi I've been studying this thread because I have the same problem--used the wrong version of autorec and now my Verizon LG G2 is stuck in fastboot. I've downloaded the correct version of autorec but I do not understand how to open the apk to access the assets file. I right click but get no option to open or extract. Can anyone help me, or direct me to a link where the laf.img files are stored? Thanks!
davidargent0628 said:
Hi I've been studying this thread because I have the same problem--used the wrong version of autorec and now my Verizon LG G2 is stuck in fastboot. I've downloaded the correct version of autorec but I do not understand how to open the apk to access the assets file. I right click but get no option to open or extract. Can anyone help me, or direct me to a link where the laf.img files are stored? Thanks!
Click to expand...
Click to collapse
Hello David, sorry to hear you're in the same mess. Sorry I just got to read your message. Please tell me if you still need assistance. I will do my best to get you out of it...
Kybby said:
Hello David, sorry to hear you're in the same mess. Sorry I just got to read your message. Please tell me if you still need assistance. I will do my best to get you out of it...
Click to expand...
Click to collapse
Thanks, but I took it to a shop that borked it completely. Just sold it on the Bay. Picked up a Moto X off Craig's...lol...oh well, the Moto is pretty cool and since it's running 4.4.4 I can't do anything to it until someone figures out how to unlock the bootloader...probably for the best...
Kybby said:
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Click to expand...
Click to collapse
Hi,
do you have an idea wich autorec is nessesary for a G2 shipped from HongKong. Ic guess I have the same issue like you. But on the case I have a D802 lable. So I thought it must be the one for a D802. May I'm wrong?
Now I tried a D800 one and it worked as I could start my phones download mode. After starting it I installed different roms but all had strange behavior like wrong touch an just flipping arround after touching. There is also no chance to connect to the network. Later I saw that my G2 32GB only shows 10GB of internal storage when its connected to pc. Any idea what I did wrong?
I would be very thankfull for help!!!!
Thanks
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
thought it was working cause it was most progress ive seen in months but now im totally stuck in bootloop mode at the LG screen, i can get to download mode but that just sticks on the firmware update page with 0% progress and i can't get adb to recognize my phone now. arrrrrrrg this is my main phone what can i do now to fix this?
need help asap
please and thank you
paul
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks alot it worked for me but my phone is stuck in download mode whilst installing firmware at %60 every time saying the phone is disconnected from pc ... any idea please
Thanks in adv
So I have read alot about this problem and not one can help me fix my phone.
I got an lg g d802t Australian version I cannot acces anything Lg screen pops up and striaght to fastboot mode... iv tried posting on the other help thread but i need this fixed asap.... and no1 has replied to my post so im making a thread.
Iv tried using fastboot cmd command or w/e but it gets stuck at waiting for device. tried downloading the driver for fastboot still happens. Iv tryd almost everything out there and yet i cant find what im doing wrong. following intrustions one by one and somehow i still cant get it working.
All the does is power on, logo comes up and boom fastboot mode. No recovery mode no hold down and power button nothing happens.
when connected to usb i hear a ding and my phone comes up with -reset- -portcharge- about 3times and then nothing.
download google adb driver, select it from the list - you can select nexus..
then "fastboot devices"
then you would need your partitions, aboot, boot, laf from the same compilation to proceed.
bender_007 said:
download google adb driver, select it from the list - you can select nexus..
then "fastboot devices"
then you would need your partitions, aboot, boot, laf from the same compilation to proceed.
Click to expand...
Click to collapse
changed computers finaly got somewhere downloaded the right drivers and other stuff now i can access the fastboot on my phone from cmd.
i then followed the other thread i posted on the fix thread (i think you know what im talking about)
and then after the erase laf part of it and then flash a new laf all working fine but now error cannot open laf
what now ?
Put laf on the c:\ . then fastboot flash laf c:\laf.img
bender_007 said:
Put laf on the c:\ . then fastboot flash laf c:\laf.img
Click to expand...
Click to collapse
works! but now after that step holding volume + and insert usb gets me back to fastboot mode not download mode...
is there a way i can flash a new system while in fastboot mode?
You should flash aboot, boot, laf and if you want the recovery.
bender_007 said:
You should flash aboot, boot, laf and if you want the recovery.
Click to expand...
Click to collapse
YES! thankyou so much i didnt flash recovery but now i can get into download mode so now im going to try and go to guide number 2 http://forum.xda-developers.com/showthread.php?t=2432476
ill get back to you if it it works thankyou again
thankyou got it working again! thanks alot man!
You'll be fine
Hi.
I think I should stop and ask for advice before trying anything else.
I have just received a 32gb D802 (International I think) with build KOT49I.D80220b and baseband M8974A-AAAANAZM-1.0.190082
It was pre-rooted. Root worked fine after updating SU binary. I downloaded twrp 2.8.0.1 from within flashify and installed it.
It displayed status 7 during recovery flash. I notice it already had philz touch recovery installed at the time rather than stock recovery.
I then tried D802_AutoRec.apk
On reboot it is stuck in fastboot mode displaying "Fastboot mode started".
I've plugged it in to usb on pc after installing minimal ADB.
What's my next step? I'm worried it may not be charging and I have limited time before it dies?
Edit: To correct sequence of events.
link
bender_007 said:
link
Click to expand...
Click to collapse
Thank you.
I ran pokreni.bat and all operations appeared to complete successfully
However on reboot following 15 seconds pressing power button it just goes back to fastboot mode
Try powering off the device.
Hold volume up - then connect usb to computer.
Is download mode alive ?
anyway - which package(philz) did you flash anyway ?
bender_007 said:
Try powering off the device.
Hold volume up - then connect usb to computer.
Is download mode alive ?
anyway - which package did you flash anyway ?
Click to expand...
Click to collapse
It doesn't power off fully it reboots. If I hold (and continue to hold) volume up immediately following exit from fastboot mode it just goes back to fastboot mode.
All I've flashed since receiving the phone is twrp 2.8.0.1 from within Autorec
Edit, sorry I'm wrong. I downloaded 2.8.0.1 from within flashify
I ask because of this: "I notice it already had philz touch recovery installed at the time rather than stock recovery."
Autorec installs 2.7.0.0
So if you downloaded the right version of 2.8.0.1 / 2.8.0.2 it should work (updating = installing from current TWRP - not philz)
EDIT: long hold the power..long long..until it's off ( cable should be disconnected)..then when you're sure it's off - hold volume up and connect to cable and obviously PC.
bender_007 said:
I ask because of this: "I notice it already had philz touch recovery installed at the time rather than stock recovery."
Autorec installs 2.7.0.0
So if you downloaded the right version of 2.8.0.1 / 2.8.0.2 it should work (updating = installing from current TWRP - not philz)
EDIT: long hold the power..long long..until it's off ( cable should be disconnected)..then when you're sure it's off - hold volume up and connect to cable and obviously PC.
Click to expand...
Click to collapse
Philz was already installed when I received the phone but I didnt realize until I tried to flash twrp with flashify.
OK, I can get it to power off completely then when holding volume up and plugging it into USB/PC it briefly enters download mode then goes to fastboot again
EDIT: Should I try this recovery http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 then renaming it to recovery.img and re-running the .bat file you linked to previously after replacing the recovery.img there with the new one?
Edit2: Just to be clear (I was confusing myself) I did manage to run D802_AutoRec.apk immediately prior to the fastboot problem.
Edit3: I can get it to the factory data reset screen when attempting to enter recovery but it goes back to fastboot after I select Yes twice
Edit4: I have the 32gb D802. Perhaps something from here would help? http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware and I could fastboot flash the relevant partitions. I dont like the look of 16G Partitions though seeing as I have a 32gb G2.
Is there any more info I can provide? I bought it from http://www.aliexpress.com/item/Orig...uad-core-5-2-inch-Refurbished/2037229256.html where it says it was russian multilanguage although it came setup in English. It does say LG-D802 on the back and packaging just so you know I haven't confused the model.
obvious said:
Is there any more info I can provide? I bought it from http://www.aliexpress.com/item/Orig...uad-core-5-2-inch-Refurbished/2037229256.html where it says it was russian multilanguage although it came setup in English. It does say LG-D802 on the back and packaging just so you know I haven't confused the model.
Click to expand...
Click to collapse
Send me imei so i can find the right kdz for it or use your imei so you can download the propper kdz, extract it etc.
bender_007 said:
Send me imei so i can find the right kdz for it or use your imei so you can download the propper kdz, extract it etc.
Click to expand...
Click to collapse
Serial and IMEI sent. Thank you
Downloading D80220C_00 from http://lg-firmware-rom.com/
Edit: Got it.
Edit2: Extracted DZ - Whole bunch of BIN files
Good. Now take aboot, boot, laf...rename them proper to aboot.img, boot.img, laf.img
bender_007 said:
Good. Now take aboot, boot, laf...rename them proper to aboot.img, boot.img, laf.img
Click to expand...
Click to collapse
Done.
Anticpating the next move I have copied them into fastboot.exe folder on PC where I have the following .bat file from earlier
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot erase recovery
fastboot flash recovery recovery.img
Should I remove the recovery.img or use another?
Edit: Nail biting
For now remove the recovery. See if you can get dload mode. Remove also the lines mentioning recovery
bender_007 said:
For now remove the recovery. See if you can get dload mode. Remove also the lines mentioning recovery
Click to expand...
Click to collapse
Powered off, held volume up, plugged in. Cant get into download mode. Goes to fastboot
Tried getting into recovery but that goes to fastboot as well
Try putting the recovery then also
bender_007 said:
Try putting the recovery then also
Click to expand...
Click to collapse
flashed extracted recovery. No errors. Cant get into recovery or download mode though. Just goes back to fastboot.
bender_007 has been a great help via PM. Thanks. I hope he doesn't mind me asking another question here.
I'm at the stage where I downloaded and installed the recommended kdz rom based on imei number but when I flash it it's Korean and the touch screen registers touches in a different place so it's pretty much unusable.
I'd read that other 32GB D802 roms should be safe to flash so I tried the EE 32GB one from http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/United+Kingdom/ - This one installs but bootloops after a while (kernel panic?) and the touch screen mis-registration issue is still present.
All ideas gratefully received
Oh..btw..I see now it says refurbished. Can you open it up somehow and see if there are other seals ?
Or at least try flashing older firmware and give it on their warranty (if there is any warranty )
bender_007 said:
Oh..btw..I see now it says refurbished. Can you open it up somehow and see if there are other seals ?
Or at least try flashing older firmware and give it on their warranty (if there is any warranty )
Click to expand...
Click to collapse
Can the variant be identified from these pics?
Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.
nuqudlover said:
Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.
Click to expand...
Click to collapse
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip
Phoenix591 said:
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip
Click to expand...
Click to collapse
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:
nuqudlover said:
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:
Click to expand...
Click to collapse
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )
Phoenix591 said:
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )
Click to expand...
Click to collapse
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?
nuqudlover said:
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?
Click to expand...
Click to collapse
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)
Phoenix591 said:
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)
Click to expand...
Click to collapse
I already put your special patched to my Lgup..
nuqudlover said:
I already put your special patched to my Lgup..
Click to expand...
Click to collapse
Try uppercut then. Use upgrade mode if it works but partition dl mode is missing. Note uppercut asks for lg up version 1.14 . I can't remember what version the patched one is but you may have to reinstall that version instead.