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!
Related
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
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Well if your PC is not recognizing the phone, then there's not much you can try I guess (other then factory reset.) Maybe someone is gonna come up with something.
Aren't the gamesaves on your sd card?
There have been hardware issues associated with multiple downloads from the market and pulling the battery. This might or might not be the case. However you are covered with warranty in case it is.
Sent from my HTC Desire S using XDA App
esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
If she created a HTC Sense account and had set it up to sync then her texts would have been saved online.
If no other options download the corresponding to your region RUU (ROM Update Utility) from here. Then reboot to Bootloader (VOL DOWN + POWER Button). Make sure that you have HTC Sync installed. Go to fastboot screen (you should see FASTBOOT USB line). Start RUU.exe. It will handle everything automatically and hopefully you will have a brand new Stock system again.
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
olyloh6696 said:
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
Click to expand...
Click to collapse
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
An boot loop isn't
an real indicator for fried emmc, most of the times you just somehow messed up part of the software or the partitions, this:
http://forum.xda-developers.com/showthread.php?t=1292730 it's an really fried emmc.
Let's try some solutions before destroying any hope!
Swyped from my Desire S
amidabuddha said:
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
Click to expand...
Click to collapse
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
so, have you tried hard reset/factory reset. let us know what happen than. next time never pull out battery when your phone freeze. just press vol up + vol down + power button (all three hardware button) and the phone will restart. I personally had this problem few times and able to recover my device. start with hard reset your phone.
look at ben_pyett signature. you need the adb+fastboot and htc drivers for your windows pc to detect your device. I'm using linux and I don't need those drivers.
olyloh6696 said:
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Update: thanks for all the suggestions. I couldn't get any of it to work, including factory reset.
We are going to send the phone in for a warranty repair, most of her personal stuff is on her Google account or the SD card, so no major problems.
The HTC Sense website with SMS backup never worked for her, there is no option to log in from the phone.
As much as i love Android I am shocked that hitting "update all" in the market and/or pulling the battery can brick a 400 $ phone. Even buggy old Windows ME was fine if you pulled the pover cord.
My iPhone friends will laugh at me well into 2012 if I tell them this.
Do HTC have more faults than other brands? Both our Desires have had trouble. I am about to upgrade mine, maybe should look at another brand?
There is some hope!
amidabuddha said:
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Click to expand...
Click to collapse
+1
I'm afraid that I must agree.
In the early days of this problem, I too was probably guilty of announcing too early to users "that's you've fried your eMMC chip - that's a warranty return" where as over time we've now come to believe that this still a chance of hope, albeit not great or guaranteed, but none the less, fortunately several people have managed to recover from this situation, by a variety of means.
So even though the possible outcome might not be likely, I think that we should attempt to always suggest that there might be hope at least until we've tried all the possible solutions and now luckily the various users have compiled guides of the suggested options so this isn't that difficult.
The only time when I'd suggest that a user should probably instantly return a device, is if they are completely non technical or have a brand new device which is still S-ON. In which case they may as well return the device under warranty and get a replacement device or motherboard which will at least contain the non dubious/faulty chip, and will remove the possibility of future occurrence completely - so they'll actually be better off for the future!
esbenm said:
Update: thanks for all the suggestions.
Click to expand...
Click to collapse
Sorry to hear this. You were just unfortunate and what happened to you is rare, also it's not a fault of Android but, a HTC eMMC chip hardware issue caused by a particular dodgy version of the eMMC chip that comes on some of these phones.
I believe that HTC realised the fault and replaced the chip with another make after a fashion. So hopefully you'll get the different chip on your replacement device/motherboard.
I also think that they've changed the market application so that it downloads one application after rather than all the applications together, which was known to cause a device freeze, which often was followed by a battery user battery pull - which then led to this problem.
Next time... Never pull the battery! there are always other options.
Take care and good luck.
Hey folks,
I am experiencing big trouble with my phone. When I was updating apps over the market, my phone froze and i had to remove the battery. Since then, my desire s is stuck at the htc logo. i can start the bootloader but selecting "factory reset" causes the bootloader to freeze.
my phone is S-off with alpharevX and rooted, so i think htc won't accept it. i was using virtuous unity 1.27 .
installing a new ruu doens't function also, its stuck when ruu says "restarting bootloader" .
i don't know what to do, it would be great if someone could help me!
Thanks a lot!
morial said:
Hey folks,
I am experiencing big trouble with my phone. When I was updating apps over the market, my phone froze and i had to remove the battery. Since then, my desire s is stuck at the htc logo. i can start the bootloader but selecting "factory reset" causes the bootloader to freeze.
my phone is S-off with alpharevX and rooted, so i think htc won't accept it. i was using virtuous unity 1.27 .
installing a new ruu doens't function also, its stuck when ruu says "restarting bootloader" .
i don't know what to do, it would be great if someone could help me!
Thanks a lot!
Click to expand...
Click to collapse
Search for eMMC chip. Sounds like another case. There are several threads with things to try, but if hboot ain't playing ball then sounds like its worth attempting a warranty repair.
Of course, forget to mention you rooted. There is a chance they won't test for it. Else it'll be a repair bill.
Sorry to be the bearer of bad news.
Sent from my HTC Desire S using xda premium
update
even when i try to get into "recovery mode" theres a white scrren with a htc logo. dunno what to do anymore :-(
mate, follow the thread on advice to return your device in a case of a fried eMMc chip... it may help!
Good luck!
morial said:
Hey folks,
I am experiencing big trouble with my phone. When I was updating apps over the market, my phone froze and i had to remove the battery. Since then, my desire s is stuck at the htc logo. i can start the bootloader but selecting "factory reset" causes the bootloader to freeze.
my phone is S-off with alpharevX and rooted, so i think htc won't accept it. i was using virtuous unity 1.27 .
installing a new ruu doens't function also, its stuck when ruu says "restarting bootloader" .
i don't know what to do, it would be great if someone could help me!
Thanks a lot!
Click to expand...
Click to collapse
Very sorry to hear that brother.
Sounds like a dead eMMC to me...
Didnt you read about battery pulling on this forum? Its spread across everyone's signatures for God's sake! I know there's no point stressing on this now but this may serve as a warning to others and help them...
As for Morial, i'd suggest you simply take your device to HTC and tell them you were updating all apps from the market, (DO NOT EVEN TALK ABOUT ROMs, BOOTLOADER, RECOVERY, etc) and it froze, so you had to do a battery pull and now it won't start.
HTC knows this is an acknowledged scenario even on s-on phones and usually just replaces the handset or the eMMC depending on availability, without asking questions. Just go to them like they owe you, not the other way around!!
Again, do not even speak about modding, flashing etc. Just pretend you have the I.Q. of an iPhone owner. That should do the trick.
P.S. iPhone owners, no offence intended.
^^
i brought the desire s today to a local electronic retailer who will send the item to htc. hope they don't recognize that its rooted.
i wasn't browsing xda-developers for about 3 months, so i didnt know about not pulling the battery
anyway thanks for your answers, very nice folks around here!
morial said:
i brought the desire s today to a local electronic retailer who will send the item to htc. hope they don't recognize that its rooted.
i wasn't browsing xda-developers for about 3 months, so i didnt know about not pulling the battery
anyway thanks for your answers, very nice folks around here!
Click to expand...
Click to collapse
@Morial, best of luck.
I'm pretty sure you'll get a brand new replacement set!
How long before you hear from them? Did the retailer commit to any timeframe?
dunno, they say it can last about a month. i`ll tell you when i hear from them
Sorry to hear what happened here.
I had a similar issue myself recently here http://forum.xda-developers.com/showthread.php?t=1257772
Hopefully they will repair it without checking it properly like I suspect they did with me. I pulled my battery out without knowing the eMMC problem too.
When I sent my phone back to HTC they told me that the only way it wouldn't be covered under warranty was if it had been water damaged.
Good luck
bad news
htc said my phone isn't under warranty anymore because of a small damage on the edge of the phone, so they sent me an email in which they proposed to repair it for 210 euros. i think this is ridiculous - my next phone surely won't be an htc-product :-(
morial said:
htc said my phone isn't under warranty anymore because of a small damage on the edge of the phone, so they sent me an email in which they proposed to repair it for 210 euros. i think this is ridiculous - my next phone surely won't be an htc-product :-(
Click to expand...
Click to collapse
That sucks! How can they do that??
What small damage was on your phone?
Sent from my HTC Desire S using xda premium
Hi
It happens exactly the same thing yesterday. I updated applications on the market. My HTC has had a lag and when I restarted ... He stuck on the start screen.
Is it possible to reinstall the ROM?
I never install Custom ROM before...
I test that night to install "Clockworkmod Recovery v3.2.0.0"
I rename in "PG88IMG.zip"
I start the bootloader and he do :
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading... [PG88IMG.zip]
Checking... [PG88IMG.zip]
But he doesn't propose me to install it...
Information :
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.6.02.03_M
eMMC-boot
Mar 30 2011,17:29:31
Is it a problem from my HBOOT version ???
Since when did having some small damage on the corner of the phone void a warranty !! Confused...
Sent from my HTC Desire S using XDA App
they said that my software failure could be a result of letting the phone fall on the ground. so they cannot say which was the cause for the phone to not boot anymore - letting it fall as the y suggest by the damage on the phone or the market suicide.
i am pretty disappointed by htc. i guess i won't buy a htc phone anymore :-(
morial said:
they said that my software failure could be a result of letting the phone fall on the ground. so they cannot say which was the cause for the phone to not boot anymore - letting it fall as the y suggest by the damage on the phone or the market suicide.
i am pretty disappointed by htc. i guess i won't buy a htc phone anymore :-(
Click to expand...
Click to collapse
That's is terrible. Shame on HTC.
Sent from my HTC Desire S using xda premium
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.
I wanted to start a thread for those of us that have bricked our Sensation by formatting the SD card while using a AOSP style or AOKP ROM.
Let's use this thread to collaborate ideas and ways to possibly un-brick our devices.
What we know
-Formatting the SD card in past versions of AOSP and AOKP caused the device to "brick" due to possibley reformatting the NAND memory or at least the eMMC partition.
-Our devices are unresponsive and are only recognized by a PC in "download mode"
-AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device(Thanks to T-Macgnolia for this explination)
-Only hope may be to try JTAG and RIFF box.
So let's try a think tank and see what happens. If you have any experience with JTAG and RIFF Box PLEASE put in your 2cents.
I am willing to tear my Sensation apart and go at it with a RIFF box since I just ordered a Galaxy Nexus from Google.
I will start researching JTAG and RIFF tonight, but I figured some one should start a thread like this to clear up the HTC Unbricking Project thread.
You got two thanks from me for this, one here and one in the Unbricking Project thread in the development forum. I am like you I can see this subject clogging up the Unbricking Project thread, so this is a good idea here if members will just use it.
Now as for how to revive devices that fall victim to the awful bug that was in the AOSP and AOKP ROMs. I truly hate that such a bad bug was not noticed before so many had fallen victim to it. I also hope someone or a group of someones can come up with a working solution. But from my knowledge JTAG will more than likely be the only option to revive these devices. I hope I am wrong though. Best of luck to all of you.
I don't know much about JTAG at this point, but if it's the only way I'm willing to go for it and share my experience. As it stands now, my Sensation is just a nice expensive paper weight, so I'm not afraid to tear it down
Well best advice I can do is tell you to start eoing searchs on Youtube. Here is a link to the only video I have found on the Sensation so far. You will need to try to find s video that shows the tear down process that will get you to the point the video I linked shows. But at least the video shows the proper way to attach the JTAG and external power supply. I suggest you aleo see if you can not get in touch with josh from Mobile Tech Videos as I know he can give you some very sound advice on JTAGing a Sensation, or just about any other device for that matter. He is known as connexion2005 here on XDA. It also might not hurt to drop ole AdamOutler a PM asking if he has any advice or input.
well im in this boat with my bricked sensation xe, im taking my phone upto http://www.fonefunshop.co.uk/ on wednesday to get it jtaged with the riff box.
but on some good news, if you read the updates on the riffbox it says it can jtag a htc phone via usb (without opening it) but you need a riffbox plugged in to open the software... so if someone could make a hack to open the software without the box connected you might be able to flash the phone
http://www.jtagbox.com/
Guys,
I'm going to RMA my phone with HTC (i got the SD card brick format issue with AOSP)
Assuming the whole of the internal memory got wiped - HTC cannot tell anything can they? So they should repair it with no hassle?
Any advice is appreciated.
just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?
I want to confirm that jtag solution works ... I bricked my phone and now its back to life
I am not the one who actually done the jtagging thing, I will ask him to post a tutorial here on how to do it step by step ...
heavy_metal_man said:
just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?
Click to expand...
Click to collapse
The latest Open Sensation builds have that problem corrected, check the change log for more details.
Swypesation
szunyimen said:
Hello pplz,
I just wanted to let you know about my story:
I had lots of unused crap that was left behind by different ROMs and APPLICATIONs on my sd card, so I used this app called SD MAID.
Then when my phone's battery dead that day, the phone turned off and I could never revive it...
I had AOKP rel 34, the one just before milestone 5.
SO probably that was the cause of the brick.
BE CAUTIOUS with any kind of sd card related app on AOSP/AOKP!!
Click to expand...
Click to collapse
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...
It seems like JTAG w/ RiffBox is the only way....boooooo.
Does anyone have or know someone with a box, or at least where to get one???
Alipk52 said:
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...
Click to expand...
Click to collapse
I don't really know what happen to Alipk52's Sensation. But I can tell you this, the bug that was in the AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device. Now with the internal memory formatted this means you have no bootloader which means the device can not boot, which means brick. So yes the SD card format bug did cause bricking.
Hi!
I've read about jtagging withot soldering but via usb cable. So, maybe someone will compile the software emulator of riff box presence...
I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2
kmmxracer said:
I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
they will replace the board.
szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
Sending your phone somewhere out whitout knowing the person ? Pretty risky.
Sent From My Sexy Sensation Running Aokp.
szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
The problem you had was not the one described in this thread, and I would put money on him not using JTAG on it at all. I find that often if I let my phone battery die completely it will not turn back on, even if I leave it on charge.
I have to charge it up a bit, unplug it, turn it on, then plug it back in again.
http://forum.xda-developers.com/showthread.php?t=1205983
i think this guy was on to something. if we could create a generic copy of the sensation using this program, with imei and other sensitive things removed and then flash it back using that program. thoughts?
I would just like to offer my Sensation as a sacrifice to the cause. It's bricked either because of the AOKP SD brick or failure to update to the ICS radio before upgrading from 2.3 to 4.0.
Sent from my HTC Sensation using Tapatalk 2
Not updating the firmware only causes bootloops, not a brick.
You'll know if it's proper bricked as it wont even charged.