Database Info

Total brick... can AT&T tell

O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?

sell the phone as is (bricked) and buy new?
I am running leedroid as well... (I read your post) and I didnt even fool with anything more than installing the ROM.... I tried the radio flash through ROM manager gtg download section, but it didnt work.. you know I have great data speeds and good phone quality, I'm not gonna risk bricking my phone because I wann "try" to get better speed.. when infact it might get worse..

I remember back in my g1 days people used the excuse that they was updating the phone and it got stuck..maybe that will work since there is an update still going around
Sent from my quietly rooted Inspire 4g running MIUI 1.4.29v2

boufa said:
O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?
Click to expand...
Click to collapse
just bring it in tell them you was doing the OTA update and now it won't boot up or anything

boufa said:
O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?
Click to expand...
Click to collapse
Really? Far as I know ROM Manager only sets up partitioning for SDCARDS, not the device.
Can you point me to the other threads that discuss this in more accurate detail, because I can't find them with my evidently feeble search ability?

Its in desire HD forum somewhere, supposedly koush fixed it with the new clockwork recoverys, but there is LOTS of bricks in that thread. I think he was using an old script for repartitioning, and it was calling the wrong partitions to repartition. I believe it was supposed to repartition the external SD which would be dev/block/mmcblk0 on a g1 or older phones, but on our phones that happens to be internal flash memory, which results in unrecoverable brick.
Edit - here's the link
http://forum.xda-developers.com/showthread.php?t=1043160

di11igaf said:
Its in desire HD forum somewhere, supposedly koush fixed it with the new clockwork recoverys, but there is LOTS of bricks in that thread. I think he was using an old script for repartitioning, and it was calling the wrong partitions to repartition. I believe it was supposed to repartition the external SD which would be dev/block/mmcblk0 on a g1 or older phones, but on our phones that happens to be internal flash memory, which results in unrecoverable brick.
Edit - here's the link
http://forum.xda-developers.com/showthread.php?t=1043160
Click to expand...
Click to collapse
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...

I bricked my Aria trying to flash a new Rom. Since it was still under the limited warranty, I called HTC. They give you a tracking number, you send it in, and they diagnose it. If it falls under the warranty then they repair it free. Otherwise if there is water damage or physical damage they'll tell you the cost to repair it or you can just have them send it back to you with no repair, but with a $39 charge. If your Inspire does not turn on at all then you should have no problem getting it repaired. Good luck
HTC customer care depeartment
1-888-354-2375
M-F 8am - 8pm EST
Sent from my Desire HD using XDA App

tweaked said:
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...
Click to expand...
Click to collapse
Instead of trying to return the phone, why doesn't the OP find someone locally who he can pay to fix it? I had a similar screw up last fall, when I was trying to root my Droid X. I found a "for real" cell phone repair man and he fixed it for me. Cost me $40.00, and the guy gave me a finger wagging lecture on the dangers of rooting your phone. Since I had by that time figured out what I had done wrong, I took the repaired phone home and rooted it correctly, and it's still running fine today.
There *has* to be a shop or a person in the same city as the OP who can fix that phone for a fee, and that's the better solution. Yeah, it costs money, but it's also a case of "You broke it, YOU fix it".
-Mike

Ultra Droid said:
Instead of trying to return the phone, why doesn't the OP find someone locally who he can pay to fix it? I had a similar screw up last fall, when I was trying to root my Droid X. I found a "for real" cell phone repair man and he fixed it for me. Cost me $40.00, and the guy gave me a finger wagging lecture on the dangers of rooting your phone. Since I had by that time figured out what I had done wrong, I took the repaired phone home and rooted it correctly, and it's still running fine today.
There *has* to be a shop or a person in the same city as the OP who can fix that phone for a fee, and that's the better solution. Yeah, it costs money, but it's also a case of "You broke it, YOU fix it".
-Mike
Click to expand...
Click to collapse
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.

tweaked said:
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.
Click to expand...
Click to collapse
LOL! I need to clarify something - I wasn't trying to direct any criticism towards you or any of the other posters, I just hit "quote", and yours was the last post. The thing that gets me personally upset is the people who post on this and other forums, saying that their rooting or ram installation froze their phone, they think they bricked it, and now they want to give it back to AT&T or Verizon and claim it's defective.
Nowhere is there a *hint* of "can someone help me find a shop in Baltimore, Maryland who I can pay to fix my phone?" - not a thought of "Well, *I* screwed up, so I guess this is going to cost me some money to fix". They seem to feel that rooting their phone (which voids their warranty) falls under an "accepted use" exception and that the service provider is obligated to give them a new phone for free, in a kind of "do over".
When I bricked my Droid X last fall, I knew that I'd screwed-up big time, but it never entered my mind to take it back to Verizon and claim it was a defective phone. The thing was fine out the box, Verizon and Motorola didn't screw up, *I* did. But that's just me, and where I'm coming from.
-Mike

Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App

tweaked said:
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.
Click to expand...
Click to collapse
Haha def from BFE Oklahoma haha...
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel

mattmiller said:
Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Do you have a link or any odin reference info
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel

Ultra Droid said:
...The thing was fine out the box, Verizon and Motorola didn't screw up, *I* did. But that's just me, and where I'm coming from.
-Mike
Click to expand...
Click to collapse
You're speaking of a concept that is all but lost these days, that being personal responsibility. It's big brother accountability was killed same 10+ years ago.
Folks don't like when the consequences of their choices bring an undesired result. I could go on and on bu I'll end the beginnings of a rant right here.
Tx

Go to the vibrant forums,look in stickies.
gchatt10 said:
Do you have a link or any odin reference info
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel
Click to expand...
Click to collapse
Sent from my HTC Desire HD using XDA App

mattmiller said:
Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Well, that's my point - there was no indication that the OP made any effort what so ever to fix it himself, or to pay someone to do it, if he couldn't. It came across as "Damn! Well, back to AT&T for a replacement." Personal Responsibility...
-Mike

Some people in this thread give me hope. Personal responsibility is all but lost these days and its good to see people offer good suggestions. Mine would be follow the golden rule. Trust me when I say no one hates ATT more than I, but still. Not saying anything about the op, just sayin.
Sent from my Desire HD using XDA App

tweaked said:
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...
Click to expand...
Click to collapse
Lithium Ion batteries have pre-programmed circuitry in them that measures the range of current. If current outside of the pre-programmed range is introduced, it simply will not charge.
So...with that said, the only way to make this method work, is to use...say...a car battery charger. Something that will spike the current at least 5 to 6 times higher than that of the battery. Otherwise the circuitry in the battery will simply stop it, and allow it to "pass-through."
Now...while we are on the subject of fraud and "frying" electronics... Put it in a microwave for LITERALLY 2 seconds. Anymore than that, and you WILL be caught once the device is inspected. This is not enough to melt any circuitry on the phone at all, nor harm anything physically. The microwave essentially is like hitting the device with an EMP. ;-) (EMP = Electro Magnetic Pulse)

tribalartgod said:
Lithium Ion batteries have pre-programmed circuitry in them that measures the range of current. If current outside of the pre-programmed range is introduced, it simply will not charge.
So...with that said, the only way to make this method work, is to use...say...a car battery charger. Something that will spike the current at least 5 to 6 times higher than that of the battery. Otherwise the circuitry in the battery will simply stop it, and allow it to "pass-through."
Now...while we are on the subject of fraud and "frying" electronics... Put it in a microwave for LITERALLY 2 seconds. Anymore than that, and you WILL be caught once the device is inspected. This is not enough to melt any circuitry on the phone at all, nor harm anything physically. The microwave essentially is like hitting the device with an EMP. ;-) (EMP = Electro Magnetic Pulse)
Click to expand...
Click to collapse
Yeah, a car battery charger. What other kind of battery charger would you attach to bare stripped wires? Lol

Sensation bricked.. I think anyway

My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....

Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?

anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt

Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App

mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char

If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App

Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.

I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.

Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt

Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.

As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.

blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt

happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck

Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino

blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....

actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.

Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.

anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?

So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium

[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 :-(

qhusb_dload brick after bad vold.fstab edit

Sorry if this is the wrong place to post - just wanted to share my unpleasant experience.
I've bricked my phone in a peculiar way - it appears to be a hard brick, non-responsive to any buttons. Plugging in to the computer gets me the dreaded qhusb_dload QPST download mode. Not a good sign.
It wasn't due to faulty ROM flashing, either. I made a bad edit to /system/etc/vold.fstab fiddling with the way the internal and external SD cards get mounted - mmc1 instead of mmc2. After one reboot, I had some sd card corrupted errors. Proceeding to format the card may have been my fatal error. By the second reboot, I was bricked. D'oh. I imagine I had accidentally mounted a partition of the internal emmc that is critical to normal operations, then tried to wipe it.
From what I've read, a USB jig won't do much good, but it's worth a try.
Anyone messing around with their /system folder, be warned.

That's sux, but on a good note, $50 and a little waiting will get your phone back, or you could just warranty that sucker ;-) give more refurb units to some other xda members lol

I sense another refurb sale on ATT.com. Sorry to hear about that, sounds bad. No guts no glory right?

I purchased this as a refurb, too. The cycle continues...
Not sure how the whole exchange process will work in this case. I mean, I can exchange for a different phone, or a new Skyrocket and pay the difference, but I really had my heart set on a cheapo skyrocket. Perhaps if I take this up with Samsung instead?

Ur 90 warranty is over already? That sux then. I personally would pay $50 and get it de-bricked, its the cheapest/best option.

I didn't expect much in the way of warranties because I purchased this refurbished. With Samsung customer service I didn't have much luck. However, I just got off the phone with AT&T, and they're overnighting me a replacement, which is cool. They have a 30 day policy on any web store items, so I'm covered. Anyways, lesson learned

check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351

RussianBear said:
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
Are you in thw process of bringing that to the skyrocket?

silver03wrx said:
Are you in thw process of bringing that to the skyrocket?
Click to expand...
Click to collapse
we need all the help we can get. just a bunch of curious noobs, ya know
the main discovery we did with sensation was to make the emmc visible to any pc it's connected to, then overwriting whatever was messed up (like the hboot) with a stock version of that file.
in theory, you should be able to do this to any phone running on a qualcomm chipset once it's in the qhsusb_dload mode. still lots to test, but anyone is welcome to participate, of course!

Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.

silver03wrx said:
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
Click to expand...
Click to collapse
nope, just sensation. they both run on a qualcomm chipset though, so i'm just speculating here.
the bricks we're "saving" right now are for people that executed s-on without fully reading the instruction, thereby leaving them in qhsusb_dload mode. your cases might be specific to a different area, but the principal is still the same:
find what is messed up and replace it with the correct file via open emmc

Big progress made for APQ8060 and MSM86xx processors. Sensation hard brick solution coming very soon and SkyRocket/T-Mobile Galaxy S II solutions already solved...

What's this I smell? Possible de-brick
Sent from my SAMSUNG-SGH-I727

I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also

amnher said:
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
Click to expand...
Click to collapse
i have the same problem xperia miro
any updates ?