Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Parinibbana said:
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Click to expand...
Click to collapse
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Phoost said:
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Click to expand...
Click to collapse
Thanks for the hint, but in fact I did not forget about it. I did replace the original one.
Parinibbana said:
Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Click to expand...
Click to collapse
Give this a try. It sounds like it will help.
http://forum.xda-developers.com/showthread.php?t=2582142
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Stuck in bootloop but can push files using adb-commands
I would like to add, that I can push files to the device over adb when I am inside CWM-recovery. I can even flash ROMs, but all that doesn´t help, since afterwards I will still be in bootloop.
If I knew which files are corrupted causing the device not to get beyond the LG-bootlogo, then I could replace the corrupted files over adb.
Any ideas?
Parinibbana said:
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Click to expand...
Click to collapse
I would try to use the method i suggested to restore your Download mode, I can confirm that it will work. Then use download mode to flash the factory *.kdz or *.tot file to your device via the LG recovery tool. I'm not an expert at this, but i think you should focus on getting download mode working, then you can restore your phone to stock fixing whatever partition is broken and keeping your phone from booting. This will get your phone back to a factory stock and booting condition, then work on modding it to the way you want.
As a side note If TWRP is not available for your device i would assume you could just substitute CWM in its place. This really doesn't matter if your only trying to get to download mode to restore your phone.
Have you tried ADB Sideload?
MK45A said:
Have you tried ADB Sideload?
Click to expand...
Click to collapse
No, what is it? How would ADB sideload help in my situation?
Do I even need it, since I can flash any ROM successfully from within normal CWM-mode and have full access to adb-commands from within CWM. But whatever ROM I flash, afterwards I am still stuck in bootloop.
How could sideload help with that?
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
In CWM, look for something like 'ADB Sideload' and then enable it.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
ADB sideload lets you push roms from your pc using command prompts to your phone.
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Have you tried out LG FlashTool?
MK45A said:
Have you tried out LG FlashTool?
Click to expand...
Click to collapse
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Parinibbana said:
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Click to expand...
Click to collapse
Can you write down the whole error or provide screenshots?
MK45A said:
ADB sideload lets you push roms from your pc using command prompts to your phone.
Click to expand...
Click to collapse
I see. This means, I don´t need to push the zip file to /sdcard/ beforehand, but can flash it directly from the laptop, right?
Here is a screenshot.
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Parinibbana said:
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Click to expand...
Click to collapse
Today I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted.
Finally unbricked my phone.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
Parinibbana said:
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/show....php?t=2451696
Click to expand...
Click to collapse
Interesting. Thanks for the feedback.
Download minimalabd https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Run this in adb
copy and past
adb shell
and also
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
and also past on cmd
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
This fixed my phone
NP
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
Hi.
Bit of a fail of a day for me, as i seem to have bricked my D802 G2.
It started after flashing the latest dorimanx kernel over CloudyG2 3.3.. Afterwards i was stuck in fastboot mode.
After lots of messing around, i used the TOT method to recover and get back to stock..
Then i used srktools to root, and autorec to get TWRP installed. However after the reboot i was stuck with a black screen bootloop, stupidly i then sideloaded and flashed cloudy over the top..
I can still get into TWRP and Download mode, however TWRP cannot mount any of the partitions - so I attempted to re-flash stock using both TOT and KDZ method however nither work (TOT method just skips the partitions for some reason)
UPDATE: Managed to get it fixed - after trying many things including the 9006 QHUSB fix in SRKtools this adb patch finally allowed me to reflash a stock rom:
http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
lenesul said:
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Click to expand...
Click to collapse
Thanks - I think the phone has been in QHUSB mode a couple of times - there have been some occasions where many drive letters have appeared in windows when the phone reboots attached to USB.. I will see if i can get it to happen again then connect to a linux machine.
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
NeoVR said:
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
Click to expand...
Click to collapse
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
lenesul said:
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
Click to expand...
Click to collapse
Its fastboot that can send img files (im trying to avoid that as it would mean destroying download mode)
twrp is 2.7.0.0
Ive also tried LGUP, it detects the phone but cant detect the version - i cant find where to edit build.prop to force it to recognise.
Update: ITS FIXED!
In the end it was this that fixed it: http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
as i had adb access i thought id give it a go, and the TOT flashed correctly after.
Many thanks everyone!
Dead, Unbrick, Debrick F460. Dead/boot security error/boot loop kitkat,lollipop version bootloaders, 9006, 9008 modes
FIRST install lg united mobile drivers, connect mobile with battery to pc, check in device manager com ports if 9006 or 9008 mode.
if you can go into custom recovery mode twrp/cwm, then it easy to fix... u need to flash zip.but your self have to make it right now of same version. here the link tutorial.. http://forum.xda-developers.com/showthread.php?t=2451696 OR try adb or terminal command or u need to make zip file. i lost that link. better try ubuntu method also.
CASE1:
if 9006 or 9008 mode, ROOTED,on lollipop/kitkat/marshmallow before phone dead but rooted, first try debrick sdcard which is simpler, then use ubuntu method. this works only if rooted before phone dead. only root access allows to rewrite files on partition here is the link http://forum.xda-developers.com/showthread.php?t=2582142
CASE2:
only 9008 mode, phone dead on lollipop/kitkat/marshmallow, not rooted, then try debrick image and Ubuntu methods. sucess rate is very low.
Guys!
the sdcard debrick may success. then these files can debrick it.
OUr devices can be fixed. After lot of research i found it. kindly go through the link given below for tutorial and do debrick. You need to try from 140 to 220. hope YOU THANK ME HERE is the Link http://m.blog.naver.com/kangmincraft/220675995736
http://m.blog.naver.com/kangmincraft/220626785379
debrick 140 https://drive.google.com/file/d/0BwKzoXanfz0jMFh1OXJ2QnROUWM/view
debrick 160 https://drive.google.com/file/d/0BwKzoXanfz0jemxYR0VNcnZULXc/view
debrick 180 https://drive.google.com/file/d/0BwKzoXanfz0jb2R4eGIzV1BHeGM/view
debrick 200 https://drive.google.com/file/d/0BwKzoXanfz0jUHBTelc4VzlQT2M/view
debrick 220 https://drive.google.com/file/d/0BwKzoXanfz0jZFBXaFRLMFJVWGc/view
try this, this is my own debrick lollipop: https://drive.google.com/file/d/0B09V79Pt4dCUSjF0ZUhNRWxiQ0k/view?usp=drive_web
Read this post who unbricked his dead mobile http://forum.xda-developers.com/showpost.php?p=66264994&postcount=14
just poweron the device after inserting the sdcard. check few times. try to go download mode.
use google translator if needed.
TIPS
sdcard miniumum 4GB, use old sdcards first. then latest memory cards, try sdcard memory higher than phone memory is advantage. try these 3 types.
debrick140 worked for most of them. try this first if you are on lollipop.
Lollipop bricked roms have higher luck.
after successful unbrick, use poweriso/ultraiso to format sdcard. i used poweriso>tools>cleanusb. then format in your pc.
ATTENTION MARSHMALLOW: IF YOU NO ROOT, NO CUSTOM TWRP, NO DOWNLOAD MODE. THEN THERE IS NO DEBRICK IMAGE YET. NOTHING WORKS. GIVE TO REPAIR RIFF,OCTOPUS BOX. THIS GUY SELLING SOUTION https: //www. facebook.com/ giaiphapandroid/. (remove spaces)IF BOUGHT, SHARE THE LINK HERE . i am not seller,i don't vouch anyone here. just helping so that you help others.
if you have friends in vietnam/korea ask them to search MM debrick and share here. if anyone have solution for MM. kindly share here.
SENIOR XDA: I REQUEST YOU TO CREATE DEBRICK FOR MARSHMALLOW.
THANK ME IF USEFUL....
Credits to Vega_Kangmin.
all copyrights to respective owners. i made simpler type. so if read all and google search, everything you can get in detail.
Reply
Hi. My name is kangmin
And you can call me 'Vega'
At first.
That debrick.img is for G3 Cat.6 (F460 S/K/L.) In korea.
So, it didn't work for international phone
(Like G3 Prime.. Maybe.. Not sure.)
And second. This debrick.img file is for kitcat,lollipop.
It didn't work for mashmellow.
Vega_Kangmin said:
Hi. My name is kangmin
And you can call me 'Vega'
At first.
That debrick.img is for G3 Cat.6 (F460 S/K/L.) In korea.
So, it didn't work for international phone
(Like G3 Prime.. Maybe.. Not sure.)
And second. This debrick.img file is for kitcat,lollipop.
It didn't work for mashmellow.
Click to expand...
Click to collapse
Hello Vega,
yes, we need this for G3 Cat.6 (F460 S/K/L.).
Thank you for your hardwork.
how are you? i have been researched all your blog today and tired translating it to english, but still i cannot understand few words. KINDLY MAKE HERE ENGLISH TUTORIAL PLEASE.
my mobile is boot security error when downgrade from marshmallow to lollipop, 5%, laf error. so i need debrick image for F460S30c_00_1223 marshmallow version. could you please make a debrick image for it?
waiting for your private message reply
Okay. I'll going to write for english
But, i don't have much times because, i have an exam
So, i'll write it as soon as possible..!
Help me Vega
Hi Kathik, I have got a problem with my LG G3 Cat.6 F460k, no download mode, no recovery, no power on, no fastboot , only qualcomm hs-usb qdloader 9008 in windows device manager, tell me, You could please tell me what program I can use to fix this problem, I don’t have the files to use in the boarddiag application, because my g3 uses the APQ8084 chipset for the 805 snapdragon processor. Please brother, help me.
Vega_Kangmin said:
Okay. I'll going to write for english
But, i don't have much times because, i have an exam
So, i'll write it as soon as possible..!
Click to expand...
Click to collapse
Thank you brother!!
Thank you Kathik, I will try this method tomorrow in my Lg G3 F460K, then I will write the results, I have many faith in this!! By the way, thank you too for guide me via whatsapp Kathik, you are a truly hero bro!!!!
:good:
manowar24 said:
Hi Vega, I have got a problem with my LG G3 Cat.6 F460k, no download mode, no recovery, no power on, no fastboot , only qualcomm hs-usb qdloader 9008 in windows device manager, tell me, You could please tell me what program I can use to fix this problem, I don’t have the files to use in the boarddiag application, because my g3 uses the APQ8084 chipset for the 805 snapdragon processor. Please brother, help me.
Click to expand...
Click to collapse
manowar24 said:
Thank you brother, I will try this method tomorrow in my Lg G3 F460K, then I will write the results, I have many faith in this!! By the way, thank you too for guide me via whatsapp, you are a truly hero bro!!!!
:good:
Click to expand...
Click to collapse
Welcome bro. hope you fix and share it here
Vega_Kangmin said:
Okay. I'll going to write for english
But, i don't have much times because, i have an exam
So, i'll write it as soon as possible..!
Click to expand...
Click to collapse
Vega. do we need to press any buttons to go into fast boot mode after mounting sdcard? kindly search Marshmallow debrick and share the link please.
manowar
manowar24 said:
Hi Kathik, I have got a problem with my LG G3 Cat.6 F460k, no download mode, no recovery, no power on, no fastboot , only qualcomm hs-usb qdloader 9008 in windows device manager, tell me, You could please tell me what program I can use to fix this problem, I don’t have the files to use in the boarddiag application, because my g3 uses the APQ8084 chipset for the 805 snapdragon processor. Please brother, help me.
Click to expand...
Click to collapse
hi manowar.
you can solve the problem with using debrick.img files.
go to the link and solve the problem!
Hello Vega and Kathik, I have not done the process yet, I will do it tonight, and then I will inform the results.
I also wanted to thank you for the hard work you are doing in publishing this tutorial and translate it into English, I know you're still working on it, but so far it is understandable and looks promising.
I have some questions to you, to clarify the process that will perform tonight, please, answer me this:
I just have a 32 GB microSD Class 10, does this serve? Or it is too large in capacity? (By the way, my Lg G3 F460K is 32GB of storage and 3GB of RAM, it has Android Lollipop 5.0.1 with HOANG LAM CAT6 1.6 ROM and it was rooted)
When I will do the format to the microSD card, before passing by the win32Disk, what format I give it? ¿FAT32 or NTFS? Or the Win32 software do it for me when it will formated the microSD?
After inserting the microSD prepared, simply press the button on/off on the phone? Or I must do any combination of on/off + vol + or any other?
It is rare to found any solution for this korean model, there are only solutions for the international models, but it seems there is nothing for the Korean model (F460L,S,K). I hope that this work will help many people in this situation and prevent all those who are paying for solving this problem.
Please brothers, answer my questions and I will do the rest. Many thanks!!!
Vega_Kangmin said:
hi manowar.
you can solve the problem with using debrick.img files.
go to the link and solve the problem!
Click to expand...
Click to collapse
I´m in the process but....
Hello brothers, good news, my phone is now in Fastboot mode, I´m working with the ADB and CMD commads, but I have several troubles, please help me in this:
I dont have de file "misc.bin", when I disarmed the original KDZ file (kitkat or lollipop) doesnt appear this file. Do you have it? Please send me or letme download it
I cant erase o create the nexts files with the commads: BackupGPT.bin neither PrimaryGPT.bin, I recibe this message when I tried: "Failed: partition table doesn´t exits"
Brothers please help me on this!! I´m very close to fix my f460 all thanks to you!!
Hello brothers Vega and Kathik, good news, thanks to you I could get my phone back, it is now 100% operational, I would not have been achieved this without your support. However, some things did not go as shown in the tutorial, so I'll detail everything I did with my F460K to help everyone with this problem. Thanks to Kathik an d Vega for the debrick files, they are the key to solve this problem.
I am very happy, now I'll help whoever needs it , as Vega and Kathik helped me!!
THANK YOU TOO TO ALL MEMBERS OF XDA, WHO HELP ME IN SOMEWAY.
:good::good::good::good:
manowar24 said:
Hello brothers Vega and Kathik, good news, thanks to you I could get my phone back, it is now 100% operational, I would not have been achieved this without your support. However, some things did not go as shown in the tutorial, so I'll detail everything I did with my F460K to help everyone with this problem. Thanks to Kathik an d Vega for the debrick files, they are the key to solve this problem.
I am very happy, now I'll help whoever needs it , as Vega and Kathik helped me!!
THANK YOU TOO TO ALL MEMBERS OF XDA, WHO HELP ME IN SOMEWAY.
:good::good::good::good:
Click to expand...
Click to collapse
Welcome! happy to hear from you. share your experience here to help others.
do you wanna upgrade to MM? just follow this link http://forum.xda-developers.com/lg-g3/general/update-downgrade-root-lg-g3-f460-s-k-l-t3353542
How I bring back my G3 F460 from Death
Hello, I'll explain you all how I recovered my LG G3 F460K from death, I must first thank @Kathik and @Vega_Kangmin for their guidance, tutorials and files, without them I would not have been able to recover my phone, the steps are basically as they are explained in Vega_Kangmin´s tutorial:
http://m.blog.naver.com/kangmincraft/220675995736
However, I found some differences that stopped me so I had to read and research in Google to make decisions and to continue with the process.
These are the steps that I follow:
1. Download all programs and files suggested in Vega_Kangmin´s tutorial.
2. I extracted the files from the original KDZ Lollipop (F460K20C_00.kdz) and put it in the folder that I call “ADB”. (My G3 had the Lam Hoang 1.6 Android 5.0.1 Rom and was rooted with debugging enabled).
3. With the Win32Disk Imager I make the first boot image to use in the phone with a microSD card, first I try with the debrick image called “debrick140.img” and the screen did nothing, unanswered. Then with the win32Disk Imager I created the image boot with 160MB and bingo!! It works!!, the screen showed the LG logo and immediately fell in Fastboot mode. Here I tell you my first warning: the only microSD card that I have was a 32GB Class 10, so I used it, then the win32Disk Imager program created in it a new partition table and reduced the 32Gb capacity only to 85MB, so after I had saved my phone, I have to save my microSD card, for that, I used Ubuntu, and one program called “Gparted” I uses it to redefine the partition table. So, beware!!!
4. I opened a CMD´s window in the folder "ADB" (shift + right click, click on "open a command window here"), plugged my phone in the PC (Windows installed the drivers of ADB interface and immediately it recognized) and I wrote my first command to verify that everything was in order:
fastboot devices
If all goes well it should show up this:
List of Devices attached
LGF460XXXXXXX device
Then I proceeded with the ADB commands, but in the tutorial I found some errors in the syntax of the commands and the order they should be done, the correct syntax is:
To remove files the syntax is ok, example: fastboot erase aboot
This is the syntax to flash new files is: fastboot flash aboot aboot.bin
(Don´t forget to change names of the extracted kdz files)
And the order for all the process in the ADB pront is this:
fastboot erase aboot
fastboot flash aboot aboot.bin
fastboot erase boot
fastboot flash boot boot.bin
fastboot erase laf
fastboot flash laf laf.bin
fastboot erase rpm
fastboot flash rpm rpm.bin
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot erase modem
fastboot flash modem modem.bin
fastboot erase SBL1
fastboot flash SBL1 sbl1.bin
fastboot erase tz
fastboot flash tz tz.bin
fastboot erase sbi
fastboot flash sbi sbi.bin
fastboot reboot
exit
Note: none of these files should be used BackupGPT.bin, PrimaryGPT.bin (if you use it the ADB will return an error saying that these tables do not exist, the file misc.bin neither will use because we do not have it and it isn´t important to revive the G3, this information I got it from here:
"YOU NEED TO EXTRACT 10 FILES FROM TOT (if you use a tot file) (aboot, boot, SBL1, dbi, laf, recovery, modem, misc, rpm, tz) and 9 FILES FROM KDZ (this is our case for the Lg G3) (misc file is not present in KDZ so dont worry it is not important) "
That out of here, please read it:
http://forum.xda-developers.com/android/general/unbrick-lg-model-download-recovery-t3060184 -----> Thanks to @hacklockx
5. After restarting the phone it show up the LG logo (this is a good news), so flash an official ROM with the LG Flash Tool as you already know and enjoy our super phone again.
By the way, in my case, after the process restart with the ADB commands, my phone start normally with all my stuff installed, I lost nothing, as if nothing had ever happened, however, I noticed slow and the camera didn´t work so I flash it with the official rom F460K20C_00.kdz and it was like new. Then I rooted it, installed the TPWR and flash again the Lam Hoang 1.6 ROM with Android 5.0.1, then installed the Xposed and that´s all!!
I hope you serve!!
Greetings from Venezuela :good::good::good:
Guys, I need help. My F460L is bootlooping but I can still access download mode. I tried flashing stock MM with LG Flash Tool but it is still bootlooping, what do I need to do?
Jinyung411 said:
Guys, I need help. My F460L is bootlooping but I can still access download mode. I tried flashing stock MM with LG Flash Tool but it is still bootlooping, what do I need to do?
Click to expand...
Click to collapse
Try these options:
1. Change your battery, try another one, in my case I have two battery, one cause endless bootloop on my G3.
2. Use the "LG Mobile Support Tool", install the program, open it, connect your G3 and see the magic happens :good:
Good luck bro
manowar24 said:
Try these options:
1. Change your battery, try another one, in my case I have two battery, one cause endless bootloop on my G3.
2. Use the "LG Mobile Support Tool", install the program, open it, connect your G3 and see the magic happens :good:
Good luck bro
Click to expand...
Click to collapse
I tried using LG Mobile Support Tool but it does not work either. I'll try the battery, thanks. Will report back.
Jinyung411 said:
I tried using LG Mobile Support Tool but it does not work either. I'll try the battery, thanks. Will report back.
Click to expand...
Click to collapse
check this link. downgrade to Lollipop. follow this link http://forum.xda-developers.com/lg-g3/general/update-downgrade-root-lg-g3-f460-s-k-l-t3353542
THANK ME IF I HELPED YOU. also MUST write feedback
Kathik said:
Dead, Unbrick, Debrick F460. Dead/boot security error/boot loop kitkat,lollipop version bootloaders, 9006, 9008 modes
FIRST install lg united mobile drivers, connect mobile with battery to pc, check in device manager com ports if 9006 or 9008 mode.
if you can go into custom recovery mode twrp/cwm, then it easy to fix... u need to flash zip.but your self have to make it right now of same version. here the link tutorial.. http://forum.xda-developers.com/showthread.php?t=2451696 OR try adb or terminal command or u need to make zip file. i lost that link. better try ubuntu method also.
CASE1:
if 9006 or 9008 mode, ROOTED,on lollipop/kitkat/marshmallow before phone dead but rooted, first try debrick sdcard which is simpler, then use ubuntu method. this works only if rooted before phone dead. only root access allows to rewrite files on partition here is the link http://forum.xda-developers.com/showthread.php?t=2582142
CASE2:
only 9008 mode, phone dead on lollipop/kitkat/marshmallow, not rooted, then try debrick image and Ubuntu methods. sucess rate is very low.
Guys!
the sdcard debrick may success. then these files can debrick it.
OUr devices can be fixed. After lot of research i found it. kindly go through the link given below for tutorial and do debrick. You need to try from 140 to 220. hope YOU THANK ME HERE is the Link http://m.blog.naver.com/kangmincraft/220675995736
http://m.blog.naver.com/kangmincraft/220626785379
debrick 140 https://drive.google.com/file/d/0BwKzoXanfz0jMFh1OXJ2QnROUWM/view
debrick 160 https://drive.google.com/file/d/0BwKzoXanfz0jemxYR0VNcnZULXc/view
debrick 180 https://drive.google.com/file/d/0BwKzoXanfz0jb2R4eGIzV1BHeGM/view
debrick 200 https://drive.google.com/file/d/0BwKzoXanfz0jUHBTelc4VzlQT2M/view
debrick 220 https://drive.google.com/file/d/0BwKzoXanfz0jZFBXaFRLMFJVWGc/view
try this, this is my own debrick lollipop: https://drive.google.com/file/d/0B09V79Pt4dCUSjF0ZUhNRWxiQ0k/view?usp=drive_web
Read this post who unbricked his dead mobile http://forum.xda-developers.com/showpost.php?p=66264994&postcount=14
just poweron the device after inserting the sdcard. check few times. try to go download mode.
use google translator if needed.
TIPS
sdcard miniumum 4GB, use old sdcards first. then latest memory cards, try sdcard memory higher than phone memory is advantage. try these 3 types.
debrick140 worked for most of them. try this first if you are on lollipop.
Lollipop bricked roms have higher luck.
after successful unbrick, use poweriso/ultraiso to format sdcard. i used poweriso>tools>cleanusb. then format in your pc.
ATTENTION MARSHMALLOW: IF YOU NO ROOT, NO CUSTOM TWRP, NO DOWNLOAD MODE. THEN THERE IS NO DEBRICK IMAGE YET. NOTHING WORKS. GIVE TO REPAIR RIFF,OCTOPUS BOX. THIS GUY SELLING SOUTION https: //www. facebook.com/ giaiphapandroid/. (remove spaces)IF BOUGHT, SHARE THE LINK HERE . i am not seller,i don't vouch anyone here. just helping so that you help others.
if you have friends in vietnam/korea ask them to search MM debrick and share here. if anyone have solution for MM. kindly share here.
SENIOR XDA: I REQUEST YOU TO CREATE DEBRICK FOR MARSHMALLOW.
THANK ME IF USEFUL....
Credits to Vega_Kangmin.
all copyrights to respective owners. i made simpler type. so if read all and google search, everything you can get in detail.
Click to expand...
Click to collapse
Hey, will this work on the D851?
If not, how do i create a debrick image for the D851?
Regards Mickey.
mickeyasamoah said:
Hey, will this work on the D851?
If not, how do i create a debrick image for the D851?
Regards Mickey.
Click to expand...
Click to collapse
only these can help you by software by money or assistance. just help. not vouch or i don;t get anything from this. your wish. remove spaces
androidbrick . com
https :// www. facebook .com/ giaiphapandroid
http :// www. vungoc -mobile. com/
if don;t wanna risk. better give to repair jtag/octoplus box which 100% fix this.