[How-to][ruu] flash Rom.zip to factory

iTeRRoRiz3

New member
Dec 13, 2012
4
2
0
i was getting this C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
then did the encripted file and now im getting
<remote: 43 main version check fail.
i think i flashed the international revolution ROM and my image version now is 1.31.651.2

I am getting the same issue I need help, I just bought the phone 4 days ago but I did not accidentally flash a bad rom or anything I am just trying to get back to factory and have tried running the exe and using cmd prompt but I get the same check fail. Also, I have had s-on the whole time and obviously I already relocked my bootloader, so idk if it is possible to go back to stock with s-on first android phone since the first evo.
 
Last edited:

Noooblet

New member
Sep 30, 2013
2
0
0
still no dice

Im Locked, and On the Black HTC Ruu screen. I'm getting this message every time.

H:\Documents and Settings\BBCB\Desktop\FastBoot\adt bundle\adt-bundle-windows\sd
k\platform-tools>fastboot flash zip Sprint_HTC_One_m7wls_1.29.651.7_encrypted_RO
M.zip
sending 'zip' (1029700 KB)...
OKAY [ 40.453s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 142.719s
 

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
Im Locked, and On the Black HTC Ruu screen. I'm getting this message every time.

H:\Documents and Settings\BBCB\Desktop\FastBoot\adt bundle\adt-bundle-windows\sd
k\platform-tools>fastboot flash zip Sprint_HTC_One_m7wls_1.29.651.7_encrypted_RO
M.zip
sending 'zip' (1029700 KB)...
OKAY [ 40.453s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 142.719s
Looks to me like you are flashing an older RUU
 

erethangbagel

Member
Dec 21, 2012
35
1
0
I get this error

C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s

any idea?

thanks!
I'm getting this same error... now the phone is stuck on the black "HTC" screen. Does anybody know how I can fix this? I guess it was caused by me being on 1.31 and trying to flash 1.29.
 
Last edited:

koolerz1569

New member
Oct 6, 2010
2
0
0
Santa Rosa
This guy is a straight ****ing boss, just teamviewered and fixed everything back to normal out of the box in 30 minutes. Thanks for that I certainly would not have known how to trick the program like you did. Thanks a million bro.
Hi there. Getting the same error here too. Do you mind sharing how you got it to work?:confused:
 

Hunterprime

Member
Oct 3, 2013
5
0
0
So I have been tearing my hair out trying to get back to stock. I had installed cyanogen and decided that I wanted to go back to stock. That was about 3-4 weeks ago and all was looking good and I was running on stock or so I thought. OTA update downloaded on my phone and when it went to install I would just get dumped in fastboot saying <relocked> <tampered> <Security warnings>. During this point I was unable to boot into recovery, it would just dump back to fastboot.

I now have managed to get the device to not even boot. It hangs during the htc screen right after the sprint logo animation. I can still get into fast boot. Help?

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 1.00.20.0913_3
version-cpld: None
version-microp: None
version-main: 3.04.651.2
version-misc: PVT SHIP S-ON
serialno: FA34VS909402
imei: 990001466636149
meid: 99000146663614
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4300mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
 

cowkong

Member
Jun 6, 2012
17
2
0
What to do

Can you help out one more guy, Bigdaddy? I have newer RUUs that are about 100 MB each and have tried each with the OP's instructions but all I'm getting is:

(this is my attempt with an older RUU from July)
fastboot flash zip RUU.zip
sending 'zip' (1032712 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))

(this is one I downloaded directly from HTCdev.com today)
fastboot flash zip RUU2.zip
ERROR: could not clear input pipe; result -536870163< waiting for device >

I'm running out of options and I've been working on this for over a day. The internet is just full of too much information and if I could just get someone's personal assistance I would be truly grateful. I miss my only One.
 
Last edited:

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
Can you help out one more guy, Bigdaddy? I have newer RUUs that are about 100 MB each and have tried each with the OP's instructions but all I'm getting is:

(this is my attempt with an older RUU from July)
fastboot flash zip RUU.zip
sending 'zip' (1032712 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))

(this is one I downloaded directly from HTCdev.com today)
fastboot flash zip RUU2.zip
ERROR: could not clear input pipe; result -536870163< waiting for device >

I'm running out of options and I've been working on this for over a day. The internet is just full of too much information and if I could just get someone's personal assistance I would be truly grateful. I miss my only One.
I'm at work right now I'll message you when I get home :D

Sent from my HTCONE using xda app-developers app
 

jeepinwk

Member
Mar 1, 2012
5
2
0
For this quick how-to I will be using the file name Rom.zip as default for the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM-1.zip firmware download available from
O.M.J. here (use ENCRYPTED version)

http://forum.xda-developers.com/showthread.php?p=40712553

From fastboot you need to first re-lock your bootloader

fastboot oem lock

Once locked it will boot back into bootloader

fastboot oem rebootRUU

Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder

fastboot flash zip Rom.zip

This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)

Make sure device is still in ruu mode(black HTC screen). If not rerun

fastboot oem rebootRUU

now simply reflash the rom.zip

fastboot flash zip Rom.zip

Let it run and it should finish this time

It will reboot to a fully stock build.

just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.


The most common error is typically

(Error 155)
You did not re lock your bootloader first
-go relock and flash again
Thank you so much for this. Been trying for 3 days to get back to stock and something about the way you worded all this clicked. Really saved me. Was about to throw phone into toilet and turn in under equip protection plan. Thanks.
 
Jan 17, 2010
30
0
0
Firmware is the stuff you can't fastboot flash like radios and other partitions that deal directly with the hardware. S-On people have to RUU or OTA to get those updates with signed zip files. Which means they also get the new bootloader, kernel, etc. which they may or may not want if they are on a custom ROM.

Since you are on 1.29.651.10, the RUU executable file (and even just the ROM zip) will work whether you are S-On or S-Off, because they are signed. The RUU is for that same version and just brings you back to stock.

It sounds like the first time you ran it you got error 155 which is reminding you that you did not lock your bootloader. If you then locked your bootloader and re-ran the RUU to success, you are now on version 1.29.651.10 stock, just like you got it from the store. There is nothing more to do here. You have all the ROM software and firmware compatible with this version.

You may then notice that you are getting a system notification informing you there is a newer version 1.31.651.2 available as an OTA (over the air update). If you have no plans to go S-Off, you can take the update and it will give you the new software and firmware for that version. There is currently no RUU for that version.

However, there is no going back to an earlier version once this is done if you are S-On. Additionally, if you decide you want S-Off later, revone and moonshine do not work on that version. Both will work on version 1.29.651.10, but apparently only if your hboot is version 1.44 and dated May 8. If you have hboot 1.44 June 21, people have had problems getting S-Off.
this is my dilemma as well, i have the 1.31.651.2 and i cant go back to the old one 1.29.651.10 , i tried the RUU thru windows and it will tell me that its not the same. I hope you can help me about this.

---------- Post added at 04:47 AM ---------- Previous post was at 04:42 AM ----------

I'm getting this same error... now the phone is stuck on the black "HTC" screen. Does anybody know how I can fix this? I guess it was caused by me being on 1.31 and trying to flash 1.29.
hi there, were you able to find a fix for this?
 

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
this is my dilemma as well, i have the 1.31.651.2 and i cant go back to the old one 1.29.651.10 , i tried the RUU thru windows and it will tell me that its not the same. I hope you can help me about this.

---------- Post added at 04:47 AM ---------- Previous post was at 04:42 AM ----------



hi there, were you able to find a fix for this?
This will get you fixed up :D
 
  • Like
Reactions: ufuruk