Hi,
I saw a couple hboot updates, but when or why should I update them? I'm now on 6.xxxxxx revolutionary using Virtuous Quattro
Sent from my HTC Desire S
The hboot is your bootloader. Just Google "what is hboot" and read a few minutes.There is no need to update for you. Everything is good.
Sent by my fingers to your head
@robba16296
If anything, flash ENG HBOOT 0.98.2000 over the revolutionary one.
Okay thanks for the replies
Sent from my HTC Desire S
foX2delta said:
@robba16296
If anything, flash ENG HBOOT 0.98.2000 over the revolutionary one.
Click to expand...
Click to collapse
Just flashing doesn't work most of the time (that's why it should be replaced), you need to replace it with dd.
Use this guide with the hboot from my signature.
@Tectas
I would first suggest fastboot, then PG88IMG and only then a dd command.
That's my preference at least.
I have used Android Flasher with the file in attachment.
First flash hboot 6.98.2000 (engHBOOToverARX.img), then original 0.98.2000. It worked fine for me. PG88IMG.zip are includes in zipfile too.
why not stay on 6.xxxxxx??
Having that too and everything is fine
Sent by my fingers to your head
An eng h-boot would come in handy if anything were to go wrong because it is can be written over. Good safety precaution
Sent from my HTC Desire Saga using xda premium
foX2delta said:
@Tectas
I would first suggest fastboot, then PG88IMG and only then a dd command.
That's my preference at least.
Click to expand...
Click to collapse
He can try, I prefer to recommend this procedure, because it's the only that accomplishes in most cases, the others can work too and do no harm if not, but it saves some time to go straight to that one ^^
Swifted from my Desire S far away from my PC
dan-fish said:
An eng h-boot would come in handy if anything were to go wrong because it is can be written over. Good safety precaution
Sent from my HTC Desire Saga using xda premium
Click to expand...
Click to collapse
Actually I see it the other way around. Keeping the revolutionary hboot with its "overwite protection" kept a lot of people flashing RUUs (which they shouldn't if they don't know what they're doing, agreed) from a lot of hurt...
Cheers
lowveld said:
Actually I see it the other way around. Keeping the revolutionary hboot with its "overwite protection" kept a lot of people flashing RUUs (which they shouldn't if they don't know what they're doing, agreed) from a lot of hurt...
Cheers
Click to expand...
Click to collapse
Obviously shows that it does work both ways. I feel better having an ENG H-BOOT just in case something were to happen.
Related
hi everyone..
currently my desire s is s-off using revolutionary and rooted aswell... it is running a custom rom
now my question is that how can i make it S-ON again. like completely out of the box state?
it is europeon unbranded htc desire s ..
i have looked around but some people say use the adb method? some say just place the eng-hboot in sd and flash it? too confusing lol
any one with a noob guide? please
thanks
oh and I already have the RUU for my desire s...
tele27 said:
hi everyone..
currently my desire s is s-off using revolutionary and rooted aswell... it is running a custom rom
now my question is that how can i make it S-ON again. like completely out of the box state?
it is europeon unbranded htc desire s ..
i have looked around but some people say use the adb method? some say just place the eng-hboot in sd and flash it? too confusing lol
any one with a noob guide? please
thanks
oh and I already have the RUU for my desire s...
Click to expand...
Click to collapse
The problem with the revolutionary hboot is that it's a little bit tricky to overwrite it, cause of this only the adb method with dd command works, take a look at this http://forum.xda-developers.com/showthread.php?t=1285312
there is this solution described and also other possibilities of this fails, after you got that just run a ruu and your device should be stock within s-on.
Sent from my HTC Desire S using XDA App
Tectas said:
The problem with the revolutionary hboot is that it's a little bit tricky to overwrite it, cause of this only the adb method with dd command works, take a look at this http://forum.xda-developers.com/showthread.php?t=1285312
there is this solution described and also other possibilities of this fails, after you got that just run a ruu and your device should be stock within s-on.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
is it not possible to use this method? haha sounds so much easier...
1.Take the ENG HBOOT found here and put the PG88IMG.zip in the root of your SD card
2.Boot into the bootloader (Volume Down + POWER)
3.Go into FASTBOOT mode
4.The bootloader will automagically detect your new HBOOT and install it
5.After rebooting your phone you can install any RUU you want. That will bring HBOOT back to the installed original
Unfortunatly with revolutionary bootloader not.
oh damn lool..
time to take the risky path
thanks anyway will let you know how it goes...
thanks once again mate
Hello, I'm on hboot 1.23 but s-on, I just want to know because somebody mentioned it before, an I actually stuck here? Literally forever? Because hboot 1.23 cannot flash other firmware files or any advanced fastboot commands.
sensation lover said:
Hello, I'm on hboot 1.23 but s-on, I just want to know because somebody mentioned it before, an I actually stuck here? Literally forever? Because hboot 1.23 cannot flash other firmware files or any advanced fastboot commands.
Click to expand...
Click to collapse
I wrote a load of stuff then re-read the OP.
Ahh S-ON, eek.
As Revolutionary won't work, can you use the HTC method to get S-OFF ?
If you can then do the PG58IMG.zip files work from: http://forum.xda-developers.com/showthread.php?t=1459767
I flashed 1.27.1100 over 1.23.0000, then again I was S-OFF.
HTC method to s-off? Never heard of it.
sensation lover said:
HTC method to s-off? Never heard of it.
Click to expand...
Click to collapse
Because it doesn't exist.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
But unlocking the bootloader via HTC might help
Rhiannon224 said:
Because it doesn't exist.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
OK Sorry wrong terminology, I was referring to: http://htcdev.com/bootloader
I know many folks have used the HTC unlock method, I don't know what the limitations with it are as I used Revolutionary. My thoughts were can you use the HTC Unlock process then flash the F/W using PB58IMG.zip back to 1.17 the use revolutionary to get full S-OFF. I don't know if that's possible but ......
I know they keep a record that you've used it on your phone.
no, that doesn't give you s-off, it just unlocks your bootloader, but thanks for trying!
EddyOS said:
But unlocking the bootloader via HTC might help
Click to expand...
Click to collapse
It will not, it still leaves you s off, meaning you can't flash radios, firmwares, etc.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
It will not, it still leaves you s off, meaning you can't flash radios, firmwares, etc.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
Ahh, it was just a thought. I guess 1.23 S-ON is on his phone for a while then :-(
I'm guessing its on till revolutionary updates.....if it ever does.
sensation lover said:
I'm guessing its on till revolutionary updates.....if it ever does.
Click to expand...
Click to collapse
Either that or a new release RUU with hboot higher than 1.23, such as an official ICS RUU that will hopefully be released in March. The test RUUs that are currently available don't work - see here:
http://forum.xda-developers.com/showpost.php?p=22500215&postcount=24
gol_n_dal said:
I wrote a load of stuff then re-read the OP.
Ahh S-ON, eek.
As Revolutionary won't work, can you use the HTC method to get S-OFF ?
If you can then do the PG58IMG.zip files work from: http://forum.xda-developers.com/showthread.php?t=1459767
I flashed 1.27.1100 over 1.23.0000, then again I was S-OFF.
Click to expand...
Click to collapse
*Edit* Never mind... I guess after getting SuperCid it worked.
How did you flash to 1.27.1100? I have been trying to get my firmware updated so I can get ICS on my Sensation but it keeps giving me the "remote: not allowed" error. I have S-Off.
redblade said:
*Edit* Never mind... I guess after getting SuperCid it worked.
How did you flash to 1.27.1100? I have been trying to get my firmware updated so I can get ICS on my Sensation but it keeps giving me the "remote: not allowed" error. I have S-Off.
Click to expand...
Click to collapse
Flash the firmware from Mike's sticky. 3.24/3.25 gives hboot 1.27.1100, but I think this version is included with later fw releases too.
Does the remote: not allowed error appear in bootloader, relating to a particular part of the fw update - e.g. radio?
Sent from my Pyramid-T
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...
Ok here it goes I will try to explain my situation. Sorry for my lack of information, and other nonsense.
I have unlocked bootloaded using HTC dev my bootloader shows a pink ***UNLOCKED*** at the top. I have loaded cwm recovery using aahk. All my attempts at trying to gain s-off have failed. I dont care about setting CID to 111111 (however many 1's it is) Is there a way to gain S-OFF with out using the aahk. I can't seem to flash any ROMS using cwm because of s-on?
When trying to attempt the downgrade via aahk in linux I am getting invalid image or some error in HBOOT, I just need to figure out how to gain s-off and all my problem I think will be solved. My problem, I have root, s-on, cwm recovery. but when flashing zips in CWM I get stuck on HTC screen. It's like its failing to write to some partitions because of s-on? I can make and restore backups just fine, except that one time when I flashed a boot.img with fastboot. (was getting desperate) so I restored and flashed the boot.img from my nandroid. All is well again.
Running Software:
Android v 2.3.3
HTC Sense 2.1
Baseband 12.56.60.25U_26.10.04.03_M
Kernal 2.6.35.10-gd2564fb
Build 2.47.502.7
HBOOT info:
*** UNLOCKED *** (Via HTC DEV )
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
Please any help or other information will be very helpful, in the mean time I will search and read up on everything. But all I seem to find is outdated information, and aahk. I would prefer to do everything manually, not matter how hard or how long it takes. I feel better doing everything myself, and I will know what went wrong and where when doing it this way. Please if there is a way to manually S-OFF, HELPS! :angel:
P.S. I have root if that helps, gained root using another tool I think it was htcsupertoolv3, but I have tried another tool as well, HTC_QuickRoot_1.1.13_Release.
Another question, Is it the radio flashing that gains S-OFF? is there a way to radio flash using fastboot with S-ON? I can flash stuff with fastboot. I Imagine I can flash with Hboot as well using a gold card, but for some reason I'm getting invalid image errors in Hboot when using aahk.
I just need some help in general lol. Don't be shy ppl I hit the thanks button alot. Thanks in advance!
You need to flash the insecure boot img and relock the bootloader before trying to run aahk... Do you have good instructions for that process?
Sent from my HTC Desire HD using xda app-developers app
RuggedHunter said:
You need to flash the insecure boot img and relock the bootloader before trying to run aahk... Do you have good instructions for that process?
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Wow, so all I need is the boot.img ( I can flash with fastboot correct?) Then relock bootloader, I don't exactly have good instructions, but I'm sure I can find! Thank you My head was hurting, now to start my search!
p.s. If you already got a link by all means post away!
I pm'd you step by step instructions for unlocking inspire, build 3.02.502.52...assuming that's what you are dealing with... If you're part way through the process already, or have already rooted via another method though, I have know idea if it'll work or what potential consequences there could be....so use it at your own risk.
Sent from my HTC Desire HD using xda app-developers app
RuggedHunter said:
I pm'd you step by step instructions for unlocking inspire, build 3.02.502.52...assuming that's what you are dealing with... If you're part way through the process already, or have already rooted via another method though, I have know idea if it'll work or what potential consequences there could be....so use it at your own risk.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Worked Like A Champ! Thank You, That boot.img is actually the one I flashed before when I thought I had screwed everything up. I just didnt relock then rerun aahk. I feel so dumb now. Thank goodness you saved my day! Much LOVE AND THANKS!
Glad I could actually help...
Now go flash Viper 1.2.3 in the Desire HD Dev threads and enjoy your *new* phone!
Sent from my HTC Desire HD using xda app-developers app
Totally went with Jellytime R30 xD, Perhaps I'll try Viper
This was my first HTC phone, and I must say after getting through all the confusion in reading old outdated stuff. It's one of my favs!
Again Thanks for the info about flashing the insecure boot.img and relocking bootloader in prep for aahk, Hopefully ppl like me who tend to overlook stuff will see this, and help them too.
Until my next phone adventure! Peace OUT XDA!
I'll just put this link here for anyone else who stumbles across this thread. It's a detailed list of instructions for new att Rom
http://forum.xda-developers.com/showthread.php?p=30828287
Sent from my Inspire 4G using xda premium
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk