Database Develop

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!

[Q] revone failed (error code = 1)

I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!

pirateye said:
I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!
Click to expand...
Click to collapse
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.

Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
It worked! Thanks a lot! :highfive:

Thanks for this I was having the same problem I'm downloading the 4.2.2 rom and doing the backup. I hope this works for me too

Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
Finally.. after hours of Googling an answer! Thanks so much.

Thanks a LOT!!!! I was really hating my device, didn't know what the problem is.
I will try it, finally found an answer...

Thanks...will try your method now.

Thanks!
Thank you very much for the help in this thread

i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5

[email protected] said:
i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5
Click to expand...
Click to collapse
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.

the firewater also didnt work..
and nor Rumrunner

[email protected] said:
the firewater also didnt work..
and nor Rumrunner
Click to expand...
Click to collapse
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output

nkk71 said:
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output
Click to expand...
Click to collapse
-> yeah i know what the S-ON and S-OFF stands for.
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA.
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img
-> i am using 4.3.android. sw version : 3.05.651.5
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off.
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)..........................
pouring (2)...........................
pouring (3)..........................
pouring (4)...........................
pouring (5)..........................
pouring (6)...........................
pouring (7)..........................
pouring (8)...........................
Wait 30 seconds, power on device, pray, run rumrunner again.
Press ENTER to exit
executed the above exe for 3 times but same ans...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35XXXXxxX164
(bootloader) imei: 9XXXXXXXXXXX499
(bootloader) meid: 99XXXXXXXXXX49
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.133s

[email protected] said:
-> yeah i know what the S-ON and S-OFF stands for. okay, fair enough
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA. interesting
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img I'm not familiar with Mr. Kapil Sir, or his radio flashing techniques... then again on the M7_U/UL you can flash radios without the need to be s-off, and I would assume the same for all M7 models
-> i am using 4.3.android. sw version : 3.05.651.5 not what i asked
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off. also not what i asked
Click to expand...
Click to collapse
okay, point taken Sir.

Sorry for not getting what u asked but tried my best to answer the Q's asked.
anyways Sorry again.
so what next..?
---------- Post added at 02:56 AM ---------- Previous post was at 02:50 AM ----------
Was trying to Flash a radio...
Please Check,
hope u might get the way out...
WHile S-ON
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.342s
while S-OFF got with firewater worked and helped to S-OFF
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.055s]
finished. total time: 0.056s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.427s
for sure it works after S-OFF .
but the minor mistake can led for failure and did a big mistake - a dump i m...
ok will correct.... hope u too have missed the correction..
but the think was
fastboot flash zip CT3G_radio.zip
where as i was writing
fastboot flash radio CT3G_radio.zip
so please dont sleep like me and do thinks..
sorry for diverting... but a good lesson for silly mistakes...

nkk71 said:
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.
Click to expand...
Click to collapse
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.

globalgpj said:
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.
Click to expand...
Click to collapse
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running

nkk71 said:
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running
Click to expand...
Click to collapse
Hi Nkk71,
I got an even bigger problem now.
I was planning on returning my M7 to get the dreaded purple haze camera fixed. Got the GRA from the company already.
I tried to get the device to S-OFF after I got it S-On as the TAMPERED writing appeared again.
I tried revone and it always failed on line 6 ./revone -s 0 -u.
I went to try firewater and it said it couldn't do it and said to reboot.
As i rebooted into a stock rom, I went to Settings, got and error message and it asked if I wanted to send the error to HTC, I clicked no, then it went into a reboot and has been stuck on a WHITE boot screen (HTC One) and won't do anything.
I can't shut it down (tried holding down the power button 2 min+), I can boot into bootloader, I can't do anything either if I put my usb cable in either adb or fastboot, it is really FROZEN !!!!
Have I bricked my phone
I even tried to install the RUU but it failed as it needs to have a working USB connection.
It seems that all I can do is wait til the battery dies naturally.
Any advice ?
After 20 minutes still frozen boot screen. I can see the amber light on behind the speaker screen.
-------------------------------------------------------------------------
***TAMPERED***
UNLOCKED
S-ON
CID - HTC__001
H-Boot 1.44
ROM 4.1.2 (stock)
I'm running this stock ROM, RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed
and have TWRP installed.

globalgpj said:
Hi Nkk71,
I got an even bigger problem now.
Any advice ?
Click to expand...
Click to collapse
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Thanks a million !!! It worked.. I heard that before, but forgot all about it. You don't hear much about that trick these days.
Yeah , no brick
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.049s
-------------------
Should I try the Moonshine S-Off software to try and S-Off the device ?
http://forum.xda-developers.com/showthread.php?t=2291087

HTC One (M7) stuck in bootloader (Tampered, Relock, S-ON) - Please help!!

Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!

HunterT said:
Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!
Click to expand...
Click to collapse
your screwed unless you can get s-off back ... never go s-on with tampered / relocked bootloader

For real? I'm done for?
clsA said:
your screwed unless you can get s-off back ... never go s-on with tampered / relocked bootloader
Click to expand...
Click to collapse
Are you serious? I followed this video and in his video his phone goes to LOCKED, mine never went to LOCKED it went to RELOCKED so I just continued with the tutorial and turned S-ON which I guess was a big mistake because then when I restarted the TAMPERED MESSAGE came up.
I was following this thread to lock it.
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
When I did ./revone -l and checked the bootloader it said RELOCKED not LOCKED

HunterT said:
Are you serious? I followed this video and in his video his phone goes to LOCKED, mine never went to LOCKED it went to RELOCKED so I just continued with the tutorial and turned S-ON which I guess was a big mistake because then when I restarted the TAMPERED MESSAGE came up.
I was following this thread to lock it.
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
When I did ./revone -l and checked the bootloader it said RELOCKED not LOCKED
Click to expand...
Click to collapse
check @nkk71 SuperGuide here >>
http://forum.xda-developers.com/showthread.php?t=2541082

HunterT said:
Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!
Click to expand...
Click to collapse
Unlock bootloader again
install TWRP
install Custom Rom
install custom kernel
make it S Off
Remove Tempered use LINK
Run RUU according to your CID & MID and your Need

Edit: Never mind :/
Sent from my HTC One using XDA Free mobile app

yatindroid said:
Unlock bootloader again
install TWRP
install Custom Rom
install custom kernel
make it S Off
Remove Tempered use LINK
Run RUU according to your CID & MID and your Need
Click to expand...
Click to collapse
he's Verizon ... he has to be s-off to unlock the bootloader

So not chance I am getting out of this one?
clsA said:
he's Verizon ... he has to be s-off to unlock the bootloader
Click to expand...
Click to collapse
There are no RUU's out there that will work with S-ON?

HunterT said:
There are no RUU's out there that will work with S-ON?
Click to expand...
Click to collapse
RUU's
http://bit.ly/vzwone-15
S-off RUU (decrypted)
http://flyhalf205.com/?dir=RUU/m7vzw
http://forum.xda-developers.com/showthread.php?t=2765784
http://forum.xda-developers.com/showthread.php?t=2764109
That pretty much covers all your options at this point

I downloaded the for one on your list
clsA said:
RUU's
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
I downloaded the first one on your list and used fastboot oem rebootRUU
Then I did fastboot flash zip rom.zip
It seems to have gotten passed the signature check but then when parsing I got a too many links error.
(bootloader) adopting the signature contained in this images...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
(bootloader) FAILED (status read failed (Too many links))
seems like the closest I got to getting it working actually.
any ideas?

HunterT said:
(bootloader) adopting the signature contained in this images...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
seems like the closest I got to getting it working actually.
any ideas?
Click to expand...
Click to collapse
Android_info fail check cid mid software no. match ?
from HTC One

HunterT said:
I downloaded the first one on your list and used fastboot oem rebootRUU
Then I did fastboot flash zip rom.zip
It seems to have gotten passed the signature check but then when parsing I got a too many links error.
(bootloader) adopting the signature contained in this images...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
(bootloader) FAILED (status read failed (Too many links))
seems like the closest I got to getting it working actually.
any ideas?
Click to expand...
Click to collapse
Android_info fail could also mean the RUU is older than your current software
you can't flash older RUU without s-off

Way out
clsA said:
Android_info fail could also mean the RUU is older than your current software
you can't flash older RUU without s-off
Click to expand...
Click to collapse
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?

HunterT said:
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?
Click to expand...
Click to collapse
hboot version ?
OS / software / version main ?
Or gatvar all without imei & serial number
from HTC One

I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34JW902721
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4058mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

HunterT said:
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?
Click to expand...
Click to collapse
hboot is 1.55 so use rumrunner or firewater & get S Off you every problem will gone

sandykalugdan said:
I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
Click to expand...
Click to collapse
you don't have the same problem as the OP, he's on Verizon, which means he can't use HTCdev to unlock, so he's in a seriously bad situation, what problem do you have?

Sorry for saying I have same problem.
I guess we are in the same situation, stuck in bootloader, tampered, relocked, s-on but I using a HTC One International version. It was running with cyanogenmod 11 and I decided to go back to stock and I have this problem.

sandykalugdan said:
Sorry for saying I have same problem.
I guess we are in the same situation, stuck in bootloader, tampered, relocked, s-on but I using a HTC One International version. It was running with cyanogenmod 11 and I decided to go back to stock and I have this problem.
Click to expand...
Click to collapse
No need to apologize, you may be in a similar situation, but the OP has a real problem because he can't unlock his bootloader; in your case:
* just go to HTCdev, get a new unlocktocken,
* unlock bootloader again
* flash back custom recovery
* install ROM

sandykalugdan said:
I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
Click to expand...
Click to collapse
The OP has a Verizon phone with locked bootloader and s-on. How is you situation alike?
Whoops little late
Sent from my HTC One_M8 using Tapatalk 4

[Q] Can't S-ON?

After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!

Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.

Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.

nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.

Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)

nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?

Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.

nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.

Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware

nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.

Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe

nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
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: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.

Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
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: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.

nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-

[Solved] - Returning to Stock with hboot 1.57.0000?

Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
*** Tampered ***
**** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
Radio-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048mb
Click to expand...
Click to collapse
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Edit: Solved this by following alray's advice to use nkk71's superguide: http://forum.xda-developers.com/showthread.php?t=2541082

WastedJoker said:
Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Click to expand...
Click to collapse
you first need to achieve s-off and then follow nkk71's guide to return stock (link in my signature)

I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.

WastedJoker said:
I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.
Click to expand...
Click to collapse
you can use a linux live usb (instructions are in the FAQ section of my guide)
how were you able to do all the other steps with Win8.1??; if you were following my guide the hboot downgrade would only be one of the first steps.

I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.

WastedJoker said:
I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.
Click to expand...
Click to collapse
depending on which method you are using, once hboot is downgraded to 1.44, that would only be the first "fastboot flash zip ruu.zip", the second one also needs to be completed
I'm not sure at what stage and method you are at, but going s-on sounds like a very bad idea at the moment

Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?

WastedJoker said:
Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?
Click to expand...
Click to collapse
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)

nkk71 said:
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)
Click to expand...
Click to collapse
Your way makes a lot of sense! I'll get the RUU from your guide links

WastedJoker said:
Your way makes a lot of sense! I'll get the RUU from your guide links
Click to expand...
Click to collapse
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this

nkk71 said:
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this
Click to expand...
Click to collapse
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)

WastedJoker said:
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)
Click to expand...
Click to collapse
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068

nkk71 said:
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068
Click to expand...
Click to collapse
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?

WastedJoker said:
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?
Click to expand...
Click to collapse
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock

nkk71 said:
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock
Click to expand...
Click to collapse
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s
I retried the unlocking and it worked this time.
Weird.

WastedJoker said:
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s
Click to expand...
Click to collapse
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable

nkk71 said:
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable
Click to expand...
Click to collapse
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!

WastedJoker said:
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!
Click to expand...
Click to collapse
Ah good luck then, cause I'm getting some bad looks here, texting right now

nkk71 said:
Ah good luck then, cause I'm getting some bad looks here, texting right now
Click to expand...
Click to collapse
All done, thanks again

WastedJoker said:
All done, thanks again
Click to expand...
Click to collapse
Nice :laugh:
could you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title