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

Root ROOTING For Dummies Guide.....the Gingerbread Edition

No problem. I would try the RUU that you run from your pc rather than the PC36IMG file that Mike is referring to. It seems that many have more luck with it.

When I tried that moments ago, everything seemed to be working fine... it said, updating image version 3.29.651.5 to 3.70.651.1. I then rebooted the phone, returning to an "HTC" screen. The PC screen showed "Waiting for bootloader" for about 2 min - then errored out saying it couldn't connect to the phone. Seconds later, the phone rebooted, and came back up to the original MIUI.

Seems like I'm striking out on all attempts.
 
When I tried that moments ago, everything seemed to be working fine... it said, updating image version 3.29.651.5 to 3.70.651.1. I then rebooted the phone, returning to an "HTC" screen. The PC screen showed "Waiting for bootloader" for about 2 min - then errored out saying it couldn't connect to the phone. Seconds later, the phone rebooted, and came back up to the original MIUI.

Seems like I'm striking out on all attempts.
Not sure where to go from here. Hang in here and someone with more experience will post another solution.
 
When I tried that moments ago, everything seemed to be working fine... it said, updating image version 3.29.651.5 to 3.70.651.1. I then rebooted the phone, returning to an "HTC" screen. The PC screen showed "Waiting for bootloader" for about 2 min - then errored out saying it couldn't connect to the phone. Seconds later, the phone rebooted, and came back up to the original MIUI.

Seems like I'm striking out on all attempts.

That is the wrong software version for hboot 2.16. That might be the issue. Did you try the RUU that Mike linked you too a few posts back? That should be the RUU for the current release.
 
That is the wrong software version for hboot 2.16. That might be the issue. Did you try the RUU that Mike linked you too a few posts back? That should be the RUU for the current release.

Nope... I didn't. I assumed his link was a c/p from the guide, and didn't pick up on the diff version number. DLing now and will report results!
 
Regretfully, I'm getting the same timeout error while 'waiting for bootloader'. The PC software says to check if the phone is connected - but when I click Exit, it prompts the phone to reboot. So the connection is there.

[edited to add]

And to confirm, the RUU now says updating from 3.29.651.5 to 4.54.651.1
 
Hmm Im wondering if MIUI is causing this due to it being a ported rom from china, Can you still get into recovery and flash a rom?
 
Not sure that the rom itself resides low enough in the system to allow it to interfere though it might be possible.....

You might try and run revolutionary on it again to see if it will turn s-off again. Starting to reach for things now :)
 
Hmm Im wondering if MIUI is causing this due to it being a ported rom from china, Can you still get into recovery and flash a rom?

Absolutely. I'm back to square one. Fully functional, rooted, with my normal OS on it. I see where you're going, and can try that... For now, I've re-run the revolution root routing to get me back to s-off. I'm going to repeat everything I've tried earlier again.

When I first rooted this phone two years ago, it was using a completely different method. So I figure rooting it using the current method may prove to be useful. If that doesn't work, I now know how to get back to this point. And from here, I'll then install a more conventional US-based ROM.
 
Absolutely. I'm back to square one. Fully functional, rooted, with my normal OS on it. I see where you're going, and can try that... For now, I've re-run the revolution root routing to get me back to s-off. I'm going to repeat everything I've tried earlier again.

When I first rooted this phone two years ago, it was using a completely different method. So I figure rooting it using the current method may prove to be useful. If that doesn't work, I now know how to get back to this point. And from here, I'll then install a more conventional US-based ROM.

If you rooted 2 years ago, how did you end up with hboot 2.16? Did you unroot or flash a more current hboot version somewhere along the way? Strange thing with revolutionary is that from my memory, it would not work to get s-off again unless you were fully unrooted. Might be that the phone was full security on and not allowing the RUU to run due to that. This is just conjecture at this point. Lets see what happens when you flash to something more normal or sense based and try and unroot from there.

Just to make sure, your hboot is 2.16 and not 2.10 correct?
 
If I told you anything other than "I don't know", I'd be lying. I really don't remember how or what I did since then. I just remember it being a nearly day-long thing, with all sorts of adb commands and sweating blood, just knowing I was going to brick my 1 week old EVO. In any case, running the revolution now did restore the S-OFF. Unfortunately, even with this, the RUU still hangs waiting on the bootloader.

Off to try steps 1 & 2 again...
 
Ok, just making sure because 2.16 is the hboot that came with the OTA update from June of 2011. If your Evo older, then it should have a lower hboot version unless you updated it for some reason along the way.
 
Did it hang or error out If i remember it took about 7 or 8 min to do the whole process. Its basicly replacing the recovery and rom It will also cycle fast boot a few times.
 
Did it hang or error out If i remember it took about 7 or 8 min to do the whole process. Its basicly replacing the recovery and rom It will also cycle fast boot a few times.

No, it errored out on the PC. The phone shows a black screen with a shiny 'htc', and the PC status window says "waiting on bootloader" after about two minutes, the PC says it cannot connect to the phone. The phone stays in the 'htc' mode until I click exit/ok on the PC error box - at which point the phone reboots unchanged.
 
No, it errored out on the PC. The phone shows a black screen with a shiny 'htc', and the PC status window says "waiting on bootloader" after about two minutes, the PC says it cannot connect to the phone. The phone stays in the 'htc' mode until I click exit/ok on the PC error box - at which point the phone reboots unchanged.

Have you tried the PC36IMG file for 4.54? I know you had tried some others but not sure if that was on the list or not.

Are you using the original HTC cable or a replacement? Do you have adb installed on your pc by chance?
 
Alright... some success! After applying the revolutionary root, I re-ran the steps given under the tutorial here; renaming the 200mb file to PC36IMG - and this time, it went through each of the 8 steps without a reboot! It did flag the bootloader as 'bypassed' stating, "can not roll back hboot version". I assume this will be taken care of with step 2 (the s-on step)?
 
Alright... some success! After applying the revolutionary root, I re-ran the steps given under the tutorial here; renaming the 200mb file to PC36IMG - and this time, it went through each of the 8 steps without a reboot! It did flag the bootloader as 'bypassed' stating, "can not roll back hboot version". I assume this will be taken care of with step 2 (the s-on step)?
That should be right Make sure you remove the ruu PC36 file before puting the other one on.
 
Alright... some success! After applying the revolutionary root, I re-ran the steps given under the tutorial here; renaming the 200mb file to PC36IMG - and this time, it went through each of the 8 steps without a reboot! It did flag the bootloader as 'bypassed' stating, "can not roll back hboot version". I assume this will be taken care of with step 2 (the s-on step)?
Ok I was wondering if you got this done?? I have some new info Today at work I tried to unroot a guys evo running mikg and both ruu files failed because the version was a missmatch Mik is using mikg as the rom version now and im assuming MIUI is doing something the same. I had to first flash a sense rom with the same version format IE 4.54.000.0. It seems if the format on the phone is different it fails. Just an fyi for anyone else running into this problem.
 
Back
Top Bottom