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

Search This thread

Narship

Member
Feb 11, 2014
19
2
Glad it worked out :good:


Why not run a custom ROM?? if you want to change to international unbranded?

1- you'll need to be S-Off

2- please post an updated "fastboot getvar all" (excluding IMEI and s/n)

3- any language pack in particular you'll need? because if you're looking for Spanish / Peru (es_PU), it seems the .401. editions don't have it :confused::
Code:
[B][U]HTC__001[/U][/B]
          .........
          <item type="boolean" name="es_AE">yes</item>
          <item type="boolean" name="es_AM">yes</item>
          <item type="boolean" name="es_AZ">yes</item>
          <item type="boolean" name="es_BY">yes</item>
          <item type="boolean" name="es_CY">yes</item>
          <item type="boolean" name="es_EG">yes</item>
          <item type="boolean" name="es_ES">yes</item>
          <item type="boolean" name="es_FR">yes</item>
          <item type="boolean" name="es_GB">yes</item>
          <item type="boolean" name="es_GE">yes</item>
          <item type="boolean" name="es_GR">yes</item>
          <item type="boolean" name="es_IE">yes</item>
          <item type="boolean" name="es_IT">yes</item>
          <item type="boolean" name="es_KE">yes</item>
          <item type="boolean" name="es_KW">yes</item>
          <item type="boolean" name="es_KZ">yes</item>
          <item type="boolean" name="es_NG">yes</item>
          <item type="boolean" name="es_PT">yes</item>
          <item type="boolean" name="es_QA">yes</item>
          <item type="boolean" name="es_RU">yes</item>
          .........
		  
[B][U]HTC__304[/U][/B]
          .........
          <item type="boolean" name="es_CY">yes</item>
          <item type="boolean" name="es_ES">yes</item>
          <item type="boolean" name="es_GR">yes</item>
          <item type="boolean" name="es_PT">yes</item>
          .........

or you could use a locale changer from the play store.

Hi!

I really really like to use sense, but my country operator (Claro Peru) uses a series of icons and customization that spoils the beauty of HTC.

(Besides the custom roms are somewhat unstable ^_^)

I would like Latin American language (Peru there, so Spanish would be nice)
Spanish Language in Mexico or Spain would be great.

Here I leave my report:

(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-microp: None
(bootloader) version-main: 3.20.598.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH41KW******
(bootloader) imei: 3544350*********
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on


:D
 

nokevin

Member
Dec 5, 2009
43
0
A MASSIVE THANK YOU, mine is all done, no vodafone rubbish & no vodafone app's and is now getting OTA's excellent work and very very helpful. One thing I did have a small problem with was when in other bootloader screen the PC lost coms with the phone and I had to load Guru_Bootloader_Reset_1.0 from a USB stick after that it all went well

THANK YOU

Hi my phone has been working perfect, thank you again. I now might have a problem, my phone has to go back to HTC for pink camera problems, I have called them and they tell me to send it in, question is do I have to do anything before I do so they dont know its been tampered with ?

Thanks
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Hi!

I really really like to use sense, but my country operator (Claro Peru) uses a series of icons and customization that spoils the beauty of HTC.

(Besides the custom roms are somewhat unstable ^_^)

I would like Latin American language (Peru there, so Spanish would be nice)
Spanish Language in Mexico or Spain would be great.

Here I leave my report:

(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.20.598.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) security: on


:D

1- first thing will be to get S-Off

2- Spanish / Spain is no problem, just not Spanish / Peru

3- I disagree with custom ROMs being unstable :laugh: my phone has been on custom since day 1 and I have yet to see it crash :victory: (unless I'm testing an early release with known bugs)


Hi my phone has been working perfect, thank you again. I now might have a problem, my phone has to go back to HTC for pink camera problems, I have called them and they tell me to send it in, question is do I have to do anything before I do so they dont know its been tampered with ?

Thanks
Can you elaborate on the state of the phone.... in general if bootloader shows LOCKED (not relocked), and doesn't have TAMPERED, then it should be good to go.
Some countries have issues with the phone being S-Off, but technically they shouldn't.
 

nokevin

Member
Dec 5, 2009
43
0
Can you elaborate on the state of the phone.... in general if bootloader shows LOCKED (not relocked), and doesn't have TAMPERED, then it should be good to go.
Some countries have issues with the phone being S-Off, but technically they shouldn't.

Thanks, my phone has:

***LOCKED***
M7_UL PVT S-OFF RH
CID-HTC_001
HBOOT-1.56.0000
RADIO-4a.253263.21
openDSP-v32. 120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Fed 26 2014, 12:32:09.0

Is that all ok ?
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Thanks, my phone has:

***LOCKED***
M7_UL PVT S-OFF RH
CID-HTC_001
HBOOT-1.56.0000
RADIO-4a.253263.21
openDSP-v32. 120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Fed 26 2014, 12:32:09.0

Is that all ok ?

yes LOCKED and no tampered is good; i don't know if you're repair center cares about s-off/s-on, that really depends where you are and who does the repair.
BUT, don't try to go s-off to s-on on your current version... it will likely trigger the TAMPERED again.
 
  • Like
Reactions: nokevin

Narship

Member
Feb 11, 2014
19
2
1- first thing will be to get S-Off

2- Spanish / Spain is no problem, just not Spanish / Peru

3- I disagree with custom ROMs being unstable :laugh: my phone has been on custom since day 1 and I have yet to see it crash :victory: (unless I'm testing an early release with known bugs)



Can you elaborate on the state of the phone.... in general if bootloader shows LOCKED (not relocked), and doesn't have TAMPERED, then it should be good to go.
Some countries have issues with the phone being S-Off, but technically they shouldn't.


Good morning :D thanks for answer.

Mmm yes, you're right, when you actually used the MIUI rom had almost no errors *and moreover I do not want to use cyanogen xD

OK, tonight I come home and start the S-OFF process but first I would like to clarify some doubts.

1. Is there any way to unlock the bootloader without using HTC DEV? (To save the warranty).
2. As I can make a copy of my Stock Recovery? (I do not plan to use TWRP or CWM).
3. The RUU change affects GPS parameters? My Location? Operator recognition by region or navigation? (I don't know about RADIO)

I'm from Latin America, so I would really a RUU with Mexico Spanish language (LA). (Spanish Spain is another continent EU xD)
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
:D


Thanks for all the help buddy. I'll check back later when the website comes back up

EDIT: I had a long look at the guide post and came up with these 2 downloads. Correct me if im wrong.

First I would need to install this: http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/ but have to change my CID to one of those listed first.
Then after changing my CID back to the original I would flash this nandroid backup to CWM http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/

Then I should find the closest stock recovery to 3.63.980.2 and finally use guru reset to relock the bootloader

Thanks in advance :D

Almost! but the ruu is no good!! (and not google edition!!) You should always go for the "lowest common denominator".... so stick with 1.xx things, lower is better not higher.

the ruu you need is already mentioned in my guide (in post #4):
"for PN0714000: set CID to HTC__044, and download this RUU: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-zip/"

then continue with the guide, and use CWM backup you mentioned above.

remember to get a stock recovery which is close, so possibly this one: http://d-h.st/BbX


Please make sure you have read the guide and are comfortable with it.... otherwise ask away.

Good Luck
 
Last edited:

DarkShock124

Member
Mar 13, 2012
11
0
Almost! but the ruu is no good!! (and not google edition!!) You should always go for the "lowest common denominator".... so stick with 1.xx things, lower is better not higher.

the ruu you need is already mentioned in my guide (in post #4):
"for PN0714000: set CID to HTC__044, and download this RUU: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-zip/"

then continue with the guide, and use CWM backup you mentioned above.

remember to get a stock recovery which is close, so possibly this one: http://d-h.st/BbX


Please make sure you have read the guide and are comfortable with it.... otherwise ask away.

Good Luck

Hey buddy just having some troubles rewriting my CID. Its giving me an "Invalid CID" error when i try to change it back from HTC_044 to HTC__39
 

HC4Life

Senior Member
Nov 16, 2007
5,518
2,140
Hardcore
I'm sending my phone on monday to repair because of the purple tint in camera. I'm a little confused...
How can i manage to reset and make stock my phone? I have Hboot 1.56 , unlocked bootloader, s-off and the latest firmware 4.19.401.11 and my cid is HTC__304.

Thx :)

---------- Post added at 04:53 PM ---------- Previous post was at 04:21 PM ----------

I also have the latest TWRP 2.7 recovery.
Please i need HELP!
 
Last edited:

detovenaar

Senior Member
Mar 2, 2009
149
35
Hi all,

Today I did transfer some files with my one to an other phone with es explorer when suddenly my phone became into a bootloop.
The phone will boot loop when the animation screen is 3 sec on his way. So I did try to get into Recovery (TWRP) but when the twrp bootscreen in screen it reboots again.
I

So I did fastboot erase cache with no results solving the problem
I did re-flashed TWRP with no results solving the problem
I did re-flashed firmware from here http://xdaforums.com/show....php?t=2316726 with no results solving the problem.

The divice is NOT able to boot into ROM and recovery

Can someone please help me with this?

ROM I am running [ROM][MAR 20] ViperOne 5.8.0 | 4.19.401.11 | Android 4.4.2 Sense 5.5

I do have backups, even from before flashing custom roms
First backup I made with the following command: adb backup -apk -all -f backup.ab
All the other backups where made with TWRP and I have them stored at my pc.

Bootloader info: M7 UL PVT SHIP S-OFF RH
CID-T-MOB101 (I did had super sid but I chanced it back before making drastic steps to come)
HBOOT 1.56.0000

I did already relock my htc one.
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
I'm sending my phone on monday to repair because of the purple tint in camera. I'm a little confused...
How can i manage to reset and make stock my phone? I have Hboot 1.56 , unlocked bootloader, s-off and the latest firmware 4.19.401.11 and my cid is HTC__304.

Thx :)

---------- Post added at 04:53 PM ---------- Previous post was at 04:21 PM ----------

I also have the latest TWRP 2.7 recovery.
Please i need HELP!

can you confirm
1- s-off
2- mid: PN0710000
3- cid: HTC__304

-> Yes, then use RUU.ZIP method (posts #1 and post #3) using:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
 
  • Like
Reactions: Narship

Narship

Member
Feb 11, 2014
19
2
at last ..

1- first thing will be to get S-Off

2- Spanish / Spain is no problem, just not Spanish / Peru

3- I disagree with custom ROMs being unstable :laugh: my phone has been on custom since day 1 and I have yet to see it crash :victory: (unless I'm testing an early release with known bugs)

Hey!

I am now S-OFF,

Spanish from Spain is good :D but actually a Spanish-America would be ideal. (thanks in advance).

By the way, before continuing with RUU, I'm trying out some ROMS (I wish I had some recommendations ^^)
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
1- first thing will be to get S-Off

2- Spanish / Spain is no problem, just not Spanish / Peru

3- I disagree with custom ROMs being unstable :laugh: my phone has been on custom since day 1 and I have yet to see it crash :victory: (unless I'm testing an early release with known bugs)

Hey!

I am now S-OFF,

Spanish from Spain is good :D but actually a Spanish-America would be ideal. (thanks in advance).

By the way, before continuing with RUU, I'm trying out some ROMS (I wish I had some recommendations ^^)


Here's an excellent index thread of ROMs, etc: http://xdaforums.com/showthread.php?t=2438026
 
  • Like
Reactions: Narship

supriza47

Member
Aug 27, 2011
16
0
can i still gain s-off if i'm on >3.XXX version? or do i have to downgrade somehow? If so please direct me to the quickest method for downgrading. Thanks
 
Last edited:

harshdev

Senior Member
Mar 6, 2010
95
5
hey @nkk71 I wanted to know is it safe flashing a dev edition (Brightstar US) RUU over T-Mobile phone? This guy reported it to be working flawlessly http://xdaforums.com/showthread.php?t=2323257

However, I am not sure about the OTA's. I believe I have to update mid and cid for OTA's.

My current stats:
Originally a Tmobile phone
mid - 713000
cid - SuperCid
GPE - 4.4.2
Firmware - 3.62.1700.1
Hboot 1.54
S-OFF

What I am scared of is changing mid. I read alot of forum and I have until now stayed away from messing around with mid.
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
hey @nkk71 I wanted to know is it safe flashing a dev edition (Brightstar US) RUU over T-Mobile phone? This guy reported it to be working flawlessly http://xdaforums.com/showthread.php?t=2323257

However, I am not sure about the OTA's. I believe I have to update mid and cid for OTA's.

My current stats:
Originally a Tmobile phone
mid - 713000
cid - SuperCid
GPE - 4.4.2
Firmware - 3.62.1700.1
Hboot 1.54
S-OFF

What I am scared of is changing mid. I read alot of forum and I have until now stayed away from messing around with mid.

I didn't read the other thread you mentioned, but yes, it's easy enough to change a GSM model to a US Developer Edition:

1- you need to be S-Off, and I highly recommend you DO NOT EVEN THINK about S-On

2- US Dev Edition has: modelid: PN0712000 and cid: BS_US001

3- with S-Off there's no need to relock bootloader, so keep bootloader UNLOCKED

4- change CID: fastboot oem writecid BS_US001

5- change MID: using [TOOL] MID change without ENG HBOOT | Aroma GUI
^^ this is done using custom recovery as mentioned in the thread, it's easy and safe, no need to mess with ENG hboots!!

6- flash Dev Edition (x.xx.1540.x) ruu.zip from http://www.htc1guru.com/downloads/ruu-zip-downloads/
although there is a 3.22.1540.1 version, i personally prefer lower versions in general (and then take OTAs), so i would use 1.29.1540.3
but that's just my personal preference
....remember to check MD5 on the download to make sure it's not corrupt!! (some people were having bad downloads a few days ago)

all done :) you can take OTA updates at your will.
 

cy88

Senior Member
Nov 14, 2010
200
105
nkk71, thanks for the comprehensive guide, it's very easy to follow and works great so far! I am getting MD5 mismatch from CWM for restoring ROGER001 CWM Backup. Already tried different ways of downloading it and downloaded it about 4 times.

Is it a known issue?

Thanks!
 

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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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