Yes, after installing Recovery Control (or Recovery Updater), it will ask if you are S-ON / Unlocked with HTC dev. You say yes and it will make it so you will not need to use fastboot except with some experimental ROMs. (Like the Sense 4.0 ROMs require fastboot) I have a guide on how to set up the Android SDK here: http://androidforums.com/evo-3d-all...ng-fastboot-updated-3-17-a-2.html#post4131303
That's what I followed for the full sdk but the sdk manager never opened after the install to do the rest and I can't get it to open now.
Something must be wrong with your computer if it can't load fastboot via mini-sdk and android SDK. Try a reboot and maybe even disabling your anti-virus/firewalls before your next attempt. I have Comodo firewall and it tries to block fastboot all the time.
I've found its best to this with a Windows XP computer. For the newbies Windows 7 may pose some challenges. by the way if you are running this on windows 7... make sure you open command prompt as an administrator. Right click and click run as administrator.
Is it possible to undo the HTCdev unlock and root process. Im just trying to gauge if this will insta-kill any warranty claim.
It will say "Re-Locked" at the top if you unlock and then lock, again. So the watermark will always be there.
Don't you just need a stock RUU? http://www.pocketables.com/2011/08/...-evo-3d-back-to-an-unrooted-s-on-state-1.html
That video pre-dates the HTC method. Also, in order to flash a RUU, you need to lock the device, first. I don't recall if flashing a RUU will revert it from Re-Locked to simply Locked, but I don't think it does. And that RUU listed in the guide you linked is an older Sprint one. It won't flash on a 1.5x HBOOT, as you have to flash the same revision or a higher one unless you're S-OFF.
Your RUU has to flash the version for your phone or it won't work. So to be able to flash on on the Evo V 4g, you would need that specific RUU (and I don't think it has been leaked yet). I do believe it restores it to "Locked" on the bootloader though (at least I am pretty sure it did for my One S, and I would assume it would be the same for any device).
So basically, we need to wait for the RUU to leak to return to complete stock? Or if we have S-off, could we use a sprint RUU and then turn S-on using fastboot? EDIT: It looks like flashing an RUU does restore it to locked. From XDA:
At this point I have: Downloaded and installed JDK and JRE SDK Tools The Recovery Image The Full SDK I have opened the command prompt with and without adminstrator. I have disabled the virus software. Have had the phone connected and not connected when trying. Even had it in bootloader mode once. And I still get the fastboot error in the command prompt window. It switches to the sdk-tools fine but as soon as i type in fastboot I get the error. I greatly appreciate everyones help and suggestions but this seems to be getting nowhere slowly.....Apparently not enough of an android ninja to pull this off.
Well, you need to make sure you are in that directory (in cmd.exe) in order to do the fastboot command. So C:\Program Files (x86)\Android\android-sdk\platform-tools is where the fastboot.exe is? Did you cd to the correct place?
What are the odds that the RUU will leak for the EVO V? I pretty much know Ill root it the second I activate it (waiting till the end of the billing cycle 6/11). But god forbid something were to happen to it I would love the ability to reset the things back to default for warranty purposes.
There are ruu leaks out already. I just need someone to post their software version. If the leaks aren't the shipped version I can get the shipped version
Thanks for the great guide! Followed it and it all went down just like you said. One thing was different, flashing the rom was very fast for me, seconds actually... it was so fast, the first time I didn't even see what happened, it rebooted and I assumed it f'd up. Did it again and it was just as fast but saw that the messages looked ok, sure enough it was rooted.
thanks for the great guide. It worked for me. I have one feedback. I can't find in it where it actually says to flash the superuser zip. I haven't put a new rom on it yet. It took me flashing the superuser zip three times to actually get root. Otherwise everything went great.