Related
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.
Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
P.S. You are stock now.
Sent from my DROID BIONIC using xda premium
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
that too, haha...
Sent from my DROID BIONIC using XDA App
Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.
Moderator Message
Breathe in, breathe out!!!!
I'll breathe when this .893 goes through and I keep root
There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...
I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access
Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it
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!
Hey,
For the past 6 hours i've been trying to root my Incredible S so i can install ICS 4.0.3 and i've just had no luck!
I have absoloutly no 'rooting' experience (jailbreak experience, yes) and i have no idea how to install custom firmware/images/roms ect.
For the first 4 hours i just tried to get rid of S-on, after reading through about 50 articles i gave up and was told to go to htcdev.com and unlock my bootloader, which is done but i can't root the phone!
I've tried the following:
HTC Supertool v3 - Unlocked my bootloader but failed with 'S-on', said my phone was rooted but is not...
SuperOneClick - Looks like it worked but didn't...
Unlock Root - 'Failed to access Shell root'
Universal Androot - Incompatible
z4root - First time, got stuck on 'Running exploit in order to obtain root access'
Second time, got to 'Attempting to apply root' and stayed like that forever (tried removing battery and restarting)
My phone may (MAY!) be rooted, i was told to download ConnectBot and if it had '$' i was not rooted but if i had '#' i was, nevertheless it came up with '$'....
Please help! I am desperate to get TRUE ICS (and none of that ****ty HTC ICS thats coming soon...)
Thanks, Danz207
UPDATE!!
I had z4root version 1.10, so i upgraded to 1.30 and this time the second step was called 'Acquiring root shell' or something like that and then it closed, but it wasn't a crash, it faded out within half a second. Anyway i opened 'Rom Manager' and it told me that i needed to root first and ConnectBox still has '$'.......
Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate
Have you tried the two links at the top of the dev forum? Read through them and you should be fine
Thank you markj338
markj338 said:
Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate
Click to expand...
Click to collapse
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!
danz207 said:
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!
Click to expand...
Click to collapse
LOL seems you're happy
So i got a used bionic I really like I know it's an old phone, but I like it, I'm new to the forums and don't know all the lingo, anyway I got this bionic xt875 running 4.1.2. I used kingroot to gain root access installed bootstrap rebooted and got encryption unsuccessful loop, tried flashing 902, 905, 863 "I think" and they all fail at 6/20 cdt.bin, I saw several different methods to fix this so I know there is a fix, but every download link for these methods and files needed are dead, does anybody still have these files, one click method, path saver method anything please help, thanks.