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.

hard bricked my lg 930

hi
i hard bricked my lg 930
how ?
i followed this step
http://www.androidauthority.com/lg-nitro-hd-clockworkmod-cwm-recovery-48447/
(do not follow)
i tried install ClockworkMod (CWM) since i installed the koereean rom and (no wi-fi to install tru rom manager)
is anything i can do for my phone like i'm not able to go in download mode, i can't see anything on screen. black
while i connect the usb cable i can hear a sound like connecting to computer
thanks a lot

We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.

Maverick.Marq said:
We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.
Click to expand...
Click to collapse
first of all thanks for response
no, it doesn't show up in adb (use command adb devices)
i can hear only the sound from computer (exactly like you connect true usb cable) but nothing on screen
yes, i tried the steps but ask to connect the phone, no usb connecting

@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2

Malnilion said:
@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
thanks
anything i can do for my phone?

some update
some update
i have 2 computers
to the first one i never installed phone drivers other then lg drivers
1- in device manager with the phone conected (without or with battery) it's show "QHSUSB_DLOAD" with exclamation , see attachment
error 2 device manager lg p930 nitro.jpg
error device manager driver lg p930.jpg
2 - in USBVIEW20.exe when i open (phone still conected) i have this error (see attachment "error in usb view.jpg" and "usb view qualcomn.jpg")

some udate 2
in second computer i had many phone drivers like sony xperia play, htc evo 3d or htc desire
it's show zeus flash device with exclamation and now QHSUSB_DLOAD like the other computer - see " error desktop device manager zeus flash device"
i made 2 posts because i can't upload more then 4 images
i think to force to take driver for QHSUSB_DLOAD but how can i do that because i tried with propietes, update driver and don't want to take " android_winusb.inf" from lg drivers
i found in adb/adroid-sdk/extras/google a file android_winusb.inf and i have 3 choises (of course, i try to force to take the drivers,)
sorry for my english
if is some developer i can give access to my computer by remote
any ideas
thanks

update
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?

nickmatine said:
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?
Click to expand...
Click to collapse
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.

drumist said:
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.
Click to expand...
Click to collapse
i used nero just to see if is some error
mmcblk0p6 partition it's the bootloader partition?

Hi
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards

@allians2002,
Unless he sent it in to be hardware-flashed, it's probably pretty much hosed.

I think I have the same problem
http://forum.xda-developers.com/showthread.php?t=1569514
There is nothing you can do. I will sell mine, or if someone need a new screen or something, just so damn unlucky...

allians2002 said:
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards
Click to expand...
Click to collapse
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people

nickmatine said:
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people
Click to expand...
Click to collapse
i also have exactly the same problem. after unbricking . and coming to korean firmware i tried putting at&t firmware images and in the last step. it gave me an error "less in memory " for system.img.
the battery was at 2% when i did that. since then the screen wont light up.
i am trying to see if i can charge the battery with an external charger and then put back to phone and try if it boots.. i am pretty sad about it ..

i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047

nickmatine said:
i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047
Click to expand...
Click to collapse
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked

hem.acharya said:
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked
Click to expand...
Click to collapse
please tell as what happened
I'll let you next week after buy medusa box

finally, i bought the medusa box but i messed up my motherboard. Why?
In the schematic diagram for Jtag they give me the wrong pins (in mirror). Beacuse i tried many times with wrong configuration my motherboard died. After that i removed the JTAG conector and i so the wrong schematic
now,i still try to fix a lg p 930 so if anybody have a hard bricked phone for sell send a messege
Sorry for my english

SOLVED
greeting
After 6 months I'm back with feedback. I was Able to fix my LG P930 with Medusa box. Meanwhile I bought a professional microscope, Octopus Box, Z3X box and Riff box, so now i fix phones by JTAG. I managed to fix my P930 so is alive again after 6 months

[Q] Rogers SGH-I747M Hard Brick, JTAG only option?

Hello,
I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.
I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.
Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.
Cannot get into Download mode. Cannot get into Recovery.
Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.
It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.
Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.
I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help
http://forum.xda-developers.com/showthread.php?t=2121306
And this guide
http://forum.xda-developers.com/showthread.php?p=8822843
Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.
When I plug the phone into my PC without the battery in the phone I get a red LED.
When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.
Looked for other solutions...
Old thread, HTC specific, not really any help... http://forum.xda-developers.com/showthread.php?t=822939
Bad news, need to send device back... http://forum.xda-developers.com/showthread.php?t=1651149
This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://forum.xda-developers.com/showthread.php?t=1916796
Possible solution with linux box... http://forum.xda-developers.com/showthread.php?t=2239451
Goes on to this one, a lot like the other linux option above... http://forum.xda-developers.com/showthread.php?t=2369125
If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?
Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://forum.xda-developers.com/showthread.php?t=2374958
I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.

dege13 said:
Hello,
I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.
I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.
Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.
Cannot get into Download mode. Cannot get into Recovery.
Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.
It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.
Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.
I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help
http://forum.xda-developers.com/showthread.php?t=2121306
And this guide
http://forum.xda-developers.com/showthread.php?p=8822843
Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.
When I plug the phone into my PC without the battery in the phone I get a red LED.
When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.
Looked for other solutions...
Old thread, HTC specific, not really any help... http://forum.xda-developers.com/showthread.php?t=822939
Bad news, need to send device back... http://forum.xda-developers.com/showthread.php?t=1651149
This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://forum.xda-developers.com/showthread.php?t=1916796
Possible solution with linux box... http://forum.xda-developers.com/showthread.php?t=2239451
Goes on to this one, a lot like the other linux option above... http://forum.xda-developers.com/showthread.php?t=2369125
If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?
Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://forum.xda-developers.com/showthread.php?t=2374958
I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.
Click to expand...
Click to collapse
I had the exactly same thing as you . I flashed the omega 4.1.2 rom and got the black screen.....
what can we do now?

yaoll78 said:
I had the exactly same thing as you . I flashed the omega 4.1.2 rom and got the black screen.....
what can we do now?
Click to expand...
Click to collapse
You guys flashed a ROM for the international S3. Check the forum you got that ROM from.
Quite sure JTAG is a good place to start now.

SD CARD
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards

rasgula said:
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards
Click to expand...
Click to collapse
Unplug and plug till pc recognize it with your files on it. I need that image so if you could share it, it would be appreciate.

I want to share but how to extract the image from sd card?
Sent from my C6506 using Tapatalk

rasgula said:
I want to share but how to extract the image from sd card?
Sent from my C6506 using Tapatalk
Click to expand...
Click to collapse
By Mr.X ''If you want to create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command''

dege13 said:
Hello,
I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.
I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.
Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.
Cannot get into Download mode. Cannot get into Recovery.
Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.
It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.
Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.
I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help
http://forum.xda-developers.com/showthread.php?t=2121306
And this guide
http://forum.xda-developers.com/showthread.php?p=8822843
Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.
When I plug the phone into my PC without the battery in the phone I get a red LED.
When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.
Looked for other solutions...
Old thread, HTC specific, not really any help... http://forum.xda-developers.com/showthread.php?t=822939
Bad news, need to send device back... http://forum.xda-developers.com/showthread.php?t=1651149
This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://forum.xda-developers.com/showthread.php?t=1916796
Possible solution with linux box... http://forum.xda-developers.com/showthread.php?t=2239451
Goes on to this one, a lot like the other linux option above... http://forum.xda-developers.com/showthread.php?t=2369125
If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?
Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://forum.xda-developers.com/showthread.php?t=2374958
I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.
Click to expand...
Click to collapse
Sent from my Intex Aqua 3.2 using Tapatalk 2

Hello, i have the same problem with an i747m, i'd appreciate if some one can share the SD image to fix this thx all for your help and i hope it wont take to long,

Cerisan said:
Hello, i have the same problem with an i747m, i'd appreciate if some one can share the SD image to fix this thx all for your help and i hope it wont take to long,
Click to expand...
Click to collapse
You flashed the wrong image too? Your phone also doesn't go into download or recovery?

Unbrink was successful
audit13 said:
You flashed the wrong image too? Your phone also doesn't go into download or recovery?
Click to expand...
Click to collapse
Hello, i hardbricked my phone with other method, but it had the same symptoms as your bricked phones, here is a link to a SD image that worked like a charm for me, tested with a 64GB micro SD, and used win32diskmanager so i can create the SD in windows, cheers and good luck unbriking your phone
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
PS The unbrink was successful , i really dont remember all the posts where i get those files but here's the file for this thread

salam i downloaded 4.4.2 rom from sammobile.com and flashed it with mobile odin everything was cool it installed sucessfully but my sim was not detected so i reebooted it but nothing happened instead it was hard bricked so i request you to give a debrick file for 4.4.2 as 4.3 debrick file does nothing for me thanks in advance waiting for ur reply
---------- Post added at 11:22 AM ---------- Previous post was at 11:15 AM ----------
rasgula said:
hi there
i have an SDcard of 4GB i tried on 4 S3 i747M hard bricked phones its worked ....this card let them alive to download mode by pressing volume down key +home key + power. i want to share this image but when ever i connect this card to my PC (windows) its shows (need to format your card)
is there any software so i can make image and share...to help those who hard-bricked their phones.
regards
Click to expand...
Click to collapse
sir i downloaded 4.4.2 rom from sammobile.com and flashed it with mobile odin everything was cool it installed sucessfully but my sim was not detected so i reebooted it but nothing happened instead it was hard bricked so i request you to give a debrick file for 4.4.2 as 4.3 debrick file does nothing for me thanks in advance waiting for ur reply

Try this
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
Sent from my SM-N900W8 using Tapatalk

Just fyi, in case you didn't see my other posts about it, updating from 4.3 to 4.4.2 using Mobile Odin will brick the device. MO cannot flash the full firmware so your brick was caused by flashing the modem onto 4.3 firmware.

rasgula said:
Try this
www(mediafire(com/download/0vg9sgcvk4zuwm0/debrick-SGH-I747M-UEMK5.img
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
plz provide ur cell no so that we can discuss it easily this file didnt worked for me
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
DocHoliday77 said:
Just fyi, in case you didn't see my other posts about it, updating from 4.3 to 4.4.2 using Mobile Odin will brick the device. MO cannot flash the full firmware so your brick was caused by flashing the modem onto 4.3 firmware.
Click to expand...
Click to collapse
sir what to do now? as 4.3 debrick img above didnt worked for me

Do you have an I747M? If you have the I747 that image won't work.
I just posted two 4.3 images to try in the debrick thread. This should probably be discussed there anyway just so all of the info is easy to find.

DocHoliday77 said:
Do you have an I747M? If you have the I747 that image won't work.
I just posted two 4.3 images to try in the debrick thread. This should probably be discussed there anyway just so all of the info is easy to find.
Click to expand...
Click to collapse
its i747m rogers bricked it by flashing 4.4.2 with mobile odin

Mobile odin cannot flash the full firmware, so you ended up with the 4.4.2 modem on 4.3 firmware which we know will brick.
You will need to use a debrick.img from another I747M, probably from another Rogers one specifically. Not sure if it'll work or not from another carrier.
Note that we have yet to get it working for any device that bricked by flashing the modem. Watch the debrick thread for updates.

Revive a dead s4 mini lte GT-I9195

Hello,
I had in the first place a hanging in the boot screen issue witouth the possibility to enter the recovery mode (only download mode) so I tried to flash the custom firmware (a lot of times) and in different ways ( Kernel first then firmware, then with PIT file ... anyway) ...
The last time a was flashing the phone it simply turn off during the flash. and since then it won't turn on ... It's not a battery issue because after that I charged the battery in another working phone and still no turn on.
When I plug the phone into the PC I still hear the usual sound. So I still believe there is hope.
After some research I found an official samsung document describing how to solve the very same problem for a galaxy s4 GT-I95100 ( the file is attached).
Did someone know if we can apply this to the mini or where we can find the specific document for my phone ?

Any Help please ? ... I just want to know if my phone still can be fixed
did anyone heard of reviving a phone that doesn't turn on ?

If it can't be turned on (no download or recovery mode), then it's hard bricked and needs to be serviced. It needs to be fixed by either replacing the main board or using a jtag box to repair boot.

arco68 said:
If it can't be turned on (no download or recovery mode), then it's hard bricked and needs to be serviced. It needs to be fixed by either replacing the main board or using a jtag box to repair boot.
Click to expand...
Click to collapse
Thanks for your response Arco ... dou you know if samsung repair center is supposed to have this jtag box to repair the boot?

I don't think all of them have it. I had to send in my Galaxy W two times for the same problem, and both times they replaced the complete motherboard.

arco68 said:
I don't think all of them have it. I had to send in my Galaxy W two times for the same problem, and both times they replaced the complete motherboard.
Click to expand...
Click to collapse
okay, from what I saw when googling about this jtag box ... I must dispose of a very updated jtag box to fix my phone. I hope I'll find a repair center having this.
Thank you anyway!

You could try this. No harm trying since it looks like you'll have to send it in to Samsung anyway.
http://forum.xda-developers.com/showthread.php?p=46318162

on russian 4pda forum was published one more method of reviving the phone (translation from russian):
initial situation:
- we have a brick with killed bootloader after unsuccessful flashing, not turning on, no reaction on buttons, no any mode available (recovery, download).
What is needed:
- any Linux, like Ubuntu, but more convinient is PartedMagic of any version;
- MicroSD card;
- working phone of the same model or dump of its first 139008 blocks (about 70MB).
How to make a dump:
- on rooted device download from Google Play app "TerminalEmulator" and run it;
- Enter su, appears "[email protected]:/ #", enter "dd if=dev/block/mmcblk0 of=sdcard/mmcblk0uptop7.img count=139008";
- after completion copy file "mmcblk0uptop7.img" from the phone to PC, for example to drive C:/.
How to revive the phone:
- insert MicroSD into PC and launch "PartedMagic";
- copy dump to MicroSD, for this open Terminal, we see "[email protected]:~#", enter "dd if=/media/WIN7/mmcblck0uptop7.img of=/dev/mmcblk0", where "/media/WIN7/" - it's your drive C:/, where stored a dump, and "/dev/mmcblk0mmcblk0" - your MicroSD in PartedMagic;
- wait for completion, remove MicroSD;
- put MicroSD to non-working phone, connect the phone to PC using USB;
- if all steps are done correctly, phone will boot by pressing the keys, using bootloader from external MicroSD;
- now it is possible to re-flash internal eMMC using Odin, to make a possibility to remove external card;
- that's all, phone completely revived.
Supported devices:
- tested on i9190, will work on i9192/i9195, should work on smartphones of other brands with new Qualcomm chips.
Technical details:
- details are too big to write. If you are interested - read about MSM8930 boot architecture and etc.
Some conclusions:
- Qualcomm has made a good modern chip, with a lot of feasibility, but not placing many information to open sources;
- Samsung - trying to complicate life of users by integrating of its own digital signature, what is leading to immediate bricking of devices when trying to modify bootloader. Be careful.
Click to expand...
Click to collapse

babuk123 said:
on russian 4pda forum was published one more method of reviving the phone (translation from russian):
Click to expand...
Click to collapse
can someone send me these files needed because I cannot find another working s4 mini. Thanks

if the phone can boot on download mode, you must flash debrick.img and stock firmware

Yes but my phone does not even boot... no mode

Anopy45 said:
Yes but my phone does not even boot... no mode
Click to expand...
Click to collapse
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
oualibadr said:
Hello,
I had in the first place a hanging in the boot screen issue witouth the possibility to enter the recovery mode (only download mode) so I tried to flash the custom firmware (a lot of times) and in different ways ( Kernel first then firmware, then with PIT file ... anyway) ...
The last time a was flashing the phone it simply turn off during the flash. and since then it won't turn on ... It's not a battery issue because after that I charged the battery in another working phone and still no turn on.
When I plug the phone into the PC I still hear the usual sound. So I still believe there is hope.
After some research I found an official samsung document describing how to solve the very same problem for a galaxy s4 GT-I95100 ( the file is attached).
Did someone know if we can apply this to the mini or where we can find the specific document for my phone ?
Click to expand...
Click to collapse
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...

andreluigo said:
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Did you get the files to send them to me?
I have the same issue...
My S4 Mini died suddenly...
Click to expand...
Click to collapse
Did you fix yours? Can you share the procedures and and the files if possible?

sarry86 said:
Did you fix yours? Can you share the procedures and and the files if possible?
Click to expand...
Click to collapse
Unfortunatelly, I couldn't fix it...
I sold it for taking of pieces!

andreluigo said:
Unfortunatelly, I couldn't fix it...
I sold it for taking of pieces!
Click to expand...
Click to collapse
You could have booted it like me but i am just stuck in a boot loop no matter what i am doing with odin

sarry86 said:
Did you fix yours? Can you share the procedures and and the files if possible?
Click to expand...
Click to collapse
The Russian method mentioned is just making a debrick image, search the debrck thread for file & procedure or internet for a debrick image for your phone

DarkJoker360 said:
if the phone can boot on download mode, you must flash debrick.img and stock firmware
Click to expand...
Click to collapse
How can i flash debrick.img my phone is booting on download mode

ArduinoPi said:
How can i flash debrick.img my phone is booting on download mode
Click to expand...
Click to collapse
Just put it in sdcard and boot normally

DarkJoker360 said:
Just put it in sdcard and boot normally
Click to expand...
Click to collapse
sorry I don't understand. Can you tell me more, please!

[Q] T-Mobile S2 T989 - hardbricked / can jtag fix it?

I received an SGH-T989 that wouldn't boot. It had TWRP on it, so I was able to flash latest stable CWM. Upon reboot, it apparently became hard-bricked.
Currently, I'm unable to enter download or recovery modes. USB Jig does not work. There is no output on the screen, even when charging the battery. When connected in Windows (32 or 64), I get a usb error message: "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
My question: Is the motherboard dead, or could a jtag repair fix it?
What I've tried:
multiple micro usb cables
usb jig
odin
keis
heimdall
Thanks xda!

Dostoevsky said:
I received an SGH-T989 that wouldn't boot. It had TWRP on it, so I was able to flash latest stable CWM. Upon reboot, it apparently became hard-bricked.
Currently, I'm unable to enter download or recovery modes. USB Jig does not work. There is no output on the screen, even when charging the battery. When connected in Windows (32 or 64), I get a usb error message: "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
My question: Is the motherboard dead, or could a jtag repair fix it?
What I've tried:
multiple micro usb cables
usb jig
odin
keis
heimdall
Thanks xda!
Click to expand...
Click to collapse
so the qhsusb_dload does not apear when your device is plugged into the computer? if so please hold on a little longer, somebody found a method of unhard bricking S3's and eventually Note 3's and the galaxy megas and im getting closer to being able to do this aswell im going to try to fix mine when i get home so hold on

Trozzul said:
so the qhsusb_dload does not apear when your device is plugged into the computer? if so please hold on a little longer, somebody found a method of unhard bricking S3's and eventually Note 3's and the galaxy megas and im getting closer to being able to do this aswell im going to try to fix mine when i get home so hold on
Click to expand...
Click to collapse
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:

Dostoevsky said:
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:
Click to expand...
Click to collapse
Hello I was wondering if the Jtag did its job?

sirsmokey said:
Hello I was wondering if the Jtag did its job?
Click to expand...
Click to collapse
Jtag should always do the job, unless there was physical damage done to the motherboard.

Dostoevsky said:
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:
Click to expand...
Click to collapse
Trozzul said:
Jtag should always do the job, unless there was physical damage done to the motherboard.
Click to expand...
Click to collapse
Thanks for the quick reply , i guess the next question i should ask , is it really worth the 100 bux for the j tag service or to put the money towards a newer phone ?,hmmm rhetorical i guess

sirsmokey said:
Thanks for the quick reply , i guess the next question i should ask , is it really worth the 100 bux for the j tag service or to put the money towards a newer phone ?,hmmm rhetorical i guess
Click to expand...
Click to collapse
The t989 has great specs, only downside is its PPI (really low) if you still love it, I would wait if you want to send it into JTAG repairs, we are on the verge of unbricking our t989 without JTAG! Looks like we need someone with a working t989D though

I have been studying the other 'unbrick' methods, its definatly mind expanding, the amount of knowledge absorbed can seriously make you forget time n space.
If there is anything I can do / contribute holler at me.
Now ill tell you something weird so I flashed a rom not meant for T989D plus I did it all without being rooted. (if it matters) since Since the flash the phone doesn't boot into recovery or show a bootanimation, just darkness.Yet it felt operational in hand.
Once I plugged it back into the PC all I got was a constant notification of drivers that cannot be identified Also it keeps connecting and disconnecting the device.
None of this is weird until I installed OMAP flash and the T.I. drivers for which was used to fix my friends nexus. After he left I plugged my s2 to the PC still nothing. I looked away for a brief moment . Then i noticed MobileGo for Android popped on screen. Visually showing my s2 as an Alcatel rom.
just bizzare.....

The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.

Lord Zog said:
The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.
Click to expand...
Click to collapse
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir

sirsmokey said:
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir
Click to expand...
Click to collapse
glad to hear its working again! might i ask how you went about this?

sirsmokey said:
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir
Click to expand...
Click to collapse
Lord Zog said:
The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.
Click to expand...
Click to collapse
Hi, so I also have a hard bricked t989 galaxy s2 (tmobile variant) and I'm attempting to understand the instructions. However my phone has another issue...usb connection to the computer does not work, it hasn't worked since the micro usb port on the phone was replaced because the old one broke. So really the phone could charge but never connect to my pc as it cant be detected...so what are my options? If i create the sd card with the image, will i still need to connect it to a pc in order to force the phone into download mode? Please help...