Go Back   Android Forums > Android Phones > HTC EVO V 4G > EVO V 4G - All Things Root

Find everything you need for the Galaxy S5 and discuss it in our S5 forum!
Have you seen that OnePlus One's awesome camera?? The forum is over here!

Like Tree15Likes

test: Reply
 
LinkBack Thread Tools
Old June 8th, 2012, 07:00 AM   #1 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default Evo V 4G RUU Flashing guide / Unroot guide

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:
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:
C:\sdk-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:2048

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:
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 1.06.00.1216. 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:
cd c:\sdk-tools
2) Let's reboot back to the bootloader. Do this by typing:

Code:
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:
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:
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): [hide]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:
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:
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:
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

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.
nannycrick and metal571 like this.

jerofld is offline  
Last edited by Brian706; June 3rd, 2013 at 06:10 PM. Reason: Added working RUU download link
Reply With Quote
The Following 4 Users Say Thank You to jerofld For This Useful Post:
hatredg0d (March 29th, 2014), metal571 (August 17th, 2012), nannycrick (November 16th, 2012), Revenant Ghost (July 7th, 2012)
sponsored links
Old June 8th, 2012, 10:16 AM   #2 (permalink)
Senior Member
 
thebryceee's Avatar
 
Join Date: Feb 2012
Gender: Male
Posts: 2,245
 
Device(s): Nexus⁴, Evo V 4G, Rooted Kindle Fire
Carrier: T-Mobile

Thanks: 140
Thanked 233 Times in 212 Posts
Default

For what reason would you update RUU?
thebryceee is offline  
Reply With Quote
Old June 8th, 2012, 02:32 PM   #3 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

Quote:
Originally Posted by thebryceee View Post
For what reason would you update RUU?
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).
jerofld is offline  
Reply With Quote
The Following 3 Users Say Thank You to jerofld For This Useful Post:
Rolo42 (July 12th, 2012), Snake X (June 9th, 2012), stephanos (August 12th, 2012)
Old June 8th, 2012, 06:35 PM   #4 (permalink)
Senior Member
 
thebryceee's Avatar
 
Join Date: Feb 2012
Gender: Male
Posts: 2,245
 
Device(s): Nexus⁴, Evo V 4G, Rooted Kindle Fire
Carrier: T-Mobile

Thanks: 140
Thanked 233 Times in 212 Posts
Default

What improvements will it give (if any) of we are able to update?
thebryceee is offline  
Reply With Quote
Old June 9th, 2012, 08:41 AM   #5 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

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.
jerofld is offline  
Reply With Quote
Old June 12th, 2012, 12:06 AM   #6 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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
__________________
A simple THANK YOU will do
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 12:34 AM   #7 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

Quote:
Originally Posted by johnny424 View Post
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
If you are just trying to root there is no need to flash the RUU just use the stickied guide.
koopakid08 is offline  
Reply With Quote
The Following User Says Thank You to koopakid08 For This Useful Post:
johnny424 (June 12th, 2012)
Old June 12th, 2012, 12:39 AM   #8 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

Quote:
Originally Posted by koopakid08 View Post
If you are just trying to root there is no need to flash the RUU just use the stickied guide.
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
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 12:41 AM   #9 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

nvm im an idiot..sorry guys
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 12:53 AM   #10 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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
johnny424 is offline  
Last edited by johnny424; June 12th, 2012 at 12:56 AM.
Reply With Quote
sponsored links
Old June 12th, 2012, 01:24 AM   #11 (permalink)
ROM Developer
 
Mobstergunz's Avatar
 
Join Date: Sep 2011
Location: Reading, PA
Posts: 2,896
 
Device(s): Zte Supreme
Carrier: Not Provided

Thanks: 1,058
Thanked 1,446 Times in 773 Posts
Default

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?
__________________
Subscribe to Hatsune Miku you know you want to

If you like what i do, feel free to Donate
Mobstergunz is offline  
Reply With Quote
Old June 12th, 2012, 01:37 AM   #12 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 02:15 AM   #13 (permalink)
Senior Member
 
thebryceee's Avatar
 
Join Date: Feb 2012
Gender: Male
Posts: 2,245
 
Device(s): Nexus⁴, Evo V 4G, Rooted Kindle Fire
Carrier: T-Mobile

Thanks: 140
Thanked 233 Times in 212 Posts
Default

Quote:
Originally Posted by Mobstergunz View Post
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?
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).
thebryceee is offline  
Reply With Quote
The Following User Says Thank You to thebryceee For This Useful Post:
Mobstergunz (June 12th, 2012)
Old June 12th, 2012, 09:50 AM   #14 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

Quote:
Originally Posted by Mobstergunz View Post
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?
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.

Quote:
Originally Posted by thebryceee View Post
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).
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.

Quote:
Originally Posted by johnny424 View Post
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
They were having troubles the other day. Perhaps try their customer feedback option to see if they can help you further?
jerofld is offline  
Last edited by jerofld; June 12th, 2012 at 09:53 AM.
Reply With Quote
The Following 3 Users Say Thank You to jerofld For This Useful Post:
johnny424 (June 12th, 2012), Mobstergunz (June 12th, 2012), thebryceee (June 12th, 2012)
Old June 12th, 2012, 10:31 AM   #15 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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?
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 11:04 AM   #16 (permalink)
Daleks Über Alles
 
agentc13's Avatar
 
Join Date: Aug 2011
Location: Skaro
Posts: 7,839
 
Device(s): HTC One S, Kindle Fire
Carrier: T-Mobile USA

Thanks: 4,106
Thanked 5,382 Times in 2,789 Posts
Default

Quote:
Originally Posted by johnny424 View Post
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?
Do you have file extensions showing? If not you may have accidentally named it recovery.img.img Check that out and see.
agentc13 is offline  
Reply With Quote
The Following User Says Thank You to agentc13 For This Useful Post:
johnny424 (June 12th, 2012)
Old June 12th, 2012, 11:07 AM   #17 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

Quote:
Originally Posted by agentc13 View Post
Do you have file extensions showing? If not you may have accidentally named it recovery.img.img Check that out and see.
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
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 11:13 AM   #18 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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?
johnny424 is offline  
Reply With Quote
Old June 12th, 2012, 12:36 PM   #19 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

Quote:
Originally Posted by johnny424 View Post
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?
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.
jerofld is offline  
Reply With Quote
Old June 12th, 2012, 12:46 PM   #20 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

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
johnny424 is offline  
Reply With Quote
sponsored links
Old June 18th, 2012, 07:25 PM   #21 (permalink)
Member
 
Join Date: May 2012
Location: New Kensington, PA
Posts: 113
 
Device(s): VM EVO V 4G, LG Revolution on Page Plus
Carrier: Not Provided

Thanks: 5
Thanked 71 Times in 11 Posts
Default

Relocking and doing the RUU still results in a *RELOCKED* status. I did this before returning my first Evo V.
3matthew13 is offline  
Reply With Quote
The Following User Says Thank You to 3matthew13 For This Useful Post:
jerofld (June 19th, 2012)
Old June 18th, 2012, 11:04 PM   #22 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by 3matthew13 View Post
Relocking and doing the RUU still results in a *RELOCKED* status. I did this before returning my first Evo V.
Is there anyway to fix this? I need to return my evo, because it's having that reboot problem.
lucky257 is offline  
Reply With Quote
Old June 19th, 2012, 07:33 AM   #23 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

Quote:
Originally Posted by 3matthew13 View Post
Relocking and doing the RUU still results in a *RELOCKED* status. I did this before returning my first Evo V.
I wonder I'd this is a hboot issue. Has anyone that installed three modified hboot tried this?
koopakid08 is offline  
Reply With Quote
The Following User Says Thank You to koopakid08 For This Useful Post:
lucky257 (June 19th, 2012)
Old June 19th, 2012, 08:11 AM   #24 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

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
jerofld is offline  
Reply With Quote
The Following User Says Thank You to jerofld For This Useful Post:
lucky257 (June 19th, 2012)
Old June 19th, 2012, 08:27 AM   #25 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

Quote:
Originally Posted by jerofld View Post
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
Do you know how you would go about flashing it manually?
koopakid08 is offline  
Reply With Quote
Old June 19th, 2012, 08:33 AM   #26 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

Quote:
Originally Posted by koopakid08 View Post
Do you know how you would go about flashing it manually?
I'd like one of the devs to confirm this, but you should be able to delete everything in the RUU that isn't in the HBOOT section and then rename the zip "pg86img.zip" then flash it through the bootloader. But I would wait for a dev to confirm that this could work (like jmz or someone), as if it goes wrong, the device will be bricked. But, the upside would be that they wouldn't be able to tell that you rooted it if the hboot wouldn't boot.
jerofld is offline  
Reply With Quote
The Following User Says Thank You to jerofld For This Useful Post:
lucky257 (June 19th, 2012)
Old June 19th, 2012, 01:01 PM   #27 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by jerofld View Post
I'd like one of the devs to confirm this, but you should be able to delete everything in the RUU that isn't in the HBOOT section and then rename the zip "pg86img.zip" then flash it through the bootloader. But I would wait for a dev to confirm that this could work (like jmz or someone), as if it goes wrong, the device will be bricked. But, the upside would be that they wouldn't be able to tell that you rooted it if the hboot wouldn't boot.
Well, thanks for responding before, but what I believe what my issue was, was just a bad flash to my device. The reason is because ever since I RUU'd it, it hasn't crashed once. It would be nice to know though if there was ever a way to have it say LOCKED again.
lucky257 is offline  
Reply With Quote
The Following User Says Thank You to lucky257 For This Useful Post:
jerofld (June 19th, 2012)
Old June 21st, 2012, 08:14 PM   #28 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

Quote:
Originally Posted by jerofld View Post
I'd like one of the devs to confirm this, but you should be able to delete everything in the RUU that isn't in the HBOOT section and then rename the zip "pg86img.zip" then flash it through the bootloader. But I would wait for a dev to confirm that this could work (like jmz or someone), as if it goes wrong, the device will be bricked. But, the upside would be that they wouldn't be able to tell that you rooted it if the hboot wouldn't boot.
If you take a look at the s off thread, it seems that going through that process will return the bootloader to a locked state as long as you do not install the modified hboot.

So what u am thinking is that if you need to return to stock you could do the s off process, use the fastboot command to put s on and then flash the RUU to go to a complete stock state. Would this work or am I just crazy?
koopakid08 is offline  
Reply With Quote
The Following User Says Thank You to koopakid08 For This Useful Post:
simplyeff (July 24th, 2012)
Old June 22nd, 2012, 09:55 PM   #29 (permalink)
Fixing stuff is not easy
Thread Author (OP)
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

Quote:
Originally Posted by koopakid08 View Post
If you take a look at the s off thread, it seems that going through that process will return the bootloader to a locked state as long as you do not install the modified hboot.

So what u am thinking is that if you need to return to stock you could do the s off process, use the fastboot command to put s on and then flash the RUU to go to a complete stock state. Would this work or am I just crazy?
Sounds logical.
jerofld is offline  
Reply With Quote
Old June 29th, 2012, 12:37 AM   #30 (permalink)
Junior Member
 
Join Date: Jun 2012
Posts: 18
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Is the RUU download link down?
Deathstar is offline  
Reply With Quote
sponsored links
Old June 29th, 2012, 06:18 AM   #31 (permalink)
Senior Member
 
Join Date: May 2011
Posts: 1,319
 
Device(s):
Carrier: Not Provided

Thanks: 59
Thanked 1,586 Times in 442 Posts
Default

Quote:
Originally Posted by Deathstar View Post
Is the RUU download link down?
The link works fine now. I just tested it. In case you didn't find it, it's under the Show under Step 1.

Edit: I should say that I'm on a computer in case you're not.
mantera is offline  
Last edited by mantera; June 29th, 2012 at 06:21 AM.
Reply With Quote
Old June 29th, 2012, 12:54 PM   #32 (permalink)
Junior Member
 
Join Date: Jun 2012
Posts: 18
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by mantera View Post
The link works fine now. I just tested it. In case you didn't find it, it's under the Show under Step 1.

Edit: I should say that I'm on a computer in case you're not.
Thanks!

It does work now, how convenient.
Deathstar is offline  
Reply With Quote
Old July 7th, 2012, 05:47 PM   #33 (permalink)
The Undead Flashaholic
 
Revenant Ghost's Avatar
 
Join Date: Jun 2012
Location: Hell
Posts: 1,269
 
Device(s): HTC Evo V 4G with Negalite-Blurom and Buttered Toast Kernel
Carrier: Virgin Mobile

Thanks: 389
Thanked 415 Times in 322 Posts
Default

Thank you so much for helping me fix my phone. I was at my wit's end with the constant bootloops from flashing the Anthrax kernel with an incompatible ROM, until I found this guide. Thanks again.
Revenant Ghost is offline  
Reply With Quote
Old July 15th, 2012, 08:13 PM   #34 (permalink)
Junior Member
 
Join Date: May 2011
Location: Milwaukee
Posts: 78
 
Device(s): EVO V 4G 3D MOTOROLA TRIUMPH
Carrier: Not Provided

Thanks: 9
Thanked 13 Times in 6 Posts
sanman1185@gmail.com
Default

Quote:
Originally Posted by Deathstar View Post
Thanks!

It does work now, how convenient.

It's down now lol...
sanman1185 is offline  
Reply With Quote
Old July 24th, 2012, 08:20 PM   #35 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 18
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by koopakid08 View Post
If you take a look at the s off thread, it seems that going through that process will return the bootloader to a locked state as long as you do not install the modified hboot.

So what u am thinking is that if you need to return to stock you could do the s off process, use the fastboot command to put s on and then flash the RUU to go to a complete stock state. Would this work or am I just crazy?
Thanks for this tip. I went s-off, ran the RUU, ran the "fastboot oem writesecureflag 3" command to s-on, and am now completely stock out of box.
simplyeff is offline  
Reply With Quote
Old July 31st, 2012, 08:15 PM   #36 (permalink)
Senior Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

I'm going to need this guide soon, can we get the hidden parts shown to circumvent the site's current issues?
metal571 is offline  
Reply With Quote
Old July 31st, 2012, 08:17 PM   #37 (permalink)
Daleks Über Alles
 
agentc13's Avatar
 
Join Date: Aug 2011
Location: Skaro
Posts: 7,839
 
Device(s): HTC One S, Kindle Fire
Carrier: T-Mobile USA

Thanks: 4,106
Thanked 5,382 Times in 2,789 Posts
Default

Quote:
Originally Posted by metal571 View Post
I'm going to need this guide soon, can we get the hidden parts shown to circumvent the site's current issues?
Yeah, I will edit the OP.
metal571 likes this.
agentc13 is offline  
Reply With Quote
The Following User Says Thank You to agentc13 For This Useful Post:
metal571 (July 31st, 2012)
Old August 1st, 2012, 01:12 AM   #38 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default mini SDK

Links to download the mini SDK are dead (%1$s)

Where to get this mini SDK ?

thanks a lot
copinyann is offline  
Reply With Quote
Old August 15th, 2012, 02:59 PM   #39 (permalink)
Senior Member
 
richking34's Avatar
 
Join Date: Jan 2012
Posts: 567
 
Device(s): Galaxy S3, Nexus 7
Carrier: Not Provided

Thanks: 0
Thanked 41 Times in 40 Posts
Default

please re upload the ruu!!!
__________________
Galaxy S3 LS
richking34 is offline  
Reply With Quote
Old August 17th, 2012, 10:30 PM   #40 (permalink)
Senior Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

That was scary, but worked for me. I had the RUU saved, and another thread has it posted already. This needs to be updated though.

You might want to mention that the bootloader can say "relocked" and not "locked" and also that a security warning can appear on the bootloader preventing you from booting to your ROM after issuing fastboot oem unlock. The whole process worked fine for me otherwise, however.
metal571 is offline  
Reply With Quote
sponsored links
Old August 17th, 2012, 11:50 PM   #41 (permalink)
Senior Member
 
johnny424's Avatar
 
Join Date: Nov 2011
Location: Washington Dc
Posts: 1,499
 
Device(s): AT&T SGS3-Google Nexus 7
Carrier: AT&T

Thanks: 435
Thanked 464 Times in 270 Posts
Default

I ran it with an u locked boot loader...after competition boot loader still says unlocked..still s off as well of course
johnny424 is offline  
Reply With Quote
Old August 18th, 2012, 01:23 AM   #42 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

Quote:
Originally Posted by metal571 View Post
That was scary, but worked for me. I had the RUU saved, and another thread has it posted already. This needs to be updated though.

You might want to mention that the bootloader can say "relocked" and not "locked" and also that a security warning can appear on the bootloader preventing you from booting to your ROM after issuing fastboot oem unlock. The whole process worked fine for me otherwise, however.
The only way to change it to locked is to go s-off, run the RUU, then do the fastboot command to put s-on.

Not that anyone actually checks the hboot for returns.
koopakid08 is offline  
Reply With Quote
Old August 18th, 2012, 01:27 AM   #43 (permalink)
Senior Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by koopakid08 View Post
The only way to change it to locked is to go s-off, run the RUU, then do the fastboot command to put s-on.

Not that anyone actually checks the hboot for returns.
Yeah I'm aware of that. I'm just saying for people who aren't doing S-OFF (probably very few people in this community at this point, lol) shouldn't get startled by "relocked" or "security warning" when they first relock their bootloader, because it's not going to say "locked" again unless you're S-OFF to my knowledge.
metal571 is offline  
Reply With Quote
Old September 1st, 2012, 06:49 PM   #44 (permalink)
jmz
Senior Member
 
jmz's Avatar
 
Join Date: Apr 2010
Posts: 562
 
Device(s):
Carrier: Not Provided

Thanks: 9
Thanked 572 Times in 192 Posts
Default

the ruu isn't on goo anymore. the updated link is at Shooter

I can't allow hotlinking though.
__________________
If you like my work feel free to donate
Or pick up my donation app on the android market
Follow me on Twitter
jmz is offline  
Reply With Quote
Old September 3rd, 2012, 07:38 PM   #45 (permalink)
Junior Member
 
Join Date: Sep 2011
Posts: 49
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

So if I want to put the phone back to 100% stock, do I only needs to do steps 1-3? The rest has you unlocking it and putting a rom back on?
hdv1990 is offline  
Reply With Quote
Old September 3rd, 2012, 08:13 PM   #46 (permalink)
Senior Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by hdv1990 View Post
So if I want to put the phone back to 100% stock, do I only needs to do steps 1-3? The rest has you unlocking it and putting a rom back on?
Correct
metal571 is offline  
Reply With Quote
Old September 5th, 2012, 04:53 PM   #47 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 0 Times in 0 Posts
Default "fastboot oem lock" command error

Hello! I am having trouble with the "fastboot oem lock" command, when I try to run it I get an error, ".... info [err] command error!!!" What does this mean?

I'm trying to go back to stock to then root and leave s-on.

At the moment im rooted with s-off and hboot 1.04.2000

Any help is greatly appreciated Thanks
screener06 is offline  
Last edited by screener06; September 5th, 2012 at 05:02 PM.
Reply With Quote
Old September 6th, 2012, 04:14 AM   #48 (permalink)
jmz
Senior Member
 
jmz's Avatar
 
Join Date: Apr 2010
Posts: 562
 
Device(s):
Carrier: Not Provided

Thanks: 9
Thanked 572 Times in 192 Posts
Default

Quote:
Originally Posted by screener06 View Post
Hello! I am having trouble with the "fastboot oem lock" command, when I try to run it I get an error, ".... info [err] command error!!!" What does this mean?

I'm trying to go back to stock to then root and leave s-on.

At the moment im rooted with s-off and hboot 1.04.2000

Any help is greatly appreciated Thanks
If you used joupunutbear s-off then you need to do the instructions in my thread
jmz is offline  
Reply With Quote
The Following User Says Thank You to jmz For This Useful Post:
screener06 (September 6th, 2012)
Old September 6th, 2012, 10:50 AM   #49 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 0 Times in 0 Posts
Default

Thats exactly the case I am currently on jounupus-s off, Ill do what you suggested and use the instructions found on Juopunutbear S-OFF page on removing s-off

Herez the Link for simplicity.... http://androidforums.com/evo-v-4gall-things-root/558583-s-off-juopunutbear-s-off-beta-release.html


Thanks
screener06 is offline  
Last edited by screener06; September 6th, 2012 at 11:36 AM.
Reply With Quote
Old September 6th, 2012, 11:37 AM   #50 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 0 Times in 0 Posts
Default

Is installing this RUU the only way to upgrade the hboot back to stock?
screener06 is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > HTC EVO V 4G > EVO V 4G - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 01:49 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.