[Q] RUU upgrade? - HTC Desire S

I have a desire s, s-on, hboot 2.00.0002, radio 3822.10.08.04_M. It was bought in UK.
I currently have the Vanilla ICE v2.0 rom installed, however there are some features that are really annoying me, and I would like to try the official HTC ics update.
I have been to htcdev and downloaded the ICS RUU (after selecting WWE as the region).
However, when I run it it bombs out, with error 155, and suggests I download the correct version.
From what I can see on here, I've been told that the WWE version should be correct version for UK, is this correct?
I did try downloading Endymion 3.5, and installing that onto my phone, however when I boot my phone, it keeps saying that the phone, messaging and pretty much everything has crashed! I tried running the RUU with that installed, and it got as far as trying to send the rom over, however it failed. Unfortunately, I cannot remember the exact error. It *may* have either been 155 or 175.
I have since read this thread -> http://forum.xda-developers.com/showthread.php?t=1655832 about re-locking the bootloader, however I have not yet managed to restore my phone to stock.
I am currently downloading a rom from here -> http://forum.xda-developers.com/showthread.php?p=31345345&highlight=link#post31345345 in the hopes it will work.
Does anyone know if you HAVE to have either a stock rom, or an older rom, in order to run the ruu?

I tried re-locking the bootloader, and running the
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
file I downloaded, however it got as far as updating the signature, and failed saying I need to get the right version.
Can someone PLEASE help.
How can I downgrade my phone to stock gingerbread, and why is the WWE ruu not working on my o2 (uk) branded phone?

check this out: http://forum.xda-developers.com/showthread.php?t=1318919&highlight=skanob

Related

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.

flashing ICS back to stock

Hey guys,
I have to flash my HTC Sensation back to stock, because it have a little hardware error (its sometimes suddenly shutting down ...)
My Sensation is from Germany..
On my phone is currently the Cyanogenmod 9. Yesterday I flashed the eng Hboot 1.17, because I read somewhere that i have to. Is this true?
After this I wanted to restore my backup of the original Rom, but this doesn't work. There were some errors and so on.
I think if I would send it back to HTC I have to uninstall the CWM and I have to install the old Hboot 1.18, but after a lot of reading today and yesterday I'm very confused., because I found no working way ...
greets
Tobi
http://forum.xda-developers.com/showthread.php?t=1516255
Person with pretty much same problem and some advice.
1. Flash old 1.17 FW (unless you're Super CID, in which case you may not need to)
-> ok i flashed a 1.17 FW. Everything is still working without any issue,but after I unlocked my phone i had the 1.17.111and so on FW. Now I have the 1.17.2008. Is this maybe a wrong fw?
2. Flash the RUU of your choice (normally the one your phone came with, if available)
->I don't know the RUU which my phone came with , the most was done by the program revolutionary. I have an unbranded European Sensation. Which is the right RUU?
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.3_Radio_10.56.9035.00U_10.14.9035.01_M_release_219990_signed.exe
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe
I read that I can brinck my phone very fast with it, so it is very important
I just have to download the exe and run it, after this it will flash my phone if it is in USB Debugging ?
I hope it is so easy to downgrade the phone from 4.0.3 to 2.3.4
3. Reset Super CID to one of your choice (again, usually the one your phone came with)
Is this important? Or is it enought if I just reinsert the battery, becuase I don't know if I'm Super CID
4. S-ON using the fastboot command in the guide in the Dev forum
with adb-tools:
-fastboot oem writesecureflag 3
-fastboot reboot-bootloader
right?
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.90 35.00U_10.15.9035.02_2_release_228602_signed.exe
This was on my unbranded Sensation when I bought it.
For SuperCID look here (Step 4):
http://forum.xda-developers.com/showthread.php?t=1192300&page=1
warning
i updated to icecreamsandwich firmware h boot 1.23. i neede to go back to stock so i follwed directions on guide to s-on and ran ruu that came with my phone and it says error get the right bootloader ruu .however it didnt brick it but bootloader says security warning wifi and wifi hotspot both gives error. ive tried everything i know to fix it with no luck. ive heard its because i upgraded the firmware.
ok I'm now on Super cid. This was just very easy
Ok now I have to download the RUU (filefactory is very slow... )
What will happen, when I would flash the wrong EU ROM? Or is this just impossible?
Is it important to reset the cid to the cid which was set, when I got the phone? Or is it set back by flashing the RUU?
I have a lot of questions, but I don't wanna brick my lovely phone
Edit:
Ok everything is now fine. My phone is now on Andorid 2.3.4, S-On, old CID and unrootet...
I hope they will repair it, because sometimes the phone run 2 days without any issue and sometimes it just runs some hours without issue...

[Q] Is there stock recovery for a Rogers S One with RUU 1.84?

I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto
Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.
you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want
Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.
I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium
Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?
don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network
Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.
if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work
Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.
factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery
donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link
I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?
Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.
for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network

Help, i think i destroyed my phone.........

Hello. I have a htc one s ville c2(s3 proc) and a long time ago i installed a custom rom (trickdroid 5.0.0 ) and it started to work hard, wi-fi not working, and things like this.So i decided to go back to stock. My phone's cid is htc_032 wich means that is for Eastern europe. I downloaded a ruu 2.15......... and i installed it. The mobile network was working very hard (100kb/s) so i think the baseband is not good.Then i found an ota for htc_032 and i tried to install it. i relocked the hboot, then flashed the firmware.zip with fastboot. All fine, but after the install i candt even open my phone or enter in hboot........ please help...

[Q] Help! HTC One S ROM RUU

Okay, where do I start. First, I have an HTC One S (S4) that is/was locked to Cincinnati Bell. The Cincinnati Bell ROM is version 1.84.422.6. The phone is a GSM. I have successfully removed the SP lock, unlocked the bootloader and upgraded the to TWRP 2.1.6. I also have superCID (11111111) and have installed superSU.
Now for my problem. I am switching from Cincinnati Bell and going to T-Mobile here in the USA. I have a T-Mobile US RUU that is version 1.84.531.2. I have attempted to install the new ROM via RUU numerous times and continually receive a 155 error. From what I can tell the RUU is unable to overwrite the current OS. As a matter of fact... I have tried to rename and change permissions on some of the files located in/around root and am unable to do so. I receive a message that indicates the system is Read-Only. I'm assuming this is related to the 155 error that I keep receiving.
I have also noted that the phone is S-on, which I believe might be causing my trouble as well. I downloaded and ran rumrunner in an attempt to gain S-off. Rumrunner went through it's gyrations but was unable to gain S-off.
So... does anyone have any ideas as to how I can:
1) Obtain S-off
2) Install the T-Mobile ROM (possibly through an image (.img) file or other method)
I have searched the web over for a valid T-Mobile image file but have yet to find one. Otherwise, I would have attempted that too by now, Needless to say I'm frustrated at best.
RESOLVED...
I stumbled upon a discussion re: facepalm and the ability to obtain s-off. I followed the facepalm procedure, obtained s-off and the ROM installed without a hitch.

Categories

Resources