Database Info

HTC Touch Pro 2 Brick

Dear Folks at XDA,
I would like to ask for you help with my HTC Touch Pro 2. I recently tried to update it to the new AthineOS CHome TF3D WM6.5 Manila ROM v 1.0 and unfortunately I failed.
The problem is that my phone now freezes at the black startup screen with the Touch Pro 2 logo and the red codes at the bottom.
I've flashed the ROM several times before and never got this issue.
Due to the fact that the phone doesn't finish the boot-up and I thus I can't get ActiveSync I'm afraid I messed up my phone for ever.
Please someone tell me I got a way out of this, I'd appreciate it very much.
Greetz,
SjonSjon

umm.... I don't think you can change the firmware just yet on the CDMA version of the phone... if you used a HardSPL that's available in the Rhodium forums then you probably used a GSM specific ROM on your CDMA phone... not sure what to tell you other than making sure you read the CDMA forum before trying something so risky. Best solution, unless someone knows how fix your phone in it's current state, is to toss it under your car and run it over and try to cash in on the insurance.

Problem solved!
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon

I am glad you have recovered the beautiful device; and thanks for sharing a working solution.

sjonsjon said:
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
Click to expand...
Click to collapse
Good job!

big thanks for solution.

You just saved my life!!!

Don't get our hopes up! This is the wrong forum. CDMA TP2s can't be flashed at all yet.

This was a life saver post so a quick bump for anyone that needs it.
I unlocked my CDMA phone, installed a few roms -- decided to go back to my stock rom default (which was Telus) -- reinstalled and bam -- bricked.

Well, technically it's not a brick if you can get back into the bootloader to reflash. So no worries everyone. If everyone reads instructions well enough we should hopefully see zero "real" bricks. Or at most, just enough to only build bbq pit rather than a house.

I think my phone is truly bricked
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.

my cdma is rebooting endlessley i reflashed stock rom and evorything. it seriously dosnt want to work. its most sadness... i am cashing in on the insurence. but they are going to send me a refurb..
spend 600$ on a phone got inurnce i hope the used one dosnt fail me.

Esazi said:
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
Click to expand...
Click to collapse
I did the same exact thing to mt TP2. Same outcome.

We have to learn somehow....
That stinks man. If you did, then your phone is truly bricked. You are going to have to get a replacement or switch to another phone because there is nothing you can do to get it going again. I tried everything possible and eventually just ordered a replacement. I have it now and it's working beautifully, but needless to say I am a little scared away from any more unlocking or flashing for a while.

If you read carefully you dont have to be scared of flashing
I was a noob some time ago but before doing anything I took care of reading and understanding before doing nothing.
lesson learned
By now I have flashed more than 60 times on 3 diferent HTC devices and all were a succes
Hope you get your TP2 working again!

I hope I can get there
Someday I hope to be a flashing expert, but until then I will take it slow and read carefully. Thanks for your encouragement. When I actually get money to pay for the unlock for my TP2, I will let you know how flashing goes.

How do you keep the phone in bootloader? Mine goes right to the press volume instuction screen. Other than that I'm stuck on the black name screen,also my usb will not register in device manager. This was my first try at flashing.

gadgetgirl28 said:
You just saved my life!!!
Click to expand...
Click to collapse
Holy hell, you're not lying. Thanks for coming back to post your solution!
This post saved me at least a few hours of frustration and ever worsening decision making.

So it's totally true???
this situation hasn't solution;
I was unlocking my phone (the HTC Touch Pro 2 <SPRINT>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, AND PLEASE somebody tell me , that it can be save it
;9

please help
i have the same problem. is there a way to save my phone?

[Guide] How to brick your Desire S

How I bricked my Desire S - information on avoiding brick and an indictment of the dubious nature of HTC's S-on policy
The Desire S is a great phone so why did I want to root it?
The main reasons for rooting and s-off for me were:
Titanium backup (android built in backup is weak)
Being able to remove bloatware that takes up unnecessary spaces and unnecessarily reduces battery performance.
To try different ROMs from the community
Video screen capture
And of course I bought the phone so isn't it mine to use as I please.
Having waited a long time for a good s-off tool to come out I was getting more and more anxious to s-off.
Alpharev got together with Unrevoked to create Revolutionary.
I had previously used the Unrevoked tool to root my first generation Desire. The tool worked easily and flawlessly even on my Mac.
I later used the Alpharev bootable CD to s-off and root a later generation Desire. Again it worked smoothly and flawlessly.
Having had this positive experience I felt confident in the new tool, Revolutionary.
I read everything I could find about how the tool worked and how others were finding results. All seemed straight forward and uncomplicated so I proceeded to download and run the tool from my PC because there was no Mac version available.
Temp root and s-off went smoothly. No apparent issuse. Both Hboot and Fastboot had been successfully replaced on the phone, and CWM recovery was working.
So I added su in recovery then ran a nand backup of the whole system at this point.
Then I downloaded a Cyan 7 ported for the Desire S that was getting good reviews and feedback. The rom seemed to flash clean. After running it for a short time it stated crashing, so I decided to try an MIUI ported to Desire S. Again a ROM with good feedback and labeled as stable.
Downloaded the ROM and flashed it after a full wipe in recovery.
This time on reboot the phone hung at the HTC screen on boot for a very long time. So I wanted to do a force shutdown.
Here is where things got ugly.
The Desire S does not have a force shutdown keystroke combo as my old Desire did. So I opted to pull the battery.
Reinserting the battery and booting into recovery nothing worked properly.
CWM wouldn't mount its partitions, wouldn't flash a rom or even do a factory reset.
I tried doing some functions in fastboot mode. But nothing worked. Any command issued in fastboot mode would just lock up the phone and terminal.
At this point I was pretty worried so I got on #revolutionary and chatted with some of the big guns. I got some good feedback to test this and try that but in the end nothing worked. So I got on XDA forum and looked for others with similar issues.
What I found at this point was very troubling.
XDA user opumps had the same issue as me and had done some great research about the problem.
http://forum.xda-developers.com/showthread.php?t=1150917
It becomes clear on reading, that like him, my Desire S had a fried eMMC chip. This is the internal storage device for HBoot. Once cooked your are basically F*ucked. There is no recovering from this by reformatting the eMMC. Pooched.
Doing the tests on the XDA post I found my eMMC to be pooched.
Now the question is, What fried the eMMc? Was it the S=off process or the forced pulling of the battery while the phone was boot locked?
I then took the phone to HTCs warranty center.
They tested the phone and called me back a few hours later. Your eMMC chip is fried they said. Yes, I said, Can you fix it please?
He told me that the eMMc was fried by the s-off tool I had used. Now, maybe he is full of **** and just wants an excuse to void my warranty. And, maybe not.
I told him to go ahead and fix it. He told me it would be a $200 Dollar replacement of the main board. ****. Well, what other choice do I have. Do it, I told him.
Next I got on the phone with the HTC help center. I got friendly with the lady technician on the call. After some nice chat I started probing for information on the Desire S. After a long conversation She told me that the Desire S, Incredible S, Desire HD all have the problem of frying the eMMC chip if the battery is disconnected while power is on. She said she gets calls every day with people who have fried their eMMC chip. Not through S-off but just because the battery came loose and lost contact while the phone was on or charging. The main reasons for the issue are as follows, HTC cheaped out on the eMMC chips in these phones, as the issue is specific to a particular series of eMMc. And because of a design flaw in the way the battery door closes, and because HTC did not include a force shutdown key combination to shut the phone off properly when locked.
So in the end it sounds like a lot of bad design and bad planning and poor foresight on HTC's part led to the fried eMMC on my phone. But they are not willing to stand behind their product and found an excuse to void my warranty and make me pay for the replacement Mainboard.
Now, here is where we get into the debate of should anyone s-off their phone? The main point here is no one should have to s-off. The phones should never be shipped s-on. It's bad policy to lock the bootloader. But having received an s-on phone you may very well want to s-off. If you decide to s-off just remember that you could easily brick your phone by many ways not related to s-off and your warranty will be void.
Another option is to not buy HTC because of the design flaws and their bad locked bootloader policy. To unlock and root a Samsung all you have to do is issue the command fastboot oem unlock. I don't know if Samsung phones also have the eMMc chip issue, so I can't comment there. But I certainly prefer their open policy on bootloaders.
Maybe the whole reason for locked bootloaders from HTC is beacause they are aware that they used sub par eMMc chips and are trying to reduce bricks.
Regardless this experience has made me very dubious of HTC in general.
I hope this is helpful and educational.

Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App

monkey21stc said:
Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Again, thanks for warning.sorry to hear your struggle, disappointed that htc use this tactic, will certainly reconsider buying an alternate make device next time of this issue persists
The volume up plus volume down plus power button combination does work, it's just but published
Very often, although have yet trio try out when the devices has hung, but certainly reboots my device .
Swyped from HTC Desire S using XDA Premium

just fyi in germay they take 184 € to repair a bricked eMMc :-(

Aye, Thanks for Sharing. I'v hade the same problem as you. I'll never buy an HTC phone again. Cheap bastards!

i need to know that every chip is different...bad for u that u got the bad one but i flash phone daily and its ok..i have same procedure every time i do that..to brick phone can happen to experts too...well if u want to risk to get root and all goodies u can say good bay to warranty..thats for sure

thanks for sharing man.
monkey21stc said:
Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
that works on miui

Buy a htc with simlock.
Mine is t-mobile
When I've started my device for the first time, is was already s-off because if I turn my phone on it will show the t-mobile logo
So u can't brick your phone if you will s-off
But thanks for sharing
Next time I won't buy a htc
Sent from my HTC Desire S using XDA Premium App

Just remember though flash memory is extremely volatile, and ripping a battery out of a phone generally isn't a good idea to begin with, although I was lucky to read about the vol up/down + power procedure before I rooted my phone.
Very interesting post, interesting to see the bigger picture behind this issue.

so here's the deal - I am 99.9% sure that the bricked eMMC chip is a problem only in devices with a chip that was faulty in the first place. When the phone first came out, there were MANY threads on the hardware faults like "Battery cover not fitting" and "Misaligned screen". This was an issue that could't be identified easily, so it wasn't reported. Now, many people are having this issue and instead of panicking, we should do some research. I think that all the guys who bricked their phone would be living close to each other, in the same country or at least the same continent ie, this is a local issue. Also, i'm sure they had one of the other issues i mentioned above. I've not seen anyone in India or Asia with any such issues, so i think we need to find out why europe is having problems. Contact the BRICKees, i'll try making a new thread.

^^^.. yes this issue you need to find the Source.. I sold my Desire yestreday to get Hold of the Desire S but my only concern is this Dead eMMC chip.. and that is the reason I am not buying it yet... I want to identofy the ones with this issue..
really I dont want to screw up my 40K Rs on a faulty set..

Got the same problem, accidentally bricked a DS with a faulty Samsung eMMC, barely 3 weeks after buying it and 2 weeks after S/OFF'ing and rooting it... (btw, isn't it strange that Samsung chips that you find in Samsung branded phones don't seem to have this problem, but strangely the chips sold to their competitors seem to always be somehow sub-par ? Clever and sneaky way to undermine the competition, if you ask me. But at the same time, I bought a SGS2 as replacement in the meantime. ^^ even though it heats up a bit, it's way better than the DS )...
Haven't RMA'd the DS yet, I'm trying my damnedest to find a way to S-ON again and trash the remainder of the partition table -so the service center won't gimme **** about it.. So far I've been able to revert back from Alpharev SOFF to PVT ENG SOFF (0.98.2000), but even this has been horribly hard to achieve.. The "secret fastboot command" to totally brick a NAND didn't work, of course. Had to do it all by hand, in the dead of night, losing many hours of sleep in the process.. :/
It's really shameful that HTC is using such deviant ways to cover their own ****ups and to shirk the payment of their dues.. So I really got no qualms about trying to con them into replacing the device under warranty either. "tit for tat", or so they say.. And they shouldn't be surprised if I never ever again buy a phone from them either, that's really bad PR if y'ask me...
PS : I just got one of those mischievous ideas that often occur to me during sleepless nights : I've read here and there about how dangerous flashing a radio is, and it should only be done if necessary, yadda-yadda-yadda... (heck, I was at my 4th radio flash -just for the fun of it, didn't even have any reception or battery problems to justify it- when I bricked my DS, and I can tell y'all that it wasn't what ****ed it up :S)
Let's just imagine -that's a hypothesis, of course- that I attempted flashing a new radio, and one of my cats "accidentally" jumped on the desk and ripped the usb cord away from the phone, making it drop down on the floor, dislodging the battery in the process.. Wouldn't this brick it nice and proper, and render the NAND totally unreadable even for a HTC service center ? xD
I guess they got a XTC device at hand, but would that help in such a case ?

Can someone confirm what exactly is meant by pressing Power and Volume + and - at the same time? Press Power and press both ends of the volume rocker switch at once? Is that it?

first press the two volume buttons and then power until it shuts down.
worked for me at least -I just learned about that trick a trifle too late

your story said that it includes desire HD? wow i didn't know that honestly when my old DHD freezed i always pull the battery out and no problems at all it's just that the constant carmode problem irritated me and ended up selling it and bought a Desire S...not yet rooted and S-Off but will do later...so it's not the S-off process it's the battery thingy...it sucks for that to happen

Thanks for guide. I'm really scare of eMMC chip problems. I never tried to S-OFF coz of eMMC chip problems. Don't wanna to make void the warranty

Thanks for sharing! I have removed my battery a few times already to force shutdown. Don't know if I'll ever try it again. Maybe as a last resort, but at least I know the risks now. Thanks again!
Sent from my HTC Desire S using XDA App

Cool thanks for Sharring
Sent from my HTC Desire S using XDA App

i work my whole life with pc, hardware, software, flashed everything from set-top boxes to mobile phones.
seriously, i can't believe that anybody can fry the eMMC (a ****ing simple NAND-based flash memory) cause he puts SOFTWARE on it - thats what it build for!!!
you can brick your phone if you destroy the bootloader or something without a possibility to fix it, this won't destroy any hardware on your phone - but thats a different story.
the only reason for s-on is to take you the chance to deinstall the bloatware which they pollute their devices.

apairofscissors said:
How I bricked my Desire S - information on avoiding brick and an indictment of the dubious nature of HTC's S-on policy
The Desire S is a great phone so why did I want to root it?
The main reasons for rooting and s-off for me were:
Titanium backup (android built in backup is weak)
Being able to remove bloatware that takes up unnecessary spaces and unnecessarily reduces battery performance.
To try different ROMs from the community
Video screen capture
And of course I bought the phone so isn't it mine to use as I please.
Having waited a long time for a good s-off tool to come out I was getting more and more anxious to s-off.
Alpharev got together with Unrevoked to create Revolutionary.
I had previously used the Unrevoked tool to root my first generation Desire. The tool worked easily and flawlessly even on my Mac.
I later used the Alpharev bootable CD to s-off and root a later generation Desire. Again it worked smoothly and flawlessly.
Having had this positive experience I felt confident in the new tool, Revolutionary.
I read everything I could find about how the tool worked and how others were finding results. All seemed straight forward and uncomplicated so I proceeded to download and run the tool from my PC because there was no Mac version available.
Temp root and s-off went smoothly. No apparent issuse. Both Hboot and Fastboot had been successfully replaced on the phone, and CWM recovery was working.
So I added su in recovery then ran a nand backup of the whole system at this point.
Then I downloaded a Cyan 7 ported for the Desire S that was getting good reviews and feedback. The rom seemed to flash clean. After running it for a short time it stated crashing, so I decided to try an MIUI ported to Desire S. Again a ROM with good feedback and labeled as stable.
Downloaded the ROM and flashed it after a full wipe in recovery.
This time on reboot the phone hung at the HTC screen on boot for a very long time. So I wanted to do a force shutdown.
Here is where things got ugly.
The Desire S does not have a force shutdown keystroke combo as my old Desire did. So I opted to pull the battery.
Reinserting the battery and booting into recovery nothing worked properly.
CWM wouldn't mount its partitions, wouldn't flash a rom or even do a factory reset.
I tried doing some functions in fastboot mode. But nothing worked. Any command issued in fastboot mode would just lock up the phone and terminal.
At this point I was pretty worried so I got on #revolutionary and chatted with some of the big guns. I got some good feedback to test this and try that but in the end nothing worked. So I got on XDA forum and looked for others with similar issues.
What I found at this point was very troubling.
XDA user opumps had the same issue as me and had done some great research about the problem.
http://forum.xda-developers.com/showthread.php?t=1150917
It becomes clear on reading, that like him, my Desire S had a fried eMMC chip. This is the internal storage device for HBoot. Once cooked your are basically F*ucked. There is no recovering from this by reformatting the eMMC. Pooched.
Doing the tests on the XDA post I found my eMMC to be pooched.
Now the question is, What fried the eMMc? Was it the S=off process or the forced pulling of the battery while the phone was boot locked?
I then took the phone to HTCs warranty center.
They tested the phone and called me back a few hours later. Your eMMC chip is fried they said. Yes, I said, Can you fix it please?
He told me that the eMMc was fried by the s-off tool I had used. Now, maybe he is full of **** and just wants an excuse to void my warranty. And, maybe not.
I told him to go ahead and fix it. He told me it would be a $200 Dollar replacement of the main board. ****. Well, what other choice do I have. Do it, I told him.
Next I got on the phone with the HTC help center. I got friendly with the lady technician on the call. After some nice chat I started probing for information on the Desire S. After a long conversation She told me that the Desire S, Incredible S, Desire HD all have the problem of frying the eMMC chip if the battery is disconnected while power is on. She said she gets calls every day with people who have fried their eMMC chip. Not through S-off but just because the battery came loose and lost contact while the phone was on or charging. The main reasons for the issue are as follows, HTC cheaped out on the eMMC chips in these phones, as the issue is specific to a particular series of eMMc. And because of a design flaw in the way the battery door closes, and because HTC did not include a force shutdown key combination to shut the phone off properly when locked.
So in the end it sounds like a lot of bad design and bad planning and poor foresight on HTC's part led to the fried eMMC on my phone. But they are not willing to stand behind their product and found an excuse to void my warranty and make me pay for the replacement Mainboard.
Now, here is where we get into the debate of should anyone s-off their phone? The main point here is no one should have to s-off. The phones should never be shipped s-on. It's bad policy to lock the bootloader. But having received an s-on phone you may very well want to s-off. If you decide to s-off just remember that you could easily brick your phone by many ways not related to s-off and your warranty will be void.
Another option is to not buy HTC because of the design flaws and their bad locked bootloader policy. To unlock and root a Samsung all you have to do is issue the command fastboot oem unlock. I don't know if Samsung phones also have the eMMc chip issue, so I can't comment there. But I certainly prefer their open policy on bootloaders.
Maybe the whole reason for locked bootloaders from HTC is beacause they are aware that they used sub par eMMc chips and are trying to reduce bricks.
Regardless this experience has made me very dubious of HTC in general.
I hope this is helpful and educational.
Click to expand...
Click to collapse
Please change the title of the thread to "how not to brick your desire s". The current one sounds really fun and why any one would want a guide to brick their phone.
Sent from Desire Aj'S using XDA eXtra Premium App!

True Brick...QHSUSB_DLOAD

Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt

Just swayed my decision on wether to root or not.

So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?

Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.

Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.

Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt

Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.

Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.

Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).

Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt

it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.

nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much

vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt

Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?

vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt

Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?

vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2

not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.

Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(

Another dead phone

Hi, I have flashed many different roms with no problems on HD2 and Desire S. This evening I thought I would try another Rom (why oh why), so duly wiped and done the usual preparation, but this time it just stuck at HTC for over half an hour, tried rebooting but nothing, tried all the ways on the forum to restart without taking the battery out, in the end I made the stupid mistake of taking the battery out and putting it back in . Well you know the rest, dead phone fried chip I think.
Now my questions are 1) its on contract from Tmobile 6 months ago, the device is obviously S-off so am wondering if I can still get it fixed by them. 2) How much does it cost to have a fried emmc chip replaced if I send it to HTC.
Any help would be greatly appreciated.

I sent it to HTC without the battery and got a repaired phone free of charge
Sent from my HTC Desire S using xda premium

Hi Dan. Can you tell me the process you went through and is your a contract phone

Can you boot into Recovery or Bootloader? The bootloop can be caused by many reasons, not only eMMC

Hi, can't boot into anything , the phone is just dead, doesn't do anything, no power.

correct me if im wrong but dosnt emmc failure still boot? im not 100% sure thats your problem

Ok, but I tried everything to power up with no luck, I know there was at least 80% battery when I used it, also nothing when I plug it in to the mains.

pandollar said:
Hi, can't boot into anything , the phone is just dead, doesn't do anything, no power.
Click to expand...
Click to collapse
This is a completely bricked phone (whatever the reason that caused it). But in this case the repair cannot state that it is S-Off. So go ahead for a replacement. There is a way to unbrick it (JTAG), but never heard so far that the HTC repair centres use that - all the problematic devices were just replaced, not repaired. Good luck

Ok, I will have to try and get them to replace it then. Many thanks for your help.

amidabuddha said:
This is a completely bricked phone (whatever the reason that caused it). But in this case the repair cannot state that it is S-Off. So go ahead for a replacement. There is a way to unbrick it (JTAG), but never heard so far that the HTC repair centres use that - all the problematic devices were just replaced, not repaired. Good luck
Click to expand...
Click to collapse
This is great..I have two bricked phones lying about that I have no idea what to do with...

virtu0s0 said:
This is great..I have two bricked phones lying about that I have no idea what to do with...
Click to expand...
Click to collapse
Find a person in your area that owns a JTAG, there is a great chance to fix them.

HTC Bootloop. No debugging, Unrooted.

Hi all!
This is new to me so I would like to apologise in advanced for this. I hope I've put this on the right section.
Go easy on me, I'm out of ideas.
Short Story
Unrooted HTC One XL is stuck in bootloop from failed software update. Phone has been in an infinite bootloop since 2013. Phone can be booted to HBoot mode.
Loss of data is not an option. Would rather the paperweight.
Google image of what is visible at HBoot attached. (Not my image)
Long story
I have my mothers HTC One XL (Telstra Aus), I've seen various name versions but this is the one the phones telling me so we'll go with it.
During a software update back in 2013 something happened which in turn messed up the update. God knows what. The phone has been in an infinite bootloop ever since. We had it sent away through our provider (Telstra). They basically shrugged their shoulders and returned it.
My mother couldn't care less about the phone itself, It's the photos.
The phone does not have usb debugging on, Is not rooted, nor can it boot to turn it on. Obviously.
After quickly getting sick of waiting for it to die before trying again the phone has been opened and battery is now "removable".
Cache cleared, reboot, soft restarts....Nothing.
Every year or so I scour the internet looking for a hail mary that may have come along. Dr Fone would be good if it catered to "Broken" htc's not just samsungs.
So I guess my question is, is there by any chance something new has come along on order to either retrieve the photos from the device? Or, different methods in which to get the phone out of its bootloop so the phone can be accessed that way? Without the loss of any data.
Sorry if this is a bit all over the place.
Thank you in advance.