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

Root ROOTING For Dummies

Matlock said:
STEP 2: Installing Drivers (WINDOWS ONLY - MAC USERS DO NOT NEED TO INSTALL THE DRIVERS)
- Remove any previously installed Drivers that you may have installed for any other ROOTing purposes.
- Go to the unrevoked website (public:windows_hboot_driver_install [RootWiki])
- Download the unrevoked modified USB driver (android-usb-driver.zip)
- Save the file to the Desktop of your computer.
- UnZip the files to the Desktop of your computer.
- Follow the instructions as carefully as you can.

(Important Note: for some reason, my phone didn’t list an Android 1.0 as a selectable option. Anything listed as an Android is what you are looking for)
(NOTE: Some have had to Re-Install the HBOOT drivers a second time after the initial install.)
Click to expand...

I already screwed up once by rooting with another tool (Autoroot), so, I want to make sure I get it right this time!

I unzipped the the drivers file to my desktop. But, what instructions are referred to here? I plugged in my phone, and it automatically installed the new drivers.

Also, the next step talks as though I should be put in bootloader mode somehow as a result of the driver installation.

I must be missing something.
Can someone help please?

UNROOTED
Device Build Number: ??
Android Version: 2.2
HBoot Version: 2.10.0001
unrevoked Version Used: Not used yet



Thanks!
Eph
 
cephraim said:
I already screwed up once by rooting with another tool (Autoroot), so, I want to make sure I get it right this time!

I unzipped the the drivers file to my desktop. But, what instructions are referred to here? I plugged in my phone, and it automatically installed the new drivers.

Also, the next step talks as though I should be put in bootloader mode somehow as a result of the driver installation.

I must be missing something.
Can someone help please?


Thanks!
Eph
Click to expand...

In that link, there are instructions on how to install them. You're supposed to go to hboot (bootloader) as a part of the process. These are different drivers. Here's the link, again:

public:windows_hboot_driver_install [RootWiki]

Let me know if you have any trouble with that.
 
akazabam said:
In that link, there are instructions on how to install them. You're supposed to go to hboot (bootloader) as a part of the process. These are different drivers. Here's the link, again:

public:windows_hboot_driver_install [RootWiki]

Let me know if you have any trouble with that.
Click to expand...

Do I have to uninstall the drivers first, as it seems like they were already installed?

Also, when I right click on Android 1.0 in Device Manager, I don't have an option to update driver. Just "Scan for changes" and "properties". Clicking on properties>Driver, the "update driver" option is grayed out.
 
akazabam said:
It's a modified driver; you'll need to update it, as the instructions say. Did you ever go through the process it describes? If not, then you need to do it.
Click to expand...

When I right click on Android 1.0 in Device Manager, I don't have an option to update driver. Just "Scan for changes" and "properties". Clicking on properties>Driver, the "update driver" option is grayed out.

EDIT: NVM. Tried it again, and now have the option to update.
 
cephraim said:
When I right click on Android 1.0 in Device Manager, I don't have an option to update driver. Just "Scan for changes" and "properties". Clicking on properties>Driver, the "update driver" option is grayed out.

EDIT: NVM. Tried it again, and now have the option to update.
Click to expand...

Sorry, missed the part above where you said it was grayed out. Now that you've got it working, finish the rest of the steps, and let me know if you run into any more problems.
 
akazabam said:
Sorry, missed the part above where you said it was grayed out. Now that you've got it working, finish the rest of the steps, and let me know if you run into any more problems.
Click to expand...

Thanks. Looks like I'm rooted.
During the Nand backup, it said it is backing up WiMax.

I see some comments later in the tutorial about WiMax keys. Does the default recovery backup handle these keys properly now, or do you still recommend ROM Manager or Armon_RA for recovery to handle the WiMax keys?

I assume this can be changed anytime, right?

It also said "No sd-ext" during Nand backup. Why is that?
 
cephraim said:
Thanks. Looks like I'm rooted.
During the Nand backup, it said it is backing up WiMax.

I see some comments later in the tutorial about WiMax keys. Does the default recovery backup handle these keys properly now, or do you still recommend ROM Manager or Armon_RA for recovery to handle the WiMax keys?

I assume this can be changed anytime, right?

It also said "No sd-ext" during Nand backup. Why is that?
Click to expand...

Congrats on successfully rooting :).

1) Clockwork 2.6.0.1 now backs up wimax keys, as you can see by the fact that it said so.
2) Many people still prefer Amon RA over Clockwork because it seems to be more reliable, but both recoveries will backup wimax RSA keys now.
3) ROM Manager is just a front-end for Clockwork, and isn't any kind of replacement.
4) You can change recovery images (CW to RA or vice versa) whenever you want. It's very simple with ROM manager. You cannot restore a nandroid made in CW on RA or RA on CW. Nandroid backups must be restored in the same recovery they were made with.
5) There's an option in recovery to partition your sdcard with an ext partition. The purpose is to create a partition with a filesystem native to Linux (Android) on the card so that you can use it with a2sd. What that means is, you can copy all your apps to the sdcard. If you haven't created one, the backup process will skip it, and tell you so. It's nothing to worry about; it's supposed to do that.
 
akazabam said:
Congrats on successfully rooting :).

1) Clockwork 2.6.0.1 now backs up wimax keys, as you can see by the fact that it said so.
2) Many people still prefer Amon RA over Clockwork because it seems to be more reliable, but both recoveries will backup wimax RSA keys now.
3) ROM Manager is just a front-end for Clockwork, and isn't any kind of replacement.
4) You can change recovery images (CW to RA or vice versa) whenever you want. It's very simple with ROM manager. You cannot restore a nandroid made in CW on RA or RA on CW. Nandroid backups must be restored in the same recovery they were made with.
5) There's an option in recovery to partition your sdcard with an ext partition. The purpose is to create a partition with a filesystem native to Linux (Android) on the card so that you can use it with a2sd. What that means is, you can copy all your apps to the sdcard. If you haven't created one, the backup process will skip it, and tell you so. It's nothing to worry about; it's supposed to do that.
Click to expand...

Awesome! Thanks! Installed ROM Manager and a bunch of root apps, including SetCPU.

Q: Is there a way to underclock the EVO below 245MHz with SetCPU?

Also used Titanium Pro to freeze a bunch of bloatware.

On A2SD, do you recommend I use this page?:
Darktremor Installation Instructions | Facebook

Not sure I'm going to load a ROM any time soon, but I do want to move my apps to SD...

Thanks again!

Eph
 
cephraim said:
Awesome! Thanks! Installed ROM Manager and a bunch of root apps, including SetCPU.

Q: Is there a way to underclock the EVO below 245MHz with SetCPU?

Also used Titanium Pro to freeze a bunch of bloatware.

On A2SD, do you recommend I use this page?:
Darktremor Installation Instructions | Facebook

Not sure I'm going to load a ROM any time soon, but I do want to move my apps to SD...

Thanks again!

Eph
Click to expand...

1) If you mean setting the minimum frequency lower than 245, yes you can, but you must use a kernel that supports that frequency. A lot of custom kernels do. If you want to try a custom kernel (or a ROM), make a nandroid backup (if you haven't already), then try whatever you want. One of the more popular kernels to try out is netarchy:

[GPL][Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.2 - xda-developers

There are many threads here discussing other kernels along with information you'll need to know about them (such as CFS/BFS, HAVS/noHAVS, etc.). Let me know if you need more direction on that. Also, if you're going to use setcpu, I suggest you read this if you're not sure how everything works:

http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html

2) I trust you followed the guide here for what bloatware is safe to freeze.

3) That's the correct link, but if I'm not mistaken, it requires a custom ROM. Read this:

[Script][A2SD] Darktremor Apps2SD 2.7.5.3 Beta 03a (01/25/2011) - xda-developers
 
akazabam said:
1) If you mean setting the minimum frequency lower than 245, yes you can, but you must use a kernel that supports that frequency. A lot of custom kernels do. If you want to try a custom kernel (or a ROM), make a nandroid backup (if you haven't already), then try whatever you want. One of the more popular kernels to try out is netarchy:

[GPL][Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.2 - xda-developers

There are many threads here discussing other kernels along with information you'll need to know about them (such as CFS/BFS, HAVS/noHAVS, etc.). Let me know if you need more direction on that. Also, if you're going to use setcpu, I suggest you read this if you're not sure how everything works:

http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html

2) I trust you followed the guide here for what bloatware is safe to freeze.

3) That's the correct link, but if I'm not mistaken, it requires a custom ROM. Read this:

[Script][A2SD] Darktremor Apps2SD 2.7.5.3 Beta 03a (01/25/2011) - xda-developers
Click to expand...

1) Yes, please point me to a good guide on kernel features. Seems like EVO users aren't setting the min speed below 245MHz, even with screen on. Is that correct? Doesn't the EVO processor throttle down to 245MHz without SetCPU?

Also, I see on that page for the netarchy kernel that PRI 1.90 eats battery. I'm at 1.90. Do you recommend I downgrade? What's the easiest way?

2) Yup!

3) What it says is: "NOTE: ROMS THAT ARE ORM (ORIGINAL ROM FROM MANUFACTURER...ALSO KNOWN AS STOCK ROMS) WILL NOT RUN ANY VERSION OF APPS2SD EXCEPT FROYO. The code to launch Apps2SD is not present in the init.rc. The only way Apps2SD will work with a Stock ROM is if the init.rc has been modified with the commands to run Apps2SD."

Is Froyo 2.1?
Since I am on 2.2, I guess I have to install a custom ROM. Or, are you aware of any stock ROMs with modified init.rc? With 230MB of internal memory left, I'm not ready to do that just for A2SD... I did run a custom ROM and A2SD on my Hero, but that's because I was running out of memory...

Thanks!
 
cephraim said:
1) Yes, please point me to a good guide on kernel features. Seems like EVO users aren't setting the min speed below 245MHz, even with screen on. Is that correct? Doesn't the EVO processor throttle down to 245MHz without SetCPU?

Also, I see on that page for the netarchy kernel that PRI 1.90 eats battery. I'm at 1.90. Do you recommend I downgrade? What's the easiest way?

2) Yup!

3) What it says is:

*EDITED OUT*

Is Froyo 2.1?
Since I am on 2.2, I guess I have to install a custom ROM. Or, are you aware of any stock ROMs with modified init.rc? With 230MB of internal memory left, I'm not ready to do that just for A2SD... I did run a custom ROM and A2SD on my Hero, but that's because I was running out of memory...

Thanks!
Click to expand...

1) Here's a good starter for you:

[GUIDE]
 
Based on what I read, I decided to go with the netarchy-cfs-havs-nosbc kernel. Have SetCPU down to 128 on screen off, and 245-1075 ondemand screen-on.

So far, so good!

Next question. If I am going to flash a ROM, I'd want something that is basically a stripped stock ROM that has A2SD enabled. On my Hero, I used NfiniteFX's Stock ROM and liked it a lot!
http://forum.xda-developers.com/showthread.php?t=790889

Is there something similar for the EVO? Stock Turbo, perhaps?

Thanks again!
 
cephraim said:
Thanks. I'll do some research on those.

Had you heard of that PRI 1.90 issue?
Click to expand...

cephraim said:
Based on what I read, I decided to go with the netarchy-cfs-havs-nosbc kernel. Have SetCPU down to 128 on screen off, and 245-1075 ondemand screen-on.

So far, so good!

Next question. If I am going to flash a ROM, I'd want something that is basically a stripped stock ROM that has A2SD enabled. On my Hero, I used NfiniteFX's Stock ROM and liked it a lot!
[ROM] NFX Sprint 2.31.651.7 STOCK Deoxed/Odex Updated:10/14/2010 - xda-developers

Is there something similar for the EVO? Stock Turbo, perhaps?

Thanks again!
Click to expand...

1) Sorry, I forgot to answer your PRI 1.90 question. Basically, if you're having bad battery life, it *might* be because of PRI 1.90. If your battery life is fine, you have nothing to worry about. It usually results in uptime equaling awake time (the phone doesn't sleep).

2) What exactly do you want? Do you want an AOSP (Based on Google source) ROM or a Sense ROM with as much of Sense removed as possible? AOSP ROMs will have a few issues here and there (4g functionality is still in alpha, and hdmi doesn't work). All Sense ROMs (stripped down or not) have everything working. Here are a couple Sense options that should have what you want:

[ROM] VaelPak 3.0 [01/01/11] - NonSense - [SBC-NOHAVSv8] - 3.70.651.1 OTA - xda-developers
[ROM]EVO-NonSense(UPDATED 1/22-Gingerbread Elements,OTA 3.70.651.1 - xda-developers

If you want an AOSP ROM, Cyanogenmod is basically the best choice.
 
akazabam said:
1) Sorry, I forgot to answer your PRI 1.90 question. Basically, if you're having bad battery life, it *might* be because of PRI 1.90. If your battery life is fine, you have nothing to worry about. It usually results in uptime equaling awake time (the phone doesn't sleep).

2) What exactly do you want? Do you want an AOSP (Based on Google source) ROM or a Sense ROM with as much of Sense removed as possible? AOSP ROMs will have a few issues here and there (4g functionality is still in alpha, and hdmi doesn't work). All Sense ROMs (stripped down or not) have everything working. Here are a couple Sense options that should have what you want:

[ROM] VaelPak 3.0 [01/01/11] - NonSense - [SBC-NOHAVSv8] - 3.70.651.1 OTA - xda-developers
[ROM]EVO-NonSense(UPDATED 1/22-Gingerbread Elements,OTA 3.70.651.1 - xda-developers

If you want an AOSP ROM, Cyanogenmod is basically the best choice.
Click to expand...

Looks like I don't have a problem with awake time on PRI 1.90.

re: what I want in a ROM
I like Sense. I think Stock Turbo will be good for me.

Thanks!
 
cephraim said:
Looks like I don't have a problem with awake time on PRI 1.90.

re: what I want in a ROM
I like Sense. I think Stock Turbo will be good for me.

Thanks!
Click to expand...

Stock Turbo is basically stock with a few things added. Presumably it will work with a2sd, but I don't see any mention of built-in support. Not that you can't just install it, but keep that in mind.
 
I want to root my phone. I was wonder can I use the current unrevoked version to root my evo.

Android version 2.2
Baseband version 2.15.00.11.19
Kernel version 2.6.32.17
Build number/Software number 3.70.651.1
PRI Version 1.9_003
PRL Version 60670
 
Ok so I'm having an issue guys that i really need help with...I'm trying to unroot my phone because my charger port is messed up to where it will charge but it will not read as a disk drive on my PC...

I got as far as flashing S-On....but once I did that and got to the next step...I was able to flash the the other package or anything else for that matter....it keeps saying "THIS CAN NOT BE DONE YET".....

My phone still works and all but i still need to get past this step so I can take it and get a new phone...So can someone please help me out...thanks in advance
 
iMakRay said:
Ok so I'm having an issue guys that i really need help with...I'm trying to unroot my phone because my charger port is messed up to where it will charge but it will not read as a disk drive on my PC...

I got as far as flashing S-On....but once I did that and got to the next step...I was able to flash the the other package or anything else for that matter....it keeps saying "THIS CAN NOT BE DONE YET".....

My phone still works and all but i still need to get past this step so I can take it and get a new phone...So can someone please help me out...thanks in advance
Click to expand...

When you rooted did you flash a new ROM or kernel or keep the stock HTC sense ROM?
 
ayaka43770 said:
I want to root my phone. I was wonder can I use the current unrevoked version to root my evo.

Android version 2.2
Baseband version 2.15.00.11.19
Kernel version 2.6.32.17
Build number/Software number 3.70.651.1
PRI Version 1.9_003
PRL Version 60670
Click to expand...

You sure can. Happy rooting and welcome to the forum!
 
You must log in or register to reply here.
Back
Top Bottom