Related
Very Big thanks to all people who made this possible (I can't mention names cuz they are too many )
The Easy Guide:
1- Check your Hboot version from the Bootloader (by switch on your device while holding volume-dwon button) , if it's 0.98.0000 then you are lucky and go to step #3 otherwise go to step #2.
2- Now you need to downgrade your Hboot, the safest way is by flashing old offical rom that has Hboot version 0.98.0000 (e.g. RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release). Fallow the steps in this thread How to DOWNGRADE Desire S with S-ON, keep in mind you will lose all data when downgrading your rom.
3- Use the AlphaRevX Public Beta 2 tool to S-OFF your device by fallowing the instructions in this guide [AlphaRevX] Public Beta 2 for Desire S.
4- (Optional) Flash recovery via Rom Manager, or use this 4EXTRecovery v2.1 (personally, I prefer the last one ).
If you want ENG HBOOT instead of AlphaRevX Hboot, check this [MISC] ENG HBOOT is here !
Important Note: when you have ENG HBOOT in your device, DO NOT flash any offical rom unless you know what you are doing, cuz your S-OFF Bootloader will be replaced with S-ON version that come with the offical rom..
Nice guide although I believe that the last step step 5 is unnecessary, as I believe that the alpharevx hboot is patched to contain the same functionality as the ENG hboot, at least that's what ieftm posted.
Sent from my HTC Desire S using XDA Premium App
ben_pyett said:
Nice guide although I believe that the last step step 5 is unnecessary, as I believe that the alpharevx hboot is patched to contain the same functionality as the ENG hboot, at least that's what ieftm posted.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
That's exactly what I thought too
ben_pyett said:
Nice guide although I believe that the last step step 5 is unnecessary, as I believe that the alpharevx hboot is patched to contain the same functionality as the ENG hboot, at least that's what ieftm posted.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
yeah that's right, moreover the alpharevx hboot will not flash bootloader from PG881IMG official rom file
I'll change it now
The eng hboot is NOT modifyed . The REAL deal. i belive alpharevxs is text edited ..no other reasons to change it, as it have the functions.
Thx
Marsdroid
Branded phone
I have a Dutch VodaFone Desire S with a upgraded HBOOT, is this a problem when downgrading the HBOOT ?
No not problem at all but you'll lose all data when downgrading
I've just got a new sensation with s-on and h-boot 1.27.000 and official vodafone ics firmware.
I wanted to frlash arhd 6.6.2, but as long as I got there I have to s.off the phone...
But I cannot s-off the phone if it's h-boot 1.27.0000, so what do I have to do?
Search...read...wait
Sent from my HTC Sensation 4G using xda premium
I've got this message from revolutionary tool:
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: HTC Sensation Z710e (pyramid-1.27.0000, Android: 4.0.3, ROM v
ersion: 3.32.162.11)
Your device: pyramid, with HBOOT 1.27.0000 is not supported at this time.
Press (almost) any key to exit.
Click to expand...
Click to collapse
In the faq I've read there is no mention about the unsupported hboot 1.27.0000...
Shall I downgrade the hboot? But how if it's not rooted nor SCID nor s-off..??
zooster said:
I've got this message from revolutionary tool:
In the faq I've read there is no mention about the unsupported hboot 1.27.0000...
Shall I downgrade the hboot? But how if it's not rooted nor SCID nor s-off..??
Click to expand...
Click to collapse
Hi,
You are right.
1.27.000 is not currently supported.
You have to wait until it is...
No,there is no eta.
So basically I'm stuck with original firmware?
What can I do then, root? scid..? cwm?
zooster said:
So basically I'm stuck with original firmware?
What can I do then, root? scid..? cwm?
Click to expand...
Click to collapse
Hi,
Yes,you can root and install CWM.
But you can only install ROMS with a 3.32 base(latest ICS)
So,6.6.2 is OK
Ok, thank you.
But I tried to flash the CWM taken from the guide thred putting the PG58IMG.zip in the root of the sd.
But when I start the bootloader it says wrong image...
zooster said:
Ok, thank you.
But I tried to flash the CWM taken from the guide thred putting the PG58IMG.zip in the root of the sd.
But when I start the bootloader it says wrong image...
Click to expand...
Click to collapse
Hi,
Try THIS ONE
Still says wrong image....
My cid num, got with adb, is: VODAP102.
Should I insert it in android-info?
Should I super cid the phone before cwm?
Youre gonna have to unlock your bootloader by using htc's official method (google it). Then youll be able to install CWM and whatever else. There are limitations, theres a good guide in the development section about htc official bootloader unlocker. Read that before attempting.
zooster said:
Still says wrong image....
My cid num, got with adb, is: VODAP102.
Should I insert it in android-info?
Should I super cid the phone before cwm?
Click to expand...
Click to collapse
Hi,
Yes,try it.
malybru said:
Hi,
Yes,try it.
Click to expand...
Click to collapse
Just tried and it does not install the CWM. So do I have to unlock the bootloader with the official method?
i have same problem, im new to all this but want to root my phone. I have updated to the new ice cream sandwich through the vodafone over air update. i have looked through step guides but i dont know where to start! i have s-on so how do i get this off or do i need to?
Thanks
zooster said:
Just tried and it does not install the CWM. So do I have to unlock the bootloader with the official method?
Click to expand...
Click to collapse
Yes you will have to use the HTC Dev method right now if you want to flash a custom ICS ROM being as those are the only ones you will be able to flash with the Hboot you have. But know this ahead of time the HYC De. Unlock is very different then the Revolutionary unlock. Click the link in my sig to learn mote about the HTc Dev unlock and what it allows you to do. But if I was you I would just wait until Revolutionary supports Hboot 1.27.0000, or someone comes up with a Hboot downgrade for the Sensation cause the HTC Dev method does not fully unlock all portitions except the radio portition like Revolutionary does. Plus it leaves evidence your bootloader has been unlocked so HTC can say your warranty is void. Check out this post to as it gives a little more insight on HTC Dev unlock.
So to root the device I have to CWM it, to CWM it I need to unlock the bootloader?
But, If not rooted, unlocked nor CWModded, can I just install ARHD?
Ok, let's take it the other way round:
My phone is locked, hboot 1.27.0000, S-on, cid VODAP102 and not rooted, but last official stock ics.
Now I want to install last ARHD, what should I do and how??
zooster said:
So to root the device I have to CWM it, to CWM it I need to unlock the bootloader?
But, If not rooted, unlocked nor CWModded, can I just install ARHD?
Ok, let's take it the other way round:
My phone is locked, hboot 1.27.0000, S-on, cid VODAP102 and not rooted, but last official stock ics.
Now I want to install last ARHD, what should I do and how??
Click to expand...
Click to collapse
To flash AHRD you will have to have a unlocked bootloader, either by HTC Dev method or by Revolutionary method. Now as stated by you, malybru, and myself we all know Revolutionary is not compatible with Hboot 1.27.0000 (as of right now), which your device currently has. So this leaves only the HTC Dev method. Now I personally agree with others here on XDA, I would normally stay far away from unlocking via HTC Dev. But seeing as you bought your Sensation new with Hboot 1.27.0000, you really have no other alternative but to wait for Revolutionary to update or for some other means of unlocking becomes available. Also if you do manage to downgrade your Hboot you will have to use HTC Dev to do it.
Now I am in no way saying you should use HTC Dev, nor am I advocating HTC Dev. I am just trying to inform you. What you do with your device is your choice and your choice only. But what ever you do, please post back here with your decision and if applicable any results.
Also if you was wondering why you have to use HT Dev to downgrade Hboot, read this post. Yeah I know it is for GB ROMs but I imagine the same probably holds true for ICS. I mean it is the HTC Dev unlock that allowsyou to downgrade in that senario. But what do I know.
T-Macgnolia said:
To flash AHRD you will have to have a unlocked bootloader, either by HTC Dev method or by Revolutionary method. Now as stated by you, malybru, and myself we all know Revolutionary is not compatible with Hboot 1.27.0000 (as of right now), which your device currently has. So this leaves only the HTC Dev method. Now I personally agree with others here on XDA, I would normally stay far away from unlocking via HTC Dev. But seeing as you bought your Sensation new with Hboot 1.27.0000, you really have no other alternative but to wait for Revolutionary to update or for some other means of unlocking becomes available. Also if you do manage to downgrade your Hboot you will have to use HTC Dev to do it.
Now I am in no way saying you should use HTC Dev, nor am I advocating HTC Dev. I am just trying to inform you. What you do with your device is your choice and your choice only. But what ever you do, please post back here with your decision and if applicable any results.
Also if you was wondering why you have to use HT Dev to downgrade Hboot, read this post. Yeah I know it is for GB ROMs but I imagine the same probably holds true for ICS. I mean it is the HTC Dev unlock that allowsyou to downgrade in that senario. But what do I know.
Click to expand...
Click to collapse
Do you mean by using Htc dev, i'll be able to downgrade my hboot?
My hboot is 1.27.0000 with S On.
Jalkren said:
Do you mean by using Htc dev, i'll be able to downgrade my hboot?
My hboot is 1.27.0000 with S On.
Click to expand...
Click to collapse
Hi,
There is currently no way to downgrade firmware with s-on and hboot 1.27.000
malybru said:
Hi,
There is currently no way to downgrade firmware with s-on and hboot 1.27.000
Click to expand...
Click to collapse
Sure, exploit H.Boot 1.27.0000 for S-Off is revolution, new model of HTC phone is same like HTC_One
****ing S-ON policy HTC because you total locked us
And that is why HTC always following behind Samsung nowadays
I'm waiting XDA revolution
Hi,
I'm new to this forum and new nothing about rooting until a few days ago...quickly discovered the fact that Revolution does not support 1.27.
I unlocked with HTC DEV, ran recovery-clockwork-touch-5.8.0.9-pyramid.img using Fastboot CLI.
After that I backed up my stock Vodafone ICS ROM using CWM then switched to the XDA guide for rooting with su-2.3.6.3 and followed rest of XDA guides for installing a ROM (really useful guides - Thanks!!)
Within an hour I had gone from stock Vodafone ICS to Virtuous Inquisition-v4.0.1
I'll admit I got hooked up on flashing recovery and was given some guidance by a friendly soul but figured the rest out from this forum..
I currently have a desires s (S-ON, not-rooted and bootloader unlocked), I am not sure if I should downgrade to hboot 0.98 as S-OFF for this is not available right now and as the title says I want you all to tell me what to do !
I could either keep this hboot and simply unlock the boot loader, root my phone and install a custom recovery to flash roms. But that way I won't be able to S-OFF my device and hence I wouldn't be able to install all custom roms such as virtuous saga which requires S-OFF .
And If I downgrade my device, I am not sure if the kernels,radio, and other things would be that efficient plus I doubt if I would be able to install all roms, like ICS Sense 4 roms
(kinda new to all this so I don't know if I am being a noob, but I seriously need your reply on this)
Sent from my HTC Desire S using xda premium
I can tell you what i did:
I unlocked my bootloader at htcdev right away when i got my desire s, then got superuser access to my phone. It was pretty fun, but I couldn't do EVERYTHING Plus, I lost parts of my warranty.
I really wanted s-off to be able to flash all roms available.
After a month or so, i did a downgrade of the hboot, with this instructions.
It worked flawlessly, although it's an hour of work or so if you're new to android. Terminal/ADB looks weird and complicating at first, but hey, you just need to copy the lines off the tutorial, it works perfect if you do as told
My advice: DON'T unlock at HTCdev (gives yo FULL warranty, even if you flash a custom rom), and just simply follow the downgrade instructions. Then you'll have full access, full warranty and no limitations at all, it's absolutely worth the downrade/s-off!
I'm running ICS now and couldn't be happier with my phone!
First of all thank you for your help on this, even I have had the same thought that its better to downgrade my phone and S-OFF it rather than keeping it S-ON.
Btw I came across anouther doubt which I guess its better to ask here instead of creating a new thread every time, : if I have to use an ruu to downgrade ny device, should my current radio (as seen in bootloader) match the ruu's radio ??
Sent from my HTC Desire S using xda premium
No
Have changed my Rom twice not touched the radio firmware at all.
If it ain't broke don't fix it, also read on xda somewhere radio firmware is a local thing it may work in your area but not mine
Sent from my HTC Desire S using Tapatalk
13th Dev said:
I could either keep this hboot and simply unlock the boot loader, root my phone and install a custom recovery to flash roms. But that way I won't be able to S-OFF my device and hence I wouldn't be able to install all custom roms such as virtuous saga which requires S-OFF .
And If I downgrade my device, I am not sure if the kernels,radio, and other things would be that efficient plus I doubt if I would be able to install all roms, like ICS Sense 4 roms
Click to expand...
Click to collapse
IMO, there is not much need for you to flash radio.. most of the time you won't need to do so..
and HBoot version can be changed if you are S-Off..
but i have to disagree with your statement that if you don't S-Off you are not able to flash all custom roms.. yes, some may fail to boot up, but mostly they will boot up without problem..
I am currently at the same Hboot as you, HTCDev unlocked and i have tried many roms without problem..
the only thing about having S-On for me is that i will always be dependant on my computer to flash ROM.. other than that, there's no problem generally.. Oh, maybe there is one thing, HTC may know that your phone has already been unlocked since you are using their unlocker.. but there are some ways to relock it and restore the "RELOCKED" in bootloader to "LOCKED"..
I am a newbie, and that's why i unlocked it with HTCDev, but if i were to do it all over again, i would have spend few more days to learn how to downgrade the Hboot and S-Off instead.. you can always flash newer Hboot later anyway..
So my advice, don't worry so much about the radio, or the Hboot version (you can tweak that later) at the moment, then downgrade the Hboot and S-Off it..
IMO it's much better than using HTC unlocker..
thank you guys for all your help and advice, finally after spending a couple of days,I successfully downgraded hboot 2.00.0002 to .98 one.
once again, thankyou all
Sent from my HTC Desire S using xda premium
I assume that you're revolutionary S-OFF by now, you can now easily upgrade on the latest re-engineered hboot
@doghous exactly !, I'm thinking of changing my hboot to the new re_engineered 2.00.0002 by vampire36, or if someone could suggest a better one.......
Sent from my HTC Desire S using xda premium
13th Dev said:
@doghous exactly !, I'm thinking of changing my hboot to the new re_engineered 2.00.0002 by vampire36, or if someone could suggest a better one.......
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I have successfully S-Off my DS from HTC Unlock using the method by Skanob, it's pretty straight forward and noob-proof.. (not that you need that now ) and can be used to revert back to stock, S-On, Locked (not Re-locked) if you ever need to repair..
As for Hboot, i have upgraded the Hboot to Eng Hboot 7.00.1002 (the one you mentioned above) so that would be my recommendation, too!
doghous said:
I assume that you're revolutionary S-OFF by now, you can now easily upgrade on the latest re-engineered hboot
Click to expand...
Click to collapse
Does anyone know what the differences between the different versions of ENG Hboot?
ENG v0.98.2000 vs. ENG v2.00.xxxx vs. ENG v7.xx.xxxx
Any benefits of using v2.00 or v7.xx over the v0.98?
Thx.
anchemis said:
ENG v7.xx.xxxx
Click to expand...
Click to collapse
This one isn't an eng hboot. Better use 2.00.2002
anchemis said:
Does anyone know what the differences between the different versions of ENG Hboot?
ENG v0.98.2000 vs. ENG v2.00.xxxx vs. ENG v7.xx.xxxx
Any benefits of using v2.00 or v7.xx over the v0.98?
Thx.
Click to expand...
Click to collapse
A good question actually, even I have the same doubt and would really appreciate if someone could post the answer !
Sent from my HTC Desire S using xda premium
This is what I've gathered from forum trawling...
v0.98.xxxx: the original hboot for 1.x roms
Has the partitions: /system, /cache, /data (all ext3 or ext4)
Fastboot support, supports Revolutionary S-OFF
ENG v0.98.xxxx: engineering version of above
v2.00.2002: the new hboot for 2.x roms (Sense 3.0 etc.)
Has the partitions: /system, /system/lib, /cache, /data (all ext4)
NOT supported by Revolutionary
-> apparently, some Sense 3.0+ roms need this new /system/lib partition to work (stability issues), but I'm not sure which ones though...
->Note Revolutionary is NOT supported, so to S-OFF you need to downgrade using TacoRoot, ZergRush/Misc_versions, XTC clip or some other method.
ENG v2.00.xxxx: engineering version of above
RVL v6.98.1000: hboot that comes after you S-OFF with revolutionary
It is of a higher version number so breaks overflashing functionality, so you CANNOT revert to RUU (for warranty returns etc.)
-> Note: This can be overflashed with v6.98.2000 (OverARX), which then allows you to overflash a stock or engineered hboot.
v7.00.1002[\B]: modified 2.00.2000
NOT ENG BOOTLOADER
But are there any real life benefits of one over the other?
for example I have the Rev v6.98.1000 hboot, so what you mean is that I could have problems while flashing roms (occasionally), and hence I should change my hboot to the engineered one ?
Sent from my HTC Desire S using xda premium
I got really frustrated with being S-ON and found the HBOOT downgrade instructions dubious so I found someone in my area with an XTC CLIP device and S-Offed the bastard , don't care much about warranty at this point however.
@ste_vald well done there !, having an s-offed device is surely much better
Sent from my HTC Desire S using xda premium
13th Dev said:
for example I have the Rev v6.98.1000 hboot, so what you mean is that I could have problems while flashing roms (occasionally), and hence I should change my hboot to the engineered one ?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
No, you should be fine installing most of the ROM's (unless specified otherwise in the OP of the ROM).
However, ENG Hboot is recommended so that if required later you can easily flash new radio's / Hboot.
Thank you, but can't I flash radios on this rev hboot
Sent from my HTC Desire S using xda premium
No, i believe you can't! You will require an ENG Hboot...
Hi guys
How can I Downgrade my hboot from 2.15 to 1.14
I've got ota jb.
now i'm using viper 1.2.1 custom rom
and have: unlocked,rooted,supercid,,cwm,
I want to install ruu but first i must s-0ff......i tried to s-off but due to my hboot version s-off method didnt work
by the way I tried facepalm s-off method
I'm not sure you can now. I've seen a few people mention in the forums that if you didn't S off before doing the OTA, you'll have to wait for a new method as the exploit was patched. I could be wrong, check the S off thread.
Sent from my HTC One S using the xda-developers app
Thank you npiper05
Sent from my HTC One S using xda app-developers app
You should be able to s off with 2.15 bootloader. I have done it no problems. Go through the s off process step by step, and for some reason it can matter what sort of ROM you have before going s off. So for example, try flashing the JB version of Viper, and then do S-Off (or one of the custom sense stock roms, ie latest t mobile, etc).
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.