Database Info

[Q] New 'Orange' Branded Phone - XTC Clip or Not?

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

[Q] Massive help needed for a noob :( Text delay on v1.47

Hello all.
I'm having some major problems with my Desire S - stock firmare v1.47, T-Mobile - and would be very thankful for any support and advice provided
I've had the phone since late August, and just over a month of having it, the phone completely died. T-Mobile replaced the mainboard, and returned it. Since receiving the repaired handset, text messages are delayed when coming through - sometimes upto an hour. Sent it off to T-Mobile again, and this time they've replaced the antenna. The same thing is happening.
While it was away the second time, I did some research and found lots of people claiming it's an issue with the 1.47 update on the Desire S.
The main reason for this thread is just to ask what my best options are from here. I'm ok S-OFFing and flashing another ROM, or downgrading if this is possible and will definitely resolve this issue; but as I'm a certified noob, I was wondering what advice you guys may have for me
Thanks,
DJM.

can't you just flash the 1.28 RUU?

Hi, thanks for the reply.
I used a T-Mobile 1.30 RUU, and S-OFF'd with revolutionary.
I *think* I might have cracked it - touch wood.
I'm amazed at android releasing updates which impede such basic functions though

great, hope you get it sorted

Thanks man
I'm getting texts through as they should at the moment, so fingers crossed it will stay that way.
I recommend that anyone with a Desire S, especially on T-Mobile UK, resists the urge to upload to 1.47

Return to Stock for Warranty Repair

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

One S [S4] rebooting when data connection is turned on

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!

GG HTC One X

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

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

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

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

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

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