Related
I have an LG G2 AT&T D800.
After I rooted my phone successfully, I also flash a custom recovery successfully.
After I did that, I wipe out my data / cache.
And i tried to install a ROM and Google Apps.
I rebooted my phone and I'm stuck with " Fast boot mode started "
I had download mode working but i accidentally made it stop working after i did CMS88168 steps from this page.
http://forum.xda-developers.com/showthread.php?t=2477595
Now I don't have my download mode starting to work and I have no clue on how to fix my phone.
Please help.
alvingaoat said:
...
I rebooted my phone and I'm stuck with " Fast boot mode started "
...
Now I don't have my download mode starting to work and I have no clue on how to fix my phone.
Click to expand...
Click to collapse
Look here
It's for the F320 variants but there is also a link to search for other variant files.
Also just in case you are unable to do what phoost suggested, what i did was keep tr ying to get into recovery, the lg logo would blink fast, but you just have to keep tr ying, and i finally got it and reflashed my rom and its been fine ever since...i did get scared tho, but my g2 is only 4 days old right now, so i can always return and get another, but just do what i said
help
MasterSe7en said:
Also just in case you are unable to do what phoost suggested, what i did was keep tr ying to get into recovery, the lg logo would blink fast, but you just have to keep tr ying, and i finally got it and reflashed my rom and its been fine ever since...i did get scared tho, but my g2 is only 4 days old right now, so i can always return and get another, but just do what i said
Click to expand...
Click to collapse
My lg g2 is stuck in fastboot mode started/usd start() an I press the buttons to go to recovery mode but recovery mode just flashes on the screen an it goes back to fastboot mode screen
larryb723 said:
My lg g2 is stuck in fastboot mode started/usd start() an I press the buttons to go to recovery mode but recovery mode just flashes on the screen an it goes back to fastboot mode screen
Click to expand...
Click to collapse
I am having this issue. Has anyone figured out how to fix? I need download mode to return to stock.
Droc1983 said:
I am having this issue. Has anyone figured out how to fix? I need download mode to return to stock.
Click to expand...
Click to collapse
i got the same problem here when flashing the slimkat.
fastboot is like adb sideload.
when you see the usb command, you need to plug the phone to the PC to sync them.
This happened to me a while back the link in post two is how I solved it. You just need to find the laf.img for your model, put it in the same folder as adb and run the adb commands in the tutorial. You might have to change the directory in cmd prompt to where adb is located. Once the laf is successfully flashed you can boot into download mode and flash the kdz for your model.
Swizzle82 said:
This happened to me a while back the link in post two is how I solved it. You just need to find the laf.img for your model, put it in the same folder as adb and run the adb commands in the tutorial. You might have to change the directory in cmd prompt to where adb is located. Once the laf is successfully flashed you can boot into download mode and flash the kdz for your model.
Click to expand...
Click to collapse
I tried this but it starts download mode but then goes to fastboot. I was trying to keep download mode. I used the laf.img in the the link you posted. I'm on verizon lg g2 is that the right laf.img?
***Got it thanks***
In the link above that is for the Korean g2 I believe. If I remember correctly there's a link to other img files in his thread. You might also consider flashing the proper boot.img as well. It was a while ago that this happened so I don't recall exactly but if you flash the Verizon boot.img and laf.img you should be good.
Phoost said:
Look here
It's for the F320 variants but there is also a link to search for other variant files.
Click to expand...
Click to collapse
that link is not working
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
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
My 501CG is in a bootloop and can't go to recovery.
The device can be detected by adb but I can't sideload anything. I've tried everything I know but couldn't fix it.
I tried to post a screenshot but the forum won't allow me and I can't explain what the problem looks like so I don't know what to do now...
Please help me. Thank you.
Teks0427 said:
My 501CG is in a bootloop and can't go to recovery.
The device can be detected by adb but I can't sideload anything. I've tried everything I know but couldn't fix it.
I tried to post a screenshot but the forum won't allow me and I can't explain what the problem looks like so I don't know what to do now...
Please help me. Thank you.
Click to expand...
Click to collapse
Can you go to fastboot? Adb still reconize it then go to ADB and type adb reboot bootloader then try to flash the recovery and factory reset. If the problem still exist after factory reset you will need to look up for system.imgs files for the zenfone 5 and flash the system imgs from fastboot
ChristopherXI said:
Can you go to fastboot? Adb still reconize it then go to ADB and type adb reboot bootloader then try to flash the recovery and factory reset. If the problem still exist after factory reset you will need to look up for system.imgs files for the zenfone 5 and flash the system imgs from fastboot
Click to expand...
Click to collapse
Thank you so much for helping me.
When I type adb reboot bootloader, it says <waiting for device> and stays that way.
I have a screenshot of the error but I can't post the proper link. Here's a modified version of the link, just replace the <dot> with a period I guess if that would work. That's the only way I can show what happens to the phone.
imgur dot com/JRcEzaN
Sorry, I'm also not very familiar with how adb, fastboot, and whatever else works, but I learn fast and can follow commands.
Well the mmcblk1 partition i think is messed up @dgadelha can you help us with this?
Hey there!
Thanks @ChristopherXI for noticing me.
@Teks0427, can you please try this guide? It will rebuild your partition table and install Android 4.3.
Hope it helps!
dgadelha said:
Hey there!
Thanks @ChristopherXI for noticing me.
@Teks0427, can you please try this guide? It will rebuild your partition table and install Android 4.3.
Hope it helps!
Click to expand...
Click to collapse
Thank you! I'll try this as soon as I get home. I hope it works...
Well. Did it work? Have any luck?
I'm so sorry for disappearing all of a sudden like that. I had to attend to a LOT of things and I totally forgot about the phone.
I'm gonna give it a go tonight and post whatever happens here right away.
Thanks guys! I really appreciate the help...
Hi! The phone won't go to droidboot mode. PressingPOWER + VOLUME UP brings me to the Asus bootup screen (sometimes with a black background and sometimes with a blue one) and the words
CSC Mode
long press power key to restart system
And sometimes it's just the normal Asus bootup screen (and gets stuck there). On that CSC mode screen, plugging in the USB and typing "fastboot devices" does nothing
D:\501KL>fastboot devices
Booting up in recovery mode works, and when in the recovery mode menu page, typing "fastboot devices" still does nothing but typing adb devices gets this response:
D:\501KL>adb devices
List of devices attached
051c7013 recovery
D:\501KL>
Running (as administrator) the file sec_offline_update_image.cmd from the recovery menu page gets this response:
D:\501KL>fastboot oem backup_config
< waiting for device >
And it stops there.
Also, when plugging the USB cable to the phone, it starts installing an "MTP USB Device" but always fails after a few minutes.
I already tried bringing the phone to the accredited Asus Zenfone repair center here in the Philippines but they said they don't have the firmware to flash this model. They didn't give any explanation nor did they refer me to anyone else who might know how to fix this thing.
@dgadelha @ChristopherXI
I have same problem but now my phone working properly
first download https://drive.google.com/file/d/0B3vLobe8_2u7SWlzZXVTYmFVcXc/view?pref=2&pli=1
and this http://www.mediafire.com/folder/7qapfy4zqvxf6 no need Zenphone4 and Zenfone6
System img and fastboot, recovery and boot file of kitkat https://docs.google.com/file/d/0Byaxd8-Kv2ZISnN4WTZVbXhpeDQ/edit?pref=2&pli=1
http://www.mediafire.com/download/4jb1mlipfrdz3cp/ww+asus-zenfone.com.rar
after that http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
fastboot flash dnx .\sec-dnx_fwr.bin
fastboot flash ifwi .\sec-ifwi-prod.bin
fastboot flash boot .\boot_sign.bin
fastboot flash recovery .\recovery_sign.bin
fastboot flash fastboot .\droidboot_sign.bin
save and run
than your in Kitkat and your problem of Can't mount /cache/recovery/log solved.
rashmi0733 said:
I have same problem but now my phone working properly
first download https://drive.google.com/file/d/0B3vLobe8_2u7SWlzZXVTYmFVcXc/view?pref=2&pli=1
and this http://www.mediafire.com/folder/7qapfy4zqvxf6 no need Zenphone4 and Zenfone6
System img and fastboot, recovery and boot file of kitkat https://docs.google.com/file/d/0Byaxd8-Kv2ZISnN4WTZVbXhpeDQ/edit?pref=2&pli=1
http://www.mediafire.com/download/4jb1mlipfrdz3cp/ww+asus-zenfone.com.rar
after that http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
fastboot flash dnx .\sec-dnx_fwr.bin
fastboot flash ifwi .\sec-ifwi-prod.bin
fastboot flash boot .\boot_sign.bin
fastboot flash recovery .\recovery_sign.bin
fastboot flash fastboot .\droidboot_sign.bin
save and run
than your in Kitkat and your problem of Can't mount /cache/recovery/log solved.
Click to expand...
Click to collapse
Read his problem carefully.
He has a 500KL not a 500CG.
That guide will not work
Apologies for saying thus but if there are no RAW firmware of the LTE model. It's pretty hopeless
Teks0427 said:
Hi! The phone won't go to droidboot mode. PressingPOWER + VOLUME UP brings me to the Asus bootup screen (sometimes with a black background and sometimes with a blue one) and the words
CSC Mode
long press power key to restart system
And sometimes it's just the normal Asus bootup screen (and gets stuck there). On that CSC mode screen, plugging in the USB and typing "fastboot devices" does nothing
D:\501KL>fastboot devices
Booting up in recovery mode works, and when in the recovery mode menu page, typing "fastboot devices" still does nothing but typing adb devices gets this response:
D:\501KL>adb devices
List of devices attached
051c7013 recovery
D:\501KL>
Running (as administrator) the file sec_offline_update_image.cmd from the recovery menu page gets this response:
D:\501KL>fastboot oem backup_config
< waiting for device >
And it stops there.
Also, when plugging the USB cable to the phone, it starts installing an "MTP USB Device" but always fails after a few minutes.
I already tried bringing the phone to the accredited Asus Zenfone repair center here in the Philippines but they said they don't have the firmware to flash this model. They didn't give any explanation nor did they refer me to anyone else who might know how to fix this thing.
@dgadelha @ChristopherXI
Click to expand...
Click to collapse
The sec_offline_update_image is for A500CG/A501CG only.
I'm sorry but I do not own an A501KL so I can't help you with that.
And if ASUS can't help you, sue them for that.
Bro You Should change your """Title:501CG Can't mount /cache/recovery/log ... etc"""
Yes, I'm so sorry. I noticed the error in the title just now. I got confused with my 2 Asus phones that I put the wrong model in the title. Stupid stupid me...
I'm so sorry for the mess.
Thank you all for your help...
I guess it will help you...
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
a8962383 said:
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
Click to expand...
Click to collapse
Thank you very much! I will try this as soon as possible...
rashmi0733 said:
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
can you please expalin this paragraph ,can't really understand .
i have everything ready from the links you provided
please reply asap
Click to expand...
Click to collapse
RONUAA said:
rashmi0733 said:
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
can you please expalin this paragraph ,can't really understand .
i have everything ready from the links you provided
please reply asap
Click to expand...
Click to collapse
If You have A501CG than Its Work
use this method
https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
Click to expand...
Click to collapse