Database Develop

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

do RUU's have to match CID's?

i have a htc one m7
CID: ORANG001
MID: PN0710000
having a hard time finding the correct RUU, just wondering as long as MID is the same does it matter if CID is different? i am s-on btw just trying to downgrade RUU's in an attempt to downgrade hboot
please help thanks

zFayZz said:
i have a htc one m7
CID: ORANG001
MID: PN0710000
having a hard time finding the correct RUU, just wondering as long as MID is the same does it matter if CID is different? i am s-on btw just trying to downgrade RUU's in an attempt to downgrade hboot
please help thanks
Click to expand...
Click to collapse
You need the exact one for your phone/region if you are S-On. Also, you can't downgrade your Hboot when you're S-On. I suspect you are on Hboot 1.54 seeing as you want to downgrade? Well you can't as you couldn't even go S-Off on that Hboot unless you had S-Off before you upgraded.
In a nutshell, you're stuck with what you have until somebody finds a way to go S-Off on Hboot 1.54 ... Why on earth do you want to downgrade anyways

AllAboutTheCore said:
You need the exact one for your phone/region if you are S-On. Also, you can't downgrade your Hboot when you're S-On. I suspect you are on Hboot 1.54 seeing as you want to downgrade? Well you can't as you couldn't even go S-Off on that Hboot unless you had S-Off before you upgraded.
In a nutshell, you're stuck with what you have until somebody finds a way to go S-Off on Hboot 1.54 ... Why on earth do you want to downgrade anyways
Click to expand...
Click to collapse
i thought it was possible to downgrade hboot with ruu as someone has done it before

zFayZz said:
i thought it was possible to downgrade hboot with ruu as someone has done it before
Click to expand...
Click to collapse
You can't run an RUU though, other than the one made for your model/region and it has to be the same as the version you are on, or newer. To run an RUU that is an earlier version than what you're on requires you to be S-Off I believe and if you're on 1.54 then there isn't currently a way to get S-Off.

AllAboutTheCore said:
You can't run an RUU though, other than the one made for your model/region and it has to be the same as the version you are on, or newer. To run an RUU that is an earlier version than what you're on requires you to be S-Off I believe and if you're on 1.54 then there isn't currently a way to get S-Off.
Click to expand...
Click to collapse
guess i'll have to wait for the hboot 1.54 to get hacked thanks

[Q] HTC Warranty and going back to stock

Hi,
A couple of questions, here is my current situation:
ROM: Vipper 2.6
Cid:vodap001
S-on
Device : PN0710000
Boot loader 1.54.0000
Bootloader is unlocked and has the messaged TAMPERED. I need to send the phone back to HTC for repair as I have a display issue.
How do I get rid of the TAMPERED message, guessing reloocking the bootloader can be done via adb\fastboot ?
If the steps I need to do requires me to be S-OFF, I can send the phone to fonefunshop to get that completed.
I just need to know the steps I should take to achieve the above.
Also need a nandroid backup for CID: VODAP001 (anyone?)
If I manage to remove the TAMPERED message and get the bootloader to show as locked, do I need to change the CID number back to VODAP001 and do I need to go back to S-ON ?

http://forum.xda-developers.com/showthread.php?t=2265618
A good read for you :fingers-crossed:
The search option would have given you Mikes thread :highfive:

I should add there is no RUU for my CID. Also, instead of RELOCKED, can you get it to show LOCKED ?
Or does that not matter if sending the phone back for repair ?

akuma24 said:
I should add there is no RUU for my CID. Also, instead of RELOCKED, can you get it to show LOCKED ?
Or does that not matter if sending the phone back for repair ?
Click to expand...
Click to collapse
You can only get it to show LOCKED if you're on hboot 1.44 and use revone to S-Off, then remove TAMPERED and change to LOCKED.

nkk71 said:
You can only get it to show LOCKED if you're on hboot 1.44 and use revone to S-Off, then remove TAMPERED and change to LOCKED.
Click to expand...
Click to collapse
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?

akuma24 said:
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?
Click to expand...
Click to collapse
Yes, once you're S-Off you can downgrade using any RUU. But you can't S-Off 1.54 at the moment (unless you know someone with a JavaCard)

akuma24 said:
Thanks, If I get S-OFF on hboot 1.54, can I downgrade to 1.44 ?
Click to expand...
Click to collapse
If you're on hboot 1.54 then you can't get s-off at the moment

rider5512 said:
If you're on hboot 1.54 then you can't get s-off at the moment
Click to expand...
Click to collapse
I can, there is a place in Sheffield, England that can S-OFF hboot 1.54 all for the sum of £12.99
Think a couple of chaps on here have already had it done.

akuma24 said:
I can, there is a place in Sheffield, England that can S-OFF hboot 1.54 all for the sum of £12.99
Think a couple of chaps on here have already had it done.
Click to expand...
Click to collapse
Ok

Unable to unlock relocked hboot

I re-locked my phone with a custom recovery and attempted to unlock again and goes through successful though the unlock screen does not show up.(Probably because I have no OS installed?)
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check [COLOR="DeepSkyBlue"]successfully[/COLOR]
OKAY [ 0.003s]
finished. total time: 0.144s
My current information is:
*** Tampered ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum:[COLOR="DeepSkyBlue"]GOOGL001[/COLOR]
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
Ive tried the method below with a few RUU's though I keep getting the error "FAILED (remote: 12 signature verify fail)" Their must some RUU that I can flash that correlates to my above information?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Code:
C:\Users\chanik\Desktop\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fa
stboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388870 KB)...
OKAY [ 15.220s]
writing 'zip'...
(bootloader) signature checking...
[COLOR="Red"]FAILED (remote: 12 signature verify fail)[/COLOR]
finished. total time: 53.263s
If someone could confirm I have fully bricked my device that be great so i can move on with my life

I foundout that i dont have a mainvar... is tjis bad?

ronniereiff said:
I foundout that i dont have a mainvar... is tjis bad?
Click to expand...
Click to collapse
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk

nkk71 said:
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Twrp, though i am unable to use it due to being relocked..

ronniereiff said:
Twrp, though i am unable to use it due to being relocked..
Click to expand...
Click to collapse
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please

nkk71 said:
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
Click to expand...
Click to collapse
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread

ronniereiff said:
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
Click to expand...
Click to collapse
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).

nkk71 said:
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
Click to expand...
Click to collapse
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.

ronniereiff said:
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
Click to expand...
Click to collapse
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.

nkk71 said:
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
Click to expand...
Click to collapse
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.

ronniereiff said:
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
Click to expand...
Click to collapse
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
I have successfully unlocked after flashing the 3.58.1700.5 kitkat firmware Just need to see how to get kitkat now

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.

ronniereiff said:
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
Click to expand...
Click to collapse
Cache unable to mount is ok, it's because it's wiped, so don't worry about that.
To be able to flash a 4.4 ROM, you need TWRP 2.6.3.3 or above, but since you're S-On you cannot flash a GPE 4.4 ROM as they require S-Off.
Use adb sideload, adb push, or OTG cable to get a ROM to TWRP.
Hit the thanks button if i've helped

nkk71 said:
Hit the thanks button if i've helped
Click to expand...
Click to collapse
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff

ronniereiff said:
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
Click to expand...
Click to collapse
Can you post where did you get the rom you flashed?

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!