Related
Now we have S-Off for HBOOT 1.06 (CDMA)
This will allow you to use UNREVOKED 3.0 to root your phone. Enjoy!!!!
http://alpharev.nl/x/beta/
Do I miss something, but what new in it for Desire?
We already have S-OFF with Alpharev 1.80.
Why do we need AlpharevX?
dmatik said:
Do I miss something, but what new in it for Desire?
We already have S-OFF with Alpharev 1.80.
Why do we need AlpharevX?
Click to expand...
Click to collapse
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
kev94 said:
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
Click to expand...
Click to collapse
not true. I have been able to s-off with 0.93.0001. Thats not the point of it.
I also checked my Desire and I got S-Off with Alpharev 1.80 and HBOOT 0.093.0001.
So, whats the difference?
Should this NOT be in the dev-forum?
Sent from my bicycle with no wheels
i only updated with new HBOOT and never used alpharev beta tool (only the old one). Check my sign...
This is specifically for CDMA users and newer HTC devices. It also means you don't have to root as you're already S-OFF - you can just flash a new ROM after flashing a custom recovery
kev94 said:
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
Click to expand...
Click to collapse
> = higher then hboot 0.93.0001.
So if your hboot is higher then 0.93.0001. You cant get s-off so his info is correct.
Scotsman828 said:
Now we have S-Off for HBOOT 1.06
This will allow you to use UNREVOKED 3.0 to root your phone. Enjoy!!!!
http://alpharev.nl/x/beta/
Click to expand...
Click to collapse
You don't even have to run unrevoked. Once they have S-Off some people have rooted by fastboot flashing a custom recovery, then flashing superuser as a zip. There's a tutorial thread over in AndroidForums (Desire All Things Root forum).
Presumably a pre-rooted ROM would also work at this point, but I guess this allows you to run Ti backup etc before doing that (or keep the current ROM).
Edit: Of course anyone doing it this way must make sure they flash the correct recovery for their device (GSM or CDMA). I believe that it's only (some) CDMA devices which have HBOOT 1.06, so most can just use unrevoked without this. And remember it's still in beta at the moment.
But it means that previously unrootable Desires can now be rooted
Yes this is for CDMA version of Desire. I tried Unrevoked before this came out and could not get root. After I ran the Alpharev to get S-Off, I got root with Unrevoked. Had to run Unrevoked so I could get ClockworksMod recovery. It was a really simple process, no need to create a special CD. I quickly canned the HTC ROM for CM7. Data worked without APN restore. Life is good
once you're s-off, you should to flash recovery through fastboot. Now you're able to flash any rom
Indeed ive just used revolutionary and it worked flawlessly on desire hboot 1.06
Hi,
I'm very familiar with flashing ROMs on phones and have flashed a fair few in my time. I flashed my sisters Desire S a while ago but recently the phone has stopped detecting the SIM card and subsequently has to go back for warranty.
I've flashed a Stock rom over it - trouble is, I now have the locked HBOOT v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade HBOOT to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
I cannot for the life of me downgrade the HBOOT version - I've tried every method out there!
I am very familiar with working in command line on Windows and Linux so don't be afraid to get technical!
Any help is very much appreciated!
Daft question, but have you tried a different Sim?
Does she still have the box?
Swyped from my Desire S using XDA Premium
Haha I spent hours debugging the sim card issue and finally came to the conclusion it's a hardware fault!
Yes - tried several different sim cards from two different carriers (this household only uses 2 carriers!)
Also tried several different ROMs/Radios - she was happily using MIUI for months then she just told me it stopped detecting her SIM card - she certainly hasn't been playing with ROMs so I know it's nothing she has done.
Update: Box is long gone
I've flashed a Stock rom over it - trouble is, I now have the locked bootloader v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade bootloader to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
Can I skip the first step? I guess not.
What has me confused is that you flashed the 0.98 hboot and you said it was s on, now you ran the RUU, and its s off....
Did you use revolutionary to get s off or was it s off to start with?
The correct steps would be.. (if you use revolutionary)
1. Use fastboot to flash 0.98.2000 over the revolutionary one.
2. Run correct RUU.
Problem you could run into are cid's of the RUU (make a goldcard to avoid error) and two misc version being higher than RUU.
Thanks for the reply. I never said it was S-on, the phone was running a custom MIUI ROM with S-Off, I flashed a stock rom straight over the top of it by running the RUU (pretty sure I shouldn't have done!) now I have stock ROM with S-Off and locked HBOOT v2.00.0002
I cannot remember if I used revolutionary to get s off originally - it was many months ago, more than likely though. I remember the phone came with S-On and I had to make it S-Off.
I just want to get S-On again with stock rom but it's proving impossible!
So just to clarify, it is currently running stock rom with LOCKED HBOOT v2.00.0002 and S-Off.
I've tried manually overwriting the version with miscinfo, I've also tried the zerg method - all to no avail.
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
foX2delta said:
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
Click to expand...
Click to collapse
Haha want screenshots? I assure you that's what I've got.
Ran an older RUU which has downgraded my HBOOT to 0.98 or 0.68 (can't remember off top of my head) and am running stock rom, HBOOT says ***locked*** at top and also says S-OFF.
I think I'm getting there now.
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Hydromea said:
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Click to expand...
Click to collapse
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROMs using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
exad said:
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROM using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
Click to expand...
Click to collapse
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Hydromea said:
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Click to expand...
Click to collapse
Yes, I did find Viper and clean rom both ran much better than they did previously.
I'm sorry, I don't know about the 3.18 OTA... Hopefully someone else here can shed more light?
Theoretically, Since you're S-OFF, you should be able to update just fine. I haven't seen anyone actually do it yet though. I would test if I could.
I didn't relock I just ruu'd and after the process was done I just pushed twrp to my phone in fastboot and flashed viper. Only took a few mins top
Sent from my Elemental Venomized S-off HTC One XL
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Hydromea said:
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Click to expand...
Click to collapse
I used the ruu for 3.18 and haven't regretted it yet. My battery life has gotten much better.
Sent from my Elemental Venomized S-off HTC One XL
OTA just downloads through the phone. IE: Go to settings about phone, check for updates and it updates. You don't have to do anything else, it prompts you and updates for you.
If there was already a 3.18 RUU that would be the fastest way. Telus is slow with releasing RUU's so I had to use ICS myself. Neither way should give you trouble.
Here's to hoping my phone doesn't brick. Running the RUU as we speak (bootloader unlocked, s-off, super-cid)...
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
Did you use the 3.18 RUU?
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
If you're hellbent on TWRP 2.2.2.0, downgrade the touchscreen firmware.
Hydromea said:
Did you use the 3.18 RUU?
Click to expand...
Click to collapse
Yeah I did. Maybe I'll look into downgrading the touchscreen firmware.
Sent from my HTC One X
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Hydromea said:
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Click to expand...
Click to collapse
yes you will here is how
http://forum.xda-developers.com/showthread.php?t=2159863
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Hydromea said:
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Click to expand...
Click to collapse
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
jerrycoffman45 said:
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
Click to expand...
Click to collapse
What he said lol
Sent from my Elemental Venomized S-off HTC One XL
this is all great info i would like to thank all of you
does this go for the rogers model as well?
babarnard said:
this is all great info i would like to thank all of you
does this go for the rogers model as well?
Click to expand...
Click to collapse
Yes.
Just an update. I successfully ruu'd to 3.18, downgraded hboot to 1.09, downgraded the touchscreen firmware, installed twrp 2.2.2.0 and all is well.
I'm sort of back where I started but maybe something good has come of it.
Sent from my HTC One X
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.
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.