[Q] S-OFF / SuperCID / Relocked - One (M7) Q&A, Help & Troubleshooting

Hey there
So I have been reading a bit about S-OFF and SuperCID because they keep getting mentioned on the forum but I never really took the time to know the importance of them. I was wondering if someone can take the time and briefly explain the benefits of each? From what I understood, S-OFF lets you install RUUs that may be older than the current ROM you have - as in you can install a 1.27 even though you are on 1.29 at the moment. Is that correct? And I read that SuperCID lets you install ROMs from any carrier - it would change your CID to 11111 or something like that which is universal and not locked down to a certain carrier or region. Is that information correct or am I missing something? I'll be looking to change CID when 4.2.2 is officially released for the One because my region always receives it last, so would I need S-OFF and SuperCID for that or just one of the two?
And the last thing is the bootloader. I have always thought that it was not possible to change the bootloader status from unlocked to locked, but rather from unlocked to relocked. I came across this thread, though, and it is confusing me. Is it or is it not possible?
Thank you.

you answered your own questions. as far as locked/relocked. S-off lets us do anything.

Related

[Q] Debranding HTC One | RevOne needs unlocked bootloader?

Hi, new to HTC here
So I plan to get a HTC One and debranding will bethe first thing I'm gonna do. I've been searching though XDA and Google.
I understand the S-off can be achieved using RevOne's method, and if my device is S-offe I can change it to other (Super)CID
I've got few things I'm not really sure though:
1. Does Revone method (and the whole debranding process) require unlocked bootloader, I wish to remain vanilla if possible
2. Do I have to use SuperCID? can I used other CID? I need CID/RUU containing my native language.
2. After changing CID do I need to flash new RUU or can I just wait for the OTA to arrive and replaced my branded FW?
Well.. at the very least, I will appreciate if anyone can point me where to start.
I have somewhat read through the RevOne and SuperCID threads.. but testimony from those with success would be invaluable.
EDIT: did more research.. so should anyone be interested:
http://forum.xda-developers.com/showthread.php?t=2327586&highlight=debrand
http://forum.xda-developers.com/showthread.php?t=2183023&highlight=debrand
Any opinion and answers will be still appreciated!
Thanks.
Hi Don't know what your native language is, but if it's Dutch I just debranded my HTC One from T-Mobile and received the latest OTA in the Netherlands.
I wrote a tutorial for it on a Dutch forum.
to put it simple
I S-OFFed an unlocked via Revo method
Changed CID to HTC__001 (need to find the best CID for your country)
Ran the proper RUU
Received OTA
You can then proceed to lock the bootloader again with revo method (won't show tampering and stuff)
and even go S-ON again if you want. (I didn't)
This shall give you a vanilla HTC One without branding that shall receive OTA's directly from HTC.
@Rubman
Thanks for chiming in!
No worry, HTC CID Lists are everywhere on Google (I'd like to use the HTC SEA CID for what it's worth).
I see, I also have received confirmation RevOne can be done without unlocking bootloader.
While I generally understand the debrand process I think it'll be handy to also have your tutorial. Can I get a link?
Don't speak Dutch, but I think Gtranslate will do, hehe.
Thanks again.
Sent from my MK16i using xda app-developers app
Sure you can have a link, I plan to write the tutorial over here as well but very busy ATM, but it's basicly just a collection of Revone CID change and then RUU install.
http://gathering.tweakers.net/forum/list_message/40436246#40436246 Just copy the post from the dude with the headbanging dog to Gtranslate and I wish you good luck.
Debranding/CID
WhizzWr said:
Hi, new to HTC here
So I plan to get a HTC One and debranding will bethe first thing I'm gonna do. I've been searching though XDA and Google.
I understand the S-off can be achieved using RevOne's method, and if my device is S-offe I can change it to other (Super)CID
I've got few things I'm not really sure though:
1. Does Revone method (and the whole debranding process) require unlocked bootloader, I wish to remain vanilla if possible
2. Do I have to use SuperCID? can I used other CID? I need CID/RUU containing my native language.
2. After changing CID do I need to flash new RUU or can I just wait for the OTA to arrive and replaced my branded FW?
Well.. at the very least, I will appreciate if anyone can point me where to start.
I have somewhat read through the RevOne and SuperCID threads.. but testimony from those with success would be invaluable.
EDIT: did more research.. so should anyone be interested:
http://forum.xda-developers.com/showthread.php?t=2327586&highlight=debrand
http://forum.xda-developers.com/showthread.php?t=2183023&highlight=debrand
Any opinion and answers will be still appreciated!
Thanks.
Click to expand...
Click to collapse
Did you get the One? What did you discover about CID? Changes GSM band reception? Can this be changed for carrier jumping?
I have a Sprint One. Am no longer with Sprint and wondering what advantage it would be to change CID. I have 2 updates to get and am researching options first. Anyone have knowledge, suggestions?
Rom: Sprint stock 1.29
S-off
Unlocked
T removed
Hboot: 1.44 stock
Twerp 2.6.3
Revone
SuperSU

[Q] [Q} Returning to stock on 2.24.401,1

Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Clivectmob said:
Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 Check this guide out
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Clivectmob said:
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Click to expand...
Click to collapse
Run a stock ROM like found in mike1986's thread, install the stock recovery and relock your bootloader ... That's all you can do at the moment because you can't go S-Off on Hboot 1.54 so the tampered flag will have to stay until you can.
Read through this, http://forum.xda-developers.com/showthread.php?t=2265618 .. there's everything there that you need to return to stock and receive OTA updates while being S-On. The only time you'll have an issue is if you can't go S-Off to remove the tampered flag and change it from relocked to locked, only an issue if you need to return it under warranty for anything that's happened as a result of you unlocking the bootloader and flashing stuff.
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Clivectmob said:
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Click to expand...
Click to collapse
According to the guy I spoke to at HTC when I sent mine back the other day, it shouldn't. He said they should only refuse to cover repair under warranty if the fault is caused by something you've done, i.e, flashing stuff or deliberate damge or something. Unfortunately that's the risk you take if you need to return it, unless there's a method to change the flag by being S-Off you just have to either not risk it and wait until you can go S-Off and be sure to remove all traces of messing, or you return it and hope for the best lol
Well, I don't need to get it fixed or anything. Just had me play and wanna return it back to normal. I have done as I said I would in the first post and applied a small application update from HTC, so it appears to have worked. As expected, I have Re-locked and Tampered displayed. Will Just wait for S-off to emerge and deal with it then. Thanks for all the replies.

[Q] Before messing with US unlocked to get 4.2.2 OTA while 4.3 arrives

First of all, hello to you all!
I have a US Unlocked with CID BS__0001 (same as Developer Edition) with everything stock, not even rooted. I already know that 4.3 is coming next month if HTC fulfills its promise but I want 4.2.2 to get rid of the black bar and get the AE/AF camera improvements.
After reading tons, and I means of threads and posts, I have a general understanding on how to proceed and what to do to get 4.2.2 OTA but I want confirmation from you guys on a few topics. I will enumerate the steps and ask a question(s) on each one.
1.- I need to unlock the bootloader via HTCDev or Revone. Then S-OFF with Revone (read about Moonshine but it seems that most folks are using the former). Going S-OFF will impact battery life? I remember reading about an error reporting service or something like it that will always run after going S-OFF. Is this true? Does it impact battery/performance in any way?
2.- After S-OFF, I will need to change my CID to SuperCID, install a stock WWE RUU and change the CID to one that already got 4.2.2 update, like HTC__001. Then the OTA updates will show up. Flashing the stock RUU posted on this guide won't affect any of the radios of my phone in any way, right? I don't want to risk getting poor reception/speeds or Wi-Fi range.
3.- After having all the OTA updates installed and running 4.2.2, I want to be able to receive the 4.3 OTA when it becomes available. Should I just change back my CID to BS__0001 and the update will show up? I also need to relock the bootloader, right? Are these the only two things to do?
I've also read that S-OFF is not possible at the moment after updating to 4.2.2. I don't want/need it as long as the 4.3 OTA can be installed normally as I'm more than happy with the One stock stuff. What do you guys recommend? Do I keep S-OFF or S-OFF?
I appreciate you taking the time to read this and answer my questions. If you have any other input, comments, suggestions or advice before I start messing with my phone, I'll be more than grateful.
Thanks!
ajua said:
First of all, hello to you all!
I have a US Unlocked with CID BS__0001 (same as Developer Edition) with everything stock, not even rooted. I already know that 4.3 is coming next month if HTC fulfills its promise but I want 4.2.2 to get rid of the black bar and get the AE/AF camera improvements.
After reading tons, and I means of threads and posts, I have a general understanding on how to proceed and what to do to get 4.2.2 OTA but I want confirmation from you guys on a few topics. I will enumerate the steps and ask a question(s) on each one.
1.- I need to unlock the bootloader via HTCDev or Revone. Then S-OFF with Revone (read about Moonshine but it seems that most folks are using the former). Going S-OFF will impact battery life? I remember reading about an error reporting service or something like it that will always run after going S-OFF. Is this true? Does it impact battery/performance in any way?
2.- After S-OFF, I will need to change my CID to SuperCID, install a stock WWE RUU and change the CID to one that already got 4.2.2 update, like HTC__001. Then the OTA updates will show up. Flashing the stock RUU posted on this guide won't affect any of the radios of my phone in any way, right? I don't want to risk getting poor reception/speeds or Wi-Fi range.
3.- After having all the OTA updates installed and running 4.2.2, I want to be able to receive the 4.3 OTA when it becomes available. Should I just change back my CID to BS__0001 and the update will show up? I also need to relock the bootloader, right? Are these the only two things to do?
I've also read that S-OFF is not possible at the moment after updating to 4.2.2. I don't want/need it as long as the 4.3 OTA can be installed normally as I'm more than happy with the One stock stuff. What do you guys recommend? Do I keep S-OFF or S-OFF?
I appreciate you taking the time to read this and answer my questions. If you have any other input, comments, suggestions or advice before I start messing with my phone, I'll be more than grateful.
Thanks!
Click to expand...
Click to collapse
1. S-off will not produce a noticeable drop in battery and no issue with performance.
2. You also need to make sure that the rom you flash supports your MID as well. You can "trick" the android info.txt file to cover this issue before you flash. There are threads around that show you how. The firmware you flash needs to sync up with the rom you flash, or you will run into radio issues, etc. Possibly even brick.
3. If you are running the HTC_001 rom, you won't be able to receive the BS_US001 OTA. For that, you would need to flash back to BS_US001 stock, which of course, would render all the work you put into flashing 4.2.2 moot. Basically, if you convert your phone to HTC_001, you'll be using those updates, not BS_US001 updates. For a buggy incremental update before 4.3, not worth it in my opinion. For any OTA, unless your device came shipped unlocked, you need to re-lock before you can OTA.
In your situation, I would re-lock (unless it shipped unlocked), s-off and wait for the 4.3 update. Hope this helps.
I unlocked my bootloader the day I bought my One , six months ago. Got S off via revone as soon as I saw it .
I haven't needed to relock bootloader to get OTA updates.
Sent from my HTC One using xda app-developers app
kibmikey1 said:
1. S-off will not produce a noticeable drop in battery and no issue with performance.
2. You also need to make sure that the rom you flash supports your MID as well. You can "trick" the android info.txt file to cover this issue before you flash. There are threads around that show you how. The firmware you flash needs to sync up with the rom you flash, or you will run into radio issues, etc. Possibly even brick.
3. If you are running the HTC_001 rom, you won't be able to receive the BS_US001 OTA. For that, you would need to flash back to BS_US001 stock, which of course, would render all the work you put into flashing 4.2.2 moot. Basically, if you convert your phone to HTC_001, you'll be using those updates, not BS_US001 updates. For a buggy incremental update before 4.3, not worth it in my opinion. For any OTA, unless your device came shipped unlocked, you need to re-lock before you can OTA.
In your situation, I would re-lock (unless it shipped unlocked), s-off and wait for the 4.3 update. Hope this helps.
Click to expand...
Click to collapse
Thanks for replying. I'm willing to do this for two things. One is to learn how to do it and gain experience as the only other experience I had flashing and rooting was with the original Kindle Fire. The second one is to get rid of the black bar and get the camera improvements, no matter how lesser they are.
About your #2 point, I think that my US unlocked MID is supported by the RUU that are available in the collection thread. If the RUU supports my MID, there won't be any issue with radios I guess.
About your #3 point. I don't mind spending a few hours doing this. After getting 4.2.2 OTA using HTC__001 (or any other CID), will I be able to revert back to BS_US001? I ask this because I would like to do it to get the intended 4.3 OTA for my exact phone model when it's available, not get stuck with HTC__001 and its updates. If I keep S-OFF then I think I will be able to revert right? Is this correct? If I can't revert to stock BS_US001 I guess I will skip my plan and wait another month to get 4.3.
Thanks again!
paul_59 said:
I unlocked my bootloader the day I bought my One , six months ago. Got S off via revone as soon as I saw it .
I haven't needed to relock bootloader to get OTA updates.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It's good to know that. Did you do the CID changing to get 4.2.2 OTA? If so, leaving S-OFF can allow me to revert back to BS_US001 when 4.3 arrives? Thanks!

[Q] What's all the fuss about S-OFF?

So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
Its not important at all
Sent from my HTC One using xda app-developers app
With S-off you can flash everything you want on your phone . Downgrade is a most comun reason.
Sent from my HTC 802w
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
Some carriers are the only users option in their area.
Like for me, that carrier would be Verizon. They have great coverage.
But they also happen to be evil and had HTC block our HTC One's MID from being able to use the HTC Bootloader Unlock bin file.
It will fail the initial checks after getting the token from you.
We also have the 1.54 hboot as stock, so there is no using moonshine, or facepalm, or any other previous method as of yet.
So in order for poor folks with carriers that strongarm smaller companies like HTC into doing things against their wishes and our wishes,
S-off allows us to then change CID,MID, etc,...as well as then go and unlock the bootloader as we should be able to do by choice.
That's why they built it and added in a warranty void warning, so we could make that choice if we so choose.
Anyway, that should make it more clear to you now at least, sorry for the extra carrier rant, lol.
Plus the obvious other advantages of flashing radios, kernels, etc,...without doing fastboot.
Ah okay. So S-off does similar to the HTCDev unlock? If I used S-Off instead could I get rid of the ugly warning text on boot?
Htc dev unlock only needed partitions. S-off unlock ALL
Sent from my HTC 802w
Stephen304 said:
Ah okay. So S-off does similar to the HTCDev unlock? If I used S-Off instead could I get rid of the ugly warning text on boot?
Click to expand...
Click to collapse
Yes you could get ride of the warning text with s-off, with s-on you cannot.
Everything what's said above + more , for example if htc one windows version ever gets ported s-off users can have it , we can also convert our device into ge edition / dev edition / flash whatever comes thru your mind , even splash screens , use modified bootloaders , we can also unlock bootloader without need of HTC official unlock process , we can lock it as well ( s-on can only relock it ) we can also completely hide we ever were rooted / unlocked for warranty reasons while s-on can't.
We can also use super cid which allows us to flash any ruu or use any region / carrier roms.
We can also downgrade bootloader or flash any other.
That's mainly it , also for example us with s-off have writeable partitions while for example s-on users still don't on 3.22 base.
And at the end maybe a good thing for you and some less advanced or less knowledgeable ppl s-on is a good thing since with s-on phone is practically indestructible software-wise , while with s-off small mistake even in fastboot could brick the device.
Sent from my HTC One using XDA Premium 4 mobile app
santod040 said:
Plus the obvious other advantages of flashing radios, kernels, etc,...without doing fastboot.
Click to expand...
Click to collapse
With the HTC One, you can flash radios and kernels in the recovery if you unlock the bootloader...
>> Sent from the abyss <<
Stephen304 said:
So I read about S-OFF and I can gather that it has something to do with unlocking the bootloader. I'm a little confused since I just went to the HTC website and did the official unlock steps, I'm now rooted with clockworkmod CM10.2, and my bootloader is S-ON.
Basically, I never did S-OFF so I'm confused about why it's so important and why didn't I have to do it?
Click to expand...
Click to collapse
To get official OTA with updates to firmware, hboot and everything you have to get them from your carrier, and this depends on your CID. You cannot change this on S-ON. So basically your are bound to your carrier for life, they may but also may not release updates (like for ex. carriers in USA skipped 4.2 if I am not mistaken). You can of course flash custom ROM using dev unlock, but it won't update the firmware.
Ah okay thanks for the info! I have one more question about S-OFF if you don't mind: If I S-OFF and disable the red warning (flashing an unsigned fw), then S-ON again, would the warning come back?
If you do s-on with modified hboot will result an instant and forever brick. Dont do that.
Sent from my HTC 802w
Stephen304 said:
Ah okay thanks for the info! I have one more question about S-OFF if you don't mind: If I S-OFF and disable the red warning (flashing an unsigned fw), then S-ON again, would the warning come back?
Click to expand...
Click to collapse
Why exactly would you want to go back to S-ON?
Sent from my HTC One using Tapatalk 4

Beginner rooting questions

Hey all, I recently acquired an HTC one m7 and I previously had an xperia z1. I had unlocked the bootloader and rooted my previous phone but coming to m7's page I've found that there are many things new here. First is the S-Off business.
I basically wanted to ask if there's a specific order in which I should go. For example S-off first, then root then unlock bootloader or anything like that.
And secondly, for the xperia line, there was a tool called Flashtool that basically did all the things you need to unlock/root your phone. I was wondering if there's something like that for the One M7 so that I can flash stock firmware if need be.
Also, I'm on kitkat 4.4.3 HBOOT 2.49 so should I keep some things in mind?
Also, what is CID?
Sorry for so many questions, any help is appreciated
Thank you!
uhh, I will tell you what i know here related to your questions.
Firstly, if you want to customize your phone, first thing is to unlock your bootloader which is easy to do. Then you need to flash a custom recovery. After that you can do what you like.as to s-off, if you don't have special requirements,I think it's not a must step.
Secondly,there is indeed a tool for htc one.you may find it in one's development forum.
May that help you!
来自我的 HTC M8Et 上的 Tapatalk
If I unlock bootloader before S-off, will I be able to get back "UNLOCKED" status or will it be "RELOCKED"
ggnoobteam said:
If I unlock bootloader before S-off, will I be able to get back "UNLOCKED" status or will it be "RELOCKED"
Click to expand...
Click to collapse
yeah you can get back to full locked status, but only with s-off, be careful though, theres not alot about for the dual sim really, you can pretty much find everything in the general section for the dual. http://forum.xda-developers.com/showthread.php?t=2495697
I think for your HBOOT, use Rumrunner to s-off. http://rumrunner.us/
EDIT: sorry for your HBOOT version you needed to use firewater s-off tool, but as thats discontinued, you'll have to try sunshine s-off tool which will cost $25 if it can s-off your device, it will run some checks first, if it can then you pay and it proceeds, if it cant it will let you know why and you dont pay: http://theroot.ninja/
if I remember correctly, CID is carrier identification.
the main things that matter, and that you need to take note of it your planning on changing them are CID, MID, HBOOT version and OS or version main (same thing really)

Categories

Resources