Root [International] D802 Stuck In Fastboot Mode

[emasemas13]

Hello,
I have same problem as Steelzz had. I just played with AutoRec. Now I'am stuck with fastboot mode. My phone is LG D802 32GB. I have tried to flash aboot.img and laf.img. Here is link for command lines:
imgur*com/bNI4co7*png (please replace * with dots, I can't share links)
Everything looks good, but nah, everything is same.
Thanks.

 

[iowabowtech]

Hello,
I have same problem as Steelzz had. I just played with AutoRec. Now I'am stuck with fastboot mode. My phone is LG D802 32GB. I have tried to flash aboot.img and laf.img. Here is link for command lines:
imgur*com/bNI4co7*png (please replace * with dots, I can't share links)
Everything looks good, but nah, everything is same.
Thanks.

Can you link me to exactly where you got your aboot and laf image files please? You should be able to post links now by the way.

Also, do you know what firmware version you were on prior to this?

 

[emasemas13]

Can you link me to exactly where you got your aboot and laf image files please? You should be able to post links now by the way.

Also, do you know what firmware version you were on prior to this?

Well, Listing of 10b_EUR_16G_partitions
I think problem will be that i tried to flash 16GB partitions.
I had latest stock rooted kit kat 4.4.2 i think.

 

[iowabowtech]

Well, Listing of 10b_EUR_16G_partitions
I think problem will be that i tried to flash 16GB partitions.
I had latest stock rooted kit kat 4.4.2 i think.

I'm not positive but I don't think those two partitions would matter in regard to 16 GB or 32 GB.

By any chance, do you have access to your MEID? If you bought the phone new, it'd likely be on the box it came in. With that, we may be able to obtain your kdz and extract the partitions from the firmware version you are/were on. If you have it, don't post it publicly, just let me know yay or nay.

 

[emasemas13]

I'm not positive but I don't think those two partitions would matter in regard to 16 GB or 32 GB.

By any chance, do you have access to your MEID? If you bought the phone new, it'd likely be on the box it came in. With that, we may be able to obtain your kdz and extract the partitions from the firmware version you are/were on. If you have it, don't post it publicly, just let me know yay or nay.

Actually, I don't know where to look it. If that's number near BAR code on the box, then yes.

 

[iowabowtech]

Actually, I don't know where to look it. If that's number near BAR code on the box, then yes.

Eh, sorry meant to say IMEI number, typing this from work.

It'll likely be referenced as such and will be a 15 digit number and may contain spaces or dashes in some places.

 

[emasemas13]

Yes, I have IMEI.

 

[iowabowtech]

Yes, I have IMEI.

Ok good. Paste the following string into a browser:

http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxxxxxxxxxx

At the end of the string, replace the 15 x's with your IMEI, then hit enter on keyboard. You should get a page with some specs on your device. About halfway down the list, hopefully there will be a web link to your device's current kdz. If so, please PM me that. Unfortunately, not all variants/carriers allow the link to show.

(there's no private info there, it's just the kdz for anyone running your variant and firmware version)

 

[iowabowtech]

Ok so the laf is a different size, not sure if it's simply because it's a different firmware version altogether or if they are in fact sized differently depending on 16/32 phone storage.

Anyway, download this and extract:

https://copy.com/vgdvkxPJemJypozc

Please note I provided some extra files just in case you end up needing them. I would recommend trying first to only deal with aboot and laf like before EXCEPT, it would be safer to flash aboot and then BOOT laf:

fastboot flash aboot aboot.img

fastboot boot laf.img

Then see if you get download mode directly after entering the boot laf command. Make sure to get that other aboot & laf out of view so you don't get confused and use one of those accidentally.

If that doesn't give you download mode, don't disconnect the phone. Leave it as is and report back.

 

[emasemas13]

Okay, now it's just weird.

But, one (E) is accessible. I think it worked.

 

[iowabowtech]

Okay, now it's just weird.

But, one (E) is accessible. I think it worked.

What is the phone's screen saying right now? Look in Windows device manager and see if there's anything there called LGE AndroidNet (or similar wording).

 

[emasemas13]

Phone - Nothing, black screen, no text.
PC:

 

[iowabowtech]

Nothing, black screen, no text.

That does happen sometimes. How about device manager? Anything listed there?

 

[emasemas13]

That does happen sometimes. How about device manager? Anything listed there?

repost:

Phone - Nothing, black screen, no text.
PC:

 

[iowabowtech]

Ok I see your edit about qhsusb_bulk.

Try unplugging the phone, press and hold power for 15 seconds. The try going back into download mode. Does fastboot mode come back or nothing at all?

 

[emasemas13]

Ok I see your edit about qhsusb_bulk.

Try unplugging the phone, press and hold power for 15 seconds. The try going back into download mode. Does fastboot mode come back or nothing at all?

Fastboot mode..

 

[iowabowtech]

Fastboot mode..

Sent you a pm.

 

[emasemas13]

Okay, my LG G2 (D802) is now fully funcionable, works like a charm
I've broke it by installing wrong Autorec. My phone was stuck at fastboot mode.
My solution:
Using sdk-tools fastboot, I flashed original aboot.img and boot.img files and then booted laf.img

And voila, I can access download mode again!

SDK-tools
LG G2 files

Sorry, I'm not that good at these things to explain good what I did there.
Thanks, iowabowtech, for help!

 

[gadget_boy]

Okay, my LG G2 (D802) is now fully funcionable, works like a charm
I've broke it by installing wrong Autorec. My phone was stuck at fastboot mode.
My solution:
Using sdk-tools fastboot, I flashed original aboot.img and boot.img files and then booted laf.img

And voila, I can access download mode again!

SDK-tools
LG G2 files

Sorry, I'm not that good at these things to explain good what I did there.
Thanks, iowabowtech, for help!

I have the same issue as you. Just to be sure to fix it you flashed:

aboot.img
boot.img
laf.img

What did you mean by booted lef.img?

Thanks

 

[emasemas13]

I have the same issue as you. Just to be sure to fix it you flashed:

aboot.img
boot.img
laf.img

What did you mean by booted lef.img?

Thanks

Hi, by booted laf.img i meant:

fastboot boot laf.img

And in my case, I didn't flash laf.img.

 

[costasp81]

Hello everyone,

I'm pretty much in the same situtation:

1. Phone wont power on
2. No recovery/download/fastboot
3. lsusb in ubuntu won't list it
4. fastboot devices/adb devices won't list it
5. Windows 8.1 device manager sees it as an unkown usb device. I installed all the drivers you suggested but still nothing.

I was trying to flash back the original KDZ when it stuck and I unplugged my phone. I then tried dd pushing the files back in the corresponding partitions, but at somepoint it turned off and since then it's dead.

Is there a chance I could do something? I prefer in linux to avoid all the driver issues I guess.

The phone is intl D802.

Thank you in advance for your help!

 

[iowabowtech]

Hello everyone,

I'm pretty much in the same situtation:

1. Phone wont power on
2. No recovery/download/fastboot
3. lsusb in ubuntu won't list it
4. fastboot devices/adb devices won't list it
5. Windows 8.1 device manager sees it as an unkown usb device. I installed all the drivers you suggested but still nothing.

I was trying to flash back the original KDZ when it stuck and I unplugged my phone. I then tried dd pushing the files back in the corresponding partitions, but at somepoint it turned off and since then it's dead.

Is there a chance I could do something? I prefer in linux to avoid all the driver issues I guess.

The phone is intl D802.

Thank you in advance for your help!

Without recovery, download mode or fastboot, the next hope is bulk mode (device listed as qhsusb_bulk in windows device manager). You evidently don't have that if linux is not recognizing the device.

The final stage of failure is QDLOader 9008 mode. If you can verify you're in that situation (again, Windows device manger will verify that), then check this solution out:

[FIX] Unbrick LG G2 stuck in Qualcomm HS-US… | LG G2 | XDA Forums

 

[costasp81]

Hi iowabowtech!

Thank you for your reply. Unfortunately Windows sees the device as an unknown USB Device:

http://i.imgur.com/MdGoWS0.png

I've uninstalled all drivers and only installed koush adb drivers (thought it might bee better).

[edit]
Linux just listed it as "Bus 001 Device 018: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)"

Any suggestions?

Once again thank you for your time and help!

 

[iowabowtech]

Hi iowabowtech!

Thank you for your reply. Unfortunately Windows sees the device as an unknown USB Device:

http://i.imgur.com/MdGoWS0.png

I've uninstalled all drivers and only installed koush adb drivers (thought it might bee better).

[edit]
Linux just listed it as "Bus 001 Device 018: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)"

Any suggestions?

Once again thank you for your time and help!

Recheck how it shows up now in Windows. A little too coincidental that Linux is showing 9008.

 

[costasp81]

Nope, no luck unfortunately.
I've given up, and took it to service. I hope they'll get it fixed.

Thank you for your time! You rock!:thumbup::thumbup: