[GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock

Search This thread

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
Major guide revision 8th February 2014
Minor update 2nd March 2014: added FAQ #8 as alternate to Guru Bootloader Reset, and also updated Post 3, 4 and 5 to reflect that

So after doing this quite a few times, I finally ended up writing a guide :cowboy:, so here goes:

A few extra notes:
* Please READ the guide, read the sections relevant to you once or twice to make yourself comfortable with the procedure, before you begin
* DO NOT mix up steps: 1 then 2 then 3, etc. NOT 2 then 3 then 1

* Mirrors for most files and common nandroids can be found in post #7

* You can disregard all the "Retired content" stuff, I just kept them for myself to remember previous release of the guide :eek:

* For a "visual" walk-through check post #8 which has a Case in Point example, with command prompt outputs and screenshots
* if you go from S-Off to S-On on hboot 1.55 it will most likely cause a "tamper detected - rebooting", and will come back with a TAMPERED bootloader

* The S-On part in the guide is strictly optional, and it's your decision, and should only be done as the last step (but before OTA to 3.xx).


-------------------------------------------------------------------------------------------------------------------------------------------
Operating System Notes
Windows 8.1 users please see FAQ #1, Windows 7 users please see FAQ #2, Mac users please FAQ #3, and Linux users please see FAQ #4

sorry for the jumping around, but I'm trying to keep the thread readable, so i don't want to put FAQ first
FAQs are in post #2

-------------------------------------------------------------------------------------------------------------------------------------------​


First you need to be S-Off, this will NOT work with S-On!!!
A) If you’re on hboot 1.44 use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
B) If you’re on hboot 1.54/1/55 try rumrunner to get S-Off: http://rumrunner.us/ and thread
C) you can use Sunshine (paid app $25) works on all M7s (and others): http://theroot.ninja/ and thread

Looks like http://firewater-soff.com/ is the most popular and successful method for most hboot/firmware/rom combinations at the moment, but nevertheless try all options! firewater is discontinued, even if you find the app, it still needs the developers' servers so it will not work.



Then, assess your current situation:

Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all

Code:
(bootloader) version: 0.5
[COLOR="Blue"][B](bootloader) version-bootloader: 1.54.0000  <---- your hboot version[/B][/COLOR]
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
[COLOR="Blue"][B](bootloader) version-misc: PVT SHIP S-OFF  <---- confirm S-Off[/B][/COLOR]
(bootloader) serialno: HTxxxxxxxxxx  <--- remove IMEI and serialno, if you are
(bootloader) imei: 35xxxxxxxxxxxxxx  <--- going to post it, dont need 2 see them
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
[COLOR="Blue"][B](bootloader) modelid: PN0710000  <---- your MID
(bootloader) cidnum: H3G__001  <---- your CID[/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(important parts highlighted in bold above)



Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/showthread.php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.

download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/showthread.php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8



Now check what options you have for your MID and CID, by visiting:
1) RUU.EXE (Windows7): http://www.htc1guru.com/downloads/ruu-file-downloads/
------> if you’ve found a RUU.EXE proceed to post 3
---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead


2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
------> if you’ve found a RUU.ZIP proceed to post 4
---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead


3) nandroid backup (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/stock-nandroid-downloads/
------> if you’ve found a CWM nandroid backup proceed to post 5
------> if you’ve found a TWRP nandroid backup proceed to post 6
some nandroids work for several CIDs, for example:
Code:
nandroid HTC__039 1.29.980.2: ro.aa.modelid=PN0714000
                              ro.aa.cidlist=OPTUS001,TELNZ001,VODAP021,HTC__039

nandroid O2___102 1.27.206.1: ro.aa.modelid=PN0710000
                              ro.aa.cidlist=O2___001,O2___102

nandroid VODAP102 1.29.161.7: ro.aa.modelid=PN0710000
                              ro.aa.cidlist=VODAP001,VODAP102,VODAPE17,VODAP405,
                                            VODAP304,VODAPD18,VODAP120,VODAP110


4) IF you haven’t found any of these, try searching and/or you may need to ask in the Q&A thread for someone to share.

4b) or change the phone to unbranded, easy enough with S-Off, just ask


-------------------------------------------------------------------------------------------------------------------------------------------
Revision history
24th November 2013:
Initial release.​
8th December 2013:
Post #3, update to CWM method to accommodate for different MID models (without the need to change MID).​
24th January 2014:
Post #7, added Case in Point example.​
8th February 2014:
Major rewrite
Revision history added
Post #1: updated (now retired) hboot 1.44 file, updated CWM recovery download, updated and added FAQ for different Operating Systems and not so FAQ
Post #2: updated for hboot 1.55+ RUU.EXE downgrade problems (retired from Post #1)
Post #2 and #3: changed from "fastboot boot CWM.img" to "fastboot flash recovery CWM.img" in order to avoid Win7 driver issues
Post #4 (CWM method): changed from RUU.EXE to RUU.ZIP method (fastboot flash zip ruu.zip) to accommodate different Operating Systems
Post #6: added to reflect retired methods
Post #7: updated to new method​
2nd March 2014:
Added FAQ #8 as alternate method to Guru Bootloader Reset​
23rd April 2014:
Moved FAQ to post #2, thanks @KidCarter93
29th December 2014:
Added FAQ #9 and AFH Mirrors in post #7​
21st March 2015:
Updated FAQs, updated S-OFF methods​
-------------------------------------------------------------------------------------------------------------------------------------------

Disclaimer:
I'm not responsible for anything going wrong with your phone!


credits:
@crushalot (for http://www.htc1guru.com and all his effort keeping it up to date)
@paulobrien (for the preloaded apps)
@Guich (for the collection of stock recoveries)
@S-trace (for originally discovering the location of the lock status flag)
@scotty1223 (for his ADB shell commands for untampered and locked)
(if I missed someone, I’m sorry, just PM me and I’ll add)

-------------------------------------------------------------------------------------------------------------------------------------------
If you found this guide useful, please press the THANKS button on the first post :).
-------------------------------------------------------------------------------------------------------------------------------------------
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
Frequently Asked Questions


FAQ:
1) Q: I'm using Windows 8.1 what should I worry about
A: when you downgrade to hboot 1.44, or it get's downgraded during an ruu, fastboot commands will no longer work and you will be stuck, so you need to use Win7 or Linux (continue reading FAQ)

EDIT: or you could try this [GUIDE] Fix Fastboot on Windows 8.1 (thanks @clsA)​


2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
dh4kjo.jpg


follow the below instructions to fix

Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways

for those who like a visual guide:

okay so I did a fastboot boot command, and as you can see it didnt install correct driver
28ioxf6.jpg



Open "Device Manager"
2ywxpp3.jpg



there's the culprit
312v6me.jpg



right click and Update Driver Software
2ivmu5k.jpg



select Browse my computer for driver software
357qek7.jpg



select Let me pick from a list of device drivers on my computer
2582flf.jpg



select Android USB Devices
143jar8.jpg



select My HTC ... (if you have more than one version, choose the latest)
axea9h.jpg



warning, select Yes
14lhelv.jpg



successful installation
21btc3d.jpg



now it looks better :)
zwx53s.jpg


and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx    recovery
-------------------------------------------------------------------------------------------------------------------------------------------


3) Q: I'm using a Mac what should I worry about
A: not much, you just can't run a Windows RUU.EXE (executable), and you probably need to use "./":
--> you'll need to use RUU.ZIP method instead
--> CWM guide also updated
----> depending on your setup, you may need to run adb and fastboot commands, with "./" as in "./adb ..." and "./fastboot ..."​


4) Q: I'm using Linux what should I worry about
A: not much, you just can't run a Windows RUU.EXE (executable), and some commands might require "sudo":
--> you'll need to use RUU.ZIP method instead
--> CWM guide also updated
----> adb seems to work just fine in any mode, but
----> fastboot may need su privileges, so you'll need to issue fastboot commands with "sudo fastboot ..."​


5) Q: How do I create a Linux Live USB

Windows users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
Mac users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx

Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
in case you're having problems setting up adb/fastboot on newer versions, use 12.04 http://releases.ubuntu.com/12.04/


Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB

No need to install, just use the "Try Ubuntu" option
20kxjt0.jpg


open a terminal
2u62uc1.jpg


and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader

in case you're having issues, please check @Danny201281's MiniGuide here for more information

you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
-------------------------------------------------------------------------------------------------------------------------------------------​

6) Q: fastboot is giving me "cannot load"
A: the filename is wrong​


7) Q: flashing 1.44 hboot gives me "FAILED (remote: 42 custom id check fail)"
A: your CID is missing in android-info.txt; the updated zip on my mega account should work, if it doesn't edit android-info.txt to include your CID using Notepad++, or temporarily change CID "fastboot oem writecid 11111111" <- 8 ones, flash hboot, and restore your original CID.​


8) Q: Guru Bootloader Reset just keeps freezing
A: Use alternate method:
credits to @scotty1223
[how to] remove your "tampered" banner
[how to] lock/unlock your bootloader without htcdev(s-off required)

I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                            ensure [B]root[/B] privileges
                            i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]


C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s

[I][SIZE="1"]Setting LOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit

C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
--> confirm that bootloader is untampered and LOCKED


9) Q: I "adb push" the backup files, but it doesn't show up in restore
A: on a few rare occasions, CWM recovery doesn't mount the data partition automatically, do "adb shell mount /data" and then try pushing the files again.​


10) Q: When I run the Windows RUU.EXE it just exits when I click next
The RUU executable needs the MS Visual C++ 2008 Redistributable Package (x86) package installed.​
-------------------------------------------------------------------------------------------------------------------------------------------

Not so FAQ (maybe):
1) Q: What is this MD5 people keep talking about
A: https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt

on Mac, Linux, and Android terminals it's already built in:
Mac: in terminal, just type md5 <name of file>
----> MD5 (<name of file>) = 12345678901234567890123456789012

Linux: in terminal, just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>

Android: in "adb shell", just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>


Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ or http://implbits.com/hashtab.aspx (available for Windows and Mac, credits to @Lizard for that one ;))
-------------------------------------------------------------------------------------------------------------------------------------------


2) Q: What can I flash (or not) with S-On/S-Off and a (re)locked/unlocked bootloader
A: This may help
2hqqz6e.jpg
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
RUU.EXE (Windows7 only)


If you’re on hboot above 1.44, then first thing is to downgrade that:
so download hboot 1.44: 1.29.401.12_hboot_1.44.zip 502 KB
..... MD5: E6AD52CB30F35D1EB870D09BD065BE62
this is originally from: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
but with modified android-info.txt to include additional CIDs
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
<---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44



Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
In bootloader/FASTBOOT USB, flash CWM recovery:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader


-> enter RECOVERY -> you should now be in CWM recovery.

Method 1: using adb commands, more reliable, but be careful with the dd commands!!
I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                            ensure [B]root[/B] privileges
                            i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s

[I][SIZE="1"]Setting LOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
and continue with below reboot command.
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/

in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
adb reboot bootloader

and confirm no TAMPERED and LOCKED status



Step 2: Run your RUU.EXE
Download your MID & CID compatible RUU.exe: http://www.htc1guru.com/downloads/ruu-file-downloads/

Run just like any Windows application.



Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55


All done. :victory: you can now take OTAs.
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
RUU.ZIP (Windows7, Mac, Linux)
for Mac users, please remember ./
for Linux users, please remember sudo



Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
In bootloader/FASTBOOT USB, flash CWM recovery:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader


-> enter RECOVERY -> you should now be in CWM recovery.

Method 1: using adb commands, more reliable, but be careful with the dd commands!!
I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                            ensure [B]root[/B] privileges
                            i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s

[I][SIZE="1"]Setting LOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
and continue with below reboot command.
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/

in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
adb reboot bootloader

and confirm no TAMPERED and LOCKED status



Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)

In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
<- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader



Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55

All done. :victory: you can now take OTAs.
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
CWM nandroid backup (Windows7, Mac, Linux)


First off, placeholders in the below guide:
CID: H3G__001 should be substituted with your CID, I’m using H3G__001 just as an example
nandroid backup: “2013-mm-dd.hh.mm.ss” has to be replaced by the real name of the nandroid backup folder



Step 1: go back to Sense 5 Stock (updated 6 February 2014 for different Operating Systems)
in bootloader/FASTBOOT USB, change your CID:
fastboot oem writecid HTC__001 (two underscores)
fastboot reboot-bootloader
-> and confirm CID is HTC__001

Download this: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

if your MID is not PN0710000
in order not to mess around with changing MID:
for PN0711000: set CID to HTC__J15, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/

for PN0712000: set CID to CWS__001, and download this RUU: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/

for PN0713000: set CID to T-MOB010, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-20-10-40-1150-04-release-324846-signed-zip/

for PN0714000: set CID to HTC__044, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/

rename the downloaded file to ruu.zip (careful about .zip.zip in Windows), then in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
<- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader

This will completely return you to 100% stock Sense 5, but European unbranded version (or whatever version the MID+CID ruu was made for).



Step 2: go back to H3G__001
fastboot oem writecid H3G__001 <- remember to replace this with YOUR CID
fastboot reboot-bootloader
-> and confirm CID is back to H3G__001



Step 3: restore nandroid
fastboot boot CWM.img

you should now be in CWM recovery; verify adb is working, by using:
adb devices
it should show your device serial number followed by "recovery" (if adb doesn't see your phone in Windows, please check FAQ #2 in first post, and fix drivers before continuing)

download this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/ <- this is just an example, remember to download the nandroid for YOUR version from here: http://www.htc1guru.com/downloads/stock-nandroid-downloads/

extract the zip on your PC, it will give you a folder called similar to "2013-mm-dd.hh.mm.ss" place it in your adb folder then push it:
adb push 2013-mm-dd.hh.mm.ss /data/media/clockworkmod/backup/2013-mm-dd.hh.mm.ss <- replace mm, dd etc. to what the download gave you

in recovery select RESTORE, it should show you the above backup, so select "2013-mm-dd.hh.mm.ss" and restore it.


You still need to get the preloaded stock apps (which get deleted when unlocking using HTCdec), so download this:

http://loadbalancing.modaco.com/download.php?file=one-1.28.401.7-preloaded-modaco-withoutmovie.zip (from this thread: http://forum.xda-developers.com/showthread.php?t=2200628)

adb push one-1.28.401.7-preloaded-modaco-withoutmovie.zip /data/media/

in recovery, select "install zip" -> "choose zip" -> and install the above file



Step 4: get back stock recovery
the above nandroid may or may not contain stock recovery, but I doubt it does, so get one from here (find one as close as possible to your version): http://forum.xda-developers.com/showthread.php?t=2463387
and rename it to stock_recovery.img (careful about .img.img in Windows)

now let's reboot to bootloader/FASTBOOT USB:
adb reboot bootloader
fastboot erase cache
fastboot flash recovery stock_recovery.img

fastboot erase cache



Step 5: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
In bootloader/FASTBOOT USB, boot to CWM recovery:
fastboot boot CWM.img

-> you should now be in CWM recovery.

Method 1: using adb commands, more reliable, but be careful with the dd commands!!
I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                            ensure [B]root[/B] privileges
                            i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s

[I][SIZE="1"]Setting LOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
and continue with below instructions.
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/

in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below instructions.

Since you're still in CWM, go ahead and:
-> "wipe cache"
-> "advanced" -> "wipe dalvik"
then
adb reboot bootloader

and confirm no TAMPERED and LOCKED status



Step 6: get your 1st OTA
finally (almost) to confirm everything is back to 100% stock, reboot your phone, and set up only basic stuff such as WiFi, check for software update and download & install the 1st one only! (make sure it's either another 1.xx or 2.xx, do not use a 3.xx update, if you intend on going S-On)
Since recovery is not exactly your version, you may need to reboot your phone manually if it doesnt by itself: the progress bar stopped somewhere in the middle -> press and hold POWER + VOLDOWN, when it reboots keep holding VOLDOWN to get back to stock recovery and let it finish its business; repeat if it gets stuck again

After finishing the OTA, boot up your ROM, and check you Settings->About to confirm your new version, then reboot to bootloader and do a fastboot getvar all, and confirm firmware and hboot are also updated



Step 7: do a factory reset
Go to Settings -> Backup & reset -> Reset phone (at the bottom select Erase all date) -> OK
to get rid of the nandroid and bootloader_reset from your internal storage



Step 8: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55


All done. :victory: you can now take any remaining OTAs.

Side note: why is this procedure so long you may ask, then take a look here for a brief explanation: http://forum.xda-developers.com/showpost.php?p=52430301&postcount=834
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
TWRP nandroid backup

Same as CWM nandroid backup in the above post

except in step 3 (and only in step 3), you need to use TWRP from here: http://forum.xda-developers.com/showthread.php?t=2173870

and change the location of the adb push command "/data/media/clockworkmod/backup/2013-mm-dd.hh.mm.ss" to what it's supposed to be for TWRP

not sure what it is right now, as I havent used TWRP, but I think it's something like "/data/media/twrp/backup/XXXXXXXXXXXX/" where XXXXXXXXXXX is your device's serial number.

I'm sure you can figure it out ;) or someone will come along and correct me :eek:
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
AndroidFileHost Mirrors:
HTC One M7_UL - modelid=PN0710000 - cidlist=HTC__001, HTC__E11, HTC__102, HTC__203, HTC__405, HTC__Y13, HTC__304, HTC__032, HTC__A07, HTC__J15, HTC__016
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
HTC One M7_U (non LTE) - modelid=PN0711000 - cidlist=HTC__001, HTC__J15, HTC__A48, HTC__M27
HTC One M7_U (non LTE) - modelid=PN0711000 - cidlist=HTC__044, HTC__038
HTC One M7_UL - modelid=PN0712000 - cidlist=CWS__001
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
HTC One M7_UL - modelid=PN0713000 - cidlist=T-MOB010
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
HTC One M7_UL - modelid=PN0710000, PN0714000 - cidlist=HTC__044
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
HTC One M7_UL - modelid=PN0710000 - cidlist=ORANG001
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
M7 CWM Nandroid Backup CID ORANG001 1.28.61.7 2013-04-22.zip
Code:
ro.aa.modelid=PN0710000
ro.aa.cidlist=ORANG001
ro.aa.romver=1.28.61.7
once extracted it will give you a folder "2013-04-22.13.54.52"
so the adb push command will be:
adb push 2013-04-22.13.54.52 /data/media/clockworkmod/backup/2013-04-22.13.54.52
stock recovery: stock_recovery_2.24.61.1.img

Note: you will first get a small "Software[/B} update" (don't confuse that with the actual System Update):
21mc5lj.jpg

before the actual OTA:
x6bk2p.jpg

once that is applied you are fully stock on 2.24.61.1

HTC One M7_UL - modelid=PN0710000 - cidlist=T-MOB101
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
M7 CWM Nandroid Backup CID T-MOB101 1.28.111.6 2013-03-29.zip
Code:
ro.aa.modelid=PN0710000
ro.aa.cidlist=T-MOB101
ro.aa.romver=1.28.111.6
once extracted it will give you a folder "2013-03-29.00.13.30"
so the adb push command will be:
adb push 2013-03-29.00.13.30 /data/media/clockworkmod/backup/2013-03-29.00.13.30
HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
M7 CWM Nandroid Backup CID O2__102 1.27.206.1 2013-03-30.zip
Code:
ro.aa.modelid=PN0710000
ro.aa.cidlist=O2___001,O2___102
ro.aa.romver=1.27.206.1
once extracted it will give you a folder "2013-03-11.17.58.27"
so the adb push command will be:
adb push 2013-03-11.17.58.27 /data/media/clockworkmod/backup/2013-03-11.17.58.27
stock recovery: recovery 1.29.206.11.img
HTC One M7_UL - modelid=PN0710000 - cidlist=H3G__001,H3G__106,H3G__G04,H3G__402
AndroidFileHost mirros:

For Windows 7: mini-sdk-1.0.31-windows.rar

Guru_Bootloader_Reset_1.0.zip
^^ I prefer the more reliable adb commands by scotty1223, since they don't freeze​
M7 CWM Nandroid Backup CID H3G__001 1.28.771.x 2013-04-09.zip
Code:
ro.aa.modelid=PN0710000
ro.aa.cidlist=H3G__001,H3G__106,H3G__G04,H3G__402
ro.aa.romver=1.28.771.6
once extracted it will give you a folder "2013-04-20.21.00.00"
so the adb push command will be:
adb push 2013-04-20.21.00.00 /data/media/clockworkmod/backup/2013-04-20.21.00.00



Retired content

Post #1 (extract): Retired content, no longer needed except for RUU.EXE method, so moved it to post #2
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download hboot 1.44: 1.29.401.12_hboot_1.44.zip 502 KB
..... MD5: E6AD52CB30F35D1EB870D09BD065BE62
this is originally from: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
but with modified android-info.txt to include additional CIDs
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
<---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
-------------------------------------------------------------------------------------------------------------------------------------------
Post #4 (extract): Retired content (because only applicable to Windows7)

Step 1: go back to Sense 5 Stock (UPDATED 8 December 2013 for different MIDs, see content below)
in bootloader/FASTBOOT USB, change your CID:
fastboot oem writecid HTC__001 (two underscores)
fastboot reboot-bootloader
-> and confirm CID is HTC__001

Run the following RUU, to downgrade to stock Sense 5: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/

This will completely return you to 100% stock Sense 5, but European unbranded version.


Update (8 December 2013): if your MID is not PN0710000
in order not to mess around with changing MID:
for PN0711000: set CID to HTC__J15, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/

for PN0712000: set CID to CWS__001, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

for PN0713000: set CID to T-MOB010, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/

for PN0714000: set CID to HTC__044, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/

-------------------------------------------------------------------------------------------------------------------------------------------
POST #2: RUU.EXE



Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
In bootloader/FASTBOOT USB, boot to CWM recovery:
fastboot boot CWM.img

you should now be in CWM recovery.

adb push Guru_Bootloader_Reset_1.0.zip /data/media/

in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished:
adb reboot bootloader

and confirm no TAMPERED and LOCKED status



Step 2: Run your RUU.EXE
Download your MID & CID compatible RUU.exe: http://www.htc1guru.com/downloads/ruu-file-downloads/

Run just like any Windows application.



Step 3: if YOU decide to go S-On
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55


All done. :victory:
-------------------------------------------------------------------------------------------------------------------------------------------
POST #3: RUU.ZIP



Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
In bootloader/FASTBOOT USB, boot to CWM recovery:
fastboot boot CWM.img

you should now be in CWM recovery.

adb push Guru_Bootloader_Reset_1.0.zip /data/media/

in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished:
adb reboot bootloader

and confirm no TAMPERED and LOCKED status



Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)

In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
<- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader



Step 3: if YOU decide to go S-On
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55

All done. :victory:
-------------------------------------------------------------------------------------------------------------------------------------------
POST #7: Case in point: CWM method for MID: PN0712000 and CID: ROGER001 for playboypaul situation
retired
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
Case in point: CWM method for MID: PN0712000 and CID: ROGER001
Honestly, I don't know if this "visual" tutorial is easier to follow, I personally actually find it too long, but to each his own ;) Hope it helps anyways :laugh:


Downloads you'll need:
a- CWM recovery: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
..... I'm using this 6.0.4.5 because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.

b- Bootloader Reset: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
MD5: fdb8264a8f4741bae22939cd7734f7c2

c- RUU.ZIP for PN0712000: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
MD5: 55254433f6396a5b9d301ebd9008b401

d- CWM Backup for ROGER001: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-4-2013-06-03-zip/
MD5: 1af173ca5f55c7501ef4089694f7f967

e- preloaded apps: http://loadbalancing.modaco.com/download.php?file=one-1.28.401.7-preloaded-modaco-withoutmovie.zip
MD5: 425c5f7001585588993691eeca7e7819

f- Stock recovery: http://d-h.st/BbX (this is 1.29.401.12, but it's the closest i could find)
MD5: 0d51ab6a134f0e426f1e7c540248fcb0

Please make sure to verify MD5!!!
-------------------------------------------------------------------------------------------------------------------------------------------

so this is what my folder looks like:
Code:
C:\ADB3>[B][COLOR="Blue"]dir[/COLOR][/B]
 Volume in drive C has no label.
 Volume Serial Number is 0622-9D4A

 Directory of C:\ADB3

06/01/2014  15:55    <DIR>          .
06/01/2014  15:55    <DIR>          ..
05/06/2013  08:07    <DIR>          [B]2013-06-03.23.51.18[/B]
                                    [B][I]^^ this I got from extracting the nandroid 
                                       backup (below in red)[/I][/B]
21/12/2013  12:26           819,200 adb.exe
21/12/2013  12:26            96,256 AdbWinApi.dll
21/12/2013  12:26            60,928 AdbWinUsbApi.dll
21/12/2013  12:26           160,256 fastboot.exe
14/11/2013  20:54         3,645,591 Guru_Bootloader_Reset_1.0.zip
03/10/2013  06:41       [COLOR="Red"]979,648,491 M7 CWM Nandroid Backup  CID ROGER001  1.29.631.4 2013-06-03.zip[/COLOR]
19/11/2013  15:13       297,289,697 one-1.28.401.7-preloaded-modaco-withoutmovie.zip
29/09/2013  21:31         9,824,512 recovery 1.29.401.12.img
14/11/2013  07:12         8,955,904 recovery-clockwork-touch-6.0.4.5-m7ul.img
15/10/2013  05:34     1,058,013,184 RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip
              10 File(s)  2,358,514,019 bytes
               3 Dir(s)   4,687,298,560 bytes free


now let's rename some of those files for easier access:

Code:
C:\ADB3>[B][COLOR="Blue"]ren "recovery 1.29.401.12.img" stock_recovery.img[/COLOR][/B]

C:\ADB3>[B][COLOR="Blue"]ren recovery-clockwork-touch-6.0.4.5-m7ul.img CWM.img[/COLOR][/B]

C:\ADB3>[B][COLOR="Blue"]ren "RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip" ruu.zip[/COLOR][/B]


C:\ADB3>[B][COLOR="Blue"]dir[/COLOR][/B]
 Volume in drive C has no label.
 Volume Serial Number is 0622-9D4A

 Directory of C:\ADB3

06/01/2014  15:55    <DIR>          .
06/01/2014  15:55    <DIR>          ..
[COLOR="Purple"][B]07/02/2014  20:27    <DIR>          2013-06-03.23.51.18[/B][/COLOR]
21/12/2013  12:26           819,200 adb.exe
21/12/2013  12:26            96,256 AdbWinApi.dll
21/12/2013  12:26            60,928 AdbWinUsbApi.dll
[COLOR="Purple"][B]14/11/2013  07:12         8,955,904 CWM.img[/B][/COLOR]
21/12/2013  12:26           160,256 fastboot.exe
[COLOR="Purple"][B]14/11/2013  20:54         3,645,591 Guru_Bootloader_Reset_1.0.zip[/B][/COLOR]
03/10/2013  06:41       979,648,491 M7 CWM Nandroid Backup  CID ROGER001  1.29.631.4 2013-06-03.zip
[COLOR="Purple"][B]19/11/2013  15:13       297,289,697 one-1.28.401.7-preloaded-modaco-withoutmovie.zip
15/10/2013  05:34     1,058,013,184 ruu.zip
29/09/2013  21:31         9,824,512 stock_recovery.img[/B][/COLOR]
              10 File(s)  2,358,514,019 bytes
               3 Dir(s)   4,687,585,280 bytes free
-------------------------------------------------------------------------------------------------------------------------------------------

Step 1: go back to Sense 5 Stock

now let's change CID so we can flash the RUU.ZIP for your ModelID: PN0712000

in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem writecid CWS__001[/COLOR][/B]  <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [  0.023s]
finished. total time: 0.023s

C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [  0.041s]
finished. total time: 0.041s
2mqm1vm.jpg

-> confirmed CID is CWS__001 :)
-------------------------------------------------------------------------------------------------------------------------------------------

so now we're all set, let's start: in bootloader/FASTBOOT USB:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.047s
and this is what fastboot ruu mode looks like:
2mmsto3.jpg


Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip ruu.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"


Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip ruu.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,15
(bootloader) [RUU]UZ,boot,27
(bootloader) [RUU]UZ,boot,41
(bootloader) [RUU]UZ,boot,54
(bootloader) [RUU]UZ,boot,68
(bootloader) [RUU]UZ,boot,81
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,16
(bootloader) [RUU]UZ,adsp,26
(bootloader) [RUU]UZ,adsp,37
(bootloader) [RUU]UZ,adsp,49
(bootloader) [RUU]UZ,adsp,60
(bootloader) [RUU]UZ,adsp,71
(bootloader) [RUU]UZ,adsp,83
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[dzdata] unzipping & flushing...
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,5
(bootloader) [RUU]UZ,dzdata,14
(bootloader) [RUU]UZ,dzdata,19
(bootloader) [RUU]UZ,dzdata,29
(bootloader) [RUU]UZ,dzdata,38
(bootloader) [RUU]UZ,dzdata,47
(bootloader) [RUU]UZ,dzdata,52
(bootloader) [RUU]UZ,dzdata,57
(bootloader) [RUU]UZ,dzdata,66
(bootloader) [RUU]UZ,dzdata,71
(bootloader) [RUU]UZ,dzdata,76
(bootloader) [RUU]UZ,dzdata,81
(bootloader) [RUU]UZ,dzdata,90
(bootloader) [RUU]UZ,dzdata,97
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0
(bootloader) [RUU]WP,dzdata,11
(bootloader) [RUU]WP,dzdata,23
(bootloader) [RUU]WP,dzdata,36
(bootloader) [RUU]WP,dzdata,70
(bootloader) [RUU]WP,dzdata,77
(bootloader) [RUU]WP,dzdata,98
(bootloader) [RUU]WP,dzdata,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,32
(bootloader) [RUU]UZ,recovery,44
(bootloader) [RUU]UZ,recovery,72
(bootloader) [RUU]UZ,recovery,85
(bootloader) [RUU]UZ,recovery,96
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
(bootloader) [RUU]UZ,system,1
(bootloader) [RUU]UZ,system,2
(bootloader) [RUU]UZ,system,3
(bootloader) [RUU]UZ,system,4
(bootloader) [RUU]UZ,system,5
(bootloader) [RUU]UZ,system,6
(bootloader) [RUU]UZ,system,7
(bootloader) [RUU]UZ,system,8
(bootloader) [RUU]UZ,system,8
(bootloader) [RUU]UZ,system,9
(bootloader) [RUU]UZ,system,10
(bootloader) [RUU]UZ,system,11
(bootloader) [RUU]UZ,system,12
(bootloader) [RUU]UZ,system,14
(bootloader) [RUU]UZ,system,15
(bootloader) [RUU]UZ,system,16
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,1
(bootloader) [RUU]WP,system,2
(bootloader) [RUU]WP,system,3
(bootloader) [RUU]WP,system,4
(bootloader) [RUU]WP,system,5
(bootloader) [RUU]WP,system,6
(bootloader) [RUU]WP,system,7
(bootloader) [RUU]WP,system,8
(bootloader) [RUU]WP,system,8
(bootloader) [RUU]WP,system,9
(bootloader) [RUU]WP,system,10
(bootloader) [RUU]WP,system,11
(bootloader) [RUU]WP,system,12
(bootloader) [RUU]WP,system,13
(bootloader) [RUU]WP,system,14
(bootloader) [RUU]WP,system,15
(bootloader) [RUU]WP,system,16
(bootloader) [RUU]UZ,system,16
(bootloader) [RUU]UZ,system,16
(bootloader) [RUU]UZ,system,17
(bootloader) [RUU]UZ,system,18
(bootloader) [RUU]UZ,system,19
(bootloader) [RUU]UZ,system,20
(bootloader) [RUU]UZ,system,21
(bootloader) [RUU]UZ,system,22
(bootloader) [RUU]UZ,system,23
(bootloader) [RUU]UZ,system,24
(bootloader) [RUU]UZ,system,24
(bootloader) [RUU]UZ,system,25
(bootloader) [RUU]UZ,system,26
(bootloader) [RUU]UZ,system,27
(bootloader) [RUU]UZ,system,28
(bootloader) [RUU]UZ,system,29
(bootloader) [RUU]UZ,system,30
(bootloader) [RUU]UZ,system,31
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]WP,system,16
(bootloader) [RUU]WP,system,16
(bootloader) [RUU]WP,system,17
(bootloader) [RUU]WP,system,18
(bootloader) [RUU]WP,system,19
(bootloader) [RUU]WP,system,20
(bootloader) [RUU]WP,system,21
(bootloader) [RUU]WP,system,22
(bootloader) [RUU]WP,system,23
(bootloader) [RUU]WP,system,24
(bootloader) [RUU]WP,system,24
(bootloader) [RUU]WP,system,25
(bootloader) [RUU]WP,system,26
(bootloader) [RUU]WP,system,27
(bootloader) [RUU]WP,system,28
(bootloader) [RUU]WP,system,29
(bootloader) [RUU]WP,system,30
(bootloader) [RUU]WP,system,31
(bootloader) [RUU]WP,system,32
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,33
(bootloader) [RUU]UZ,system,34
(bootloader) [RUU]UZ,system,35
(bootloader) [RUU]UZ,system,37
(bootloader) [RUU]UZ,system,38
(bootloader) [RUU]UZ,system,39
(bootloader) [RUU]UZ,system,40
(bootloader) [RUU]UZ,system,40
(bootloader) [RUU]UZ,system,41
(bootloader) [RUU]UZ,system,42
(bootloader) [RUU]UZ,system,43
(bootloader) [RUU]UZ,system,44
(bootloader) [RUU]UZ,system,45
(bootloader) [RUU]UZ,system,46
(bootloader) [RUU]UZ,system,47
(bootloader) [RUU]UZ,system,48
(bootloader) [RUU]WP,system,32
(bootloader) [RUU]WP,system,32
(bootloader) [RUU]WP,system,33
(bootloader) [RUU]WP,system,34
(bootloader) [RUU]WP,system,35
(bootloader) [RUU]WP,system,36
(bootloader) [RUU]WP,system,37
(bootloader) [RUU]WP,system,38
(bootloader) [RUU]WP,system,39
(bootloader) [RUU]WP,system,40
(bootloader) [RUU]WP,system,40
(bootloader) [RUU]WP,system,41
(bootloader) [RUU]WP,system,42
(bootloader) [RUU]WP,system,43
(bootloader) [RUU]WP,system,44
(bootloader) [RUU]WP,system,45
(bootloader) [RUU]WP,system,46
(bootloader) [RUU]WP,system,47
(bootloader) [RUU]WP,system,48
(bootloader) [RUU]UZ,system,48
(bootloader) [RUU]UZ,system,48
(bootloader) [RUU]UZ,system,49
(bootloader) [RUU]UZ,system,50
(bootloader) [RUU]UZ,system,51
(bootloader) [RUU]UZ,system,52
(bootloader) [RUU]UZ,system,53
(bootloader) [RUU]UZ,system,54
(bootloader) [RUU]UZ,system,55
(bootloader) [RUU]UZ,system,56
(bootloader) [RUU]UZ,system,56
(bootloader) [RUU]UZ,system,57
(bootloader) [RUU]UZ,system,58
(bootloader) [RUU]UZ,system,59
(bootloader) [RUU]UZ,system,60
(bootloader) [RUU]UZ,system,61
(bootloader) [RUU]UZ,system,62
(bootloader) [RUU]UZ,system,63
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]WP,system,48
(bootloader) [RUU]WP,system,48
(bootloader) [RUU]WP,system,49
(bootloader) [RUU]WP,system,50
(bootloader) [RUU]WP,system,51
(bootloader) [RUU]WP,system,52
(bootloader) [RUU]WP,system,53
(bootloader) [RUU]WP,system,54
(bootloader) [RUU]WP,system,55
(bootloader) [RUU]WP,system,56
(bootloader) [RUU]WP,system,56
(bootloader) [RUU]WP,system,57
(bootloader) [RUU]WP,system,58
(bootloader) [RUU]WP,system,59
(bootloader) [RUU]WP,system,60
(bootloader) [RUU]WP,system,61
(bootloader) [RUU]WP,system,62
(bootloader) [RUU]WP,system,63
(bootloader) [RUU]WP,system,64
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,65
(bootloader) [RUU]UZ,system,66
(bootloader) [RUU]UZ,system,67
(bootloader) [RUU]UZ,system,68
(bootloader) [RUU]UZ,system,69
(bootloader) [RUU]UZ,system,70
(bootloader) [RUU]UZ,system,71
(bootloader) [RUU]UZ,system,72
(bootloader) [RUU]UZ,system,73
(bootloader) [RUU]UZ,system,74
(bootloader) [RUU]UZ,system,75
(bootloader) [RUU]UZ,system,77
(bootloader) [RUU]UZ,system,78
(bootloader) [RUU]UZ,system,79
(bootloader) [RUU]UZ,system,80
(bootloader) [RUU]WP,system,64
(bootloader) [RUU]WP,system,64
(bootloader) [RUU]WP,system,65
(bootloader) [RUU]WP,system,66
(bootloader) [RUU]WP,system,67
(bootloader) [RUU]WP,system,68
(bootloader) [RUU]WP,system,69
(bootloader) [RUU]WP,system,70
(bootloader) [RUU]WP,system,71
(bootloader) [RUU]WP,system,72
(bootloader) [RUU]WP,system,72
(bootloader) [RUU]WP,system,73
(bootloader) [RUU]WP,system,74
(bootloader) [RUU]WP,system,75
(bootloader) [RUU]WP,system,76
(bootloader) [RUU]WP,system,77
(bootloader) [RUU]WP,system,78
(bootloader) [RUU]WP,system,79
(bootloader) [RUU]WP,system,80
(bootloader) [RUU]UZ,system,80
(bootloader) [RUU]UZ,system,80
(bootloader) [RUU]UZ,system,81
(bootloader) [RUU]UZ,system,82
(bootloader) [RUU]UZ,system,83
(bootloader) [RUU]UZ,system,84
(bootloader) [RUU]UZ,system,85
(bootloader) [RUU]UZ,system,86
(bootloader) [RUU]UZ,system,87
(bootloader) [RUU]UZ,system,88
(bootloader) [RUU]UZ,system,88
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,90
(bootloader) [RUU]UZ,system,91
(bootloader) [RUU]UZ,system,92
(bootloader) [RUU]UZ,system,93
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,95
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]WP,system,80
(bootloader) [RUU]WP,system,80
(bootloader) [RUU]WP,system,81
(bootloader) [RUU]WP,system,82
(bootloader) [RUU]WP,system,83
(bootloader) [RUU]WP,system,84
(bootloader) [RUU]WP,system,85
(bootloader) [RUU]WP,system,86
(bootloader) [RUU]WP,system,87
(bootloader) [RUU]WP,system,88
(bootloader) [RUU]WP,system,88
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,90
(bootloader) [RUU]WP,system,91
(bootloader) [RUU]WP,system,92
(bootloader) [RUU]WP,system,93
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,95
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,97
(bootloader) [RUU]UZ,system,97
(bootloader) [RUU]UZ,system,98
(bootloader) [RUU]UZ,system,98
(bootloader) [RUU]UZ,system,99
(bootloader) [RUU]UZ,system,99
(bootloader) [RUU]UZ,system,100
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,97
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,99
(bootloader) [RUU]WP,system,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,99
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,7
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,20
(bootloader) [RUU]UZ,radio,26
(bootloader) [RUU]UZ,radio,33
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,53
(bootloader) [RUU]UZ,radio,60
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,79
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,53
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
2mouikz.jpg

okay, so the progress bar didn't go all the way, but the command reported "Successful" (check the command prompt output above, I've highlighted it in bold), so let's reboot:

Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [  0.037s]
finished. total time: 0.037s
-------------------------------------------------------------------------------------------------------------------------------------------

Step 2: now let's get back your original CID:

in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem writecid ROGER001[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [  0.018s]
finished. total time: 0.018s

C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [  0.042s]
finished. total time: 0.043s
ifyeco.jpg

-> confirmed we're back on hboot 1.44 and CID is back to ROGER001 :)
-------------------------------------------------------------------------------------------------------------------------------------------

Step 3: restore nandroid

now let's start the restore procedure, so first boot into CWM recovery:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot boot CWM.img[/COLOR][/B]
downloading 'boot.img'...
OKAY [  1.248s]
booting...
OKAY [  0.000s]
finished. total time: 1.248s
rqxcie.jpg


and push the CWM backup to the phone: (if adb doesn't see your device please check FAQ #2 in post #1)
Code:
C:\ADB3>[B][COLOR="Blue"]adb push 2013-06-03.23.51.18 /data/media/clockworkmod/backup/2013-06-03.23.51.18[/COLOR][/B]
push: 2013-06-03.23.51.18/system.ext4.tar.b -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/system.ext4.tar.b
push: 2013-06-03.23.51.18/system.ext4.tar.a -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/system.ext4.tar.a
push: 2013-06-03.23.51.18/system.ext4.tar -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/system.ext4.tar
push: 2013-06-03.23.51.18/recovery.log -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/recovery.log
push: 2013-06-03.23.51.18/recovery.img -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/recovery.img
push: 2013-06-03.23.51.18/nandroid.md5 -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/nandroid.md5
push: 2013-06-03.23.51.18/data.ext4.tar.a -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/data.ext4.tar.a
push: 2013-06-03.23.51.18/data.ext4.tar -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/data.ext4.tar
push: 2013-06-03.23.51.18/cache.ext4.tar.a -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/cache.ext4.tar.a
push: 2013-06-03.23.51.18/cache.ext4.tar -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/cache.ext4.tar
push: 2013-06-03.23.51.18/boot.img -> /data/media/clockworkmod/backup/2013-06-03.23.51.18/boot.img
11 files pushed. 0 files skipped.
3112 KB/s (1501325993 bytes in 471.001s)
and let's restore it: in CWM, press "backup and restore" -> "restore from /sdcard"
ff8u13.jpg


yep, it's there so press it and restore it.
-------------------------------------------------------------------------------------------------------------------------------------------
next to get the preloaded apps, so:
Code:
C:\ADB3>[B][COLOR="Blue"]adb push one-1.28.401.7-preloaded-modaco-withoutmovie.zip /data/media/[/COLOR][/B]
2944 KB/s (297289697 bytes in 98.593s)

now "+++++Go Back+++++" all the way back to the main CWM screen, and press "install zip" -> "choose zip from /sdcard"
11uxh1g.jpg


and select & install the "one-1.28.401.7-preloade..."
-------------------------------------------------------------------------------------------------------------------------------------------

Step 4: get back stock recovery

Code:
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]

C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [  0.047s]
finished. total time: 0.047s

C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery stock_recovery.img[/COLOR][/B]
sending 'recovery' (9594 KB)...
OKAY [  1.230s]
writing 'recovery'...
OKAY [  0.780s]
finished. total time: 2.010s

C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [  0.047s]
finished. total time: 0.047s

C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [  0.031s]
finished. total time: 0.031s
-------------------------------------------------------------------------------------------------------------------------------------------

Step 5: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)

Code:
C:\ADB3>[B][COLOR="Blue"]fastboot boot CWM.img[/COLOR][/B]
downloading 'boot.img'...
OKAY [  1.232s]
booting...
OKAY [ -0.000s]
finished. total time: 1.232s

C:\ADB3>[B][COLOR="Blue"]adb push Guru_Bootloader_Reset_1.0.zip /data/media/[/COLOR][/B]
2653 KB/s (3645591 bytes in 1.341s)

then in the main CWM screen, press "install zip" -> "choose zip from /sdcard"
zx1owg.jpg


and select & install the "Guru_Bootloader_Reset...",

go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"
t8rgcx.jpg

and the output
2z599h2.jpg


now "+++++Go Back+++++" all the way back to the main CWM screen, and
-> "wipe cache"
-> "advanced" -> "wipe dalvik"

Code:
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
and looky here:
2qd2vz5.jpg


no TAMPERED and LOCKED status :)
-------------------------------------------------------------------------------------------------------------------------------------------

Step 6: get your 1st OTA

now reboot your phone, and set up only basic stuff such as WiFi, check for software update and download & install the 1st one only!

Since recovery is not exactly your version, there is a possibility that it will hang (somewhere between 25% to 50%, I think) on the update screen:
2mouikz.jpg


if it does, press and hold POWER + VOLDOWN, when it reboots keep holding VOLDOWN to get back to stock recovery and let it finish its business; in case it gets stuck again, repeat the procedure

After finishing the OTA, boot up your ROM, and check you Settings->About to confirm your new version, then reboot to bootloader and do a fastboot getvar all, and confirm firmware and hboot are also updated
(I think by now you should be able to do this without more detailed instructions)
-------------------------------------------------------------------------------------------------------------------------------------------

Step 7: do a factory reset

Go to Settings -> Backup & reset -> Reset phone (at the bottom select Erase all date) -> OK
to get rid of the nandroid and bootloader_reset from your internal storage
a31e6p.jpg

-------------------------------------------------------------------------------------------------------------------------------------------

Step 8: if YOU decide to go S-On (NOT RECOMMENDED, ONLY IF YOU REALLY INSIST)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55

-------------------------------------------------------------------------------------------------------------------------------------------

After that your phone is "out of the box", :victory: and you are free to take any further OTA updates you like.
 
Last edited:

jande425

Member
Sep 2, 2012
22
2
C:\AndroidADB>fastboot flash zip 1.29.401.12_hboot_1.44.zip
sending 'zip' (501 KB)...
OKAY [ 0.250s]
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: 0.749s


every time i try my CID is OPTUS001
 
  • Like
Reactions: LibertyMarine

jande425

Member
Sep 2, 2012
22
2
help me pleasseeeee

i get this every time :(

i am s off with hboot 1.44

C:\AndroidADB> fastboot flash zip ruu.zip
sending 'zip' (1045181 KB)...
OKAY [ 43.507s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 60.354s
 
  • Like
Reactions: LibertyMarine

Nightf0x_007

Senior Member
Nov 5, 2012
602
58
easy fast clean tutorial

just a question does s-on and lock bootloader does it permanently or just change words from ... to ... ?

and is it easy to go back to s-off and unlock ?
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
easy fast clean tutorial

just a question does s-on and lock bootloader does it permanently or just change words from ... to ... ?

and is it easy to go back to s-off and unlock ?

S-on is strictly optional! (i will add that info), so it's up to YOU if u decide to s-on

Bootloader Reset can be used to LOCK and UNLOCK anytime, as long as u r S-OFF
Otherwise u will need HTCdev to unlock again, or revone if u are on hboot 1.44

Sent from my HTC One using Tapatalk
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,743
7,571
50
Beirut
i get this every time :(

i am s off with hboot 1.44

C:\AndroidADB> fastboot flash zip ruu.zip
sending 'zip' (1045181 KB)...
OKAY [ 43.507s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 60.354s

alright if anyone happens to see this this is where i am at now

i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"


i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha

currently hboot 1.44
s off

mate, there is no ruu.exe or ruu.zip for OPTUS001, there is a nandroid, so you need to follow post #1 then post #4 for CWM nandroids!!

first unlock your bootloader again: fastboot boot CWM.img, "install zip" -> "select zip" -> Guru Bootloader Reset, and UNLOCK the phone.

then follow post #4, and use these:
in step 3, use this: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-optus001-1-29-980-x-rar/
in step 4, try this stock recovery: http://d-h.st/BbX

if you still have trouble, post a "fastboot getvar all" (remove IMEI and serialno)
 

Dynomutt

Senior Member
Aug 23, 2011
52
4
Newcastle upon Tyne
001
C:\AndroidADB>fastboot flash zip 1.29.401.12_hboot_1.44.zip
sending 'zip' (501 KB)...
OKAY [ 0.250s]
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: 0.749s


every time i try my CID is OPTUS001

used Super CID and it downgraded to HBOOT 1.44

I get this also my cid is VODAP001

and the same 24 parsing erro when trying to flash RUU

EDIT: i had to use superCID to get it to work

still getting this though
C:\AndroidADB> fastboot flash zip ruu.zip
sending 'zip' (1045181 KB)...
OKAY [ 43.507s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 60.354s
 
Last edited:

SaHiLzZ

Senior Member
Jan 19, 2011
2,000
516
Why wont it fail... this is the android-info.txt file from that zip. Unzip, add your cid, zip backup and then run it if you need it.

modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.29.401.12
btype:1
aareport:1
hbootpreupdate:3
 

Dynomutt

Senior Member
Aug 23, 2011
52
4
Newcastle upon Tyne
Why wont it fail... this is the android-info.txt file from that zip. Unzip, add your cid, zip backup and then run it if you need it.

modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.29.401.12
btype:1
aareport:1
hbootpreupdate:3

i cant find android-info.txt in my RUU can I just add it to the zip?
 

Dynomutt

Senior Member
Aug 23, 2011
52
4
Newcastle upon Tyne
Rather you should be changing the CID to match one of the CIDs in android.txt.

You are trying to run what RUU?

i am trying to flash vodafone uk RUU, there is no android.txt file in the RUU, i have 2 different one and same 24 parsing error

Edit - sorry my bad, i was trying to flash an OTA, it seems there is no voadfone UK RUU :(
 
Last edited:

SaHiLzZ

Senior Member
Jan 19, 2011
2,000
516
Sounds like you are using the wrong file, it maybe an OTA file, not a firmware/RUU file. Where did you get the RUU from? Link?

---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------

i am trying to flash vodafone uk RUU, there is no android.txt file in the RUU, i have 2 different one and same 24 parsing error

Edit - sorry my bad, i was trying to flash an OTA, it seems there is no voadfone UK RUU :(

Looks like you can use this file: http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/

Actually DO NOT use this... lets see what OP says. However 2.24.161.1 needs 1.54 HBOOT.. A mis-match with 1.44HBOOT will ruin your device.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 108
    Major guide revision 8th February 2014
    Minor update 2nd March 2014: added FAQ #8 as alternate to Guru Bootloader Reset, and also updated Post 3, 4 and 5 to reflect that

    So after doing this quite a few times, I finally ended up writing a guide :cowboy:, so here goes:

    A few extra notes:
    * Please READ the guide, read the sections relevant to you once or twice to make yourself comfortable with the procedure, before you begin
    * DO NOT mix up steps: 1 then 2 then 3, etc. NOT 2 then 3 then 1

    * Mirrors for most files and common nandroids can be found in post #7

    * You can disregard all the "Retired content" stuff, I just kept them for myself to remember previous release of the guide :eek:

    * For a "visual" walk-through check post #8 which has a Case in Point example, with command prompt outputs and screenshots
    * if you go from S-Off to S-On on hboot 1.55 it will most likely cause a "tamper detected - rebooting", and will come back with a TAMPERED bootloader

    * The S-On part in the guide is strictly optional, and it's your decision, and should only be done as the last step (but before OTA to 3.xx).


    -------------------------------------------------------------------------------------------------------------------------------------------
    Operating System Notes
    Windows 8.1 users please see FAQ #1, Windows 7 users please see FAQ #2, Mac users please FAQ #3, and Linux users please see FAQ #4

    sorry for the jumping around, but I'm trying to keep the thread readable, so i don't want to put FAQ first
    FAQs are in post #2

    -------------------------------------------------------------------------------------------------------------------------------------------​


    First you need to be S-Off, this will NOT work with S-On!!!
    A) If you’re on hboot 1.44 use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
    B) If you’re on hboot 1.54/1/55 try rumrunner to get S-Off: http://rumrunner.us/ and thread
    C) you can use Sunshine (paid app $25) works on all M7s (and others): http://theroot.ninja/ and thread

    Looks like http://firewater-soff.com/ is the most popular and successful method for most hboot/firmware/rom combinations at the moment, but nevertheless try all options! firewater is discontinued, even if you find the app, it still needs the developers' servers so it will not work.



    Then, assess your current situation:

    Reboot to bootloader/FASTBOOT USB, then:
    fastboot getvar all

    Code:
    (bootloader) version: 0.5
    [COLOR="Blue"][B](bootloader) version-bootloader: 1.54.0000  <---- your hboot version[/B][/COLOR]
    (bootloader) version-baseband: 4A.18.3263.15
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main: 3.07.1700.1
    [COLOR="Blue"][B](bootloader) version-misc: PVT SHIP S-OFF  <---- confirm S-Off[/B][/COLOR]
    (bootloader) serialno: HTxxxxxxxxxx  <--- remove IMEI and serialno, if you are
    (bootloader) imei: 35xxxxxxxxxxxxxx  <--- going to post it, dont need 2 see them
    (bootloader) meid: 00000000000000
    (bootloader) product: m7_ul
    (bootloader) platform: HBOOT-8064
    [COLOR="Blue"][B](bootloader) modelid: PN0710000  <---- your MID
    (bootloader) cidnum: H3G__001  <---- your CID[/B][/COLOR]
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 3801mV
    (bootloader) partition-layout: Generic
    (bootloader) security: off
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    (bootloader) commitno-bootloader: dirty-94cf81a8fd
    (bootloader) hbootpreupdate: 11
    (bootloader) gencheckpt: 0
    (important parts highlighted in bold above)



    Common downloads for all methods:
    download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
    ..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
    rename the file to CWM.img (careful about .img.img in Windows)
    this is originally from: http://forum.xda-developers.com/showthread.php?t=2173863
    I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.

    download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/showthread.php?t=2527194)
    ----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8



    Now check what options you have for your MID and CID, by visiting:
    1) RUU.EXE (Windows7): http://www.htc1guru.com/downloads/ruu-file-downloads/
    ------> if you’ve found a RUU.EXE proceed to post 3
    ---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead


    2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
    ------> if you’ve found a RUU.ZIP proceed to post 4
    ---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead


    3) nandroid backup (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/stock-nandroid-downloads/
    ------> if you’ve found a CWM nandroid backup proceed to post 5
    ------> if you’ve found a TWRP nandroid backup proceed to post 6
    some nandroids work for several CIDs, for example:
    Code:
    nandroid HTC__039 1.29.980.2: ro.aa.modelid=PN0714000
                                  ro.aa.cidlist=OPTUS001,TELNZ001,VODAP021,HTC__039
    
    nandroid O2___102 1.27.206.1: ro.aa.modelid=PN0710000
                                  ro.aa.cidlist=O2___001,O2___102
    
    nandroid VODAP102 1.29.161.7: ro.aa.modelid=PN0710000
                                  ro.aa.cidlist=VODAP001,VODAP102,VODAPE17,VODAP405,
                                                VODAP304,VODAPD18,VODAP120,VODAP110


    4) IF you haven’t found any of these, try searching and/or you may need to ask in the Q&A thread for someone to share.

    4b) or change the phone to unbranded, easy enough with S-Off, just ask


    -------------------------------------------------------------------------------------------------------------------------------------------
    Revision history
    24th November 2013:
    Initial release.​
    8th December 2013:
    Post #3, update to CWM method to accommodate for different MID models (without the need to change MID).​
    24th January 2014:
    Post #7, added Case in Point example.​
    8th February 2014:
    Major rewrite
    Revision history added
    Post #1: updated (now retired) hboot 1.44 file, updated CWM recovery download, updated and added FAQ for different Operating Systems and not so FAQ
    Post #2: updated for hboot 1.55+ RUU.EXE downgrade problems (retired from Post #1)
    Post #2 and #3: changed from "fastboot boot CWM.img" to "fastboot flash recovery CWM.img" in order to avoid Win7 driver issues
    Post #4 (CWM method): changed from RUU.EXE to RUU.ZIP method (fastboot flash zip ruu.zip) to accommodate different Operating Systems
    Post #6: added to reflect retired methods
    Post #7: updated to new method​
    2nd March 2014:
    Added FAQ #8 as alternate method to Guru Bootloader Reset​
    23rd April 2014:
    Moved FAQ to post #2, thanks @KidCarter93
    29th December 2014:
    Added FAQ #9 and AFH Mirrors in post #7​
    21st March 2015:
    Updated FAQs, updated S-OFF methods​
    -------------------------------------------------------------------------------------------------------------------------------------------

    Disclaimer:
    I'm not responsible for anything going wrong with your phone!


    credits:
    @crushalot (for http://www.htc1guru.com and all his effort keeping it up to date)
    @paulobrien (for the preloaded apps)
    @Guich (for the collection of stock recoveries)
    @S-trace (for originally discovering the location of the lock status flag)
    @scotty1223 (for his ADB shell commands for untampered and locked)
    (if I missed someone, I’m sorry, just PM me and I’ll add)

    -------------------------------------------------------------------------------------------------------------------------------------------
    If you found this guide useful, please press the THANKS button on the first post :).
    -------------------------------------------------------------------------------------------------------------------------------------------
    34
    RUU.ZIP (Windows7, Mac, Linux)
    for Mac users, please remember ./
    for Linux users, please remember sudo



    Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
    In bootloader/FASTBOOT USB, flash CWM recovery:
    fastboot flash recovery CWM.img
    fastboot erase cache
    fastboot reboot-bootloader


    -> enter RECOVERY -> you should now be in CWM recovery.

    Method 1: using adb commands, more reliable, but be careful with the dd commands!!
    I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

    Code:
    C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
    List of devices attached
    HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                                ensure [B]root[/B] privileges
                                i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
    
    C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
    
    [I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
    echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
    1+0 records in
    1+0 records out
    1 bytes (1B) copied, 0.009370 seconds, 106B/s
    
    [I][SIZE="1"]Setting LOCKED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
    echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
    4+0 records in
    4+0 records out
    4 bytes (4B) copied, 0.007691 seconds, 520B/s
    
    ~ # [B][COLOR="Blue"]exit[/COLOR][/B]
    exit
    and continue with below reboot command.
    Method 2: Guru Bootloader Reset, more automated, but may freeze
    adb push Guru_Bootloader_Reset_1.0.zip /data/media/

    in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

    go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
    adb reboot bootloader

    and confirm no TAMPERED and LOCKED status



    Step 2: Flash your RUU.zip
    Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
    Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)

    In bootloader/FASTBOOT USB, flash it:
    fastboot oem rebootRUU
    fastboot flash zip ruu.zip
    fastboot flash zip ruu.zip
    <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
    fastboot reboot-bootloader



    Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
    fastboot oem writesecureflag 3
    reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
    as far as I know, this was introduced in hboot 1.55

    All done. :victory: you can now take OTAs.
    31
    RUU.EXE (Windows7 only)


    If you’re on hboot above 1.44, then first thing is to downgrade that:
    so download hboot 1.44: 1.29.401.12_hboot_1.44.zip 502 KB
    ..... MD5: E6AD52CB30F35D1EB870D09BD065BE62
    this is originally from: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
    but with modified android-info.txt to include additional CIDs
    in bootloader/FASTBOOT USB, flash it:
    fastboot oem rebootRUU
    fastboot flash zip 1.29.401.12_hboot_1.44.zip
    fastboot flash zip 1.29.401.12_hboot_1.44.zip
    <---- just in case the above said “failed flush again”
    fastboot reboot-bootloader
    --> and confirm hboot is now 1.44



    Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
    In bootloader/FASTBOOT USB, flash CWM recovery:
    fastboot flash recovery CWM.img
    fastboot erase cache
    fastboot reboot-bootloader


    -> enter RECOVERY -> you should now be in CWM recovery.

    Method 1: using adb commands, more reliable, but be careful with the dd commands!!
    I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

    Code:
    C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
    List of devices attached
    HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                                ensure [B]root[/B] privileges
                                i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
    
    C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
    
    [I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
    echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
    1+0 records in
    1+0 records out
    1 bytes (1B) copied, 0.009370 seconds, 106B/s
    
    [I][SIZE="1"]Setting LOCKED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
    echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
    4+0 records in
    4+0 records out
    4 bytes (4B) copied, 0.007691 seconds, 520B/s
    
    ~ # [B][COLOR="Blue"]exit[/COLOR][/B]
    exit
    and continue with below reboot command.
    Method 2: Guru Bootloader Reset, more automated, but may freeze
    adb push Guru_Bootloader_Reset_1.0.zip /data/media/

    in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

    go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
    adb reboot bootloader

    and confirm no TAMPERED and LOCKED status



    Step 2: Run your RUU.EXE
    Download your MID & CID compatible RUU.exe: http://www.htc1guru.com/downloads/ruu-file-downloads/

    Run just like any Windows application.



    Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
    fastboot oem writesecureflag 3
    reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
    as far as I know, this was introduced in hboot 1.55


    All done. :victory: you can now take OTAs.
    22
    CWM nandroid backup (Windows7, Mac, Linux)


    First off, placeholders in the below guide:
    CID: H3G__001 should be substituted with your CID, I’m using H3G__001 just as an example
    nandroid backup: “2013-mm-dd.hh.mm.ss” has to be replaced by the real name of the nandroid backup folder



    Step 1: go back to Sense 5 Stock (updated 6 February 2014 for different Operating Systems)
    in bootloader/FASTBOOT USB, change your CID:
    fastboot oem writecid HTC__001 (two underscores)
    fastboot reboot-bootloader
    -> and confirm CID is HTC__001

    Download this: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

    if your MID is not PN0710000
    in order not to mess around with changing MID:
    for PN0711000: set CID to HTC__J15, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/

    for PN0712000: set CID to CWS__001, and download this RUU: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/

    for PN0713000: set CID to T-MOB010, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-20-10-40-1150-04-release-324846-signed-zip/

    for PN0714000: set CID to HTC__044, and download this RUU: http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/

    rename the downloaded file to ruu.zip (careful about .zip.zip in Windows), then in bootloader/FASTBOOT USB, flash it:
    fastboot oem rebootRUU
    fastboot flash zip ruu.zip
    fastboot flash zip ruu.zip
    <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
    fastboot reboot-bootloader

    This will completely return you to 100% stock Sense 5, but European unbranded version (or whatever version the MID+CID ruu was made for).



    Step 2: go back to H3G__001
    fastboot oem writecid H3G__001 <- remember to replace this with YOUR CID
    fastboot reboot-bootloader
    -> and confirm CID is back to H3G__001



    Step 3: restore nandroid
    fastboot boot CWM.img

    you should now be in CWM recovery; verify adb is working, by using:
    adb devices
    it should show your device serial number followed by "recovery" (if adb doesn't see your phone in Windows, please check FAQ #2 in first post, and fix drivers before continuing)

    download this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/ <- this is just an example, remember to download the nandroid for YOUR version from here: http://www.htc1guru.com/downloads/stock-nandroid-downloads/

    extract the zip on your PC, it will give you a folder called similar to "2013-mm-dd.hh.mm.ss" place it in your adb folder then push it:
    adb push 2013-mm-dd.hh.mm.ss /data/media/clockworkmod/backup/2013-mm-dd.hh.mm.ss <- replace mm, dd etc. to what the download gave you

    in recovery select RESTORE, it should show you the above backup, so select "2013-mm-dd.hh.mm.ss" and restore it.


    You still need to get the preloaded stock apps (which get deleted when unlocking using HTCdec), so download this:

    http://loadbalancing.modaco.com/download.php?file=one-1.28.401.7-preloaded-modaco-withoutmovie.zip (from this thread: http://forum.xda-developers.com/showthread.php?t=2200628)

    adb push one-1.28.401.7-preloaded-modaco-withoutmovie.zip /data/media/

    in recovery, select "install zip" -> "choose zip" -> and install the above file



    Step 4: get back stock recovery
    the above nandroid may or may not contain stock recovery, but I doubt it does, so get one from here (find one as close as possible to your version): http://forum.xda-developers.com/showthread.php?t=2463387
    and rename it to stock_recovery.img (careful about .img.img in Windows)

    now let's reboot to bootloader/FASTBOOT USB:
    adb reboot bootloader
    fastboot erase cache
    fastboot flash recovery stock_recovery.img

    fastboot erase cache



    Step 5: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
    In bootloader/FASTBOOT USB, boot to CWM recovery:
    fastboot boot CWM.img

    -> you should now be in CWM recovery.

    Method 1: using adb commands, more reliable, but be careful with the dd commands!!
    I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

    Code:
    C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
    List of devices attached
    HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                                ensure [B]root[/B] privileges
                                i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
    
    C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
    
    [I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
    echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
    1+0 records in
    1+0 records out
    1 bytes (1B) copied, 0.009370 seconds, 106B/s
    
    [I][SIZE="1"]Setting LOCKED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
    echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
    4+0 records in
    4+0 records out
    4 bytes (4B) copied, 0.007691 seconds, 520B/s
    
    ~ # [B][COLOR="Blue"]exit[/COLOR][/B]
    exit
    and continue with below instructions.
    Method 2: Guru Bootloader Reset, more automated, but may freeze
    adb push Guru_Bootloader_Reset_1.0.zip /data/media/

    in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"

    go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below instructions.

    Since you're still in CWM, go ahead and:
    -> "wipe cache"
    -> "advanced" -> "wipe dalvik"
    then
    adb reboot bootloader

    and confirm no TAMPERED and LOCKED status



    Step 6: get your 1st OTA
    finally (almost) to confirm everything is back to 100% stock, reboot your phone, and set up only basic stuff such as WiFi, check for software update and download & install the 1st one only! (make sure it's either another 1.xx or 2.xx, do not use a 3.xx update, if you intend on going S-On)
    Since recovery is not exactly your version, you may need to reboot your phone manually if it doesnt by itself: the progress bar stopped somewhere in the middle -> press and hold POWER + VOLDOWN, when it reboots keep holding VOLDOWN to get back to stock recovery and let it finish its business; repeat if it gets stuck again

    After finishing the OTA, boot up your ROM, and check you Settings->About to confirm your new version, then reboot to bootloader and do a fastboot getvar all, and confirm firmware and hboot are also updated



    Step 7: do a factory reset
    Go to Settings -> Backup & reset -> Reset phone (at the bottom select Erase all date) -> OK
    to get rid of the nandroid and bootloader_reset from your internal storage



    Step 8: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
    fastboot oem writesecureflag 3
    reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
    as far as I know, this was introduced in hboot 1.55


    All done. :victory: you can now take any remaining OTAs.

    Side note: why is this procedure so long you may ask, then take a look here for a brief explanation: http://forum.xda-developers.com/showpost.php?p=52430301&postcount=834
    17
    Frequently Asked Questions


    FAQ:
    1) Q: I'm using Windows 8.1 what should I worry about
    A: when you downgrade to hboot 1.44, or it get's downgraded during an ruu, fastboot commands will no longer work and you will be stuck, so you need to use Win7 or Linux (continue reading FAQ)

    EDIT: or you could try this [GUIDE] Fix Fastboot on Windows 8.1 (thanks @clsA)​


    2) Q: I'm using Windows 7 what should I worry about
    A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
    dh4kjo.jpg


    follow the below instructions to fix

    Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
    just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
    though you should already have them since you have been using your phone anyways

    for those who like a visual guide:

    okay so I did a fastboot boot command, and as you can see it didnt install correct driver
    28ioxf6.jpg



    Open "Device Manager"
    2ywxpp3.jpg



    there's the culprit
    312v6me.jpg



    right click and Update Driver Software
    2ivmu5k.jpg



    select Browse my computer for driver software
    357qek7.jpg



    select Let me pick from a list of device drivers on my computer
    2582flf.jpg



    select Android USB Devices
    143jar8.jpg



    select My HTC ... (if you have more than one version, choose the latest)
    axea9h.jpg



    warning, select Yes
    14lhelv.jpg



    successful installation
    21btc3d.jpg



    now it looks better :)
    zwx53s.jpg


    and can confirm:
    Code:
    C:\ADB3>[B]adb devices[/B]
    List of devices attached
    HTxxxxxxxxxx    recovery
    -------------------------------------------------------------------------------------------------------------------------------------------


    3) Q: I'm using a Mac what should I worry about
    A: not much, you just can't run a Windows RUU.EXE (executable), and you probably need to use "./":
    --> you'll need to use RUU.ZIP method instead
    --> CWM guide also updated
    ----> depending on your setup, you may need to run adb and fastboot commands, with "./" as in "./adb ..." and "./fastboot ..."​


    4) Q: I'm using Linux what should I worry about
    A: not much, you just can't run a Windows RUU.EXE (executable), and some commands might require "sudo":
    --> you'll need to use RUU.ZIP method instead
    --> CWM guide also updated
    ----> adb seems to work just fine in any mode, but
    ----> fastboot may need su privileges, so you'll need to issue fastboot commands with "sudo fastboot ..."​


    5) Q: How do I create a Linux Live USB

    Windows users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
    Mac users: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx

    Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
    in case you're having problems setting up adb/fastboot on newer versions, use 12.04 http://releases.ubuntu.com/12.04/


    Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB

    No need to install, just use the "Try Ubuntu" option
    20kxjt0.jpg


    open a terminal
    2u62uc1.jpg


    and install adb & fastboot using (copy/paste 1 line at a time into terminal):
    Code:
    sudo add-apt-repository ppa:nilarimogard/webupd8
    sudo apt-get update
    sudo apt-get install android-tools-adb android-tools-fastboot
    you can then check version, by typing "adb version"
    and check connection using "adb devices" in custom recovery or booted phone
    and "sudo fastboot devices" in bootloader

    in case you're having issues, please check @Danny201281's MiniGuide here for more information

    you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
    -------------------------------------------------------------------------------------------------------------------------------------------​

    6) Q: fastboot is giving me "cannot load"
    A: the filename is wrong​


    7) Q: flashing 1.44 hboot gives me "FAILED (remote: 42 custom id check fail)"
    A: your CID is missing in android-info.txt; the updated zip on my mega account should work, if it doesn't edit android-info.txt to include your CID using Notepad++, or temporarily change CID "fastboot oem writecid 11111111" <- 8 ones, flash hboot, and restore your original CID.​


    8) Q: Guru Bootloader Reset just keeps freezing
    A: Use alternate method:
    credits to @scotty1223
    [how to] remove your "tampered" banner
    [how to] lock/unlock your bootloader without htcdev(s-off required)

    I recommend you copy/paste the "echo | dd" commands!! (If you write to the wrong partition/offset you could have a brick)

    Code:
    C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
    List of devices attached
    HT34xxxxxxxx    recovery [I]<- you need to be in CWM recovery to
                                ensure [B]root[/B] privileges
                                i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
    
    
    C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
    
    [I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
    echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
    1+0 records in
    1+0 records out
    1 bytes (1B) copied, 0.009370 seconds, 106B/s
    
    [I][SIZE="1"]Setting LOCKED[/SIZE][/I]
    ~ # [B][COLOR="Blue"]echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
    echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
    4+0 records in
    4+0 records out
    4 bytes (4B) copied, 0.007691 seconds, 520B/s
    
    ~ # [B][COLOR="Blue"]exit[/COLOR][/B]
    exit
    
    C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
    --> confirm that bootloader is untampered and LOCKED


    9) Q: I "adb push" the backup files, but it doesn't show up in restore
    A: on a few rare occasions, CWM recovery doesn't mount the data partition automatically, do "adb shell mount /data" and then try pushing the files again.​


    10) Q: When I run the Windows RUU.EXE it just exits when I click next
    The RUU executable needs the MS Visual C++ 2008 Redistributable Package (x86) package installed.​
    -------------------------------------------------------------------------------------------------------------------------------------------

    Not so FAQ (maybe):
    1) Q: What is this MD5 people keep talking about
    A: https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt

    on Mac, Linux, and Android terminals it's already built in:
    Mac: in terminal, just type md5 <name of file>
    ----> MD5 (<name of file>) = 12345678901234567890123456789012

    Linux: in terminal, just type md5sum <name of file>
    ----> 12345678901234567890123456789012 <name of file>

    Android: in "adb shell", just type md5sum <name of file>
    ----> 12345678901234567890123456789012 <name of file>


    Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ or http://implbits.com/hashtab.aspx (available for Windows and Mac, credits to @Lizard for that one ;))
    -------------------------------------------------------------------------------------------------------------------------------------------


    2) Q: What can I flash (or not) with S-On/S-Off and a (re)locked/unlocked bootloader
    A: This may help
    2hqqz6e.jpg