Does the hboot version matter all that much? I have 1.44 right now.
Should I update? If yes, why? What does it affect?
Xenosis said:
Does the hboot version matter all that much? I have 1.44 right now.
Should I update? If yes, why? What does it affect?
Click to expand...
Click to collapse
IMO, it doesn't really matter.. although I've heard that you need the more recent HBOOTs for 4.4.4 etc. If 1.44 is working fine for you, there isn't any reason to upgrade.
StormyNight said:
IMO, it doesn't really matter.. although I've heard that you need the more recent HBOOTs for 4.4.4 etc. If 1.44 is working fine for you, there isn't any reason to upgrade.
Click to expand...
Click to collapse
Thanks, that was my hunch.
I was recently running slimrom 4.4.4 without any issues (that I could notice) on 1.44.
Xenosis said:
Thanks, that was my hunch.
I was recently running slimrom 4.4.4 without any issues (that I could notice) on 1.44.
Click to expand...
Click to collapse
Personally I would not update the HBOOT from 1.44. It makes it very easy to get S-OFF if you need it when you have 1.44 by using revone.
I'm not one that likes to update my hboot.... that being said.
1. If you use Windows 8.1 you will not be able to use fastboot with hboot 1.44.
2. Also I have noticed lately some of the latest RUU's (M7 and M8) require you to have the matching hboot or they will not work, some things to consider.
Related
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Not possible
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Spartn said:
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Click to expand...
Click to collapse
Nope, not possible unless you have S-Off.
i wish i had known that security is better to leave off
thanks guys i think i just have to wait for s off which will work on new hboot 1.54..
will flashing stock ruu work to downgrade hboot?
djcoolguyno1 said:
will flashing stock ruu work to downgrade hboot?
Click to expand...
Click to collapse
That has been answered here already - no
EddyOS said:
That has been answered here already - no
Click to expand...
Click to collapse
How did you get s-off on 1.54?
sopaj96 said:
How did you get s-off on 1.54?
Click to expand...
Click to collapse
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
nkk71 said:
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
Click to expand...
Click to collapse
Exactly that ^
bobs ur uncle, fanny's ur aunt etc..........................
I guess it would be a good idea to post some pointers regarding this issue.
If you're s-on and on fw 1.54, you can't use revone to s-off.
Since you can't s-off, you are limited to flashing only RUUs that are compatible with your CID AND same or higher fw than you currently have on your device.
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there. The only possible way to s-off might be using a java card but I personally wouldn't go that way, even if you found some place that can do it.
makbil said:
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there.
Click to expand...
Click to collapse
So if going from 1.55 back to 1.44 is not possible. And Getting S-OFF with 1.55 is not possible.
Would Sprint be able to reflash my phone with either a working 1.55 or 1.44?
Spartn said:
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Click to expand...
Click to collapse
Try to s-off your phone with hboot 1.54 using rumrunner.
I'm running converted GE with 1.54 Google Hboot on my AT&T M7 (S-Off)
in order to go back to stock with the RUU I have to first load the 2.17 firmware Vomer provided in his thread.
If I don't do that I get error 155 when using the RUU.
I lock my bootloader before running it.
What am I missing. I thought S-off and SuperCID bypassed the checks and RUU's just worked.
Thanks for any advice.
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
iElvis said:
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
Click to expand...
Click to collapse
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
gunnyman said:
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
Click to expand...
Click to collapse
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
iElvis said:
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
Click to expand...
Click to collapse
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
gunnyman said:
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
Click to expand...
Click to collapse
You might try sticking with the 2.17 hboot and see if that helps.
iElvis said:
You might try sticking with the 2.17 hboot and see if that helps.
Click to expand...
Click to collapse
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
gunnyman said:
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
Click to expand...
Click to collapse
Must be the GE hboot or perhaps hboot 1.54 from 2.24 in general. I had a AT&T device with the new firmware and hboot 1.54 (from 2.17) I was able to run the RUU with s-off and bootloader still unlocked.
My fear is an ota for the ge would break the ability to downgrade hboot. The 2.17 works because it is the same 1.54
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Rex2369 said:
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Click to expand...
Click to collapse
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
gunnyman said:
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
Click to expand...
Click to collapse
Coming from full GE experience (1.54 hboot, GE recovery and ROM), I had to flash just the 1.44 hboot and relock my bootloader before the Dev RUU worked for me.
Sent from my HTC One using xda premium
So clearly HTC changed something about what S-off means and what you can and can't do with it.
Alright, so my friend has an AT&T One and it had 1.26.502.10 firmware (like mine), but he had some camera issues... He decided to do all the modding (root, s-off, etc...) and upgraded to 4.2.2 firmware 2.24. His camera issues continue, and he plans on returning to 4.1.2 with the available RUU that returns the phone to 1.26.502.12. He is s-off, supercid, unlocked bootloader, rooted, running twrp 2.6.0.1 and is on stock rooted 2.24.401.1 Rom. I thought of just using that RUU to return him to fully stock, but since it has all the mods I'm not really sure if I should take another approach or other steps. Please help me out here, I don't wanna brick his phone (even though he's taking it to be replaced). Thanks in advanced!
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Just run the RUU, as he's S-OFF there should be no issues
jerrycoffman45 said:
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Click to expand...
Click to collapse
Yes, that's the very file I have. Thanks! Will run it now! Thanks for the quick reply!
EddyOS said:
Just run the RUU, as he's S-OFF there should be no issues
Click to expand...
Click to collapse
Will do, thanks for ur quick reply!
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
EddyOS said:
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
Click to expand...
Click to collapse
Hmm, will I get a kind of error during the RUU process that might possibly brick the device or will it warn me before the RUU process starts? Can I and should I just flash the 1.44 RUU from fastboot before starting the RUU? The phone's on 2.24 right now with the modded 1.54 hboot (I know he first has to flash the original, but can/should he flash the 1.44 instead?).
EDIT: As far as I've read till now, the ones having errors were converted to Google Edition with GE hboot and all... I did read about 2 people (one with 2.17 and the other with 2.24 like my friend's phone) both on 1.54 hboot and it worked for both of em. I'm just gonna go ahead and flash the RUU on my friend's phone and hope for the best
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
ERROR: run distiller again and READ
Click to expand...
Click to collapse
connelhooley said:
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
Click to expand...
Click to collapse
Moonshine does not work with hboot 1.54
connelhooley said:
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
Click to expand...
Click to collapse
No it does not, I am sorry.
dgtiii said:
No it does not, I am sorry.
Click to expand...
Click to collapse
I assume there isn't a way to s-off that version of HBOOT then?
connelhooley said:
I assume there isn't a way to s-off that version of HBOOT then?
Click to expand...
Click to collapse
Not at the moment ... I believe they are working on it though.
s-off
Can you not s-off atall now?
nathlynn22 said:
Can you not s-off atall now?
Click to expand...
Click to collapse
You can if you've got hboot 1.44 but not with 1.54..... HTC closed the exploit with the updated firmware.
If you're s-off with 1.44 then upgrading the firmware won't lose you s-off.
rider5512 said:
You can if you've got hboot 1.44 but not with 1.54..... HTC closed the exploit with the updated firmware.
If you're s-off with 1.44 then upgrading the firmware won't lose you s-off.
Click to expand...
Click to collapse
Is it possible to downgrade your HBOOT? I'm guessing not but thought I'd ask! I also read everywhere that's its pretty risky and probably not worth it.
connelhooley said:
Is it possible to downgrade your HBOOT? I'm guessing not but thought I'd ask! I also read everywhere that's its pretty risky and probably not worth it.
Click to expand...
Click to collapse
Even if you managed to once you rebooted the phone it would essentially brick, and to boot the new hboot you need to reboot.
Just going to have to wait
Sent from my HTC One using Tapatalk 4
I just my One and it came with the following software:
Android Version: 4.2.2
Software Number: 2.24.401.1
HBOOT: 1.54
I understand that Revone S-OFF is not possible with my HBOOT. But is it possible to downgrade HBOOT (and maybe the software, dunno if it's also needed) and achieve S-OFF?
If so, can anyone point me to the right procedure? Or is it as simple as flashing HBOOT 1.44 (for instance) with the fastboot command and then proceed with Revone S-OFF?
Nazgulled said:
I just my One and it came with the following software:
Android Version: 4.2.2
Software Number: 2.24.401.1
HBOOT: 1.54
I understand that Revone S-OFF is not possible with my HBOOT. But is it possible to downgrade HBOOT (and maybe the software, dunno if it's also needed) and achieve S-OFF?
If so, can anyone point me to the right procedure? Or is it as simple as flashing HBOOT 1.44 (for instance) with the fastboot command and then proceed with Revone S-OFF?
Click to expand...
Click to collapse
It is not possible to downgrade your HBOOT
dirtbikerr450 said:
It is not possible to downgrade your HBOOT
Click to expand...
Click to collapse
Thanks for the clarification on that
dirtbikerr450 said:
It is not possible to downgrade your HBOOT
Click to expand...
Click to collapse
It is possible to downgrade your HBOOT if you had s-off prior to upgrading to HBOOT 1.54. However, it is not possible for the OP because he doesn't already have s-off and wants to downgrade to get it.
ajr901 said:
It is possible to downgrade your HBOOT if you had s-off prior to upgrading to HBOOT 1.54. However, it is not possible for the OP because he doesn't already have s-off and wants to downgrade to get it.
Click to expand...
Click to collapse
Just to be clear... Not even if I use this: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe?
Nazgulled said:
Just to be clear... Not even if I use this: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe?
Click to expand...
Click to collapse
It will fail. The RUU checks version numbers and won't allow an earlier version to run.
Nazgulled said:
Just to be clear... Not even if I use this: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe?
Click to expand...
Click to collapse
If you're on HBOOT 1.54 and you don't already have S-OFF, there is no way do downgrade to back to HBOOT 1.44 AS FAR AS I AM CONCERNED. However, I could be wrong. I have never had to use an RUU to downgrade an HBOOT. I've only ever used it to downgrade a radio and touchpad driver and to go back to stock ROM. So it might work for you. You should give it a shot. The worst thing that might happen is that it will fail and you will be back to square one.
Let me know how it goes!
---------- Post added at 01:39 PM ---------- Previous post was at 01:36 PM ----------
iElvis said:
It will fail. The RUU checks version numbers and won't allow an earlier version to run.
Click to expand...
Click to collapse
@Nazgulled, listen to Mr. @iElvis here. He seems to know what he's talking about.
iElvis said:
It will fail. The RUU checks version numbers and won't allow an earlier version to run.
Click to expand...
Click to collapse
Totally correct, the only exception is when you already have S Off, in which case if you run a RUU it will completely wipe your phone and then install the version contained in the ruu, even when it involves downgrade (of hboot, Rom, firmware etc)
Sent from my HTC One using xda app-developers app
Got it :good:
In the same crappy position as you.. Waiting patiently for RevOne to update ?