Database Info

[Q] Return US version back to stock?

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

Warranty exchange while rooted?

So I have a problem, my HOS is constantly disconnecting from the network. It'll only stay connected as long as I'm not browsing using the 4G network, on Wifi works fine, never disconnects.
At first I heard it was a problem with the TMO network and they were working on updates, so I waited; then I heard it was a problem with the HOS and the TMOB RUU version, and loading a HTC EU ROM would solve the problem; then I heard that it was a problem with the radio, but no one has a consistent method of flashing an updated radio with S-ON (some say OK to flash with Clockwork, others not so much luck, seen reports of soft bricks).
I havent seen anyone really find a solution for this problem. Seen folks say the build.prop needs to be updated (which I haven't tried), others have fixed with different ROMs, everyone has a different solution that only appears to work for them.
FWIW
HBOOT-1.09.0000
RADIO-0.16.31501S.16_2
Running TrickDroid 7.1.0
So my thought is that it's a problem with my device (I got it the first day it came out) so I assume it has to be a manufacturing defect that hopefully a warranty exchange would resolve.
I'm down for reloading stock, but as I recall the minute the bootloader is unlocked the disclaimer appeared. Anyone know how to lock the bootloader?
My other question is, has anyone done a warranty exchange or know if they care if the device is rooted since more than likely they'll just reflash it to stock and put it in the refurb stock. I've done warranty exchanges with G1, N1 and MT4G while rooted and no one seemed to care. But now that the bootloader has the disclaimer on boot, I fear I'll be on the hook for the device since it's rooted.

You can flash radio zips cuz you hboot is 1.09
Sent from my HTC One S using xda premium

randomnoob83 said:
You can flash radio zips cuz you hboot is 1.09
Click to expand...
Click to collapse
With clockwork or another method?

With TWRP. I had those disconnect issues with T-Mobile stock everything, but unlike you, I ran the RUU, so yes I got an update HBOOT but those issues are gone.
T-MobileUS HTC One S running Stock Rooted 2.21.

I flashed my radio with clockwork.
Sent from my HTC VLE_U using xda premium

thanks guys. very excited to hear that the new radio solved the issue. I was waffling between ditching the HOS for a GNexus but the camera on the HOS and the overall form factor kept keeping me near.
I'll try it as soon as I get back in town.

Please let us know if this works for you.
My girlfriend just bought a T-Mobile one s after seeing how nice my one x was, and she has been plagued with radio problems the entire time. I've ran the latest T-Mobile US RUU hoping it would fix the issues but it has not.
Obviously, I'd like to hold out as long as possible with rooting her phone incase she needs to return it. Anyway, let us know how it goes.

[Q] Flash back to stock ROM

I did search and found some info, but still require some help
Have a One XL, I owned this phone since new, but was using a couple of other devices in the past few months, friend of mine borrowed the One XL, and had asked me before if it was ok for him to flash a different ROM.
Turns out he flashed the Viper XL rom, and its really good, but, since then, he's returned the phone back to me, and I'm intending on passing the phone along to my mother.
I think she'll find it easier without all the different Viper settings and variables, so would like to return to original, but it appears that (when booting into recovery) that there isnt a backup in there? My mate said he probably wiped it by accident
I have all the right tools on my PC, but need some help and guidance on how to:
1. Download original ROM
2. Flash it back
any tips?
thanks!

I have a Samsung GS 1 and if I want to flash back an original rom I go into download mode and use ODIN or THOR (?) to flash back the original ROM.
I don't know if the same tools can be used for your phone.

sephstyler said:
I did search and found some info, but still require some help
Have a One XL, I owned this phone since new, but was using a couple of other devices in the past few months, friend of mine borrowed the One XL, and had asked me before if it was ok for him to flash a different ROM.
Turns out he flashed the Viper XL rom, and its really good, but, since then, he's returned the phone back to me, and I'm intending on passing the phone along to my mother.
I think she'll find it easier without all the different Viper settings and variables, so would like to return to original, but it appears that (when booting into recovery) that there isnt a backup in there? My mate said he probably wiped it by accident
I have all the right tools on my PC, but need some help and guidance on how to:
1. Download original ROM
2. Flash it back
any tips?
thanks!
Click to expand...
Click to collapse
rather than original rom why don't you just flash one of the rooted almost stock roms here? UrDroid or CleanROM would be good choices.

If he's giving it to his mother, I don't think root is a good idea, just in case. That's like giving a non techy a pc with Linux and giving their default account root access.
Go to your bootloader and tell me what hboot version you have and if it says s-on or s-off.
Is your phone from at&t?
Essentially your options would be to flash a stock non rooted rom or ruu. But to ruu you would need to meet certain conditions or you'll brick.
Sent from my One X using xda app-developers app

Thanks for that. Sorry for the late response. I've been away for work. In fact I'm still away. I believe from memory its S-off. Not from AT&T. Hong Kong stock I believe (online purchase)
Can't confirm hboot till I see the phone next. Maybe a month away!!
Sent from my C6603 using Tapatalk 4 Beta

you can find ruu and run it.

Please HELP
Guys please help me to get the right RUU for my HTC ONE X
Version:3.14.207.27
Cid: O2___102
Hboot 1.36.0000
Radio-5.1204.162.29
Android : 4.2.2

HtconexTornado said:
Guys please help me to get the right RUU for my HTC ONE X
Version:3.14.207.27
Cid: O2___102
Hboot 1.36.0000
Radio-5.1204.162.29
Android : 4.2.2
Click to expand...
Click to collapse
That's the international one x quad core don't flash anything from here go to the forum for your device or you will brick your phone
Sent from my HTC One XL using xda premium

[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] Wifi Error - Can't turn on Wifi

I had problems (even before rooting) where my wifi would simply not work. If I go into settings and try to switch it from On to Off, it would simply say there was an "Error". Earlier in 2013, I had rooted and installed a Cyanogenmod Rom on my phone (I forget which one exactly, but it was JB). After a while, I went back to stock. A week or so later, the problem happened again. I did a factory reset. It fixed the problem for a day. Then it happened again and not even a factory reset would fix it.
I got a Nexus 5 for Christmas, so I'm looking to sell this phone but want to fix the wifi before I do so. I've seen a couple of people with a similar problem but no fixes. Does anyone know what is the cause of this problem and how to fix it?
Thanks.

Um, how did you return to stock? Ruu or a backup?
Sent from my One Xl using xda premium

If it was happening while your phone was completely stock I don't think there's anything you can do that's going to be worth it. It'll likely have to go to a repair centre and the cost would be more than you can sell the phone for. You could list the phone on Swappa, there may be people who require only the display, motherboard etc.
You could try running an RUU as a last attempt saving though.
Sent from my Evita

magnetboard said:
Um, how did you return to stock? Ruu or a backup?
Click to expand...
Click to collapse
A nandroid is only going to put you back on the stock ROM, not stock recovery, etc. You may also have s-off, unlocked bootloader, SuperCID, etc. that would make the phone "not stock", but you have given zero details for us to answer your question.
Going back to stock should only be necessary for selling the device or returning for warranty (not necessary for AT&T).

Well, a nandroid, as stated by Tim, only gibes you the stock ROM. An ruu wipes anything that might have messed with anything.
Sent from my One Xl using xda premium

I used an RUU to go back to stock.
The details for my phone are:
S-Off
CID-11111111
HBoot-2.14.0000
If there is any other information that would be helpful, let me know and I can try to provide it. I'm planning on selling it on Swappa...my hope was to fix the wifi before doing so.

If you've done an RUU and still no WiFi then you've run out of options.
Sent from my Evita

Thanks. That's what I was expecting...just wanted to make sure.