Wait a minute here.
I have the latest ota zip which I pulled off my htc one s before I flashed rooted super cid and so fourth.
Anyway. My hboot in the ota zip shows a hboot 1.14.0005 youre saying that the newest HBOOT is 2.15?
I am on tmobo usa in Connecticut can someone verify what the latest HBOOT is for a branded tmobo usa phone is?
hboot_ville_1.14.0005_signedbyaa.nb0 is whats inside the firmware.zip dated 1/28/2013
So whats this 2.15 you speak of?
Flash
So since im supercid s-off rooted custom rom can I boot into twrp and flash the firmware.zip and radio.img rcdata manually to get the newest radio and hboot?
Or will this have bad effects on my s-off and custom rom?
Please note there's a risk if u up to JB
Tim2246 said:
Wait a minute here.
I have the latest ota zip which I pulled off my htc one s before I flashed rooted super cid and so fourth.
Anyway. My hboot in the ota zip shows a hboot 1.14.0005 youre saying that the newest HBOOT is 2.15?
I am on tmobo usa in Connecticut can someone verify what the latest HBOOT is for a branded tmobo usa phone is?
hboot_ville_1.14.0005_signedbyaa.nb0 is whats inside the firmware.zip dated 1/28/2013
So whats this 2.15 you speak of?
Click to expand...
Click to collapse
DEAR TIM,
The 2.15 HBOOT is use for the euro JB system, is u change SCID to 11111111 and S-off, then u can RUU to the EURO version
Tim2246 said:
So since im supercid s-off rooted custom rom can I boot into twrp and flash the firmware.zip and radio.img rcdata manually to get the newest radio and hboot?
Or will this have bad effects on my s-off and custom rom?
Click to expand...
Click to collapse
No, you cannot run ota.zips in custom recoveries, such as twrp. You need to relock and flash stock recovery, but of you do that, you might as well upgrade to the latest as the guy above mentioned.
I guess tmobile has not released the update yet, that's why you don't have the latest
But why do all that, just flash a radio from the radio collection/installer and be done with it. No benefit in updating hboot. There are lots of zips in the dev section already premade to install hboots in recovery...if you really want, but messing with hboot always Carries risk..I'd say, don't touch it.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Thank You
ROBBIE0528 said:
DEAR TIM,
The 2.15 HBOOT is use for the euro JB system, is u change SCID to 11111111 and S-off, then u can RUU to the EURO version
Click to expand...
Click to collapse
Thanks for the rapid response.
But if I change my cid from htc__001 to super cid and run the ruu that means I cant do any of there ota's for it will brick according to the forums though correct?
And I though if I extracted the radio.img and rcdata zip I could flash them separately.
Just not sure how.
The most you can do is 2.35.531.12, which is 1.xx hboot, positive. 2.15 is the Jellybean OTA hboot version. But if you r going to do those things, it should require the HTC__xxx or SuperCID2 (22222222). Also, I bricked my fone doing the update, so you should just flash CM10 and screw TMOUS because it deserved to be shi**ed, screwed, and fuc**d on.
you'll get updates quicker thru the devs than the carrier
that's one reason we rooted
Tim2246 said:
Thanks for the rapid response.
But if I change my cid from htc__001 to super cid and run the ruu that means I cant do any of there ota's for it will brick according to the forums though correct?
And I though if I extracted the radio.img and rcdata zip I could flash them separately.
Just not sure how.
Click to expand...
Click to collapse
the JB system(HBOOT 2.XXX.X) won't allow u to flash radio.img individual.
Only Hboot below 1.13.xxx can flash separately~
Tim2246 said:
Thanks for the rapid response.
But if I change my cid from htc__001 to super cid and run the ruu that means I cant do any of there ota's for it will brick according to the forums though correct?
And I though if I extracted the radio.img and rcdata zip I could flash them separately.
Just not sure how.
Click to expand...
Click to collapse
Super cid and ruu is fine...just don't do ota while super cid.
Once you do the ruu mentioned, you'll be right up to date and no need for ota anyways.
ROBBIE0528 said:
the JB system(HBOOT 2.XXX.X) won't allow u to flash radio.img individual.
Only Hboot below 1.13.xxx can flash separately~
Click to expand...
Click to collapse
Unless you are s-off...once s-off, hboot doesn't matter.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Related
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
You need to read up a bit and start again
http://forum.xda-developers.com/showthread.php?t=1192300
zahdekar said:
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
Click to expand...
Click to collapse
have you already tried step 4 here?
matt95 said:
have you already tried step 4 here?
Click to expand...
Click to collapse
yes ı tried repeatedly. but always ı get fat error in adb.
do you want to upgrade to 3.25 right?
---------- Post added at 12:48 AM ---------- Previous post was at 12:46 AM ----------
http://forum.xda-developers.com/showthread.php?t=1459767
look here...search HTC part 2...there is your cid HTC__M27 download 3.24 file and install it
yes ı want to update to 3.25 and install any radio.
zahdekar said:
yes ı want to update to 3.25 and install any radio.
Click to expand...
Click to collapse
i have found the 3.24 file try installing it and do supercid with that hboot
ok i tried. but not work. hboot is still 1.23
zahdekar said:
ok i tried. but not work. hboot is still 1.23
Click to expand...
Click to collapse
i think you already know it but just to be sure...you have to download the file i attached you before and then put that file on your sdcard and then reboot in bootloader....have you done so?
zahdekar said:
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
Click to expand...
Click to collapse
dude, you are s-on, you can't flash radios sorry. Shoulda used revolutionary.
yes i downloaded part 2, 3.24 zip file and placed root of sd card. flashed in fastboot.i got " wrong file or no file" error.
zahdekar said:
yes i downloaded part 2, 3.24 zip file and placed root of sd card. flashed in fastboot.i got " wrong file or no file" error.
Click to expand...
Click to collapse
are you sure that it is your cid? type this on cmd and tell me what it says: fastboot getvar cid (obviusly you have to be on fastboot mode)
Behold_this said:
dude, you are s-on, you can't flash radios sorry. Shoulda used revolutionary.
Click to expand...
Click to collapse
ok. but revolutionary dont support hboot 1.23.
matt95 said:
are you sure that it is your cid? type this on cmd and tell me what it says: fastboot getvar cid (obviusly you have to be on fastboot mode)
Click to expand...
Click to collapse
C:\android-sdk-windows\platform-tools>fastboot getvar cid
< waiting for device >
cid: HTC__M27
finished. total time: 0.003s
zahdekar said:
C:\android-sdk-windows\platform-tools>fastboot getvar cid
< waiting for device >
cid: HTC__M27
finished. total time: 0.003s
Click to expand...
Click to collapse
that's strange man...the one i provided should work...hmmm
zahdekar said:
ok. but revolutionary dont support hboot 1.23.
Click to expand...
Click to collapse
That's correct. You screwed yourself when you updated to ics firmware with s-on (or you set s-on after flashing though i can't figure out why). You are stuck for now until revolutionary supports the new hboot or until a new update that is supported comes out. You can now only upgrade, no downgrading for you, until s-off.
Behold_this said:
That's correct. You screwed yourself when you updated to ics firmware with s-on (or you set s-on after flashing though i can't figure out why). You are stuck for now until revolutionary supports the new hboot.
Click to expand...
Click to collapse
well if he could find the right fw witout supercid it could upgrade
Do I have to wait for the update of revolutionary? i can install custom 4.0.1 ice rom. but it is very slow and i cannot install official rom.
zahdekar said:
Do I have to wait for the update of revolutionary? i can install custom 4.0.1 ice rom. but it is very slow and i cannot install official rom.
Click to expand...
Click to collapse
Well I think revolutionary will not support that one... They are supporting the newer why support an older one?
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
matt95 said:
Well I think revolutionary will not support that one... They are supporting the newer why support an older one?
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Click to expand...
Click to collapse
ok. thanks for help. if you find a way. please share on this post. OK?
Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?
I am having at&t htc one x bootloader with :
**** tampered ****
**** unlocked ****
evita pvt shp s-on rl
hboot-1.09.0000
radio-0.19as.32.09.09_l
opendsp-v28.1.0.32.0504
emmc-boot
apr 2 2012,21:08:24
installed twrp 2.2.0 recovery and stock rooted rom 2.23707.2 asia generic.
Now the problem is, i am facing the mobile signal(not wifi) dropping issues and i have to revert back to at&t stock rom, i have downloaded the official at&t ruu 2.20.502.2.....exe,
but i am concerned with the doubt that will the ruu will work 100% on supercid 111111 without any problem after relocking the bootloder or do i have to revert back the stock at&t cid, and if yes then what is the procedure to revert back the stock at&t cid???????
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
gunnyman said:
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
Click to expand...
Click to collapse
thanks for the help,appreciable. But i don't want to flash just the radio, coz i already did that, but it did not solve my problem. So the question still continues..Can i run Ruu with the current supercid 111111 or do i have to revert it back to stock???
SORRY FOR BAD ENGLISH. ITS NOT MY FAMILIAR LANGUAGE.
You don't have to change cid to flash the ruu just relock the bootloader
gunnyman said:
you don't have to change cid to flash the ruu just relock the bootloader
Click to expand...
Click to collapse
thanks for the help,
Are you already on 2.20? If not, why not run 1.85 RUU?
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
good question.
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
Doesn't look like the op is on 2.20, the hboot for 2.20 is 1.14.0002.
Absolutely Right, i am not on 2.20,
Sent from my HTC One XL using xda app-developers app
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
hemsmaverick said:
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
Click to expand...
Click to collapse
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
gunnyman said:
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
Click to expand...
Click to collapse
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
hemsmaverick said:
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
Click to expand...
Click to collapse
won't work because RUU's include a signature check and if you alter the files in any way, that signature check will fail.
gunnyman said:
won't work because ruu's include a signature check and if you alter the files in any way, that signature check will fail.
Click to expand...
Click to collapse
ok, well as per ur earlier suggestion, i have flash the radio incl ril files from at&t 1.85, asia 2.23, currently on a o2 2.29.
But signal dropping solution has not been resolved.
I have dropped the plan of running ruu and will install custom rom tn special edition 3.6
can u suggest me the best radio for better mobile signals? (i am from india -region asia)
is it possible to update only the hboot ( stuck with 2.09 no RUU's for CID OPTUS001 ) , can it be done just by flashing the hboot img ?
If not is there any other way I can update my hboot ? thanks
Bricking
is there any risk that involves like bricking my phone if i tried to manually flash hboot.img file ?
nipunf said:
is there any risk that involves like bricking my phone if i tried to manually flash hboot.img file ?
Click to expand...
Click to collapse
It's possible that you might brick your phone by updating the HBOOT. I wouldn't do it. Why do you want to anyway?
JB
well I just wanted to try jb that’s all , since there is no 4.0.4 update for my phone I was thinking if I update my hboot from 2.09 to 2.11 I might have a chance installing JB
Installing JB that way will not work. You may want to try installing the RUU.
usaff22 said:
Installing JB that way will not work. You may want to try installing the RUU.
Click to expand...
Click to collapse
can we bypass the CID check in RUU ?
nipunf said:
is it possible to update only the hboot ( stuck with 2.09 no RUU's for CID OPTUS001 ) , can it be done just by flashing the hboot img ?
If not is there any other way I can update my hboot ? thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2234559
firmware.zip package from HTC for One S (Snapdragon S3, VilleC2). Follow the instructions, so you will update your hboot, radio, recovery, etc.
the problem is the cid
my cid is BSTAR301 and I can´t find a way to update anything on my phone. I stuck on 4.0.3
I have the ota so i can just extract the radio.img and rcdata? or what do i need to extract?
Now i do have the newest ota so how would I flash the info?
I dont want to have to unroot, uncid relock all that bs so since i am super cid and rooted with twrp can i just run the ota from twrp and get the updated hboot which is 1.4.0005
and radio and so fourth?
Why, no difference in hboot and radio you can flash in recovery.
To answer your question, no. OTA's cannot be run in custom recovery or if unlocked.
By the way, latest hboot is 2.15
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
latest hboot?
ryanshew said:
Why, no difference in hboot and radio you can flash in recovery.
To answer your question, no. OTA's cannot be run in custom recovery or if unlocked.
By the way, latest hboot is 2.15
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Click to expand...
Click to collapse
Wait a minute here.
I have the latest ota zip which I pulled off my htc one s before I flashed rooted super cid and so fourth.
Anyway. My hboot in the ota zip shows a hboot 1.14.0005 youre saying that the newest HBOOT is 2.15?
I am on tmobo usa in Connecticut can someone verify what the latest HBOOT is for a branded tmobo usa phone is?
Tim2246 said:
I have the ota so i can just extract the radio.img and rcdata? or what do i need to extract?
Now i do have the newest ota so how would I flash the info?
I dont want to have to unroot, uncid relock all that bs so since i am super cid and rooted with twrp can i just run the ota from twrp and get the updated hboot which is 1.4.0005
and radio and so fourth?
Click to expand...
Click to collapse
1) What OTA??? T-Mobile OTA or Jellybean?
2) Run the RUU!!! Whatcha talking about, extracting rom.zip!!! Not necessary.
Tim2246 said:
Wait a minute here.
I have the latest ota zip which I pulled off my htc one s before I flashed rooted super cid and so fourth.
Anyway. My hboot in the ota zip shows a hboot 1.14.0005 youre saying that the newest HBOOT is 2.15?
I am on tmobo usa in Connecticut can someone verify what the latest HBOOT is for a branded tmobo usa phone is?
Click to expand...
Click to collapse
Boot it into HBOOT!!! Google it!!!
Sheesh!!!
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.