Database Develop

[Q] How to downgrade to a hboot older than 1.25 [Solved]

Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).

KazumaSaruwatari said:
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
Click to expand...
Click to collapse
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps

Lexmazter said:
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Click to expand...
Click to collapse
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?

KazumaSaruwatari said:
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
Click to expand...
Click to collapse
Well, as far as i know, you unlock the bootloader again, S-OFF, and after that you flash the RUU, i didn't install any RUU's until now, you should check the guide from stona15 that can be found here, There are more details about what to do and what you want.
Hope this helps

I have S-off how do I downgrade with an RUU?

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.

[Q] Just want to confirm if I can flash RUU when I"m S-OFF and CID11111111

All,
I have the Dev Edition with S-OFF and CID111111 running ARHD 13.3. With the latest update to the Dev Edition to 4.3, can I just flash the RUU for the latest of the Dev Edition? Will it work with TWRP custom recovery?
Thanks for any info.

Emh, the RUU isn't a zip, but an exe that you have to flash with the pc...
However, you can flash it

You can flash an RUU when S-OFF with Super CID, I've done it a number of times
The RUU is a complete update so it will overwrite the custom recovery anyway

Awesome guys....with that being said, I have a few more question. Since I'm S-Off and Super CID, you said I can flash any RUU, but it will wipe the custom recovery. That is fine, but when I want to flash a ROM in the future, I will have to reflash a new recovery correct? Will this mess with my HBOOT? I'm on 1.55 right now.
Also, I'm on the http://forum.xda-developers.com/showthread.php?p=39588860 looking at the collecdtion of RUU's...do I flash the ZIP, EXE or the Decrypted RUU's?
Again, thanks for your replies!

Download the RUU from HTCDev directly so you know you've got the right file, then flash it with the phone connected in fastboot. It will downgrade the HBOOT and put the phone back to 1.29.1540.16 and be just like it was out the box (except you'll still be S-OFF with Super CID). You can then get the OTA to .17 and then the OTA to Android 4.3...after that, you can flash a custom recovery and do what you want (but I'd take a nandorid first of course)

EDDYOS,
Thanks for all your info!! I will do exactly that!
One last question, I promise...since I am on S-OFF I should not be worried that flashing the RUU and downgrading to HBOOT 1.54 and not be able to achieve SOFF again? Cause isn't 1.54 having issues with SOFF? Or does that not matter to me since I have the Dev Editoin?
Again, thanks for all your advice.

You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF

EddyOS said:
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
Click to expand...
Click to collapse
EddyOS...
Thanks alot! Gotcha!

[Q] Developer Edition flashed to GPE, back to Stock?

I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)

docdoc518 said:
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
Click to expand...
Click to collapse
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk

n1234d said:
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!

docdoc518 said:
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
Click to expand...
Click to collapse
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk

so as long as the you are s-off, you can ruu to any version even if you are at 1.54 hboot?
n1234d said:
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse

You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first

EddyOS said:
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
Click to expand...
Click to collapse
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information

docdoc518 said:
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
Click to expand...
Click to collapse
Follow what eddy says, he's the man @eddy, how does the hboot version make a difference??
Sent from my iPod touch using Tapatalk

I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me

EddyOS said:
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
Click to expand...
Click to collapse
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.

You should be fine on that HBOOT, just try it and if it works it works! If not, you'll get an error and then you just following the second post in the GPe conversion thread

docdoc518 said:
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
Click to expand...
Click to collapse
Yep, go ahead and try, if it gives you an error, post back.
AFAIK, the dev edition BS_US001 gets OTAs the quickest, so you could keep it at that. SuperCID will allow you to flash any RUU/OTA, even of a different region/MID/CID
Nope, you're not being a pain We're all trying to learn and help here

Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:

docdoc518 said:
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
Click to expand...
Click to collapse
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result

EddyOS said:
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
Click to expand...
Click to collapse
Newbie move I suppose :angel: haha
I've been rooting and flashing ROMs on my Androids since the G1/Dream believe it or not, but with every new phone/manufacturer there's always new terminology and steps to be taken so I feel like I start over every single time, which honestly isn't much of a bad thing, keeps things exciting (even though HTC made the G1 but that was what feels like ages ago now)
Thanks again guys, it's hard not to feel intimidated but it's been an extremely pleasant experience learning from you. This is why xda is by far the best site you can find for these things.
Cheers

[Q] Going back to Sense from GPE

Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance

diesalher said:
Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance
Click to expand...
Click to collapse
here are some links, if you're going to use a signed/encryped ruu, then you'll need to downgrade hboot first https://www.androidfilehost.com/?fid=23329332407580580
http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
http://androidruu.com/getdownload.p...50.13_10.33.1150.01_release_316789_signed.zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
https://www.androidfilehost.com/?fid=23329332407584993

Thanks. Whats the difference between signed and unsigned?

diesalher said:
Thanks. Whats the difference between signed and unsigned?
Click to expand...
Click to collapse
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2

nkk71 said:
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2
Click to expand...
Click to collapse
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?

diesalher said:
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?
Click to expand...
Click to collapse
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634

clsA said:
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
Click to expand...
Click to collapse
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.

diesalher said:
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.
Click to expand...
Click to collapse
The 1.28.401.7 is Jelly Bean it's equal to a 3.xx.xxx.x RUU
So the Firmware you would want is this http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip