Database Info

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.

Command Error when changing CID

Hi folks,
I have unlocked and s-offd my Voda HTC Chacha.. installed a WWE Rom but havent recieved any OTA since then.. I am on 1.19 and there is a 1.54 OTA out..
just checked the CID through adb and its set to Super CID 11111111 instead of generic HTC__001. Tried changing it but I get Command Error. Any idea or solution for this?
Also, Is this the reason why no OTA are showing up?
If no, please advise how can I update the phone via OTA
Many thanks

What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK

qzfive said:
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
Click to expand...
Click to collapse
Here are the full details mate:
Android 2.3.3
Software 1.19.206.2
Baseband 47.14.35.3030h_7.47.35.17
Kernel 2.6.35.10-g8db500e
cheers

Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.

qzfive said:
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
Click to expand...
Click to collapse
Fantastic mate, downloaded it as we speak..
not sure how it stayed on 1.19 as after I used XTC Clip, the logos and boot image were gone so I assumed I had a stock rom.. oh well.. everyday is a learning day..
I will let you know how I get on..
cheers for your help mate..

Update... Installed the 1.33 which then took the OTA update which is all good... However I still can't change the CID to HTC__001.. (currently set at 1111111)
Sent from my HTC Sensation Z710e using Tapatalk

why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone

ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
I know but it doesn't help with OTA updates
Sent from my HTC Sensation Z710e using Tapatalk

ok, but..
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
True, but it forces non-qwerty keyboard users to manually modify the layout in /system/usr/
as described here , because CID is taken into account on default layout.
Once you know the trick, it's OK, but really annoying to do every time you install a new ROM

[Solved] Update branded phone using unbranded RUU + Goldcard

Hello,
I have a Desire S T-Mobile UK Branded phone. S-On and not rooted (further phone info at the bottom of this post).
I am wondering if it is possible (using a goldcard?) to manually update it using an unbranded RUU from this thread.
Also, if I was to update it using this method, would I have to keep the goldcard in the phone? And would I receive any future OTA stock updates from HTC?
If this is possible are there any risks involved or negative results? If so any preferred ways of updating the phone?
After much research I have been unable to find an explicit answer as to the results of doing the above for this phone. Having never performed anything like this before, I want to be certain before jumping in and being a new member I am unable to post in the perhaps more relevant development section/ threads.
Thank you in advance,
Mike
Phone Information:
Software Build number: 1.47.110.3 CL78999
SAGA PVT SHIP S-ON RL
HBOOT- 0.98.0002
RADIO- 3805.06.02.03_M
CID: T-MOB005

How did you obtain your CID?
I also have a branded D-S and would like to know if getting OTA updates is possible.

m91wilson said:
Hello,
I have a Desire S T-Mobile UK Branded phone. S-On and not rooted (further phone info at the bottom of this post).
I am wondering if it is possible (using a goldcard?) to manually update it using an unbranded RUU from this thread.
Also, if I was to update it using this method, would I have to keep the goldcard in the phone? And would I receive any future OTA stock updates from HTC?
If this is possible are there any risks involved or negative results? If so any preferred ways of updating the phone?
After much research I have been unable to find an explicit answer as to the results of doing the above for this phone. Having never performed anything like this before, I want to be certain before jumping in and being a new member I am unable to post in the perhaps more relevant development section/ threads.
Thank you in advance,
Mike
Phone Information:
Software Build number: 1.47.110.3 CL78999
SAGA PVT SHIP S-ON RL
HBOOT- 0.98.0002
RADIO- 3805.06.02.03_M
CID: T-MOB005
Click to expand...
Click to collapse
If you install the unbranded RUU using a goldcard, then you will get OTA notifications for the unbranded ROM and not your original TMOBILE ROM.

Yeah you can do what you are saying. Not sure if you'd get ota's though, maybe the unbranded ota updates wouldn't be pushed.
You only need to keep the goldcard in while installing the RUU. To be safe rather don't keep it in afterwards, keep it safe.
You can install it either by flashing the ROM.zip (I think) or by running the RUU .exe

Thanks for the replies, yes I understand that the RUU will essentially wipe the phone and install the new, unbranded version.
So as long as I use the goldcard then there is essentially no risk in the procedure? And I will be left with an unbranded version of the HTC/ Android software, without the additional apps from my network provider?
foX2delta said:
Yeah you can do what you are saying. Not sure if you'd get ota's though, maybe the unbranded ota updates wouldn't be pushed.
You only need to keep the goldcard in while installing the RUU. To be safe rather don't keep it in afterwards, keep it safe.
You can install it either by flashing the ROM.zip (I think) or by running the RUU .exe
Click to expand...
Click to collapse
trifonius said:
How did you obtain your CID?
I also have a branded D-S and would like to know if getting OTA updates is possible.
Click to expand...
Click to collapse
I got it using CID Getter which is a simple app available on the market, I am unable to link to it, being a new user.

m91wilson said:
I got it using CID Getter which is a simple app available on the market, I am unable to link to it, being a new user.
Click to expand...
Click to collapse
Thanks, I found it.

I have successfully installed the unbranded RUU, -
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822, from this thread.
Just incase any others in a similar position happen to find this thread -
I did it using a goldcard which was not very difficult to make, when following the various guides out there and then running the RUU executable file.
I have restored my applications offline, using Astro (which I installed from an apk), to prevent the market having to re-download them all at once and now with the market activated, they are all correctly recognised.
My phone is now totally unbranded and running software number 2.10.401.8.
This appears to have solved the delayed text messages, dropped calls and unreliable signal issues I was having with the T Mobile branded software. If only they would update the software themselves and remove this known bug, it would save a lot of people the time an effort of manually updating their phones in order to have them go back to being reliable!
The only thing that remains to be seen is if I will get OTA updates, as (AFAIK) the phone is currently running the very latest version available so there is no way to tell.
Thanks again to this community, which through its numerous guides and the answers on this thread, have made me once again - a very happy Desire S owner.

HTC India to HTC Europe

Hi,
I'm in the UK and I bought my Sensation XE from Hong Kong and use it with a T-mobile sim.
The mobile seems to think it's Indian and I would like to change it to a UK or euro setup.
At present it has HBOOT 1.18 and has CID HTC__038 with ro.carrier HTC-India. Software number is 1.77.720.103.
I had to use locale app to change it from india to UK so that I could have a UK keyboard/dictionary and also receive UK news in the news app.
Now it's coming up to release time for ICS and I would like to make my phone so that it receives the UK version.
Is it possible to flash my phone with the most recent Euro RUU to do this? If I do will I still need to change the CID to HTC__001 and will the RUU change all the bits relating to India that show up when you run the CID Getter app?
I've tried running the RUU > "RUU_PYRAMID_LE_HTC_Europe_1.73.401.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_220036_signed" and it looks as though it will change my software version to a version lower than it is currently on. From what I have read on the thread > http://forum.xda-developers.com/showthread.php?t=1193033&page=2 about "How to debrand...." I was under the impression I might need to use revolutionary to get S-OFF, change my CID to HTC__001 or HTC11111 run the RUU then put S-ON again or leave it off.
All just a little confused as to what's best to do.
Sorry for the long post with multiple questions.
I updated the Mrs Desire to Runnymede AIO without too much headache the other day so thought I'd look into sorting out my XE.
Cheers

Finally got there by myself.
Had to HTC Dev unlock bootloader. Flash recovery with 4EXT recovery. Use 4EXT recovery to flash an old ROM with HBOOT 1.17. Use Revolutionary to get S-OFF. Use RUU for most recent Euro GB ROM.
No have S-OFF, Unlocked bootloader, 1.18 HBOOT, Stock HTC european ROM. CID HTC__001.
Still no ICS update available when checking updates though

[Q]OTA Update for Euro phone from overseas?

OKAY so this might be an odd question, mods can delete as soon as I get an answer that's ok but I have this situation:
I live in South Africa, where the HTC One S has not yet been released. On holiday in the Netherlands I decided to buy a SIM lock free HTC One S. With my old South African SIM card cut to size, the roaming features worked fine but I received the first OTA system update via a Dutch WiFi Network while still on holiday. This brought my device to software version 1.78.401.2 with Android 4.0.3. However I am now back in South Africa and although the HSDPA works fine here and such, I've seen the new 2.21 Android 4.0.4 update has since been released for Euro devices. I have checked my CID which is HTC__E11 or similar but checking under settings doesn't show any updates. Will the update become available to my device and can I receive the OTA update from South Africa?
I'm stock unrooted.
Thanks in advance. If suggested ideas include checking HBOOT please advise as I don't know how to check on this device, just came from an HTC Wildfire with CM.

AFAIK you'll get OTA updates based on your CID and it doesn't matter which carrier you're on. I'd imagine you'll get your OTA soon even if you pull your SIM out and move to Antarctica as long as you have Wifi. Never mind your hboot version it doesn't matter if you're on stock software, but if you want to check hold volume down for a while when powering on

Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels

usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.

fmedrano1977 said:
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.

usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
The first thing I did with my new device was run the 2.21 RUU followed by unlocking the bootloader and rooting it.
The only problem I had was running CWM recovery (probably my error) but no problems at all with TWRP recovery.

usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.

usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Hey Usaff
Thanks for the advice, was slow to realize it was vol down+ power until the softkey lights flash
The RUU flashes and wipes the phone, correct? Strangely I remember using an RUU to get Froyo on my old Wildfire when it was still stock and somehow that functioned like an OTA and never wiped my data, might be remembering incorrectly, was a long time ago...
EDIT
Correct, but isn't root system related and not firmware related?
Click to expand...
Click to collapse
Is that the distinction between S-OFF and rooting? I know rooting gains access to Android system files and stuff, then is S-OFF just a security flag for HTC devices? Noob questions I know...

fmedrano1977 said:
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
It is system related but firmware also greatly affects rooting, especially if a firmware upgrade upgrades your HBOOT version.
Sent from pixels to more pixels