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

Root Evo V 4G RUU Flashing guide / Unroot guide

If you're talking about the hboot, it is not. It is 1.04.

I think that's where your error might be coming from. You should be on a stock bootloader. If returning completely to stock, you should just use the RUU. It will return everything to stock.

Also, should the phone still be in bootloader when I run the RUU.exe, or should it be just connected while in the normal mode?

I've ran it from both successfully before. One time I had a problem running it while booted up and it worked from the bootloader so, I guess it depends. Seems like most times it's recommended to run from the bootloader though.
 
  • Like
Reactions: Kamau
Upvote 0
I think that's where your error might be coming from. You should be on a stock bootloader. If returning completely to stock, you should just use the RUU. It will return everything to stock.



I've ran it from both successfully before. One time I had a problem running it while booted up and it worked from the bootloader so, I guess it depends. Seems like most times it's recommended to run from the bootloader though.

Yep, that is what it was. I just ran the RUU.exe, and it says locked after it finished. I also just flashed the odex stock rom, it rebooted, and now it has that annoying song at boot (which I was was estatic to get rid of).
Thanks for your help.
 
Upvote 0
My phone is S-Off. It was doing a few strange things. Hot reboots would hang on multiple roms. I had tried to flash back to the 1.14 update after doing the "turn your phone into an EVO 3D" thing and that did not work.

I decided to RUU. It worked, although I had to use the zip method.

When I tried to flash a recovery it would not take. Then I unlocked the bootloader again and the recovery flashed. In the bootloader it says "Unlocked" and S-Off and it appears to behave like an S-Off phone. The hot reboot problem is gone.

Is this result normal for doing an RUU on a phone that is S-Off and re-rooting it? This probably does not come up much because phones are unrooted to be sold or returned.
 
Upvote 0
When I tried to flash a recovery it would not take. Then I unlocked the bootloader again and the recovery flashed. In the bootloader it says "Unlocked" and S-Off and it appears to behave like an S-Off phone. The hot reboot problem is gone.

Is this result normal for doing an RUU on a phone that is S-Off and re-rooting it? This probably does not come up much because phones are unrooted to be sold or returned.
That's the difference between radio S-OFF and hboot S-OFF which are explained further in this post. Once you are radio S-OFF it is not necessary to unlock the bootloader to enable the restricted fastboot commands since you can use a custom hboot instead.

If you do unlock the bootloader after gaining radio S-OFF and want to return to 100% stock there are now zip files in this post thanks to scotty85 and brian706 that can set your bootloader back to "locked" status instead of the "relocked" that the "fastboot oem lock" command sets and flags that your phone has been modified at some point.

ramjet73
 
  • Like
Reactions: Brian706
Upvote 0
Ramjet, thank you for the information. My question now is absent the need to set the phone to stock at this time and having no plans to use a rom that that requires other than hboot 1.57, do I need to flash one of the custom bootloaders and relock the phone? Can I flash a custom bootloader and not relock?

Instead of unlocking the bootloader as I did, could I have simply flashed a custom bootloader using a PG86IMG.ZIP in the root of my sdcard and then used fastboot to flash a recovery?

I kind of think the answers are that I don't have to look the bootloader unless I need to do another ruu. If I need another bootloader with a lower version, I can flash it and not lock the bootloader. As for the second paragraph, I suspect I could have done that and eliminated the need to generate another unlock code, as I had deleted the original. I suspect locking of the bootloader is a side effect of the s-off procedure which is why a flashing a custom bootloader is part of the package/s-off procedure.
 
Upvote 0
Ramjet, thank you for the information. My question now is absent the need to set the phone to stock at this time and having no plans to use a rom that that requires other than hboot 1.57, do I need to flash one of the custom bootloaders and relock the phone? Can I flash a custom bootloader and not relock?
Yes, you can flash a custom hboot without relocking but that's probably not necessary at this point since you already unlocked.

Instead of unlocking the bootloader as I did, could I have simply flashed a custom bootloader using a PG86IMG.ZIP in the root of my sdcard and then used fastboot to flash a recovery?
Yes.

I kind of think the answers are that I don't have to look the bootloader unless I need to do another ruu. If I need another bootloader with a lower version, I can flash it and not lock the bootloader. As for the second paragraph, I suspect I could have done that and eliminated the need to generate another unlock code, as I had deleted the original. I suspect locking of the bootloader is a side effect of the s-off procedure which is why a flashing a custom bootloader is part of the package/s-off procedure.
You don't need to lock the bootloader to flash an RUU after you are S-OFF. I haven't unlocked/locked/relocked since gaining S-OFF. The only thing that might be needed at this point is to flash the zip that locks your bootloader if you ever need to return to 100% stock.

ramjet73
 
Upvote 0
Now here is where things get strange. I flashed Hboot 1.04 EN and hot reboots started to hang again. Uh oh, and I don't think this is normal. Then I flashed jupnautbear 1.57.5757. It is contained in a zip file that is downloaded from unlimited.io with the wire trick exploit. The zip has to be renamed PG86IMG.zip for it to flash. That worked and the hot reboots started working again. Perhaps I could have done this instead of an RUU. The odd part is in the hboot it no longer reads locked or unlocked at the top. Instead it reads Jumpnaut, or something like that. I have never seen this before.

I don't know if this last flash fixed things permanently and I am a bit afraid to flash 1.04 EN again. Will roms that will not work with stock 1.57 work with Jumpnautbear 1.5757?

I suspect this weirdness is related to the S-Off which did not terminate normally. The process hung at the end but when I tried it again, it said I had s-off and exited.

Any ideas?
 
Upvote 0
Thanks! This may be seen as a stupid question, but where can I check whether my bootloader is locked, unlocked or relocked? I went to the bootloader, but I don't see any of these listed anywhere.

It usually says it on the bootloader screen. I am guessing you are on a custom hboot which hides that information.

My guess would be that you are locked. If you did s-off and had it flash a custom hboot, then you would still be LOCKED as the wire trick returns you to LOCKED. Unless you physically unlocked the bootloader again, it should still be locked.

Also, the RUU would return you to a stock hboot which then would display locked or unlocked at the top.
 
Upvote 0
It usually says it on the bootloader screen. I am guessing you are on a custom hboot which hides that information.

My guess would be that you are locked. If you did s-off and had it flash a custom hboot, then you would still be LOCKED as the wire trick returns you to LOCKED. Unless you physically unlocked the bootloader again, it should still be locked.

Also, the RUU would return you to a stock hboot which then would display locked or unlocked at the top.

Thanks! I mainly just need to make sure I'm on the stock bootloader (I don't even know how to get a different bootloader...the hboot isn't the bootloader is it?) so that I don't brick my phone in trying to flash RUU. I flashed back my hboot to 1.57 so hopefully that will show whether its locked or not.
 
Upvote 0
Thanks! I mainly just need to make sure I'm on the stock bootloader (I don't even know how to get a different bootloader...the hboot isn't the bootloader is it?) so that I don't brick my phone in trying to flash RUU. I flashed back my hboot to 1.57 so hopefully that will show whether its locked or not.

Hboot is the bootloader. Hboot 1.57.0000 is stock and should show the lock flag status. If it's 1.57.5757 that is the juopunutbear modified hboot.
 
Upvote 0
I never thought I would ever have to run the RUU, so I've basically glossed over anything related to RUU. But now, I think I want to learn RUU-ness. The one thing that caught my attention was that there is an extra step that needs to be taken before one can RUU, and I can't remember what the hell it is. I've seen Brian link people over to XDA for more info. It's also probably in a guide somewhere.

Given the recent OTA, there's been a lot of chatter about RUU lately, and to me, all the threads are starting to run together.

My phone is effectively at JoeBlow status with 1.50 JBEAR and S-OFF plus Unlocked. Is the Jefofld guide a good place to start, or is it a dated guide? Is there something mroe current I should be looking at?
 
Upvote 0
omg no matter WHAT I try, I am always getting error 140. I checked the ruu log in my C drive and I get this bit:

<T092439><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T092439>
<T092439><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>

I tried the zip image for flashing but that won't work either. I don't know what I could have done to it to make it not work anymore D:

Oh, if this helps, I got an error sign at some point when I tried to relock the bootloader in the command prompt but it did say relocked nonetheless...
 
Upvote 0
omg no matter WHAT I try, I am always getting error 140. I checked the ruu log in my C drive and I get this bit:

INFOchecking main version...

FAILED (remote: 43 main version check fail)

I tried the zip image for flashing but that won't work either. I don't know what I could have done to it to make it not work anymore D:

Oh, if this helps, I got an error sign at some point when I tried to relock the bootloader in the command prompt but it did say relocked nonetheless...

If you have taken the November update, you need to flash a zip through recovery before you can run the Ruu. If you have taken the March ota update, unfortunately there is no ruu if you are s-on. So if you didn't take this months update, flash this through your recovery:
http://db.tt/JUdxrcC0

I got this from Ramjet73 at XDA. Normally I would link but I'm on my phone and don't want to try and find it :p
 
  • Like
Reactions: ramjet73
Upvote 0
I never thought I would ever have to run the RUU, so I've basically glossed over anything related to RUU. But now, I think I want to learn RUU-ness. The one thing that caught my attention was that there is an extra step that needs to be taken before one can RUU, and I can't remember what the hell it is. I've seen Brian link people over to XDA for more info. It's also probably in a guide somewhere.

Given the recent OTA, there's been a lot of chatter about RUU lately, and to me, all the threads are starting to run together.

My phone is effectively at JoeBlow status with 1.50 JBEAR and S-OFF plus Unlocked. Is the Jefofld guide a good place to start, or is it a dated guide? Is there something mroe current I should be looking at?

Basically if you are s-off, you can always run the Ruu. Doesn't matter if you are unlocked and doesn't matter if you are trying to downgrade.

S-on has to lock bootloader before running the Ruu. Unfortunately there is only one version of the ruu. The original release... So after the November update, the main version got updated and people couldn't run the Ruu because of the main version check. The ruu won't let you downgrade. Ramjet73 put together a flashable zip that will lower your main version thus allowing you to run the Ruu.

Now with the March update, the bootloader got updated as well. The ruu also checks the hboot before running and will not allow you to downgrade. Naturally if you are s-off it will just run. No security checks are being done. But for s-on users, they are stuck without an ruu unless they get s-off or someone gets a hold of the ruu from htc.
 
Upvote 0

BEST TECH IN 2023

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

Smartphones