Updated to 2.2... LOST ROOT. Anyone else?

[Noflex]

First post here thought I'd share my experience today with this.

PLayed a few times with the froyo unofficial update on the X.

First round got that logwrapper bs. Fixed, sbf'd back to 2.1, rooted. Then Froyo'd

NOTICED my rooting failed. Messed it up I guess.

Cleaned cache, wiped data, SBF'd then Froyo'd No root, just wanted to see it for what it was.

Got bored, cleared cache, wiped data, SBF'd, THEN ROOTED then Froyo'd
Then Lost root pretty sure I did it right as I ran my root apps. Then they stopped functioning.

Tried to rename using root explorer and would;nt R/O anymore.

All I did was do a reset using quickboot (which needs root) asked for permission and it was a go.

Came back with root. SO reset maybe? But seriously like sbf'd 3-4 times today. 2.1->2.2->2.1->2.2->....... blah not messing with it anymore. It works, I'll try to help if I can but sbf is needed for sure.

 

[fwaggle]

lost root too. Hope someone can figure this out. I dont want to use SBF and start over. Help...

thanks,

AC

If you still have a working busybox, this might track down where you put su:

busybox find /system -perm -2000 -print

If it spits out something like /system/xbin/su or /system/xbin/suwhoopsitypoed, then type that entire command in (including the full path) and you should get root privs.

If you didn't copy su, then after the update su is clobbered and set non-suid, so you'll have lost root.

I believe the only way out of that is to SBF back to 2.1 (see "Unbricking your DroidX" thread), rooting, and then re-upgrading following the instructions carefully.

 

[aaronc_98]

lost root too. Hope someone can figure this out. I dont want to use SBF and start over. Help...

thanks,

AC

If you still have a working busybox, this might track down where you put su:

busybox find /system -perm -2000 -print

If it spits out something like /system/xbin/su or /system/xbin/suwhoopsitypoed, then type that entire command in (including the full path) and you should get root privs.

If you didn't copy su, then after the update su is clobbered and set non-suid, so you'll have lost root.

I believe the only way out of that is to SBF back to 2.1 (see "Unbricking your DroidX" thread), rooting, and then re-upgrading following the instructions carefully.

Thanks. i didnt copy the file before the update so I guess that I will have to SBF back to 2.1 and do it right, unless someone comes up with a way to root 2.2 before i get around to it...

thanks,

AC

 

[tony1208]

Dam I am in the same boat also...freaking droid-life did not mention moving the su file over to keep root...I really don't want to sbf flash ....

Sent from my DROIDX using Tapatalk

 

[JMC1018]

i also lost root when i updated. thing is i copied the file to where it was suppose to go and still lost it. no big deal im sure there will be a fix soon

 

[tony1208]

i also lost root when i updated.
thing is i copied the file to where it was suppose to go and still lost it. no big deal im sure there will be a fix soon

That's what I am thinking...2.1 was rooted in like a week so hopefully 2.2 will be too


Sent from my DROIDX using Tapatalk

 

[fwaggle]

i also lost root when i updated. thing is i copied the file to where it was suppose to go and still lost it. no big deal im sure there will be a fix soon

Did you try this?

busybox find /system -perm -2000 -print

 

[JMC1018]

i also lost root when i updated. thing is i copied the file to where it was suppose to go and still lost it. no big deal im sure there will be a fix soon

Did you try this?

busybox find /system -perm -2000 -print

ill try it out now...wont install busy box. says its rooted then says busy box not installed. when i try to install it status says fail due to not having nand unlocked or was unable to remount.

 

[fwaggle]

ill try it out now...wont install busy box. says its rooted then says busy box not installed. when i try to install it status says fail due to not having nand unlocked or was unable to remount.

You can probably push busybox to /tmp, and then chmod 755 it and then run /tmp/busybox <whatever busybox command you want>.

I'm personally betting something mis-fired when you tried to do the "save your root" step - some of the upgrading instructions I've seen out there don't really go to very great lengths to tell you the really critical steps if you want to keep root.

If you get busybox on there and you don't have any copies of su that are suid, then you basically have two options right now: 1) wait for someone to root Froyo on this phone (if I had the money to lose, I'd put money on a Droid2 root exploit being workable on the X as well) or 2) SBF back to 2.1 and give it another go.

 

[tony1208]

i also lost root when i updated. thing is i copied the file to where it was suppose to go and still lost it. no big deal im sure there will be a fix soon

Did you try this?

busybox find /system -perm -2000 -print

ill try it out now...wont install busy box. says its rooted then says busy box not installed. when i try to install it status says fail due to not having nand unlocked or was unable to remount.

where do i type that ?

 

[fwaggle]

where do i type that ?

abd shell or a terminal emulator.

 

[JMC1018]

When I run/ system/xbin/su I can get the permission. Just have to figure out how to get tthe apps to work. Can I move su back into bin?

 

[fwaggle]

When I run/ system/xbin/su I can get the permission. Just have to figure out how to get tthe apps to work. Can I move su back into bin?

I didn't move it, I just did busybox chmod u+s /system/bin/su and it got the desired effect. If you're wondering why I'm so into busybox, it's because the stock android binaries don't support a lot of the handy arguments. chmod 4755 /system/bin/su probably has the same effect, if I have my octal file modes correct.

I figured leaving another copy in xbin would probably not hurt if there's another OTA update that clobbers setuid /system/bin/su.

 

[Happystranger]

:icon_ banana:Success..Finally got Root back after losing it today from updating to Froyo. Even though I did move su to xbin, I had lost root. Here's what I did:

In Terminal Emulator:

/system/xbin/su (if you moved your su to the xbin before updating, this should grant you permission and you should see the # symbol)

Type the following after the previous command:

mount -o rw,remount /dev/block/system /system
mv /system/bin/su /system/bin/su.bak
cd /system/xbin/
cp su ../bin/

Again this only worked for me because I actually did move my su to the xbin directory prior to updating. Thanks Fwaggle and Jbeck22 at Mydroidworld for the scripts.

 

[JMC1018]

happy stranger thanks alot worked like a charm