Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
Hello,
This morning I was in the market ( My Apps) and i chose Update all option. Loads of apps started to download, and after few minutes my phone froze. So i removed the battery and since then I', stuck in the bootloader menu:
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011, 14:58:38
I can't do factory reset or access recovery. At some point I have successfully ran RUU, problem is I'm on UK O2 but being complete idiot I installed 3's ROM. Even the 3's ROM don't boot up. I can't run RUU anymore, because every time RUU is trying to reboot into boot loader it get stuck.
So,
I got phone from O2 that has a 3 logo (its stuck on it),
I have S-OFF phone so it probably voided the warranty.
Can anyone think of any solution please?
Thanks in advance for your help guys.
If you need more info please let me know.
Marcin
There are at least 5 similar topics, one is mine (same thing happened to me). Use search.
Does adb works yor you ?
yeap I have also created a topic on this.
I had to send mine back to HTC to fix.
What I would like to know is, if you send it back to HTC, would they notice the s-off and charge you money?
What ROMs were you all on? I got a similar problem on stock ROM after XTC Clip S-OFF, but a battery pull fixed it. I guess this only happens with S-OFF stock ROMs, so switch to avoid this.
No, adb doesn't see my phone....
mpolak83 said:
No, adb doesn't see my phone....
Click to expand...
Click to collapse
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
InfernalByte said:
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
Click to expand...
Click to collapse
When I run Adb devices it doesn't list my phone...so it doesn't work i suppose....
If I send my phone to HTC for repair will they accept it or will charge me because of S-OFF??
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
mpolak83 said:
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
Click to expand...
Click to collapse
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
InfernalByte said:
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
Click to expand...
Click to collapse
I have tried that, but I got the error that I can't roll back to older version of hboot.
I have just booked my phone for repair.. I'm gonna act stupid. I'll tell them that my friend installed something on my phone etc. Probably won't work... I will let you know what they said.
HTC gave me some terms and conditions to read and one of the says:
2.3 NonWarranty chargeable Repair Service
a) Repair of a Device that is
In-Warranty but which needs to be repaired including the following or similar
reasons shall be classified as a NonWarranty chargeable Repair Service:
1) Accidental damage. Accidental damage to the Device, such as dropping it
on the ground or in water. 2) Broken Liquid Crystal Display (hereinafter
known as “LCD”). 3) Damaged Sync or Charger Connector. 4) Damage
caused by liquid entering the Device, or other misuse due to the failure of the
Customer to follow the instructions properly. 5) Failure of the Customer to
upgrade the software according to the procedures outlined under the
warranty terms card of the Device. 6) Downloading illegal software onto the
Device. 7) Where the fault is caused by downloading illegal software onto the Device
or other accidental damage, the Customer shall be required to pay for spare
parts, labour, diagnosis and software refurbishment along with shipping and
handling charges.
Is S-OFF classified as illegal software?
Everything except RUU is illegal software...
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
So I'm busted?
It's 50:50
Sent from my HTC Desire S using Tapatalk
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Quick update.
I have sent my phone to HTC for repair under warranty yesterday. I have checked the status today, and it says "We are repairing your phone" So it looks like HTC don't check if the phone was rooted or have S-OFF
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
InfernalByte said:
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Click to expand...
Click to collapse
Aren't custom Sense ROMs illegal ?
Coz Sense is HTC Proprietary framework.
goatimus said:
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
Click to expand...
Click to collapse
You have to go to fastboot
Sent from my HTC Desire S using Tapatalk
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..
This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...
True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app
Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....
Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it
ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.
glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on
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!
I have an HTC One X with 3.18 firmware that is rooted, SuperCID, S-OFF and unlocked. I want to return it to stock, unroot and re-lock - basically I want to get it as close to stock as possible.
I made a backup of the stock ROM prior to flashing a custom ROM onto it, so I was able to restore that.
So here is how I assume I need to go about this:
unroot - not sure how to do this, I can't RUU 3.18 can I? I'm downloading the stock OTA right now just in case.
set the bootloader back to "locked" using this: http://forum.xda-developers.com/showthread.php?t=2168578
Is this correct? Do I need to undo the SuperCID? Is it possible to undo the S-OFF?
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
exad said:
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's a work phone. My bosses didn't care about me rooting it, but I will need to return it eventually to exchange it for another phone and it needs to be stock in case another employee gets it.
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
exad said:
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
Click to expand...
Click to collapse
Ah, gotcha. I didn't know that would happen when I unlocked and rooted - thought I had read everything I needed to about it prior to rooting, but I guess I missed that.
I guess I could just RUU, change the CID back, but leave it as S-OFF. That would keep it from getting bricked, right? The chances of it being an issue would be pretty slim I imagine.
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
So there's really no way to return it back to stock? That's kind of a bummer...
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
kimboinatl said:
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
Click to expand...
Click to collapse
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
RollTribe said:
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
Click to expand...
Click to collapse
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
EDIT: Crap, just realized my tampered flag is still on. The RUU doesn't fix this, right? Guess I need to remove this first.
kimboinatl said:
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
Click to expand...
Click to collapse
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
RollTribe said:
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
Click to expand...
Click to collapse
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
kimboinatl said:
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
Click to expand...
Click to collapse
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
31ken31 said:
When I ruu'd it set it back to locked
Click to expand...
Click to collapse
Really? RUU shouldn't have an effect on the LOCKED flag.
31ken31 said:
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Are you sure? If so, did you happen to have s-off when you did this?
Yes and supercid
Sent from my HTC One XL using xda premium
kimboinatl said:
Are you sure? If so, did you happen to have s-off when you did this?
Click to expand...
Click to collapse
If he didn't (have s-off) he would have bricked.
I am also curious about this. If the combo of S-off and RELOCKED and RUU results in LOCKED, than its the first I've heard of it.
Running the RUU and UNLOCKED, I can say first hand, the result is that it still says UNLOCKED.
I went ahead and used the method here to set it back to LOCKED:
http://forum.xda-developers.com/showthread.php?t=2168578&page=3
I set the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
31ken31, I probably would have just tried what you did if this wasn't a work phone, I just didn't want to risk it.
Thanks to everyone for the help!
kimboinatl said:
the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
Click to expand...
Click to collapse
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
redpoint73 said:
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
Click to expand...
Click to collapse
Yes on both counts
I could have also claimed that I got one with super CID, I think I've read that it happens sometimes, but it was easy enough to change back so hey, why not.
I'll really miss having root though. It makes things so much better.