Database Develop

[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

Help getting back to stock!

Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR

Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
Click to expand...
Click to collapse
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app

bored_stupid said:
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Relocked
hboot 1.44
S-On
Didn't change cid or modelid
Latest Venom Rom was on it..

This is what I get trying installing RUU I downloaded:
ERROR [140]: BOOTLOADER VERSION ERROR

Rolando88 said:
Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR
Click to expand...
Click to collapse
that RUU is no good in any case, you need to use the 1.28.401.7 version (provided you meet the requirements, which can only be checked using the output of "fastboot getvar all")
and with S-On, your phone will only show RELOCKED not LOCKED, so the buyer will know that you had it unlocked at one point.

Post a fastboot getvar all please
Sent from my Nexus 7 using XDA Premium HD app

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW909481
(bootloader) imei: *************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3879mV
(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.042s

Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app

bored_stupid said:
Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.

Deleted

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
You need to unlock your bootloader again. Flash recovery and then s-off follow this guide
http://www.htc1guru.com/guides/get-s-off/
Then follow the guides to return to stock.
Sent from my HTC One using XDA Premium HD app

gartner83 said:
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.
Click to expand...
Click to collapse
I got this error message when I tried to flash
RUU Zip M7 UL JB 50 HTC Europe 1.29.401.16 R Radio 4A.14.3250.13 10.33.1150.01 Release 318486 Signed 2 4 Decrypted

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.

danlat1415 said:
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.
Click to expand...
Click to collapse
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.

gartner83 said:
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.
Click to expand...
Click to collapse
You can even leave leave the phone as s-off.
Won't be an issue, still covered by HTC warranty. They only care about boot loader status.

I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44

Rolando88 said:
I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44
Click to expand...
Click to collapse
what ROM are you on?
Recommend this one for revone: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
otherwise try http://firewater-soff.com/

ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!

Rolando88 said:
ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!
Click to expand...
Click to collapse
This is normal, it's due to s-off.
Sent from my HTC One using Tapatalk

[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

Display mesed up.

Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
C:\sdk tools\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
C:\sdk tools\sdk-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.051s
C:\sdk tools\sdk-tools>fastboot flash zip aman.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.125s]
finished. total time: 2.375s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk tools\sdk-tools>fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?

General Al Capo said:
Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?
Click to expand...
Click to collapse
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
Click to expand...
Click to collapse
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery

clsA said:
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery
Click to expand...
Click to collapse
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
your phone was Google play edition ... I hope you did not relock the bootloader, their is no way to unlock a bootloader on the GPe
the fastboot flash zip aman.zip may have been the fatal mistake. If you can not flash another hboot over it your screwed as far as I can tell.
Maybe @alray or @Danny201281 or @nkk71 can help you

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZ...ew?usp=sharing.
Click to expand...
Click to collapse
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.

alray said:
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.
Click to expand...
Click to collapse
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.

General Al Capo said:
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.
Click to expand...
Click to collapse
Uninstall HTC Sync leave the driver
What happened to the Google play RUU.zip I linked you too?
Your not ready to flash the Developer RUU yet.
Get the phone back working with the RUU I linked first.
I use Windows 8.1 every day it only affects HTC One with hboot 1.44
You have hboot 1.54 it should work fine

clsA said:
You have hboot 1.54 it should work fine
Click to expand...
Click to collapse
Not after he flashed the modded hboot. He is now on Hboot 1.43 so he will need win 7

The problem is everytime i write fastboot oem rebootRUU the device restarts.

General Al Capo said:
The problem is everytime i write fastboot oem rebootRUU the device restarts.
Click to expand...
Click to collapse
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).

alray said:
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).
Click to expand...
Click to collapse
I did that.At the end it says error-please get the correct rom utility.

General Al Capo said:
I did that.At the end it says error-please get the correct rom utility.
Click to expand...
Click to collapse
still not answered my crucial question from post #5 :
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
Click to expand...
Click to collapse
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.

Andriod info of RUU
modelid: PN0712000
cidnum: BS_US001
cidnum: BS_US002
mainver: 7.17.1540.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
getvar all
C:\abc\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.130s
C:\abc\sdk-tools>
Click to expand...
Click to collapse
alray said:
still not answered my crucial question from post #5 :
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.
Click to expand...
Click to collapse
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.

General Al Capo said:
Andriod info of RUU
getvar all
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.
Click to expand...
Click to collapse
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?

alray said:
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?
Click to expand...
Click to collapse
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.

General Al Capo said:
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.
Click to expand...
Click to collapse
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.

alray said:
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.
Click to expand...
Click to collapse
Thanks for your help:good:.Will try this RUU after downloading it.

The RUU you gave me worked like a charm.Thank you for your assistance.

General Al Capo said:
The RUU you gave me worked like a charm.Thank you for your assistance.
Click to expand...
Click to collapse
glad to know everything is fine now. Don't forget if you want to convert your device again to another version, use the method clsA posted at first page. Very much easier and safer. The whole procedure is now done using a GUI (aroma installer) from a custom recovery.