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

Root Guide to Rooting 2.2 for Windows and Linux

Ok, I know many ppl. have been talking about easy root and universal androot. I was rooted on easy root, went to do a backup with ROM Manager and could not do it. So, I unrooted with easy root and rooted with Universal androot and the backup worked without a hitch. Now, the question i've seen is did easy root not mesh well with clockwork mod and rom manager, or the other way around or both. Just letting ppl. know *FOR ME, WITH AN ORIGINAL DROID 1, THIS WORKED* I will post when I actually try a ROM with Universal androot installed. Also, sorry if this is not the correct spot to post.
 
Upvote 0
Hi all. Been lurking for a little while now, reading up on things. I finally went ahead and tried to root using the Linux method this morning and things did not go well. When it rebooted I got the dead battery warning and the FC every time and the phone would reboot on its own.. I followed a link on how to put the stock 2.1 back on and now all is fine. I thought that once I signed back into my account my apps would automatically re-download?

I am not walking away a quitter as I am going to try again. Just wondering if anyone had any idea as to what might have happened?
 
Upvote 0
Hi all. Been lurking for a little while now, reading up on things. I finally went ahead and tried to root using the Linux method this morning and things did not go well. When it rebooted I got the dead battery warning and the FC every time and the phone would reboot on its own.. I followed a link on how to put the stock 2.1 back on and now all is fine. I thought that once I signed back into my account my apps would automatically re-download?

I am not walking away a quitter as I am going to try again. Just wondering if anyone had any idea as to what might have happened?

pm me and I will help you figure out what happened
 
Upvote 0
This is awesome! Thanks OMJ!! I had a few setbacks... but a quick search was all I needed to fix. Thought I'd share:

Have vista 32... Had trouble restarting w/ the UP on the dpad. Uninstalled Moto-drivers...and it worked!

Had trouble installing .spf... was getting: Failed Flashing process. (0x7100). Had to go into c:/ - program files - motorola - RSD Lite - and right click on SDL and select run as admin...worked like a charm!

The rest of the instructions were spot on!

Thanks again!!

:D:D:D:D:D:D
 
Upvote 0
Anyone having issues with purchasing SetCPU on the market? I go through the whole process and then have an error after all my credit card info is inputted. Little sketchy.

I bought it today. The first time I tried it sat and thought about my click on the "buy" button for quite a while, then went back to main SetCPU screen in market. I clicked "buy" again and it went right through.

I just assumed my 3G was a little flakey at an inopportune moment is all.

It is all installed on my Droid now.


Cheers
 
Upvote 0
Success!

Last week I tried and failed because I didn't read, follow, and understand every step. The steps are fairly simple once you understand what is going on. The point is you have to understand them. After recovering last week, thanks to the great guides for unrooting on these boards, I researched all week. I practiced (without actually doing them) each and every step. That might sound a little overboard but my mistakes the first time were rushing and not paying attention to detail. I wanted to make sure I got it right this time. Once I actually performed the process, it was less than 10 minutes.

Thanks OMJ and everyone else for a great guide and a great tutorial! Now I'm going to spend the next two weeks researching ROMs because I understand that is also not a step to be taken lightly.

Cheers.
 
Upvote 0
Stuck after step 10, Windows Vista is claiming I need SE Flash Omap3430 MI Driver...

Can't flash image SPR to phone without the driver apparently, read topic here please: http://androidforums.com/droid-all-...h-omap3430-mi-driver-missing.html#post1476086

Please post with any info you have about downloading the driver or a fix. Thanks.

Are you rooting from Froyo FRG01B or from 22D?

If you are still on 01B why don't you try universal Androot instead?

You have probably done all of the hard stuff so you can just download Universal Androot and in 30 seconds you will have root.

(I say this, but understand I rooted for the first time yesterday so I am actually a noob with limited understanding of all the technicalities. I believe OMJ is the recognized God Of Root)
 
Upvote 0
HI OMJ,

Thanks for your guide. Unfortunately, I'm stuck in a frustrating cycle where my phone turns on, show the batter as red with a line through it. Then the system process force closes, and suddenly the phone reboots.

I'm trying to root my phone so that I can give CM6 a spin, because I'm having some pretty serious bugs with FRG22D, and FRG01, and what came before it.

I use Linux, so the steps were pretty simple. The install was successful. And Mybackup pro recognized my phone as rooted, but like I said, it's extremely unstable and I don't know what to do.

Please advise.
 
Upvote 0
HI OMJ,

Thanks for your guide. Unfortunately, I'm stuck in a frustrating cycle where my phone turns on, show the batter as red with a line through it. Then the system process force closes, and suddenly the phone reboots.

I'm trying to root my phone so that I can give CM6 a spin, because I'm having some pretty serious bugs with FRG22D, and FRG01, and what came before it.

I use Linux, so the steps were pretty simple. The install was successful. And Mybackup pro recognized my phone as rooted, but like I said, it's extremely unstable and I don't know what to do.

Please advise.

Seems like what happened is you flashed the whole SPRecovery sbf file instead of just the recovery partition of it.

you probably typed some thing like one of these
./sbf_flash -r -recovery SPRecovery_ESE81.sbf
./sbf_flash SPRecovery_ESE81.sbf

Instead of
./sbf_flash -r --recovery SPRecovery_ESE81.sbf


The solution is pretty simple you have to flash a rom.
So boot into recovery by powering on your phone by holding X. Then mount mass usb storage. Then download a rom. (I would suggest starting with FRG22D as a base because it just an easier place to start than Cyanogenmod. I can explain further if need be but with cyanogen you must also flash gapps.

Save that rom on your sdcard as update.zip

Then go back to the main recovery screen then go to install then allow update.zip installation then install update.zip. If you have any problems feel free to pm me.
 
Upvote 0
Seems like what happened is you flashed the whole SPRecovery sbf file instead of just the recovery partition of it.

you probably typed some thing like one of these
./sbf_flash -r -recovery SPRecovery_ESE81.sbf
./sbf_flash SPRecovery_ESE81.sbf

Instead of
./sbf_flash -r --recovery SPRecovery_ESE81.sbf


The solution is pretty simple you have to flash a rom.
So boot into recovery by powering on your phone by holding X. Then mount mass usb storage. Then download a rom. (I would suggest starting with FRG22D as a base because it just an easier place to start than Cyanogenmod. I can explain further if need be but with cyanogen you must also flash gapps.

Save that rom on your sdcard as update.zip

Then go back to the main recovery screen then go to install then allow update.zip installation then install update.zip. If you have any problems feel free to pm me.

OMJ,

I followed the instructions to a T, and actually performed them a second time just to double check.

Some more info, I was running stock FRG22D. I followed your instructions, and everything installed correctly. But when the phone boots, I have the following symptoms:

  1. Process system force closes
  2. If the usb cable isn't plugged in, the screen is black, except for the notification bar and the image on screen occupies half of the screen
  3. The phone reboots after about 1.5mins.

Any additional advice?
 
Upvote 0
OMJ,

I followed the instructions to a T, and actually performed them a second time just to double check.

Some more info, I was running stock FRG22D. I followed your instructions, and everything installed correctly. But when the phone boots, I have the following symptoms:

  1. Process system force closes
  2. If the usb cable isn't plugged in, the screen is black, except for the notification bar and the image on screen occupies half of the screen
  3. The phone reboots after about 1.5mins.

Any additional advice?

OMJ,

I downloaded Peter Alfonso's deodexed frg22d rom, flashed it, and I'm back in business, rooted and all.

Thanks for all of your help.
 
Upvote 0
I'm having a bit of a problem here. My phone was running FRG22 OTA update. I wasn't too happy and finally decided to root and followed this guide step by step. Everything worked fine except now it is just in a constant cycle of rebooting. It never completes the boot cycle. I just keep getting the "DROID" text and then the eye, which freezes and then repeats. All of this happens within a 10-15 second time period. I am able to get into SPRecovery mode just fine though by doing a battery pull and reboot. I tried to install the rooted FRG22 download listed in this thread. Any ideas of what I can do to fix this? I'm just dying to join the rooted community.
 
Upvote 0
I'm having a bit of a problem here. My phone was running FRG22 OTA update. I wasn't too happy and finally decided to root and followed this guide step by step. Everything worked fine except now it is just in a constant cycle of rebooting. It never completes the boot cycle. I just keep getting the "DROID" text and then the eye, which freezes and then repeats. All of this happens within a 10-15 second time period. I am able to get into SPRecovery mode just fine though by doing a battery pull and reboot. I tried to install the rooted FRG22 download listed in this thread. Any ideas of what I can do to fix this? I'm just dying to join the rooted community.

Try booting into recovery and wiping data and cache. I will play around with this tonight and figure out what the problem is but I think it may be issues with that rom.
 
Upvote 0
Glad you got it worked out. I have no clue what was happening after you flashed the first rom. Thats really off the wall.

Just an FYI, I had the exact same problems describe above.

I went from FRG01B to FRF22 (that was easy and fun!) to following root directions for 2.2 and then the problems started. Double-checked, triple-checked, verified every file and installation directory. Nada.

Checked this thread, downloaded (for almost 30 minutes) FRG22D and all is well in the world. :D

Just one question, what is the difference between FRG01B and FRG22D? I verified that I have the right build number on my phone but other than that, is there something I should be seeing?

robYn
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones