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

Root [Release] Android 2.2 Froyo for the Droid X

Kernel says .32 .... the highmem (>256 mb ram) fix didn't come until .33 I believe.

I lost root on this. I copied (not moved) su to xbin. That was probably it.

Other than that, not having all my ram, and still having motoblur it is all good.
 
BLK MAJK said:
THIS.

I am exactly the same way. I followed the alldroid guide too....not real excited about losing root. That and my quadrant scores are basically the same as with 2.1 (1350's)....
Click to expand...

Drocap works for me, asked for permissions ans I gave it, but rootexplorer won't won't do the same.
 
I was using root explorer (after updating to 2.2) and just noticed that all of the stock apps have a duplicate with a .odex extension. What's this for?
 
Ok guys, for those of you missing root after this, I noticed something:

The copy of su that you copied to xbin still works to give you root access if you open up a terminal and type "/system/xbin/su"

I'm currently mounting my /system/ as rw and trying to copy it back, by running the xbin/su to do it.

You might try this, I'll report back soon if it works fully.
 
I don't know why I did it, but I couldn't resist. Hopefully, if this isn't final, it won't be a big ordeal and require a system wipe to get final on here.

First, I backed up system data and apps using Titanium.

I then unfroze all of the apps that I had frozen with Titanium. I then MOVED su from system/bin to system/xbin.

Rebooted into recovery mode and installed update.zip.

After staring at the red eye for about 3-4 minutes, system came back up successfully.

I did indeed keep root.

Wow, lucky, that went very smoothly.

Very curious to see if this bug was resovled
http://androidforums.com/support-tr...428-battery-drain-due-software-bug-w-gps.html

Will be testing it shortly.
 
Quasse said:
Ok guys, for those of you missing root after this, I noticed something:

The copy of su that you copied to xbin still works to give you root access if you open up a terminal and type "/system/xbin/su"

I'm currently mounting my /system/ as rw and trying to copy it back, by running the xbin/su to do it.

You might try this, I'll report back soon if it works fully.
Click to expand...

might be onto something with that. The alldroid guide said to COPY....leaving the old one behind...which is still installed on the system and referenced. I wonder if we blow out the original, somehow reinstall (or remap the call for the apps) the new copy in xbin...if we get it back...


EDIT: I can confirm that if I open my terminal emulator and run the version of SU that we copied to xbin, it gives me root access.....now we need to figure out how to make it call that one all the time....
 
Yeah, reporting back, copying the xbin/su to bin/su does not work. I still have the exact same problem as before. It seems to be somehow related to the position of the file? I'm going to try a "rm /system/bin/su" and then replace it fully...
 
BLK MAJK said:
might be onto something with that. The alldroid guide said to COPY....leaving the old one behind...which is still installed on the system and referenced. I wonder if we blow out the original, somehow reinstall (or remap the call for the apps) the new copy in xbin...if we get it back...


EDIT: I can confirm that if I open my terminal emulator and run the version of SU that we copied to xbin, it gives me root access.....now we need to figure out how to make it call that one all the time....
Click to expand...

Couldn't we just move it back to bin
nvm
 
BLK MAJK said:
I tried root explorer, wireless tether and even running SU in terminal emulator... "Permission Denied" :(
Click to expand...

Exact same here. I also use SwitchPro, which has a reboot phone function on it. This function requires root access, and it still works. However, I can't get my "#" prompt in Terminal using SU command (denied), as well as the other root apps. :confused:
 
I think the implication there is that koush has patched clockwork recovery to work with 2.2 and has incorporated it in an all in one .zip
 
Ok guys. Figured it out.

IF YOU LOST ROOT BECAUSE YOU COPIED su INSTEAD OF MOVING IT:

Full instructions on my blog: here

EDIT: 1. Open terminal and make sure su exists in /system/xbin/su and run it to get a root terminal. You should see a #
2. Run "mount -o rw,remount /dev/block/system /system"
3. Run "cp /system/bin/su /system/bin/su.bak"
4. Run "cd /system/bin/"
5. Run "rm su"

You now have root again.

If you screw this up, you will seriously screw things up, so do this at your own risk, and be careful.
 
Quasse said:
Ok guys. Figured it out.

IF YOU LOST ROOT BECAUSE YOU COPIED su INSTEAD OF MOVING IT:

EDIT: 0. Open terminal and make sure su exists in /system/xbin/su and run it.
1. Run "mount -o rw,remount /dev/block/system /system"
2. Run "cp /system/bin/su /system/bin/su.bak"
3. Run "cd /system/bin/"
4. Run "rm su"

You now have root again.

If you screw this up, you will seriously screw things up, so do this at your own risk, and be careful.
Click to expand...

hope you don't mind added to OP
 
Quasse said:
Ok guys. Figured it out.

IF YOU LOST ROOT BECAUSE YOU COPIED su INSTEAD OF MOVING IT:

Full instructions on my blog: here

EDIT: 0. Open terminal and make sure su exists in /system/xbin/su and run it.
1. Run "mount -o rw,remount /dev/block/system /system"
2. Run "cp /system/bin/su /system/bin/su.bak"
3. Run "cd /system/bin/"
4. Run "rm su"

You now have root again.

If you screw this up, you will seriously screw things up, so do this at your own risk, and be careful.
Click to expand...

Confirmed working! Many thanks Quasse!!:D
 
Quasse said:
I don't mind, (glad I could help out!) but you did spell my name wrong :p

Edit: I also just cleaned up my post a bit to make it clearer for everyone, if you want to cop that updated version.
Click to expand...

alright super fixed:D
 
Ok, so I was nervous to do this, but am antsy as hell so I gave it a whirl.

-I deleted logwrapper and renamed the logwrapper.bin, also deleted hijack file
-Reverted back to the old boot animation because I wasn't sure
-removed my overclocking
-removed my theme
-Copied the ADB instructions on how to xfer root to 2.2
-removed bootstrap (assumed with what I did first)
-took me alittle bit to boot into recovery, i had to do a battery pull
-updated the zip!
-that took about 3-5 minutes
-rebooted and i have froyo

Questions
1. Drocap works no problem (can I safely assume I have root?)
2. Titanium Backup says it cannot find root access

What gives? heh

Do I need to perform Quasses troubleshooting even though I did it via adb as stated on alldroid?

Thanks!
 
You must log in or register to reply here.
Back
Top Bottom