Database Users

Stuck in APX Mode and Need Help!

Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.

The Same Here

The same here too...
Sent from my Galaxy Nexus using xda app-developers app

It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.

ponypowerracin said:
It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.
Click to expand...
Click to collapse
heck, you can almost get your money back by "parting" it out. Dincdoesme is looking for a front display assembly
Ok, as I sent you the link in PM, for the rest of you folks, here's some things to try.
Note This. I am NOT a brickmaster. I'm just lucky getting things running again for a lot of people. So if these methods don't work, well, don't shoot the cook! I've never been stuck in APX mode, but I've cooked some bootloader's before.
There are a few things that causes this.
1. Your PC is playing tricks. You should disable anti-virus and such. And sometimes, using a different PC can make a difference.
2. Your USB cable. They are not all created equal, as a pin layout may be different. I use my HTC Desire's USB cable and never had an issue. My camera's cables act like they will work, but always produce errors.
3. You have corrupted or damaged memory blocks where the bootloader resides. In this case, the MB will more than likely need replaced.
So with that said, I will give you a link. Now, this zip has one of the very early NVFlash bootloader apps. I couldn't find my original pure NVFlash setup, but I've used this one often in the past. It may be more tolerant.
http://d-h.st/32X
Unzip the contents to a folder.
Have your SBK number ready. You should already have this from your UID number.
Power off your tab. Then manually put it in APX mode, by pressing and holding the pinhole rest, then press and hold PWR. After 4 seconds, release PWR, then 1 second later release pinhole. Your display should be black with a white PWR button. If not try it again or reverse the switches (been a long time)
Start the NVFlash application. DO NOT DOWNLOAD ANY BUNDLES. Plug your tab in when prompted. Always select Auto.
Ignore any windows messages. If it looks like it stops stating no APX devices, just continue.
There are 2 bootloaders and a CWM package. 1 bootloader is for the 500, the other for the 501. They are identicle except for the logo. Just choose one.
Now, note that this is a version 3 unlocked bootloader. It's ok.
At the end, you may or may not get some red ebt message. Ignore it. Just reboot it into CWM.
Hoping this works for you guys.
In the meantime, I'll still look for my original NVFlash which will rule out windows apps and conflicts.
MD

ponypowerracin said:
Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.
Click to expand...
Click to collapse
jancarlos1597 said:
The Same Here
Click to expand...
Click to collapse
sebone02 said:
The same here too...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
For you guys stuck in apx - please provide a screenshot of your error messages!!
there are way too many things it COULD be and is difficult to help without physically having the tab in hand!!!! Pictures!!! post some pictures
Running nvFlash,
Go in and edit the .bat file and delete all lines beginning with 'cls' close and save, then run it...and post the error here - not saying you can be fixed but at least all error codes will be in one place.
Depending which error you have will determine whether yr tab needs to be sent to acer for repair...or something far more simple like uninstalling and reinstalling BOTH sets of drivers....
IF apxFlashv4 or timmydeansv4 or MD's suggestion above does not fix you, then yr motherboard is toasted and will need replacement
sebone02 said:
The same here too...
Click to expand...
Click to collapse
@sebone02 -
yr a bit different as u rec'd yr tab stuck in apx, so we dont know what rom was on there b4 this happened....But the bootloader tools definitely wont work from HC3.2 -
first thing to do is make sure you have both sets of drivers installed
the acer ones and the android sdk ones. Then connect to your pc
is the apx device showing and/0r the acer boot/recovery drivers
Try to perform a hard reset to format the cache and userdata
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is to a rotation lock) and power on simultaneosly
4) As soon as the tablet vibrates you can release the power on button and you should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Then run timmydeansv4.

Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nvbat error
EUU error, same thing happens with factory EUUs and root-3.2.1, this error comes up as soon as the tablet switches to apx download mode
Bad Sector error
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot

Yeah, my bag of tricks is empty at the moment. I see in the posts above you, where jazzyjames and a couple others are in the same boat. Everything points to an unrecoverable error in the boot loader partition.
Maybe those guys will stumble onto something, or skirlaz_cz will have some input.
On the 700/701/510 we had the issue right at the start when the first cwm's were couurupting the data partitions when wipes or restores were done. Samsung s3 had the same bug that bricked the partitions. The lead dev in the 700 forum got his own stuck in apx mode for some unknown reason. End result are main board changes for all of them including mine.
On the 70x, they found several hidden partitions, so am hoping that mess is sorted out now.
MD

thanks for posting the pix - i see each tool reports different errors - not sure why this would be, all i can tell you is i have had a couple of nvflash errors along with the EUU update failed screen and the display showing "reboot the device", (all at the same time) which never went away no matter how many times i rebooted....somehow though thru multiple tries over many days i got a working tab again...
I'm sure that in the end the apxflash tool finally recognised my tab in apx mode,
once that happened i manually flashed a bootloader.bin and recovery.img -
you can try this if you have tdv4, use the .img files in there to manually flash via apxflash tool
also, if u have access to linux - running nvflash command from it has helped others...
finally lcd047 ran nvflash directly from tdv4 (his was a partition error):
lcd407; said:
* I downloaded timmyDean's root-3.2.1-V4.7z
* I booted the tablet (in APX mode) and I connected the USB cable to it
* in the directory root-3.2.1/Image I run the command
Code:nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
* without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
* I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
As I already noted, I lost all the data from the internal sdcard. I'm not sure if that was the result of the re-creation of partitions, or I inadvertently did that while messing with nvflash, the bottom line is all files are gone. In turn, restoring the CWM backup didn't do much good, because most apps will fail in interesting ways without the sdcard data, so I'll probably just start from scratch and reinstall the apps from a Titanium backup. But I have a working tablet again.
Click to expand...
Click to collapse
another good thread to take a look at, although i got lost after page1!!!!
No access to ROM or Recovery its the only fix i have seen that addresses the problem and provides a solution - its a shame i cannot understand it, lol
from what i've seen on the boards the ebt issue is damn near unrecoverable,
partition errors seem a little easier??
bct errors can sometimes be recovered from using the dump my bct option in apxflash 0.4 IF you can get the tool to recognise yr tab...
If tdv4 fails then its a bit of a lottery in finding something else that works
ensuring that an apx device is recognised by yr pc is fundamental in getting any of the automated tools to work....
I do wish you all the best in finding a solution, and please keep us all posted on how u ALL get on with this....
rgds dibb

ponypowerracin said:
Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot
Click to expand...
Click to collapse
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?

mandar_h said:
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?
Click to expand...
Click to collapse
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.

ponypowerracin said:
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.
Click to expand...
Click to collapse
I'm way out of warranty. So I doubt if they will entertain my case at all.
Thanks for the reply.

Try Acer m8 they have been known to repair these faulty out if warranty tabs. That's if you're certain its the chip....See this http://forum.xda-developers.com/showthread.php?t=2738138
Sent from my HTC_PN071 using Tapatalk

[Q]Stuck on Google splash

OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.

a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck

joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.

a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?

I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.

joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck

a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.

joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...

a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.

joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(

Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)

ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.

Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...

ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.

[FIX][Noob Friendly] No recovery, No download mode, No booting android, qhsusb_bulk?

No recovery, No download mode, No booting android, No fastboot? - In this case you are right here!
You are in the following situation:
If you power on your device, it goes to the LG logo and becomes black with running backlight quickly.
You have no access to the recovery mode.
You can't enter download mode.
There is no way to boot into the android system.
Usually your device is shown as qhsusb_bulk in Windows device manager.
Sometimes Windows recognizes about 13 partitions.
What you will need:
A working linux distribution (no way around that, but don't be afraid, e.g. slax)
If you want to run Linux in a Virtual Machine (no installation), preferably the VMWare Player (only for 64bit OSes) or an older Version of VMWare Player that supports 32bit.
A windows machine
A kdz for your device: 1, 2 or 3
The kdz extractor for WINDOWS!
Your broken G2
A micro USB cable
A little introduction:
We saw it a few times in the past months that people did weird things with their phone and didn't have anything more than a bootloader. This means no access to recovery nor download mode nor a booting android system. The last case was @petrasl27 (Thanks for the screenshots btw. ;D ). @bender_007 and @Art Vanderlay did an awesome job and helped petrasl27 to recover his phone within one hour. So thanks to those two! For those who want to read the original discussion, read a few pages here!
This thread here is similar to this one here, but I would say quite a bit easier to understand.
Disclaimer: I am not responsible for your phone. I did everything with my best knowledge, but I can't guarantee that your phone is working afterwards and every single command is written correctly. But I hope so, and it should ofc. If you have any issues, feel free to ask for help. We are kind, no worries. If you find mistakes, hit me up and I will correct them ASAP.
Let's start!
1) Install Linux
The easiest way is just do download the VMWare Player, installing, running it and using the .iso you downloaded before (pick other 3.x Linux Kernel if you downloaded slax). If you are unsure how to get Linux running, google it or ask here. Make sure, the usb port which you are going to use is linked through to the virtual machine.
You can also make the iso bootable and run the Linux as live system.
2) Extract the kdz
Switch to Windows, open the kdz extractor. Tick everything in the upper window, and click on extract kdz. Then open the .dz which just was created in the working directory of the kdz extractor. Tick "aboot_xxxxxx.bin", "boot_xxxxxx.bin" and "laf_xxxxxx.bin" in the lower window and hit extract dz. Then move the .bin files to your Linux desktop by using an USB stick, online storage or something like this.
Rename the files to "aboot.img", "boot.img" and "laf.img".
3) Preparing everything
Remove all your USB devices (except your G2 and your Keyboard & Mouse) from your computer, open a Terminal and type
Code:
ls /dev/sd*
The sda, sda1, sda2 etc. should be the partitions on your computer. But there should be a few others with sdb, sdb1, sdb2, etc. but no more. The sdb ones should be numbered from 1 to 36. This is your G2. Keep in mind how the three letters are (sdb, sdx, what so ever). (Make sure you run this as Super User, if you don't use slax!)
Then type
Code:
gdisk -l /dev/<insert the three letters you found out with the command above>
example:
Code:
gdisk -l /dev/sdb
It should now look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keep the numbers of the marked partitions in mind. In this case aboot=5, boot=7, laf=23.
4) Preparing everything
If you've managed it to get here, you are almost done. It's almost time for the final step now:
Open a terminal and type
Code:
cd Desktop
ls
You should now see the filenames of the 3 files (aboot.img, boot.img, laf.img) on your desktop in the terminal. If you do not, you either didn't type "cd Desktop" properly (The linux terminal is case sensitive!!!) or you haven't copied the files to the desktop.
5) Flashing the stuff
Code:
dd if=aboot.img of=/dev/<the 3 letters of your G2><the number of your aboot partition>
dd if=boot.img of=/dev/<the 3 letters of your G2><the number of your boot partition>
dd if=laf.img of=/dev/<the 3 letters of your G2><the number of your laf partition>
example (in my case):
Code:
dd if=aboot.img of=/dev/sdb5
dd if=boot.img of=/dev/sdb7
dd if=laf.img of=/dev/sdb23
6) Go back to stock using the kdz method
Now just follow this thread to get back to stock.

Reserved - just in case^^

bricked my lg g2 d802..plz help
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...

hbk4 said:
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...
Click to expand...
Click to collapse
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.

I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..

Soufiansky said:
I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..
Click to expand...
Click to collapse
Which one are you refering to?
NVM, adjusted the OP. Either use VirtualBox or download an older version of VMPlayer (which supports 32bit obviously) by picking Version 6.0 as major version.

Sunandroid said:
Which one are you refering to?
Click to expand...
Click to collapse
VMWAREplayer

Soufiansky said:
VMWAREplayer
Click to expand...
Click to collapse
read my post above (edited it).

Sunandroid said:
read my post above (edited it).
Click to expand...
Click to collapse
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.

Soufiansky said:
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.
Click to expand...
Click to collapse
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.

Sunandroid said:
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.
Click to expand...
Click to collapse
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.

Soufiansky said:
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.
Click to expand...
Click to collapse
What button combo do you use to factory reset?

Sunandroid said:
What button combo do you use to factory reset?
Click to expand...
Click to collapse
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..

problem soleved.....finally
Sunandroid said:
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.
Click to expand...
Click to collapse
finally , i solved the problem..
with the help of soombons (droidth) , i was able to fix my d802 in just 2 minutes. - USING SRK 2.0 TOOL ...
sharing the link for people with same problems
---
[LG-G2] Unbrick (qhsusb_bulk) by SRK Tool 2.0 (D8…: https://youtu.be/ERZvlJIC9dE
tonnes of thanks to SOOMBONS for the prompt help !..
CHEERS !!!

Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Soufiansky said:
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..
Click to expand...
Click to collapse
Weird. Did you use this method to go back to stock: http://forum.xda-developers.com/showthread.php?t=2432476
This worked fine for me every time I used it. Try to flash a KK ROM again, but do a CSE flash.
chaitea said:
Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Yeah I guess you have to do as you mentioned. Only thing you could try before doing so:
Hold down the power button for 20 secs. Then wait a few secs and try to get into download mode. Maybe the device shows up as qhusb_bulk again.

Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks

Batou069 said:
Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks
Click to expand...
Click to collapse
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.

Sunandroid said:
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.
Click to expand...
Click to collapse
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks

Batou069 said:
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks
Click to expand...
Click to collapse
Are you sure you can't get into download mode? (hold down the power button for 20 seconds (not shorter!), then holding the vol+ button and connect the phone to a computer)?
I could imagine that you can enter the recovery after holding down the powerbutton for 20 seconds with the button combo. I think so, because the kernel must be working somehow since it still manages to get shown properly on windows.
If none of the options above is working, the pin shortage is probably the easiest way to get into qhsusb_bulk and start freshly (following this thread).

LG G2 Stuck with grey lines after using auto rec. please for god sake help me.

ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device; LG G2 D802 32GB

Some one please?

DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.

This is why I worry messing around with my G2

Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk

Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.

This is a known problem. Have LG send you a new one

blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?

did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.

Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.

walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.

Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files

wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk

So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.

Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!

Possibly bricked device, need D80020y image? (URGENT)

Hi, I was trying to update my LG G2 D800 to Lollipop using this guide:
http://webtrickz.com/how-to-update-lg-g2-to-official-lollipop-os/
However, after the device rebooted, it went to the LG logo screen, displayed this message in the top left corner, and went to an indefinite black screen.
boot certification error
secure booting error
cause: boot certification verify
Holding down the power button for about 15 seconds turns the device off, but sometimes it turns itself back on and does it again. Turning it off, then quickly holding volume down and power button, releasing on logo, then holding again brings it to a "Factory Data Reset" screen, however, doing a reset does nothing and puts me immediately back to the same problem.
Holding volume up and plugging it into my PC does the same thing, and when plugged in, windows recognizes about 20 "unformatted drives", and shows it as QHSUB_BULK in device manager, under other devices.
Before this, I was running stock 4.4.2, D80020y, rooted with towelroot. I had attempted to create a TWRP recovery, and it said it succeeded, however it was unable to boot to recovery.
I was going to try to fix it using this thread: http://forum.xda-developers.com/showthread.php?t=2582142
However, I am unable to find an img for D80020y.
I have access to a Win 8..1 desktop, and I can run whatever OS necessary in a VM.
Does anyone know where to find one? Or, can anyone provide me with one? Or, is there another way to fix this?
I'm just worried that my device is totally gone at this point, and considering I bought it used, I have no warranty, nor a phone to replace it, currently.
Thanks so much to anyone who can help me!

First off, why didn't you just do an OTA update to Lollipop (via settings/about phone) instead of trying to manually do it? It's a lot easier and you could of avoided all of this...
Anyways, I am not sure what exactly happened (maybe it was a bad flash or maybe you screwed up somewhere), but it looks like you've gotten yourself in a real mess.
Did you triple check that you followed the article step by step? Did other people state in the comments about any problems they faced when using the method?
I have tried that method you linked before, and I used Ubuntu, which is best for that method. However, it did not work for me. I remember going on and on with that and ultimately just flat out replaced my logic board when I had a bricked G2.
And I can totally relate to to the twenty unformatted drives, I have been in same exact situation with the endless windows popups when I plug in my phone, but I never really figured out the issue. I remember before I was stuck in fast boot mode, and after awhile I couldn't even get to fast boot.
Can you get into recovery? Is the phone still alive? If so, you can use this to get back to stock http://forum.xda-developers.com/showthread.php?t=2432476
Hope this helps a bit, I have never been in your situation but if you want a real, simple solution to this: I would purchase and replace your logic board (phone's motherboard). It is a definite fix. If you are not comfortable with that, then I would advise to go ahead and do some research about this. Unfortunately, I have no idea where you can get that img (I do not have a D800, but rather a VS980), but I am sure with some Google searches you can find it.
I have bricked a couple phones in the past, and we all learn from our mistakes!
Best of luck!

fischer12345 said:
*snip*
Click to expand...
Click to collapse
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.

Jtpetch said:
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Click to expand...
Click to collapse
Gotcha. I haven't ran into the issue you have been describing at all before, but I just wanted to try to understand this situation a little better, I wish I could tell you what exactly happened.
As far as your problem, here's what I would do. The phone is still alive correct? Contact LG and send that bad boy in. Tell them you used it for a couple of months and all of a sudden it does not work anymore. I think that would be your best bet. However, do not tell them you modified it or whatever you tried to do with it.
Be aware if you do send it in to LG, make sure you have not tried to open up the phone and screw around with it internally. They will not fix it if that is the case. Also, it can be quite pricey depending on your current condition.
Oh, and LG will not provide you with those files, they are there to help you with any kind of phone issue, but not these kinds of issues.
This my friend is the best advice I can give you! Again, another option would be replacing the logic board, but that is ONLY a last resort.
BTW, you didn't hard brick it so that's a plus

I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jtpetch said:
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
Click to expand...
Click to collapse
can you enter download mode? pressisng VOL UP and then plug your phone and keep button press. does it goes to usb icon with curved arrows?

No download mode for me. Trying to boot to it just brings me the same error, and black screen.

Jtpetch said:
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Click to expand...
Click to collapse
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.

raptorddd said:
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
Click to expand...
Click to collapse
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.

Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
do the QHUSB_BULK Fix when u try it (its in 4)
anyway i got my g2 in a much heavier brick,
i have a third party lab that can possibly fix my g2...
its not that expensive....
so I just need to hope they can fix it

Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ

raptorddd said:
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
Click to expand...
Click to collapse
Yes, I am sure. I just tried it again, though, to confirm. Held volume up, plugged in USB, and it went to the LG logo screen, showed the same error text in the top left, and went to a black screen.
I am downloading the SRKtool right now, and will try as soon as i have it.

Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?

Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Click to expand...
Click to collapse
am not sure but there isnta kdz for lollipop right? you may need to go to KK KDZ
ooo you have d800 same as me. you need to download this and use the kitkat
Download Installer - KitKat 4.4.2 D80020c
http://forum.xda-developers.com/showthread.php?t=2663369 do that and once you in KITKAT ill tell you
if you need helps just ask

Ah, ok, will do. And thanks so much for all the help!

Jtpetch said:
Ah, ok, will do. And thanks so much for all the help!
Click to expand...
Click to collapse
no problem just hit thanks it i helped, once you in KK ill tell you how to go from there.

Wow, it flashed and everything without a hitch. I'm in KK now, and everything seems all good. So how would I go about upgrading to lollipop?

Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great

Jtpetch said:
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Click to expand...
Click to collapse
am glad you liked it, just pass the knowledge when someone is in the same shoes as you were..

i have the same problem as you please help
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
please guide me through what you did to get back to download
Click to expand...
Click to collapse