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?
So got the Incredible S in the beginning of July and was very happy with it, beat the hell out of my old HD2 who got bricked Desided not to root this one cause it was already android and i didnt want to break the warranty. But then the 2.3.3 update came and i didnt recieve text and calls was dismissed. (it is an own thread about this issue on the forums) so i desided to try a rom from XDA to see if this could help solve the issue. It did not but i rooted the phone (S-off right?) and used it with GSM only.. today i talked with HTC support and got a hold of the RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0 802U_38.02.01.11_M_release_172670_signed.. the cusomter support guy uploaded it and i installed it with the USB cable.. the installer said everything went fine.. the phone reebots.. boots to the HTC logo screen and turns off again.. and keeps on going in the same cycle..
I can get into bootloader, but when i press "power" to choose recovery it goes straight to the white htc screen again and reebots.. what to do now? Is this one dead also?
Tried rename RUU to PG32IMG and put it on the memory card.. still no luck it says "Bootloader - Bypasses"
"TP - Bypassed"
"TP - Bypassed"
Why? And still no luck tried with two signed RUU's now.. The bootloader says
Vivo PVT SHIP S-OFF RL
HBOOT 6.13.1002
At least i want all the Revolutionary stuff gone.. Any idea? Im out of ideas right now.. Oh geez, it booted the 2.1.3 RUU.. nice.
But why would not the other room work? This is the one i have to get workin.. Any ideas?
Does the RUU got a radio in it? Please share this RUU cause I believe this is not avaible anywhere. I would give it a try then and report if I have issues.
Sent from my HTC Incredible S using xda premium
Yes I think it can be a radio conflict too, perhaps you downgraded it.
Here you go Please give a report if it work on your device
I also want to gain S-ON on my Incredible, used AlphaRevX Beta to get the S-OFF but i need it to be S-ON again, and i cant really fint the information on how to do it. These forums are amazing but very hard to navigate true, and find the information you are looking for.
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
So did it work ?
Sent from my xxx using Tapatalk .
wallytax said:
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
Click to expand...
Click to collapse
How to do this? Do i need to S-ON first? Or?
I have a Mint Condition HTC One phone I am trying to sell - Mostly just because I also own a Nexus 4 and love it - and decided I'd rather keep it and use the money on the HTC One on something else.
I'm having a hard time selling it because the "everything is unlocked" is making people scared to buy it.
It's S-OFF, SuperCID, TWRP 2.6.0.1, Bootloader Unlocked, Running 2.24 Firmware and Android Revolution 12.1, Sim Unlocked too.
It's originally a Rogers Canada HTC One
Is there any way (or guide) to completely make it stock again to help sell it? Any help would be appreciated.
Yep, just flash the Rogers RUU (if available) and then you're good to go! If there isn't one then use one of the Nandroids provided and then get the stock recovery and relock the bootloader
don't forget to go back to S-ON after flashing the RUU
herwegan said:
don't forget to go back to S-ON after flashing the RUU
Click to expand...
Click to collapse
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
bigystyle84 said:
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
Click to expand...
Click to collapse
just download the RUU (sorry, don't know if there is one for your carrier), be sure to be s-off, and then run the RUU.exe or flash the RUU.zip.
the RUU will flash stock recovery, stock rom and i think it will even relock your bootloader. and then you'll be able to download OTA-updates again.
last step is to put it back to s-on and you should be done..
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
EnIXmA said:
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thanks
I'm S-OFF using the Revone Method
I'm on firmware 2.24 and HBoot 1.54 (Still S-Off though)
If anyone has time, can somebody give me a real quick overview on what I need to do? I'll buy ya a beer!
I'm not real familiar with HTC Devices - This was my first experience and to be honest, Right now I'm wishing I didn't do this if I knew before hand I was going to flip it so fast.
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
herwegan said:
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
Click to expand...
Click to collapse
You cant run the RUU with Super CID. You will have to change it to one that matches the RUU you choose before running it, but keep s-off. Then you should be able to use the tool as mentioned above or do all the things manually. You can use my guide if you like:
http://forum.xda-developers.com/showthread.php?p=43458497
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
bigystyle84 said:
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Click to expand...
Click to collapse
you could take the latest open europe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7), or take an AT&T one.. don't really know which one would be better for your situation you'll know it better
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Click to expand...
Click to collapse
this is also an option. you can flash this nandroid backup through cwm recovery. but then you'd have to manually install stock recovery and lock the bootloader/go back to s-on. why not :good:
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Click to expand...
Click to collapse
you can stay on 1.54 if everything works fine after flashing the older firmware. the "warning text" is related to this thread: http://forum.xda-developers.com/showthread.php?t=2316726
but if you've never installed a custom HBoot you don't have to worry about this when going back to s-on. just check once if the red warning text in the bootscreen is there.
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Click to expand...
Click to collapse
hope it works :fingers-crossed:
crushalot said:
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
Click to expand...
Click to collapse
Hey, I'm trying to do the same thing as OP, and this thread has been the closest thing to my issue. I'm trying to return everything on my phone to stock, however my Canadian carrier is Bell. Currently my HTC One has the bootloader unlocked, is rooted, TWRP recovery, and TrickDroid installed.
If I understand your instructions correctly, what I should do (given I want to restore using a nandroid backup) is:
1) S-Off my phone
2) Change the CID to CWS___001 and run the ATT RUU
3) Change the CID back to my original (BM_001 is what I think it is, do you know how I can make sure? What command to run for ADB?)
4) The Nandroid backup from http://forum.xda-developers.com/showthread.php?t=2207874&highlight=bell+update for my phone is for CWM (it's this one: M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5), does that mean I have to change my recovery from TWRP to CWM at this point?
5) Use fastboot to boot the recovery --> two questions regarding this, 1) why would I not install the .zip I downloaded from step 4? 2) where do I get the recovery.img? Just the one that is in the zip? In which case, shouldn't I also has to boot the boot.img or anything else?
6) I also want to upgrade the radio, should that be done last?
Thanks for all your help!
Lastly, I'm looking for a ROM to flash afterwards, I was wondering if you had any suggestions/know of a ROM that can allow me to use the swipe2sleep features, as well as hold the back touch button to force kill an app.
Just sell it on swappa. They love rooted unlocked modded phones.
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include? Does ARHD stick with older HBOOT?
If it does update hboot,
If I turn S-OFF right away, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version in case I need to turn S-ON?
Is it safe to turn S-OFF right now, and just leave it off, just in the case if my hboot gets updated or something - I can always revert to an older version.
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
rowebil said:
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include?
If I turn S-OFF, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version?
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
Click to expand...
Click to collapse
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
squabbi said:
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
rowebil said:
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
Click to expand...
Click to collapse
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
squabbi said:
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
It's safe to go S-Off now and leave it off. hboot updates won't cause S-On
ARHD won't update your hboot.
If your hboot is updated, you must be already S-Off to downgrade.
You are on 1.44 right now. If you go s-off now, you will remain s-off even after accepting OTAs, and you can downgrade your hboot whenever you feel like. On the other hand, if you are s-on right now, and accept an OTA, you'll be upgraded to the locked down 1.54, on which you can't get s-off, nor can you downgrade.. What I suggest is going s-off right now, and doing whatever flashing you want to do.. Beware, with s-off, you can permanently brick(hard brick) your phone. If you ever want to go back to s-on, flash an RUU of ONLY 4.1.2. All roms work with s-off, so no need to worry
Sent from my HTC One using Tapatalk 4
rowebil said:
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
Click to expand...
Click to collapse
An ruu should, but if you don't want to factory restore, you can just flash the ruu.
Sent from my One using Tapatalk 4
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app
Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.
CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think