i have a htc one m7
CID: ORANG001
MID: PN0710000
having a hard time finding the correct RUU, just wondering as long as MID is the same does it matter if CID is different? i am s-on btw just trying to downgrade RUU's in an attempt to downgrade hboot
please help thanks
zFayZz said:
i have a htc one m7
CID: ORANG001
MID: PN0710000
having a hard time finding the correct RUU, just wondering as long as MID is the same does it matter if CID is different? i am s-on btw just trying to downgrade RUU's in an attempt to downgrade hboot
please help thanks
Click to expand...
Click to collapse
You need the exact one for your phone/region if you are S-On. Also, you can't downgrade your Hboot when you're S-On. I suspect you are on Hboot 1.54 seeing as you want to downgrade? Well you can't as you couldn't even go S-Off on that Hboot unless you had S-Off before you upgraded.
In a nutshell, you're stuck with what you have until somebody finds a way to go S-Off on Hboot 1.54 ... Why on earth do you want to downgrade anyways
AllAboutTheCore said:
You need the exact one for your phone/region if you are S-On. Also, you can't downgrade your Hboot when you're S-On. I suspect you are on Hboot 1.54 seeing as you want to downgrade? Well you can't as you couldn't even go S-Off on that Hboot unless you had S-Off before you upgraded.
In a nutshell, you're stuck with what you have until somebody finds a way to go S-Off on Hboot 1.54 ... Why on earth do you want to downgrade anyways
Click to expand...
Click to collapse
i thought it was possible to downgrade hboot with ruu as someone has done it before
zFayZz said:
i thought it was possible to downgrade hboot with ruu as someone has done it before
Click to expand...
Click to collapse
You can't run an RUU though, other than the one made for your model/region and it has to be the same as the version you are on, or newer. To run an RUU that is an earlier version than what you're on requires you to be S-Off I believe and if you're on 1.54 then there isn't currently a way to get S-Off.
AllAboutTheCore said:
You can't run an RUU though, other than the one made for your model/region and it has to be the same as the version you are on, or newer. To run an RUU that is an earlier version than what you're on requires you to be S-Off I believe and if you're on 1.54 then there isn't currently a way to get S-Off.
Click to expand...
Click to collapse
guess i'll have to wait for the hboot 1.54 to get hacked thanks
Related
Can anyone help me find this stock recovery as i want to unroot and update my rom then re-root
mimicuk said:
Can anyone help me find this stock recovery as i want to unroot and update my rom then re-root
Click to expand...
Click to collapse
No resolution for this?
I'm S-ON, hboot 1.54, CID=VODAP001.
As I understand things, i cant S-OFF because i'm on hboot 1.54 and Revone doesnt work on 1.54.
I cant use SuperCID because i'm S-ON
I cant flash any firmware unless the CID=VODAP001
(and now I wont get any OTA's as i went ahead an flashed a new ROM)
So i'm slightly stuck until either someone finds a way to S-OFF the hboot 1.54 or we track down a nandroid backup or RUU for CID=VODAP001
smithbill said:
No resolution for this?
I'm S-ON, hboot 1.54, CID=VODAP001.
As I understand things, i cant S-OFF because i'm on hboot 1.54 and Revone doesnt work on 1.54.
I cant use SuperCID because i'm S-ON
I cant flash any firmware unless the CID=VODAP001
(and now I wont get any OTA's as i went ahead an flashed a new ROM)
So i'm slightly stuck until either someone finds a way to S-OFF the hboot 1.54 or we track down a nandroid backup or RUU for CID=VODAP001
Click to expand...
Click to collapse
i have same problem did u sort it iut
Grathite said:
i have same problem did u sort it iut
Click to expand...
Click to collapse
Yes I did.
You want to use Rumrunner to achieve S-OFF (assuming you are on hboot 1.54 and S-ON like I was).
Full details are available at:
http://forum.xda-developers.com/showthread.php?t=2488772
Make sure to pay attention to the various requirements. It does work. I am now S-OFF, hboot 1.55 and SuperCID and have been able to flash new Firmware without issues.
Bill
Grathite said:
i have same problem did u sort it iut
Click to expand...
Click to collapse
for hboot 1.54 and 1.55:
http://forum.xda-developers.com/showthread.php?t=2487888 and http://rumrunner.us/
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.
basically trying to get s-off on my device i am on hboot 1.54 as i recently updated to sense 4.2.2
CID: ORANG001
MID: PN0710000
version main: 2.24.61.1
now i have rooted with TWRP & wondering if i can use this nandroid to downgrade:
M7 CWM Nandroid Backup / CID ORANG001 / 1.28.61.7 (Orange UK - Thanks to Azzabear)
http://click.xda-developers.com/api... / 1.28.61.7&jsonp=vglnk_jsonp_13761274174228
would it work & would it downgrade the hboot?
Nandroid won't downgrade hboot.
Sent from my HTC One using xda premium
could i use an older RUU to replace hboot?
zFayZz said:
could i use an older RUU to replace hboot?
Click to expand...
Click to collapse
Sorry, I've no experience with RUUs - never used one. I would guess it would but since you're S-ON you obviously can't superCID, so you would need to find the proper RUU for your CID.
There is no known way to downgrade an hboot on an s-on device.
gunnyman said:
There is no known way to downgrade an hboot on an s-on device.
Click to expand...
Click to collapse
Just wondering for my own interest, gunny.. what does an RUU restore? I thought it was stock hboot, firmware, rom, recovery, etc. (everything basically). Or is it just that it can't downgrade even with an RUU if you are S-ON and would need to wait on a new RUU being released? Unless you're S-off and can superCID, then your can run any RUU - and that would downgrade *everything*..
cheers
redbull123 said:
Just wondering for my own interest, gunny.. what does an RUU restore? I thought it was stock hboot, firmware, rom, recovery, etc. (everything basically). Or is it just that it can't downgrade even with an RUU if you are S-ON and would need to wait on a new RUU being released? Unless you're S-off and can superCID, then your can run any RUU - and that would downgrade *everything*..
cheers
Click to expand...
Click to collapse
The RUU is as far as I know a collection of all of the partition images for the phone.
Even with S-off it is not possible to downgrade an HBoot without flashing that HBoot separately. IOW if you are on a 1.54 firmware, in order to flash an RUU containing 1.44 Hboot you have to flash the 1.44 Hboot by itself or else the RUU will fail.
SuperCID (11111111) will pass the CID check
It is my understanding that in the past, S-off meant you could downgrade with just the RUU but that doesn't seem to be the case anymore.
The RUU install checks a few things
MID and CID
HBoot must be the same or greater version number
if these checks fail, the RUU won't flash even with S-off
The beauty of S-off is, we can flash these things manually without the RUU bypassing the checks.
You can simply use the DD command in a root shell and copy the partitions to the phone, but this is dangerous, because if you put a partition in the wrong location, BRICK.
My knowledge here is not as advanced as many here, so someone please correct me if I got any of this wrong.
.
Hi,
A couple of questions, here is my current situation:
ROM: Vipper 2.6
Cid:vodap001
S-on
Device : PN0710000
Boot loader 1.54.0000
Bootloader is unlocked and has the messaged TAMPERED. I need to send the phone back to HTC for repair as I have a display issue.
How do I get rid of the TAMPERED message, guessing reloocking the bootloader can be done via adb\fastboot ?
If the steps I need to do requires me to be S-OFF, I can send the phone to fonefunshop to get that completed.
I just need to know the steps I should take to achieve the above.
Also need a nandroid backup for CID: VODAP001 (anyone?)
If I manage to remove the TAMPERED message and get the bootloader to show as locked, do I need to change the CID number back to VODAP001 and do I need to go back to S-ON ?
http://forum.xda-developers.com/showthread.php?t=2265618
A good read for you :fingers-crossed:
The search option would have given you Mikes thread :highfive:
I should add there is no RUU for my CID. Also, instead of RELOCKED, can you get it to show LOCKED ?
Or does that not matter if sending the phone back for repair ?
akuma24 said:
I should add there is no RUU for my CID. Also, instead of RELOCKED, can you get it to show LOCKED ?
Or does that not matter if sending the phone back for repair ?
Click to expand...
Click to collapse
You can only get it to show LOCKED if you're on hboot 1.44 and use revone to S-Off, then remove TAMPERED and change to LOCKED.
nkk71 said:
You can only get it to show LOCKED if you're on hboot 1.44 and use revone to S-Off, then remove TAMPERED and change to LOCKED.
Click to expand...
Click to collapse
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?
akuma24 said:
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?
Click to expand...
Click to collapse
Yes, once you're S-Off you can downgrade using any RUU. But you can't S-Off 1.54 at the moment (unless you know someone with a JavaCard)
akuma24 said:
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?
Click to expand...
Click to collapse
If you're on hboot 1.54 then you can't get s-off at the moment
rider5512 said:
If you're on hboot 1.54 then you can't get s-off at the moment
Click to expand...
Click to collapse
I can, there is a place in Sheffield, England that can S-OFF hboot 1.54 all for the sum of £12.99
Think a couple of chaps on here have already had it done.
akuma24 said:
I can, there is a place in Sheffield, England that can S-OFF hboot 1.54 all for the sum of £12.99
Think a couple of chaps on here have already had it done.
Click to expand...
Click to collapse
Ok