Database Develop

Any chances of resurrecting my Galaxy Tab?

Ok! I bought a Samsung P1000N Galaxy Tab from ClaroPR this week. Like always with every android devices i have i rooted it with superoneclick. Yesterday i was trying to update the tablet to gingerbread since it had Froyo. Follow the tutorials in here to flash it(I guess i didnt read the warnings about the secure bootloaders or something like that) but the thing is that i ended up softbricking my device. The gingerbread i was trying to flash was the JQ1. Anyways, i tried to flash it using Odin 1.7, it ended up failing and now i just have the cell triangle and computer logo of dead on the screen. Thing is that i know its not supposed to be totally bricked. But then in the device manager it doesnt show as samsung composite device or anything like that. I need help from someone who has gone thru this already and knows what to do. Or is it just a brick and thats it? Thanks...

enelyam said:
Ok! I bought a Samsung P1000N Galaxy Tab from ClaroPR this week. Like always with every android devices i have i rooted it with superoneclick. Yesterday i was trying to update the tablet to gingerbread since it had Froyo. Follow the tutorials in here to flash it(I guess i didnt read the warnings about the secure bootloaders or something like that) but the thing is that i ended up softbricking my device. The gingerbread i was trying to flash was the JQ1. Anyways, i tried to flash it using Odin 1.7, it ended up failing and now i just have the cell triangle and computer logo of dead on the screen. Thing is that i know its not supposed to be totally bricked. But then in the device manager it doesnt show as samsung composite device or anything like that. I need help from someone who has gone thru this already and knows what to do. Or is it just a brick and thats it? Thanks...
Click to expand...
Click to collapse
If you get anything on the screen at all (Triangle, Download mode, Samsung logo, etc...) It's not bricked, just sponged. Unfortunately I don't have any experience with the P1000N, but in general, try reloading the samsung drivers and try another USB port. Once you get it to show up in device mangler you can push the right tar with Odin and you'll be cooking with gas again. Sorry I can't help with this specific model, but sammy devices in general are hard to truly "brick"

Okay i think now its dead. It turned off when it lost the charge and now not even Heimdall recognize it. So if someone knows about a good tutorial on Jtaging this i will appreciate.
Edit: Found useful guide in here to resurrect it so i will give that a try...

The Unbrickable Mod works like a champ! I know, because I had to resort to this over this last weekend.
However, it does require mods to the mainboard that require some skill. Once accomplished, it is virtually impossible to brick your Tab.
http://forum.xda-developers.com/showthread.php?t=1338073

enelyam said:
Okay i think now its dead. It turned off when it lost the charge and now not even Heimdall recognize it. So if someone knows about a good tutorial on Jtaging this i will appreciate.
Edit: Found useful guide in here to resurrect it so i will give that a try...
Click to expand...
Click to collapse
Why you want to go for Jtag just becoz battery is dead. Get the Tab Opened, Recharge the battery externally (Repair/Service Center should help). Follow the Team Overcome Guide to install the Stock Safe Rom and then you can either continue with it or move to any other ROM of your choice.
I would keep JTAG as the Last option.
If it's new Tab, it should still be under warranty.

wow, impressive post (the unbrickable mod).. Not sure I'd have the guts to do that though..

Hard Bricked Galaxy Tab!

I rooted my Tab with Clock Mod and I'm still on contract I installed the wrong ROM (Stupid Mistake) I clicked reboot now nothing happens?
I do get a driver connection when I press the power button for 10 seconds on The PC (not my pc A friends) The tab is my only device to the Internet besides I'm writing this from his PC.Of course the screens blank.
Please Help, I'm on contract with a carrier paying for A not working device I'm hoping to get it working and restoring but to A stock/un rooted versrion.
Yes i was rooted and had Clock Mod when trying to install A ROM being dumb. As I said You can ear the driver sound in the computer when pressing the power for 10 secounds but no screen, I hope there is a way to reverse this and get back to my orginal boot loader.
Thanks :.(
If i can save i be staying on stock software.

Does Odin recognize the device
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

I am with spudster
Odin Does not recognize the device, but when i plug it into my desktop i can her the input sound, but i look in device manager and the device will not pop up, but although when i hold the power button for 10 seconds it will start making the driver sound, it makes the driver sound like i am pulling the usb cable in than out, the driver sound stops as soon as i release the power button. i we have tried to put the device in download mode, blind folded. I have looked up on youtube and all i found was Jtag.Look This Up On Youtube ( Samsung Galaxy TAB 8.9 (LTE) - JTAG Brick Repair Servic) .But i couldnt do this bbecause the tablet is also owned by a carrier.. Please Help, Thank you

If Odin doesn't recognize the device you're in trouble. I would try to flash the stock rom with odin but I don't think it will work. But maybe you get lucky. If it's still under warranty you could try that. Just play dumb and say it stopped working and you don't know why. Otherwise jtag is your only other option.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

OK,The computer detects it but odin won,t I will try to get A JTag service
if theres nothing else that can fix it :.(

Try to flash using ADB !
---------- Post added at 12:05 AM ---------- Previous post was at 12:02 AM ----------
If irs detected by the pc ADB should work! Worth a try mate

..
None of these works, except for the jtag, which i havnt done yet... i need to buy a jtag and figure out how to use it??

jaydenmoore2015 said:
None of these works, except for the jtag, which i havnt done yet... i need to buy a jtag and figure out how to use it??
Click to expand...
Click to collapse
No. Google mobiletechvideos. It's a service you send your device to and they jtag it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

.
The computer is only detecting it

Have you installed the device drivers on the PC? Odin wont recognise the tab without them.
If you can get into download mode, install drivers (or Kies) on PC and then odin should see the tab when connected.

Re
Yep, i have downloaded all the drivers for my device....
well i have let my battery go FLAT and now i am getting this device driver Qualcomm HS-USB QDLoader 9008 (COM6) So i try odin again because thinking that the COM6 at the end would be recognized and it still doesnt turn on, i have looked for jTagers around my state there is hardly any and the only one is over seas.... Is there any other ways to do it with a program

..
Only thing it is doing though reconizing An driver when we plug it in the computer.
If there is A way to reverse the firmware changes back to stock This would be A relief.
We could take it to a tech or back to samsung to repair with orginal firmware but that may not be in A few months since I will need to save the money.
The tab was fine untill I mistakly flashed the wrong Firmware (stupid me)
Thanks for the help so far.

Hey
We could try this
http://forum.xda-developers.com/showthread.php?t=1975274

re
all the drivers are installed all that it says is this this driver, Qualcomm HS-USB QDLoader 9008 (COM6) and i have just opened my device up and taken out the battery, and i put all the componants back together, The Device Is Just Doing The Same Thing

jaydenmoore2015 said:
all the drivers are installed all that it says is this this driver, Qualcomm HS-USB QDLoader 9008 (COM6) and i have just opened my device up and taken out the battery, and i put all the componants back together, The Device Is Just Doing The Same Thing
Click to expand...
Click to collapse
You're hard bricked. Jtag or warranty are your only options.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

D....
Spudster1 said:
We could try this
http://forum.xda-developers.com/showthread.php?t=1975274
Click to expand...
Click to collapse
Doesnt Work

Ok, Guess im screwed till May or when ever I can get money to send it back to samsung
And how can warranty apply? its on a contract and Ive already opened it to get to the battery (plus theres a few cracks that I will be replacing)
Thats why I was iffy about rooting in the first place should of stayed with stock..
Thanks Anyway, I will update yous when I get the money for the reparis.

[Q] Bricked Samsung Ativ S T899M Rom Flash?

New to Windows Phone 8 (been flashing custom ROMs on Android phones for a few years). Got an unlocked (previous Rogers) Ativ S SGH-T899M from Canada and have been using it on T-Mobile for the past few months. I tried to update it to GDR3 via the "Preview for Developers" and the phone is bricked. It gave me a BSOD error during the update and now it won't turn on. I tried every button combination possible to reset it to no avail.
When I connect it to my PC, it comes up as a Qualcomm HS-USB QDLoader 9008 (COM3).
I've searched everywhere and it seems that there are no T899M ROMs to flash? Any ideas and help would be greatly appreciated it. I love my phone and don't want to get rid of it!

No ROMS are available for it. I've been meaning to ask who has been leaking the ROMs for the 3g/non-lte model, but I have no clue. This is one of the things I've covered in the FAQ.

ROM is out... http://forum.xda-developers.com/showpost.php?p=58872571&postcount=6

qhsusb_bulk hard bricked my Shamu,how can i unbrick it?

Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.

no one?

Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.

This updates been a nightmare

synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that

beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.

This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys

randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.

synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.

I'm still stuck. Any progress ?

synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked

I had to RMA

randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.

efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.

Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!

http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine

randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.

i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful

randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA

im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.

Hard bricked stock HTC One M7

Hi, new to this forum so apologies in advance if I write something really noobish here.
So my old device HTC One M7 decided to kill itself for no reason, it's completely stock, I haven't tampered with it at all.
I had it on power saver mode because I had been on an interrail trip through Europe and then just one morning it died without warning, the night before I plugged it in to charge and when dawn breaks, it's dead.
I first thought it was the black screen of death that some Android might suffer from but I tried the steps of shining a bright light at the top left corner of the screen but nada, and then I plugged it into my laptop which saw it as "Qualcomm HS-USB QDLoader 9008" and I tried some steps from the guide that dexter93 posted and well it didn't work, I also tried to use a RUU but it always returned with that there wasn't any device connected to the USB port, however something happened because now it's not shown as the "Qualcomm HS-USB QDLoader 9008" but as the "QHSUSB-DLOAD".
I don't know what it means but I hope that my device hasn't passed the Gates of Valhalla.
If you need more specific information please do tell me /BTV

BorisTheViking said:
Hi, new to this forum so apologies in advance if I write something really noobish here.
So my old device HTC One M7 decided to kill itself for no reason, it's completely stock, I haven't tampered with it at all.
I had it on power saver mode because I had been on an interrail trip through Europe and then just one morning it died without warning, the night before I plugged it in to charge and when dawn breaks, it's dead.
I first thought it was the black screen of death that some Android might suffer from but I tried the steps of shining a bright light at the top left corner of the screen but nada, and then I plugged it into my laptop which saw it as "Qualcomm HS-USB QDLoader 9008" and I tried some steps from the guide that dexter93 posted and well it didn't work, I also tried to use a RUU but it always returned with that there wasn't any device connected to the USB port, however something happened because now it's not shown as the "Qualcomm HS-USB QDLoader 9008" but as the "QHSUSB-DLOAD".
I don't know what it means but I hope that my device hasn't passed the Gates of Valhalla.
If you need more specific information please do tell me /BTV
Click to expand...
Click to collapse
Dead motherboard

alray said:
Dead motherboard
Click to expand...
Click to collapse
How can you be so sure?

BorisTheViking said:
How can you be so sure?
Click to expand...
Click to collapse
3 years in this forum, saw hundreds of QHSUSB_DLOAD threads/posts.
Either caused by
flashing an incompatible firmware:
Flashed incompatible firmware, then rebooted the phone and went directly in QHSUSB_DLOAD mode.
Hardware problem:
Phone randomly shut-off and went in QHSUSB_DLOAD mode.
Most of the time, when its caused by #1, you can fix it using dexter93's Unbrick Project. If its #2 you'll have to send it for repair.
Yo can however try the Unbrick Project, just to be sure (maybe your firmware got corrupt for whatever reason and the hardware is still good)

alray said:
3 years in this forum, saw hundreds of QHSUSB_DLOAD threads/posts.
Either caused by
flashing an incompatible firmware:
Flashed incompatible firmware, then rebooted the phone and went directly in QHSUSB_DLOAD mode.
Hardware problem:
Phone randomly shut-off and went in QHSUSB_DLOAD mode.
Most of the time, when its caused by #1, you can fix it using dexter93's Unbrick Project. If its #2 you'll have to send it for repair.
Yo can however try the Unbrick Project, just to be sure (maybe your firmware got corrupt for whatever reason and the hardware is still good)
Click to expand...
Click to collapse
But that's the thing, it did randomly shut itself down but it entered Qualcomm HS-USB QDLoader 9008 mode instead of QHSUSB_DLOAD mode.
I myself managed to get it into QHSUSB_DLOAD mode.

BorisTheViking said:
But that's the thing, it did randomly shut itself down but it entered Qualcomm HS-USB QDLoader 9008 mode instead of QHSUSB_DLOAD mode.
I myself managed to get it into QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
If dexter93's guide didn't helped then there's nothing more you can do. You're not the first one and not the last one to have this problem and unless it was caused by a bad firmware.zip flash (it wasn't) no one ever found a solution to revive their phone.
Sent from my HTC One using XDA Labs

alray said:
If dexter93's guide didn't helped then there's nothing more you can do. You're not the first one and not the last one to have this problem and unless it was caused by a bad firmware.zip flash (it wasn't) no one ever found a solution to revive their phone.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Not even JTAG?
And if I manage to open the phone, you wouldn't know where the internal storage is?

BorisTheViking said:
Not even JTAG?
And if I manage to open the phone, you wouldn't know where the internal storage is?
Click to expand...
Click to collapse
The internal storage is a tiny Samsung chip soldered on the motherboard.
Sent from my HTC One using XDA Labs

alray said:
The internal storage is a tiny Samsung chip soldered on the motherboard.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Right and that translates to that everything is burnt to a crisp?
So there is no way to retrieve anything from the internal storage?