• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ***[How-To] Root your Droid X***

I agree with the hesitant folks. I'll only root my X when we have a confirmed way to return to stock so that froyo can be installed. That only makes sense...

Great job on the quick root tho. Now we just need that bootloader lol. Also, with the new law out it's finally legal to root our phones! Although I'm sure it still violates the EULA and voids the crap outta all warranties lol. Though I'm pretty sure that if you have insurance on your phone you can still use that without any issues. That's a no questions asked deal. Just pay the deductible ($50 for me since I'm grandfathered in lol) and they send you a brand new handset and you ship yours to them in the included postage-paid envelope =0)

But ya, I'll wait until we can reverse the process to do this. Can never be too careful with a $500+ phone lol.
 
Simply having rooted your phone should not brick your phone during any update. Rooting is simply getting super administrator permissions. That would not cause an update to fail or brick your phone.

Now what you do after getting root can absolutely cause and issue with updates as experienced with .604. However, you should be fine if you don't remove any files or applications after getting root. Adding apps and files probably won't cause an issue, but removing OEM files might.

The short answer is simply don't remove any files or applications after getting root and you will be fine.
 
colchiro said:
The biggest obstacle to installing froyo could be deleting apps that came preinstalled (like Blockbuster, CityId, etc). Missing these apps broke the 604 upgrade for some people, apparently b/c it checked for these apps so it could update them.

Whether or not missing preinstalled apps will break froyo, will soon be determined.
Click to expand...

Hmm didn't think these "these non system" would of made a difference. Guess I will reinstall, JIC.
 
That's why instead of actually removing the apps, I chose to use Titanium Backup to "freeze" them. It makes them invisible to the system, and not consume any RAM by running in the background.

So if I ever want to unroot and do the Froyo OTA, it's just a matter of unfreezing these apps and then removing the superuser files.
 
Well, since we're getting 2.2 in a month or so, it would probably be wiser of me not to delete any files? Not even CityID? TIA.
 
How far can theming go without being able to install custom ROMs? I'm coming from a rooted Droid, and I'm used to just downloading a zip and installing it the same way I would a ROM. Not sure how I would go about it.

I broke my Droid and will get my Droid X by the end of the week and I just want to get rid of that god awful grey notification bar.
 
Steven58 said:
Well, since we're getting 2.2 in a month or so, it would probably be wiser of me not to delete any files? Not even CityID? TIA.
Click to expand...
I would say that's a good decision. I just got my replacement DX today and rooted it right away for the apps, but won't be removing anything until 2.2. I might freeze some stuff with Titanium Backup though.
 
You have debugging on right and its in pc mode if its still not recognizing it, its going to take some some extra steps. Keep it plugged in
 
droider13 said:
You have debugging on right and its in pc mode if its still not recognizing it, its going to take some some extra steps. Keep it plugged in
Click to expand...

OK Also in device manager it doesn't say Droidx it says: Moto Composite ADB Interface
 
droider13 said:
At the very top of the device manager does it say android something
Click to expand...

ADB Interface when I open it says: Moto Composite ADB Interface.
Now warning icon its looks good to go at this point but the MTP Interface window only says Droix no serial #.
 
This is to choppy maybe the easy method is the better one for me.
Are there any negative effects verse the manual way?
 
n0m0n said:
ADB Interface when I open it says: Moto Composite ADB Interface.
Now warning icon its looks good to go at this point but the MTP Interface window only says Droix no serial #.
Click to expand...

In adb if you type
adb devices does a serial number show
 
n0m0n said:
Yeah this time it did before I was typing adb devices in the run window, and the dos prompt flashed for a second.
This time I opened a cmd prompt.
Click to expand...

Then its simple lets do it
Download this an put all the files in it into I am guessing your tools folder or where your adb.exe is located
And then follow these instructions If you get stuck any where let me know

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.
 
First line returned the following cannot stat 'Superuser.apk': no such file or directory.

Should this have been placed on the sdcard as well?
I dropped it in the tools folder as directed.
 
n0m0n said:
Yes unzipped the download and select all copy paste in the folder where the SDK exe is.
Click to expand...

I am not sure why it couldn't find it unless you pointed the cmd to the wrong place. See what I have is the tools folder right on my desktop
so when I do
cd C:\Users\Jeff\Desktop\tools
i am ready to go, eacj file is in there individually right, not the folder. I know adb is right because it didn't say adb:not found
 
droider13 you still here?

Got to exploit pressed enter and then toggled wifi on and off... permission denied
Tried again with BT same outcome.

Now I type ./exploid and then toggle right?

Tried repeatedly

Do I have to start in the beginning again?
 
n0m0n said:
droider13 you still here?

Got to exploit pressed enter and then toggled wifi on and off... permission denied
Tried again with BT same outcome.

Now I type ./exploid and then toggle right?
Click to expand...

Alright we are making progress:D
So this is what I did, before I ran ./exploid I turned on bluetooth and then right after I ran it I turned it off then back on then run rootshell
 
But I enter exploit and within a half second it says permission denied not even enough time to turn off and on.

Do I have to start from the beginning?
 
You must log in or register to reply here.
Back
Top Bottom