downgrade hboot - One (M7) Q&A, Help & Troubleshooting

Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?

c0de1 said:
Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?
Click to expand...
Click to collapse
If you have S-OFF you can flash it through fastboot. Do you need the 1.44.0000 or the 1.43.0000?

c0de1 said:
Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?
Click to expand...
Click to collapse
It's possible but I wouldn't mess around with HBOOTs, just wait until it is supported. It only takes one bad flash to fully brick your phone.

MacHackz said:
It's possible but I wouldn't mess around with HBOOTs, just wait until it is supported. It only takes one bad flash to fully brick your phone.
Click to expand...
Click to collapse
Not dangerous if he used original stock hboot 1.44.0000. I would not trust a modded hboot.

Rex2369 said:
Not dangerous if he used original stock hboot 1.44.0000. I would trust a modded hboot.
Click to expand...
Click to collapse
It is dangerous, if anything happens to the PC or cable mid flash or the flash fails for any reason then it's bricked. It's not likely but it could happen

Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?

c0de1 said:
Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?
Click to expand...
Click to collapse
The touch panel was part of the drivers in the firmware.zip for 2.17, it had nothing to do with the hboot. Not sure if anyone still has the old ones for you to use

c0de1 said:
Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?
Click to expand...
Click to collapse
Now did you downgrade 1.44 from 1.54 ?

Try installing the 1.28 RUU that may downgrade the touch panel firmware.

maxal said:
Now did you downgrade 1.44 from 1.54 ?
Click to expand...
Click to collapse
What do you mean?, yes i have downgrade the hboot from 1.54 to 1.44
just used:
- fastboot reboot bootloader
- fastboot oem rebootRUU
- fastboot flash zip yourhboot.zip
- reboot reboot-bootloader
o yeah you MUST have S-OFF to do this with fastboot!

Electronic Punk said:
Try installing the 1.28 RUU that may downgrade the touch panel firmware.
Click to expand...
Click to collapse
okay and this will wipe my phone clean i think ?
or is it also posible with fastboot without wipe?

c0de1 said:
What do you mean?, yes i have downgrade the hboot from 1.54 to 1.44
just used:
- fastboot reboot bootloader
- fastboot oem rebootRUU
- fastboot flash zip yourhboot.zip
- reboot reboot-bootloader
o yeah you MUST have S-OFF to do this with fastboot!
Click to expand...
Click to collapse
Thanks but I don't have s-off, I tried but I think the new hboot may not work with revone.

c0de1 said:
okay and this will wipe my phone clean i think ?
or is it also posible with fastboot without wipe?
Click to expand...
Click to collapse
It will, I don't believe I saw 1.28 decoded so there is no seperate firmware.zip - an ota might have one but I haven't seen the touchpanel firmware in an OTA.

Electronic Punk said:
It will, I don't believe I saw 1.28 decoded so there is no seperate firmware.zip - an ota might have one but I haven't seen the touchpanel firmware in an OTA.
Click to expand...
Click to collapse
Do you know by change what the steps are to return to stock when i have unlocked hboot and s-off ?

I guess relock and then flash the ruu right from the bootloader.

If you have s-off then we can make a firmware.zip that contains the 1.44.0000 hboot and corresponding tp_SYN3202.img touch panel firmware. I've attached one built for the 1.29.1540.16 Dev Edition RUU files.
Just make sure that the modelid, cidnum, and mainver in android-info.txt of the zip match what's already on your phone (can get these values from the hboot screen) and change android-info.txt if you have to.
Code:
modelid: PN0712000
cidnum: BS_US001
mainver: 1.29.1540.16
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Then flash as mentioned in the earlier post, using 'fastboot oem rebootRUU' and 'fastboot flash zip firmware.zip'.

cschmitt said:
If you have s-off then we can make a firmware.zip that contains the 1.44.0000 hboot and corresponding tp_SYN3202.img touch panel firmware. I've attached one built for the 1.29.1540.16 Dev Edition RUU files.
Just make sure that the modelid, cidnum, and mainver in android-info.txt of the zip match what's already on your phone (can get these values from the hboot screen) and change android-info.txt if you have to.
Code:
modelid: PN0712000
cidnum: BS_US001
mainver: 1.29.1540.16
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Then flash as mentioned in the earlier post, using 'fastboot oem rebootRUU' and 'fastboot flash zip firmware.zip'.
Click to expand...
Click to collapse
I have done that, now i will test it !

c0de1 said:
I have done that, now i will test it !
Click to expand...
Click to collapse
It works like a charme, thank you so much !

MacHackz said:
It is dangerous, if anything happens to the PC or cable mid flash or the flash fails for any reason then it's bricked. It's not likely but it could happen
Click to expand...
Click to collapse
But anything you do to mod the HTC One is dangerous then of course if those scenarios you mention happens. But like you said highly unlikely.

Rex2369 said:
But anything you do to mod the HTC One is dangerous then of course if those scenarios you mention happens. But like you said highly unlikely.
Click to expand...
Click to collapse
Nah, only a hboot or possibly a radio flash can cause a brick like that, nothing else on your One is dangerous and irreversible

Related

can i downgrade with a nandroid using TWRP/CWM

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.
.

[Q] Going back to Stock ATT

hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
biopl said:
hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
Click to expand...
Click to collapse
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
alray said:
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
Click to expand...
Click to collapse
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
biopl said:
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
Click to expand...
Click to collapse
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
alray said:
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
Click to expand...
Click to collapse
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
biopl said:
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
Click to expand...
Click to collapse
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
clsA said:
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
yes
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
do NOT try going S-On with that hboot version!
nkk71 said:
do NOT try going S-On with that hboot version!
Click to expand...
Click to collapse
i dont plan to
biopl said:
i dont plan to
Click to expand...
Click to collapse
:good::good:
nkk71 said:
:good::good:
Click to expand...
Click to collapse
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
clsA said:
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
Click to expand...
Click to collapse
hboot 1.55 introduced an interesting patch, when going from S-Off to S-On, after a few reboots it comes back with "tamper detected - rebooting", and then TAMPERED is back in bootloader.
NB: i cannot confirm this to be 100% true, but i've seen more than a few posts that confirm, even after a full signed ruu etc etc etc, this has happened.
only way to avoid it was to go s-on before updating to 1.55 (hence my guide says to downgrade to lowest version)

[Q] downgrade from 4.4.2 to 4.1.2

Hi guys, I want to downgrade from 4.4.2 to 4.1.2. I'm currently running arhd 71.1 with s-off unlocked twrp and hboot 1.57. I want to downgrade from this state to stock 4.1.2 and hboot 1.44 and keep s-off. I also heard that I should downgrade the fw to make the touch-screen work. What are the steps to do that?
Sent from my HTC One using XDA Free mobile app
kRYySTy said:
Hi guys, I want to downgrade from 4.4.2 to 4.1.2. I'm currently running arhd 71.1 with s-off unlocked twrp and hboot 1.57. I want to downgrade from this state to stock 4.1.2 and hboot 1.44 and keep s-off. I also heard that I should downgrade the fw to make the touch-screen work. What are the steps to do that?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Well, here is the hboot. http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
If you don't want to use a RUU, you should search for 4.1.2 rom for HTC One.
thomaslio said:
Well, here is the hboot. http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
If you don't want to use a RUU, you should search for 4.1.2 rom for HTC One.
Click to expand...
Click to collapse
So i need to flash hboot 1.44 and the flash RUU? And everything will be ok? I will have fw 1.xx and stock 4.1.2 rom?
kRYySTy said:
So i need to flash hboot 1.44 and the flash RUU? And everything will be ok? I will have fw 1.xx and stock 4.1.2 rom?
Click to expand...
Click to collapse
You should check this thread http://forum.xda-developers.com/showthread.php?t=2358738
If you use RUU.exe file, you should stop before using command that makes phone go s-off to s-on.
kRYySTy said:
So i need to flash hboot 1.44 and the flash RUU? And everything will be ok? I will have fw 1.xx and stock 4.1.2 rom?
Click to expand...
Click to collapse
What are your MID and CID?
if MID=PN0710000 and CID are one of those:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
HTC__Y13 --> HTC-Nor
then download: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
and flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes, twice
fastboot reboot-bootloader
Notes:
1- this will not work on Windows 8.1 (hboot 1.44 doesn't work with 8.1)
2- this will completely wipe your phone including internal storage
you can look at my guide for more info: http://forum.xda-developers.com/showthread.php?t=2541082
(stay S-OFF)
kRYySTy said:
So i need to flash hboot 1.44 and the flash RUU?
Click to expand...
Click to collapse
Yes! You will need to verify that your hboot is 1.44 before flashing the RUU. If you flash with the wrong hboot the device may get bricked.
You should also have your recovery back to stock.
Thanks everyone! I found everything I need on @nkk71 thread. I will come later with an edit if everything was OK or I f***ed my phone
Sent from my HTC One using XDA Free mobile app
kRYySTy said:
Thanks everyone! I found everything I need on @nkk71 thread. I will come later with an edit if everything was OK or I f***ed my phone
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
everything will be fine, just make sure to check MD5 on your downloads to make sure nothing is corrupt, and stay s-off (unless you're going for warranty).
if you need other files let me know, i have many of the files mirrored on AFH
One last question:is stock recovery needed at any step or I can downgrade hboot and flash ruu with twrp installed?
Sent from my HTC One using XDA Free mobile app
kRYySTy said:
One last question:is stock recovery needed at any step or I can downgrade hboot and flash ruu with twrp installed?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Actually i am not sure, someone told me once that i needed stock recovery. I still do this, just to be sure my device don't get bricked.
kRYySTy said:
One last question:is stock recovery needed at any step or I can downgrade hboot and flash ruu with twrp installed?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
any ruu will contain everything (stock hboot, stock recovery, stock firmware, stock rom), no need to flash anything separately (it will also completely wipe everything from you phone) -> "out of the box"
if you're going to use the ruu.zip method (which i prefer over ruu.exe), then you don't even need to downgrade hboot
Reason: the hboot downgrade is necessary when flashing signed RUUs (zip or exe), otherwise it will fail (no brick, just fail due to signature check); but when using a decrypted ruu.zip, such as the one I linked, or the one's in htc1guru ruu.zip section, there is no signature check (because the ruu are decrypted, hence having no signature), the first flash will downgrade/update hboot, the second flash will continue with the rest of the firmware and rom.
(obviously flashing decrypted ruu can only be done with s-off)
you can see an example of a ruu.zip flash, in my thread in post #8
---------- Post added at 04:12 PM ---------- Previous post was at 04:09 PM ----------
thomaslio said:
Actually i am not sure, someone told me once that i needed stock recovery. I still do this, just to be sure my device don't get bricked.
Click to expand...
Click to collapse
stock recovery (amongst other things) is needed for OTA updates.
nkk71 said:
stock recovery (amongst other things) is needed for OTA updates.
Click to expand...
Click to collapse
So that means, if i am going to flash a RUU.zip i don't need an stock recovery? What about the hboot, do i need to set that one to 1.44 or does it go to 1.44 when i flash the RUU?
EDIT: Sorry, i did only read what you quote to me. So i got my answer, thanks! I will prefer .zip's in the future!
thomaslio said:
So that means, if i am going to flash a RUU.zip i don't need an stock recovery?
Click to expand...
Click to collapse
correct, RUU will already contain stock recovery.
thomaslio said:
What about the hboot, do i need to set that one to 1.44 or does it go to 1.44 when i flash the RUU?
Click to expand...
Click to collapse
if RUU is same or higher version, then ==> NO need to downgrade hboot
if RUU is lower version, then
---> decrypted RUU.ZIP ==> NO need to downgrade hboot
---> encrypted/signed RUU.ZIP ==> YES, you need to downgrade hboot first
---> RUU.EXE implies an encrypted/signed RUU.ZIP ==> YES, you need to downgrade hboot first
---------- Post added at 07:44 PM ---------- Previous post was at 06:59 PM ----------
thomaslio said:
EDIT: Sorry, i did only read what you quote to me. So i got my answer, thanks! I will prefer .zip's in the future!
Click to expand...
Click to collapse
yep, i do too , but remember they have to be decrypted ruu.zip, if you just extract it from the RUU.EXE and try flashing it, you'll still get the signature fail if hboot is higher than the ruu.zip's

[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

[Q] Can I downgrade 6.06 to 1.29 with S-OFF

Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 1.29.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
uhm, what? this is nonsense , the lastest available RUU is "4.19.401.9" which must be flashed under hboot 1.56 ... there is no need to go to initial release of android 4.1!
WARNING!!! YOU MUST FLASH HBOOT 1.56 BEFORE APPLYING 4.19.401.9 RUU
RUU: http://d-h.st/KmT
+There is no need to LOCK your bootloader to get an OTA update... Mine is always unlocked and never had a problem with OTA's
+RUU's work only under S-OFF
Androidian10 said:
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 4.20.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
Click to expand...
Click to collapse
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Seanie280672 said:
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Click to expand...
Click to collapse
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Androidian10 said:
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Click to expand...
Click to collapse
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Seanie280672 said:
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Click to expand...
Click to collapse
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Androidian10 said:
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Click to expand...
Click to collapse
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Seanie280672 said:
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Click to expand...
Click to collapse
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Androidian10 said:
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Click to expand...
Click to collapse
cid and mid need to match the ruu your flashing first.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Already checked with fastboot getvar all.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Androidian10 said:
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Click to expand...
Click to collapse
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
here you go, do this instead, this is going to be a bit backwards and forwards.
Unlock your bootloader, and flash TWRP recovery, then use the mid change tool to change your mid to the correct one.
https://www.androidfilehost.com/?fid=23622183712469376
next copy this guru reset file to your internal storage and flash it, select no to stock radio and no to stock recovery: http://www.htc1guru.com/2013/11/guru-reset-3-63-707-4-stock-rom/
now lock your bootloader
and finally flash the matching firmwqare from here: http://d-h.st/BWu this will put stock recovery and stock radio on your phone.
Seanie280672 said:
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
Click to expand...
Click to collapse
I actually ran the RUU. It's now stuck on waiting for device after the usual flush after 90 hboot pre-update.
I changed the modelid in the android-info.txt since it was decrypted.
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Androidian10 said:
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Click to expand...
Click to collapse
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Seanie280672 said:
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Click to expand...
Click to collapse
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Androidian10 said:
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Click to expand...
Click to collapse
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Seanie280672 said:
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Click to expand...
Click to collapse
It's okay now. I found a matching mid RUU for my phone.
But my question now is should I go S-ON to remove the red "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings" warning? Or just leave it S-OFF and hope that the techies at the store doesn't notice it?
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Androidian10 said:
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Click to expand...
Click to collapse
no, leave it s-off, if you turn it back s-on now you will get the tampered flag back.

Categories

Resources