Develop Bugs

[Q]HTC Desire HD QHSUSB_DLOAD driver[brick caused by rom manager sdcard repartition]

Dear All,
After I did repartition sd-card with rom manager i can't boot my phone. I mean i can't even get to download or recovery mode. I think it also repartition internal sd too. Right now when I plug in to charge or usb even the red light does not turn on but windows 7 does recognize it as QHSUSB_DLOAD, if can find a driver I think I can flash it with odin but after several hours of searching I could not find any driver suitable for it. Can anybody help me with this?

Yep, odin is probably the right program to use
Here's another thread with the same story.

I know but as I don't have that weird driver Odin does not recognize phone. So I need the drivers called qhsusb_dload...

Actually I would only use Odin with Samsung...

I hope somebody can find solution to this problem, that we flash entire phone without recovery mode... if somebody has the driver please post it...

Ya, I have the same issue.
I wasn`t able to find the driver for my device too. Sad Panda!
...seems like there`s no solution right now. I ll give it to HTC this evening if noone could give THE advice to repair it on my own.
Does anyone know why the desire is crashing when trying to use ROM Manager to partition the sd-card?

Well, I think I will give it to HTC a few hours later today seems to me there is nothing we can do about it.

All the drivers that are needed are installed with HTC Sync. Odin won't find your DHD because it's meant for Samsung phones (and even they have to be turned on in download mode). As your phones won't boot to either recovery or bootloader there's not much you can do.

You are right, I already sent it to HTC. I hope they don't recognize that it's rooted. But as it has already repartitioned the sd-inside, I don't think they will try to recover any data and try to understand it.

xsdenied said:
You are right, I already sent it to HTC. I hope they don't recognize that it's rooted. But as it has already repartitioned the sd-inside, I don't think they will try to recover any data and try to understand it.
Click to expand...
Click to collapse
so what happened? did they replace it for you?????

was there ever a solution to this? did anyone have luck with htc?

Yes they give me new one 3 days later, so everything went ok.

duarab said:
was there ever a solution to this? did anyone have luck with htc?
Click to expand...
Click to collapse
yes there is a solution: go to your carrier and tell them my phone is NOT WORKING. they will keep you waiting for 2 weeks, then will give you a new phone. i did this and got my phone a new

I don't know if this helps anyone...... I found the drivers for "QHSUSB_DLOAD" but I haven't been able to do much else. If anyone else finds a way to recover the device please post.

Koush confirmed that this was an issue with older versions of ROM Manager and has since been fixed. However, this happened toe yesterday using the latest recovery and the latest ROM Manager. He hasn't responded to me as of this post. A new phone is on its way from tmobile.

vcglmcg143 said:
I don't know if this helps anyone...... I found the drivers for "QHSUSB_DLOAD" but I haven't been able to do much else. If anyone else finds a way to recover the device please post.
Click to expand...
Click to collapse
is this work for Motorola Arix...
thanks for advance ....

aaurnab said:
is this work for Motorola Arix...
thanks for advance ....
Click to expand...
Click to collapse
The device is bricked. The drivers don't help. The only fix it to send it back and get a new one.

Update: I can now repair the Desire HD with advanced JTAG recovery. If you need help with a bricked Desire HD, please PM me...

Riff Box Jtaging recovery im guessing.
Now i Dont have riff box, but I have x64 drivers installed and working for the qualcomm port, and QPST sees the phone properly. The only thing im missing are the files to flash.
Edit:
If anyone is needing them; Attached are the x64 drivers for "qhsusb dload"

You can't flash the phone when it's in CPU mode. The only devices that can really do that are the NVFlash units that are the Tegra 2 chipsets. From what I know, JTAG is required. And yes I use the RIFF box and advanced micro-soldering to recovery these particular models. The Desire HD is a very difficult phone to take apart and requires skill in small electronics to not damage components. Despite the build quality, HTC makes phones that are very difficult to dis-assemble.

[Q] Bricked Galaxy Nexus

Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.

Have you tried booting into Odin mode

ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.

have you your warranty on it?
return it and get a new one

It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.

I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?

Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.

same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks

Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!

Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.

After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys

galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.

OUYA stuck in APX/NVFlash

After loop updates to last version(1.0.248->1.0.264), my OUYA lost ethernet connection in (third in few minutes) update process and freeze. Reboot, it is stuck in APX/NVFlash mode. Help!
Thank you very much

Salvadorbs said:
After loop updates to last version(1.0.248->1.0.264), my OUYA lost ethernet connection in (third in few minutes) update process and freeze. Reboot, it is stuck in APX/NVFlash mode. Help!
Thank you very much
Click to expand...
Click to collapse
What symptoms are you getting? How do you know it's in NVFlash mode?
Sent from my Nexus 7 using xda premium
---------- Post added at 10:58 PM ---------- Previous post was at 10:46 PM ----------
The update was most likely incomplete/corrupt. Unfortunately, I've heard that the Ouya uses SBK in nvflash. You should try the print screen method of forcing a reboot to recovery (check out the post by mbm http://forums.ouya.tv/discussion/1380/recovery-mode). If you can get there, we can get you a flashable zip that would solve the issue.
Sent from my Nexus 7 using xda premium

mybook4 said:
What symptoms are you getting? How do you know it's in NVFlash mode?
Click to expand...
Click to collapse
Black screen and I connected ouya with my computer. It enumerates with an nvidia vendor id.
mybook4 said:
[/COLOR]The update was most likely incomplete/corrupt. Unfortunately, I've heard that the Ouya uses SBK in nvflash. You should try the print screen method of forcing a reboot to recovery (check out the post by mbm ). If you can get there, we can get you a flashable zip that would solve the issue
Click to expand...
Click to collapse
Unfortunately, print screen method (keyboard seem doesn't work in apx mode) doesn't work.

Have you tried to see if fastboot works, e.g. "fastboot devices" to see if the ouya shows up?
If you need to install fastboot, you can use this guide to install and configure the SDK http://forum.xda-developers.com/showthread.php?p=41247928
Sent from my Nexus 7 using xda premium

mybook4 said:
Have you tried to see if fastboot works, e.g. "fastboot devices" to see if the ouya shows up?
Click to expand...
Click to collapse
No, it doesn't work.:crying:

Salvadorbs said:
After loop updates to last version(1.0.248->1.0.264), my OUYA lost ethernet connection in (third in few minutes) update process and freeze. Reboot, it is stuck in APX/NVFlash mode. Help!
Thank you very much
Click to expand...
Click to collapse
What is the exact VID/PID?
If it fails to boot anything but APX mode, you are screwed. APX is locked down on the ouya (So much for "Open", eh?), and there's basically no way to get around it.
OUYA can *probably* fix it ,assuming they even know the SBK is set (I'm not really convinced.).
The weird thing however:
None of the released OTA's flash the bootloader or anything else that should ever be able to cause it to get stuck in APX.
No amount of failed flashing should be able to get it into that mode, ever!

rayman said:
What is the exact VID/PID?
Click to expand...
Click to collapse
USB\VID_0955&PID_7030
rayman said:
If it fails to boot anything but APX mode, you are screwed. APX is locked down on the ouya (So much for "Open", eh?), and there's basically no way to get around it.
OUYA can *probably* fix it ,assuming they even know the SBK is set (I'm not really convinced.).
Click to expand...
Click to collapse
I hope OUYA to release SBK and files for NVFlash (and obviously source code of rom and kernel, is it open console or not???? ). I don't want lost more money for a return (shipment fees and customs duties, I'm in Italy).
rayman said:
The weird thing however:
None of the released OTA's flash the bootloader or anything else that should ever be able to cause it to get stuck in APX.
No amount of failed flashing should be able to get it into that mode, ever!
Click to expand...
Click to collapse
In fact, It is incredible.
In the first day, my console is stuck in "Type password to decrypt storage" message after os boot. I succeded enter in recovery mode and make a factory reset. Yesterday this issue with APX mode. OUYA console is not ready for mass market.

The modem updater-scripts for my GS3 usually check a hash of applicable files before flashing. Ouya can probably do the same to ensure that they don't write a bad system partition / boot.img to the device. From the description, it sounds like the weak networking capabilities of the Ouya caused the updater.zip to incompletely download. Then the reboot into recovery caused the corrupt zip to be run. Basically...the update bricked the device. They need to fix both the weak networking and update their scripts to account for potentially corrupt files. It would be cool if we could somehow trick the device back into recovery.

[Q] Nexus 7 Hardbricked?!

Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!

See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582

mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?

crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.

mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!

crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.

mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.

crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.

Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?

crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs

malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.

crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links

malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!

crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?

malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).

For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.

The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.

Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/

Unbrick bricked by writing boot.img to wrong mmcblk

Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?

Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone

valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.

hi , can you boot into recovery ? ..if yes, i can maybe help

olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-

olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.

here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310

olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"

Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?

PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.