Difference between RUU & OTA - HTC Desire S

Hi Friends,
Have a few questions pls, Thanks in advance.
1 What is the difference between official OTA update & RUU update?
2 Is it required to have a rooted phone to make RUU?
3 In case a phone is rooted already, will it be able to be updated by official RUU?
4 Are there any diff betwee n OTA & RUU in terms of settings, regional configuration, stability.. .etc?
Sent from my HTC Desire S using xda app-developers app

1. OTA is incremental and doesn't erase anything. RUU is complete and erases everything.
2. No.
3. Yes.
4. Completely different things, since OTA is incremental and upgrades your existing ROM. Can't compare apples to oranges.

Thanks, but what is the major disadvantage of RUU, I understand it will erase all my data & will have to restore data & applications, is there anything else that make it a second choice?
Sent from my HTC Desire S using xda app-developers app

Why is it second choice? It's not about choice, it's about picking the right tool for the job. When you want to get OS upgrade, OTA is better - because you get the upgrade without extra pain (without starting everything from scratch). When you suspect your phone is misbehaving, or for some other reason want to restore your phone to the stock state - RUU is the way to go. They're not "better" than each other, they're different, for different occasions.

And im new to this stuff and if you can say or give the link to the thread where i can find what ota is it would be perfect, i searched xda but all i found was roms with ota
Sent from my GT-I9300 using xda premium

OTA is "Over-The-Air", so unless it arrives to your phone automatically, as it's supposed to - I believe people aren't keeping OTAs anymore. Once, when Nexus One was still considered a new phone, they did - but not anymore, for a long time now. In the forum you'll only be able to find RUUs, I believe.

In case a phone is rooted already, will it be able to be updated by official OTA?
It seems that OTA does not work for me anymore after I S-OFF'd and rooted.
I know also flashed a new radio. Does that affect the possibility of OTA in any way?
Cheers.

OTA doesn't care about rooting or S-OFFing. If there is OTA standing - it'll be delivered to the phone. Installing it might be problematic (can't be installed by custom recovery without disabling signature check), but the delivery WILL happen. S-OFF doesn't affect OTA in any way. If you don't get OTA - that's because there is no OTA, the servers are stopped.

I see. Signature check be the problem. Any solution for that?

This is only relevant if you have stock rooted ROM and custom recovery.
In that case, you need to locate the ZIP file downloaded by system update, and install it manually in recovery, skipping signature detection.

After reading...
nodeffect said:
5. I've just received this system update OTA - 1.47.61.1 or later. If I install it, will I loose my S-OFF and root?
- Yes, you will lose both S-OFF and root once you update because it will update the hboot to 0.98.0002. However, you can try following this guide http://forum.xda-developers.com/showpost.php?p=16110608&postcount=5 to update the OTA but not the hboot. Check this one out also http://forum.xda-developers.com/showthread.php?t=1190992 and http://forum.xda-developers.com/showthread.php?t=1194488 to S-OFF and root if you have updated the OTA.
Click to expand...
Click to collapse
I decided that it is probably not a good idea to go down to OTA route.

Hi,
I had the stock rom RUU​_Saga​_S_HTC​_ARA​_2.14​.415​.3_Radio​_20.4801​.30.0822U​ and I wanted to install the European RUU​_Saga​_S_HTC​_Europe​_2.10​.401​.9_Radio​_20.4801​.30.0822U​. But in the install process there was an 155 error. I tried some times but the same result. I read here a lot and finally I unlocked the phone HTCDEV as my hboot is 2.00.0002 and flash 4EXT_Recovery_v2.2.7_RC5 and ICE_DS_4.4 rom.
I experience some problem with this rom, so is it possible to install the european ruu of GB?

Yes, if you use goldcard or if you're SuperCID (which can only happen on this phone if you unlock it with XTC-Clip).
If you didn't understand something from the above - Google it.

Jack_R1 said:
Yes, if you use goldcard or if you're SuperCID (which can only happen on this phone if you unlock it with XTC-Clip).
If you didn't understand something from the above - Google it.
Click to expand...
Click to collapse
I know the words goldcard and supercid. I saw few threads name them . Thanks for the reply I will try the goldcard.

So i made my sd card Goldcard. what's next, in order to install stock european ruu GB? some guidance maybe?

Relock your bootloader and immediately install (without exiting FASTBOOT USB mode).

Jack_R1 said:
Relock your bootloader and immediately install (without exiting FASTBOOT USB mode).
Click to expand...
Click to collapse
I relocked the phone and when i try to install the european ruu it gives me the error 140, and stuck in bootloader. Then I install the ARA ruu and all gone well the phone runs well.
The problem though exists. I want the european ruu and not the ara ruu. Any ideas?

Related

[GUIDE][2.3.4 OFFICIAL HTC S-OFF ROOT] Pyramid_HTC_Europe_1.45.401.2-1.35.401.1_P2

THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Update 2011/08/14
Added more information and details
Renamed thread into GUIDE
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root. This will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader. I tested these steps and i have a 2.3.4 401 Sensation with Locked HBOOT, S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via "Over The Air" (OTA) or using OpenRecovery (OR). I did not use the OR-Method but you can find a lot of information about here. I do not advertise any guides for the OR-method since i did not test them myself.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
dacleric said:
....
4) Update to 2.3.4 via ...... using recovery.
Have fun!
Click to expand...
Click to collapse
How? Can some please explain step by step?
Thanks
anyone have a change log? google failed me for once in my life
The 2.3.4 update include an new hboot Version 1.18...
Are u sure that u can install cwm and root the phone again after applying the update?
I think u will be s-on again after the hboot get changed...
Everything I'm reading (the two other threads about this update) says the above method will NOT work. I don't think the OP even tried. Wait for a real dev to cook this up.
dacleric said:
THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via OTA or using recovery.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
Click to expand...
Click to collapse
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
^^ see the thread in the general section about this.
http://forum.xda-developers.com/showthread.php?t=1214707
Around page ten or so.
And this:
http://forum.xda-developers.com/showpost.php?p=16585832&postcount=123
A little more:
http://forum.xda-developers.com/showpost.php?p=16582890&postcount=31
eloyloy said:
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
Click to expand...
Click to collapse
Oh boy Some of use knew this was gonna happen
do not flash this to a stock rooted rom - it will **** it up - wait for your favourite dev to update their rom
flashing this will give you the new locked htc bootloader and you will not be s-off anymore (even though it still says you are)
it's taken me nearly 3 hours to get back to normal
EddyOS said:
When I say I'm S-OFF again, I mean I'm back to my old 2.3.3 ROM before I flashed the new update.
Everyone, DO NOT TRY AND FLASH THIS OVER YOUR ROOTED PHONE - WAIT FOR YOUR ROM TO BE UPDATED BY THE DEVS
Click to expand...
Click to collapse
xxxxxxxxxxx
Ledroid will tell us
Sent from my HTC Sensation Z710e using XDA Premium App
Hi all,
I've just done this update
Backup with Titanium
Reflash with 2.3.3 stock ROM (my Sensation was already S-Off)
OTA update to 2.3.4
ClockWork Recovery
Root
Restore with Titanium
Reboot and that's it
No OTA
I did exactly like shown in the first post, but i wont get the update ota. It sais that my phone is actually actual.
Could I have done something wrong?
Got the Sensation from T-mobile -> debrandet it like this:
http://forum.xda-developers.com/showthread.php?t=1193033
And used the RUU version from the first post.
Thanks
done as suggested - works fine for me!
I was off this weekend.
I posted this howto cause i did it with my phone. Whyever would i post a guide when it does not work?!
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
At least thats the case for me.
dacleric said:
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
Click to expand...
Click to collapse
Are you sure you can't flash the eng hboot too?
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
no - i did not try to.
I am pretty happy with my phone right now. Fast and long battery pack - replaced Sense with LP.
When testing the early (pre-soff) custom roms and test recoverys I had to flash stock RUUs a couple of times.
To get the phone back into a decent state I needed to pg58 flash eng&unsecured boot then root and fastboot recovery.
Can't for the life of me think why anyone would s-off their phone then install stock/ota for any reason (bar repair). It's like buying a track day race car, shouting "look what I've got" then pushing it around rather than thrashing it.
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Sent from my HTC Sensation Z710e using XDA App
d3vilskid said:
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Click to expand...
Click to collapse
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
dazweeja said:
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
Click to expand...
Click to collapse
Np, i was trying to figure out how to flash pg2fs_spcustom.img and I found out that the only way to do it was to flash the new hboot first than it would read that pg2fs img.
Sent from my HTC Sensation Z710e using XDA App

[Q] System update 1.45.162.1

So I got the notification that there's a Software update for my HTC Sensation; 1.45.162.1 (41.09MB) - Android 2.3.
I'm rooted via Revolutionary and still on original Vodafone (NL) stock ROM... However the update doesn't work for me. All I see is the green Android with a Triangle and an exclamation mark in it....
So after some search it seems that some other people have this issue, but that was in the tread for the 1.45.401.2 update....
Now what I would like to know now is this; Do I really need to go back to S-ON or is there any other way to get this update?
I'm asking this as going back to S-ON might brick the phone and also as I don't seem to find the original ROM in this thread.
Also, this as the instruction on this page clearly says:
Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
Click to expand...
Click to collapse
So..... I'm kinda lost now and I'm wondering how to proceed?? Would someone enlighten me?
THANKS!
as far as the US TMO update..you just had to be on the stock rom. You'll still keep S=OFF. And I'm still S=OFF after the update.
jmcghee1973 said:
as far as the US TMO update..you just had to be on the stock rom. You'll still keep S=OFF. And I'm still S=OFF after the update.
Click to expand...
Click to collapse
Ok... Strange... Any idea why I got stock on the green Android with a Triangle and an exclamation mark in it? The only way I can use my phone is to remove the battery and then it starts again, but it seems that it hasn't been updated.
If you backed up your original stock ROM w/ CWR, then restore in recovery.
Then run the update.
Gunkk said:
If you backed up your original stock ROM w/ CWR, then restore in recovery.
Then run the update.
Click to expand...
Click to collapse
But I'm already running stock rom... All I've done is rooted my phone and removed some bloatware such as The Sims, Soundhound etc. But that wouldn't be the problem would it?
Sent from my HTC Sensation Z710e using XDA App
Did you change your CID ?
Sent from my HTC Sensation Z710e using XDA App
Unroot & make sure you have your stock recovery...not cwm recovery. You'll lose root regardless when you update but you can re-root afterward.
m0rgul said:
Did you change your CID ?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Yes, I did. However I'm not sure if that's still the case as I've used CWM to put back the original stock rom after I didn't like a custom ROM.
How can I check if I still have Super CID?
EDIT: I can confirm that my CID is 11111111. After exploring the forums I also have tried to install the updates with the following CID's as well;
HTC__E11 + VODAPE17.
However without any luck!
jmcghee1973 said:
Unroot & make sure you have your stock recovery...not cwm recovery. You'll lose root regardless when you update but you can re-root afterward.
Click to expand...
Click to collapse
EDIT: I do have the first backup (made using CWM) which I made before I rooted and changed my CID. But that's not what you mean? This as this is the first backup I made from my device.
Ok... I'm fine with that BUT:
I don't seem to find the original ROM in this thread.
I do see Vodafone's UK, France and 3 HTC Europe Roms... So not quite sure what to choose?
This as the instruction on this page clearly says:
Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
Click to expand...
Click to collapse
Is there any other way I can install the updates?
And will I have the same problem in the future as well, with other upcoming updates?
THANKS!
I think it's strange that OTA vodaphone 1.45.162.1 gets pushed to your phone if you have set Super CID, because OTA is based on CID. I had to change CID after I unbranded my phone(installing stock RUU HTC EUR), to get OTA 1.45.401.2.
It should work when you set CID to 'VODAPE17', or maybe the problem is the phone being unlocked, you should have chec.ked before using revolutionary that an RUU was available to restore your original rom..
At last try to restore your first backup, and set CID to 'VODAPE17'.
Also try to download the OTA file on your phone and copy it to your computer.
m0rgul said:
I think it's strange that OTA vodaphone 1.45.162.1 gets pushed to your phone if you have set Super CID, because OTA is based on CID. I had to change CID after I unbranded my phone(installing stock RUU HTC EUR), to get OTA 1.45.401.2.
Click to expand...
Click to collapse
Ok.. Didn't knew that.
It should work when you set CID to 'VODAPE17', or maybe the problem is the phone being unlocked, you should have chec.ked before using revolutionary that an RUU was available to restore your original rom..
Click to expand...
Click to collapse
As far as I know I haven't unlocked my phone... All I have done is the following:
- Rooted via Revolutionary
- Installed CWM
- Made a backup
- Made sure I had Perm root access
- Set the super CID.
Yeah... I know.. I should have done so, but I was too excited I guess...
At last try to restore your first backup, and set CID to 'VODAPE17'.
Also try to download the OTA file on your phone and copy it to your computer.
Click to expand...
Click to collapse
That I can try! Thanks.
So I've downloaded the OTA file and I think I understand why the VODAPE17 doens't work. The update is called: "OTA_Pyramid_Vodafone_DE_1.45.162.1-1.35.162.1_release_208996.zip".
So I'm going to try with Vodafone DE CID and see if I can update!
Will keep you updated!
UPDATE: No, even with CID set to VODAP102 I can't get the update installed.
So I extracted the zip file and went through the files and saw a file called: updater-script.
I opened this file and saw the following lines:
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "VODAP102" , "VODAPE17" ,
"VODAP304") == "t");
Click to expand...
Click to collapse
Now... I already have tried all the 3 Vodafone CID and the super cid is 11111111. Should I check the rest as well or what can I do?
This worked for me.....
BioTecK said:
Ok.. Didn't knew that.
As far as I know I haven't unlocked my phone... All I have done is the following:
- Rooted via Revolutionary
- Installed CWM
- Made a backup
- Made sure I had Perm root access
- Set the super CID.
Yeah... I know.. I should have done so, but I was too excited I guess...
That I can try! Thanks.
So I've downloaded the OTA file and I think I understand why the VODAPE17 doens't work. The update is called: "OTA_Pyramid_Vodafone_DE_1.45.162.1-1.35.162.1_release_208996.zip".
So I'm going to try with Vodafone DE CID and see if I can update!
Will keep you updated!
UPDATE: No, even with CID set to VODAP102 I can't get the update installed.
So I extracted the zip file and went through the files and saw a file called: updater-script.
I opened this file and saw the following lines:
Now... I already have tried all the 3 Vodafone CID and the super cid is 11111111. Should I check the rest as well or what can I do?
Click to expand...
Click to collapse
Hi - I had exactly the same issue as you - it turned out that the OTA will not run if you are S-OFF, I had to go back to S-ON and then install the OTA, then go back to S-OFF.
Worked a treat - then I decided that I didn't like stock and installed a ROM - lol
iftikar666 said:
Hi - I had exactly the same issue as you - it turned out that the OTA will not run if you are S-OFF, I had to go back to S-ON and then install the OTA, then go back to S-OFF.
Worked a treat - then I decided that I didn't like stock and installed a ROM - lol
Click to expand...
Click to collapse
Hmm... I see... So there's no chance that I can install this while having S-Off? Even not with CWM?
Also, would restore to factory setting do the trick as well? (Instead of using RUU?)
ok don't worry abt the S=OFF .. its ok.. You need to find the RUU of the rom that originally shipped on your phone. Run it via your pc with your phone connected and then do the update.
You may have to set your CID back to the original... I did but I didn't test it with 11111111 first.
jmcghee1973 said:
ok don't worry abt the S=OFF .. its ok.. You need to find the RUU of the rom that originally shipped on your phone. Run it via your pc with your phone connected and then do the update.
You may have to set your CID back to the original... I did but I didn't test it with 11111111 first.
Click to expand...
Click to collapse
Is there any way to figure out which rom was originally shipped and the CID on my phone?
Running the RUU shouldn't be a problem as I've done that a couple of time when I wanted to install EnergyROM on my old TP2.
Thanks.
so where is asian update ? i'm stell waiting but it didnt come
one question, my device is rooted now, can i update ?
BioTecK said:
Is there any way to figure out which rom was originally shipped and the CID on my phone?
Running the RUU shouldn't be a problem as I've done that a couple of time when I wanted to install EnergyROM on my old TP2.
Thanks.
Click to expand...
Click to collapse
You say your on a stock "backed up " rom... go to Settings > About Phone> Software Information & look at the Software Number
jmcghee1973 said:
You say your on a stock "backed up " rom... go to Settings > About Phone> Software Information & look at the Software Number
Click to expand...
Click to collapse
That's what I did and I was running 1.35.162.1.
While searching the forum and Google and checking the OTA update I noticed that I needed to have RUU of Vodafone DE (Hence the 162 code in my software information).
At some point I came across a website which had posted the "latest" RUU for Vodafone De; RUU_Pyramid_Vodafone_DE_1.27.162.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191975_signed.
So I downloaded the file and ran it. After this I searched for any OTA updates and I could download 1.35.162.1. I was able to download and install this without any problems.
After a restart I searched again for any other updates and I could download the latest version which is 1.45.162.1! Again, I was able to download and install this update without any problems! =)
So I guess everything is just working right! Luckily I'm still S-OFF and some how the phone seems to be MUCH faster then it used to be!! So I'm all happy again!
THANKS again for your help and everyone else!!
So wait...you were able to install it with all the custom mods like clockwork recovery s-off and root?? I tried installing the update but it wouldn't install assuming because I had the custom recovery not stock. Can someone clarify? I have a t Mobile branded sensation also. Thanks
Sent from my HTC Sensation 4G using XDA App
nexicon said:
So wait...you were able to install it with all the custom mods like clockwork recovery s-off and root?? I tried installing the update but it wouldn't install assuming because I had the custom recovery not stock. Can someone clarify? I have a t Mobile branded sensation also. Thanks
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Not quite...
I was only able to install the OTA updates after I run the original RUU... Without it I wasn't able to install as well.
A lesson which I learned today is that you need to flash to the original RUU before you can install the OTA's.
Hope this helps.
Glad to see you managed to sort it out, just curious, what is your hboot version now ?

One S new OTA update ?

Hi
Today i got a message that there is a new firmware ready for my ONE S.
It says it includes 4.0.4 and sense 4.1 plus wifi enhancements and ea games.
The wifi enhancements and ea games was also offered on a different update not too long ago.
Problem is that whenever i download and try to install it reboots and goes into CWM which stops with an error that it cannot find the file.
When i try to install the file manually from the download directory with the signature verification off (if on it fails at once) i get :
assert failed: check_cid(getprop("ro.cid"), "00000000", "11111111", "22222222", 3 4 5 6 7 etc ........
Error in sdcard/download/OTA_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5-2.21.401.10_release_275774cltf0sxl730g7fp1.zip
Status 7...
My phone is S-off via htcdev and rooted to be able to install adblocker and a few other things.
I have seen some sites and explanations for "status 7" but they are mostly linked to people flashing homemade roms, i am trying to flash a rom that supposedly is directly coming from HTC...
Anyone know what is wrong ?
1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...
Antubis said:
1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...
Click to expand...
Click to collapse
Ok, will there be a "modified stock" that i can flash without having to remove CWM and install stock recovery.
Antubis said:
1) You had to search how to proceed before asking...
2) You're not S-OFF...
3) You have to unroot, use stock recovery (and maybe relock bootloader, there are some discussions about it...) to apply an OTA.
4) You're not S-OFF, you'll be flamed for what you said...
Click to expand...
Click to collapse
could you give me link, where it describes, how to unroot and get stock recovery?
OP, you may need to change your CID first, there are threads and posts on this. Esp now with 2.31 out
And for FYI--some people did get s-off phones--not saying OP does--
rugmankc said:
OP, you may need to change your CID first, there are threads and posts on this. Esp now with 2.31 out
And for FYI--some people did get s-off phones--not saying OP does--
Click to expand...
Click to collapse
Stiflerlv said:
could you give me link, where it describes, how to unroot and get stock recovery?
Click to expand...
Click to collapse
I changed my CID, Re-Locked boot-loader and installed stock recovery. I'm on 2.21 my phone can't even find the ota so there must be other factors
That's why I never do OTA's, just wait for it in next rom like TD or Axiom etc
sharpinator said:
I changed my CID, Re-Locked boot-loader and installed stock recovery. I'm on 2.21 my phone can't even find the ota so there must be other factors
Click to expand...
Click to collapse
Your phone needs to be on 1.78 so you could get this 2.23 OTA. I am on 2.21 and don't have OTA either. We will need to wait for RUU file of 2.23

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.

Converting AT&T carrier unlocked HTC One A9 from stock 1.27.502.5 to Nougat

Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
bbsmitz said:
Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
Click to expand...
Click to collapse
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update? I'm guessing it will void my warranty, but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back.) I guess my question is, warranty aside, is there really any negative to turning S-off?
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Thanks again for your time.
Best,
Bbsmitz
bbsmitz said:
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update?
Click to expand...
Click to collapse
No, after converting to another version, you'll receive ota updates for that version.
I'm guessing it will void my warranty,
Click to expand...
Click to collapse
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back
Click to expand...
Click to collapse
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
I guess my question is, warranty aside, is there really any negative to turning S-off?
Click to expand...
Click to collapse
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Click to expand...
Click to collapse
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
alray said:
No, after converting to another version, you'll receive ota updates for that version.
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
Click to expand...
Click to collapse
Edit2: I figured out the problem. I had to boot into the bootloader and then run
Code:
htc_fastboot oem rebootRUU
before I could run the RUU sucessfully. Am leaving the rest of this post up just so that other people googling this have a touch point.
Okay so I've used Sunshine to turn s-off and unlock my bootloader. I then changed my CID to BS_US001.
I then tried to install the HTC version of Marshmallow (maybe silly, but heard people having issues with Nougat and the battery) using the RUU.exe file. It started successfully, but then halfway though, after it had transferred the ROM over, it threw an ERROR155 and aborted, leaving my phone with an empty progress bar, and that circular green arrow icon in the middle. I used the command line to restart my device and had to factory wipe it, but otherwise not the worse for wear.
I tried googling it; do I need to relock my bootloader for the RUU.exe files to work? I think the Sunshine FAQ recommended against doing that. Is this a risky step?
Edit: Here are some instructions I found from the HTC One M8 firmware flashing thread. My error says "unknown" but I imagine its similar.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
Click to expand...
Click to collapse
help
Is this guide convert AT&T bindings factory unlocked htc? I cant access wifi hotspot. also cant run RRU.
hiii i have htc one a9300 by mistak i wipe every thing including internal memory now my fon sows that no "os install are you sure wanto reboot " please tell me wat to do now
AT&T conversion
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
How do I get started to do this. How do I find out my mid Cid and if I need to change? How do I flash firmware first? I have android 6.0 software 1.27.502.5. I have done a run before but never changed from a carrier. I went to the link above but I don't know what some if this means and where to start and what steps to take in order.

Categories

Resources