Database Info

if s-off update is coming, could carriers "block" this or switch it s-on?

read in a german board, that someone mailed to vodafone about the upcoming update to get s-off.
VF answered that they dont know if they remove the locked bootloader in the upcoming updates.
so my question: is it tecnically possible for VF to switch s-on again if they are getting a s-off update from htc? would this be legal?
just asking because just received my branded sensation on friday and if the unbranded sensation is coming the next 2 weeks i could change it.
but i only would do this if there isnt any way for the vodafone branded version to get s-off.
hope u can get me

The answer to your question would be yes your carrier could switch you back to S-On with an OTA, or send out an OTA with a locked bootloader/refuse to send out an OTA with an unlocked bootloader.
I would think though that HTC would just release the unlocked bootloader update, on their website for us to flash ourselves through the Rom Update Utility.
It's also unclear how they are trying to work with the carriers so that we'll have nice, bloated, roms with unlcoked bootloaders, instead of HTC just releasing a cleaned up rom. WOn't matter anyway cause once we have # we're gonna get rid of anything we don't want anyway.

[Q] Question about s-off and revolutionary?

Hi All.
Quick question, I have rooted my sensation and s-off'ed, sweet.
Here is me question, what happens if our friends at HTC update the part that made the s-off possible? Will we get the updates or will only the users who did not tinker with the firmware get them?
Cheers folks.

HTC has stated that there new HTC-DEV site will be where you will be able to S-off your device, its not gonna come in an OTA push, IMO revolutionary has got us S-off, so who care what HTC has coming for S-off....its a little late, besides if you S-off with HTC they want to document who is S-offing their devices.......eff em and just enjoy your no strings attached S-off.

Number 1...It is never a good idea to take an OTA on your phone if you have it rooted.
Number 2...OTA's may contain patches to exploits that were used to obtain s-off.
Number 3...OTA's may or may not s-on your phone depending on how the devs obtained s-off in the first place.
Moral of the story is if you want to maintain root never OTA

i own a sensation device
if i use this revolutionary tool to s-off, recovery and root, is it possible to s-on later? (e.g. to give my phone to htc service to be in warranty)
If i just use the ruuxxxxxx.exe for my device to put the official rom , the phone will be s-on again? or is there any other way?
and wht about official OTA updates? how is going to be achieved?

There is a way to to gain s-on again but it's risky atm. Look for the guide in the stickies in the development forum.

You will not get an OTA on a rooted custom ROM.. end of story!!
So enjoy

emm_stra said:
i own a sensation device
if i use this revolutionary tool to s-off, recovery and root, is it possible to s-on later? (e.g. to give my phone to htc service to be in warranty)
If i just use the ruuxxxxxx.exe for my device to put the official rom , the phone will be s-on again? or is there any other way?
and wht about official OTA updates? how is going to be achieved?
Click to expand...
Click to collapse
Yes it is possible to make you device s-on again just be sure to follow everything to the letter and don't screw up. Also why would you want to. If anything permanently root it and stick with that.
HTC Sensation Stock Perm_Rooted 4.3.3
HTC Sensation Stock Perm_Rooted 4.3.3

Bobguy21 said:
Yes it is possible to make you device s-on again just be sure to follow everything to the letter and don't screw up. Also why would you want to. If anything permanently root it and stick with that.
HTC Sensation Stock Perm_Rooted 4.3.3
HTC Sensation Stock Perm_Rooted 4.3.3
Click to expand...
Click to collapse
thank you
what about the other questions???

Sorry it took so long you cannot update when rooted. Because of clockworkmod recovery. But just install a stock bases ROM the has the update like I did. hope this helps.
HTC Sensation LeeDroid 2.3.4 Perm_Rooted

Problem with DeBranded Sensation & 2.3.4 update...Error Status 7

Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J

y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.

Something has changed...revolutionary now supports the new "locked" bootloader!

Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.

So how can I update my sensation with s-off?
A bug in me from being updated.

That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.

Hi
I have the exact same problem as yours, what can we do to update it?

Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.

H3G__001 UK Stock image anyone?

EDIT:
Here is the official RUU for H3G (Three UK) standard model Sensation
Was pointed out by another forum member, so I have mirrored it onto Mutliupload.
http://www.multiupload.com/5IQK830UIJ
Now everyone who has to send their Sensation supplied by Three in for warranty, just...
Make sure CID is H3G__001 (or SuperCID 11111111, though if CID is this, you don`t really need this ROM)
Once CID is correctly set, reboot into bootloader menu and run the RUU.
Having correct CID enables you to receive OTA updates once you have installed the RUU / ROM. If you update OTA, bare in mind, that it will also update your HBOOT to 1.18.0000 *Locked*
So once you have done this, do S-on to resecure your NAND and there you go... Ready for a warranty return...
My 0.0000000000002p worth anyway.
Thought it might help people who are on Three...
Tested and confirmed by me
Hello everyone!
I`m sorry to trouble everyone, but I was wondering if anybody had a backup of the original three uk (CID: H3G__001) ROM?
I have changed my CID and got Android Revolution installed.
I would just like a copy of this original ROM for warranty purposes.
I have looked at the stock ROMs pages and I can see the generic pyramid roms, however I keep drawing a blank when it comes to anything from H3G (three)
Any advice anyone could give?
or maybe...
1) Would someone who owns a UK H3G sensation (standard one) could upload an image somehow?
2) Would I be able to create a ROM indestinguishable from the original one installed (which includes startup logos OEM three crapware etc...)
3) Yes I was a complete dipsh*t for not making a nandroid backup (I was a complete Android virgin, iPhones were my bag)
Any advice/flaming is much welcomed!
I HAVE FOUND THE RUU!!!
Made a multiupload link for it so it is easier to find. Will put the link on as soon I`ve got 8 posts!

N10AP said:
Hello everyone!
I`m sorry to trouble everyone, but I was wondering if anybody had a backup of the original three uk (CID: H3G__001) ROM?
I have changed my CID and got Android Revolution installed.
I would just like a copy of this original ROM for warranty purposes.
I have looked at the stock ROMs pages and I can see the generic pyramid roms, however I keep drawing a blank when it comes to anything from H3G (three)
Any advice anyone could give?
or maybe...
1) Would someone who owns a UK H3G sensation (standard one) could upload an image somehow?
2) Would I be able to create a ROM indestinguishable from the original one installed (which includes startup logos OEM three crapware etc...)
3) Yes I was a complete dipsh*t for not making a nandroid backup (I was a complete Android virgin, iPhones were my bag)
Any advice/flaming is much welcomed!
Click to expand...
Click to collapse
ya not on ya own there, I have done several flashes, always backing up original 1st, but for some reason this step was "missed" when i flashed arhd to

There's an RUU somewhere, search for it
Sent from my HTC Sensation Z710e using xda premium

I have searched everywhere I can think of. I am aware of the stock HTC ruu files. These seem to be the generic ones and they are incompatible with my CID. I have changed my CID but would just be nice to find the proper RUU so I can change it completely to stock, and not just to the generic one. I'm sure changing the CID will invalidate the warranty.
Matty
Sent from my HTC Sensation XE with Beats Audio using xda premium
EDIT:
The Three Stock RUU works 100%. For newbies... Remember:
CID must be 11111111 (SuperCID) or H3G__001 to receive Over-The-Air updates. To change CID, search elsewhere! There are TWO underscores in the CID
To avoid 155 error when running RUU, run RUU when in recovery... Use adb to get into recovery or pull battery / vol down / power... You know the score!
I`m sure all this has been posted a thousand times, but I`m hoping it will help people who are on Three UK (Hutchison 3G).

Many thx
Sent from my HTC Sensation Z710e using XDA App

[Q] cant update back to 2.3.5 after downgrading hboot and whatnot

okay so I haven't quite got used to my HTC yet, am so used to my old nexus s, so that could be why I am confused.
Basically as soon as i got the phone the ota updated to 2.3.5 sense 3.0 and all was fine but then i decided to downgrade my Hboot so i'm back to the 98.000 or whatever and it works fine, i used revolutionary, re-romed a lot!! and then took rev off, so its back to S-on and Hboot locked... the only thing is that since being back on sense 2.1 i wondered if i could push the ota update back (no longer showing up) or if someone had the RUU? mines the VODAFONE version though so the normal europe one doesn't work trust me.
if anyone could help it would be much appreciated, thanks.

If your phone is vodafone branded, then the CID setting would lock you to using vodafone RUUs / OTAs, hence generic HTC / europe ones would fail.
To solve that you can either:
1. Use XTC clip to get SuperCID or
2. Create Goldcard
Both methods allow you to flash non-brand-authorised RUUs / OTAs.
Hope this helps!

i used the goldcard and ran the RUU straight after and it worked perfectly THANK YOU! .. me and my boyfriend had made a goldcard before but we never really knew what it did lol.. now i know