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
For those that lost root due to the TMOUS OTA 2.3.4 update, here's how I got it back.
When i updated, I had to install the stock recovery for the update to take affect. When I reverted back to stock recovery, the update flashed. I wiped my device, however, and thought that I'd be able to keep root and use Titanium. I was wrong, so here's how I fixed it:
Requirements (mostly just reminders not really telling you what to do here....)
1. S-OFF prior to updating
2. Stock Recovery to process the update
3. Disable Fastboot (Settings > Power > Fastboot)
Regain Root on 2.3.4 OTA Update
1. Download the HBoot CWM Recovery and SU flash able ZIP file from here:
http://forum.xda-developers.com/showthread.php?t=1192300
2. Place the HBoot CWM Recovery file on the root of your sdcard (i.e.. sdcard/)
3. Power off device
4. Go into HBoot (Vol Down + Power)
5. Flash the CWM Recovery image
6. Reboot
7. Delete the CWM Recovery file off of your sd card
8. Power off
9. Reboot into Recovery (can be selected through HBoot if easier)
10. Choose the SU Root ZIP file that you downloaded in step 1 and flash it
11. Reboot, you're rooted with CWM Recovery again
This method work perfectly for me. I imagine anyone who did the OTA Update and has Rooted their phone would know they went to Stock recovery to apply the update or were always on it.
Thank you for the guide
Noobish question, how did you remove CWM and go back to stock recovery? Perhaps you should add this to the OP.
I was just gonna write this up. Oh well. THANX! I'd press your thanx button but I used them all up already. Maybe a beer?
EDIT: Can you please write up a how-to for going from whatever anyone is on to TMOUS Stock 1.45.531.1 + CWM + Root ? I believe it would be really helpful and I am just too lazy to do it myself
WARNING After installing the OTA, the bootloader now says in pink on the very top
******LOCKED*******
Also, Fastboot flash commands don't work (trying to flash splash image)
HBOOT is now: 1.18.0000
Re-running Revolutionary fixes it. and extended Fastboot commands work again.
And brings it back to 1.17.1111
if someone made a nandroid backup of the ota rooted thru cwm couldnt you just load that instead using the restore option?
As always gents.... Just a tiny tiny bit of patience will go a long way.
If your already rooted through Revolutionary, there is zero need to flash any official FOTA. Not sure why some people seem to want to try it out when they're already rooted? It's NO different than the Euro 2.3.4 OTA. Peeps all over these forums and the web are saying the same thing....no change.
Actually worse if you count the fact that heavy graphically intense games crash now as they do with all stock kernel 2.3.4 Euro ROMs.
Rooted versions of the Tmous 2.3.4 FOTA are already rolling out (birgertime I believe has one out). Give it a day and there will be more that are heavily customized like the ones from Baadz, Lee, Mike etc
It's easy to understand why people want to install the latest official firmware...but if you're rooted and or want to be....there is no need to ever go through official channels (HTC/Tmo) to get your updates.
Just for the people who might be unclear. To everyone else... carry on
Hoggles said:
As always gents.... Just a tiny tiny bit of patience will go a long way.
If your already rooted through Revolutionary, there is zero need to flash any official FOTA. Not sure why some people seem to want to try it out when they're already rooted? It's NO different than the Euro 2.3.4 OTA. Peeps all over these forums and the web are saying the same thing....no change.
Actually worse if you count the fact that heavy graphically intense games crash now as they do with all stock kernel 2.3.4 Euro ROMs.
Rooted versions of the Tmous 2.3.4 FOTA are already rolling out (birgertime I believe has one out). Give it a day and there will be more that are heavily customized like the ones from Baadz, Lee, Mike etc
It's easy to understand why people want to install the latest official firmware...but if you're rooted and or want to be....there is no need to ever go through official channels (HTC/Tmo) to get your updates.
Just for the people who might be unclear. To everyone else... carry on
Click to expand...
Click to collapse
exactly what i said and what i was thinking. my brother in law & friend aren't rooted yet so they could go for the OTA but my fiancé and I are rooted. I have to make sure she doesn't install the update. i have no desire to root her sensation again. lol - for me, i'll be downloading the euro ota
EmceeGeek said:
exactly what i said and what i was thinking. my brother in law & friend aren't rooted yet so they could go for the OTA but my fiancé and I are rooted. I have to make sure she doesn't install the update. i have no desire to root her sensation again. lol - for me, i'll be downloading the euro ota
Click to expand...
Click to collapse
Keep one thing in mind though... Your brother in-law & friend should realize that if they do ever one day want to root, they should stay far away from any official HTC updates. HTC will make them agree to an online waiver that will void many parts of their warranty if they choose to use HTC's online unlocker.
If they ever plan on rooting, they should go through Revolutionary....simply because it's the best of both worlds. You can have root, HTC/Tmo will never know.... and you can now get S-ON back after Revolutionary for warranty repairs and such
Quick question. I just got my sensation replaced with a new one(previous one had problems) and it came with 2.3.4 can I still get s-off and root?
Sent from my HTC Sensation 4G using XDA App
nxt said:
WARNING After installing the OTA, the bootloader now says in pink on the very top
******LOCKED*******
Also, Fastboot flash commands don't work (trying to flash splash image)
HBOOT is now: 1.18.0000
Re-running Revolutionary fixes it. and extended Fastboot commands work again.
And brings it back to 1.17.1111
Click to expand...
Click to collapse
Thanks, I was wondering why this happened.
Nightfall983 said:
Quick question. I just got my sensation replaced with a new one(previous one had problems) and it came with 2.3.4 can I still get s-off and root?
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Yes Revolutionary works just fine, make sure you download the latest version from http://revolutionary.io/
nxt said:
Yes Revolutionary works just fine, make sure you download the latest version from http://revolutionary.io/
Click to expand...
Click to collapse
Thanks, I'll root it now
Sent from my HTC Sensation 4G using XDA App
I currently have an unlocked boot-loader, with clean-rom 4.2. I'm beginning to think my phones battery is bad (haven't done all my testing yet). I have an extended warranty with best-buy (basically they take it back in any condition). I want to revert the phone back to stock and remove the splash screen when I start the phone that say's basically "this is an experimental build......". I would also like to re-lock the boot-loader just to be safe. Any help would be awesome, I also have Mac, not sure if it's harder to do it on one or not.
You will want to first relock your bootloader, then use RUU to get back to stock. JeepFreek has written a nice tutorial on how to use RUU on a mac.
http://forum.xda-developers.com/showthread.php?t=1668156
Your bootloader will say "Relocked" instead of "Locked". There is nothing that can be done about that until S-Off is achieved.
nerk69 said:
You will want to first relock your bootloader, then use RUU to get back to stock. JeepFreek has written a nice tutorial on how to use RUU on a mac.
http://forum.xda-developers.com/showthread.php?t=1668156
Your bootloader will say "Relocked" instead of "Locked". There is nothing that can be done about that until S-Off is achieved.
Click to expand...
Click to collapse
Yeah i saw that post earlier, I already have a similar program to Virtual box and am just gonna use that. I looked up how to relock the bootloader and i know it will say re-locked. But for a technichan to see that they would have to go into the bootloader. My main concern is that when i boot the phone normaly i get the htc splash screen with red words underneath that basicly say, that this is a test version of android. I'm not sure if thats just because of my custom rom or not.
kyleallen5000 said:
My main concern is that when i boot the phone normaly i get the htc splash screen with red words underneath that basicly say, that this is a test version of android. I'm not sure if thats just because of my custom rom or not.
Click to expand...
Click to collapse
Those just appear when you have an unofficial boot image (which now gets flashed with custom ROMs once the devs figured out how to do it). I think the red text will be gone when you RUU and the boot image goes back to stock.
Okay thank you, like I said. I wont be trying any of this stuff till im sure my battery is faulty, but if i determine it is I will give these steps a try.
Thanks again
You'll never get rid of the "***RELOCKED***" text in hboot.
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.
Last time I had an HTC phone was before they introduced the S-Off / S-ON.
So, I already got TWRP installed
Working great, LTE/4G is good, I made stock backup for everything.
Planning to install the Bad Boy ROM
but can't find anything about how to set S-Off / S-ON.
I was trying to install BusyBox, Titanium Backup, Adaway, and many other Apps which requires root, all of which won't work properly because it's S-On? so I want to switch to S-Off, make the install changes, then switch it back to S-On?
Because as I understand it, when it's S-Off many Apps and even LTE/4G might not work because it needs to be in S-On ?
--- EDIT ---
in download mode it shows:
htc_ocnwhl PVT S-ON
S-off is not available yet, but hopefully it will be. If you install Badboyz ROM you will have a choice of Superuser or Magisk for root. Those apps should be able to work once you obtain root, nothing to do with S-off/S-on. S-off is mainly for flashing unsigned firmware. In all the HTC phones I have had, never once did I lose 4G/LTE when obtaining S-off.
BusyBox says it cannot write to system.
Same with Adaway, it's even a Known issue they have listed in the Help pages, that S-Off is needed to be able to modify the HOST file, when it's S-On it cannot write to it.
Hopefully we can get S-Off working on this phone, really liking this U11 so far. :good:
As far as I know there is a thread about systemless AdAway if running stock rooted with Magisk. Not sure though.
Sent from my htc_ocnuhl using XDA Labs
If it's anything like recent htc phones the stock kernel also write protects /system even when rooted. Custom kernel should fix your issues.
mattman83 said:
If it's anything like recent htc phones the stock kernel also write protects /system even when rooted. Custom kernel should fix your issues.
Click to expand...
Click to collapse
I'll try that :good:
Yes, a lot of Apps that I use that needs to write to System, heck even I myself want to replace and remove stuff from system, like all those Google Stuff.
Anyway yeah, I can't write to System partition with the stock kernel it seems.
Which of the currently released custom kernels allows to write to System?
... time to check the Dev section to see what's available :laugh:
server hiccup duplicated
AllGamer said:
... time to check the Dev section to see what's available :laugh:
Click to expand...
Click to collapse
Maybe that would have been a better idea: (1) BEFORE you did everything you did to your U11 and (2) BEFORE you started this thread.
There are lots of resources here on XDA. It seems a great number of people are just doing things to their handsets before they read up on the complications and consequences, then asking questions afterwards. (One other poster on the forum actually unlocked, flashed an alternate recovery and ROM, without making any Nandroids or backups of stock, and only THEN tried his SIM in the device, only to find that it didn't work and he has no way back now. Permission to smack the moron?)
If you have $649 to throw away, great. Otherwise, let's be careful out there and take a little more time to study before we bork our phones.
And, oh, XDA has a GREAT search function, too!
Seems like Kirisakura-OCEAN-0.2 might do the trick.
Optionally I could go with LeeDrOiD ROM, but it's based on Europe version of the stock image.
Not sure if that will affect the Radio for the American models.
AllGamer said:
Seems like Kirisakura-OCEAN-0.2 might do the trick.
Optionally I could go with LeeDrOiD ROM, but it's based on Europe version of the stock image.
Not sure if that will affect the Radio for the American models.
Click to expand...
Click to collapse
LeeDrOiD is safe. I flashed European version of roms all the time.
Yeah s-off is only needed if you want to change base firmware (radio, bootloader etc). Most usefull for downgrading the firmware.
Also S-off lets you reset the phone to LOCKED without the RELOCKED normal htcdev unlock allows for.
AllGamer said:
Seems like Kirisakura-OCEAN-0.2 might do the trick.
Optionally I could go with LeeDrOiD ROM, but it's based on Europe version of the stock image.
Not sure if that will affect the Radio for the American models.
Click to expand...
Click to collapse
I am running LeeDrOiD on sprint USDA and its working perfectly!!!!
AllGamer said:
Seems like Kirisakura-OCEAN-0.2 might do the trick.
Click to expand...
Click to collapse
Oh and do you have the dl url for Kirisakura-OCEAN-0.2 for kali? or any variation of linux I'll make it work!!! >>>>>?
I will hack it if given the tool!
jmkhenka said:
Also S-off lets you reset the phone to LOCKED without the RELOCKED normal htcdev unlock allows for.
Click to expand...
Click to collapse
Not on the U11 with its temp S-OFF shenanigans. The XTC2Clip can gain temp S-OFF on the U11 (needs a new 50 dollar adapter) but so far there is no way to set the bootloader back to locked status, it's relock only. HTC needs to release a bootloader that supports S-OFF - either through a leak or a legitimate firmware update - or S-OFF is going to be out of reach for all practical purposes for awhile. Temp S-OFF is a huge liability. Screw up one thing while you're in that state, as soon as the phone goes back to S-ON at the next boot, you've got a brick.
semi-noob here, and slightly confused... The past phones I've flashed, seemed to equate "S-OFF" to "able to remount /system as RW'..... S-ON/OFF is unrelated to /system remounting, having root access/root shell, etc?