(Run means type the command in quotes [but not the quotes] then press the Enter key)
Download the attached archive and expand it to a folder you can find (eg. c:\DroidXRoot_v2)
Set up ADB (Step-by-step guide for Windows Vista/7 HERE. <-- USE THAT THREAD FOR ADB SUPPORT PLEASE.)
On the phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Status bar, USB connection: Make sure "PC Mode" is selected.
Open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
Run "adb devices". If you don't see your device listed under "List of devices attached", return to step 2 and follow the link to setup ADB (use that topic for support) and return here when "adb devices" lists your X.
Run "CD c:\DroidXRoot" (or where ever you expanded the archive)
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid"
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
On your phone, navigate to a screen where you can switch wifi/bluetooth on/off easily (settings, or a home screen with a widget)
IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
Run "./exploid" and follow directions on screen. Once this completes you'll be back at a shell prompt.
Run "rootshell". You'll be prompted for a password.
Type in password "secretlol" and press Enter then you are root! (You'll know because your prompt will now be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user shell (on phone still)
Run "exit" to drop back to your machine command prompt (instead of phone)
To Confirm root is established:
Run "adb shell"
Run "su" (now you should see the # sign which indicates you are root)
Watch your screen so you can allow Superuser root access.
What we now can do
-Run root only apps such as SetCPU, drocap2, AdFree, Titanium Backup, etc.
-Have full access to the system to change framework, themes, etc.
-Install root only ports (i.e. Samsung Galaxy S LWPs?)
What we cannot do yet
-Don't have a full recovery method, in case you screw something up royally
-Don't have custom kernels for overclocking
-Bootloader is still locked, can't flash custom ROMS
Thanks for posting this here...has anyone come up with a way to remove the Blockbuster application? I downloaded Root Explorer and my search for "Blockbuster" only shows the installer apk.
PC mode. Also, make sure you have ADB configured first, this requires a lot of command prompt work.
There's a link the in the first post on how to configure ADB if you do not know how to do that.
Thanks I rooted my Dinc so I'm good with the prompt. I just didn't see anything about the mode which seems like a pretty important step. Did I just miss it?
Thanks for the "How To Guide" for us Android noobies Fab.
I'm still a bit weary of rooting my device though, I don't know why. What truly is the biggest gain to rooting besides being able to Wi-Fi tether at the moment?
Does this void any and all warranties/insurance tied to the device?
rotting nub here.... Do any of these steps risk bricking your phone? I'm specifically looking at that toggle wifi on/off immediately after the next step portion. We won't brick our phones if we miss-time it will we?
thanks!!! this is sweet exploit exploit exploit exploit!
If I root it, is there a way to reset it back to no root access? For example if I do a factory reset do we know if this will reset it back to stock with no root access?
If I root it, is there a way to reset it back to no root access? For example if I do a factory reset do we know if this will reset it back to stock with no root access?
If I root it, is there a way to reset it back to no root access? For example if I do a factory reset do we know if this will reset it back to stock with no root access?
Not yet, but I'm sure we will have it in a matter of days.
Done, wireless tether for root works great. Took all of fifteen minutes including installing the sdk which i didn't have on this computer. Thanks birdman and the entire development community.
Last edited by swagner53; July 22nd, 2010 at 01:04 PM.
Ok I am stuck. I have downloaded everything I need and am familiar with using a command prompt. Here is where I am stuck:
In the device manager my phone is listed as "Android Composite ADB interface" but at the command prompt I type "adb devices" and the list is empty so I can't get past this step. I am running Windows Vista 32bit. Can someone please help me get past this step? Thanks.
__________________ Nexus 4, rooted, AOKP, and LTE -Charlie Walters
Don't forget to click "Thanks" if someone helps you out
I'm pretty good with computers but have had an EnV2 until now so as you could guess I'm pretty far behind when it comes to phone tech. Can anyone explain to me the pros (I'm sure there are tons but once again a noob) of rooting it. Isn't it already supposed to be pretty much "uncapped" since it runs Android and not a Mac based software? Again any help with understanding this is appreciated.
__________________
Whatever your phone can do, my Droid X can do better (and faster, and more efficient, and cooler).
Ok I am stuck. I have downloaded everything I need and am familiar with using a command prompt. Here is where I am stuck:
In the device manager my phone is listed as "Android Composite ADB interface" but at the command prompt I type "adb devices" and the list is empty so I can't get past this step. I am running Windows Vista 32bit. Can someone please help me get past this step? Thanks.
yes I turned it on. When I am in PC mode USB debugging is not connected. When I switch to USB storage mode then USB debugging connects, but then when I try to push superuser.apk to the SD card I get an error saying "Permission denied"
not working for me either. im on windows 7. that adb thing is what wont work. it says everything is updated to the latest drivers. then when i run the cmd prompts for adb i get
"adb is not recognized blah blah"
what do i do now
also when i try to browse and click on the folder i get
"best driver for this device is already installed"
Last edited by bumpylemon; July 22nd, 2010 at 12:56 PM.
question regarding adb. i have it all setup for my dinc. if i installed drivers for the Dx, that won't mess up my connectivity with my dinc right?
also...for the wifi tether. for those who got it to work. there's no special things you have to do? just install from market? i remember for my dinc i had to put some files in some directories to make it work.
use the motorola usb drivers instead of the android ones. It installs everything for you automatically. also you need to download the sdk tools to get the adb program
The Following 2 Users Say Thank You to chaosman For This Useful Post:
Excellent,
my gratitude goes to all those involved in this process. Now comes (from what I've read) the much more difficult part of cracking the boot loader.
Once that's done we'll truly have a way of ensuring custom updates and back-ups if we screw up. Not to mention eliminate the need/ chance for future ota's undoing all the changes.
not working for me either. im on windows 7. that adb thing is what wont work. it says everything is updated to the latest drivers. then when i run the cmd prompts for adb i get
"adb is not recognized blah blah"
what do i do now
also when i try to browse and click on the folder i get
"best driver for this device is already installed"
Device(s): DROIDX, Droid Eris, 4 HP touch pads that will be running ANDROID!
Carrier: Not Provided
Thanks: 23
Thanked 24 Times in 19 Posts
Quote:
Originally Posted by chrlswltrs
Ok I am stuck. I have downloaded everything I need and am familiar with using a command prompt. Here is where I am stuck:
In the device manager my phone is listed as "Android Composite ADB interface" but at the command prompt I type "adb devices" and the list is empty so I can't get past this step. I am running Windows Vista 32bit. Can someone please help me get past this step? Thanks.
What folder are you in (at the cmd prompt)? You need to be in your androsdk tools dir. As an example, mine lives on my C drive located as C:/androidsdk/tools
Once you are in the TOOLS dir of your androidsdk folder, THEN type adb devices and see if you are able to locate your device.
What folder are you in (at the cmd prompt)? You need to be in your androsdk tools dir. As an example, mine lives on my C drive located as C:/androidsdk/tools
Once you are in the TOOLS dir of your androidsdk folder, THEN type adb devices and see if you are able to locate your device.
Tried that, there is still no devices listed.
It will list it when I switch my X to USB mass storage, then USB debugging connects.
When I am in PC mode my phone is not listed in ADB devices and USB debugging will not connect
1: You need the Android SDK from Android SDK | Android Developers. I put it in my DroidXRoot folder which is in my C:. (So it's CroidXRoot/android-sdk-windows/).
2: If, when you run "adb devices" you get "adb is not recognized as and internal or external command, operable program or batch file.", then you need to do a little extra.
-in Windows 7/Vista. click start and type system var and hit enter. Go into "Environment Variables". From here, select "path" from the bottom list box and choose "edit". Add your sdk location (mine is CroidXRoot/android-sdk-windows/tools) to the end of this. Just copy and paste the following to the end of the string which pops up when you click "edit":
;C:\DROIDXRoot\android-sdk-windows\tools
In XP, right-click "my computer" choose "properties" . from he select advanced, and then "environmental variables". Now follow the instructions just above.
Now, re-run "adb devices" and your X should show up.
The Following User Says Thank You to humungus For This Useful Post:
***[How-To] Root your Droid X***
