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!

Unable to unlock relocked hboot

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Which RUU on SuperCID 11111111?

Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks

Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.

Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
wrong forum... ask in Q & A :good:

passion8059 said:
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.
Click to expand...
Click to collapse
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?

Thread Moved to Q&A, Help & Troubleshooting forum.
As a future reference, all questions get posted in Q&A, NOT development. Even if you have a development related question in future, it still belongs in Q&A.
Regards,
- KidCarter93
Forum Moderator

Mr.Nieto said:
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?
Click to expand...
Click to collapse
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
your brightstar RUU failed because the MID mismatch
also post a fastboot getvar all without imei/sn

clsA said:
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
Click to expand...
Click to collapse
Here is the getvar all result:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.161.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ea0bccbd
hbootpreupdate: 11
gencheckpt: 0
I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM or HTC Stock ROM on my phone...

Mr.Nieto said:
Hi. I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM on my phone...
Click to expand...
Click to collapse
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654

clsA said:
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654
Click to expand...
Click to collapse
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?

Mr.Nieto said:
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?
Click to expand...
Click to collapse
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?

clsA said:
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?
Click to expand...
Click to collapse
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...

Mr.Nieto said:
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...
Click to expand...
Click to collapse
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined

clsA said:
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined
Click to expand...
Click to collapse
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?

Mr.Nieto said:
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?
Click to expand...
Click to collapse
probably because your s-on relocked and SuperCID
@SaHiLzZ @nkk71
is their anything he can do ?

clsA said:
probably because your s-on relocked and SuperCID
Click to expand...
Click to collapse
What can i do now?

Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device

SaHiLzZ said:
Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device
Click to expand...
Click to collapse
That worked, thanks! Now i try to install TWRP...

Hold on. WHAT is your final goal?
sent from my mobile device

Installing TWRP worked too! Very nice! Thanks!
Got a question... i am currently able to S-OFF and change CID...
What is required to install the RUU
RUU_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 to set the CID to a special One? And what is required too for that step? Is that possible?

SaHiLzZ said:
Hold on. WHAT is your final goal?
sent from my mobile device
Click to expand...
Click to collapse
My first goal is to install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I want a stock rom from HTC on my device... when that isnt possible i install the GPE Custom ROM

[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