Database Develop

Returning phone to stock, a bit afraid...

I had big problems with latest update, whole thing can be read here.
So I did consider all links in that thread what I need to do, and honestly I am a bit afraid, right now on my fastboot menu stands this:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013,23:06:14.1375
...and all other is stock, didn't update anything although phone is asking for update.
So what I need to do now is next as far I understand from all those posts:
- Install custom recovery to my phone, namely TWRP (because CWM can make problems)
- Then I need from recovery to install SuperSU
- Then I need to disable all possible things on my PC (FW, AV etc)
- Connect my phone to PC in standard mode
- Run soju.exe in admin mode and wait till it finishes it (now my phone should be S-Off)
Now this is tricky part for me (I didn't understand the thing with Tampered flag and lock state very well)
- Now I need to install stock rom back to my phone, and it is good to do it with this image, will I have touch screen after installing this?
- Go to OS and do factory reset
- Now, as far I understand I need to run TWRP not install, but just to run it so the phone stays in original state
- While in TWRP I clean cache and run script for removing Tampered flag and to lock bootloader
When all this finished I just need to clean cache and that's it?
Since I didn't install TWRP I'll have original recovery... Also, there they mention that SuperSU needs to be removed, but I don't have it if I follow steps that I wrote here!?
Is this correct procedure? I don't want to mess a lot around my phone...
The S-Off flag I saw can be locked from within fastboot so that I can do whenever I want
Cheers...

This worked for me
http://forum.xda-developers.com/showthread.php?t=2541082
After you unlock your device you most downgrade to hboot 1.44
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Good luck!

Ronnymes said:
This worked for me
http://forum.xda-developers.com/showthread.php?t=2541082
After you unlock your device you most downgrade to hboot 1.44
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Good luck!
Click to expand...
Click to collapse
Thanks m8

Huh, one problem, cannot find nandroid backup with CID HTC__032, what to do now?
Cheers...

rex1825 said:
Huh, one problem, cannot find nandroid backup with CID HTC__032, what to do now?
Cheers...
Click to expand...
Click to collapse
lol me, I have RUU.exe for my phone... I think I can do it in like less then 10min...
Thanks, cheers...

rex1825 said:
lol me, I have RUU.exe for my phone... I think I can do it in like less then 10min...
Thanks, cheers...
Click to expand...
Click to collapse
it'll take a bit more than 10mins, between download (depends on your connection), flashing (5~10mins), booting (another 5~10mins)
and if you untampering too, that takes another few seconds

nkk71 said:
it'll take a bit more than 10mins, between download (depends on your connection), flashing (5~10mins), booting (another 5~10mins)
and if you untampering too, that takes another few seconds
Click to expand...
Click to collapse
I was looking for zip, exe and nandroid all together, a bit rushing there... then I sit down and read once more through tutorial, and see that only one of those is in fact needed.
Just one question more, regarding hboot, there is 1.44 version from 1.29.401.12, does it matter that my RUU.exe is 1.28.401.7?
Cheers...

rex1825 said:
I was looking for zip, exe and nandroid all together, a bit rushing there... then I sit down and read once more through tutorial, and see that only one of those is in fact needed.
Just one question more, regarding hboot, there is 1.44 version from 1.29.401.12, does it matter that my RUU.exe is 1.28.401.7?
Cheers...
Click to expand...
Click to collapse
Nope, hboot won't matter (it's only a temporary step), but ruu will!
Make sure u get ruu for ur mid & CID
Sent from my HTC One using Tapatalk

nkk71 said:
Nope, hboot won't matter (it's only a temporary step), but ruu will!
Make sure u get ruu for ur mid & CID
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
mid PN0710000
CID HTC__032
For this I found "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe"
Cheers...

Did S-Off and hboot @1.44
Now it's time to move on...
Cheers...

Finally...
I did it nkk71 tnx to your guide...
Cheers...

HTC one bricked

Hi There,
I was wondering if anybody could help me please.
I have a HTC one m7 international version, which by mistake wiped the os, now only reboot in bootloader. I have tried to use various RUU but i can not get anywhere allways failed since is S-ON and relocked
I can not get which version the phone has, so i have used the cidnum and modelid. Here below see fastboot loader description.
May be you all have any ideas how to fix this problem.I have been trying for the last 3 days without getting anywhere.
B4 it went wrong I was using CM11 rom 4.4.2 kitkat
I have tried these 2 RUU but failed RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
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 (1)
Many thanks for you help.
version 0.5
version bootloader 1.44.0000
version baseband 4A.14.3250.13
version main? none
version misc pvt ship S-ON
product M7UL
Platform HB00T-8064
modelid PN0710000
cidnum HTC–001
partiton layout generic
security on
build mode ship

gauchosanto said:
Hi There,
I was wondering if anybody could help me please.
I have a HTC one m7 international version, which by mistake wiped the os, now only reboot in bootloader. I have tried to use various RUU but i can not get anywhere allways failed since is S-ON and relocked
I can not get which version the phone has, so i have used the cidnum and modelid. Here below see fastboot loader description.
May be you all have any ideas how to fix this problem.I have been trying for the last 3 days without getting anywhere.
B4 it went wrong I was using CM11 rom 4.4.2 kitkat
I have tried these 2 RUU but failed RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
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 (1)
Many thanks for you help.
version 0.5
version bootloader 1.44.0000
version baseband 4A.14.3250.13
version main? none
version misc pvt ship S-ON
product M7UL
Platform HB00T-8064
modelid PN0710000
cidnum HTC–001
partiton layout generic
security on
build mode ship
Click to expand...
Click to collapse
Can you boot to recovery?
Can't think of a good sig

donkeykong1 said:
Can you boot to recovery?
Can't think of a good sig
Click to expand...
Click to collapse
I am afraid not able any longer

gauchosanto said:
I am afraid not able any longer
Click to expand...
Click to collapse
Try to flash custom recovery via fastboot. it should work. If that works, you just need to sideload a ROM and flash it via custom recovery
Can't think of a good sig

gauchosanto said:
I am afraid not able any longer
Click to expand...
Click to collapse
we not need recovery
We need fastboot getvar all
Then we can help you
from HTC One

your correct rom is the 401 ruu, you don't want to be flashing the asia RUU that's the wrong one.
modelid PN0710000
cidnum HTC–001
(this is WWE Europe edition)
also, you have HBOOT 1.44, that is known to cause problems with windows 8 and above, make sure you are using windows 7 and your drivers and fastboot/adb is up to date.
but like yatindroid said, post your fastboot getvar all.

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0

lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Which RUU you applied ?
6.09.401.111 is might not available
So your only chance is any how unlock it
flash TWRP
Restore nandroid backup

yatindroid said:
Which RUU you applied ?
6.09.401.111 is might not available
So your only chance is any how unlock it
flash TWRP
Restore nandroid backup
Click to expand...
Click to collapse
When i enter flashboot or bootloader... My phone freezers.. Any idea

lordtopher said:
When i enter flashboot or bootloader... My phone freezers.. Any idea
Click to expand...
Click to collapse
maybe hardware issues than

yatindroid said:
maybe hardware issues than
Click to expand...
Click to collapse
what must i do then ???

yatindroid said:
maybe hardware issues than
Click to expand...
Click to collapse
so what should i do?? will i be able to use my phone again ?????:crying:

Nope. It's dead. If it acted up on its own. Bury it. Throw it. Or blend it.

lordtopher said:
so what should i do?? will i be able to use my phone again ?????:crying:
Click to expand...
Click to collapse
take it service center

[Q] How to go from HBOOT 1.57 to HBOOT 1.44 in order to install Stock RUU

I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!

consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots

consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
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 Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.

Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?

consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe

[Q] RUU For htc one

ok so I've been searching for the correct RUU for my phone for some time now and have gone through 3 without any of them working. It always gets stuck "5% checking headers." Can somone please give me the correct RUU for me to install and maybe some directions on installing it, i might be doing it wrong. I relocked my bootloader and S is on. I have T mobile US.
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A. 21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24. 531.3
eMMC-boot 2048MB
MIDN0713000
CID: T-MOB10
Thank you

Aceboog33 said:
ok so I've been searching for the correct RUU for my phone for some time now and have gone through 3 without any of them working. It always gets stuck "5% checking headers." Can somone please give me the correct RUU for me to install and maybe some directions on installing it, i might be doing it wrong. I relocked my bootloader and S is on. I have T mobile US.
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A. 21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24. 531.3
eMMC-boot 2048MB
MIDN0713000
CID: T-MOB10
Thank you
Click to expand...
Click to collapse
I would recommend you get s-off now with rumrunner before you up the hboot to 1.56 / 1.57 and have to pay for it
Why do you want to RUU is your phone broken ? or do you just want to update it ?
Download this OTA and remove and flash the firmware.zip in it >> http://www.htc1guru.com/2013/10/t-mobile-3-24-531-3/
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now flash this RUU >>
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe

clsA said:
I would recommend you get s-off now with rumrunner before you up the hboot to 1.56 / 1.57 and have to pay for it
Why do you want to RUU is your phone broken ? or do you just want to update it ?
Download this OTA and remove and flash the firmware.zip in it >> http://www.htc1guru.com/2013/10/t-mobile-3-24-531-3/
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now flash this RUU >>
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
Click to expand...
Click to collapse
yes, the phone is not working. I accidently wiped it about a week ago without having a rom on it and now im stuck in bootloader, I relocked my bootloader and originally wanted to put a custom rom back on the phone but ive been without a phone for too long now and just want it to work again. I have a few questions, do I have to get S-off in order to do what you said above. 2., If so how do i get S off via rum runner, not really a pro with this. And 3, is the RUU you posted the correct one for my htc one.

Aceboog33 said:
yes, the phone is not working. I accidently wiped it about a week ago without having a rom on it and now im stuck in bootloader, I relocked my bootloader and originally wanted to put a custom rom back on the phone but ive been without a phone for too long now and just want it to work again. I have a few questions, do I have to get S-off in order to do what you said above. 2., If so how do i get S off via rum runner, not really a pro with this. And 3, is the RUU you posted the correct one for my htc one.
Click to expand...
Click to collapse
no
follow instructions from rumrunner thread, you don't need s-off to flash what he said but if you want to have it, better to do it now because once updated you'll have to use sunshine s-off and it cost 25$. Rumrunner is free.
yes

S-off to S-on (Purple tint) Are correct these steps?

Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.

Nasrudin78 said:
Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.
Click to expand...
Click to collapse
You need to downgrade hboot to 1.44 or you will get a fail when you use the ruu.
Also hboot 1.44 has the ability to boot a custom recovery without actually flashing it to the device and returning to s-on on hboots above 1.55 could lead to Tampered message returning after you've completed the process. Then you will need to go back to s-off and start again. So it is best to downgrade hboot to 1.44, lock bootloader remove tampered, run the ruu. Then take the first (and only the first) OTA update. If the update installs OK then it's safe to say you can go back to s-on. :good:
Sent from my HTC One using Tapatalk

But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?

Nasrudin78 said:
But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?
Click to expand...
Click to collapse
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk

Uppps, but now that I'm reading more in detail... If I decide to take the 1st OTA just for extra checking, Can this OTA change the hboot (I mean, hboot 1.44 to more actual one)
doing "fastboot oem ...3" impossible due to the Tampered message protection in hboot > 1.55?
Thx

Danny201281 said:
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <DEL>
(bootloader) imei: <DEL>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!

Nasrudin78 said:
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
Click to expand...
Click to collapse
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
Click to expand...
Click to collapse
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!
Click to expand...
Click to collapse
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning
Click to expand...
Click to collapse
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
Why do 2nd,3rd OTA and so on change hboot and not 1st (only for understanding the reason)?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx

Nasrudin78 said:
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx
Click to expand...
Click to collapse
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk

Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
And what happens if technical support receives the terminal with JB?
I mean, They asked me if my terminal had the last firmware version, because although I explained them that it was a HW problem, they insist to go last version and check if it fixes .
Then if I send the terminal (let's supose up to hboot 1.55 and JB) they would discover that I'm hiding something to them...
That's the reason I want to let the terminal with the latest firmware and Android version...
Thx

Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Option 1:
htc_fastboot flash zip LP.zip (x2)
Apply 1st OTA (risk of TAMPERING??)
SOFF -> SON
Click to expand...
Click to collapse
Option 2: (safer??)
fastboot flash zip JB.zip (x2)
Apply 1st OTA ( here I'd have hboot 1.54)
SOFF -> SON
Apply 2nd, 3rd, and so OTA's up to LP and last firmware (risk of TAMPERING??)
Click to expand...
Click to collapse
Thanks, that's my last question. Sorry

Nasrudin78 said:
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Thanks, that's my last question. Sorry
Click to expand...
Click to collapse
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk

Danny201281 said:
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks Danny,
Option 2 worked like a charm! But i spent more than 3hours during the overall OTA update process. LOL!