Related
Hi,
Convinced my wife to also get a Desire S and we are picking one up from Orange UK later today.
She will need root so that we can install an app to get the phone to connect to our car phone kit. I'm assuming that the phone will come with Android 2.3.3 and the associated HBOOT.
I'm guessing the options are to diable the OTA updates, S-Off with Alpharevx and use gingerbreak for root. I'm assuming the advantage is that this can all be reversed if there is a layer problem with the phone. The downside will be that we won't be able to update the phone until Alpharevx, etc, catches up with new phone software releases.
The alternative is to S-off via XTC-Clip (there is one nearby) which will ne permanent and allow pre-rooted updated RUU's to be more regularly installed.
Does anyone have any views on the best way forward.
As an aside, I'm guessing that installing an unbranded ROM does not affect any functionality of the phone on the Orange UK mobile network.
Many thanks,
Damian
Hello,
Assuming that you get a hboot version that can be s-off'd then I'd use revolutionary and follow the method that you described.
You're right about disabling ota updates do that immediately as if applied then they can seriously limit your options.
There is something called uma (I think that's right name?) which I believe enables you to use your wifi to make calls when mobile signal is weak, I believe that this can be used on orange but I don't know if your devices would come with it. If you're from UK you can now piggy back Tmobile so you have more chance of a decent signal.
If you get a later version of hboot, that can't be s-off'd then you still have several options open to you:
you could attempt to use the official htc unlock htcdev.com unlock routine, even though this devices still isn't listed as supported I've read that some users have successfully used this method to unlock their devices successfully. Although I can't provide any links so you'll have to either read around or post a further question in an attempt to get some info on how to do this method.
You could alternatively drop the revolutionary boys a line and ask them is they plan to update their software to later versions off this devices hboot To see If any etas are forthcoming , although developers tend not to like eta requests
Another option before considering xtc would simply be to wait HTC to add support for this device, it's supposed to be coming, but so is xmas, although you won't be unhappy with the device running stock, although I run a rooted custom and love it, my wife is still running stock as it's her first Android device and she's still loving it!
Although then there's always the xtc route and as an original xtc user I can recommend this route although as you're aware it's not reversible and you must consider the effect it well have on your warranty
Good luck with your choice, psst back any questions
Swyped from my Desire S using XDA Premium
Thanks for the reply.
Picked the phone up on Saturday and it is Hboot 0.98.0002 and Radio 3805.06.02.03_M.
My wife seems happy with things, apart from the mobile data/signal does not seem as robust as with her old Nokia. I've told her that a radio update may improve this as it did with mine when I recently updated it.
Think will go down the Revolutionary route. I need to check but assume that you can just flash a new radio with the Revolutionary Hboot. I think for now she will be happy with 2.3.3 and we will see how things pan out with updates in the next few months.
Thanks again,
Damian
As I said I am thinking about getting this phone but I am worried after reading around that doing the whole htcdev token thing for opening it up for root voids your warranty. So my questions are...
1. Can it be reversed?
2. Can tmobile tell too? Even if it can be reversed?
3. Has anyone tried to see if this works http://forum.xda-developers.com/showthread.php?t=1578908
4. Does htcdev get you s-off?
5. What is s-off?
Sent from my NexusHD2 using XDA
1. Yes and no. The bootloader can be re-locked, but as with all HTC devices, once you've unlocked it, there's signs that you did. Mine says *TAMPERED* for example once I rooted it. I don't think that'll ever go back.
2. T-Mo can tell if you bring it into the store. It doesnt take much work. All they gotta do is load the bootloader.
3. I have no idea, but my guess is that the end-result is the same as #1. The method you've linked in no way hints at being "secretive" about the unlock. I'd also not recommend you use it, since it's not necessarily a tried and true way. Following HTCdev.com's process IS however a tried and true way. I mean -- why NOT use the official HTC route?
4. No, HTCdev does NOT get you S-OFF. I have no idea what does, but you can still load CWM recovery, root, and load ROMs with S-ON anyways. Only reason you need S-OFF is if you start messing with paritions, which I wouldn't recommend unless you know what youre doing and are prepared to accept the consequences.
5. S-OFF lets you mess with partitions as far as I can tell. It may do more, but I'm not sure. I'm brand new to HTC phones (my first phone was a Nexus S).
Keep in mind with all of this, that your worries about unlocking are pretty much useless. Keep in mind -- if you're needing to send your phone in for warranty repair, you're 99% likely sending it in for HARDWARE repair. HTC and other mfr's (Samsung too) generally will honor your warranty if the cause is obvious (vol button breaks, capacitive buttons break, etc).
And if you're unlocking your phone, chances are any software problems you have are going to be taken care of by YOU anyways. Keep that in mind.
Cheers, and happy flashing!
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
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!
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