Database Info

[Q] S-off vs radio s-off

What is the difference between 'regular' s-off and radio s-off? is it just two different areas of nand that are locked separately? If that is the case, why would you ever want to only unlock one and not all?
I assume this is all basic stuff for the HTC vets, but the inspire is my first HTC phone.
Thanks

http://tinyurl.com/4ztqe45
jokes, jokes.
really though, from the first result...
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
Click to expand...
Click to collapse

LOL, no, that is funny. I need to bookmark that.
I had searchedboth Google and the forums. I understand that s off is turning off Sig checking on updates. More wanted to know why there is separate soff and radio soff.
Sent from my Inspire '4g'.

There's S-Off and then ENG S-Off. The latter allows you to flash radio.img.

[Q] Some questions about HOX ATT CID, bootloader & LTE

Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
6./ In the thread radio & RIL , I read that update 2.2x will replace HBOOT and make old radio not compatible, is it because new HBOOT resize the radio partition smaller? So if I flash a custom rom based on Asia RUU 2.29 for example (not the dreaded 2.20 ATT), my current HBOOT will be replaced by new HBOOT as well? With no S-OFF, we can not flash HBOOT so will I be stuck with the new HBOOT and therefore, new radio roms only?
Looking forward to hearing from HOXL gurus. Thanks.

linhldz said:
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
Click to expand...
Click to collapse
1. Spoofed CID is permanent unless you go in and change it back. For all intents and purposes, it's permanent.
2. Actually to run an RUU, you must relock your bootloader or it will fail. As long as you have your unlock token or Super CID, you can re-unlocked your bootloader once you are done and flash SuperSU to get root back. Or just flash a pre-rooted stock ROM.
3. Not sure. Make sure to fully read the post. I have never run an RUU for a phone with an RUU from a different carrier. Again, make sure you read about that one.
4. You just don't want to run the 2.20 RUU for AT&T. It will make it so you can not flash radios at all and you must flash boot.img from adb or from Android terminal emulator. It is just the 2.20 RUU that will do this. A custom ROM will not, so no need to worry.
5. It will not disable LTE, but if you don't have an LTE APN in your phone it shouldn't be looking for LTE and you can also turn off the LTE radios on any non-AT&T ROM.
My recommendation after all of your questions would be to flash a pre-rooted stock ROM or a cleaned up debranded ROM (like Clean Rom, but there are more out there). Change the APN to what ever country you are in and do the *#*#4636#*#* thing to turn off your LTE radio. Again, the *#*#4634#*#* to turn off the radio will not work on a stock AT&T ROM.

Thank you, Butters. Still I've got one more question - added in the first post.

linhldz said:
Thank you, Butters. Still I've got one more question - added in the first post.
Click to expand...
Click to collapse
If you are flashing a custom ROM, you do not have to worry about your HBOOT being changed. It doesn't matter what the custom ROM is based on. You only have to worry about that with running an RUU (which is from HTC for a specific carrier).
If you have 1.85 on your phone, just keep a 1.85 RUU on your computer and flash away any ROM you want. If something gets messed up and you need to RUU, you'll always have that 1.85 RUU with the old hboot.
Running the 2.20 RUU, you will lose all ability to flash any radios, so you will be stuck with the AT&T 2.20 radio. Being that you are overseas, I would not recommend this because it may not (probably isn't) the best radio for your use case.

If you want a stock ROM, there are pre-rooted versions posted in Development that are flashable from TWRP. Easier then relocking the bootloader and running the RUU, and no threat of hboot changes (or having to research what was changed in the hboot).
Or just install a custom ROM. They are often based on recent firmware versions, but already de-bloated, and with awesome customizations added.
After all, if you want to run a stock RUU, why did you unlock the bootloader in the first place?

Thank guys, really appreciate. Just flashed CR5 with confidence, so far so good.
Early assessment: Quite smooth, the LTE problem with AT&T stock rom has disappeared, battery life improves greatly.

[Q] RUU not working to update RADIO from new HBOOT

Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?

Inferi0r said:
Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?
Click to expand...
Click to collapse
The new Jelly Bean firmware will no doubt come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville

radio
uunderstanding 65 said:
The new Jelly Bean firmware will no t come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
Hi, is my understanding correct that jb will improve the radio on my HTC one s so I should get better reception!?

Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium

Inferi0r said:
Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Why do some RUUs have different radios than others? T-Mobile US is definitely different, they contain tweaks as far as I know that optimizes it for their frequencies etc.

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).

Advice on S-Off for rooted/unlocked HOX w/ 4.0.2

I have an AT&T HOX running the original stock ICS 4.0.2 The phone is rooted, bootloader unlocked and has Supercid.
I would like to install one of the new Cyanogenmod ROMs that require HBoot version to be 2.14 or newer, but I'm having problems. I can't use an RUU to upgrade to 4.2.2 or whatever, because I'm supercid and will probably brick the phone. Facepalm/Rumrunner/Firewater/moonshine etc, S-Off tools do not work with this particular kernel for whatever reason, and I just get the "Please install an 'unsecure kernel" advice at the end of the attempt.
So, basically, I can't get S-Off because none of the tools work with my OS version, and I can't update my OS via the normal channels because of having supercid, and I can't upgrade my firmware because I'm not S-Off. Kind of a catch 22-22-22 situation.
I'm not even sure what question to ask at this point, so I'm open to any advice you guys are willing to offer in regard to upgrading to HBoot 2.14 to meet the requirements to install CM 11 on my phone. My current HBoot version is 1.14
**Edit** Current firmware - 2.20
Thanks in advance.

Maybe a solution
Well, I finally found a thread by someone with a similar situation. It looks like the procedures outlined by Heisenberg in his replies did the trick for that particular person, so I'm gonna give that a try I guess. I'm not sure how I missed that thread after all the searching I've done before now, but for anyone who might be interested:
http://forum.xda-developers.com/showthread.php?t=2218990
Thanks

Try to flash Kickdroid 5.0 as outlined in the other thread, then you should be able to get s-off.