Database Develop

4.3 GE back to Stock sense

Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!

RockLee91 said:
Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!
Click to expand...
Click to collapse
Simply flash a stock RUU which matches the CID or just use fastboot oem writecid 11111111 to be able to flash any RUU.

RockLee91 said:
Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!
Click to expand...
Click to collapse
if you have S-Off download any RUU and open the .EXE file on your Windows PC, then follow the instruction

Can i execute a ruu of a lower version? And can i do that with 1.54 hboot? When i try with HTC__001 cid the setup wizard give me error this is the ruu i want to flash. RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Its the correct One?

I've tried with super cid but the result was the same... Any advice?

RockLee91 said:
I've tried with super cid but the result was the same... Any advice?
Click to expand...
Click to collapse
Try this.
1. Run the RUU and click next but no further
2. Go to your user folder ie C:\Users\Nameofuser\AppData\Local\Temp
3. Search for rom.zip and then copy it to another location on your PC
4. Stop the RUU
5. Reboot your phone into the bootloader
6. Go into fastboot
7. fastboot oem rebootRUU
8. fastboot flash zip rom.zip (will fail the first time)
9. fastboot flash zip rom.zip (should now work)

daleski75 said:
Try this.
1. Run the RUU and click next but no further
2. Go to your user folder ie C:\Users\Nameofuser\AppData\Local\Temp
3. Search for rom.zip and then copy it to another location on your PC
4. Stop the RUU
5. Reboot your phone into the bootloader
6. Go into fastboot
7. fastboot oem rebootRUU
8. fastboot flash zip rom.zip (will fail the first time)
9. fastboot flash zip rom.zip (should now work)
Click to expand...
Click to collapse
The first time i do fastboot the terminal work for a while and then get the failed message, the second time got failed message again without work, it says status read failed (too many links)

RockLee91 said:
The first time i do fastboot the terminal work for a while and then get the failed message, the second time got failed message again without work, it says status read failed (too many links)
Click to expand...
Click to collapse
Did you literally flash everything to get the GE edition as per another thread on the conversion and also did you flash the 4.3 GE hboot?

I flash the zip of the rooted GE 4.3 the same way you told me to do before.
I follow this guide : http://forum.xda-developers.com/showthread.php?t=2358781

RockLee91 said:
I flash the zip of the rooted GE 4.3 the same way you told me to do before
Click to expand...
Click to collapse
can you run fastboot getvar all and post the output here?

INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: *************
INFOimei: *************
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3826mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.062s

Probably a good idea to remove your IMEI and SERIAL number from your post but anyway...
Try just flashing the stock rom from this thread using CWM or TWRP and then flash the stock recovery back after.
http://forum.xda-developers.com/showthread.php?t=2224752

Done, remove from quote top pls XD

daleski75 said:
Probably a good idea to remove your IMEI and SERIAL number from your post but anyway...
Try just flashing the stock rom from this thread using CWM or TWRP and then flash the stock recovery back after.
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
how can i get custom recovery on GE 4.3?

RockLee91 said:
how can i get custom recovery on GE 4.3?
Click to expand...
Click to collapse
Flash a custom recovery as normal ie fastboot flash recovery openrecovery.img etc

i have flashed the rom that you linked me but now the phone stuck on boot screen :crying:
any advice?
SOLVED: i've flashed another rom and now work like a charm i flashed android revolution hd 12.1 ^^ tnx for all the support you saved me!

HELP! HTC One will not flash RUU. Stuck on fastboot flash zip ruu.zip

I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???

Kenmaster828 said:
I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???
Click to expand...
Click to collapse
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.

nkk71 said:
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.
Click to expand...
Click to collapse
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version

Kenmaster828 said:
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version
Click to expand...
Click to collapse
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.

herwegan said:
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.
Click to expand...
Click to collapse
So I basically screwed myself when I reverted back to S-ON.

Kenmaster828 said:
So I basically screwed myself when I reverted back to S-ON.
Click to expand...
Click to collapse
Are you still on hboot 1.44? Then get S-Off again.

nkk71 said:
Are you still on hboot 1.44? Then get S-Off again.
Click to expand...
Click to collapse
I just got back on S-OFF. I am a happy camper

Kenmaster828 said:
I just got back on S-OFF. I am a happy camper
Click to expand...
Click to collapse
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.

nkk71 said:
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.
Click to expand...
Click to collapse
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.

Kenmaster828 said:
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.
Click to expand...
Click to collapse
Don't know "QBKING77's tutorial", but you can use pretty much any RUU now that you're S-Off. Downgrading is possible thanks to S-Off. Just stick to SPRINT RUUs, ROMs etc, as I understand they (and possibly Verizon) are different from other carriers.
And remember to keep S-Off, that will always allow you to downgrade if needed or flash firmware, etc.

How do you get S-Off after custom ROM
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34NW******
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4279mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.554s
I have tried the 502.12 and 502.15 "cingular" RUU (ZiIPs and EXEs), to no avail.
Can't revone (get "error code = 1" [not -1]), so I can't seem to get S-Off. Moonshine fails in test 2.1 (between reboots basically).
Any ideas?

Have you tried to install viper or ARHD and get S-off again?

michaeljthom said:
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
Any ideas?
Click to expand...
Click to collapse
Check the date in bootloader; if it's before June 2013, then revone should work. If the date is June or after then it's a patched hboot 1.44, and you need to downgrade before running revone, check this thread it has the downgrade instruction (T-Mob and ATT only): http://forum.xda-developers.com/showthread.php?t=2431515
and remember you need to be on a Sense 5, 4.1.2 based ROM.

nkk71 said:
and remember you need to be on a Sense 5, 4.1.2 based ROM.
Click to expand...
Click to collapse
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?

michaeljthom said:
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?
Click to expand...
Click to collapse
1- first thing, did you check the bootloader date? if it's the patched 1.44 (ie June 2013 or after) then if you do the downgrade (only for ATT and T-Mobile), I think that also includes the ROM.
2- and just to get a Sense 5/4.1.2 based ROM on your phone, you just flash it through custom recovery (any custom or stock ROM will do), if you can't find one I'll PM you a link to one that worked for me, but first check point 1

Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.

michaeljthom said:
Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.
Click to expand...
Click to collapse
I just took a quick look at the ATT downgrade guide and the first thing it asks (actually point 3) is to install a nandroid backup, that will put the correct Sense 5 ROM on your phone, no need to go look for one.
Hit the thanks button if I've helped

Score. Thanks so much. I think finding a nandroid backup (and then switching to cwm from twrp) was really the key here. But I'm now all fully restored to stock. Thanks again!!

Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed

LMH1998 said:
Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed
Click to expand...
Click to collapse
same problem . Please help!

Is Using GURU Reset Roms same as USING RUU?

Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?

Bocko92 said:
Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (excluding IMEI and s/n)

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 4001mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0

Bocko92 said:
Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?
Click to expand...
Click to collapse
The Guru reset is not as complete as a true RUU but it is very close, close enough in fact you can take OTA after using it. and after the OTA your are indeed completely stock. The guru reset doesn't update your firmware so yeah it's important that you get the correct Reset to match your current firmware.
if this is the one you used you should be good to go
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/

Bocko92 said:
version: 0.5
version-bootloader: 1.55.0000
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__102
gencheckpt: 0
Click to expand...
Click to collapse
since you dont care about warranty, just go ahead and install http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ using CWM or TWRP
if you want to receive & install OTA updates (when they become available), select "stock recovery" in installer.

nkk71 said:
since you dont care about warranty, just go ahead and install http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ using CWM or TWRP
if you want to receive & install OTA updates (when they become available), select "stock recovery" in installer.
Click to expand...
Click to collapse
Thanks, i did install it, but i notice some lag when switching between normal notifications and toggles in the notification shade - is it normal ?
P.S I'm a new One user.
Wiped everything when installed the zip. Was just wondering if it cleans everything properly so the normal perfromance of the phone is achieved or i must play with the RUU.exe .. and S-OFF. I'd like to be completely stock since im sick of modding my phone .. and once i S-OFF i dont know how to S-ON.

Bocko92 said:
Thanks, i did install it, but i notice some lag when switching between normal notifications and toggles in the notification shade - is it normal ?
P.S I'm a new One user.
Wiped everything when installed the zip. Was just wondering if it cleans everything properly so the normal perfromance of the phone is achieved or i must play with the RUU.exe .. and S-OFF. I'd like to be completely stock since im sick of modding my phone .. and once i S-OFF i dont know how to S-ON.
Click to expand...
Click to collapse
1- if you ever decide to go S-Off then DO NOT GO BACK S-ON
2- you are now completely stock (your firmware is 3.62.401.1, and since you dont have s-off it's the official one), and the Guru Reset has put your ROM back to 100% stock -> so performance, etc. is 100% stock
3- you won't get it any different with an RUU (performance and experience)
4- you could try a factory reset, to clean everything and set up your phone from the beginning

Do you think it's worth it to go through the trouble of S-OFF-ing just to use the RUU, or the phone's just fine with the .zip. I'm kinda of perfectionist - i want to do it right and never bother again with flashing and modding?
Thanks again!

Bocko92 said:
Do you think it's worth it to go through the trouble of S-OFF-ing just to use the RUU, or the phone's just fine with the .zip. I'm kinda of perfectionist - i want to do it right and never bother again with flashing and modding?
Thanks again!
Click to expand...
Click to collapse
you're phone is 100% stock right now; the only advantages of going to S-Off and (eventually) run an RUU is if you need your bootloader to say "LOCKED" as opposed to UNLOCKED/RELOCKED.

It still says that my device's been tempered with, is that normal?

Bocko92 said:
It still says that my device's been tempered with, is that normal?
Click to expand...
Click to collapse
That's a so-so question, in theory it should go away once stock recovery has been installed, but in practice i've seen it sometimes go away and sometimes not, even when 100% stock.

Bocko92 said:
It still says that my device's been tempered with, is that normal?
Click to expand...
Click to collapse
nkk71 said:
That's a so-so question, in theory it should go away once stock recovery has been installed, but in practice i've seen it sometimes go away and sometimes not, even when 100% stock.
Click to expand...
Click to collapse
The Tampered and unlock/relock can be removed it you use nkk71 full Superguide for returning to stock >> http://forum.xda-developers.com/showthread.php?t=2541082
but it's a lot of work just to remove some red text on a screen you rarely ever see

If i want to use RUU do i have to first flash hboot 1.44 ? wont it break something with my firmware version?

Bocko92 said:
If i want to use RUU do i have to first flash hboot 1.44 ? wont it break something with my firmware version?
Click to expand...
Click to collapse
no it won't break anything in firmware, it will just downgrade hboot to allow RUU to work and "fastboot boot <name of recovery>.img" to work.
but if you're on Win8 / 8.1 that's gonna be an issue cause it will likely break fastboot & adb. better to use Win7 WinXP or even Ubuntu Live USB if you can't get your hands on Win7 or XP
EDIT: remember you have to be S-OFF !!!

I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?

Bocko92 said:
I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?
Click to expand...
Click to collapse
yeah, you're (very likely) going to have issues with win 8.1, better to get Win7 or an Ubuntu Live USB
do you have a win7 pc around somewhere handy? (cause it's not worth installing, better to "Try Ubuntu" Live USB)

Bocko92 said:
I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?
Click to expand...
Click to collapse
yes it the combination of win 8.1 and hboot 1.44.000 that will give you the problem

nkk71 said:
yeah, you're (very likely) going to have issues with win 8.1, better to get Win7 or an Ubuntu Live USB
do you have a win7 pc around somewhere handy? (cause it's not worth installing, better to "Try Ubuntu" Live USB)
Click to expand...
Click to collapse
Okay, im on windows 7, im S-OFF and my bootloader is unlocked but when i try to flash it it fails -
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.733s

Bocko92 said:
Okay, im on windows 7, im S-OFF and my bootloader is unlocked but when i try to flash it it fails -
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.733s
Click to expand...
Click to collapse
looks like android-info.txt is actually a little messed up in there
Code:
cidnum: HTC__E11cidnum: HTC__102
^^ line break missing.
, so just temporarily change CID to 11111111
fastboot oem writecid 11111111 <- 8 ones
then do the downgrade hboot, then restore cid
fastboot oem writecid HTC__102
and continue.

CANNOT THANK YOU ENOUGH KIND SIR ! I'm finally back to stock and locked. Really dude, you saved me there .. much love.
P.S No homo

[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

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!