Related
So my TP touchscreen stopped working, and even when I re-booted the stock ROM from HTC, there was no action- I was stopped at the calibration screen. I sent the unit back to Expansys, and I received the following reply.
"Greg,
Hey my repair centers exact words were that the device was upgraded illegally. Thus why the refusal to repair under warranty. The charge is to put back to all factory settings. basically they have to replace the guts of the unit.
Thanks,
Joe Bunch
Customer service Supervisor"
I paid almost $1000 for this phone, and the touchscreen gave up the ghost, now it is the OS smoking the hardware?
Any input would be helpful, as I'm really not sure how this plays out.
Greg
Get the phone back and put everything back to stock like spl and and stuff i had the same problem with my fuze when the screen stopped working i tried my best in guessing and flashed stock rom and stock spl BUT i messed up with the SPL because i forgot to read the directions properly and my device would not activesync any more so i took the risk anyways and sent it to HTC directly since i am not with ATT i cant get a device replacement from ATT. i just got my phone back about 4 days ago and HTC installed a new screen without any problems.
Thanks for the help. Can I send it directly to HTC instead of to Expansys first, because that is how expansys has it set up.
greghad said:
Thanks for the help. Can I send it directly to HTC instead of to Expansys first, because that is how expansys has it set up.
Click to expand...
Click to collapse
You should be able to Expansys is just a retail seller like ATT and them. So i believe you should be able to send it directly to HTC. Call the number look it up on their websites. If you can not find it let me know and i will look for it again.
Thanks so much for the idea, I'm having Expansys send it back to me, I'll hard-reset the phone, and send it into HTC with my receipt from Expansys.
Greg
Also, you have flashed ROMs and Hard spl on it right? If so i would suggest you try and get the stock ROM that you got with the phone and then try to put stock SPL back. Message me if you need help with what i am talking about.
i contacted htc directly for my european tpro and they are ready to repair my battery drain problem. however, i need to flash stock rom and spl before sending. i am little nervous flashing stock spl - not sure if it would brick my phone or not. once i do this, i can send it to them. i read the first page from hardspl, it looks straightforward - hope it stays that way.
kmahesh said:
i contacted htc directly for my european tpro and they are ready to repair my battery drain problem. however, i need to flash stock rom and spl before sending. i am little nervous flashing stock spl - not sure if it would brick my phone or not. once i do this, i can send it to them. i read the first page from hardspl, it looks straightforward - hope it stays that way.
Click to expand...
Click to collapse
make sure you read towards the bottom of the first post on the hard spl page. There they have specific instructions for returning back to stock spl.
URGENT Info needed
I did that - everything worked fine..... the last step says "to verify, volume down + reset, see version number on tricolour screen, should now just say 1.90.0000". When I tried to do that - I dont see tricolor screen.
In my device info, it says " ROM = 5.05.405.1 WWE"; "Radio = 1.11.25.01" and protocol = "52.58.25.30U".
Does this mean that I fully recovered this to factory settings?
Thanks
greghad said:
Thanks so much for the idea, I'm having Expansys send it back to me, I'll hard-reset the phone, and send it into HTC with my receipt from Expansys.
Greg
Click to expand...
Click to collapse
Not sure how the law in your countries handles these kind of things. But over here software CANNOT limit warranty. You remember the warning that goes something like this: "this device is designed to handle interference, even if it is harmfull for the device itself." So even when you use your device normally, it can stop functioning, due to it's software.... Does this limit warranty? NO.
What if you installed Photoshop on your laptop and your laptop overheats due to Photoshop heavy CPU usage. Is your laptop manufacturer limiting your warranty? NO. Say you don't like Vista and reinstall XP. Nothings happens to your warranty. That's how warranty works, it is ment for hardware malfunction due to bad design. If your device dies due to some software interference (illegal or not), that's bad hardware design and cannot limit your warranty. Although here in Holland. Not sure how that's abroad.
Rahza
Rahza said:
Not sure how the law in your countries handles these kind of things. But over here software CANNOT limit warranty. You remember the warning that goes something like this: "this device is designed to handle interference, even if it is harmfull for the device itself." So even when you use your device normally, it can stop functioning, due to it's software.... Does this limit warranty? NO.
What if you installed Photoshop on your laptop and your laptop overheats due to Photoshop heavy CPU usage. Is your laptop manufacturer limiting your warranty? NO. Say you don't like Vista and reinstall XP. Nothings happens to your warranty. That's how warranty works, it is ment for hardware malfunction due to bad design. If your device dies due to some software interference (illegal or not), that's bad hardware design and cannot limit your warranty. Although here in Holland. Not sure how that's abroad.
Rahza
Click to expand...
Click to collapse
Wow that actually makes sense, seems every country has better standards for warrantys then the US =/
ogrillion said:
Wow that actually makes sense, seems every country has better standards for warrantys then the US =/
Click to expand...
Click to collapse
You should check this out. Companies can say all sort of stuff regarding warranty, but they are not the law (or above the law). Consumers have rights. So go learn and kick Expansys' b*tt with your new learned stuff. I'm almost certain that the US has some homolog law.
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!
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
some time in the past week, i accidentally dropped my HTC one X and the LCD screen broke (several cracks) which obviously would require a replacement but the phone is still usable, i can still call/text, literally everything except of course the screen is cracked.
So i went to the nearest HTC service center and the screen replacement would cost $260 (converted to dollars from my local currency) PLUS $150 because im using a different ROM (MIUI to be exact) and not the stock ROM.
theyre asking me to pay an additional fee because im using a different ROM and a rooted phone, I only wanted to replace my LCD screen. the OS is still working! and they were saying some technical stuff like the board was broken and other reasons they could think of to persuade me.
now my question, is it still possible to 'unroot' my phone and bring it back to the HTC stock ROM, without a trace of being rooted previously?
this topic is also related to my other post "How to get RUU - i need it to revert back to stock ROM"
pedenski said:
some time in the past week, i accidentally dropped my HTC one X and the LCD screen broke (several cracks) which obviously would require a replacement but the phone is still usable, i can still call/text, literally everything except of course the screen is cracked.
So i went to the nearest HTC service center and the screen replacement would cost $260 (converted to dollars from my local currency) PLUS $150 because im using a different ROM (MIUI to be exact) and not the stock ROM.
theyre asking me to pay an additional fee because im using a different ROM and a rooted phone, I only wanted to replace my LCD screen. the OS is still working! and they were saying some technical stuff like the board was broken and other reasons they could think of to persuade me.
now my question, is it still possible to 'unroot' my phone and bring it back to the HTC stock ROM, without a trace of being rooted previously?
this topic is also related to my other post "How to get RUU - i need it to revert back to stock ROM"
Click to expand...
Click to collapse
It is possible, using an RUU to relock the bootloader and unroot the phone, but where the bootloader says ***TAMPERED*** and ***UNLOCKED*** now, it will change to ***RELOCKED***. AFAIK, there is no way to make the boatloader show ***LOCKED***", it will forever show ***RELOCKED***, unless you unlock it again. So basically there will always be some trace of your phone having been unlocked. Someone else pointed out that, aSsuming you've followed the most popular unlock guides, you had the use the HTC Dev site to get a file, and that since you did that, it's also on record on some server someWhere that you have unlocked your phone.
So basically, unless it's a know manufacturing defect, you are most likely screwed. Don't quote me on that though, as there are always stories of people saying the right things to the right people and getting their devices replaced where most others were not able to.
garfnodie said:
AFAIK, there is no way to make the boatloader show ***LOCKED***", it will forever show ***RELOCKED***
Click to expand...
Click to collapse
You can change the flag back to LOCKED if you S-off: http://forum.xda-developers.com/showthread.php?t=2168578
But as mentioned, HTC presumably has some record of you unlocking the bootloader via the HTCDev.com website.
Plus, there was a thread a while back on the "international" One X forum section where people were reporting that HTC was honoring the warranty for phones with unlocked bootloaders; but denying warranty service for unlocked bootloader if a custom ROM was every installed (even if the phone was returned to the stock ROM before sending in for warranty). So apparently, HTC has some way of knowing a custom ROM was ever installed, even if its no longer on the phone.
A question for the OP: have you tried going through your carrier for a repair? Some carriers (such as AT&T) seem to be much more forgiving about modding the phone, and might forego any "custom ROM" fee.
$150 extra to replace a screen because you have a custom Rom? They have no relation. Find someone else to do the repair, or just order the parts and do it yourself. Not very hard to do, order LCD+digitizer, and watch some you tube videos on the process.
Sent from the HOXL dimension of S-OFF
Hi Guys
Couple day ago I sent my phone to HTC repair center. I've run RUU, relocked bootloader. I reported two following issues:
1. Chipping case
2. Signal problems
Unfortunately, HTC refused to repair my device under for free. They are saying that because I unlocked by bootloader I need to pay (£144) for new MotherBoard and after that they can fix my problems free of charge. I sent few messages to them explaining that unlocked bootlaoder isn't related to any of the of these issues but now I'm quite out of ideas what else can I do to made them fix my phone for free. Please see the last email from HTC support team and if you have any idea how I can convince them, please let me know.
Thanks in advance for any help.
I can understand your point of view on this case and the frustration this process has caused. However there are a few points that I would like to clarify for you.
Firstly, we are only quoting your for the replacement of the mainboard as this is the only part of the repair that is being classed outside of the warranty. All other work will have been deemed covered by the warranty and therefore free of charge. The reason we have to repair all parts of the device is that any work carried out on the device must be done so to a reasonable standard, according to the Supply of Goods and Services Act (1982). HTC class this standard as returning the device to a fully warrantable state. We have issued you with a quote for the repair of the mainboard because we have found that this part is faulty and needs to be replaced.
As you have stated, the htcdev.com website states that:
"This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty."
This means that if we need to replace your mainboard and you have unlocked the bootloader this work will no longer be covered by the warranty, as this technical process is "use other than in accordance with the user manual", as stated in point 7 part c of the warranty statement.
As I have stated, all faults found with the device, including the reported fault with the casing, will be repaired once you have paid the quote. The only part that you are being charged for is the replacement of the mainboard, which is not covered by the manufacturing warranty.
You have to tell them that they need proof that by unlocking the bootloader you damaged your device. Otherwise it should be free of charge - the HTCDev website states that the bootloader unlock MAY void your warranty, and to charge for the repair they need proof that signal problems/MAO chipping was caused by the unlocked bootloader.
Sent from my One S using Tapatalk 2
Yes, I told them that many times but they are claiming that they need to revert phone to "fully warrantable state" which means even if the motherboard is not broken but because bootloader is unlocked they need to put new one with locked bootloader.
They are saying that they will fix my issues under warranty but they need to charge me for new motherboard, because this only part that is not under warranty.
They don't need a new main board just to change the lock status from ***RELOCKED*** to ***LOCKED***.
That should be purely software based and they most certainly have the software to do that.
What about asking them not to replace the main board?
Apparently ***LOCKED*** status can be only done by replacing MB and I'm no able to tell if that is true or not.
I can't ask them to not replace the MB because they are saying that under Supply of Goods and Services Act they need to revert phone to fully warrantable state which means that they want to put new MB with locked bootloader, fix my issues and then the phone will as new and fully covered.
jacakowal said:
Apparently ***LOCKED*** status can be only done by replacing MB and I'm no able to tell if that is true or not.
I can't ask them to not replace the MB because they are saying that under Supply of Goods and Services Act they need to revert phone to fully warrantable state which means that they want to put new MB with locked bootloader, fix my issues and then the phone will as new and fully covered.
Click to expand...
Click to collapse
Not sure then. Guess you will just have to maybe send it to Tecardo who may be able to unbrick it for you.
Sent from my One S using Tapatalk 2
Don't fix it if it is not broken
Do not spend money getting the motherboard replaced in order to get a free repair. I use the guys at XpressFix in Orlando, FL to fix my HTC Butterfly. I just mailed it in and got it back, fixed, in a couple of days. It sounds like it takes a lot less time and effort than what you have already put into convincing those guys at HTC.
I dont know if this is a option:
But get it back, free of any charge??
(I know HTC will charge a small fee if you want the device returned without repairs here in the EU)
You could s-off , then run your own stock ruu, then s-on again (So you dont have the relocked status). So you have the original locked status. (If your device is supported?)
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
I dont know if this is a option:
But get it back, free of any charge??
(I know HTC will charge a small fee if you want the device returned without repairs here in the EU)
You could s-off , then run your own stock ruu, then s-on again (So you dont have the relocked status). So you have the original locked status. (If your device is supported?)
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
You're on the right track, except getting back to your ***LOCKED*** status isn't as simple as that.
http://forum.xda-developers.com/showthread.php?t=2155955
However, do NOT flash the HBOOTs in recovery as it could permanently brick your device.
Just ask for your device back without any changes. HTC might have noted that you unlocked your bootloader as well, so it might be a good idea to send it to your carrier next time.
usaff22 said:
You're on the right track, except getting back to your ***LOCKED*** status isn't as simple as that.
http://forum.xda-developers.com/showthread.php?t=2155955
However, do NOT flash the HBOOTs in recovery as it could permanently brick your device.
Just ask for your device back without any changes. HTC might have noted that you unlocked your bootloader as well, so it might be a good idea to send it to your carrier next time.
Click to expand...
Click to collapse
Thats a hex-edited hboot.
Thats not wat i mean.
I mean this: ( i have done this on my older devices several times this way for waranty)
http://forum.xda-developers.com/showthread.php?t=2158514
Yess, This is that easy.
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
Thats a hex-edited hboot.
Thats not wat i mean.
I mean this: ( i have done this on my older devices several times this way for waranty)
http://forum.xda-developers.com/showthread.php?t=2158514
Yess, This is that easy.
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
That will still show ***RELOCKED*** on the bootloader and does not hide the fact that the bootloader was previously unlocked. They will still charge for repairs
usaff22 said:
That will still show ***RELOCKED*** on the bootloader and does not hide the fact that the bootloader was previously unlocked. They will still charge for repairs
Click to expand...
Click to collapse
Ive read the multiple linking topics IN the topics now.
I now see what you mean. I saw the command lines, and was assuming too much.
Its possible but not for the unexperienced.
Gonna test some things for myself now.
Gonna check differences with my old devices.
And the disadvantages of a locked s-off.
Verstuurd van mijn HTC One S met Tapatalk