• 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

wow. i've gotten WAYYYYYY FURTHERRRRRRR sorry for being such a noob - i'm now on this part..

4.it will detect your phone's specific serial number. use that to generate the beta key on the revolutionary website.

i have followed all of the directions. plugged my phone to my computer - charge only - and it just sits there when i run the file..

did you turn on usb debugging? also make sure that htc sync and any other programs that can sync to your phone like doubletwist or pdanet is uninstalled.
 
Hey, loaded the latest mikmik rom and it appears my SU privileges don't seem to be working... I try to load Ti backup and a number of other apps that require su and the su or root privileges keep failing...

Any suggestions? I have HBoot 6.16.1.0002 (or the like). I did the Gingerbreak...

But it is up n running! WOO to the HOO!

D'ohBoy
 
Hey, loaded the latest mikmik rom and it appears my SU privileges don't seem to be working... I try to load Ti backup and a number of other apps that require su and the su or root privileges keep failing...

Any suggestions? I have HBoot 6.16.1.0002 (or the like). I did the Gingerbreak...

But it is up n running! WOO to the HOO!

D'ohBoy

Update su or you can also flash the older su in recovery. This should solve su privileges error

Did you flash 2.59? I believe this issue was taken care of
 
For those of you who have gotten stuck at the with the "Waiting for device" on the DOS window, I was having the same problem. What I found was that the sticker on the back of my phone had one digit off from what the serial number was in the DOS window. I plugged the serial number from the DOS window into the beta key generator and it worked just fine.

Hope that helps anybody who was having that problem.
 
For those of you who have gotten stuck at the with the "Waiting for device" on the DOS window, I was having the same problem. What I found was that the sticker on the back of my phone had one digit off from what the serial number was in the DOS window. I plugged the serial number from the DOS window into the beta key generator and it worked just fine.

Hope that helps anybody who was having that problem.

thanx for that tip. i was not aware of that.
 
Thanks, root and su and with the latest from mikmik. Thanks again to all who have helped me here on this forum directly and by making the info available, you guys rock!

D'ohBoy
 
I need some help. I can't find superuser su-2.3.6.3-efgh-signed.zip on my phone and I do not know what to do in terms of the rooting process without it. Don't want to brick my phone
 
The only zips that come up are LOST.DIR, rosie.scroll, and rssreader.

well where did you place it when you transfered the file over? if you do not have it, then in recovery there should be under mounts and storage, a usb toggle. you can then transfer the file over and flash it in recovery.
 
Hi...couple questions I had that seemed to get overlooked so bumping up with a quote....thanks for looking...

First thing you do is make a nandroid of you current setup then make a nandroid of ONLY your wimax keys and save that somewhere safe. Then flash a custom rom and have fun. :D

I've previously made a nandroid of only my wimax keys but I have also extracted my keys using a method at the XDA forums (link and method escapes me at the moment, sorry...perhaps someone can post the link if they have it available.

I was wondering the process for restoring the keys for EACH of the options above (nandroid and extracted)?? Does one simply flash the wimax key-only nandroid to restore?? Is the use of one method easier than the other??

...and I just realized another question: is it suggested to make a nandroid of JUST the Wimax keys or the first three options in Amon RA AND sd-ext AND the Wimax keys all in one nandroid??

THANKS!!
 
Hi...couple questions I had that seemed to get overlooked so bumping up with a quote....thanks for looking...

ok so to get your wimax keys back onto your phone use this thread:http://forum.xda-developers.com/showthread.php?t=1127250.

i keep one nandroid backup that has the first three backed up and my wimax key on my computer and dropbox. this was of the stock rom when i first rooted my phone. it is mainly for the wimax keys. so when you make a nandroid backup for safe keeping, i guess just backing up your wimax would be ok. but for me it also so i can go back to stock albeit it will be froyo stock.
 
ok so to get your wimax keys back onto your phone use this thread:[HowTo] restore RSA key using Terminal Emulator - xda-developers.

i keep one nandroid backup that has the first three backed up and my wimax key on my computer and dropbox. this was of the stock rom when i first rooted my phone. it is mainly for the wimax keys. so when you make a nandroid backup for safe keeping, i guess just backing up your wimax would be ok. but for me it also so i can go back to stock albeit it will be froyo stock.

That was a quick reply, thanks for the suggestions and the link!!

Question...at the XDA link, step one states:

1. Assume you backed up your RSA key and have wimax.img file somewhere

If I have done, as YOU have done, a Amon RA nandroid backup of the first three backup options PLUS the wimax keys, then what is/where is this "wimax.img file" that the XDA post is referring to? Do I need to extract something or rename something?? Is what HE is referring to a nandroid backup of ONLY the wimax keys for flashing and he renamed the nandroid??

THANKS!!

------------
EDIT: IMPORTANT NOTE!!

After posting the above, I did a little looking/research into the Amon Ra nandroid backups that I had on my phone and saved to my computer. I asked about the "wimax.img" file mentioned in the XDA post and FOUND what that was.

If you create a nandroid backup of the "first three options" plus your SD-ext data, the nandroid folder is named something like this:

BDES - 20111022-0646

The number portion is the date and time of the backup. BDES stands for back files of "boot.img" "data.img" "ext.img" (for SD-external I would imagine) and "system.img."

If, as is often suggested, you do NOT backup your wimax keys with each and every backup, your BDES or similar nandroid will NOT have your wimax keys in an image file.

I DO have a Amon Ra nandroid backup of ONLY my wimax keys and the ONLY img file in that backup is: wimax.img

So, I answered my own question above as it appears that the "wimax.img" file that is necessary to restore your keys as directed in the XDA post is found right there in the nandroid folder!! :)

So, I helped myself...hope I helped someone else as well! :D
 
Just making sure, but when this guide was initially released, I rooted my EVO for the first time. Everything went smoothly.

Now I want to upgrade to the newest software version.. all I need to do is place it on my SD card and then go through BootLoader and upgrade? I won't need to update anything else, it'll work without a problem?

This is the ROM I'm talking about...

[ROM][STOCK][10/25/11] 4.54.651.1(w/ security ota)(rooted & non-rooted & update zip)
[ROM][STOCK][10/25/11] 4.54.651.1(w/ security ota)(rooted & non-rooted & update zip) - xda-developers

Thanks for the help! :)
 
Just making sure, but when this guide was initially released, I rooted my EVO for the first time. Everything went smoothly.

Now I want to upgrade to the newest software version.. all I need to do is place it on my SD card and then go through BootLoader and upgrade? I won't need to update anything else, it'll work without a problem?

This is the ROM I'm talking about...

[ROM][STOCK][10/25/11] 4.54.651.1(w/ security ota)(rooted & non-rooted & update zip)
[ROM][STOCK][10/25/11] 4.54.651.1(w/ security ota)(rooted & non-rooted & update zip) - xda-developers

Thanks for the help! :)
yes put it on your card. no about your bootloader. you need to flash this in your recovery. just make sure to make a nandroid backup and wipe everything (except sd card, obviously), before flashing it.
 
ocnbrze, Thanks!

Now Do I place the .zip file on my SD card anywhere? Because in Recovery, it said it couldn't find the file.
 
ocnbrze, Thanks!

Now Do I place the .zip file on my SD card anywhere? Because in Recovery, it said it couldn't find the file.

yes you put it on the card some place that you will find it. preferably on the root of your card which means not in any folder (though now days you can put a flashable zip file in a designated folder if you wish, just as long as you know which one).

and i think that you are confusing hboot (bootloader) when it scans for a PC36IMG file, but it does not find one so it will report "wrong or no image found." that is something else. in recovery you need to scroll down and find the file yourself. you will use the vol up and down buttons to scroll and the power button to select it.
 
I understand what you're saying and I went thru the procedures, but it still says it cannot find the file. Do I need to rename the .zip file?
 
I understand what you're saying and I went thru the procedures, but it still says it cannot find the file. Do I need to rename the .zip file?

ok in recovery you select install(flash depending on which recovery you have) from sd card. from there you select zip and scroll down until you find the rom then select it by using the power button.
 
ok in recovery you select install(flash depending on which recovery you have) from sd card. from there you select zip and scroll down until you find the rom then select it by using the power button.
I figured out the problem, I had so many folders on my SD card that I didn't scroll down far enough. Applying update now. Sorry lol.

Also, it said that vr superwipe wouldn't install so it aborted installation?

"Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5

It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.

Installation aborted."
 
I figured out the problem, I had so many folders on my SD card that I didn't scroll down far enough. Applying update now. Sorry lol.

Also, it said that vr superwipe wouldn't install so it aborted installation? Something about Gingerbread 3.0 and not being compatible?

ok sounds like have clockwork mod 3(or higher). basically, there are two kinds of scripts, edify and amend. clockwork mod only supports eddify. while most flashable files like superwipe uses amend. only amon ra 2.3, clcokwork mod 2.6 and TWRP have support for both scripts. so you can go to http://androidforums.com/evo-4g-all...ooting-dummies-guide-gingerbread-edition.html and go to the switching recoveries section to get amon ra2.3 onto your phone.
 
ok sounds like have clockwork mod 3(or higher). basically, there are two kinds of scripts, edify and amend. clockwork mod only supports eddify. while most flashable files like superwipe uses amend. only amon ra 2.3, clcokwork mod 2.6 and TWRP have support for both scripts. so you can go to http://androidforums.com/evo-4g-all...ooting-dummies-guide-gingerbread-edition.html and go to the switching recoveries section to get amon ra2.3 onto your phone.
Ah okay, and then go back and use vr superwipe? I appreciate you helping me!!
 
Ah okay, and then go back and use vr superwipe? I appreciate you helping me!!

no worries.

yes once you switch recoveries you can then flash superwipe among other files without any worries. plus amon ra is a much better recovery. just remember to make a nandroid backup once you switch to it. also if you made any nandroid backups with clockwork mod they will not work with amon ra. just follow the guide.
 
no worries.

yes once you switch recoveries you can then flash superwipe among other files without any worries. plus amon ra is a much better recovery. just remember to make a nandroid backup once you switch to it. also if you made any nandroid backups with clockwork mod they will not work with amon ra. just follow the guide.
I feel like a burden lol but now in HBoot, it says theres no image?

I downloaded PC36IMG RA 2.3.zip and renamed it to PC36IMG (without an extension, windows shows it as an unknown file). Then I transfered the file to my root folder on my SD card. Turned off phone, booted in BootLoader and then went to "bootloader", it ran and gave me that error. Even tried going to "hboot usb" and still gave me that error. Any ideas?
 
Back
Top Bottom