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.
Related
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.
Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.
What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
I am super CID.
gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too
Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).
I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.
I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?
If you're on jb and hboot 2.00, that's normal... and written in the first post.
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Is there any chance to make this for the k2cl ( boost mobile ) version?
idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".
old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.
Oh, thank you for the info. Is there any link about this work in progress?
idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.
HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80
szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !
Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Edit 2013-07-10: I've solved my issues and am now on Hboot 2.15 with S-OFF (didn't lose it with the upgrade) and CM10.1! See the last post for details.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Since you are already S-OFF there is no need to upgrade your H-Boot. That does not effect the rom at all. With the Radio, when you flash the Rom it will automatically change the radio to the one preset by CM10.1 for the Rom. If you live in an area not covered by the radio, with S-OFF, you can flash any radio that you would like that is covered where you live and gives you the best service for your Provider.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Change your cid back to your og HTC one.
Supercid has lost most it value since your soff. You can change it whenever you want.
Ehh the low hboot you have has almost no added use since your s-off.
Forget about needing a new radio, who told you that? You can flash whatever radio you want.
You need a update hboot and firmware.
New kernels require that. Not radio.
Easiest way. Run latest ruu with your original unbranded HTC cid. No need to relock or s-on. Afterward custom recovery and start flashing.
Verstuurd van mijn One S met Tapatalk
Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?
m1schi said:
Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?
Click to expand...
Click to collapse
if flashing a ruu s-off will be preserved.
so
change to your original cid with fastboot command.
flash a ruu wich is/came originaly with your cid/device (lower version is no problem, if you cant find the jb one of your device),
then do otas till your on JB.
the flash stock recovery, then custom rom. finished.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22
vatsaman said:
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22
Click to expand...
Click to collapse
That's what I'm wondering about: Everyone seems to tell me some other way to upgrade my phone.
You tried to upgrade your phone via RUU?
There seems to be a method without the RUU, just fastboot: http://forum.xda-developers.com/showthread.php?p=42985992#post42985992
This should get me onto the newest HBOOT and let me use AOSP ROMS with 3.4 Kernel, without loosing S-OFF or bricking my device?
Edit 2013-07-10: I've used this method to go from my hboot 1.06 to hboot 2.15, while still having S-OFF.
http://forum.xda-developers.com/showthread.php?p=42985992#post42985992
Can I S-OFF the hboot 2.02 ??
I mean this guide: http://forum.xda-developers.com/showthread.php?t=1399331 will work for my HBOOT 2.02 ?
No, because zergRush won't work. You'll have to unlock your bootloader to gain any sort of root.
Edit: this guide would work
http://forum.xda-developers.com/showthread.php?t=1318919
To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.
paulie-uk said:
To S-OFF you first have to downgrade to an older HBOOT, which is done by gaining some form of root, running misc_version and then an older RUU. After you're S-OFF you can put on a newer (S-OFFed) HBOOT if you don't want Revolutionary's default one.
As long as you're running gingerbread (i.e. Android 2.3.x, and not ICS which is 4.0.4), you can get temproot. See my signature for more information.
Click to expand...
Click to collapse
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
I understand you have to downgrade first, and then S-OFF, but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Are you S-OFF paulie-uk?
readmanr said:
S-OFF is something I too want to do to my HTC Desire S, looking in your signature you are running 2.00.2002.
I am on a newer HBOOT the 2.02.0002.
[...]
Are you S-OFF paulie-uk?
Click to expand...
Click to collapse
I'm hboot S-OFF (what revolutionary can provide), not radio S-OFF (sadly the only way to do this on SAGA is with some extra equipment). I believe the 2.02.0002 hboot came in the ICS RUU, it's just got a bit tighter security, I don't think the partitions have changed since the last version (someone correct me if I'm wrong here).
readmanr said:
There seems to be a lot of people still on 2.00.X and not on the 2.02.X.
Click to expand...
Click to collapse
I'm using an S-OFFed ENGineering hboot, where you see people on the other version (2.00.0002) it is (usually) the stock SHIP hboot.
readmanr said:
I understand you have to downgrade first, and then S-OFF
Click to expand...
Click to collapse
You will have to downgrade. Sadly this will wipe your phone.
readmanr said:
but after S-OFF can I then flash the ICS RUU and get it back to 2.02.0002?
Will it still say Revolutionary? or go back to saying Unlocked (As I am HTC DEV Unlocked).
My main concern is that I don't like the idea of having 0.98, on there after, or having a fake number 6.98 or 7.00.2000 etc.
Click to expand...
Click to collapse
After you're S-OFF, I'd suggest you try a custom ROM and not flashing the 4.0.4 RUU (it's a buggy experimental version). Flashing an official RUU is pretty much how you return to stock, so it would most likely overwrite your S-OFFed hboot with a S-ON stock one. Remember, the S-OFF on our device is done in the hboot and not the radio.
When you're S-OFFed the first hboot you will have will be Revolutionary's 6.98 one. You can change this after.
I've found that 2.00.2002 works with all of the ROMs I've tried (which have been based on gingerbread, ICS and JellyBean). The "fake number" ones are there to make flashing a S-ON hboot more difficult, meaning that an OTA update wouldn't undo it. However, it is quite obvious if you were to send your phone in for repairs (still in warranty!?!?!) which is why a few of the tech-savvy who want S-OFF put on the ENG hboots instead.
If you want to overwrite Revolutionary's hboot with a different one with a lower version number, you will need to use dd and if it goes wrong it will brick your phone. You can find the ENG hboots on cyannogenmod's wiki if you don't trust the files I provide in other posts, but I strongly suggest you read about what you're going to do until you're comfortable with it before taking action.
Remember that after changing a hboot or radio, you should always re-wipe and re-flash your phone as partitions can move and always check the md5 first.
So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.
zain910128 said:
So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.
Click to expand...
Click to collapse
In response to your first question, SuperCID is a generic CID that unlocks your device from being identified and restricted to a certain carrier or region.
You don't need to worry about rooting methods for any specific version, you already have an unlocked bootloader and s-off, and your phone will stay like that unless you deliberately change it.
You don't want to update just the hboot. The ROMs look for a certain hboot version to be present during installation, but this is actually to verify that you have the right firmware installed, so you need to update your firmware, not just the hboot.
Luckily you don't need to mess around with any RUU at all. There's a much better and easier solution to your problem and that's simply to flash the 2.15 firmware package. There's a download and full instructions in my guide thread, you'll find the link in my signature.
Transmitted via Bacon
I have hboot 1.14 and built 2.20
You've mentioned installing firmware 2.15 package. Isnt that a downgrade ?
Also, can you explain the relation between hboot-firmware-built-RUU ?
timmaaa said:
In response to your first question, SuperCID is a generic CID that unlocks your device from being identified and restricted to a certain carrier or region.
You don't need to worry about rooting methods for any specific version, you already have an unlocked bootloader and s-off, and your phone will stay like that unless you deliberately change it.
You don't want to update just the hboot. The ROMs look for a certain hboot version to be present during installation, but this is actually to verify that you have the right firmware installed, so you need to update your firmware, not just the hboot.
Luckily you don't need to mess around with any RUU at all. There's a much better and easier solution to your problem and that's simply to flash the 2.15 firmware package. There's a download and full instructions in my guide thread, you'll find the link in my signature.
Transmitted via Bacon
Click to expand...
Click to collapse
zain910128 said:
I have hboot 1.14 and built 2.20
You've mentioned installing firmware 2.15 package. Isnt that a downgrade ?
Also, can you explain the relation between hboot-firmware-built-RUU ?
Click to expand...
Click to collapse
No it isn't a downgrade, the 2.15 refers to the hboot that's contained in the firmware package. Here's a brief explanation:
RUU: contains the ROM, recovery, firmware. An automated process which installs all of these items.
Firmware: contains the hboot, modules for Wi-Fi, media, etc.
ROM: the operating system (this is what is referred to by the build number).
Trust me, I'm very experienced with this device, all you need to do is what I outlined in my initial reply.
1095
timmaaa said:
No it isn't a downgrade, the 2.15 refers to the hboot that's contained in the firmware package. Here's a brief explanation:
RUU: contains the ROM, recovery, firmware. An automated process which installs all of these items.
Firmware: contains the hboot, modules for Wi-Fi, media, etc.
ROM: the operating system (this is what is referred to by the build number).
Trust me, I'm very experienced with this device, all you need to do is what I outlined in my initial reply.
Click to expand...
Click to collapse
Thanks a bunch !
Successfully running CM11.
A couple of more things id like your thoughts on:
1. Can you tell me how i can get rid of the splash screen message ?
Or is it possible to use my own splash screen ?
2. When i go to settings to customise slider lock shortcuts, it is pre set to unlock on right and various other shortcuts on the other 4 slots. I wanted to have unlock on top and the other shortcuts on either side. However, im unable to edit the right side shortcut.
zain910128 said:
Thanks a bunch !
Successfully running CM11.
A couple of more things id like your thoughts on:
1. Can you tell me how i can get rid of the splash screen message ?
Or is it possible to use my own splash screen ?
2. When i go to settings to customise slider lock shortcuts, it is pre set to unlock on right and various other shortcuts on the other 4 slots. I wanted to have unlock on top and the other shortcuts on either side. However, im unable to edit the right side shortcut.
Click to expand...
Click to collapse
Do you mean the red text? You can flash a modified hboot but they can cause problems, my advice is just deal with the text. You can only have the unlock target on the right, you can't modify that.
Transmitted via Bacon