Evo V 4G RUU Flashing guide / Unroot guide

Last Updated:

  1. jerofld

    jerofld Fixing stuff is not easy VIP Member

    Note that if you intend to re-root after flashing the RUU you should do a backup with Titanium Backup or MyBackupPro before starting. This will wipe your device of all settings, apps, etc. Basically, anything that isn't backed up onto your SD card!

    This is also going to be the way of flashing firmware updates for those of you who do not get S-OFF. Either that or take OTAs, which may be problematic if you're running a custom ROM.

    Step 1) How to install and configure the Android SDK

    First, you need to download all of the following software:

    Note that if you followed my rooting guide, this is the same setup, except the RUU. If you still have all of this installed, you just need to download the RUU, everything else (SDK, HTC Sync, ROM and TWRP) are exactly the same.

    1) HTC Sync is needed to link your phone to your computer with the proper drivers. On XDA they link the HTC drivers by themselves. These are fine, but I can't find a direct link on the HTC site, so I'm linking HTC Sync.

    2) Mini-SDK is a multiple platform set of fastboot and ADB so that you do not have to download the full Android SDK. It is easier to use, too. Just download sdk-tools.zip and extract it to your hard drive. I'll assume that most of you are using Windows, and for this tutorial, I'll extract Mini SDK to C:\sdk-tools. But Mini-SDK has Mac and Linux versions included in the zip file, so all are supported here.

    Alternatively, if you want to install the full Android SDK, you can do so by following this guide.

    3) The current RUU, which can be found here: http://goo.im/stock/shooter/ruu (alternatively herehttp://www.freefilehosting.net/pg86img) You will need the link that says ICS and VM in it. Currently, it is the third from the top. I cannot directly link to the file.

    If you are rooting again after flashing the RUU, you will need this, as well:

    4) A rooted ROM based off the current version (current version is 2.17.651.5). Optionally, you can use any ROM based off of the current version. Here is the stock ROM: Evo V Stock ROMs. Place this on your SD card. I recommend making a new folder called /ROMs and putting it in there.

    5) TeamWin Recovery Project (TWRP) version 1.1.1 - Get the IMG version and rename to 'recovery.img', put it in your C:\SDK-tools folder.

    Step 2) Lock the bootloader

    Note: If you came from Step 4 from my rooting guide because you were having trouble with flashing the unlock token, you do not have to do this step. You can proceed to Step 3 of this guide. If your bootloader is UNLOCKED (as in, it says UNLOCKED at the top) then you have to do this step.

    1) Plug your phone into your computer with the data cable.

    2) Power the phone down. Reboot phone into hboot mode by holding volume down and then press power. Keep volume down held until you boot into hboot mode.

    3) You should already be in fastboot if you connected your phone to your computer through your USB cable. If not, select the Fastboot option. Fastboot should be highlighted and be in bold red. Set the phone down and concentrate on your computer.

    4) Now, click Start and either open Run, or click in the text box in your start menu. Then type 'cmd'. You get a command prompt. Now we need to go to the Mini SDK folder. If you installed it in the same directory I did, you can copy (or type):

    Code (Text):
    1. cd C:\sdk-tools
    Now go back into your command prompt and right click on it. Click paste and then push enter. You should now be in the mini SDK directory. If you have Windows 7, you can go to your mini SDK folder and hold shift and right click on the folder and click "Open command window here" as an alternative means than copying and pasting (thanks to mteezey for the tip). To check that you are in the right folder, you can type 'fastboot' then enter, you should get this:

    Code (Text):
    2. C:\sdk-tools>fastboot
    3. usage: fastboot [ <option> ] <command>
    4. commands:
    5. update <filename> reflash device from update.zip
    6. flashall flash boot + recovery + system
    7. flash <partition> [ <filename> ] write a file to a flash partition
    8. erase <partition> erase a flash partition
    9. getvar <variable> display a bootloader variable
    10. boot <kernel> [ <ramdisk> ] download and boot kernel
    11. flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
    12. devices list all connected devices
    13. continue continue with autoboot
    14. reboot reboot device normally
    15. reboot-bootloader reboot device into bootloader
    16. help show this help message
    17. options:
    18. -w erase userdata and cache
    19. -s <serial number> specify device serial number
    20. -p <product> specify product name
    21. -c <cmdline> override kernel commandline
    22. -i <vendor id> specify a custom USB vendor id
    23. -b <base_addr> specify a custom kernel base address
    24. -n <page size> specify the nand page size. default:2048
    26. C:\sdk-tools>
    If you see this, fastboot is running correctly. :)

    5) Now in the command prompt you need to send the oem lock command to the phone to lock the bootloader.

    Type this in the command prompt and hit enter:

    Code (Text):
    2. fastboot oem lock
    6) Pick up your phone and scroll down in hboot and select reboot bootloader. If sucessful, you should now see LOCKED at the top. :)

    Step 3) Run the RUU

    First off make sure your phone is at least 50% charged prior to starting this step, but full charged is preferred. ;)

    1) Make sure the HTC drivers you downloaded earlier are installed and working. Do this by connecting your phone to your computer. If your computer detects it, your drivers are working.

    2) Run the RUU.exe on your computer. It takes a few minutes to boot up, so don't be alarmed if it doesn't appear immediately.

    3) Follow the prompts. It should ask you to ensure your phone is plugged into the computer and that ADB debugging is on. If you're still in FASTBOOT USB from Step 4 of my rooting guide, that's fine, the RUU.exe will detect that and be able to work from fastboot.

    4) The RUU should recognise the phone and start running. Be patient, do not unplug the phone under any circumstances!!

    Alternative method to flashing a RUU

    If RUU.exe does not work for you, you can manually extract the RUU.zip from the RUU.exe.

    1) Go to Start > Run > type "%temp%" and push enter, this is your temp directory. I recommend you clear out as much as you can.

    2) Run RUU.exe with this folder open. You'll see a few new directories, in one of them, there is a file called rom.zip. Copy that file to your SD card and rename it to "PG86IMG.zip".

    3) Reboot your phone into bootloader mode. This file should flash.

    Thanks to EddyOS for his post here: RUU as .zip ... possible?

    5) Reboot your phone (I believe it does it automatically) to make sure everything is loaded correctly. Go to Settings > About Phone and check to see that your firmware is updated. For 2.17.651.5, the values should say: Software version 2.17.651.5, baseband should be If you see those values, you are good!

    If you simply wanted to unroot, you are done. If you want to root again, please continue:

    Step 4) Re-unlock your bootloader

    1) Now that we're back in Android, connect your computer to the phone again, open a CMD window and get back to C:\sdk-tools by typing:

    Code (Text):
    1. cd c:\sdk-tools
    2) Let's reboot back to the bootloader. Do this by typing:

    Code (Text):
    1. adb reboot bootloader
    And verify that it says FASTBOOT USB in red. If it says HBOOT in blue, push power to switch to FASTBOOT and ensure your USB is connected. Once it says FASTBOOT USB, proceed.

    You are going to need your Unlock_code.bin from HTC dev. If you have it, proceed to step 3. If you deleted it, read the following:

    1) Check your Email, it might still be there.

    2) If not, you can get the token again. Type the following command in the command prompt:

    Code (Text):
    1. fastboot oem get_identifier_token
    A long text boxes will come up. Right mouse button click on the screen and click mark.

    Then highlight the token from <<<< Identifier Token Start >>>> to <<<<< Identifier Token End >>>>>, like shown:


    Do not highlight info or bootloader or any extra spaces or text. Once you have done that, right click again and hit copy.

    Now go to HTCdev - Unlock Bootloader and fill out the forms and paste the code into the device identifier token box and submit. You'll get an email (check your spam folder) with your unlock_code.bin. Once your receive it, transfer that file into your C:\sdk-tools\ folder.

    3) Flash the Unlock_code.bin file.

    Code (Text):
    1. fastboot flash unlocktoken Unlock_code.bin
    It will prompt you that asks you if you want to unlock, you do.

    4) The phone should reboot. You are unlocked again!

    Step 5) Flashing the recovery, again

    Now we need to get back into the bootloader. Here's how to do it, if you don't remember how to do it (and so you don't have to go back to a previous step):
    We need to turn off one of HTC's defaulted on features. It is the very frustratingly named 'Fast Boot' in Settings > Power. No, this is not 'fastboot' in the Android SDK. This is a feature that is like Hibernate in Windows but for HTC devices. I really hate how HTC calls it this, but that's what they decided to call it.

    Next, go to Settings > Applications > Development and check USB Debugging. You'll need this enabled for the adb reboot command. Plus a number of rooting apps require it. Give the computer a few minutes to recognize your phone, install drivers, and so on, if it needs to.

    Connect your phone to your computer. From now until you're done flashing your ROM, you will not disconnect the USB cable. So don't even think about it!

    Quick tip: Do NOT connect to a USB 3.0 port. For some reason, fastboot will not detect your device if you're connected through a USB 3.0 port. If you're unsure if you have a USB 3.0 port, don't worry about it unless your fastboot commands say that they're waiting for device when the device is hooked up.

    Now, in the command prompt, type (or copy and paste):

    Code (Text):
    1. adb reboot bootloader
    You should now be in your bootloader. It should say "FASTBOOT USB" in red highlight. If so, this is good! If not, make sure HBOOT in the menu is highlighted and push the power button. This will change it to FASTBOOT and it'll detect that it's connected to USB and change in a few seconds.

    Now we will reflash TWRP 1.1.1. If you don't have the TWRP recovery as 'recovery.img' in your C:\SDK-Tools folder, you're going to have to download it again (make sure to get the IMG file and not the ZIP!) and rename it to 'recovery.img' and make sure you copy it to C:\SDK-tools! Now you can type (or copy):

    Code (Text):
    1. fastboot flash recovery recovery.img
    This now flashes TWRP 1.1.1. A vertical green progress bar will be displayed on the right. If it returns a command like 'file not found'. Make sure you renamed the recovery-twrp-shooter-1.1.1.img to recovery.img. If it still doesn't work, make sure the recovery file is in the C:\sdk-tools\ folder. Can you just change the command to read "fastboot flash recovery recovery-twrp-shooter-1.1.1.img"? Yes, but it makes the next command tougher to type every time you want to flash something. So renaming it once before you flash is easier than typing it every single time you want to access the recovery through fastboot.

    Now type (or copy/paste):

    Code (Text):
    1. fastboot boot recovery.img
    Step 6) Flashing the ROM

    To flash a ROM/Kernel, do the following:

    1) Go to Wipe Menu

    A) Wipe Cache
    B) Wipe Dalvik Cache
    OPTIONAL) Wipe Everything (Data Factory Reset) - This is useful if you have problems with flashing certain ROMS. Some ROMs require this before flashing. For the stock ROM, this isn't necessary. But you already wiped the device twice already, another time won't hurt.

    2) Go back and now go to Install Zip.

    A) Choose Zip
    B) Go to the folder ROMs/
    C) Select the ROM you want to flash (Shooter_S_Sprint_WWE_2.17.651.5_odex.zip for example)
    D) If you're flashing another kernel, you would find your kernel and by selecting Choose Zip and finding the kernel file. The kernel must be selected AFTER the ROM is selected, or else the kernel built into the ROM will overwrite the kernel you want to flash.
    E) Check 'Reboot After Successful Flash' - this is just a nice feature of TWRP that makes it so you don't have to pay attention to the flashing process.
    F) Flash Zips Now

    3) Sit back and relax. The flash is going to take 3 or so minutes. Then it'll reboot. The reboot will take 5 minutes or so and will always take 5 minutes or so every time you clear out the cache and dalvik cache. It is normal. So let it do it's thing. If 10 minutes goes by, check for bootlooping. Every boot animation has a start animation and then a repeat animation. If you see the start animation a second time in a boot cycle, you may have a bootloop problem. If so, pull out the battery (or push vol up + down + power) then push vol down + power to get into the bootloader. Your USB cable should be connected still, so make sure it shows 'FASTBOOT USB' again. If so, type 'fastboot boot recovery.img' in the command prompt to go back into recovery. Wipe everything again (data, dalvik and cache) and try a reflash.

    If successful, congradulations! You updated your firmware, kernel and ROM!

    (Optional) Installing 4EXT - Highly Recommended!

    There is a recovery that makes it really easy for HBOOT 1.5 people to flash ROMs and kernels. It's called 4EXT Touch Recovery. If you're familiar with ROM Manager, you'll love this app/recovery. You can control every aspect of your phone's recovery from an app. Best of all, even with S-ON Unlocked, you can flash kernels without using fastboot. Just go to their website to get the free version that comes with a 3 day trial of the full version, or get the full version. After you're done with the trial, I'm sure most of you will want the full version. It makes everything easy. I use it, too, and I'm on HBOOT 1.4 :p

    To install, download/install the app (free or paid) and open it. Give it SuperUser permissions and then click through all the pop up dialogs. Push the install button at the top. Indicate if you are S-ON or not (if you had to unlock with HTC, then you click yes). And it installs. And after 5 minutes of running the free version, your trial for the full version starts. So come back in 5 minutes and reload the app (by pushing the back button until you get back to the desktop and relaunch). If you're on the paid version, you can just start using the app immediately.

    Now go to recovery and you can do everything you would normally do in recovery, but it's fully automated once you click start after selecting all your options. Including making backups, wiping caches, and installing ROMs. Remember to support the developers if it makes things a lot easier for you!

    Thanks to jmz for the Stock ROM and RUU, and Granite1 for laying the groundwork for unrooting instructions (http://androidforums.com/evo-3d-all-things-root/539403-3vo-unroot-guide.html) and everyone else that I cited in my rooting guide for some of the commands. :)

  2. thebryceee

    thebryceee Well-Known Member

    For what reason would you update RUU?
  3. jerofld

    jerofld Fixing stuff is not easy VIP Member

    RUUs are like the ultimate recovery tool. If you came from a Motorola phone, a RUU is like a SBF file. If you didn't, it basically reprograms the entire phone to stock conditions. Factory resets just clear the /data and /cache partitions, the RUU will fix /boot, /system, /data, /cache and will reflash the radios.

    It's basically a unbricking tool. It also can be used to upgrade radios/basebands without taking OTAs (that can be problematic for root users).
    stephanos, Rolo42 and Snake X like this.
  4. thebryceee

    thebryceee Well-Known Member

    What improvements will it give (if any) of we are able to update?
  5. jerofld

    jerofld Fixing stuff is not easy VIP Member

    At this point, there will be no improvements, as this RUU is the same version that came stock on your phone.

    Later along in the device's life, HTC will hopefully be making some updates to the radios, making them more power/signal efficient. Then a new RUU will come out and those of you who are S-ON Unlocked will have 2 choices to get the new radios: Unroot and take the OTA and then re-root or relock and run the RUU. I find that running the RUU is better than taking OTAs.
  6. johnny424

    johnny424 Well-Known Member

    hi guys just my evo v today and working on getting this puppy rooted..

    thanks much to the op for taking the time to make this guide but i have a few questions

    for now i am trying to get root access and custom recovery until more roms are available down the road sooo

    do i need to unlock my bootloader before running the ruu or can i skip right to step 3 in the guide and run the ruu?

    step 2 was the lock the bootloader but of course mine is already locked out of box..i have skd-tools downloaded and moved to C:drive i downloaded the twrp recov img. renamed it to recovery.img and moved it into my sdk-tools folder so if im correct i will go straight to step 3 then to 4 to unlock my bootloader for the first time..then to 5 to flash my recovery img?

    any help would be awsome
  7. koopakid08

    koopakid08 Well-Known Member

    If you are just trying to root there is no need to flash the RUU just use the stickied guide.
    johnny424 likes this.
  8. johnny424

    johnny424 Well-Known Member

    well for now i just wanna root and use the ext4 recovery

    the guide from the stickies is the one im following by the way..but im kinda confused im used to samsung phones and odin..at which step do i begin working is where i dont follow..thanks for any help
  9. johnny424

    johnny424 Well-Known Member

    nvm im an idiot..sorry guys
  10. johnny424

    johnny424 Well-Known Member

    to change to a non 3.0 usb port should i just switch to a different port..im getting waiting for device after i typed command for identifier token?

    can i just pull the battery to get out of fasboot and start over once i have switched usb ports? i dont see a reboot option
  11. Mobstergunz

    Mobstergunz Well-Known Member Developer

    2 quick questions does this put the phone back to an out of box state (complete stock) and is it necessary to do s-off to flash Roms and mods?
  12. johnny424

    johnny424 Well-Known Member

    anyone els have trouble with htcdev? im having trouble submitting my token output..i click begin unlock but it does nothing..tried two different browsers
  13. thebryceee

    thebryceee Well-Known Member

    I think when you go to relock it, it'll say "relocked" instead of "locked" so they'll know if you unlocked it before.

    You don't need s-off if you have 4EXT to flash ROMs (and kernels, whenever they release the source codes).
    Mobstergunz likes this.
  14. jerofld

    jerofld Fixing stuff is not easy VIP Member

    Flashing a RUU puts it to complete out-of-box state. If the bootloader is S-ON Unlocked, it'll need to be relocked before the RUU will flash. If the bootloader is S-OFF, then no relocking is necessary and flashing the RUU will leave the bootloader S-OFF. So manual S-ON will need to be done if the user is trying to achieve full stock settings with S-OFF.

    I've been told that flashing the RUU after relocking will revert it from Relocked to Locked, because HBOOT is being written over by a new HBOOT. But HTC will still have the record that you registered for an unlock code.

    They were having troubles the other day. Perhaps try their customer feedback option to see if they can help you further?
    Mobstergunz, johnny424 and thebryceee like this.
  15. johnny424

    johnny424 Well-Known Member

    anyone who has trouble with htcdev...keep trying different browsers..i used three and finnaly got it..one more question though

    i am trying to install the twrp recovery img..i renamed it recovery.img and placed it in my sdk-tools folder

    type fastboot flash recovery recovery.img but im getting back cannot load recovery.img......any suggestions?
  16. agentc13

    agentc13 Daleks Über Alles VIP Member

    Do you have file extensions showing? If not you may have accidentally named it recovery.img.img Check that out and see.
    johnny424 likes this.
  17. johnny424

    johnny424 Well-Known Member

    that is exactly what i did...

    just flashed su a moment ago

    thank you for your help everyone..think i will give s-off a go around later this evening
  18. johnny424

    johnny424 Well-Known Member

    a few more questions...

    so with htc phones you do not need busy box installed? only need to unlock your bootloader?

    i have the twrp recovery installed but if i wanted to switch to ext4 i would just download the paid version of their app?
  19. jerofld

    jerofld Fixing stuff is not easy VIP Member

    Busybox should be installed in the SU Patch. It's just not installed as a stand-alone app like what you may be used to. You can download and install the BusyBox app from GPlay if you so wish, it won't hurt anything.
  20. johnny424

    johnny424 Well-Known Member

    well after i flashed the su patch and booted up..i downloaded some favorite su apps and it prompted for permission and all the root apps work fine..su works fine..but i went to update su binary everything checked off fine except for the busybox installed option..it said busybox not found..which is weird because everything seems to be working fine
  21. 3matthew13

    3matthew13 Well-Known Member

    Relocking and doing the RUU still results in a *RELOCKED* status. I did this before returning my first Evo V.
    jerofld likes this.
  22. lucky257

    lucky257 New Member

    Is there anyway to fix this? I need to return my evo, because it's having that reboot problem.
  23. koopakid08

    koopakid08 Well-Known Member

    I wonder I'd this is a hboot issue. Has anyone that installed three modified hboot tried this?
    lucky257 likes this.
  24. jerofld

    jerofld Fixing stuff is not easy VIP Member

    Hmm...I wonder if you did the S-OFF thing if you could manually flash the HBOOT and it would revert back to *locked* vs *relocked*

    I guess they fixed that from Hboot 1.50. What a shame :(
    lucky257 likes this.
  25. koopakid08

    koopakid08 Well-Known Member

    Do you know how you would go about flashing it manually?

Share This Page