Hello!
I was wondering if it's ok to downgrade image versions. eg: 1.29.980.17 *TO* 1.29.707.3 ? via RUU
I have S-OFF and also super CID at 11111111. Is it alright to proceed with this?
:good:
That should be fine.
-Sent from Marino's One-
I already downgraded from 1.29.401.16 to 1.27.401.3 and back to 1.29.401.16 again using an RUU + OTA(while being S-Off) and it's perfectly fine so yeah it should be safe.
I am guessing that's not do-able except with S-OFF, right? And do you know SuperCID in order to install ANY RUU or should S-OFF?
TarekElsakka said:
I am guessing that's not do-able except with S-OFF, right? And do you know SuperCID in order to install ANY RUU or should S-OFF?
Click to expand...
Click to collapse
You need S-Off to get SuperCID.
Sent from my HTC_PN071 using Tapatalk 4 Beta
Related
Dears,
i am currently on firmware version 2.24.401.1 and would like to revert back to 1.29.401.16 (bootloader 1.44.0000).. can please someone help me to find where can i download this firmware ?
thanks a lot in advance
zeekabal said:
Dears,
i am currently on firmware version 2.24.401.1 and would like to revert back to 1.29.401.16 (bootloader 1.44.0000).. can please someone help me to find where can i download this firmware ?
thanks a lot in advance
Click to expand...
Click to collapse
You can`t downgrade the Hboot unless you are S-Off.
It is S-ON but bootloader is unlocked using www.htvdev.com
Shall i still S-Off ?
Sent from my LT26ii using xda app-developers app
zeekabal said:
It is S-ON but bootloader is unlocked using www.htvdev.com
Shall i still S-Off ?
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
If you have the 1.54 HBOOT already, then the consensus is that you can't S-OFF. 1.54 most likely blocked the current methods of getting S-OFF.
Even if you RUU back to 1.29.401.16, the HBOOT wouldn't change. It's a one way deal if you didn't S-OFF on 1.44 HBOOT.
cee43ja1 said:
If you have the 1.54 HBOOT already, then the consensus is that you can't S-OFF. 1.54 most likely blocked the current methods of getting S-OFF.
Even if you RUU back to 1.29.401.16, the HBOOT wouldn't change. It's a one way deal if you didn't S-OFF on 1.44 HBOOT.
Click to expand...
Click to collapse
then how can I make use of my phone again
how can i flash a .zip ROM if my phone is not mounting the sdcard
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.
.
Hello! I have the One M7_U(801e). Will it be OK to flash the developer edition RUU (Originally for the M7_UL) to my phone after getting s-off and superCID?
n1234d said:
Hello! I have the One M7_U(801e). Will it be OK to flash the developer edition RUU (Originally for the M7_UL) to my phone after getting s-off and superCID?
Click to expand...
Click to collapse
AFAIK, the RUU install will stop because of not matching model. I remember i wanted to flash a different RUU (accidentally) for my Sensation and it gave me the mismatch error.
davebugyi said:
AFAIK, the RUU install will stop because of not matching model. I remember i wanted to flash a different RUU (accidentally) for my Sensation and it gave me the mismatch error.
Click to expand...
Click to collapse
But after getting superCID and changing the MID to the dev edition (current : PN07110) would it work?
Sent from my iPod touch using Tapatalk
n1234d said:
But after getting superCID and changing the MID to the dev edition (current : PN07110) would it work?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I am not aware of what kind of checks the RUU installer performs and what will be the result if you flash it - sorry.
If you're S-OFF and have Super CID it will flash fine
EddyOS said:
If you're S-OFF and have Super CID it will flash fine
Click to expand...
Click to collapse
So any M7UL RUU on the M7U is fine?
Sent from my iPod touch using Tapatalk
Yep, just no 4G
Another query, suppose I flash this http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/
While I'm s-off, superCID, and on hboot 1.54, will s-off remain after the RUU flash is complete?? Won't an RUU reset s-off? I don't wanna be stuck on 1.55 with s-on
Sent from my iPod touch using Tapatalk
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
nathlynn22 said:
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
alray said:
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
Click to expand...
Click to collapse
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
It's cool I used ruu.exe and downgraded my hboot. Now I've got stock phone just can't get s -on says waiting for device
Sent from my C6833 using Tapatalk
Nevermind. Thanks guys looking good
Sent from my C6833 using Tapatalk
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
good, i'll go read your updated guide! thanks for the info.