• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help HARD BRICK LG G2 qhsusb_bulk, but no partitions detected.

ohcafe02 said:
HELLO...iowabowtech
I'm in the same situation.
My PC detected Qloader 9008(via port 3 but I had chang to port41).
My model is LG G2 D802/32gb.
No drive found.No partition.No light on charging.Black Screen.
I tried so many methods but nothing work.
When use BoardDiag3.99c it shown <Device dload mode, device was not found in dload trying flash programmer>
I'm hopeless:(.
Please guiding me what can I do to recover it.
(Apologize to my bad English)
Click to expand...

i have same issue :(
Have you solved the problem ???
Sir iowabowtech Please help
 
iowabowtech said:
The reason for opening the phone in his case was to verify that it's a genuine D802 and not a refurb with mismatching motherboard. I'm aware of the tool to fix as I've had it since before it was publicly released. But we don't want to go flashing the wrong model's partitions. ;)
Click to expand...

Sir my phone is D802 but internal written D800 and on ic written D801 !!!
so how can i will recognize my phone's model ??? plz
 
Zebesh said:
Sir my phone is D802 but internal written D800 and on ic written D801 !!!
so how can i will recognize my phone's model ??? plz
Click to expand...

Use the model stamped on the rear of the motherboard. When you use the boarddiag tool, use the tot for the model stamped on the motherboard. Then flash all the individual partitions with that tool. It says "restore boot" as the default option but if you use the dropdown, you can restore all the partitions if you've already selected a tot as your target file.
 
iowabowtech said:
Use the model stamped on the rear of the motherboard. When you use the boarddiag tool, use the tot for the model stamped on the motherboard. Then flash all the individual partitions with that tool. It says "restore boot" as the default option but if you use the dropdown, you can restore all the partitions if you've already selected a tot as your target file.
Click to expand...

Sir thanks for reply :)
Sir it is D801 written on a board see picture sir i have downloaded tot files and extraction has been done on boarddiag v2.99a now when i tick on AP check and EMMC Test it gives me error emmc partition fail see picture.One thing more sir i have no partition show in computer management see picture
20170219_004848.jpg
bh.jpg
ddddd.jpg
 
You can try flashing the img's from a d801 tot but it may not work. The emmc test failure could mean its corrupt or damaged. If that's the case you would be unable to continue.
 
iowabowtech said:
You can try flashing the img's from a d801 tot but it may not work. The emmc test failure could mean its corrupt or damaged. If that's the case you would be unable to continue.
Click to expand...

Sir Thanks for instant reply you are sach a great 👍 :) :)
Sir i have remove 2 capacitors and short with tweezer now it is in 9006(com15)
disk drive partitions also found now what will be the next step ???

dax.jpg


Partition Photo See >>>

partition.jpg
 
iowabowtech said:
You can use the srk tool, its the easiest method.

https://forum.xda-developers.com/lg-g2/general/choise-unbrick-qhsusbbulk-qualcomm-9006-t3093844

Remember you will choose d801 to fix.
Click to expand...
I'm sorry for posting my thing here but I was unable to find where to make a thread from. (And I'm in REAL BIG TROUBLE)

I had rooted my d800 and installed twrp 2.7.0.0. I flashed a ROM (via https://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195). My phone booted and worked well until I rebooted it. Now it's stuck on the boot screen (no bootloops though).
The worst part is my phone DOES NOT CONNECT TO A PC EVER SINCE I ROOTED IT and I forgot to flash a custom recovery (and don't know how to access the stock recovery). I do have the backup of d80020y system but don't know how to access recovery.
Do you have any suggestions @iowabowtech.
Screenshot_20170219-144324.png
 
IMG_20170219_182512183_HDR.jpg
Okay. Finally. For the first time my phone does connect to the PC. But it shows under driver software installation that
USB Composite Device - ready to use
QHSUSB_BULK - no driver found
USB Mass Storage Device - ready to use
Qualcomm MMC Storage USB Device - reafy to use

It says that QHSUSB_BULK driver isn't installed but it still shows the numerous drives (I don't know what that means). What should I do next? Follow the same guide as for a QHSUSB_BULK error (as on http://androidforums.com/threads/lg-g2-d800-bricked-soft-bricked-back-to-brick.953331/)?
 
Last edited:
ShivangAgrawal said:
View attachment 116512 Okay. Finally. For the first time my phone does connect to the PC. But it shows under driver software installation that
USB Composite Device - ready to use
QHSUSB_BULK - no driver found
USB Mass Storage Device - ready to use
Qualcomm MMC Storage USB Device - reafy to use

It says that QHSUSB_BULK driver isn't installed but it still shows the numerous drives (I don't know what that means). What should I do next? Follow the same guide as for a QHSUSB_BULK error (as on http://androidforums.com/threads/lg-g2-d800-bricked-soft-bricked-back-to-brick.953331/)?
Click to expand...

There is a qhusb driver posted in one of the threads here. That would show you the exact error code. But I can tell you already that you are in 9006 mode. So yes, you can use the same advice I just posted to the previous guy. The srk tool from XDA.

Edit: here's the link for the qhusb drivers:
https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

Instructs for driver install...unzip into a regular folder on your desktop. Go to device manager, right click on qhusb device and manually update driver using the entire folder of drivers on your desktop as the source location. Windows will pull the individual files it needs.
 
Last edited:
iowabowtech said:
There is a qhusb driver posted in one of the threads here. That would show you the exact error code. But I can tell you already that you are in 9006 mode. So yes, you can use the same advice I just posted to the previous guy. The srk tool from XDA.

Edit: here's the link for the qhusb drivers:
https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

Instructs for driver install...unzip into a regular folder on your desktop. Go to device manager, right click on qhusb device and manually update driver using the entire folder of drivers on your desktop as the source location. Windows will pull the individual files it needs.
Click to expand...
How to do that 'dd'? While in download mode? (As I said it's the first time my phone has connected to the PC, I haven't spent time with adb ever)
 
Last edited:
iowabowtech said:
There is a qhusb driver posted in one of the threads here. That would show you the exact error code. But I can tell you already that you are in 9006 mode. So yes, you can use the same advice I just posted to the previous guy. The srk tool from XDA.

Edit: here's the link for the qhusb drivers:
https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

Instructs for driver install...unzip into a regular folder on your desktop. Go to device manager, right click on qhusb device and manually update driver using the entire folder of drivers on your desktop as the source location. Windows will pull the individual files it needs.
Click to expand...
How to do the 'dd'? While in download mode? (As I've said before it's the first time my phone has connected to the PC, so I haven't spent any time with adb. I'm a noob)
 
ShivangAgrawal said:
How to do the 'dd'? While in download mode? (As I've said before it's the first time my phone has connected to the PC, so I haven't spent any time with adb. I'm a noob)
Click to expand...

Your phone was showing up as being in qhsusb_bulk (9006). That's why all the extra partitions were showing up on your PC. So while in that mode, my advice was to use the srk tool from XDA developers site. I linked it several posts ago for another user having the same problem as yourself.

You don't have to know how to use the dd utility when using the srk tool as it does it all for you. You just select your model and choose the option to fix a 9006 bulk brick.
 
iowabowtech said:
Your phone was showing up as being in qhsusb_bulk (9006). That's why all the extra partitions were showing up on your PC. So while in that mode, my advice was to use the srk tool from XDA developers site. I linked it several posts ago for another user having the same problem as yourself.

You don't have to know how to use the dd utility when using the srk tool as it does it all for you. You just select your model and choose the option to fix a 9006 bulk brick.
Click to expand...
I'll try that ASAP. Thanks alot for your precious time and guidance

EDIT : I just read on a thread that G2 could be unbricked just by kdz/tot if download mode was accessible. Do I still need to dd write those img files if that's the case??

EDIT2 : Is it possible to dd write the TWRP img instead of recovery.img ?? And then flash the system backup of d80020y that I did before bricking. (That'll be easier for me, as well consume less data. Data is life) @iowabowtech
 
Last edited:
Hi guys, @iowabowtech please help me, I tried to install LineageOS on my sister's Lg G2 D800 and got it bricked now and when it starts goes to download mode always, when I try to flash with LG FlashTool I got this error "Laf retrieve gpt failed", I opened it and short the capacitors, I installed the Qualcomm driver and it connects in qhsusb_bulk 9006 but in disk management only recognize 1 partition, my computer is an old one with Windows XP SP3, I tried SRK Tool but it doesn't work. Please help me what can I do?

Thanks in advance.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom