Database Develop

Rooting your Motorolla Droid running 2.2.1 write-up

The OTA 2.2.1 update made things complicated for Droid users who want to root and download non market apps. After several days, countless hours and trial and error, this is my little write up on how I rooted a Motorolla Droid running 2.2.1 Build # FRG83D.
z4root no longer works and neither does the ability to download non market apps with 2.2.1. This is the easiest way to do it although there are other longer processes to root your phone which may have not been used on a 2.2.1 Moto Droid. I did a factory reset before I started but that is optional, let's begin.
*** Disclaimer ***
Please make a Nandroid or backup before this just incase.
1. Go to Motorolla's site and downloaded the Motorola 4.8.0 Driver with MotoConnect here. This program automatically downloads the driver your computer needs. This is a MUST. Lots of websites’ and write-ups forget or are vague on this easy step and it makes for a headache. Once downloaded, click on “Update Drivers” and click start. (You can download the driver file and wait for your Hardware Manager to pop up and go that route or just take the easy way and do this)
2. Download the latest version of Superoneclick and follow its directions on how to install it, you can find it here.
3. Connect your phone with your PC via USB. Make sure that USB debugging is ON. I removed my SD card to be on the safe side but if you choose not to, make sure you do not mount the SD card.
4. Open the Superoneclick program after un-zipping it, in Administrator mode. Follow the directions, there is even a video on how to do it. After your phone is rooted, click on " Allow non market apps ". Superuser should now be installed on your phone in your app's list.
*** The newest version of Superoneclick install BusyBox along with Superuser. Open your app drawer and look for these two. If both are there, you are done! If not, continue to step #5. ***
5. Disconnect your phone from your computer and restart your phone. It's not needed but, it's best to start with a fresh restart.
6. Go into your market from your phone, download Busybox ( free app ) and run it. Once installed, make sure within the app it states that your phone is rooted and the latest version of Busybox is displayed.
7. Restart your phone, this step is a must.
Your phone now has root access. You can download non market apps as well. I use Titanium Backup to remove bloat and such but you can use your favorite file manager.
Why the OTA 2.2.1 made things disfunctional, I don't know but this is my little solution and hope it helps.

I am going to give this a nice healthy bump since I have seen a couple Root confusion threads. I will be more then happy to answer any questions.

THANKS
Thank you so much!!!!!!!

Working on a Droid 1 for the first time. This is just the info I needed! Thank you sir!

Not a problem! I actually find that a stock ROMed, rooted and cleaned up Droid 1 is just as quick as the ROMs available to download if not quicker.

Thanks!
Hi,
Wanted to say thanks! Your write up was concise, straightforward and easy to understand... The app worked just like it said it would and rooted my Droid (the original) 2.2.1 FRG83D like a charm!
The Tutorial was a god send as that clarified what to expect and how to react if something went "brown & lumpy".
Thanks and now off to make a backup before learning the other fun stuff!

Tried this, downloaded the driver PC sees the phone, check
DL and run superone click, Check
no busybox, download and install, says rooted, check
here's the problem, can't get into recovery can't do a nand before or after rooting. seems recovery can't see the sdcrad.
I tried to root my Droid 1 (2.2.1 FR83d) with super one click. Everything seemed to work. I got super user access, TI backup runs (mostly)
From Rom manager I installed Clockwork it said everything work but no recovery mode access (yellow triangle) After reading up here it was suggested to flash SPrecovery and then back to clockwork so I did that bot SP and clock work appeared to run fine but still no recovery mode.
Setcpu seems to be working superuser is working but I cannot make a backup of the phone (nand, ROM manager recovery both fail) TI can't uninstall factory apps, and dose not make a complete backup just apps and restores dose not do a complete restore.
It seems I have half a rooted phone. Any ideas on how to fix this?
Click to expand...
Click to collapse

Just rooted my OG Droid. Thanks for the guide!
Edit: Just noticed that BusyBox didn't install with SuperOneClick, and that it is failing to install with the BusyBox installer app.
Edit: Okay, BusyBox installed. Backup created, ready for some ROMs!

A2Aegis said:
Just rooted my OG Droid. Thanks for the guide!
Edit: Just noticed that BusyBox didn't install with SuperOneClick, and that it is failing to install with the BusyBox installer app.
Edit: Okay, BusyBox installed. Backup created, ready for some ROMs!
Click to expand...
Click to collapse
The new version of superoneclick should install busy box if not get busybox from the market.
How did you get busy box to finally install? What solved the problem?
Sent from my DROIDX using XDA App

Ben's said:
The new version of superoneclick should install busy box if not get busybox from the market.
How did you get busy box to finally install? What solved the problem?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
For some reason my SU settings didn't pop up, and that caused the install to fail. The 2nd time around, it asked me for permission and it worked.

K I need help please. I used the rs4 lite guide to root the wife's phone ,that was successful, installed rom manager and did the clock mod flash now I can't get recovery,none , I installed busy box and still nothing lol, help I was gonna put cyan 7 on

I figured it out lol, just had to search the forums a bit more , running cyanogen 7 and is a sweet rom . Sry for being a noob . Thanks to all who came up the Rome and cracks y'all rock

Great walk through. Some of you might need another driver (ADB) for XP. They won't let me post the link but it's at Alldroid.

Worked flawlessly on my new 2.2.1 Droid 1, thanks!

Thank you very much for the post, helped me a lot for my rooting Droid / Roi as it is Verizon but I have with Iusacell in Mexico

This thread should be pinned.

My computer says your superoneclick is infected with a virus. Bummer for all the peeps that downloaded it already.......

Hey All,
This is going to be somewhat on and off topic.
I have jumped into the world of Android with both feet in the last few weeks.
So far I have obtained:
A Color nook which I have rooted using autonooter 3.0.0 running stock OS and also run Honeycomb off my SD card (until the real version comes out)
A Moto Backflip which I have rooted using rageagainstthecage-arm5.bin and is now running Unofficial CyanogenMod v6.1.2 (Froyo 2.2.1)
And Now I just bought a Droid with a dead battery, 16GB SDcard and a bad micro USB port for $25! (figured at $25 for a 16GB card it was worth the risk) I was able to "jump start" the battery and got it to power on. Its currently running 2.2.1 with build number FRG83D and is not rooted. Looks like the digitizer has a dead swath right down the middle.
Anyway, I can fix both things for <$30, so at $55 I still think I got a deal. Not too mention the fun of repairing and hacking it!
So my question:
I plan to use it for a little while before spending $$$ and making the repairs. But w/o a USB connector it does not seem that I can root my version.
Do I have any other options? keep in mind the current lack of ability to push things with ADB.

Super fast and easy. thank you so much!

micl9 said:
Hey All,
This is going to be somewhat on and off topic.
I have jumped into the world of Android with both feet in the last few weeks.
So far I have obtained:
A Color nook which I have rooted using autonooter 3.0.0 running stock OS and also run Honeycomb off my SD card (until the real version comes out)
A Moto Backflip which I have rooted using rageagainstthecage-arm5.bin and is now running Unofficial CyanogenMod v6.1.2 (Froyo 2.2.1)
And Now I just bought a Droid with a dead battery, 16GB SDcard and a bad micro USB port for $25! (figured at $25 for a 16GB card it was worth the risk) I was able to "jump start" the battery and got it to power on. Its currently running 2.2.1 with build number FRG83D and is not rooted. Looks like the digitizer has a dead swath right down the middle.
Anyway, I can fix both things for <$30, so at $55 I still think I got a deal. Not too mention the fun of repairing and hacking it!
So my question:
I plan to use it for a little while before spending $$$ and making the repairs. But w/o a USB connector it does not seem that I can root my version.
Do I have any other options? keep in mind the current lack of ability to push things with ADB.
Click to expand...
Click to collapse
have you tried adb wireless from the marketplace? i got a nook color recently too and had a hell of a time with adb through usb, but adb wirless seems to work great.

Can this Root Droid 3?

I do not have a Droid 3 yet, But I am considering it. What came to mind was the fact that root is not established yet, as far as I know. This makes me want to take a run at it, they were the best days when I use to work on the hack for Droid X.
But before I start playing around with a new device, I was wondering if anyone has tried this? And also I am wondering what other apps and methods have been attempted?
http://www.techofweb.com/technology/root-android-gingerbread-gingerbreak.html

Gingerbreak tried and failed
Z4Root tried and failed
Superoneclick tried and failed
Doroot tried and failed
that is just what I tried and I am no "pro rooter" like some others.

To my knowledge, no 2.3.4 device has been fully rooted yet (for the exception of the nexus).
I could be wrong, though. Completely, totally wrong.
But nothing out there can get us root. That im sure of.
Sent from my DROID3 using XDA App

Gingersnap restated my phone. And that am I root app. Says when I select advanced details it says I am root but all the su files say permission denied.
Sent from my DROID3 using Tapatalk

sparkyman216 said:
Gingersnap restated my phone. And that am I root app. Says when I select advanced details it says I am root but all the su files say permission denied.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
So...it kinda worked? Maybe that is something to work off of. Sounds like you got farther than anyone else. I would start a thread or something titled "Gingersnap reports successful root on Droid 3" so others can see and maybe expand upon it.

nerdslogic said:
So...it kinda worked? Maybe that is something to work off of. Sounds like you got farther than anyone else. I would start a thread or something titled "Gingersnap reports successful root on Droid 3" so others can see and maybe expand upon it.
Click to expand...
Click to collapse
....Yeah, no. If it "kinda worked", he would have temproot.
Sent from my DROID3 using XDA App

Well right now we dont have a sbf but they just released a rooted gb for the droid x2 so shouldnt be long for us

ovelayer said:
Well right now we dont have a sbf but they just released a rooted gb for the droid x2 so shouldnt be long for us
Click to expand...
Click to collapse
This release has no relationship to the Droid 3 getting root sooner or later unfortunately. This is updating Froyo to Gingerbread (and 2.3.3 at that) and since Froyo was easily rootable, they used a rooted device to pull the update that was OTA and then rooted the update. Rooted devices with custom recoveries (which the froyo based DX2 had) can install unsigned .zip files....so you can install the rooted "update.zip" and have Gingerbread with root.
None of this applies to the Droid 3 because we started at Gingerbread (and 2.3.4 too which is even more difficult to root) and no custom recoveries (because root will have to happen first).

Sounds like fun and challenging!

The Atrix has been rooted from an unrooted/locked state on 2.3.4.
http://wiki.rootzwiki.com/index.php/Motorola_Atrix

elkay said:
The Atrix has been rooted from an unrooted/locked state on 2.3.4.
http://wiki.rootzwiki.com/index.php/Motorola_Atrix
Click to expand...
Click to collapse
Interesting.. is this fasboot flashing the unlocked bootloader?

faylix said:
Interesting.. is this fasboot flashing the unlocked bootloader?
Click to expand...
Click to collapse
No, this is with the bootloader still locked and 2.3.4 already installed. Here's the full discussion. Second post is the method from the wiki. I already asked if the original creator of the exploit was on the thread and could say whether we would be able to use the same method with the D3.
http://forum.xda-developers.com/showthread.php?t=1138204

elkay said:
No, this is with the bootloader still locked and 2.3.4 already installed. Here's the full discussion. Second post is the method from the wiki. I already asked if the original creator of the exploit was on the thread and could say whether we would be able to use the same method with the D3.
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
I'm guessing you meant couldn't say.
What we need is a list of bootloader verisions and exactly what is being installed here with this update. Our bootloader is 0A.03 I don't know what the atrix is.
I also don't know exactly what its being overwritten here... how or how make copys of the things being replaced. *sigh*
any chance we coudl use a program like RDlite or backup our bootloader before we go ahead and write all over it... ?
this is close guys... 2.3.4 has been rooted on its own and now its just a matter of time before it makes it s way to us!
- faylix / local

I took a look at the file and it's very possible something similar could be devised for the D3, but we need the SBF file so that the preinstall partition can be pulled from it to use.
The Atrix devs have all of those files and tools available to them already, which is why they were able to create this kind of exploit.
If we had SBFs and an engineering device available to us this would have all been done very quickly on the D3 too. Unfortunately, so far we don't have either.

cellzealot;16200770
If we had SBFs and an engineering device available to us this would have all been done very quickly on the D3 too. Unfortunately said:
We have the SBF for an engineering device don't we.... we spoke on PM about someone who had this...
Click to expand...
Click to collapse

Can any type of temproot be achived at all?
Sent from my Droid using XDA Premium App

faylix said:
I'm guessing you meant couldn't say.
Click to expand...
Click to collapse
No, I meant what I said. I meant that I asked those things but didn't have a response yet.
This is very, very close.

This is what I got after gingersnap.
Congratulations! You have root access!
Superuser.apk - com.noshufou.android.su - version 2.3.6 is installed!
Standard su binary location: /system/bin/su: No such file or directory
Standard su binary location: /system/xbin/su: No such file or directory
Alternate su binary location: /sbin/su: Permission denied
Root user id: Root not properly returning its user id
Root group id: Root not properly returning its group id
Sent from my DROID3 using Tapatalk

su is root, that's the Super User account.
SuperUser.apk is just an app to let you control what apps can access "su".
You can have root without SuperUser.apk
You can't have root without "su"

Yea I know just showing what it sajd
Sent from my DROID3 using Tapatalk

Problem with Hashcode's tweaked D3 Bootstrap

I got a new phone in yesterday and after starting up, I immediately rooted and installed Hashcode's tweaked version of Koush's Bootstrap Recovery. I did a Nandroid backup and everything went smoothly. However, I went on to flash Dark Droid and everything worked great, but after clicking "Bootstrap Recovery" after flashing (as I read that one should after flashing a new ROM), I received the following error:
Failure
/data/data/com.hashcode.droid3.bootstrap/files/surunner.sh
[Permission denied]
Any idea as to what's going on here? Thanks in advance.
Sent from my DROID3 using Tapatalk

Check superuser it looks like it did not get su permission.

i had some issues like that, it was solved by updateing busybox then su. worth a shot anyway.

eww245 said:
Check superuser it looks like it did not get su permission.
Click to expand...
Click to collapse
I checked SU and the Bootstrapper definitely has SU permissions. I also updated SU, but to no avail.
Anyone else?

did you check busybox?

lordgodgeneral said:
did you check busybox?
Click to expand...
Click to collapse
I'm not very familiar with how Busybox works or how to "check" it. Could you teach me?
Edit: So I know there is some version of Busybox installed on my phone (doesn't psouza's one-click root automatically install it?), but I went ahead and donwloaded the Busybox installer from the Market and installed the latest version. Still not working. I even removed permission from SU in order to regain permission but that also didn't work.

Bump...still can't figure it out. Thank you again in advance.

Hello Lyxdeslic,
Have you tried Koush's stock Droid 3 Bootstrap? I'm curious if his apk would also have the same error.
I've seen a total of 2 users describe the issues that you're seeing. And 1 case was fixed, but never was explained how to me, the other issue was never resolved.
The 1st reply has it correct. The issue is that the Bootstrap "thinks" it has SU permissions, but it doesn't. And I'm 100% sure it has to do with the upgrade of Superuser.apk tho for 99% of users, all of it works seemlessly.
I apologize for not being able to provide much help :/

Hashcode said:
Hello Lyxdeslic,
Have you tried Koush's stock Droid 3 Bootstrap? I'm curious if his apk would also have the same error.
I've seen a total of 2 users describe the issues that you're seeing. And 1 case was fixed, but never was explained how to me, the other issue was never resolved.
The 1st reply has it correct. The issue is that the Bootstrap "thinks" it has SU permissions, but it doesn't. And I'm 100% sure it has to do with the upgrade of Superuser.apk tho for 99% of users, all of it works seemlessly.
I apologize for not being able to provide much help :/
Click to expand...
Click to collapse
My friend, no need to apologize at all. I appreciate the response, as I was considering PMing you but I didn't want to be a bother considering you probably get tons of PMs a day.
However, I uninstalled your tweaked Bootstrap this morning (also deleted data prior) and reinstalled it, and permissions were re-granted and it works now. I just realized that this did indeed happen after SU binaries were updated. All seems to be working well now.
One last quick question; after re-installing, if I boot into Recovery mode...will your Bootstrap still recognize and find the Nandroid backup on my SD card, which was also created with your Bootstrap during the first installation? I don't have my phone on me at the moment and I forgot to test.
Thanks again for the support. Kudos to you.

uninstall bootstrap and try the new safestrap

The Solutor said:
uninstall bootstrap and try the new safestrap
Click to expand...
Click to collapse
The Safestrap isn't to be used with ROMs other than CM7 Alpha and the stock MotoBlur ROM, if I'm not mistaken.

Lyxdeslic said:
The Safestrap isn't to be used with ROMs other than CM7 Alpha and the stock MotoBlur ROM, if I'm not mistaken.
Click to expand...
Click to collapse
It let to enter in the recovery, and is enough for me.

Ok, right...but why would you want to enter recovery in case of a bootloop when you can't flash the ROM you want to to restore your system? I mean yea Hashcode did create the MotoBlur ROM compatible with Safestrap only but still. Both options (safestrap and bootstrap) are needed, in my opinion.
Sent from my DROID3 using Tapatalk

Lyxdeslic said:
Ok, right...but why would you want to enter recovery in case of a bootloop when you can't flash the ROM you want to to restore your system? I mean yea Hashcode did create the MotoBlur ROM compatible with Safestrap only but still. Both options (safestrap and bootstrap) are needed, in my opinion.
Click to expand...
Click to collapse
I think that trying yourself is better than theorize...
They are two different sw created for different purposes, but those purposes are overlapping on the part that counts: booting in to recovery.

The Solutor said:
I think that trying yourself is better than theorize...
They are two different sw created for different purposes, but those purposes are overlapping on the part that counts: booting in to recovery.
Click to expand...
Click to collapse
Correct. They both get you into recovery...but he wants to flash a ROM other than CM or stock. Which Safestrap has no use for. He needs a bootstrap, no ifs ands or buts. Safestrap is of no use to him.

redsox985 said:
Correct. They both get you into recovery..
Click to expand...
Click to collapse
This is what is needed to flash a rom (whatever rom), to do a nandroid backup and so on.
Period.
If you don't use a safestrap enabled rom just don't use the related feature

The Solutor said:
This is what is needed to flash a rom (whatever rom), to do a nandroid backup and so on.
Period.
If you don't use a safestrap enabled rom just don't use the related feature
Click to expand...
Click to collapse
Safestrap is different in the way that it flashed roms. So. There.
OP:
You can install safestrap (after uninstalling whatever recovery app you had before) and hold tight until later tonight or tomorrow when I update DarkDroid with safestrap compatibility.

dpwhitty11 said:
Safestrap is different in the way that it flashed roms. So. There.
Click to expand...
Click to collapse
Listen, I'm used to talk just when I'm sure about things.
Right now I've installed a rom starting with safestrap, and works perfectly.
So why don't try yourself instead of posting guesses as facts ?

The Solutor said:
So why don't try yourself instead of posting guesses as facts ?
Click to expand...
Click to collapse
lol, ok buddy.
Don't get all offensive.
Sent from my DROID3 using XDA App

dpwhitty11 said:
OP:
You can install safestrap (after uninstalling whatever recovery app you had before) and hold tight until later tonight or tomorrow when I update DarkDroid with safestrap compatibility.
Click to expand...
Click to collapse
Looking forward to your latest

Making Sure everything is OK

So, I would of already rooted my Droid 3, exept, that it did not have custom recovery. But I want to make sure that both of these are available
Rom Manager
Custom Recovery(Obviously)
Thanks for any response.

techno-update said:
So, I would of already rooted my Droid 3, exept, that it did not have custom recovery. But I want to make sure that both of these are available
Rom Manager
Custom Recovery(Obviously)
Thanks for any response.
Click to expand...
Click to collapse
You can use Droid 3 Bootstrap or Safestrap as a custom recovery, IMO I see no reason to use ROM manager, as Safestrap (what I use) works perfectly..
Safestrap is better than normal Bootstrap because you can enable the "safe system" and install the system partition on the /preinstall directory (so you can leave your normal system intact) Although it depends on your phone model, if you're running a XT862 (Motorola Droid 3 - Verizon) then you're set. Other phone models have issues with safestrap.
-You might be able to use ROM Manager, but I would stick with Safestrap or Bootstrap because I KNOW that they work.

I like to use custom recovery though because it is easier/simpler and faster to do. I had it on my Droid Incredible. Just want to make sure it works right now. Though i will look at that. How would i apply it?

techno-update said:
I like to use custom recovery though because it is easier/simpler and faster to do. I had it on my Droid Incredible. Just want to make sure it works right now. Though i will look at that. How would i apply it?
Click to expand...
Click to collapse
You should be able to find Safestrap via Hashcode's website, go to the [SELFKANG] Cyanogenmod 7 page in Android Development, and you will be able to find his website that has the file. It is an APK file, so you just install it and run the installation from the app. I have not used custom recovery through ROM Manager, because I don't think it's compatible, but you could try it out..

The Mods need to sticky kshen1's information thread.
http://forum.xda-developers.com/showthread.php?t=1289611
-smc

somemadcaaant said:
The Mods need to sticky kshen1's information thread.
http://forum.xda-developers.com/showthread.php?t=1289611
-smc
Click to expand...
Click to collapse
Okay, so we do have it, can I flash it from Rom Manager?

techno-update said:
Okay, so we do have it, can I flash it from Rom Manager?
Click to expand...
Click to collapse
i don't think we can, rom manager flashes a version of the custom recovery to the bootloader which runs before the phone runs so that if you accidentally mess up your phone, you can easily restore it back to how it was before, and we don't have an unlocked bootloader, so by using the 2nd-init, we bypass needing to unlock the bootloader to be able to run custom ROMs (at least this is the way i understand it), so until they release a bootloader unlock, we're stuck using 2nd-init and bootstrap/safestrap to load up custom roms.....some roms you need to use safestrap and for some you need to use bootstrap, so you'd just have to check their instructions they give before the download link to make sure you're using the right one, using the wrong one can cause unforseen things to happen and can possibly brick your phone

Alright, I rooted, installed bootstrap recovery. Everything is good. Thanks guys.

[Q] How to Root Moto Droid running 2.2.3

I have looked around the forums and google searched this for the last hour. I've been trying to root it with SuperOneClick and Pete's Motorola Root Tools and have had no success. The build number is FRK76. My brother updated it and i can't root it anymore. Any help will be accepted.

I am having the same issue. Any rooting options out there for 2.2.3? Someone out there please help out.
Thanks...

Same problem here. It got updated to FRK76, cant find any support to root it.

I found that using Superoneclick v1.7 works when you use the rageagainstthecage method. This was the latest version I found that included this method; it has been removed in later versions.

Root 2.2.3 (FRK76)
I had the same problem:
Current version of SuperOneClick could not root my Droid (2.2.3 FRK76)
Downloaded SuperOneClick 1.7,
ran it (selecting rageinthecage option)
and it succeeded in rooting my phone.
Thank you!
- michael
PS: I got v 1.7 here
jaymode said:
I found that using Superoneclick v1.7 works when you use the rageagainstthecage method. This was the latest version I found that included this method; it has been removed in later versions.
Click to expand...
Click to collapse

slsmag said:
I had the same problem:
Current version of SuperOneClick could not root my Droid (2.2.3 FRK76)
Downloaded SuperOneClick 1.7,
ran it (selecting rageinthecage option)
and it succeeded in rooting my phone.
Thank you!
- michael
PS: I got v 1.7 here
Click to expand...
Click to collapse
hi my virus scanner says there is a virus in the .zip file is that normal and will it do no harm?

eaglesfan398 said:
hi my virus scanner says there is a virus in the .zip file is that normal and will it do no harm?
Click to expand...
Click to collapse
I can't vouch for that zip file but yes version 1.7 will get flagged by your virus scanner. I posted in the other thread where I got my version of 1.7 from and the link has a description of why it gets flagged by your virus scanner: http://forum.xda-developers.com/showthread.php?t=1406287&page=2

Root Droid using 2.2.3 with Mac OS X
Can someone point me to step by step instructions on how to root my Droid 1 running 2.2.3 using my Mac running Snow Leopard 10.6.8? I've searched quite a bit so far and have not come across what I need. I have not rooted before, and I'd like some help. Everyone here seems to be the most helpful I've seen on most forums so I figured this would be the place to ask. All assistance is greatly appreciated.
I tried using mono and running SuperOneClick v 1.7 with the rageinthecage option and it failed, also failed using all other exploits in both the 2.3.3 version on SOC and the 1.7 version of SOC.
Each time I try I get "Automatic version checking failed, Is your OS 2.0 or higher?" with options of YES, NO, OR CANCEL. No matter what i choose, the process stops.
Is using mono the problem? I am willing to try anything manually or otherwise, I just need some guidance. Thanks in advance!
Nate

Never mind, I've got it taken care of

How did you get it taken care of?

I am officially a sap. I download all excited thinking "hey, maybe wireless will finally work on a wpa2 encrypted network." But of course we should not fix a serious usability issue. Instead lets take away root making it even harder to use the device.
Err.. I simply meant to say, "hey, thanks for the tip on getting superoneclick 1.7 to do the jpb!"

UniversalAndroot is what you looking for.

I was able to use the latest SuperOneClick w/ my Droid @ 2.2.3 and it worked the first time on Win7 64-bit. I don't remember my build number (it seems to have changed since installing CM7), but I got it in January of 2010.

so ive been at this all day reading and searching these forums with no luck.
i have a droid one, running 2.2.3 FRK76, bought the phone used. says it has kernel version 2.6.32.9-g68eeef5. no clue what this is.
have tried to root with superoneclick with rageagainstcage option clicked. also tried the one click some one had posted on this site in one of the forums. Sd card is unmounted. debugg mode is selected. and i cant get past first time it says waiting for device. what do i do? im usign windows xp

First, it's but joined up as mass storage it's it? Also run one chick as admin if you aren't
Sent from Tyler`s Tweaked Charge

I know I'm kinda late to the party but my brother brought me a Droid and I was finally able to root with unlockroot.com I tried everything else suggested and this finally worked first try. It's funny but I don't remember it ever being that difficult before.
Sent from my SPH-D710 using XDA

I have an old Droid 1. I would like to root it and assume the 1.7 is what I need. After that where can I find roms. I only could find a thread for the Droid 2.
life is better with root.

links for rooting
I am having the same problem. I have been at this for 2 days now trying to root my droid 2.2.3. I tried
psouza4 method
it didnt work. I got the error message:
ERROR: adb could not be granted root access via local.prop method
Try again from the start, but if the problem continues, check your version
of Gingerbread -- hopefully you don't have a version where this exploit
was fixed.
then I tried to download super one click and I couldnt find the link....
I need help... anyone??
THANKS!