Database Users

I softbricked my LS980 and cannot escape fastboot. Assistance Requested.

Had a problem with audio playback (volume always high no matter what). Decide to flash. PAC for my Sprint LS980. I see this:
Seems to be a lot of confusion so I'll clear things up..
ZV7->ZV8->ZVA is how the ota history goes, with ZVB on the way.
If you're on stock ZVA, your aboot (bootloader) may not be downgraded, in that case, use FreeGee from Play Store to install a recovery, it will automatically downgrade your aboot.
if you have the ZVA Radio, just flash furnace or dr87's kernel after you flash an AOSP ROM, all done.
Click to expand...
Click to collapse
Sorce: http://forum.xda-developers.com/showthread.php?t=2669074
Seeing the last sentance, I think that if I flash ZVA Radio, SlimKat ROM (the one that causes me problems) and then dr87's kernel I could try a ZVA experience. I flashed SlimKat again becuase I was going to change anyway, I wanted to try it with ZVA.
Tell myself why not, I do it.
Fails but I didnt pay much attention. I reboot.
Stuck in fastboot mode and cant escape. Recovery is a no-go.
Tried flashing both ZV7aboot.img and twrp2.6.3.0.img into their appropriate partitions (boot and recovery).
Still having problems, but now I cant do any button combination (except DownloadMode. Cant turn off) after ZV7aboot.img flash.
I dont want to erase my memory (~26GB of valuable data). Is there a way to flash a ZV8Radio.zip from fastboot? I think thats my problem, but Im not too sure. Just access to recovery would allow my to fix my problems.
Thanks anyone for any help! I think I really screwed myself over this time. Thanks everyone!
Edit: Anyone know where to get a boot.img and system.img for the Sprint LS980?

zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.

Savoca said:
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Click to expand...
Click to collapse
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.

RevolcFael4 said:
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
Click to expand...
Click to collapse
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.

Savoca said:
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Click to expand...
Click to collapse
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.

RevolcFael4 said:
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
Click to expand...
Click to collapse
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2

Savoca said:
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Click to expand...
Click to collapse
Thanks for the link! That was extremely helpful.
What I did to gain access to twrp again was:
Download boot.img from the link.
Download aboot.img from link.
Download twrp.img (but this isnt necessary, file is already available on phone. No need.)
* Enter command 'fastboot flash boot boot.img'
* (If you hold power it starts showing LG Logo.)
* Go back to Fastboot. Enter command 'fastboot flash aboot aboot.img'
* Now TWRP access is regained! Phone doesnt boot normally, must flash ROM and stuff again.
Thanks a lot! This was an okay first fastboot experience.

Soft Bricked Sprint LS980?
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
Click to expand...
Click to collapse
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!

x_lord said:
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
Sorry for not replying, but I see you managed to fix your problem. All you needed to do was download .img files, then enter commands through fastboot. Although it is slightly more complicated than that, its the rough outline of what needs to be done to fix it. Nice work fixing your problem. I came back to this thread to remind myself of the commands that need to be entered (My comments help myself).
I think I am just going to copy-paste the quoted box above if anyone needs instructions how to do this. Thanks for the quick guide I can use to help others!

bricked , simple fix?
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible

True2This said:
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
Click to expand...
Click to collapse
Sorry, I barely understood what to do originally. What you have to do next is to reflash the aboot/boot/ whatever partitions but getting to that position might be difficult. Maybe some sort of command would allow you to connect to it oncemore?
Sorry, try to look into it more and see if a dev could help. Try posting something in /r/lgg2 but then again I cant be certain anything would happen. Good luck!

Easy guide
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!

Unbrick Ls980 formatting partitions
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing

RevolcFael4 said:
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Click to expand...
Click to collapse
i tried this with almost all model files but still on fastboot any other option?>

I want to say thank you so much for this thread. Just got a new (refurb) G2 switching carriers to T-Mo and my idiot self used the wrong root program and soft bricked to fastboot. 4 .img files later and a few commands and I don't think I've ever been so happy to see a download screen on a phone...

juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
GREAT, You are a life saver :laugh:

juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
wow.. worked flawlessly... thank you very much :good::good::laugh::laugh:

[Q] hours for searching for nothing help plz!

I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!

There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.

let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!

alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.

alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.

If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.

It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.

downloadmode should still work. go back to any kdz for your version
also source and versions post next time

[Q] Fastboot mode, no download mode, bricked autorec Videotron LG G2 D801 D801V20E

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

Help with a unique D802T brick? (bad partition?)

So I've got my (recently purchased T_T) Australian G2 (D802T) in a bit of a pickle. Here's the story of my rapid descent into idiocy: Rooted with ioroot (went fine), installed TWRP via autorec (whoops!). From here I installed several roms but none would boot past optimizing apps - after some further reading this is apparently a known issue with the D802T.
From here I followed the instructions at http://forum.xda-developers.com/showthread.php?t=2432476 and successfully reset back to stock firmware using a D802T kdz I found online. On first boot the phone asked for a decryption pin, which I fixed by booting to the stock recovery and letting it do its thing. However, it seems that the image was for the 16GB version - I was left with only 10GB accessible space.
This is where I got double stupid - I followed about half of http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ to fix the issue, but rather than copying over the blank images and re-imaging the firmware again, I tried to get clever by growing the userdata partition manually. Unfortunately it seems that I screwed up, since on next boot I once again had the decryption lock, and now neither the factory reset nor re-flashing the firmware will fix it. The last thing I tried tonight was installing the LG Mobile Support Tool and letting it automatically download and install the firmware, but it seems to be in the exact same condition. Apparently the kdz re-imaging (even CSE Flash) doesn't actually reformat anything... :/
Any ideas? I have access to:
download mode
stock recovery/factory reset screen
bootable stock ROM that locks me out due to thinking it's encrypted, when in fact it's just an incorrect partition table.
Is there any way to get adb access back? Or perhaps to get the phone in to some kind of usb mass storage mode as described in http://forum.xda-developers.com/showthread.php?t=2582142 ? As it is it's only recognized by linux as a serial device - if I could get rw access to the raw storage I think I could fix it up pretty easily.

Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?

amdpox said:
Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?
Click to expand...
Click to collapse
maybe you should first try downloading your kdz from here and trying that.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.

Art Vanderlay said:
maybe you should first try downloading your kdz from here and trying that.
Click to expand...
Click to collapse
Doubt it'll be much different but I'll give it a shot, thanks.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.
Click to expand...
Click to collapse
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.

amdpox said:
Doubt it'll be much different but I'll give it a shot, thanks.
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.
Click to expand...
Click to collapse
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.

Art Vanderlay said:
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.
Click to expand...
Click to collapse
Fair enough. It feels like I'm at the point of last resort, though.
I tried that 20D kdz, seems to be in the same state. (I'm guessing that's exactly the image that the automated support tool downloaded and flashed.)

Is this fixed ?

bender_007 said:
Is this fixed ?
Click to expand...
Click to collapse
Sadly not. Totally stuck for ideas here... anyone know anything more sensible to try than the cable-pulling?

[HELP] Brick after flashing bootloader

So I was on AT&T d80020y stock ROM with TWRP installed via Autorec. I tried flashing Blisspop 3.5. For this, first I flashed bootstack-d800-LP_30d-loki-signed.zip downloaded from here and then reboot. That seems like a mistake because I entered on bootloop: LG logo for a sec and then screen is off.
Since I couldn't get either into recovery or download mode (I got the "secure booting error" message), I followed this guide and pushed the sbl1.img aboot.img, rpm.img, tz.img and TWRP 2.6.3.2 fom d800 10p (wich I downloaded from here). After this, I could get into recovery and restored a full nandroid of the d80020y I've made before everything. But still the phone won't boot and I can't go into download mode (same secure booting error).
Considering I'm practically a noob, I've run out of resources. What's the problem here? I could guess that the nandroid restore didn't fix the bootloader mess, but I'm not sure how to procceed. Should I install a d80020y bootloader? If so, the "wrong" LP bootstack also had a modem.img inside, should I flash the right one too? I'm going crazy on this...
Thanks people.
----- UPDATE -----
I was able to flash JB Bootloader (downloaded from here) via adb sideload. From here, I can enter download mode and should be able to flash stock ROM via KDZ/TOT. But this also made me thinking that maybe if I restore KK Bootloader, I could restore nandroid again and then the system will boot. Problem is that, when trying to adb sideload KK Bootloader, it seems something's different on Windows 8 drivers and adb devices doesn't show my phone. Actually, when I plug the phone beeing into TWRP recovery/download mode, device manager doesn't shows LG G2 device (screenshot attached, arrows on the 3 devices LG related).
I tried switching USB port (both 2.0 and 3.0), different LG Mobile Drivers versions and Universal ADB Drivers from here, (wich helped on the first adb sideload), but adb still doesn't recognize my phone. Any idea? I guess this is also a problem for flashing via KDZ, is it?

Just to understand, right now youre device fully working? without download mod? can you get recovery?

maozer said:
Just to understand, right now youre device fully working? without download mod? can you get recovery?
Click to expand...
Click to collapse
Device is not working. Still stuck on LG logo then black screen when booting, still get the "secure booting error" when download mode. I do get TWRP recovery (I guess that's because I pushed the image to the recovery partition).

http://blastagator.ddns.net/bootloader.php
try adb side load
download and flash jb bootstack and then u will be able to go to download mode then tot/kdz method with lg flash tool.

maozer said:
http://blastagator.ddns.net/bootloader.php
try adb side load
download and flash jb bootstack and then u will be able to go to download mode then tot/kdz method with lg flash tool.
Click to expand...
Click to collapse
Originally I was on KK, shouldn't I download KK 20y bootstack?
Also, it seems I can't get the device detected when running adb devices. Should I be in TWRP's adb sideload option? I've got ADB working now.
I don't want to mess things again, so I want to be sure. I should flash JB bootloader and then flash JB Stock ROM from KDZ? Won't it work with KK Stock ROM? (My phone came with KK already)

axel.lacapmesure said:
Originally I was on KK, shouldn't I download KK 20y bootstack?
Also, it seems I can't get the device detected when running adb devices. Should I be in TWRP's adb sideload option?
Click to expand...
Click to collapse
well, i had ur problem like 4 hours ago.. same certification error and that's what i did.. cant garuntee anything. it worked for my d800..
use this video like this guy with the bootstack
https://www.youtube.com/watch?v=Oo2cErfUSSE
good luck
---------- Post added at 03:46 PM ---------- Previous post was at 03:35 PM ----------
axel.lacapmesure said:
Originally I was on KK, shouldn't I download KK 20y bootstack?
Also, it seems I can't get the device detected when running adb devices. Should I be in TWRP's adb sideload option? I've got ADB working now.
I don't want to mess things again, so I want to be sure. I should flash JB bootloader and then flash JB Stock ROM from KDZ? Won't it work with KK Stock ROM? (My phone came with KK already)
Click to expand...
Click to collapse
well i couldnt manage to find kk kdz d800 rom so i just used tot file from here: http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/AT&T/

I would like to try sideload KK Bootstack, but can't get ADB working. I did sideload JB bootloader, but then I think Windows messed up with the drivers and now ADB doesn't recognize my phone. I resintalled LG drivers, also tried Universal ADB Drivers from here but command adb devices doesn't show up any devices.
Attach a screenshot of device manager when my phone is connected to the PC (spanish OS, but I think it's understandable). I mark the only devices that are LG related.
Any suggestions?