Root Rooting the Droid without rsd lite up to and including FRG83D

[Landau93]

I think that what your problem is, is that you did not extract the .zip. You MUST extract the .zip in order to have access to the .bin file.

Kratos

oh my god thank you so much i was having a b*%$& of a time trying to figure that out but after i did that thanks to you i had a problem free rooting thank you so much!

 

[kratos]

oh my god thank you so much i was having a b*%$& of a time trying to figure that out but after i did that thanks to you i had a problem free rooting thank you so much!

Any time. Oh and welcome to the forum!

Kratos

 

[DWilliams]

I'm trying to root my phone using this method.

I'm a Linux user and don't have Windows installed on any machine I own. I figured this tutorial was written for Windows so in order not to deviate too much from the instructions I figured I'd attempt this in a virtualbox VM of windows. I enabled USB debugging as per the instructions and installed the motorola drivers and android SDK/toolkits inside my VM. I plugged my phone in and assigned it over to the windows VM. "adb devices" shows that it is indeed seeing my phone. Every other command seems to freeze, though. "adb push" and "adb shell" both hang. The phone shows no signs that anything at all is happening. I've let the commands just sit there for 30 minutes and nothing at all happens. Am I doing something wrong or will this not work in virtualbox?

If I install the android SDK in Linux and run these commands will it work as intended?

 

[OMJ]

I'm trying to root my phone using this method.

I'm a Linux user and don't have Windows installed on any machine I own. I figured this tutorial was written for Windows so in order not to deviate too much from the instructions I figured I'd attempt this in a virtualbox VM of windows. I enabled USB debugging as per the instructions and installed the motorola drivers and android SDK/toolkits inside my VM. I plugged my phone in and assigned it over to the windows VM. "adb devices" shows that it is indeed seeing my phone. Every other command seems to freeze, though. "adb push" and "adb shell" both hang. The phone shows no signs that anything at all is happening. I've let the commands just sit there for 30 minutes and nothing at all happens. Am I doing something wrong or will this not work in virtualbox?

If I install the android SDK in Linux and run these commands will it work as intended?

Installing the android sdk in Linux and run the commands there would be your best bet. Just make sure you change the path to match Linux's folder system instead of windows.....ie anything with c:\droidroot\ would need to be changed to ~/droidroot/ or whatever folder you extract to. If you need help feel free to pm me. I will also link a tutorial for installing the sdk on linux in case you need it.

start [CVPCS Android Wiki]
steps 1 and 2 are required for setting up the sdk. The rest of the steps wont help you at all unless you want to start building from source.

 

[DWilliams]

Installing the android sdk in Linux and run the commands there would be your best bet. Just make sure you change the path to match Linux's folder system instead of windows.....ie anything with c:\droidroot\ would need to be changed to ~/droidroot/ or whatever folder you extract to. If you need help feel free to pm me. I will also link a tutorial for installing the sdk on linux in case you need it.

start [CVPCS Android Wiki]
steps 1 and 2 are required for setting up the sdk. The rest of the steps wont help you at all unless you want to start building from source.

I went ahead and did it fine in Linux. The only catch was getting ADB to show my phone as a device, but I was able to get it to show up by creating a udev rule with the following:

SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0660", GROUP="adbusers"

and adding myself to the adbusers group as described

 

[OMJ]

I went ahead and did it fine in Linux. The only catch was getting ADB to show my phone as a device, but I was able to get it to show up by creating a udev rule with the following:

SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0660", GROUP="adbusers"

and adding myself to the adbusers group as described

Glad you got it worked out. I use the udev rules that are in that linked tutorial. So far they have worked well for all the android phones I have had.

 

[webdeveloper24]

was curious on if there was a cammand line or script in this process to disable OTA updates. I have read and done this before in the past but been a year or so ago since i have done so and was just curious if it was a step in this thread? I am rooted on the Droid 1 and system updates still pop-up.

Thanks in advance

 

[The FlyerFly]

just wanted to thank everyone who worked on this. you guys do great work here, and are great at simplifying things for the intermediate phone geek like myself.

About a week ago, I had FRG22D rooted and had decided to bypass the FRG83D OTA update. But then I had to completely revert back to FRG83D stock because i needed a replacement (volume rocker and charger port both went bad). When I got my new phone, I took the FRG83D update and used OMJ's directions above. Perfect!!

Thanks again everyone.

 

[fl0w3n]

Weird, I am getting a " "adb" is not recognized as an internal or external command, operable program or batch file"

I'm in the right directory, tried it in a few directories (unzipping to new dir) to no avail.

Suggestions?

 

[kratos]

Weird, I am getting a " "adb" is not recognized as an internal or external command, operable program or batch file"

I'm in the right directory, tried it in a few directories (unzipping to new dir) to no avail.

Suggestions?

I have had this a couple times after installing everything. The first thing I did, was ensured that adb was actually placed in the correct location (which I see you have done). The second thing is I verified that my Motorola drivers were actually installed. I highly suggest installing the Moto Drivers using PDANet. You will need to go to this link: Download PdaNet and follow the directions. I cannot remember if I had to install the app on my phone first, but it wouldn't hurt to do so.

Once I installed the PDANet app on my computer, I was able to use adb without a problem.

Kratos

 

[illement]

I'm a n00b, but I'm really interested in rooting my Droid, but scared that I will "brick" my phone. Not even sure exactly what that means. I downloaded all the stuff necessary, but the steps make no sense to me. Any way this can be broken down into English?

 

[teddyearp]

They are written in English, lol. But just read them a few times until it starts making sense. When you decide to go through with it, I suggest printing them out so you can check off each step as you go. If it never makes sense, then maybe . . . . . don't.

Also here's another way to root your phone and has a ton of explanation of what you're doing as well:

Root Droid 1 - regardless of OS version - Droid Forum - Verizon Droid & the Motorola Droid Forum

good luck

 

[illement]

I unzipped the Android SDK thing to my C drive like the video tutorial says and it's installing archives now. I don't know where they're going though. Was I supposed to install that on my pc or phone?

 

[johnlgalt]

The Android SDK installs to our computer, not your phone.

The latest Android SDK has moved the location of adb.exe from the /tools folder to /platform-tools so I had to change my System's PATH environment variable so adb would work from anywhere again. I'll check out the tuts later today to see if they need adjusting...

 

[fl0w3n]

I have had this a couple times after installing everything. The first thing I did, was ensured that adb was actually placed in the correct location (which I see you have done). The second thing is I verified that my Motorola drivers were actually installed. I highly suggest installing the Moto Drivers using PDANet. You will need to go to this link: Download PdaNet and follow the directions. I cannot remember if I had to install the app on my phone first, but it wouldn't hurt to do so.

Once I installed the PDANet app on my computer, I was able to use adb without a problem.

Kratos

Trying this now.

This one has 64bit version, maybe that was my issue as I am using W7 64.



I installed PDANet and was connected through USB Tether (computer recognized it as connection, said I transfered some data as I used web pages) so I can assume the drivers are working properly.
Still the same result though, that I find no "abd" etc. I don't even see a file in the Tools folder called ADB anything, so I'm not sure what is going on here...



I'm now redownloading ADB, although I am going to give the .exe a try now. I prefer not to install needless things to my SSD, but oh well. I'll just reinstall windows if it bothers me


I suppose the lack of a Java JDK could have something to do with it?

 

[kratos]

Trying this now.

This one has 64bit version, maybe that was my issue as I am using W7 64.



I installed PDANet and was connected through USB Tether (computer recognized it as connection, said I transfered some data as I used web pages) so I can assume the drivers are working properly.
Still the same result though, that I find no "abd" etc. I don't even see a file in the Tools folder called ADB anything, so I'm not sure what is going on here...



I'm now redownloading ADB, although I am going to give the .exe a try now. I prefer not to install needless things to my SSD, but oh well. I'll just reinstall windows if it bothers me


I suppose the lack of a Java JDK could have something to do with it?

See the post right above the one I have quoted.

Kratos

 

[fl0w3n]

See the post right above the one I have quoted.

Kratos

Tried that directory too, \platforms, as \platform-tools doesn't exist, and same result. No files in that folder any ways.

SDK .exe won't install because it says I don't have a Java JDK, which I clearly just installed twice, so I don't know what is going on.

 

[rovrhys]

Will this work with FRG83D?
Because I tried to root using RSD Lite and this method and it doesnt seem to work still.
Rsd wouldnt recognize my Phone and this method I cant seem to get past number 5. idk where the adb tools are located.
any help would be awesome

 

[teddyearp]

@fl0w3n: Go to java.com to verify your java install. Also if the newer version of the android sdk is giving you fits, you can still use an older one. I've got a couple in my collection linked in my sig.

@rovrhys: Have you made sure that usb debugging is enabled on your phone?

 

[tom777]

Will this work with FRG83D?
Because I tried to root using RSD Lite and this method and it doesnt seem to work still.
Rsd wouldnt recognize my Phone and this method I cant seem to get past number 5. idk where the adb tools are located.
any help would be awesome

this method works fine for stock FRG83D. For me, adb.exe is located here: c:\apps\android-sdk_r05\platform-tools\adb.exe

There was a change in location for adb with one of the recent updates to the sdk tools. While my directory is named 'r05', my version has actually been upgraded to the latest r8.

So, for you, assuming your sdk tools is current, you should find it under the platform-tools directory under the main install directory you chose.

 

[Scott351W]

I've tried several times but it always seems to hang at step 13. How long does it take before you should see the #?

 

[teddyearp]

I've tried several times but it always seems to hang at step 13. How long does it take before you should see the #?

What kind of messages are you getting after step 11?

 

[Scott351W]

What kind of messages are you getting after step 11?

None it just seems to hang. blinking underscore, no # or $. any ideas?

 

[tom777]

I didn't time it to see exactly how long it took for me, but it was enough I was starting to worry... I bet 2-3 minutes maybe? When it completes, it exits your shell taking you back to your regular command prompt.

 

[teddyearp]

I've tried several times but it always seems to hang at step 13. How long does it take before you should see the #?

What kind of messages are you getting after step 11?

None it just seems to hang. blinking underscore, no # or $. any ideas?

So where is it really hanging? Step 13 as you first stated, or step 11 as you then replied? Did you get any other error messages along the way? You do have usb debugging enabled, right?

Sometimes with a guide that is this command prompt intensive, it is better to print it out and check off the steps as you go.