• 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

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.
 
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.
 
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?
 
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.
 
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. :)
 
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.
 
I'm going to need this guide soon, can we get the hidden parts shown to circumvent the site's current issues?
 
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.
 
I ran it with an u locked boot loader...after competition boot loader still says unlocked..still s off as well of course
 
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.
 
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.
 
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?
 
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
 
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
 
Back
Top Bottom