Database Develop

downgrade hboot

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

Can I install a Google Edition RUU in a HTC Developer Edition device?

I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards

only if your s-off

Victor Potasso said:
I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards
Click to expand...
Click to collapse
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help

alray said:
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help
Click to expand...
Click to collapse
Can I set my device to s-off?

Victor Potasso said:
Can I set my device to s-off?
Click to expand...
Click to collapse
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
First you need to be S-Off, this will NOT work with S-On!!!
A) If you’re on hboot 1.44 use revone to get S-Off: http://forum.xda-developers.com/show....php?t=2314582
B) If you’re on hboot 1.54/1.55 use rumrunner to get S-Off: http://rumrunner.us/ and http://forum.xda-developers.com/show....php?t=2487888
Click to expand...
Click to collapse
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820

alray said:
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820
Click to expand...
Click to collapse
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID

Victor Potasso said:
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID
Click to expand...
Click to collapse
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.

alray said:
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.
Click to expand...
Click to collapse
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate

Victor Potasso said:
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate
Click to expand...
Click to collapse
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.

swag1981 said:
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.
Click to expand...
Click to collapse
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards

Victor Potasso said:
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards
Click to expand...
Click to collapse
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.

swag1981 said:
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.
Click to expand...
Click to collapse
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:

Victor Potasso said:
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:
Click to expand...
Click to collapse
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk

Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
Cheers

Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
:cheers:

Give this site a read over too when you get a chance http://www.htc1guru.com/downloads/
Sent from my HTC One using Tapatalk

swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.

swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I just tried run this .exe but I got this error http://imgur.com/rYvIdBd
I downloaded RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe but my current ROM is Android 4.3 version 3.22.1540.1. I suppose I got this error because I tried to install a oldest version in my device. Does it make any ****ing sense?
I'm downloading the .exe for 3.22.1540.1 and than try to install it.
Regards

alray said:
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.
Click to expand...
Click to collapse
Yep, my device has MID as PN0712000 and CID BS_US001
I tried run RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe from HTC1GURU byt i got this error http://imgur.com/rYvIdBd
My current software version is 3.22.1540.1.

@alray and @swag1981
I followed this thread http://forum.xda-developers.com/showthread.php?p=46046898
If I have a hboot S-ON it has to be LOCKED or RE-LOCKED. It'll never work with hboot UNLOCK. So if your hboot is S-OFF it not matter.
Thank u mates. You were friggin' awesome.
Regards

Htc One stuck 4 triangle please help

Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11

Antoo1984 said:
Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Click to expand...
Click to collapse
which HBOOT version are you on ?

You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk

Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED

raghav kapur said:
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
Click to expand...
Click to collapse
i'm on hboot 1.56

Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Not really, With S-ON you can flash signed ruu of same or higher version with bootloader LOCKED or RE-LOCKED.
S-OFF is only needed to flash unsigned RUU or for downgrading, and with S-OFF you can flash a RUU with a locked/relocked or unlocked bootloader.
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
Edit: So you were on 4.19.401.11 before flashing 4.19.401.9 ? You can't downgrade with S-ON

DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?

Antoo1984 said:
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?
Click to expand...
Click to collapse
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)

raghav kapur said:
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
Click to expand...
Click to collapse
i've try to unlock bootloader but noting happen, say always relocked

Antoo1984 said:
i've try to unlock bootloader but noting happen, say always relocked
Click to expand...
Click to collapse
You don't get to the unlock bootloader option ??

no nothing

Antoo1984 said:
no nothing
Click to expand...
Click to collapse
I really don't know if there is a solution, maybe we could ask @nkk71 if he have an idea....
OP is stuck in ruu mode after an incomplete ruu flash from 4.19.401.11 to 4.19.401.9. S-ON, bootloader relocked (not able to unlock again). THe only option in bootloader is RUU in orange.

Antoo1984 said:
no nothing
Click to expand...
Click to collapse
Yes, @nkk71 might have an idea. Im just sharing what I know- If you cannot get into fastboot also, you really have a serious problem. Your only option (not 100% sure) is an RUU based on 4.19.401.11, which doesn't currently exist. If there is another solution, I don't know. But I think you will have to wait for an RUU based on your version.

Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
That screenshot does not look nice!
you're firmware is in limbo... from the looks of it, you did the first flash, but didn't do the second flash.
So first make sure the RUU you have is not corrupt, the MD5 should be 9AD4111CE86981E3DFFCCE6D9EE80551
Second, do you still have a custom recovery installed, or a rooted ROM?

I've stock recovery , i'm sure
Before i've a stock rom by grureset
I can use ruu 4.19.401.9? Or can i flash rom.zip with fastboot?
Inviato dal mio GT-N8000 usando XDA Premium HD app

Finally i've found a solution!!!!
i've downloaded the ota 4.19.401.11 extract firmware.zip
flash it with fastboot 2 times and now i can access to bootloader!!
Thanks for support

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

Htc One AT&T trying to upgrade to lollipop using official RUU - get error 155

Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,

BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!

BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!

BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!