Database Info

[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!

[Q]Serious Problems With HTC Sensation[Q]

Okay, so I guess these problems may not seem serious to you, but they really do to me.
I'm on my third Sensation in two weeks. Ridiculous, I know. My local Orange store seems to have received a 'bad batch'.. yeah right, more like their software messes the phone up. Anyway I'm having problems with S-off'ing.
The first two Sensation's I recieved from Orange, had *Bootloader Locked* on the HBOOT, however this one does not have that at all? It doesn't say anything about a locked or unlocked bootloader at the top of HBOOT.
The problems first started when I attempted to S-Off. I have ALL my drivers installed and do not have any interrupting applications. Revoloutionary manages to complete all steps however on the 2/3rd time rebooting the bootloader it suddenly losses connection with my phone. It manages to root and everything, but then it will loose connection at this point and there seems to be not a thing I can do about it.
I have no idea how to fix this situation, I don't want to run a custom rom, I just want to be able to run a stock de-branded phone with S-ON!
Also, I was wondering if I S-Off, install Stock HTC Software, then S-On again will I be able to recieve updates OTA?
Thnaks XDA.

[Q] Locked display spontaneously turning on - UNSOLVED

Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks

Pride4u said:
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Click to expand...
Click to collapse
Does it happen on any other ROM, or only on Endymion? Have you tried Reaper and tried to reproduce the problem there?

I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.

Pride4u said:
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Click to expand...
Click to collapse
Why use Unity kernel with Endymion when Endymion kernel is excellent on the ROM by itself?
I would suggest you try another ROM like Reaper and see if the problem persists...

Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.

Pride4u said:
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Click to expand...
Click to collapse
Why I asked you to try another ROM is because if my hunch is correct, you have a hardware problem... I just didin't want to say it till we had ruled out the software issue. This is the exact same thing that happened to my wife's phone a month after purchasing it (Desire S) and HTC put it down to a hardware problem (mainboard) and replaced the device free of cost under warranty (wife never allowed me to touch her phone, so it was S-on, stock!!)
I hope you don't have the same problem, but it sounds exactly like the problem my wife's phone had... the only way is to flash another ROM and see if the issue persists. Make a nandroid backup. What have you got to lose?

What I've got to lose is the time spent, but I guess I have no other choice so I'll get around to it as soon as I find the time.
If it's HW problem I may encounter some trouble as I've bought the phone from an e-shop that sells unofficially distributed phones because they offer considerably lower prices, although it is true that the customer service and complaints may be rather poor.
I'd have to send the phone to them and wait like a month or so until they finally decided that my complaint wouldn't be accepted :-D Not to mention that I would have to unroot the phone and change it back to the S-ON setting.
Anyway, let's hope for the best.

Shameless bump - I'd like to ask a question about Titanium Backup.
I've backed up my installed apps but would like to know whether it will be OK if I back up the system and user data - I don't if it matters that the data will be from a different ROM - in other words, if the system structure doesn't change.
For contacts backup Google sync will be the best I guess.
EDIT:
Installed Reaper 1.6 and the problem is gone. I lost some data in the process as Titanium backup didn't back up the notes from Endymion HTC Notes, never mind, though.
EDIT2: EPIC FAIL! I was probably just unlucky not to see the phone flashing for a long time but today I've seen the screen turning on of its own accord again. Repair service, here I come! :-(

Won't turn on and no charge light

Just sent my HTC Sensation off for repair under warranty due to this fault :
Running OpenSensation nightly 20120810 and TamCore 3.0.40 without any issues and updated the nightly every 2-3 days with no issues. had the phone 12 months and had it s-OFF and unlocked about 4 hours after buying it. At that time running CM7 as that's all there was, updated to various ROMs until I settled on OpenSensensation (tried CM9 a couple of times for a few days but prefer OpenSensation). All ROMs installed fine over the past 12 months
Installed Kingdoms and Lords off Google play (huge game 200MB data download via wireless), after first game phone froze and reset. So I reduced the overclock, game running fine. Had another game later on in night playing for about 15 minutes. Phone froze again, switched itself off and didn't come back on again !!!!
Tried charging it thinking battery was flat, no charge. Took battery out as it was an Anker 1900mah just in case it had blown. Put original HTC battery back in, no charge light, nothing. Took battery out and left it out 2-3 hours as suggested on 'net as it 'might' help
No charge, tried another USB lead plugged into desktop. Still no charge .... oh crap
Took to T-Mobile shop I got phone and explained situation, forgetting to mention it was running custom ROM, they tried. Still no charge, no reaction in shop. Zero, zip
They sent it off for inspection/repair yesterday under warranty and said it should take 2-4 weeks
It had been running custom firmware since the day I got it on contract and has never caused me any grief, apart from some roms running better than others while I made a choice which ROM to stick with
Question I'm asking is can HTC still test the phone even though its not taking a charge or I assume not powering and just froze and died, assuming the motherboard is fine does anybody know if they use test points that bypass the USB socket to power it up
And how can just playing a legitimate game downloaded off Google Play freeze the phone and shut it down never to power up again
I'm guessing the possibilities of a faulty USB charge socket, faulty power switch or fried CPU/GPU/motherboard considering it just froze and died
I used it as a phone but did play games quite a lot during the day when I had a few minutes while not working, and had it overclocked to around 1625-1728 which it ran stable at without overheating
If they send it back refusing to touch it due to finding custom firmware on it I'm looking at the Samsung galaxy SIII over the HTC Nexus One simply because the Samsung has a removal battery and additional microsd card slot where for some reason I assume is to make rooting more awkward the HTC has a hardwired battery and NO extra sim card slot. I was looking to replace it when my contract expired in February but if they refuse to fix it citing custom firmware (even though it has been working perfectly for 12 months running various custom firmware) I have no real choice but to buy out my contract and get a new contract. Bummer

Hmmmm,
Reading a few postings it appears there is a possibility that the motherboard is fried somehow, or a 'hard brick' through a bad ROM install ... I wasn't updating and firmware, not updating any ROMs
Just playing a game downloaded and installed off Google Play, but if it means the motherboard is fried then at least it means HTC will have to replace it as 'faulty' so saving me the upfront cost of buying out my contract thas has 6 months to run

Actually if you overclock the device or flash a kernel htc doesn't have to replace anything.. by "playing a game downloaded from google play" you mean "playing a game downloaded from google play on a device controlled by custom drivers which clearly make your device out of warranty". So I'm not sure.. altough it's possible that it's not the fault of the kernel but the mainboard had some issues. They are able to test the charging port and the main board seperately. Let us know abouth the end.

It would interesting to see HTC's response either way so I'll report back once they have a look at the phone
As I don't have a loan phone at present so have no phone until they get one back from customers having their phone repaired, I have to use the 'net to check on the status of the repair via the T-Mobile website

I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with

thescrapyard said:
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
Click to expand...
Click to collapse
for replaced mother boards ..there is a different version of jb ..check my soff guide ..link in my signature

Will let you know how it goes, thanks

Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far

thescrapyard said:
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
Click to expand...
Click to collapse
for flashing eng-hboot aka changing from LOCKED to Juopunutbear
check the troubleshoot point #3 solution in my soff guide ..its explained there
and for thanks ..there is a button to say that

All sorted, now running the latest nightly of Kanga JellyBean 4.1 and full rooted and back to how it was before the motherboard dies, apart from running Android 4.1
Also feels much smoother and much faster, even though its only running the default slight overclock that Kanga sets as teh default, so might leave it at that as it feels faster than previous when running OpenSensation 4.03
Great stuff

GG HTC One X

So, here's my situation:
I have a HTC One X that is currently on Straight Talk.
Since Straight Talk doesn't push updates through the BYOP program, I called ATT and asked them what I can do to get the JB 4.1 update.
They told me to get it off the HTC website and do it myself and stuff like that.
So, downloaded HTC Sync Manager, ROM, everything.
Ran the ROM, it installed, everything was lookin' sexy.
Well, everything was working very sexy as well until my phone randomly reboot.
I was like dafuq, thought it must have been a tiny glitch, so didn't pay that much attention to it, until it reboot randomly again 10 minutes later.
This time, however, it didn't get past the ATT logo, and it reboot again. I tried getting it into bootloader, did that, and wiped the phone through bootloader.
Everythin' going dandy, then another random Reboot.
HOWEVER, this time it was just stuck at the HTC logo, and then turned off. Unresponsive. Zero. Nada.
Soooooo. now I have a HTC One X, that's unresponsive, as if the battery is completely dead.
THING IS THOUGH: When I plug it into my computer, it does the ba-dum sound, followed by a da-da-da right after.
Checked DM, apparently it's QHSUSB_LOAD now with an Error 28.
I read on other forums that apparently you have to have S-off to do even a normal update?
How come HTC didn't have it on their website?
It didn't say sh*t on installation windows either about having s-off.
Kinda like someone giving you cake and saying "Oh yeah lol, I **** in there"
Phone is bricked, no doubt, looking for a JTag around my town and Craigslist atm as well, but just wondering, is there anything else that it could be?
I'm 19 and I'm desperate to have my NoLifePartner One X back.
kthxgaiz<3

If you had never rooted the phone or unlocked the bootloader you can install an official update no problems.
The whole "must be s-off" thing is for people who have rooted, and therefore have SuperCID. If you have SuperCID and run an official update while s-on, it will brick.
So if you had never altered your device, you should have been ok. In saying that, these official updates have been known to brick stock phones from time to time.
So, if you had a stock phone and ran the correct update and it bricked your device, that should be covered by warranty I believe.
Sent from my Evita

QHSUSB_LOAD after running the 3.18 RUU means you are bricked.
As mentioned in the previous reply, S-off is not "supposed" to be a requirement for running the RUU. For some reason not completely understood, the 3.18 RUU (and folks also report for 3.17 RUU on some other carriers) and OTA will brick the phone if it is SuperCID and S-on. So S-off (or alternately changing back to the AT&T CID) is the workaround. This was not the case with previous RUUs (SuperCID and S-on was fine). In any case, if the phone was SuperCID, it was a user modification, and HTC is under no obligation to inform you that it can brick the phone.
If you didn't have SuperCID, than its possible the RUU just bricked the phone randomly. Its happened to a small minority of people. Anytime bootloader or radio is modified/updated, and things do go quite right, you stand a small chance of bricking the device. In this case, you should be covered under warranty if the phone is less than a year old.

What if I bought the phone used from a store in my city, and the 'void' stickers have already been altered..?

UserNamesTooMainstream said:
What if I bought the phone used from a store in my city, and the 'void' stickers have already been altered..?
Click to expand...
Click to collapse
Your screwed

P_Dub_S said:
Youre screwed
Click to expand...
Click to collapse
And not by a 5 ft 7 120 smoking sexy dirty blonde lookin for a rebound...
:thumbdown::beer::beer:
Sent from my HTC One XL using xda premium