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
Related
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.
I'm coming back to my cha-cha after trying to use an s2 - i miss the keys!
The "p" (as in letter p) button is playing up and htc online support have offered a warranty fix *if* it doesn't have "illegal" software on it (such as custom rom or unlocked bootloader.....
I have s-off via clip, rooted and super osr on ....
Do i just need to flash an ruu on or is there more does anyone know please?
I think ruu will still leave the s-off - but some people on here last year said they got there unit s-off'd out the box so maybe s-off alone wouldn't matter.
Any tips what ruu to use - the lower the better so i can put osr back when i get phone back.....
thanks guys
My letter "P" is playing up too. It's starting to annoy me now.
I flashed the Ruu rom, still s-off.
Phone gets collected next week by HTC.
Please tell us if they repaired it, and when it come back to you, check if you still have S-OFF
They repaired it, only took one day.
Was s-off still, had newer software on than the ruu I had used.
It's back to super osr now of course
Sent from my Nexus 7 using xda app-developers app
qbert456 said:
They repaired it, only took one day.
Was s-off still, had newer software on than the ruu I had used.
It's back to super osr now of course
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Makes sense... An american judge decided that it is legal to root or (yeah, some of us have a lag of taste) jailbreak your phone. The waranty can only be voided with messing up the hardware of your phone. Since HTC also sells ChaCha's with S-OFF, they cannot blame you for unlocking it yourself. What kind of software you'll run on your phone is your own choice, and HTC can't do anything about it. They just try to scare you off with telling you this fairytale
Hello guys. I've finally created an account and joined your community hoping that i would finally be able to find an answer to problem my phone has, as i haven't really found something similar while i was wasting time searching on google. I have the S4 version of the One S, updated to 4.1.1 stock, no rooting or anything else done.
Okay, now let me describe what happens : Whenever i turn on my Data connection, it works fine for a couple of minutes, then it self-reboots. The screen randomly turns off, then the HTC logo appears and it's back on. If i don't turn data connection off as soon as possible, it won't pass too long until it reboots again. Each time, I receive the notification to send the error report to HTC, but it didn't really help me. This has been happening ever since i bought my phone, 3 months ago.
I even tried contacting HTC support, i chatted with an operator and described him my problem, but his only two solutions were factory reset or warranty. The first one didn't work, unfortunately. That's why i came here, hoping that there may be a software problem or something like that which could be fixed somehow.
PS: Wi-Fi has no problem at all. It's all smooth and fine. Reboots are only caused by data connection.
Wish you a nice day!
I'm no expert, but it seems that you have a retarded phone. Try running an RUU for your CID, take it back down to Ice Cream Sandwich and then do the OTA update again. If that continues to happen, then run the RUU again and stick with ICS. It's better than Jelly Bean, battery life is much much longer, and the sense improvements aren't all that good. Having personalised text message themes is nice, but that's one of the only upsides.
Running RUU doesn't require unlocking, which voids the warranty? If i do that, and it eventually fails, warranty won't be an option anymore, i guess. Am i wrong?
Bogdan9183 said:
Running RUU doesn't require unlocking, which voids the warranty? If i do that, and it eventually fails, warranty won't be an option anymore, i guess. Am i wrong?
Click to expand...
Click to collapse
Running RUUs requires having a LOCKED bootloader, so you don't have to worry about that. Secondly, it says that is MAY void your warranty. HTC have to prove that unlocking the bootloader made it break.
But, from what I read, as I have very little knowledge of this, I still have to downgrade the hboot from 2.15, my actual version to a lower one. And this requires rooting. Am I right?
I will try tomorrow to use the RUU from 4.1.1, it has the same version and radio like my phone. I suppose that's fine, right? [my Cid is 405]
Sent from my HTC One S using xda app-developers app
If the RUU says HTC__405 and Ville (if you have the 1.5Ghz S4 version) or Ville_C2 (if you have the 1.7Ghz S3 processor) then it will work perfectly.
Sent from my One S using xda premium
Take it to warranty if it was doing that from the first day you bought it... DON't Try to fix it, it sounds as a hardware problem, and to be fair, why do you want to repair it??? TAKE IT TO THE SHOP YOU BOUGHT IT! STOP.
I also had some kind of problem, it wasn't related to Data, but more with WIFI, and it wasn't fixed completely until I flashed A FULL RUU of the latest Jelly Bean Rom Available, probably in the process rewriting every bit of software, radio and such!
I was on the verge of throwing my phone out the window more than one time, but I bought it second hand so I didn't had warranty!
This is the only thing you cand do, flash a RUU for your region or operator, beside that it's hard to diagnose the problem... OTA Updates can do nasty things sometimes, so I don't recommend it...
After the flash, if it still acts up it's a hardware problem!
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
Does the T-Mobile HTC One S always come S-Off or was I lucky on my trade today? I traded my mint Sony Xperia Play (AT&T) this morning for a HTC One S, also mint. I've traded, bought and sold to the guy before and I know he gets his devices new by special means and knows nothing about rooting, bootloaders or S-Off.
Anyways I got curious in snooping around the bootloader menu and to my surprise found it to be S-Off...
Was this luck or do all/most/many come this way?
...nobody knows??? Just curious...
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
Oh okay. I was surprised to find it S-Off when I got this thing. I couldn't believe my eyes. That will save me a load full of work, especially the part were some of the tools require a Linux OS instead of Windows. Now ofcourse Linux is a download and installation away, but my "temporary" (now permanent) laptop is so old it only packs 128mb of ram (max can ONLY reach 512mb) and any type of Linux installation just hangs and never installs no matter how many hours you leave it running.
Not to mention some of these devices require the "hotwire" trick, and every time i need something (such as a paper clip) it is nowhere to be found.
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
all the devices come with s-on.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
Nah trust me his knowledge on rooting and so on is VERY LOW. It once took me nearly an hour to show him how to flash a rom on a device I sold him and in a day or two he already messed things up since the rom would wipe many key apps when given an old fashion factory reset. ANOTHER good hour wasted explaining to him the process over phone. If he were to buy these devices used already then sell them to me I would believe that perhaps that person did it instead of him. He gets them brand new in a store he works in, instead of commissions/bonuses for his many sales his boss lets him pick a free phone of his choice as long as its not 100% modern (e.g. a Nexus 5. wish I had that type of boss) in which he gets the opportunity to make more money off of that but remember, his boss doesn't have to pay cash, and he's basically stuck with selling it himself.
If he cant flash a simple rom, or even use a simple app to root a device, I doubt he will ever be able to S-Off an HTC. Also if he were younger (lol) I'd consider the possibility. I honestly believe that this thing may have mistakingly been left S-Off or something by the factory. Or maybe it served a purpose back at HTC.
Whatever the case, it was a big surprise to me.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
tivofool said:
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
Click to expand...
Click to collapse
Hey now that you mention it I think thats the race his bosses are. But whats a supercid? Never heard of that before?
Nah definitely not as lucky to have a supercid. I assume CID = Carrier Identification seeing mine is T-Mobile related.
Sent from my LG-LS970 using xda app-developers app