HBOOT - 2.15.0000
Radio - 1.13.50.05.31
S-ON
JB 4.1.1
Unlocked and rooted with TWRP 2.5 recovery.
TMO
Tried this method for Super CID - http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
When I try to dump the partition onto the SDcard, I get "Permission Denied"
I can't wipe the stock rom with TWRP or with Superwipe.
I just got a new phone under warranty exchange and realized that it is running 4.1.1. I'm not a noob but definitely feel like one. I tried searching the boards and all I can come up with is that maybe this can't Super CID yet. Is that true or am I missing a step for this newer build? Is there some other way to flash a ROM with S-ON and no Super CID? Any assistance would be appreciated.
You can flash whatever ROM you want without soff...just need to fastboot the boot.img.
For super cid, start on step 2 of that link using terminal emulator right on your phone.
Also, use twrp 2.3.3 or 2.2.2, people have been having issues with higher versions Or you can use cwm.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Thanks!
ryanshew said:
You can flash whatever ROM you want without soff...just need to fastboot the boot.img.
For super cid, start on step 2 of that link using terminal emulator right on your phone.
Also, use twrp 2.3.3 or 2.2.2, people have been having issues with higher versions Or you can use cwm.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Click to expand...
Click to collapse
Attempted, was able to pull the mmcblk0p4 file, changed in HEX editor...instead of appearing as CWS__001 as the line to change, mine says T-MOB010 before my IMEI number. I changed it to 11111111, pushed the file and when I "fastboot oem readcid" it still reads T-MOB010. Tried in on the desktop and terminal emulator a couple of times. I just can't get the CID to stick!!!
Any other recommendations? I changed from TWRP to CWM 6.0.3.1 touch. I doubt the recovery has anything to do with it. Fully rooted...stuck on S-ON until I can figure out why I can't Super CID. MUST FLASH CUSTOM ROM!
i have this same problem. did you ever get it fixed? my Super CID wont stick
mantiis said:
i have this same problem. did you ever get it fixed? my Super CID wont stick
Click to expand...
Click to collapse
I gave up for a little bit. I achieved s-off with moonshine but have yet to attempt again. I'm on vacation in two weeks and will devote a full day to it then.
darius359 said:
I gave up for a little bit. I achieved s-off with moonshine but have yet to attempt again. I'm on vacation in two weeks and will devote a full day to it then.
Click to expand...
Click to collapse
If you have s-off, you don't need this. All you need to do is fastboot oem write cid 11111111
hTConeS | SoFF | CharmAnDroiD | eleMeNtal
*INveRTeD sENsE 5 ROM+ThEmE+TwEAkS*
*CharmAnDroiD 3.0 FULL ROM UPDATE*
ryanshew said:
If you have s-off, you don't need this. All you need to do is fastboot oem write cid 11111111
Click to expand...
Click to collapse
And what if we have S-On? I have S-On and can't get s-off because (I think) my hboot is causing USB connectivity problems when booted into the OS. I cannot get SuperCID to stick.
ryanshew said:
If you have s-off, you don't need this. All you need to do is fastboot oem write cid 11111111
Click to expand...
Click to collapse
Can't Supercid with HBOOT 2.15.
It's vacation time, so I'm trying again. About to switch to an older recovery and just start messing around and seeing what kind of damage I can do...
FIXED
I wasn't able to flash TWRP to 2.3.3.0 so I just updated to the newest version 2.6.0.0.
I was finally able to wipe the system and data and everything and flash a fresh new rom.
TOOK LONG ENOUGH!!
Thanks to this forum!!!
If you are S=ON then you can not get scid with 2.15. The only (known to this time) way to get the s=off is moonshine script and then you can write the scid.
Yes you can. At least some of us. I am on 2.15 and used facepalm to get s-off, and that requires scid first.
Sent from my One S using Tapatalk 4
El_Svanto said:
Yes you can. At least some of us. I am on 2.15 and used facepalm to get s-off, and that requires scid first.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
I have 2.15 rooted and bootloader unlocked, unable to get scid or s-off, any suggestions?
darius359 said:
I gave up for a little bit. I achieved s-off with moonshine but have yet to attempt again. I'm on vacation in two weeks and will devote a full day to it then.
Click to expand...
Click to collapse
I have the same problem as everyone I can't do SuperCID and S-Off.
I am HTC One S T-mobo10 HBOOT - 2.15.0000 Radio - 1.13.50.05.31 S-ON TWRP 2.6.3.0 recovery I've used every means possible I'm tired of reading all the forums, if you have a video how to make s-oFF moonshine upload or explains the community will thank:
darius359 said:
I gave up for a little bit. I achieved s-off with moonshine but have yet to attempt again. I'm on vacation in two weeks and will devote a full day to it then.
Click to expand...
Click to collapse
Did you have any issues with moonshine? Tried doing this last night and it hangs on "Test 3" forever. I know it says not to touch your phone but after watching 2 shows on TV had to stop. Thoughts or suggestions?
Thanks!
Solved
So I followed someone else's directions and installed LinuxMint on a USB and was able to successfully run moonshine. I'm not S-OFF!
st3wy said:
I have 2.15 rooted and bootloader unlocked, unable to get scid or s-off, any suggestions?
Click to expand...
Click to collapse
If it works in windows moonshine I did this tutorial but in spanish to help all who have problems to make the soff
http://www.taringa.net/posts/celulares/17401702/Como-hacer-soff-en-HTC-one-s-3-14-531-17RD.html
I have an HTC One S (duh) with CM10, hboot 1.14, S-ON, no superCID at the moment.
I want to flash a new ROM, but everything either needs me to have S-OFF (superCID) at the least, or a newer hboot.
So in order to update my hboot, I was under the impression that I needed to get back on stock ROM. I tried that - got some error while running the RUU. I also don't remember why I got that impression.
I can't do superCID because my phone, while showing up under fastboot devices, says device not connected with ADB shell. I already tried reinstalling the adb drivers, no luck.
I can't do either S-OFF (facepalm or moonshine).
So, should I just give up at this point?
Mythic~ said:
I have an HTC One S (duh) with CM10, hboot 1.14, S-ON, no superCID at the moment.
I want to flash a new ROM, but everything either needs me to have S-OFF (superCID) at the least, or a newer hboot.
So in order to update my hboot, I was under the impression that I needed to get back on stock ROM. I tried that - got some error while running the RUU. I also don't remember why I got that impression.
I can't do superCID because my phone, while showing up under fastboot devices, says device not connected with ADB shell. I already tried reinstalling the adb drivers, no luck.
I can't do either S-OFF (facepalm or moonshine).
So, should I just give up at this point?
Click to expand...
Click to collapse
You will need to be S-off for the ROMs that require 2.16 HBoot.
The other ROMs (require 2.15 HBoot) You will be ok with S-on. Just have to remember to fastboot flash the boot.img before installing the ROM.
But first you need to update your firmware to 2.15.
So keep trying RUU.exe trying one that will work with your CID. Look for RUU that have JB that will bring you the 2.15 Hboot and Jelly Bean update.
Remember to lock your bootloader before running the RUU (since you are S-on)
tivofool said:
You will need to be S-off for the ROMs that require 2.16 HBoot.
The other ROMs (require 2.15 HBoot) You will be ok with S-on. Just have to remember to fastboot flash the boot.img before installing the ROM.
But first you need to update your firmware to 2.15.
So keep trying RUU.exe trying one that will work with your CID. Look for RUU that have JB that will bring you the 2.15 Hboot and Jelly Bean update.
Remember to lock your bootloader before running the RUU (since you are S-on)
Click to expand...
Click to collapse
Yeah, I've done all that for the RUU. I'm 100% sure I have the right one, but when I run it it gives me an error. When I get home I'll try again.
Mythic~ said:
I have an HTC One S (duh) with CM10, hboot 1.14, S-ON, no superCID at the moment.
I want to flash a new ROM, but everything either needs me to have S-OFF (superCID) at the least, or a newer hboot.
So in order to update my hboot, I was under the impression that I needed to get back on stock ROM. I tried that - got some error while running the RUU. I also don't remember why I got that impression.
I can't do superCID because my phone, while showing up under fastboot devices, says device not connected with ADB shell. I already tried reinstalling the adb drivers, no luck.
I can't do either S-OFF (facepalm or moonshine).
So, should I just give up at this point?
Click to expand...
Click to collapse
In terms of Supercid and s-off. You can get supercid on roms that aren't stock, but you need supercid for s-off. So my phone was stock, then i flashed cm10, then i gained supercid, then s-off, then i could put whatever rom i fancied on (in that order). I had HBOOT 2.15.
Dunno if it helps because it sounds like you are using windows and i use linux but i had problems with adb too. Which I fixed by using the equivalent to "run as administrator".
I found the root of my problems - apparently my HTC drivers installation was corrupted, so most processes would get to a point but be unable to continue because of some error having to do with the drivers.
I reinstalled them, so hopefully I'll have some success with rumrunner.
Just kidding. Rumrunner says I'm "not rooted" even though I am running a custom ROM with unlocked bootloader.
So I'm S-OFF, but the RUU refuses to work. (I'm trying to get a kitkat-based ROM and i need hboot 2.15 for that)
I always get the error:
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 1 (7601)
IE Version: 9.11.9600.16476
Any help?
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.