[Q] RUU to go back stock - HTC One S

I know there are several threads like this one but I prefer not to write another RUU request while you're answering to another user
So, I got a HTC One S S3 yesterday... I began to unlock it because I wanted to change its CID. I found that in the S3 version the CID can't be changed (still) when I had already installed the TWRP Recovery.
Now I'd like to go back to stock, but there is not a RUU compatible with my device: It has VODAP102 as CID, but the RUU for Vodafone AT here doesn't work. I found the kernel source for the same software version I have in htcdev.com, my question is: is it possible to build a RUU or at least a boot.img from it?
The sources can be found in htcdev /devcenter/downloads (sorry but being new I can't post direct links!), HTC One S as Device, Vodafone as Carrier and UK -
1.11.161.133 as software version. Actually I am in Italy, but the software and kernel version are exactly the same.
Thank you in advance.

Bump to first page and a little addendum:
I've read again all the possibilities I have with this phone, and if I have understood accurately then I'm forced to go back to stock, roms like the ThickDroid seem to require a non-branded CID, but that's the point... it is the CID that's compelling me to maintain this original Vodafone software, otherwise I would have already installed the HTC "basic" rom.
Am I missing something?
Thank you again!

Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM

mikejasonsmith said:
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
Click to expand...
Click to collapse
Yes I checked, but they have just unbranded RUUs, here in the forum there's one RUU for Vodafone but the region isn't the same as mine.

I've read that it is possible to flash an OTA update deleting the string that checks the CID - I'll have to take a look about that (moreover, it seems very difficult to find .zip OTA updates for this phone...).
Nevertheless I'd like to find this RUU update too - it is an important option too. So... bump to first page.

Related

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

H3G__001 UK Stock image anyone?

EDIT:
Here is the official RUU for H3G (Three UK) standard model Sensation
Was pointed out by another forum member, so I have mirrored it onto Mutliupload.
http://www.multiupload.com/5IQK830UIJ
Now everyone who has to send their Sensation supplied by Three in for warranty, just...
Make sure CID is H3G__001 (or SuperCID 11111111, though if CID is this, you don`t really need this ROM)
Once CID is correctly set, reboot into bootloader menu and run the RUU.
Having correct CID enables you to receive OTA updates once you have installed the RUU / ROM. If you update OTA, bare in mind, that it will also update your HBOOT to 1.18.0000 *Locked*
So once you have done this, do S-on to resecure your NAND and there you go... Ready for a warranty return...
My 0.0000000000002p worth anyway.
Thought it might help people who are on Three...
Tested and confirmed by me
Hello everyone!
I`m sorry to trouble everyone, but I was wondering if anybody had a backup of the original three uk (CID: H3G__001) ROM?
I have changed my CID and got Android Revolution installed.
I would just like a copy of this original ROM for warranty purposes.
I have looked at the stock ROMs pages and I can see the generic pyramid roms, however I keep drawing a blank when it comes to anything from H3G (three)
Any advice anyone could give?
or maybe...
1) Would someone who owns a UK H3G sensation (standard one) could upload an image somehow?
2) Would I be able to create a ROM indestinguishable from the original one installed (which includes startup logos OEM three crapware etc...)
3) Yes I was a complete dipsh*t for not making a nandroid backup (I was a complete Android virgin, iPhones were my bag)
Any advice/flaming is much welcomed!
I HAVE FOUND THE RUU!!!
Made a multiupload link for it so it is easier to find. Will put the link on as soon I`ve got 8 posts!
N10AP said:
Hello everyone!
I`m sorry to trouble everyone, but I was wondering if anybody had a backup of the original three uk (CID: H3G__001) ROM?
I have changed my CID and got Android Revolution installed.
I would just like a copy of this original ROM for warranty purposes.
I have looked at the stock ROMs pages and I can see the generic pyramid roms, however I keep drawing a blank when it comes to anything from H3G (three)
Any advice anyone could give?
or maybe...
1) Would someone who owns a UK H3G sensation (standard one) could upload an image somehow?
2) Would I be able to create a ROM indestinguishable from the original one installed (which includes startup logos OEM three crapware etc...)
3) Yes I was a complete dipsh*t for not making a nandroid backup (I was a complete Android virgin, iPhones were my bag)
Any advice/flaming is much welcomed!
Click to expand...
Click to collapse
ya not on ya own there, I have done several flashes, always backing up original 1st, but for some reason this step was "missed" when i flashed arhd to
There's an RUU somewhere, search for it
Sent from my HTC Sensation Z710e using xda premium
I have searched everywhere I can think of. I am aware of the stock HTC ruu files. These seem to be the generic ones and they are incompatible with my CID. I have changed my CID but would just be nice to find the proper RUU so I can change it completely to stock, and not just to the generic one. I'm sure changing the CID will invalidate the warranty.
Matty
Sent from my HTC Sensation XE with Beats Audio using xda premium
EDIT:
The Three Stock RUU works 100%. For newbies... Remember:
CID must be 11111111 (SuperCID) or H3G__001 to receive Over-The-Air updates. To change CID, search elsewhere! There are TWO underscores in the CID
To avoid 155 error when running RUU, run RUU when in recovery... Use adb to get into recovery or pull battery / vol down / power... You know the score!
I`m sure all this has been posted a thousand times, but I`m hoping it will help people who are on Three UK (Hutchison 3G).
Many thx
Sent from my HTC Sensation Z710e using XDA App

Remove Revolutionary Unroot for official OTA & Warranty & Stock Rom

I bought my used Desire S and it was rooted with revolutionary so i could not get OTA from 2.3.3 beyond. I read some threads but nobody was telling me which RUU i needed as my phone was unbranded and i was not sure about its origin. I managed to bring back the official stock Rom and original radios, hboot and downloaded and installed 2.3.5 successfully.
Nobody could help but finally i managed to take the risk and it paid off thankfully.
It is the easiest and fastest way to unroot, remove superuser, revolutionary and to restore hboot back to normal and S-On again, to get official updates including ICS.
Download the attachment "usmanxhmed.rar", it has Android Flasher and FlashENGHBOOT.
Attach your phone to PC with USB cable, make sure you have HTC fastboot drivers installed.
Open Android Flasher and select bootloader and browse to the file FlashENGHBOOT which you downloaded in file "usmanxhmed.rar", boot phone into fastboot and click flash.
It will remove REVOLUTIONARY **** from the phone.
Now download your specific RUU from this link http://www.filefactory.com/f/c64d333a2755a421/ i was unsure which is my RUU for the phone as i bought it second hand, my phone was unbranded, i matched the software version and radio version in my software information of the phone and downloaded the specific RUU.
After flashing the RUU my Desire S became factory fresh and back to S - ON and updated my phone with Android 2.3.5 and Sense 3 and hopefully/ may be i will get ICS in future as well
Good guide cheif :thumbup:
Sent from my HTC Desire S using XDA
Thanks ttocs99
Quick question, this might not be the best spot for it but it is somewhat related.
My desire s is branded/locked to vodafone portugal, so i have no specific RUU in that list. What will happen if i use Europe one? Or UK's Vodafone?
Best Regards,
Daniel
dan_alexandre said:
Quick question, this might not be the best spot for it but it is somewhat related.
My desire s is branded/locked to vodafone portugal, so i have no specific RUU in that list. What will happen if i use Europe one? Or UK's Vodafone?
Best Regards,
Daniel
Click to expand...
Click to collapse
Vodafone UK !
I have a Desire S from Vodafone Germany and it works perfect with the Vodafone UK RUU.
Stefan

[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

Looking for a compatible RUU File for HTC One S Cincinnati Bell (PJ40110)

Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).

Categories

Resources