[Q] Return US version back to stock? - HTC One S

So I will be returning the One S, albeit a great phone, back to TMobile to get my slice of the SIII tomorrow (last day of 14 day period) -- I have a general understanding on returning it back to stock, but as far as getting it completely back to the way I had it, maybe not so much. Anyone have a walkthrough on turning S-On and getting it entirely back to the way I bought it?
Thanks in advance.

id_twin said:
So I will be returning the One S, albeit a great phone, back to TMobile to get my slice of the SIII tomorrow (last day of 14 day period) -- I have a general understanding on returning it back to stock, but as far as getting it completely back to the way I had it, maybe not so much. Anyone have a walkthrough on turning S-On and getting it entirely back to the way I bought it?
Thanks in advance.
Click to expand...
Click to collapse
Did you flash a custom rom or just rooted and nothing else?

relock the bootloader and run the Tmobile RUU.
job done !!
PS. You may need to revert to stock recovery before running RUU.

azzledazzle said:
relock the bootloader and run the Tmobile RUU.
job done !!
PS. You may need to revert to stock recovery before running RUU.
Click to expand...
Click to collapse
All I did was run cmd " fastboot oem lock" and run T-mobile RUU.
Waiting for my exchange ONE S

Related

[Q] Returning One S to T-Mobile for service. What is best way to return to stock?

I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
fbihawk said:
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Click to expand...
Click to collapse
Now also having issues with HTC Development text showing up every time you start the phone. Kind of a dead giveaway. Anybody have thoughts?

[Q] Oem relock causing bootloop

Hi basically I have a very retarded lot of HTC care people in my town. I wanted to get back stock on my phone. After searching long and hard did not find my RUU anywhere. (Its the HTC__038 India VilleC2 for HTC One S). As my bootloader was unlocked guess they were unable to flash the ROM.
Now I thought I will lock the bootloader and then take it over to them for rework. But when I do it, the phone gets stuck on boot and does not load further. I have to again unlock, and restore before the phone becomes operational again.
So can someone tell me how to fix this issue if at all??
I have 3 choices.
1. I get the RUU for my phone and all is sweet.
2. I get a NANDROID from someone else and flash that and try to update. (All I am trying to do it get to 4.0.4)
3. Lock bootloader and take it to HTC care in a working condition else they threaten to ship it to HQ for checking. That will mean 30 days (min) downtime. no cant do!!
So if anyone has any suggestions I will be glad to hear. Thanks.
fatpanda0 said:
Hi basically I have a very retarded lot of HTC care people in my town. I wanted to get back stock on my phone. After searching long and hard did not find my RUU anywhere. (Its the HTC__038 India VilleC2 for HTC One S). As my bootloader was unlocked guess they were unable to flash the ROM.
Now I thought I will lock the bootloader and then take it over to them for rework. But when I do it, the phone gets stuck on boot and does not load further. I have to again unlock, and restore before the phone becomes operational again.
So can someone tell me how to fix this issue if at all??
I have 3 choices.
1. I get the RUU for my phone and all is sweet.
2. I get a NANDROID from someone else and flash that and try to update. (All I am trying to do it get to 4.0.4)
3. Lock bootloader and take it to HTC care in a working condition else they threaten to ship it to HQ for checking. That will mean 30 days (min) downtime. no cant do!!
So if anyone has any suggestions I will be glad to hear. Thanks.
Click to expand...
Click to collapse
Without the right RUU you have no chances here if you ask me.
A nandroid from another phone will not work for you (at least I know somebody who tried it once and it resulted in a bootloop).
But there should be a RUU for you. I can't imagine there is no RUU for India!
The best you can do for now is to search this thread and if you find nothing, to ask for your RUU:
http://forum.xda-developers.com/showthread.php?p=35379039
Sent from my HTC One S running TrickDroid 4.0
O
Schlengge said:
Without the right RUU you have no chances here if you ask me.
A nandroid from another phone will not work for you (at least I know somebody who tried it once and it resulted in a bootloop).
But there should be a RUU for you. I can't imagine there is no RUU for India!
The best you can do for now is to search this thread and if you find nothing, to ask for your RUU:
http://forum.xda-developers.com/showthread.php?p=35379039
Sent from my HTC One S running TrickDroid 4.0
Click to expand...
Click to collapse
Well I have been trying for ages to come across this RUU but to no avail. That's the reason I am still on a custom ROM as I can't do any updates. I am really interested in trying other ROMs. But there is no way of doing it without the 4.0.4 update. Thanks for the help though.
fatpanda0 said:
O
Well I have been trying for ages to come across this RUU but to no avail. That's the reason I am still on a custom ROM as I can't do any updates. I am really interested in trying other ROMs. But there is no way of doing it without the 4.0.4 update. Thanks for the help though.
Click to expand...
Click to collapse
I believe Football can get any RUU but you have to pay for it.
Darknites said:
I believe Football can get any RUU but you have to pay for it.
Click to expand...
Click to collapse
Really!! wow thats news. Thanx mann.. Could you link me to the forum where I get in touch with him??
http://forum.xda-developers.com/showthread.php?t=1543588

[Q] can anybody help a noob?

I have a HTC Sensation and running CM10, I urgently need help unrooting my phone and going back to stock so I can send it off for repair.
I am unsure how to do the necessary to revert back and what I need in order for the manufacturer to fix a hardware problem that I have.
Any help would be great. I am having difficulty finding information that I (a noob) can understand,
Thanks in advance!
go here
S.K.O.W said:
I have a HTC Sensation and running CM10, I urgently need help unrooting my phone and going back to stock so I can send it off for repair.
I am unsure how to do the necessary to revert back and what I need in order for the manufacturer to fix a hardware problem that I have.
Any help would be great. I am having difficulty finding information that I (a noob) can understand,
Thanks in advance!
Click to expand...
Click to collapse
HI,
if you want to send it back to htc service center all you can do is to flash a ruu for more details go here
http://forum.xda-developers.com/showthread.php?t=1672425
Are you soff or son
shrex said:
HI,
if you want to send it back to htc service center all you can do is to flash a ruu for more details go here
http://forum.xda-developers.com/showthread.php?t=1672425
Are you soff or son
Click to expand...
Click to collapse
Yes I finally got it back to stock and S-On! was having trouble when flashing the RUU, I kept getting an 155error, all I had to do was manually put my phone in Bootloader and it would continue on there, (I was ment to do that automatically), I am all ready to send off for repair :good:
S.K.O.W said:
Yes I finally got it back to stock and S-On! was having trouble when flashing the RUU, I kept getting an 155error, all I had to do was manually put my phone in Bootloader and it would continue on there, (I was ment to do that automatically), I am all ready to send off for repair :good:
Click to expand...
Click to collapse
Now if you made a nandroid backup before you flashed the RUU, when you get it back from teh rpair shop you can just s-off again and reflash your back up and it'll be just like you left it, only less broken.

[Q] Return to as close to stock as possible

Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Tersanyus said:
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Click to expand...
Click to collapse
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
exad said:
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
Click to expand...
Click to collapse
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
31ken31 said:
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
exad said:
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
Click to expand...
Click to collapse
I forgot about su access prompt. That could be a shocker lol
Sent from my HTC One X using xda premium
exad said:
I would leave just the bootloader unlocked and S-OFF and RUU.
Click to expand...
Click to collapse
I agree. Couple reasons (both related to RUU). If the new user for some reason needs to recover the phone, and runs the RUU (not unheard of, HTC support will sometimes direct customers to do this), that person will either:
1) Brick the phone, if its left as SuperCID and S-on
2) If S-on (but CID is changed back), and bootloader is left unlocked, the RUU won't run. The person will have no idea why, and will likely be stuck.
S-off solves both of these potential issues. If you are at all worried about the next user. I would S-off, then run the RUU to return the phone to stock. The only thing that would be "not stock" is unlocked bootloader and S-off. But neither of these will mean anything or affect a less experienced user.
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
redpoint73 said:
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
Click to expand...
Click to collapse
I didn't mean leaving it supercid--that is obviously a risk.
exad said:
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
Click to expand...
Click to collapse
That's kind of my point. Selling it rooted is fine, just represent it for what it is. You shouldn't give a modified phone to someone who doesn't know what that even means.
The phone is going to a friend who has a Pantech Burst currently. As someone mentioned I didn't want them to get a SuperSU prompt for root access and have no idea what that means. I tried a stock rooted rom but it kept rebooting. I did factory reset/data wipe and reloaded the rom twice but still kept doing it. I thought it odd too. Cleamrom is acting just fine though.
After hard bricking a Droid DNA which I don't know if it was due to being unlocked and such I'm starting to feel rooting and custom roms isn't for me anymore. The Droid DNA was replaced and the replacement was never unlocked (and since it has most recent software it couldn't be unlocked. Don't get me wrong, I love not running stock devices. It's such a great feeling to get rid of all that carrier added bloat that I most liked.
I've actually moved on from the DNA as well. I'm on a One now from AT&T as my primary phone. And I so hate all that AT&T bloat in there. It's all disabled but still seeing it there just sends chills down my spine.
So now I am not so sure what to do about the One X now. My original thought was RUU back to factory and relock the bootloader and keep S-ON. That way if someone did look they'd only see "RELOCKED".
Makes me miss the easy days when I used a Captivate and Note 1. Those were so easy to use custom roms on.
iElvis said:
I didn't mean leaving it supercid--that is obviously a risk.
Click to expand...
Click to collapse
Your previous post didn't explicitly say anything about that, one way or another. So I was just clarifying for the benefit of the OP. I knew what you meant, but wanted to make sure the OP did, too!

[Q] Steps to going back to stock

Im rooted, s-on, hboot 1.09 and on viper 2. Im selling my one s on ebay since i bought a nexus 5 and wanted to know the steps to getting the phone back to the stock rom so when sold, the buyer wont have any issues or stability problems.
Thanks!
andrewt328 said:
Im rooted, s-on, hboot 1.09 and on viper 2. Im selling my one s on ebay since i bought a nexus 5 and wanted to know the steps to getting the phone back to the stock rom so when sold, the buyer wont have any issues or stability problems.
Thanks!
Click to expand...
Click to collapse
Here is a post I wrote to someone else, assuming you need t-mobile RUU.exe otherwise use a different RUU.
http://forum.xda-developers.com/showpost.php?p=46260606&postcount=2
Then perform a factory reset from either the settings or through the bootloader.
http://www.htc.com/us/support/howto.aspx?p_id=463&id=315367&p_name=htc-one-s-t-mobile

Categories

Resources