Database Users

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish

usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556

Great post, very easy to follow, thank you.

yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help

this also works for the samsung Galaxy S in recovery mode.

mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline

hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx

yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)

just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers

Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?

{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.

Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App

Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey

Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo

pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA

Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons

Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !

Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination

Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...

rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

Best Guide Online on how to Root your X

I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.

This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
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" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will 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, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.

Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App

ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own

MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.

I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.

How to remove .apk's: A Complete Newbs Guide

So, I'm a newb. I got my Incredible and all I wanted to do was root it so I could start picking it apart. I patiently waited, reading all the posts on here and all the flaming by complete jackholes, that weren't contributing at all to any of the discussions. unrevoked, with all of their hard work, nailed it! It is now pathetically simple to root your Incredible.
I recently started installing custom ROMs on my Incredible (Jager, Virtuous, Ultimate Droid and SkyRaider). They're all great ROMs, but I totally dug CrystalClearROMs Ruby. It's slim, fast and intuitive. But, it had some bloatware that I didn't want, namely Amazon MP3. I researched and found a couple of pages that explained how to remove .apk's from other phones but not from the Incredible (correctly). After piecing the parts together, I came up with this...hope it helps.
I take no responsibility for you screwing your phone up. This worked perfectly on mine.
Pre-requisites
Your Incredible must be rooted
You must have ClockworkMod installed
You must have ROM Manager installed (buy it, it is totally worth it)
You must have the Android 2.2 SDK installed
You have to be able to follow directions
These directions assume you are using Windows 7
I would post links to all of this stuff, but I'm a newb and I can't post links...sorry.
OK, here goes...
Connect your Incredible to your PC with the micro USB port. You need to have the proper drivers installed and USB debugging turned on.
Open ROM Manager and select "Reboot into Recovery".
After your phone reboots, select "mounts and storage" and press the optical trackpad.
Select "mount /system" and press the optical trackpad.
Press the power button to return to the previous menu.
On your PC, unzip the Android SDK and place it in a folder, where you can get to it.
Browse to the Tools folder in the SDK and hold down shift while you right click inside the folder. Select "Open command window here". A command window should open in C:*****\android-sdk-windows\tools>
Type "adb devices" (without the quotes. all directions from here out are without the quotes). Your display should say..."List of devices attached" followed by a custom string of digits and the word "recovery". If you don't see this, you've done something wrong.
Try using your up and down arrow keys while in the cmd window instead of re-typing
Now type "adb shell". You should get "~ #" in the cmd window.
You are now browsing your Incredible using the shell.
Useful commands while inside the shell...
ls = list
cd = change directory
cd / = to the top directory
exit = exit out of the shell
Type "cd /system/app". You are now browsing the "system/app" directory.
Type "ls" to see a list of apk's that are currently installed on your Incredible.
The Amazon MP3 apk was named "com.amazon.mp3.apk".
To delete it, type "rm com.amazon.mp3.apk" and press enter.
This will work with any apk. However, make sure you know what you're deleting. You can do really bad things to your Incredible if you delete the wrong apk!
Once you've deleted all the apk's you want to, select "reboot system now" on your Incredible and sit back and enjoy an adult beverage, while your Incredible reboots.
Hopefully, if you've done everything right, your phone reboots with the offending app gone from your Incredible. If not, you better re-install your OS.
I hope this helped you in your quest to create the perfect ROM. Let me just say again that I love CrystalClearROMs Ruby. If you're looking for the ultimate in trimmed down ROM, look no further. If you want the Market, make sure you install the version with Google Apps or you'll be installing apk's to get it.
Good luck!
Jeremy

You should include instructions on fully removing said apks, including the use of pm. Just deleting is often not enough.

Just wondering, is it fine to just delete the apk in Root Explorer?

is it not the same to just remove them using root explorer?

What's the difference between apks in /system/app folder and /data/app folder ? I can easily delete (or move to another backup directory) the apks from the system/app folder and they disappear from the apps list. However, when I move/ delete apks from /data/app directory, they still remain there.
Yes, I can uninstall the apps in /data/app directory, but that's not what I want to do. I just want to move it temporarily and move it back when I need it.
Thanks

just to put my $0.02... i wouldnt totaly delete them, just in case you need to reinstal for whatever reason. try this instead...
mkdir /system/app.disabled
mv /system/app/"whateverapp".apk /system/app.disabled/
that way youre not seeing or using them but still around if you need to get them back. works for me anyway.....

I just use titanium backup and choose uninstall (i back the app up first incase I need it) easy and no shell commands.

Told you I was a newb. I checked out Titanium Backup and that is pretty sweet.
I am not familiar with pm...can anyone explain? Thanks!

From what I've read online the use of pm is
pm uninstall [nameofapk.apk]
Since its Linux I think you could type pm --help to get a full list and description of use but I'm not near a computer yet to test it

DX noob here. Anybody wanna help me out?

I ordered my DX earlier today and should have it tomorrow afternoon. (yay!)
I'm coming from the LG Ally, which I played around with quite a bit as far as root/roms go. I ended up bricking it when the Froyo update came out trying to get from 2.1 to one of the new 2.2.1 roms.
I've seen a lot of stuff about the DX and it looks like a lot of progress has been made (yay, again!). I love the look of Gingerbread, so I'd probably look into flashing one of the roms that supports a GB theme (Liberty looks cool!), but I don't want to run into trouble when the official GB release comes out.
So, how hard is this on the DX? What are the general steps? What in the world is a SBF?
Any sort of basic noob-friendly introduction would be greatly appreciated!
Thanks!

Here is a bunch of stuff I have put together for various people that should get you started:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r08-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following:
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ( at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers <your operating system> you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.

Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!

lextex said:
Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!
Click to expand...
Click to collapse
No, you do not have to do it this way. I just used this as an example for something I was doing for someone else, especially since they needed the sdk anyways... Just was practice.
(PS, not sure what you mean by sideloading... sorry just not familiar with the term...) Nonetheless...
You can just download the file, and then use file manager to install the file or any app installer you may normally use. Just make sure that under Settings-->Applications-->Unknown sources, that the check box is marked. Then you should be good to go.
As for bootstrap... You are basically replacing a logwrapper file that tells the phone to boot to Motorola's built in recovery. Koush's bootstrap hijacks this and writes its own logwrapper and allows for the recovery process to be interrupted so backing up/restorying, etc. You can load that apk the same way you do Z4root.
As for SBF files, I'm can't recall what it actually stands for, but it is basically a file from Motorola that allowed their employees to flash a phone back to "out of the box" state in the event that a customer ruined their phone or had issues with it... this goes way back to even the Motorola Razor days I believe... In any event, it is used alongside a program called RSDlite. This program allows you to connect your phone to your computer and flash the sbf files that have been released, and as a result allows you to restore your phone back to a "clean" state in the event that you mess up the /system partition and for other uses as well.
I will be adding more to a basic guide for all things Droid X later this weekend. If you have more questions, feel free to post back. And check out my other post here:
http://forum.xda-developers.com/showthread.php?t=940986
This includes the same info as I posted here already, but should have some more updates this weekend.
Good luck!

new here also.
i thought droid x could not be rooted.
i bought mine in october 2010; it's running 2.2.1
thanks in advance

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.

66 people have read this and nobody has any suggestions to help?

i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....

I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?

Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'

juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.

Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer

If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!

I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.

Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer

OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."

ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number

Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?

First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.