Related
Just been trying and failing to use the new rooting method that doesn't unlock the bootloader, when I noticed that when in FASTBOOT & HBOOT, the first line of text reads:
NEXUSONE PVT SHIP S-OFF
Now, I am certain I had checked this before and it was S-ON, but I can't remember if this was before I had sent it back to HTC for a repair, or maybe it is due to installing the pre-release 2.2 update.zips?
Either way, is this of any use to anyone?
its S-ON for me and im on stock frf72
are you sure you dont have a holiday nexus (phones given to employees and special prelease testing)
If it was a holiday phone it would say ENG S-OFF, not SHIP S-OFF
Ps. This was in development a minute ago... I put it there for a reason lol
ATT band phone, rooted, 2.2, S-ON
Rusty! said:
If it was a holiday phone it would say ENG S-OFF, not SHIP S-OFF
Ps. This was in development a minute ago... I put it there for a reason lol
Click to expand...
Click to collapse
Engineering phone & Holiday phone are not the same thing.
Oh, I thought they both had the 768Kb SPL?
Either way, mine was bought from Google in late Jan, standard battery cover and the SPL 100% used to be S-ON.
Is this really of no use to anyone? I thought it might be handy for the relocking bootloader quest?
Rusty! said:
Is this really of no use to anyone? I thought it might be handy for the relocking bootloader quest?
Click to expand...
Click to collapse
well if you sent it in to get it that way...its not gonna help much since we cant make a full image of the phone. are u unlocked now? can you relock?
Ah didn't know that it couldn't be dumped, just assumed it could be after reading that some folks had got their hands on the ENG SPL. Guess this is a non-starter then. Bugger.
Also I can't be sure that it is down to HTC, but it's all I can think of that would have changed it.
knightnz said:
Engineering phone & Holiday phone are not the same thing.
Click to expand...
Click to collapse
My N1 is running stock build ERD56C with bootloader locked - HBOOT says ENG S-OFF.
My battery cover has the AndroidBug waving the flag with the link to the holiday phone game on it and my bootanimation is the one that's included in the latest CyanogenMod 6 release (you may have frequented those threads about that, I pulled the anim out of my phone and posted it on Modaco - not sure if it was my bootanim the cyanogen guys used tho?! link: http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/311351/build-version-erd56c/).
Anyway, I've been told by a few folks that I've got a holiday phone but I guess if I'm ENG S-OFF then it must be an engineering one? Certainly it didn't seem like my bootanimation had been widely seen before...
Question is, may my phone be any use in the quest to relock the bootloader?
Rusty! said:
Ah didn't know that it couldn't be dumped, just assumed it could be after reading that some folks had got their hands on the ENG SPL. Guess this is a non-starter then. Bugger.
Also I can't be sure that it is down to HTC, but it's all I can think of that would have changed it.
Click to expand...
Click to collapse
it MAY be possible. I remember that we got a hold of the Engineering SPL for the G1 when one of the Devs got their g1 back with the eng spl still on it
Interesting.
Well if anyone knows what commands need typing to try, post away!
OP this may by the rumor about FRF91 fixing the non-unlocked rooting method that surfaced with FRF72. I cannot confirm this though.
Er, what's that got to do with S-OFF SPLs?
Quick question for my awesome XDA'ers. I am upgrading to a HTC Evo tomorrow.....yeah ....yeah....finally. As a result I need to unroot my phone so that I can sell it on EBay. I tried once before to unroot by using the latest RUU and recieved a Bootloader Error 140. Further reading explained that this is due to my HBoot being 1.47. My question to you all is, I came accross this link for changing to S-Off in HBoot. If I do this, should I be able to install the latest RUU. Once installed, should I be able to change back to S-On and thus the phone is unrooted?? Any and All help is appreciated.
Side note - the people on the CDMA Hero XDA forums have been awesome people. I thank all of you and hopefully the Evo people are just as cool!!!
Thanks
***Thanks to you all - the unrooting worked like a charm - for anyone that wants to unroot, I believe this is the easiest process - less than 20 minutes
My process was as follows
** Go to http://unrevoked.com/rootwiki/doku.php/public/forever and download zip (place on SD card)
** Got to http://geekfor.me/hero/radios/radio-242010427/ and downgrade radio from .29 (place on SD card)
** Go to http://forum.xda-developers.com/wiki/index.php?title=Hero_CDMA&oldid=9386#2.1_Sense_Based_ROMs and find a 2.1 Rom to download (I chose NFX Sprint - first one)
From here all you do in flash, flash, flash. First flash the Rom and allow it to get up and running (no need to sign in). Once it has settled -remove battery and flash the downloaded radio (go to http://geekfor.me/faq/flash-radio/ if you have questions). Once completed, reboot phone and allow to settle in. Remove battery and in bootloader screen you should see that the battery has been downgraded to .27. Now you can flash the unrevoked forever (just like any ROM). Once flashing is complete, go back to bootloader screes and you will notice it says S-Off. Reboot phone and allow to settle in. From here all you need is a HTC/Sprint authorized RUU ( you can find one on the WIKI above) and follow the directions. Now things will appear to be going as normal and then you will recieve a 155 Error on your computer, never mind it, look at your phone and you will see that it is still downloading. Wait till everything has downloaded and all you see is RUU in Red. Remove battery and press power and allow to boot up. Your phone is now unrooted. You can tell my looking at the Kernel which is now a HTC kernal and you can try to do a HTC Update. IN NO WAY DO I TAKE ANY CREDIT FOR ANY OF THIS. I just know how to google my ass off and the people on XDA have been awesome in answering questions. This is my first time creating directions, so bare with me. I don't know much, so keep the questions basic. Like I said before, this was my process and it worked...now on to sell the phone on EBay. FYI, the Hero was awesome, but this damn EVO is crazy!!!
Happy Unrooting!!!
the12nv said:
Quick question for my awesome XDA'ers. I am upgrading to a HTC Evo tomorrow.....yeah ....yeah....finally. As a result I need to unroot my phone so that I can sell it on EBay. I tried once before to unroot by using the latest RUU and recieved a Bootloader Error 140. Further reading explained that this is due to my HBoot being 1.47. My question to you all is, I came accross this link for changing to S-Off in HBoot. If I do this, should I be able to install the latest RUU. Once installed, should I be able to change back to S-On and thus the phone is unrooted?? Any and All help is appreciated.
Side note - the people on the CDMA Hero XDA forums have been awesome people. I thank all of you and hopefully the Evo people are just as cool!!!
Thanks
Click to expand...
Click to collapse
Unrevoked forever has an s-on zip to fix your bootloader issue. From there you can run RUU. I never had a problem unrooting with s-off and I'm the same version. You can try super one click. It has an unroot option.
Sent from my HERO200 using XDA Premium App
Super 1 click???...ill look for it...and I will try the s-off...thanks for the response
Sent from my HERO200 using XDA Premium App
No prob. Let me know how that works for you. You will need android sdk installed if you don't already. Easy to run though.
Sent from my HERO200 using XDA Premium App
I haven't checked in a while, but last time I did... an s-off hero cannot return to s-on status.
Sent from my HTC Hero CDMA using XDA App
theSlack said:
I haven't checked in a while, but last time I did... an s-off hero cannot return to s-on status.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
If you run the ruu in zip format it will return you to s-on if you were s-off
Yea Its Me Again With The
Modified Hero
laie1472 said:
If you run the ruu in zip format it will return you to s-on if you were s-off
Yea Its Me Again With The
Modified Hero
Click to expand...
Click to collapse
Only the eng-spl darch put up, regaws method is forever, like a diamond.
sent from a series of tubes
If you used unrevoked forever there is an s-on zip. I have used it before and it works. You do need to change your radio to .27 or lower to flash however.
I hope you ate buying that Evo off contract or from ebay and not using an upgrade. Come June or so it will be on like Donkey Kong with the 3d!
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Bought off Craigslist....$200...now if I can sell my hero for $100-$150...I will be all set....I must day the Evo is dope....time for rooting it...thanks to you all for your help....
Sent from my PC36100 using XDA Premium App
So this restored your hboot back to 1.41?
me a while, I tried all of the tutoials and guides for downgrading and one almost did it but I would lose adb every time. So here is a fully working method to go from the latest ruu 2.3.4 with radio 2.15.10 back to 2.1 with radio 2.10.00 and full root!!! Works perfectly.
Start off by following this guide... http://forum.xda-developers.com/showthread.php?t=768295&highlight=ota
When you get to the point after you run the ./rageagainstthecage-arm5.img command and it kicks you out of adb and you can't get back into adb that's ok, reboot your phone, normal reboot, not full power down, then run the ruu from here... http://forum.xda-developers.com/showthread.php?t=829783&highlight=3.26.605.1
then run the newest unrevoked, and when it reboots the phone into hboot, you have to manually run the update. Then reboot, if the phone only boots to hboot/fastboot, unplug the usb cable, pull battery, power back up, and run the update again, reboot to full boot and you will be at 2.1-update1. Delete the PB31IMG.zip from your sdcard. Re-run unrevoked, and You are ROOTED!!! Man that was quite a run, enjoy your rooted(again) phones.
UPDATE: instead of running the latest unrevoked, as it didn't work out for me, I just popped the new CWM PB31IMG.zip on the sdcard, rebooted to hboot and installed. I just went from Android 2.3.4 RUU / radio 2.15.10 to fully rooted 2.1 update1. So I know it works. Happy Flashing all
Why in the world would you.... UGH YOU HAD THE ANDROID SDK INSTALLED INCORRECTLY SO ADB WASNT WORKING
Sent from my ADR6300 using XDA App
Smokeey said:
Why in the world would you.... UGH YOU HAD THE ANDROID SDK INSTALLED INCORRECTLY SO ADB WASNT WORKING
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope it was installed right, even in that guide there are a lot of people that have that problem, because it doesn't work on 2.3.4 with radio 2.15.10
OK how about this for a question ... do you think this method could be use to root an EVO that is s-on w/ 2.3.3? Using the appropriate files of course.
jumperalex said:
OK how about this for a question ... do you think this method could be use to root an EVO that is s-on w/ 2.3.3? Using the appropriate files of course.
Click to expand...
Click to collapse
it should work with s-on, just make sure you run unrevoked-forever after to turn s-off again, assuming that's what you want
actually looks like this is my solution http://revolutionary.io/ ... just found it here http://forum.xda-developers.com/showthread.php?t=865204 but sadly no DINC support
I'm a little confused. Isn't that a Froyo Rom.zip (November, 2010) you posted? But you somehow downgraded to 2.1? Did you start out with s-on then?
iowabowtech said:
I'm a little confused. Isn't that a Froyo Rom.zip (November, 2010) you posted? But you somehow downgraded to 2.1? Did you start out with s-on then?
Click to expand...
Click to collapse
No I started with s-off, and ya, I went from 2.3.4 to 2.1. It is an ruu exe. You should be able to run any ruu you want to, as long as its a rootable version.
danwguy said:
No I started with s-off, and ya, I went from 2.3.4 to 2.1. It is an ruu exe. You should be able to run any ruu you want to, as long as its a rootable version.
Click to expand...
Click to collapse
But you typically can't go backward with the RUU's due to the "main version is older" roadblock. However, s-off aside, if you were able to revert backward (to either 2.1 or 2.2), then those are rootable. I'm just having issues here because you were s-off to start with which means you could have just shortcutted straight to the part of flashing the CWM PB31IMG and been done with it. But the fact you went backward to a rootable OS seemingly without utilizing s-off to do so leads me to believe you did this for an experiment to benefit others?
Bottom line, if you were able to revert to an older OS, the accidental s-on crowd should be able to follow in those footsteps and root from a prior OS.
I couldn't flash cwm because I ran an official ruu that removed root and everything and upgraded me to 2.3.4 that couldn't be rooted yet. But yes this was kind of an experiment to see of I could downgrade to an older OS without utilizing s-off. I really do hope this will help others who did the dumb thing like I did and do an official update, or anyone looking to downgrade to an older official OS.
The problem most people have is that they unrooted to s-on and then upgraded. If you were s-off and then upgraded with the OTA files posted, then all that would happen is you lose root and you woukd have to reflash a custom recovery. It seems that most people's issue is that they weren't s-off to begin with before they upgraded.
Sent from my ADR6300 using XDA App
Has anyone tried this on an S-ON, 2.3.4 Incredible? If not, I'm taking the plunge tonight and will post results.
One other user in the general forum isn't having luck as s-on but it shouldn't matter. The OP didn't use his s-off until the very end and was able to get back to 2.1 without using s-off to do so. That's the key here, getting back to a rootable OS so you CAN get root and s-off. I'm GUESSING the reason unrevoked failed at the end was because it was updated for Froyo. Perhaps if he'd have either went straight to 2.2 or upgraded from 2.1 to 2.2 and then tried unrevoked, it may have worked.
Just a thought...remember that slcd's on 2.1 = black screen. There's a lot of slcd's out there these days so 2.2 might be preferred if possible.
iowabowtech said:
One other user in the general forum isn't having luck as s-on but it shouldn't matter. The OP didn't use his s-off until the very end and was able to get back to 2.1 without using s-off to do so. That's the key here, getting back to a rootable OS so you CAN get root and s-off. I'm GUESSING the reason unrevoked failed at the end was because it was updated for Froyo. Perhaps if he'd have either went straight to 2.2 or upgraded from 2.1 to 2.2 and then tried unrevoked, it may have worked.
Just a thought...remember that slcd's on 2.1 = black screen. There's a lot of slcd's out there these days so 2.2 might be preferred if possible.
Click to expand...
Click to collapse
He said he started s-off, 8th post first page.
Sent from my ADR6300 using XDA App
deadsoulboy said:
Has anyone tried this on an S-ON, 2.3.4 Incredible? If not, I'm taking the plunge tonight and will post results.
Click to expand...
Click to collapse
It probably won't work because this guy started s-off and did a bunch of extra steps when he lost root after updating. Since he was s-off to begin with, all he had to do was reflash a custom recovery and superuser. It probably wont hurt for you to try, but I'm just saying most people don't get the difference between being rooted and s-off.
Sent from my ADR6300 using XDA App
AJGO23 said:
He said he started s-off, 8th post first page.
Click to expand...
Click to collapse
I know he started s-off but he only used s-off after he had successfully downgraded his OS to Eclair the way I read it. So he was already on an android OS that is rootable by way of Unrevoked and instead of dicking with Unrevoked any longer b/c it was failing on 2.1, he just decided to load CWM by utilizing Unrevoked instead. I think if he'd have been on 2.2, it may have worked.
If he did utilize s-off somewhere in between, I'm not seeing where it would have been?
iowabowtech said:
I know he started s-off but he only used s-off after he had successfully downgraded his OS to Eclair the way I read it. So he was already on an android OS that is rootable by way of Unrevoked and instead of dicking with Unrevoked any longer b/c it was failing on 2.1, he just decided to load CWM by utilizing Unrevoked instead. I think if he'd have been on 2.2, it may have worked.
If he did utilize s-off somewhere in between, I'm not seeing where it would have been?
Click to expand...
Click to collapse
2.3.4 is rootable if you have s-off. The only reason all of this worked for him is because he was s-off from the beginning allowing him to downgrade all the way down to 2.1. If he were s-on from the very beginning he couldn't have downgraded, thus everything else wouldn't have worked. Like I said in my last post, since he was s-off when he upgraded to 2.3.4, all he had to do was flash a custom recovery and superuser to regain root instead of going through that whole process. He was pretty vague in his posts though.
Sent from my ADR6300 using XDA App
AJGO23 said:
2.3.4 is rootable if you have s-off. The only reason all of this worked for him is because he was s-off from the beginning allowing him to downgrade all the way down to 2.1.
Click to expand...
Click to collapse
Absolutely agree anything is rootable with s-off.
However, s-off does not allow you to downgrade back to 2.1, nothing but a hack allows that, specifically the flash_image. And that's the thing, I'm not seeing where anyone would need s-off to make that portion of things happen. If it did, it blows the theory I admit but what step precisely would require s-off? He's not flashing any zips in the bootloader until the PB31IMG that was the official signed 2.1 zip that doesn't even require s-off in the first place, it can be flashed with s-on.
Anyway, I admit I'm still a little shaky on this but IMO we are looking a different scenario than those false positives posted in other threads. Those people didn't know they had s-off and were able to flash clockwork back, that's a given. But the key here was being able to revert to a former OS which is not an easy task and in my mind, does NOT involve the presence or absence of s-off to do so. If that can be repeated, root and s-off can both be acquired on Froyo with Unrevoked 3.
Alright guys, wish me luck.. I'm installing adb now, will post results.
I'm using a non-rooted, S-ON Droid Incredible, 2.3.4.. AMOLED.
Fingers are crossed.
iowabowtech said:
Absolutely agree anything is rootable with s-off.
However, s-off does not allow you to downgrade back to 2.1, nothing but a hack allows that, specifically the flash_image. And that's the thing, I'm not seeing where anyone would need s-off to make that portion of things happen. If it did, it blows the theory I admit but what step precisely would require s-off? He's not flashing any zips in the bootloader until the PB31IMG that was the official signed 2.1 zip that doesn't even require s-off in the first place, it can be flashed with s-on.
Anyway, I admit I'm still a little shaky on this but IMO we are looking a different scenario than those false positives posted in other threads. Those people didn't know they had s-off and were able to flash clockwork back, that's a given. But the key here was being able to revert to a former OS which is not an easy task and in my mind, does NOT involve the presence or absence of s-off to do so. If that can be repeated, root and s-off can both be acquired on Froyo with Unrevoked 3.
Click to expand...
Click to collapse
You can downgrade as long as you have the right radio before using the RUU. Since you can use the Froyo RUU to return completely to stock, I don't see why you couldn't use the official Eclair RUU to downgrade even further as well.
Sent from my Droid Incredible using XDA App
I have tried both moonshine and revone and cant seem to get s-off on my HTC One M7. When I try on Moonshine it gets to the adb part and times out and says for me to fix it. When I try revone, I get an error code -6. Any suggestions on what I can do to fix this?
DevinM7 said:
I have tried both moonshine and revone and cant seem to get s-off on my HTC One M7. When I try on Moonshine it gets to the adb part and times out and says for me to fix it. When I try revone, I get an error code -6. Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
Need more info. Specifically, what is your Hboot version?
I'm a complete noob man. I recently moved over from iphone to android. Where do I find out my HBoot version?
Sent from my HTC One using xda app-developers app
Complete noobs shouldn't S-off
#justsayin
adb reboot bootloader
look at the top for hboot version.
If it says 1.54 you can't S-off
DevinM7 said:
I'm a complete noob man. I recently moved over from iphone to android. Where do I find out my HBoot version?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That's cool bro, me too not that long ago. HTC One is my first Android, and I love it. Reboot into bootloader (hold down volume and power simultaneously, phone will reboot into bootloader mode). You'll see your Hboot version there. S-off only works on Hboot 1.44.
A word of caution from one noob to another. S-off is serious stuff, and not really needed for 90% of the mods here at xda. You can flash custom roms and recoveries, and radios, all without S-off. Just be careful, and read Everything. I mean it, I have spent countless hours here at xda reading before I did anything. The community here is very willing to help, as am I.
What have you done to your phone thus far? Unlocked? Rooted? Custom recovery or ROM?
Appreciate it guys. Yea I'm running HBoot 1.44, so I guess that solves that, lol. Yea I have rooted my phone with TWRP recovery. I was really hoping to turn s-off so I could switch over to Google play edition. Any suggestions on roms and other stuff to try out? And Thanks for being helpful and patient with me. Unfortunately I'm used to dealing with jailbroken iPhones.
Sent from my HTC One using xda app-developers app
DevinM7 said:
Appreciate it guys. Yea I'm running HBoot 1.44, so I guess that solves that, lol. Yea I have rooted my phone with TWRP recovery. I was really hoping to turn s-off so I could switch over to Google play edition. Any suggestions on roms and other stuff to try out? And Thanks for being helpful and patient with me. Unfortunately I'm used to dealing with jailbroken iPhones.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
1.44 CAN be S-off'ed
DevinM7 said:
Appreciate it guys. Yea I'm running HBoot 1.44, so I guess that solves that, lol. Yea I have rooted my phone with TWRP recovery. I was really hoping to turn s-off so I could switch over to Google play edition. Any suggestions on time and other stuff to try out? And Thanks for being helpful and patient with me. Unfortunately I'm used to dealing with jailbroken iPhones.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The fact that you're coming from the jailbreak community is good, imo. Thing is, it's practically impossible to brick an iPhone, even a jail broken one, as you could always just restore the iPhone. S-off definitely gives you the opportunity (possible but not probable, depends on what you do) to brick your phone permanently. That being said, I used Revone and it worked well and easily. Read and follow the instructions in the OP for Revone to a T. I recommend reading about the first 50 pages in that thread before you try anything also (ignore the last half of the Revone thread for the most part, just page after page of people shocked and complaining the can't S-off Hboot 1.54). Some people get Revone to work pretty easily, some try 20 times and then it just works.
Here: http://forum.xda-developers.com/showthread.php?t=2390346 is a rom for GpE 4.3 that you could flash right now as you are, but yeah, you have to be S-off to fully convert.
From spending so much time here lately, some observations one noob to another:
-Either stay stock or go custom (I recommend custom), and stick to it. A lot of people here went custom (including S-off), and f'd up their Ones trying frantically to get back to stock for an OTA. Forums were littered with people who messed that up.
-Careful with TWRP. I use it and like it, but be very careful when you are wiping Dalvik/cache. Ton of people here blaze through the wipe options, then all it takes is a swipe, and suddenly they've erased everything and can't boot their phone. Just always triple check before that final swipe.
-if you modify your Hboot in any way, never ever go S-on until you flash a stock Hboot. Doing so will permanently brick your phone. I can't think of a reason to ever go S-on, but that was part if the whole return to stock for OTA scenario.
Hope this all helps!
Thanks so much for your help man. You have been a great help. So let me make sure I have this right. I have to change my HBoot version to be able to s-off at this point?
Sent from my HTC One using xda app-developers app
DevinM7 said:
Thanks so much for your help man. You have been a great help. So let me make sure I have this right. I have to change my HBoot version to be able to s-off at this point?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You're welcome, happy to help!
No! If you are n Hboot 1.44, you should be able to go S-off fine. I recommend Revone, only because that's what I used. Just read, read, read, and follow the instructions to the letter.
Thanks! Do you know the URL to the OP for revone?
Sent from my HTC One using xda app-developers app
DevinM7 said:
Thanks! Do you know the URL to the OP for revone?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582
Here yah go, no problem
Bear with me as this is my first HTC device in a long time. I got it used and the bootloader is unlocked but says **TAMPERED**. I understand I could relock it and return it to stock but it seems I need S-OFF in order to do this. Currently, the phone is still S-ON. What would be the correct steps in getting rid of the tampered message? If you can just guide me in the right direction, it would be much appreciated. Thank you.
There are plenty of guides to s-off, look in the original development section...
Sent from my HTC One using XDA Premium 4 mobile app
xxquicksh0txx said:
There are plenty of guides to s-off, look in the original development section...
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So, I do need S-OFF to relock? I know there are guides but not sure which is the first step.
Nicraz said:
Bear with me as this is my first HTC device in a long time. I got it used and the bootloader is unlocked but says **TAMPERED**. I understand I could relock it and return it to stock but it seems I need S-OFF in order to do this. Currently, the phone is still S-ON. What would be the correct steps in getting rid of the tampered message? If you can just guide me in the right direction, it would be much appreciated. Thank you.
Click to expand...
Click to collapse
Get s-off using revone
http://forum.xda-developers.com/showthread.php?t=2314582
And don't go s-on again unless ABSOLUTELY necessary. There are quite a few prerequisites for s-on, otherwise you'll brick your phone!!!
Sent from my HTC One using xda app-developers app
Nicraz said:
So, I do need S-OFF to relock? I know there are guides but not sure which is the first step.
Click to expand...
Click to collapse
You don't need it to relock, but it will say "Relocked" instead of "Locked"
With S-off you can change it to back Locked, like it was never touched.
The s-off guides have a list of requirements that you need before you get started if you do go that path.
Are you trying to make it look completely stock? Or just relocking? They require completely different things.
Sent from my HTC One using XDA Premium 4 mobile app
Doesn't 'tampered' just mean it's still got the custom recovery on it? Sure I've read if you get the stock one back on it goes away
xxquicksh0txx said:
You don't need it to relock, but it will say "Relocked" instead of "Locked"
With S-off you can change it to back Locked, like it was never touched.
The s-off guides have a list of requirements that you need before you get started if you do go that path.
Are you trying to make it look completely stock? Or just relocking? They require completely different things.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll head over there and make sure to read.
I'm a bit hesitant of doing anything with it. I was looking to just change it back to stock completely and possibly selling it. People who don't really root their phones may be turned off by the whole tampered thing, especially if they want to send it back to HTC for repair or something.
Nicraz said:
I'll head over there and make sure to read.
I'm a bit hesitant of doing anything with it. I was looking to just change it back to stock completely and possibly selling it. People who don't really root their phones may be turned off by the whole tampered thing, especially if they want to send it back to HTC for repair or something.
Click to expand...
Click to collapse
Once you're s-off you can remove the tampered sign, and even lock (as opposed to relocked) using revone.
As long as you're on hboot 1.44.
You can even keep it s-off because some phones come s-off by default so service centers shouldnt be able to complain about that.
Do quite a bit of reading if you do want to go back to s-on, otherwise a brick can happen!
Sent from my HTC One using xda app-developers app
nkk71 said:
Once you're s-off you can remove the tampered sign, and even lock (as opposed to relocked) using revone.
As long as you're on hboot 1.44.
You can even keep it s-off because some phones come s-off by default so service centers shouldnt be able to complain about that.
Do quite a bit of reading if you do want to go back to s-on, otherwise a brick can happen!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you very much. I just wanted a bit of guidance on what direction to take. Thanks again!!