Dear All,
I just S-off and rooted a HTC Sensation 4G the cid when it was S-offed and rooted was cidnum: T-MOB010. I have as a newbie had wiped my original stock ROM but I do have a backup. From what i read from the forum adb tools require you to setup the phone in USB debugging and change to charging mode. Right now I do not have a ROM installed. My question is , is there anyway I can change the CID to superCID so i can install any ROM. I'm trying to find ROMs to work on my htc but still no luck. I was wondering whether if I superCID'd it then i would have a better chance. THanks!
Don't think you can. You must use ADB. Sorry
Can you suggest a ROM for me if possible so at least I can install it and then change the CID. I was looking over virtuousrom where there is support for t-mob010
Thanks in advance for the help!
Deathsongx3 said:
Don't think you can. You must use ADB. Sorry
Click to expand...
Click to collapse
I'm not sure what that is, I don't live in US but if you need a great rom, I can suggest a few.
http://forum.xda-developers.com/showthread.php?t=1408351
Virtuous Inquisition is a great senseless rom, i've been using it for a few months. Smooth and all.
But if you are a sense lover, you can go for InsertCoin
http://forum.xda-developers.com/showthread.php?t=1468683
Goodluck~
numb2droid said:
Can you suggest a ROM for me if possible so at least I can install it and then change the CID. I was looking over virtuousrom where there is support for t-mob010
Thanks in advance for the help!
Click to expand...
Click to collapse
You need to SuperCID via ADB tools.
You can run the ADB commends required even if you do not have a ROM installed as it uses fastboot.
You do NOT need to have SuperCID in order to install and use a Custom ROM.
What does your Bootloader screen say at the moment ? As in have you still got GB compatible Firmware or ICS compatible Firmware ?
As the person above me said, you don't need to boot your phone in order to supercid it. Do what is said here http://forum.xda-developers.com/showthread.php?t=1192300 and skip steps 5,6,7.
And to install a rom, you don't need to supercid... just install the firmware it asks you to install and then, install the rom. I'd recommend ARHD 6.3.0, get the firmware package for your cid from here: http://forum.xda-developers.com/showthread.php?t=1459767 (just be sure to take the 3.30 one) and follow this guide: http://forum.xda-developers.com/showthread.php?t=1471941
P.S. Any rom is compatible with your CID as long as you have the right firmware package I think. (Just wait for someone to confirm what I'm saying, because I'm not sure)
youssefkiev said:
As the person above me said, you don't need to boot your phone in order to supercid it. Do what is said here http://forum.xda-developers.com/showthread.php?t=1192300 and skip steps 5,6,7.
And to install a rom, you don't need to supercid... just install the firmware it asks you to install and then, install the rom. I'd recommend ARHD 6.3.0, get the firmware package for your cid from here: http://forum.xda-developers.com/showthread.php?t=1459767 (just be sure to take the 3.30 one) and follow this guide: http://forum.xda-developers.com/showthread.php?t=1471941
P.S. Any rom is compatible with your CID as long as you have the right firmware package I think. (Just wait for someone to confirm what I'm saying, because I'm not sure)
Click to expand...
Click to collapse
Any custom ROM will work with any CID, assuming compatible firmware and radio. You need the "appropriate" CID to install RUUs. For example when I first got the phone the first thing I did was to change the CID and install a generic European RUU to debrand it.
EDIT: compatible firmware relates to the HBOOT version and has no relevance to the CID itself. There are compatible firmware/radio combinations. The appropriate Radio is included with the ICS firmware packs.
Note: If you revert back to 1.17 HBOOT for GB ROMs you'll need to flash an appropriate Radio. There is a thread in the dev section: http://forum.xda-developers.com/showthread.php?t=1178143
The reason there are so many CIDs mentioned in the firmware thread, is that many CIDs seem to have popped up for the Sensation and many folks didn't SuperCID. The reason in that thread for so many installs for groups of CID versions of the firmware, is that there appears to be a limit on the number of characters in the section that checks the CID. ALL the firmware downloads are the same (for the same HBOOT version), they just do different CID checks. If you're SuperCID and of them will work. I hope the explanation isn't too convoluted.
Does anyone know that if I can change the CID of my sensation z710a with ADB WIFI as the usb port is not working?Thanks.
seawind107 said:
Does anyone know that if I can change the CID of my sensation z710a with ADB WIFI as the usb port is not working?Thanks.
Click to expand...
Click to collapse
you cant :/
Sent from my HTC Sensation Z710e using XDA
Hi,
sorry for asking because the forums are full of information on how to root the HTC Sensation but I'm a bit overwhelmed and though I read through several threads before starting I just want to be sure I understand everything right and the information provided is still valid.
First some information about my phone:
My phone is completely stock and just arrived back from an HTC repair (no motherboard change concerning repair report). It's not branded (bought retail).
Android 4.0.3
Sense 3.6
Software version: 3.33.401.53
Kernel-Version: 3.0.16-g31a4fc7
Baseband-Version: 11.76A.3504.00U_11.24A.3504.31_M
Build number: 3.33.401.53 CL391535
Browser-Version: WebKit/534.30
HBOOT 1.27.0000
I'm on Windows 7 x64.
My goal is to install a JB ROM with root access.
I saw some all-in-one tools to achieve my goal:
[TOOL][2 DEC] HTC Sensation/XE/4G Super Utility (AIO) by kgs1992 v8.0
[TOOL] HTC Sensation 4G All-In-One Toolkit V4.0 [7-16-2013] [Noob-Proof]
Is it safe to use such tools, do they well in guiding me through the needed steps and which one is better/safer/easier/more up-to-date?
If going "manually" as far as I understood I have two choices:
1. S-OFF via HTC Dev unlock (auggie2ks guide)
OR
2. S-OFF via the new method HERE.
Which one is better/safer/easier? Will they work with firmware 3.33 (only 3.32 is mentioned)?
Concerning the 2nd guide the wire trick is easier in 1st guide? What else is more complicated there?
Now concerning the order of the manual steps and some questions (referring to [GUIDE] How to Root & S-OFF HTC Sensation - HBOOT 1.27.0000 & Firmware 3.33! and [GUIDE] Juopunutbear S-OFF (HBOOT 1.27.0000 with 3.32 ICS Firmware)):
1. Requirements:
1.1 HTC drivers (windows)
1.2 Enable USB Debugging
1.3 SDCARD ready to be wiped
1.4 Prepared paperclip
2. Steps to perform in that order
2.1 HTC Dev unlock (in case of not using the new method in point 2 above)
2.2 Temp root the phone by flashing Superuser-3.0.7-efghi-signed.zip
How to flash?
2.3 Flash boot.img from Stock 3.32 Rooted ROM in Fastboot
Currently I seem to be on 3.33 so which one to use and where to get the stock rooted ROM from?
2.4 Run Juopunutbear, follow instructions and do the wire trick
2.5 Flash custom recovery (4-EXT) with HTC Sensation 4G All-In-One Toolkit
2.6 Permanently root the phone with HTC Sensation 4G All-In-One Toolkit
2.7 Write Super CID
Do I need this (unbranded retail phone)?
Further questions:
I also read about some universal Firmware HERE. Do I need this when already on (stock) 3.33?
Do I need to flash some special radio (I'm in Germany)?
ROM decision:
After all the mess with S-OFF I'd like to install a nice JB ROM and would be very happy for suggestions because of the great amount of ROMs available in the DEV forum.
What features should I pay attention on (I noticed some problems on stock with free RAM and maybe for example there are some ROMs addressing this in some way)?
Thanks in advance for some hints
Regs,
slaecker
real_sl4cker said:
Hi,
sorry for asking because the forums are full of information on how to root the HTC Sensation but I'm a bit overwhelmed and though I read through several threads before starting I just want to be sure I understand everything right and the information provided is still valid.
First some information about my phone:
My phone is completely stock and just arrived back from an HTC repair (no motherboard change concerning repair report). It's not branded (bought retail).
Android 4.0.3
Sense 3.6
Software version: 3.33.401.53
Kernel-Version: 3.0.16-g31a4fc7
Baseband-Version: 11.76A.3504.00U_11.24A.3504.31_M
Build number: 3.33.401.53 CL391535
Browser-Version: WebKit/534.30
HBOOT 1.27.0000
I'm on Windows 7 x64.
My goal is to install a JB ROM with root access.
I saw some all-in-one tools to achieve my goal:
[TOOL][2 DEC] HTC Sensation/XE/4G Super Utility (AIO) by kgs1992 v8.0
[TOOL] HTC Sensation 4G All-In-One Toolkit V4.0 [7-16-2013] [Noob-Proof]
Is it safe to use such tools, do they well in guiding me through the needed steps and which one is better/safer/easier/more up-to-date?
If going "manually" as far as I understood I have two choices:
1. S-OFF via HTC Dev unlock (auggie2ks guide)
OR
2. S-OFF via the new method HERE.
Which one is better/safer/easier? Will they work with firmware 3.33 (only 3.32 is mentioned)?
Concerning the 2nd guide the wire trick is easier in 1st guide? What else is more complicated there?
Now concerning the order of the manual steps and some questions (referring to [GUIDE] How to Root & S-OFF HTC Sensation - HBOOT 1.27.0000 & Firmware 3.33! and [GUIDE] Juopunutbear S-OFF (HBOOT 1.27.0000 with 3.32 ICS Firmware)):
1. Requirements:
1.1 HTC drivers (windows)
1.2 Enable USB Debugging
1.3 SDCARD ready to be wiped
1.4 Prepared paperclip
2. Steps to perform in that order
2.1 HTC Dev unlock (in case of not using the new method in point 2 above)
2.2 Temp root the phone by flashing Superuser-3.0.7-efghi-signed.zip
How to flash?
2.3 Flash boot.img from Stock 3.32 Rooted ROM in Fastboot
Currently I seem to be on 3.33 so which one to use and where to get the stock rooted ROM from?
2.4 Run Juopunutbear, follow instructions and do the wire trick
2.5 Flash custom recovery (4-EXT) with HTC Sensation 4G All-In-One Toolkit
2.6 Permanently root the phone with HTC Sensation 4G All-In-One Toolkit
2.7 Write Super CID
Do I need this (unbranded retail phone)?
Further questions:
I also read about some universal Firmware HERE. Do I need this when already on (stock) 3.33?
Do I need to flash some special radio (I'm in Germany)?
ROM decision:
After all the mess with S-OFF I'd like to install a nice JB ROM and would be very happy for suggestions because of the great amount of ROMs available in the DEV forum.
What features should I pay attention on (I noticed some problems on stock with free RAM and maybe for example there are some ROMs addressing this in some way)?
Thanks in advance for some hints
Regs,
slaecker
Click to expand...
Click to collapse
For rooting as S-Off, Unlock bootloader first and then follow auggie2ks guide for S-off as the wire trick is relatively easier than no htcdev unlock method.
If your goal is to only install custom JB Rom then you can do it by just unlocking bootloader and then flashing 4Ext Recovery via fastboot. For flashing Rom just enable smartflash in the 4EXT recovery tools option and you're good to go to flash custom ROM.
For rooting there is a permanent one click root tool present in ganeshp guide for S-Off(No htcdev unlock one).
For flashing universal firmware you need to be S-Off. If you plan to do so then do S-off now as Stock ROM is a prerequisite to attain S off.
For good JB Rom you have many options. If you want Sense based ROM then flash ViperS 3.1.2 JB with Sense 4+.
Sent from my HTC Sensation Z710e
MrJukeHardbane said:
For rooting as S-Off, Unlock bootloader first and then follow auggie2ks guide for S-off as the wire trick is relatively easier than no htcdev unlock method.
If your goal is to only install custom JB Rom then you can do it by just unlocking bootloader and then flashing 4Ext Recovery via fastboot. For flashing Rom just enable smartflash in the 4EXT recovery tools option and you're good to go to flash custom ROM.
For rooting there is a permanent one click root tool present in ganeshp guide for S-Off(No htcdev unlock one).
For flashing universal firmware you need to be S-Off. If you plan to do so then do S-off now as Stock ROM is a prerequisite to attain S off.
For good JB Rom you have many options. If you want Sense based ROM then flash ViperS 3.1.2 JB with Sense 4+.
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
Hi,
many thanks for the reply.
I wonder what exactly is universal firmware and if I need it at all?
If I go for S-OFF are the steps I wrote above correct or have I mixed something or unneccessary stuff in there?
What about Super CID? What exactly is this and do I need that?
Concerning a good JB ROM I prefer non-Sense because meanwhile I like the feel of pure Android.
Regs,
slaecker
real_sl4cker said:
Hi,
many thanks for the reply.
I wonder what exactly is universal firmware and if I need it at all?
If I go for S-OFF are the steps I wrote above correct or have I mixed something or unneccessary stuff in there?
What about Super CID? What exactly is this and do I need that?
Concerning a good JB ROM I prefer non-Sense because meanwhile I like the feel of pure Android.
Regs,
slaecker
Click to expand...
Click to collapse
universal firmware is a patched firmware and you can flash it only when you are on S-OFF
if you go for S-OFF just follow only ganeshp's guide
supercid gives you the ability to install whatever ruu.exe you want
rzr86 said:
universal firmware is a patched firmware and you can flash it only when you are on S-OFF
if you go for S-OFF just follow only ganeshp's guide
supercid gives you the ability to install whatever ruu.exe you want
Click to expand...
Click to collapse
Thanks, what are the benefits of this patched firmware?
real_sl4cker said:
Thanks, what are the benefits of this patched firmware?
Click to expand...
Click to collapse
it contains a patched hboot which is unlocked and free to any fastboot command
real_sl4cker said:
Baseband-Version: 11.76A.3504.00U_11.24A.3504.31_M
Build number: 3.33.401.53 CL391535
My goal is to install a JB ROM with root access.
Is it safe to use such tools, do they well in guiding me through the needed steps and which one is better/safer/easier/more up-to-date?
Click to expand...
Click to collapse
Yes, relatively they're safe. But I highly recommend not using them. They will unlock your device, but you will have a hard time maintaining it.
real_sl4cker said:
If going "manually" as far as I understood I have two choices:
1. S-OFF via HTC Dev unlock (auggie2ks guide)
OR
2. S-OFF via the new method HERE.
Which one is better/safer/easier? Will they work with firmware 3.33 (only 3.32 is mentioned)?
Concerning the 2nd guide the wire trick is easier in 1st guide? What else is more complicated there?
Click to expand...
Click to collapse
The wire trick will be a easier in method 1.
If you just want JB roms, and seeing as you are on 3.3x already, you need not change your firmware (s-off not needed for flashing roms). You however can update your radio if you choose to S-OFF.
With S-OFF, you'll have a easier time flashing roms though.
real_sl4cker said:
2. Steps to perform in that order
2.2 Temp root the phone by flashing Superuser-3.0.7-efghi-signed.zip
How to flash?
Click to expand...
Click to collapse
You should have a custom recovery by now. You can flash zips in it.
real_sl4cker said:
Currently I seem to be on 3.33 so which one to use and where to get the stock rooted ROM from?
2.4 Run Juopunutbear, follow instructions and do the wire trick
2.5 Flash custom recovery (4-EXT) with HTC Sensation 4G All-In-One Toolkit
2.6 Permanently root the phone with HTC Sensation 4G All-In-One Toolkit
2.7 Write Super CID
Do I need this (unbranded retail phone)?
Click to expand...
Click to collapse
S-OFF is needed to superCID and to flash unsigned firmware and/or hboots. Unless you want to flash an ruu not originally meant for your device you'll need superCID.
real_sl4cker said:
Further questions:
I also read about some universal Firmware HERE. Do I need this when already on (stock) 3.33?
Do I need to flash some special radio (I'm in Germany)?
Click to expand...
Click to collapse
Don't fix it if it ain't broke.
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
AFAIU it all depends on the xxx after the 3.16. in the version of the firmware, which method is likely to work with your device.
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
I was able to change to supercid with the same config as you have ( 3.16.401.8 and origo cid HTC__001) so it should for you. If you'll manage to supercid just get s-off useing facepalm metod. Worked for me.
Sent from my HTC One S
if you got the xxxxxxx.9 it wont work indeed.
but on the xxxxxxxx.8 supercid/facepalm method should work, i did this myself back then.
since hboot didnt change going from .8 to .9, it might be possible to reflash the ruu to get back on .8 (as you did before i presume).
but if the ota going to .9 did change something permanent its a bust.
I believe the RUU I tried flashing was HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L...
-If I go the Facepalm route, I have to SuperCID. I can't because I am unable to change mmcblk0p4 (write-protection, I'm guessing. I did take the JB OTA from T-Mobile at one point...)
-If I go the Moonshine route, the device crashes when Moonshine tries the ADB test (reboot from bootloader). This happens using the ville_3.16.661.4 and ville_3.14.531.11 versions...
Possible solutions:
1. Downgrade hboot to an earlier version without write-protection on mmcblk0p4 so I can SuperCID -> Facepalm. I'm currently on hboot 2.15 - is this possible?
2. Flash a ROM of a firmware supported by Moonshine - anyone have that?
rialsolk pecans
UPDATE: I apologize for the double post, but I was able to S-OFF using Moonshine.
What I used:
ViperROM 2.1
TWRP 2.3.3.0
Windows 7 Pro x64
Moonshine - HTC One S Telus Windows 3.16.661.4
I currently have hboot 2.15. Thanks for looking!
Hi guys,
so happy to be a part of this community!
My HTC One S is unlocked, rooted and S-ON:
CID: T-MOB102
HBOOT: 2.15
I'm currently using MaximusHD 10.0 (though I couldn't make the firmware upgrade because I'm not S-OFF).
I'm creating this thread because none of the currently opened ones covers my case. I wanted to S-OFF earlier and tried Facepalm but could not get superCID (as far as I know this is because of the write protection), so this method didn't work for me. Moonshine I think will not work also, because I'm not using a stock ROM. ( From the Moonshine instructions: 8. Use the matching Stock RUU, some stock based ROMs may work, but we cannot test them all.)
Before flashing MaximusHD 10.0 I've made a backup of my original 4.1.1 ROM that came with the device with the custom recovery (TWRP 2.4.3.0 as far as I can remember). Unfortunately when I try restoring from backup my device is in a bootloop.
Can you please advise how to obtain S-OFF so that I can enjoy the MaximusHD?
Please accept my apologies if this is not the right place for this thread.
Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
No, unfortunately I could not find stock RUU for TMOBA devices
If you need stock ruu go to www.htc.com and select your device and download the file for this file to work you need your bootloader to be lock stock or relocked. and just run the ruu and it shold work..
so you dont have any problems enter fastboot and make sure it says fastboot usb and than run ruu and it should put your phone to stock. I just did this with my phone.
Are you refering to the downloads at htcdev because I couldn't find anything else?
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.