Related
NOT COMPATIBLE WITH DEVICES SHIPPED WITH GINGERBREAD 2.3
One click Radio S-OFF tool
YouTube videoHTC - Quietly Unlocked
About:
This tool will make a Desire HD Radio S-OFF after it has been permrooted with Visionary. After running this tool, you can flash any ROM and kernel to your device using ClockworkMod. No bootloader S-OFF needed! You use this tool at your own risk!
What's the difference to other methods?
First of all, this is easy. The steps are straightforward, you do not need to tinker with complicated command line stuff. Radio S-OFF is the way these devices are meant to be made S-OFF, it is a safe way. If you use this method, reverting to stock is very easy! Unfortunately without ENG bootloader (my other tool) you cannot use fastboot commands (advanced stuff) and, for example, my Kernel Update Utility. To make a raw comparison, this tool is for everybody including new users and the eng hboot S-OFF version is for enthusiasts. Many experienced users have both, because having both allows supreme flexibility.
I recommend to use Radio S-OFF instead of traditional bootloader ENG S-OFF, because this can be more easily removed and is much much safer!
System requirements:
Windows XP SP2 or higher
.NET Framework 4.0
HTC Sync (or ADB drivers)
Desire HD with stock kernel (or Apache14's 1.0.7 / 1.1.4 Sense)
It will not work on 1.72.405.3 or higher build, or new radio (12.28b.60.140e_26.03.02.26_M is ok). Downgrade first!!
So, in detail, the Root & S-OFF process goes like this:
Install Visionary
Open Visionary and tap temproot, then attempt permroot now. Your device will reboot.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Download the Radio S-OFF tool and place it in the root of your hard drive (c:\[tool folder goes here])
Open my "Desire HD easy radio tool.exe" (Windows 7, right click & run as administrator), choose the first option, click "Do it"! There may be a SuperUser request on your phone, allow it.
Done. (Remember to click the thanks button)
But you might want to continue if you are a new user:
If you want to flash a radio (to improve signal and battery life) some day, do ENG S-OFF (no need to use Visionary again, just run the tool)
To flash a custom rom: Get Rom manager from the market, which will install a ClockWorkMod recovery for you. Just open it up and tap "Flash ClockworkMod recovery"
Download a custom ROM, put it to your SD, and flash it using Rom manager or ClockworkMod itself. You can access ClockworkMod through Rom manager. It is recommended to do "wipe data / factory reset" in ClockworkMod before installing ROM from SD card.
It will create a backup of your phone partition 7 (radio config) to the root of your sdcard, I recommend to keep that somewhere really safe!
To go back to S-ON:
Flash stock ROM (RUU, not over 1.7)
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
If you like my work, please consider: (or just hit the thanks button )
Thanks: Paul O'Brien for visionary, scotty2 and others who found the method to patch P7, Guhl and everyone else who has worked on the G2 root, gfree and wpthis, link to the source code, those have been released under GPL
Download link is in the end of the second post
[TOOL][VIDEO] One click Radio S-OFF, SimUnlock (Easy Root Guide)
FAQ:
Q: Why is this Radio Tool, does it flash a radio?
- From end user's view, it has nothing to do with radios, the name comes from the S-OFF technique this tool uses.
Q: I cannot find "System Info" in SHIP bootloader
- That is normal, just refer to the CID list when reverting to stock.
Q: How can I revert to full stock, I have ClockworkMod and/or ENG S-OFF too?
- Just follow the S-ON instructions.
Q: Can I use ENG S-OFF with this one? Which one first?
- Yes you can, it does not really matter, but I would do Radio S-OFF first.
Q: Does no fastboot stuff mean slow device startup (no HTC Fastboot)?
- No, I am talking about issuing commands to the bootloader through USB.
Q: Is this Radio S-OFF permanent, does it go away if I flash RUU/factory reset?
- It is permanent until you remove it using this tool.
Q: I already had ENG S-OFF and I ran the tool, how do I find out if it worked?
- If you used the first option, see bootloader system info. There should be CID-11111111.
Q: I have now ENG S-OFF and Radio S-OFF, how do I get to stock?
- Just follow the S-ON instructions, everything will be back to stock.
Q: I have 1.72 or higher system, what should I do??
- Downgrade using this guide, or flash Raidroid if you already have ENG S-OFF & ClockworkMod.
Q: I tried to flash a radio, but it says not allowed!
- You will also need ENG S-OFF to flash radios, because ENG S-OFF enables fastboot commands.
Q: I want to make my device stock, I cannot find the RUU but I have a backup of the stock rom.
- Follow these instructions.
Click to expand...
Click to collapse
Checking the device state:
- Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
- If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
- If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
- If system info CID is 11111111, your device is SuperCID
- And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
- You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
Click to expand...
Click to collapse
CID list:
- Unbranded: "HTC__001"
- O2: "O2___102"
- Orange: "ORANG001"
- German T-Mobile: "T-MOB101"
- Vodaphone UK: "VODAP001"
- More here
Click to expand...
Click to collapse
Troubleshooting:
- "Unknown error, probably connection"? See here, try with WiFi enabled.
- If that^ did not help, open a command window, go to the tool folder, and type: "adb shell" and "su". Then leave the window in the background, and run the tool again.
- "SD card failed"? When phone is connected to PC, check with some file manager that SD is accessible and works. Try another SD.
- Make sure you are rooted by downloading Terminal emulator from the market, write "su", '#' should appear.
- Check all the requirements. Twice. HTC Sync is mandatory!
- Keep your phone awake when you are running the tool, a superuser window might appear. You have to allow.
- Check your SD card, and tell us in the thread if a p7backup appeared on it.
- If it says Done and the CID does not change in ENG bootloader, you have most likely flashed too new radio.
Click to expand...
Click to collapse
Downloadcount:
v1: 1402 downloads
v2: 322 downloads
v2.1: 2396 downloads
Please do not re-upload the file anywhere.
WHOA! i just used your last tool to get s-off!
is this better? will it work over the previous one?
It will work over the S-OFF bootloader, I tested it myself
jkoljo said:
It will work over the S-OFF bootloader, I tested it myself
Click to expand...
Click to collapse
I can confirm that.
Hi,
how can i back to original?
My previous attempts have failed.
with friendly greet
starbase64
You will have to wait until Apache14 releases his kernel, which allows you to use command line to flash back the backup that is on your sdcard. The kernel works, so it is just a matter or time
Hi,
can not flash clockworkmod also.
with friendly greet
starbase64
So, this patches radio?
So if we run an oficial RUU or OTA, it overwrites the radio, thus restoring back to S-ON?
ttav said:
I can confirm that.
Click to expand...
Click to collapse
Yep, right on !
Eddie1506 said:
So, this patches radio?
So if we run an oficial RUU or OTA, it overwrites the radio, thus restoring back to S-ON?
Click to expand...
Click to collapse
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
afrcom15 said:
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
Click to expand...
Click to collapse
There is a partition 7 backup. Just restore that!
Sent from my Desire HD using XDA App
afrcom15 said:
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
Click to expand...
Click to collapse
How's that possible?
Sorry I'm confused what this is. What difference to the other s-off tool ?
Sent from my Desire HD using XDA App
vimto25 said:
Sorry I'm confused what this is. What difference to the other s-off tool ?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
yes tell us pls
This is permanent radio S-OFF as opposed to just ENG HBOOT S-OFF which can be wiped if you flash a standard ROM/RRU.
Flash this and you'll keep S-OFF no matter what you flash
JonnyFoxtrot said:
This is permanent radio S-OFF as opposed to just ENG HBOOT S-OFF which can be wiped if you flash a standard ROM/RRU.
Flash this and you'll keep S-OFF no matter what you flash
Click to expand...
Click to collapse
wow thanks
cool story!
THIS ROCKS!!!!!!!
If you use this one, you cannot use fastboot commands. If you like to play with your phone, then use the another one. This one is somewhat safer, however. In worst case scenario it is not possible to brick a device by using this tool, although to be honest, the other one has very very strict safety measures, too.
Jonny, the ENG bootloader will also survive a RUU if you do not have radio s-off.
jkoljo said:
If you use this one, you cannot use fastboot commands. If you like to play with your phone, then use the another one. This one is somewhat safer, however. In worst case scenario it is not possible to brick a device by using this tool, although to be honest, the other one has very very strict safety measures, too.
Jonny, the ENG bootloader will also survive a RUU if you do not have radio s-off.
Click to expand...
Click to collapse
so should we flash yes or no?
and why?
I have a backup with my stock ROM but when I go back to it everything still these such as root,s-off,Rom manager . So if I downloaded a clean stock ROM it will take everything off like it was when I first started phone up? And if I use this tool I can use stock ROM and my device is always s-off no matter what I do? Ifso how would you take s-off if needed for warranty issue. Thanks
Sent from my Desire HD using XDA App
DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
The title says it all!
Doktaphex said:
As the title suggests, this is warning against flashing the new RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_ 26.04.02.17_M2_release. It contains a new version of HBoot that breaks root and standard S-OFF! Please refer to these threads for more info:
http://forum.xda-developers.com/showthread.php?t=879375
http://forum.xda-developers.com/showthread.php?t=875099
You may be safe if you have full radio S-OFF and SuperCID but this is unconfirmed, and I would steer well clear until the DEVs have cracked open this latest HBoot.
Click to expand...
Click to collapse
Confirmed:
Only if you have full radio S-OFF you can 'downgrade' to 1.32xxxxxx and root
Yes, I can confirm that, too. You have to have Super-CID (Radio S-OFF) to downgrade. Rooting is not possible in this new one. Yet.
Can please someone explain me what's the real difference between ENG S OFF But CID 11111 and SHIP S OFF and CID HTC....?
ENG S-OFF: It is engineering bootloader S-OFF (may include Radio S-OFF). Allows custom bootloader commands, for example radio flashing, also allows to install custom roms.
SHIP S-OFF: Radio S-OFF, does not allow radio flashing, but allows ClockworkMod flashing. Usually comes together with SuperCID.
CID 11111111: Super-CID, Super Carrier ID, allows you to downgrade, and flash really anything to the phone without the phone saying "no thanks".
CID HTC__xxx: HTC Carrier ID, does not allow downgrading via RUU, but you can still flash through ClockworkMod if you are S-OFF.
Thank you very much for this answer..I ask because i cannot find this information somewhere in one post!
I am with ENG S-OFF and CID 11111111
So i can flash the new RUU and i am able to revert back to 1.32xxxxxx and root again.Correct?
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Yeah but it needs clockworkmod, which goes away if people use the actual RUU. Also flashing system.img does not replace the bootloader, so S-OFF stays in fine (also hboot S-OFF).
How can you tell what your CID is?
madindehead said:
How can you tell what your CID is?
Click to expand...
Click to collapse
Bootloader > Fastboot > System Info (or something like that)
If you are SuperCID then it is 11111111 if not, then it begins with HTC_xxxx
looks like also this RUU_Ace_Orange_ES_1.75.75.2_Radio_12.28e.60.140f_2 6.04.02.17_M2_release also seems to stop you gaining root and fix's patched Hboot as someone saying he flashed the rom and can't gain root.
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
can you tell how to extract the system.img from rom?
all i get is a [0] file. dont know what to do with it.
[HOW TO SAFELY FLASH THE NEW ROM AND BE ABLE TO REVERT BACK]
Currently, the new ROM (1.72.405.3) has a new HBOOT (so you can't install ENG HBOOT S-OFF) and is difficult to root (not as simple as it is with previous ROMs). However, it also has a better radio, and a faster ROM with various bugfixes. This ROM is also Android Froyo v2.21. If you want to try out the new ROM, whilst maintaining the ability to 'revert' back to your older, hackable state then follow the below instructions carefully. Also, do not worry about extracting system.img files and whatnot.
*It is recommended to do a NANDROID BACKUP first
*All RUUs can be obtained from www.xdafil.es/DesireHD/RUU/
*If you don't do steps 1-3 properly and flash the new ROM, you will not be able to revert back
*Radio S-OFF and SuperCID can be obtained by following instructions in this thread: http://forum.xda-developers.com/showthread.php?t=857537
*Tutorial for flashing RUUs (needed for steps 4 & 8): http://forum.xda-developers.com/showthread.php?t=841890
1. Install Radio S-OFF (NOT ENG HBOOT S-OFF) and SuperCID
2. Go to bootloader, then System Info. (If System Info is not there, but you have SHIP S-OFF skip step 3 and proceed to step 4)
3. Make sure CID is 11111111 *AND* the bootloader shows S-OFF. If not, repeat step 1
4. You can now flash the new ROM (1.72.405.3)
5. This will remove ENG HBOOT (if you had it) and ClockworkMod
6. If you did steps 1-3 correctly, your Desire HD should still be S-OFF. Go to bootloader and check. If not, you did not do steps 1-3 correctly and will have to wait for the new HBOOT to be cracked.
When you are done with the new ROM and want to go back, follow the instructions below:
7. Download the HTC RUU 1.32.405.6 of your choice (Since you are SuperCID you can flash any RUU)
8. Flash it to your Desire HD
9. Root your ROM using Visionary, and install ROM Manager and flash ClockworkMod. You can optionally install ENG HBOOT S-OFF now if you like.
If you made a NANDROID Backup, you can restore this now from ClockworkMod
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
I can't get this to work myself, unfortunately.
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
I have this working. The supplied .zip file does not include Superuser.apk. After following the instructions and then installing Superuser from the market I now have root on this rom.
Look forward to testing it over the next couple of days while I lay in hope of some custom roms based off this version.
EDIT: Superuser keeps force closing
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
doh!
being used to the days of winmo I flashed this rom over my cyanogen taking a backup first.
Now I can't revert back to the old stock rom, any way of doing this (easily ish)?
Hi, I'm ENG S-Off but my CID is not 1111111, what's the safest way to do the Super-CID?
I'm stucked abroad using a **** phone cos I can't use another sim in my DHD
Sent from my Desire HD using Tapatalk on Revolution 1. 92
ninja.rogue said:
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
Click to expand...
Click to collapse
Also on the same boat...
Anyone??
ninja.rogue said:
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
Click to expand...
Click to collapse
looks like you are, you have superCID.
I have a HTC One XL(no AT&T logo) that seems to have Hboot 2.1.5 (I went into the bootloader menu that appears when you vol + power on). I recently sent in my One X (with Tegra processor) in for warranty and somehow got a One XL back, so I don't know much about the phone. It came with Sense 5 and JB 4.2.2. I've already unlocked the bootloader via htcdev.com and flashed TWRP 2.6.3.0 recovery, and through that I flashed superuser.zip, which worked because I was able to use Titanium backup.
I wanted to follow the Facepalm S-Off guide ( http://forum.xda-developers.com/showthread.php?t=2155071 ) so that I could install a custom rom (LiquidSmooth). That guide requires my phone to be Super-CID, but I am unsure how to do that on my phone because it has Hboot 2.1.5 and all the one click installers specify hboot 2.1.4 or some AT&T firmware version that I don't know whether my phone has or not.
So does anybody know how to SuperCID or S-off my phone?
Thanks in advance
Unfortunately the 2.15 hboot has write protection enabled, which means it isn't possible for you to get SuperCID at the moment. Obviously that means you can't get s-off. I believe this problem is being worked on but we have no ETA yet. You should be able to flash most ROMs without s-off though, as you are on new enough firmware.
Sent from my Evita
timmaaa said:
Unfortunately the 2.15 hboot has write protection enabled, which means it isn't possible for you to get SuperCID at the moment. Obviously that means you can't get s-off. I believe this problem is being worked on but we have no ETA yet. You should be able to flash most ROMs without s-off though, as you are on new enough firmware.
Sent from my Evita
Click to expand...
Click to collapse
i dont know how but i am on 2.15 and i do have supercid and soff!?
You already had SuperCID and s-off before you upgraded to the 2.15 firmware.
Sent from my Evita
Can I S-OFF the hboot 2.02 ??
I mean this guide: http://forum.xda-developers.com/showthread.php?t=1399331 will work for my HBOOT 2.02 ?
No, because zergRush won't work. You'll have to unlock your bootloader to gain any sort of root.
Edit: this guide would work
http://forum.xda-developers.com/showthread.php?t=1318919
To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.
paulie-uk said:
To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.
Click to expand...
Click to collapse
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
I understand you have to downgrade first, and then S-OFF, but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Are you S-OFF paulie-uk?
readmanr said:
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
[...]
Are you S-OFF paulie-uk?
Click to expand...
Click to collapse
I'm hboot S-OFF (what revolutionary can provide), not radio S-OFF (sadly the only way to do this on SAGA is with some extra equipment). I believe the 2.02.0002 hboot came in the ICS RUU, it's just got a bit tighter security, I don't think the partitions have changed since the last version (someone correct me if I'm wrong here).
readmanr said:
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Click to expand...
Click to collapse
I'm using an S-OFFed ENGineering hboot, where you see people on the other version (2.00.0002) it is (usually) the stock SHIP hboot.
readmanr said:
I understand you have to downgrade first, and then S-OFF
Click to expand...
Click to collapse
You will have to downgrade. Sadly this will wipe your phone.
readmanr said:
but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
Click to expand...
Click to collapse
After you're S-OFF, I'd suggest you try a custom ROM and not flashing the 4.0.4 RUU (it's a buggy experimental version). Flashing an official RUU is pretty much how you return to stock, so it would most likely overwrite your S-OFFed hboot with a S-ON stock one. Remember, the S-OFF on our device is done in the hboot and not the radio.
When you're S-OFFed the first hboot you will have will be Revolutionary's 6.98 one. You can change this after.
I've found that 2.00.2002 works with all of the ROMs I've tried (which have been based on gingerbread, ICS and JellyBean). The "fake number" ones are there to make flashing a S-ON hboot more difficult, meaning that an OTA update wouldn't undo it. However, it is quite obvious if you were to send your phone in for repairs (still in warranty!?!?!) which is why a few of the tech-savvy who want S-OFF put on the ENG hboots instead.
If you want to overwrite Revolutionary's hboot with a different one with a lower version number, you will need to use dd and if it goes wrong it will brick your phone. You can find the ENG hboots on cyannogenmod's wiki if you don't trust the files I provide in other posts, but I strongly suggest you read about what you're going to do until you're comfortable with it before taking action.
Remember that after changing a hboot or radio, you should always re-wipe and re-flash your phone as partitions can move and always check the md5 first.
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor. Currently service provider is Koodo - a division of Telus (in Canada).
CID: ROGER001
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
arjundas86 said:
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor.
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
Click to expand...
Click to collapse
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
LS.xD said:
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
Click to expand...
Click to collapse
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
arjundas86 said:
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
Click to expand...
Click to collapse
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
LS.xD said:
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
Click to expand...
Click to collapse
Thanks for the toolkit.
cid: ROGER001
Btw, what's the purpose of going SuperCID?
Also, I don't want to install lower hboot. I am on hboot 1.08 and I think I need to install hboot 2.15. Right?
I guess S-OFF isn't absolutely necessary, but would be nice to have. Would you recommend using the S-OFF command from the toolkit you linked?
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
With superCID you can switch to other CIDs e.g. for unbranding your device Also it's needed for "Facepalm S-OFF" (Was the only working method for me)
Sent from my loved HTC One S using (most time buggy) Tapatalk
LS.xD said:
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
arjundas86 said:
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
Click to expand...
Click to collapse
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
LS.xD said:
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
Click to expand...
Click to collapse
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
arjundas86 said:
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
Click to expand...
Click to collapse
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
LS.xD said:
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
Click to expand...
Click to collapse
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
arjundas86 said:
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
Click to expand...
Click to collapse
To run a RUU NOT MATCHING your stock CID you need S-OFF // SuperCID. You cant install TMobile RUU at first :/
I would act like this:
Run latest Rogers RUU --> READ FACEPALM GUIDE CAREFULLY. There is how to gain SuperCID and then S-OFF. Once done you can change CID to whatever you want and run a (unbranded) RUU with HBoot 2.15.
But that is just what i thought about it. I suggest to let someone else CONFIRM the way suggested by me first.
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
@Rapier
thank you for the provided help as usual
Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
LS.xD said:
...Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
Click to expand...
Click to collapse
For you? NO. You're better than me
The story is like this. I bought the phone in 2012. At that time, the highest hboot was 1.14 I believe (don't remember exactly) and there was no S-Off method available (they appeared later). There was something else tho. The lower hboots (1.09 and lower) permitted to write in the kernel partition or radio partition like an S-Off device. HTC then covered this in the higher hboots. So even if there was no S-Off method, there was a downgrade method that was used to downgrade the hboot from whatever you had to 1.09 or below. I downgraded mine to 1.06...don't ask why I didn't choose 1.09, I thought that was the RUU I considered to be fine for me at that time.
Now being on hboot 1.06 I can do anything except I cannot flash firmwares directly. So I cannot flash a new hboot with red letters removed for example. But I don't care about this...I can flash radios or kernels or splash screens like any S-Off user. The procedure for getting latest firmware and S-Off seems a little bit risky and I've read about alot of issues or problems from people who failed or tried countless times to reach that. So I've asked myself why should I do that if I don't need it?
Then it came the rumor and there were some brick cases of devices that were having some Android 4.3 ROMs and were not on latest firmware (in the meantime 2.13 and 2.15 hboots arise and also the S-Off method). It proved to be not the firmware fault after all. But CM team has included a check in the updater script of the ROM ZIP, to validate if the hboot was 2.13 or 2.15...if not, the flash won't happen. It's a simple assert command present there at the beginning of the script that do the check. As CM team was the pioneer in having the newest Android version ROMs available, everybody based initially their ROMs/builds on CM...so the check in the script was automatically carried over to all the ROMs out there. And it's still here.
As I've tested and I could run fine those ROM's (by removing the check before flash), I noticed that this requirement does not apply to everyone. Some could run fine the ROMs even if they're not on the "latest" firmware.
So that's why I am on 1.06...cause I don't know why should I go through some risky procedures when I don't need to.
Rapier said:
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
Click to expand...
Click to collapse
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
Rapier said:
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
Click to expand...
Click to collapse
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
LS.xD said:
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
Just IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
Click to expand...
Click to collapse
Yes, you're right. That's what I meant. I will delete the updater-script lines that Rapier mentioned before trying to install CM11.
If it doesn't work, at least I can restore to my backup, without risk of bricking.
Then I can try the hboot update and s-off if required.
Thanks.
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444....
Click to expand...
Click to collapse
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't want
arjundas86 said:
...I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
It's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
BUT, if you're NOT going to upgrade your firmware and you'll be lucky to have the ROM working, you won't need to S-Off since your current hboot is lower than 1.09 and allows you to flash radios and kernels directly from recovery.
And at this point, as you said, it worth a try like you are now and only if it's not working like this you should upgrade and do S-Off. I guess is much easier and less risky to remove 4 lines from that script and flash the ROM to see if it's working, than to go through the firmware upgrade & S-Off procedures
Rapier said:
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't wantIt's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
Click to expand...
Click to collapse
Hey Rapier,
I'm having trouble doing getting the zip signed.
I tried the zip signer you had in your guide, as well as a bunch of other zip signing programs, but none of them seem to do the job. I keep getting Error: Status 7.
Not getting bootloops or anything like that, so I was able to restore to my backup. No harm done.