Related
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 2.16
How can I install CM11 successfully ?
Thx :laugh:
Installing CM 11
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
Aquire S-Off and SuperCID . This makes things ten times more easier . There are recent thread posts in Android development that show you how .
You will have to actually update your hboot to 2.15 and implement a twrp that supports SElinux.
1 ) http://forum.xda-developers.com/showthread.php?t=2322755
Use that to upgrade your hboot.
2 ) http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
Download and flash this recovery.
3 ) http://download.cyanogenmod.org/?device=ville
Get the latest nightly from the get.cm
... and flash away
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
If you need specifics, Let me know.
I've been down your path and I hopefully can help you out on each step.
Happy flashing
S-Off
Thanks for the fast reply.
Is it better to do S Off before superCID ?
To make it s-off which méthode should i use? Facepalm or moonshine?
kc6992 said:
Thanks for the fast reply.
Is it better to do S Off before superCID ?
To make it s-off which méthode should i use? Facepalm or moonshine?
Click to expand...
Click to collapse
S-Off First, Cause that's what enables you to install different RUU's and update/downgrade firmware.
Try Facepalm
.. and for superCID, use one of the toolkit's. that one's a bit easier
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
You have hboot 2.16 not 1.16. What I suggest is before downgrading, try one of CM11 builds for 2.16. They're compiled by RockR172 for 2.16 and they're based on official builds. Latest available is the one from 20/12 and you'll find it in the second post from the CM11 thread. If you find then CM11 comfortable to use, you could downgrade your hboot to 2.15 and start using the official nightlies.
Sent from nowhere over the air...
Hboot
Rapier said:
You have hboot 2.16 not 1.16. What I suggest is before downgrading, try one of CM11 builds for 2.16. They're compiled by RockR172 for 2.16 and they're based on official builds. Latest available is the one from 20/12 and you'll find it in the second post from the CM11 thread. If you find then CM11 comfortable to use, you could downgrade your hboot to 2.15 and start using the official nightlies.
Sent from nowhere over the air...
Click to expand...
Click to collapse
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
kc6992 said:
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
Click to expand...
Click to collapse
Yes. That was the one I told you about. In the second post, you'll find links to the 2.16 builds. The latest one is THIS. That step for flashing kernel in fastboot is mandatory for anyone that's S-On, for any ROM and for any hboot higher than 1.09. So after you flash that ROM, reboot to fastboot and flash the boot.img (that you have previously extracted from the ROM zip) using that command.
For downgrade, there a couple of threads describing the procedure in the Dev section, there's no need to repeat all this at this point. Fist flash this CM and see if you are OK with it...not to find later that you've downgraded and now you want MaximusHd back. Going from sense based ROMs to non-sense based ROMs was a challenge for many and there are alot of things that differs. That's why I said you might want to check first and only after take such decision
I just compiled a recent CM11 version (0109-nightly) for hboot 2.16. You can download it from
https://drive.google.com/file/d/0B0ajti88ZAFzYkZqNEVydkZwSzg/edit?usp=sharing
if you want. Its compiled from the official CM11 sources where additionally two cherry picks
are necessary to support the new hboot and TWRP recovery
http://review.cyanogenmod.org/#/c/53647/
http://review.cyanogenmod.org/#/c/53559/
Edit: Note that this build is ONLY for HBOOT 2.16 !!!
If you are s-on you still have to extract the kernel (boot.img) from the archive and flash it via fastboot after
flashing the zip. Alternatively you can use the FlashImageGUI app (from play store). In this case flash the boot.img BEFORE
you flash the rom zip. Worked great for me when I was still s-on and you don't need a computer to flash a
new rom.
kc6992 said:
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
Click to expand...
Click to collapse
Hey Bro How Did U managed to install Maximus Hd on S on and without supercid...plzz tell me m tired of this Tmobile Rom.....thankx.
I believe Twistedkat ROM works on hboot 2.16. Check it out in dev forum
http://forum.xda-developers.com/showthread.php?t=2584591&page=37
Nobody?????
Hemantgits said:
Nobody?????
Click to expand...
Click to collapse
What Hboot are you on ?
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
drkxyz said:
I just compiled a recent CM11 version (0109-nightly) for hboot 2.16. You can download it from
https://drive.google.com/file/d/0B0ajti88ZAFzYkZqNEVydkZwSzg/edit?usp=sharing
if you want. Its compiled from the official CM11 sources where additionally two cherry picks
are necessary to support the new hboot and TWRP recovery
http://review.cyanogenmod.org/#/c/53647/
http://review.cyanogenmod.org/#/c/53559/
Edit: Note that this build is ONLY for HBOOT 2.16 !!!
If you are s-on you still have to extract the kernel (boot.img) from the archive and flash it via fastboot after
flashing the zip. Alternatively you can use the FlashImageGUI app (from play store). In this case flash the boot.img BEFORE
you flash the rom zip. Worked great for me when I was still s-on and you don't need a computer to flash a
new rom.
Click to expand...
Click to collapse
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
fatboyslimerr said:
I believe Twistedkat ROM works on hboot 2.16. Check it out in dev forum
http://forum.xda-developers.com/showthread.php?t=2584591&page=37
Click to expand...
Click to collapse
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
rom
rosswhite said:
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
Click to expand...
Click to collapse
I wasn't confused. I really was S-On with twrp 2.4.1 and it worked well
Now i'am back on hboot 2.15 and i flashed CWM in order to flash CM11.
For maximusHD on hboot 2.16 and S-ON I just followed the tutorial : http://forum.xda-developers.com/showthread.php?t=2445392
I know it may sound confusing, but maximusHD worked for me on S-ON, and it has been my daily Rom for over 3 months.
When i installed it, I just couldnt run the firmware.zip (i had a fail) but it worked correctly without.
kc6992 said:
I wasn't confused. I really was S-On with twrp 2.4.1 and it worked well
Now i'am back on hboot 2.15 and i flashed CWM in order to flash CM11.
For maximusHD on hboot 2.16 and S-ON I just followed the tutorial : http://forum.xda-developers.com/showthread.php?t=2445392
I know it may sound confusing, but maximusHD worked for me on S-ON, and it has been my daily Rom for over 3 months.
When i installed it, I just couldnt run the firmware.zip (i had a fail) but it worked correctly without.
Click to expand...
Click to collapse
Ok, the thing is it's the firmware.zip that gives you a hboot version of 2.16. So if you didn't flash that, you were on a lower hboot, you can still flash the ROM I believe but you only have 2gb of storage available. Anyway, It doesn't matter now. Enjoy CM11.
CM nightly on 2.16 firmware works great for me. Updated to 0110 in the meanwhile and I only have the known bugs like backlight not coming
up after a phone call and very rare reboots (indeed no reboot on 0110 since now :fingers-crossed: )
There are indeed lots of people who installed MaximusHD on hboot 2.16 with s-on over in the MaximusHD thread. It's very dangerous though
and may lead to bricked devices ...
rosswhite said:
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
Click to expand...
Click to collapse
Here is an updated CM11 build for hboot 2.16, containing the latest patch for the backlight bug. Its been built from the
original CM11 sources.
https://drive.google.com/file/d/0B0ajti88ZAFzRmV3Mi1aM2lxY0E/edit?usp=sharing
Works great and I haven't had any backlight problems or reboots yet !!!
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
Mozziliac said:
What Hboot are you on ?
Click to expand...
Click to collapse
Hboot 2.15
New CM11 built 140115 for hboot 2.16 for anyone who is interested
https://drive.google.com/file/d/0B0ajti88ZAFzMDl4TW1Oc2tVQVE/edit?usp=sharing
Can anyone post/link this into the CM11 development section?
Have fun ...
drkxyz said:
New CM11 built 140115 for hboot 2.16 for anyone who is interested
https://drive.google.com/file/d/0B0ajti88ZAFzMDl4TW1Oc2tVQVE/edit?usp=sharing
Can anyone post/link this into the CM11 development section?
Have fun ...
Click to expand...
Click to collapse
Now you can post it yourself.
i just recently S-OFF through Rumrunner and i was wondering if im able to install maximusHD 10 (sense 5 + android 4.2). I'm not sure if hboot 2.16 is required, since im S-OFF with hboot 2.15. thanks.
xPhrosty said:
i just recently S-OFF through Rumrunner and i was wondering if im able to install maximusHD 10 (sense 5 + android 4.2). I'm not sure if hboot 2.16 is required, since im S-OFF with hboot 2.15. thanks.
Click to expand...
Click to collapse
Part of the install instructions for MaximusHD is updating your hboot version from 2.15 to 2.16. So yes, 2.15 is correct for now. When you go to download the ROM there are 2 files, the ROM and the installer package. The installer package contains the firmware (this is what updates the hboot to 2.16) and the recovery. This is why the instructions are a little complicated. Basically you have to flash the rom first, then flash the firmware, then flash the recovery, then flash the ROM again. Just note, you can not mount storage in TWRP recovery for 2.16. Also, if you are a stock android fan then stay on 2.15 if you want to have a greater choice of ROM's. Currently I think the only AOSP based ROM that supports the 2.16 hboot is CM11.
Sent from my Nexus 7 using XDA Premium 4 mobile app
rosswhite said:
Part of the install instructions for MaximusHD is updating your hboot version from 2.15 to 2.16. So yes, 2.15 is correct for now. When you go to download the ROM there are 2 files, the ROM and the installer package. The installer package contains the firmware (this is what updates the hboot to 2.16) and the recovery. This is why the instructions are a little complicated. Basically you have to flash the rom first, then flash the firmware, then flash the recovery, then flash the ROM again. Just note, you can not mount storage in TWRP recovery for 2.16. Also, if you are a stock android fan then stay on 2.15 if you want to have a greater choice of ROM's. Currently I think the only AOSP based ROM that supports the 2.16 hboot is CM11.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
okay, that makes much more sense now. thanks a lot!
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery
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.
Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app
Silentwidow said:
Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.
benJX said:
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.
Click to expand...
Click to collapse
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000
Rapier said:
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000
Click to expand...
Click to collapse
Yes on Vanir AOSP I had to do this to make it flashable on 2.16 (btw thx for your guide )
Sent from my ElementalXed One S