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
Related
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
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
+1
Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium
No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app
LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol
ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
http://forum.xda-developers.com/showthread.php?p=39588860
No offense but you didn't look very hard. Its in a sticky in the dev thread
Once you s-off (which is ridiculously easy for this device) you can use any RUU. Good luck and enjoy
Sent from my One using Tapatalk 2
Anicane said:
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
Click to expand...
Click to collapse
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
AllAboutTheCore said:
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
Click to expand...
Click to collapse
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Anicane said:
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Click to expand...
Click to collapse
Cool, yes, you are correct, S-Off can be reverted ... It's also worth noting that if you S-Off now, you'd be able to upgrade to Hboot 1.54 and still maintain S-Off. The problem lies with those, like me, who are on the 1.54 Hboot but haven't gone S-Off ... We're now stuck until a solution is available, although I didn't want to go S-Off so it's not really a problem.
If you go S-Off btw you can flash any RUU from any region and change your Cid/Mid, although I can't help you on the whole RUU when S-Off process as I've never run one, nor been S-Off as I previously mentioned lol.
I still can't find which RUU is for my phone, is there anyway to find ? is it via CID or any other way ?
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
EddyOS said:
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
Click to expand...
Click to collapse
It is 1.29.401.16
Anicane said:
It is 1.29.401.16
Click to expand...
Click to collapse
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
EddyOS said:
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
Click to expand...
Click to collapse
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Anicane said:
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Click to expand...
Click to collapse
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
EddyOS said:
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
Click to expand...
Click to collapse
Well, i am thinking of a scenario which i don't know is possible or not, so here it goes. Since i want to be on the safe side, how about i take a nandorid back of the stock, and than if i wanted to returen to stock, simply flash an RUU like 1.29.401.16, and than simply recover the nandroid backup over it, and update if i wanted to ? Is it possible ?
The only problem is that i don't know how to remove the custom recovery when it restore the nandorid back, and update it.
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Seanie280672 said:
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Click to expand...
Click to collapse
Great, thanks! I will flash the original firmware in a sec, but the most recent RUU I can find is this one: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
And I am not sure if that is also based on hboot 1.57 and because of that, if I am able to flash this RUU. Currently I am downloading it but the download speed is terrible, I will report back after I tried.
Or are you saying that I can flash the stock firmware 5.xx.401.xx on top of the current 6.xx firmware? I thought that wouldn't be possible because I'm currently on a higher firmware version but I'll give it a shot!
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Seanie280672 said:
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Click to expand...
Click to collapse
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
WiiiLDFARMER said:
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
Click to expand...
Click to collapse
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Once it's finished, boot the phone once and then back into bootloader and check the hboot version, if it is lower than the version you have on there now then you'll know you have stock hboot and should be safe to s-on, however like I said before, make sure your locked and tampered has gone before setting s-on (not sure if s-on is required for warranty)
Seanie280672 said:
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Click to expand...
Click to collapse
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
WiiiLDFARMER said:
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
Click to expand...
Click to collapse
Unfortunately I don't know that, there's been some reports it comes back after you s-on not after the ruu, I think it's HTC 's way of catching you out, others say it's been fine, are you sending it to HTC or your operator ?
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
However , if you've had s-off with that phone before, chances are you'll get it again, you'll just have to do whatever you did before to get it, then go back to stock again, and send it s-off.
WiiiLDFARMER said:
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
Click to expand...
Click to collapse
Try this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
It worked for me, returned full stock!
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