• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] Can't restore stock rom on HTC one.

rosh88

Newbie
Aug 18, 2013
15
0
the corresponding RUU to my phone is a zip file and there are no .exe files in that zip file. On cmd via fastboot i type "fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail" in the end cmd. What will happen if i download a different RUU with the same baseband as my phone?
 
since you are posting in the ATT forum,i assume that you have an att device.

sounds like you are simply not flashing a proper zip file,wich must contain,among other things,an android info text document,and if you are still s on,it must pass an htc signiture check,and have a relocked bootloader,if the file contains images other than boot,system,or recovery.

the sigiture fail error is becasue you are trying to use a file that has been modified,and no longer passes the htc signiture check.


a .exe file can be found at the link in this thread:
http://androidforums.com/t-one-all-..._10-40-1150-04_release_326691_signed_2-a.html

i just checked it,its leading you to htc's site,where the most current .exe file is availble.

you can get the utility to run by starting it with the phone in fastboot,or RUU mode( fastboot oem rebootRUU ). again,the bootloader must be locked if youre s on.

you can extract rom .zip in this manner:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be renamed to PxxxIMG and flashed in hboot,from a FAT32 sd card


rom.zip can be flashed in this manner:
if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides :))

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

be aware that the newest ruu will break the ability to achieve s off,so id be hesitant to do that if all possible.

is your phone currently not working? you should be able to install a rom,or restore a backup. some more info on your situation may help us help you :)
 
Upvote 0
What will happen if i download a different RUU with the same baseband as my phone?
it probably will not flash. an ruu must pass signiture,CID,MID,hboot,and main version checks,among others for an s on device to allow the flash.

Hey guys, Im having some issues with my HTC one. I trying to restore my htc one back to stock and found a nandroid backup online that corresponds with my phones version...i have sdk tools like fastboot to run in cmd..but im having trouble flashing it...any ideas?
if you are using CW recovery,and need to restore a CW nandroid,you can push it to the proper location using ADB using the following: http://androidforums.com/internatio...card-if-your-phone-wont-boot.html#post5933877
 
Upvote 0
hey guys, Im a noob to the android world and please dont mind my stupid question...after alot of difficulties (bricking the htc one while flashing the google play edition rom) i managed to root my device and installed a custom rom...now I have to unroot it and flash the stock rom back before i send it to htc...how can i unroot it and flash a stock rom using cwm? thanks guys.
 
Upvote 0
Not with CWM. If you really want to unroot you need to relock the bootloader and use a ROM Update Utility (RUU) to reflash the stock firmware. That will also remove CWM, which you want to do if returning it to HTC.

You'll need to tell us what type of handset you have, whether it is branded or not, and is so what network, so that we can find the right RUU for your phone. Or can we just assume ATT? In which case Scotty linked it in post #2 above.

If you took a backup with CWM before rooting then restoring that would restore the unrooted ROM, but you'd still have a custom recovery installed. That's why we want the RUU.
 
  • Like
Reactions: rosh88 and scotty85
Upvote 0
It is unlocked and unbranded...but according to fastboot..its a rogers (Canada) device...1.29.631.17...which failed to load using fastboot and sideloading using adb :( and i thought i downloaded the right ruu but always getting "(remote: 24 parsing android-info fail)"...my S is on btw.
 
Upvote 0
It is unlocked and unbranded...but according to fastboot..its a rogers (Canada) device...1.29.631.17...which failed to load using fastboot and sideloading using adb :( and i thought i downloaded the right ruu but always getting "(remote: 24 parsing android-info fail)"...my S is on btw.

i addressed that in post #2 as well. you are not installing a correct file.

you are somewhat SOL,as there does not exist an ruu for your build. youll need to flash a stock rom,or restore a stock nandroid. from there you will need to install a stock recovery. from there you can do a factory reset,and hope with a stock recovery and boot image in place that your tampered badge goes away,but it may not.

youre also stuck with relocked while your s on.

last and not least,ill move this to the international forum since you dont have an att device :)

hopefully you can find a user with that build that has captured an OTA package,from wich we can install the correct firmware.
 
Upvote 0
  • Like
Reactions: rosh88 and scotty85
Upvote 0
thanks alot guys, you are guys are amazing.

What do I use to restore the rogers nandroid? CWM would abort the installation after so many minutes, sideloading using adb would say error on cmd...fastboot flashing will result in the typical signature fail...

youll want to push the nandroid to the proper folder using the guide i linked above( http://androidforums.com/internatio...card-if-your-phone-wont-boot.html#post5933877 )

then simply use cwm to full wipe,and restore that nandroid :)

skimming back over things,i dont see wether your device is booting or not. if its booting into an OS,you alternately can simply plug into a PC,then drag and drop the nandroid into the proper cwm folder,rather than pushing with adb
 
Upvote 0
Ok, I have dragged and dropped the nandroid in the "backup" folder under the "clockwork mod" folder which was under internal storage in phone. Booted the phone into recovery, and chose "install zip from sd card" but the zip file isnt showing up, just the recent backup i made prior to booting it just now. ps: my phone is booting.
 
Upvote 0
Ok, I have dragged and dropped the nandroid in the "backup" folder under the "clockwork mod" folder which was under internal storage in phone. Booted the phone into recovery, and chose "install zip from sd card" but the zip file isnt showing up, just the recent backup i made prior to booting it just now. ps: my phone is booting.

If your phone is already android 4.2.2 the location of CWM/Backup is different than the one you see on the PC.
The PC looks under data/media/0/CWM/Backup
CWM looks for your backup under data/media/CWM/Backup
you can use a root explorer to move it to the correct location after you copied it to phone on a PC.
and you don't choose install zip you choose Restore after all the files are in the right place
 
  • Like
Reactions: scotty85
Upvote 0
alright so i downloaded a file explorer called root browser, and moved the ruu accordingly to "data/media/Clockwork mod/Backup"...entered recovery mode and chose back up and restore...and it still wasnt there :(

What RUU ?
you need this in the data/media/CWM/Backup folder -> M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 - Bugsy Lawson's Resource

it's a zip file unzip it and move the contains to the location above
Boot to recovery and choose restore
2013-06-03.23.51.18
 
  • Like
Reactions: rosh88
Upvote 0
I have the zip nandroid file in the location above, i extracted it in the same folder and clicked restore and got "md5 mismatch"

how did you extract it? are you left with a single folder named 2013-06-03.23.51.18 inside?

could be you changed something during the extraction/move process,or it could be a bad download. try re-downloading the nandroid and see what happens. i will download as well,and we can compare md5's of the zipped file and unzipped nandroid.

and what about the OTA update that was posted a few posts above...what do i do with that?
lets not get ahead of ourselves. well discuss that as soon as you are able to restore the rom. :)
 
Upvote 0
yep, so i load up cwm recovery----->backup and restore---->restore----> 2013-06-03.23.51.18---->"yes-restore"....trust me I have downloaded it numerous times back to back...didn't help at all

ok... lets double check your md5's

for the dowload zip folder i got:
2013-06-03.23.51.18.zip 1af173ca5f55c7501ef4089694f7f967


and if i check the folder inside after extracting the zip,i get these for the files inside:
2013-06-03.23.51.18\boot.img f887ed739e28ccfaf2a66c615bf6df4c
2013-06-03.23.51.18\cache.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\cache.ext4.tar.a 1713af66638c93a9b6baffa8cc7d10a8
2013-06-03.23.51.18\data.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\data.ext4.tar.a 8ab6e879b9d6dbef2ee8718bc8f5ad10
2013-06-03.23.51.18\nandroid.md5 4baa18c76a8b94b0aa56c61ef61d4f6f
2013-06-03.23.51.18\recovery.img 894bae8a3ff9b4932881a3310dc64780
2013-06-03.23.51.18\recovery.log 5942593492f76b34dfadeafa906c412a
2013-06-03.23.51.18\system.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\system.ext4.tar.a e0aa2f2f299d8c0db96816c874699573
2013-06-03.23.51.18\system.ext4.tar.b 7cabb6ab0dbabdc7b63416170dd27d16


wich match the provided list inside the folder(labled "nandroid")

im off to work atm,ill try and restore it on my phone and make sure we dont have the same issue. :)
 
Upvote 0
ok... lets double check your md5's

for the dowload zip folder i got:
2013-06-03.23.51.18.zip 1af173ca5f55c7501ef4089694f7f967


and if i check the folder inside after extracting the zip,i get these for the files inside:
2013-06-03.23.51.18\boot.img f887ed739e28ccfaf2a66c615bf6df4c
2013-06-03.23.51.18\cache.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\cache.ext4.tar.a 1713af66638c93a9b6baffa8cc7d10a8
2013-06-03.23.51.18\data.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\data.ext4.tar.a 8ab6e879b9d6dbef2ee8718bc8f5ad10
2013-06-03.23.51.18\nandroid.md5 4baa18c76a8b94b0aa56c61ef61d4f6f
2013-06-03.23.51.18\recovery.img 894bae8a3ff9b4932881a3310dc64780
2013-06-03.23.51.18\recovery.log 5942593492f76b34dfadeafa906c412a
2013-06-03.23.51.18\system.ext4.tar d41d8cd98f00b204e9800998ecf8427e
2013-06-03.23.51.18\system.ext4.tar.a e0aa2f2f299d8c0db96816c874699573
2013-06-03.23.51.18\system.ext4.tar.b 7cabb6ab0dbabdc7b63416170dd27d16


wich match the provided list inside the folder(labled "nandroid")

im off to work atm,ill try and restore it on my phone and make sure we dont have the same issue. :)

So I've got exactly what you have :S
 

Attachments

  • Screenshot_2013-08-28-10-36-56.jpg
    Screenshot_2013-08-28-10-36-56.jpg
    27.6 KB · Views: 211
Upvote 0
ahhh. now we are getting somewhere ;)

the md5sum is a way to verify the integrity of files that you flash,and you should NEVER flash something without first checking it to make sure it has not become corrupt. while most files will not cause unrecoverable damage,some can brick your device permantly and unrecoverably:)eek:) so checking the md5 is a very,very good habit to get into.

just google "free md5 summer" or something to that affect and install it on your PC.

you can check files on your phone with a market app called "scary aliens android file verifier" (scary alien's AFV)

first thing we should check is the md5 sum of the still zipped download. it should equal: 1af173ca5f55c7501ef4089694f7f967

the nandroid restored just fine on my phone,so there is something wrong with your download or process.

i personally would prefer that you unzip and check the files on the PC,rather than on your phone.

this is what i did:
-unzipped the download
-pluged in to the pc
-moved the 2013-06-03.23.51.18 folder to the internal storage
-used root explorer to move the folder to the location described by clsa
-booted to recovery
-backed up my current rom
-wipe data/factory reset
-restored nandroid using clsa's directions
 
  • Like
Reactions: rosh88
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones