1349 replies to this topic

[Giblet535]

SU doesn't even show TB in the log. Only apps allowed shown are ES File Explorer, ROM Manager, Root Check Basic, Root Explorer & Voodo OTA RootKeeper.

NP here.

Check permissions on /system/bin/su maybe.

Bring up a terminal or ConnectBot in "local" mode.

Please Login or Register to see this Hidden Content

The owner should be root or 0 (zero), the group should be root or 0, and the mode should be -rwsr-sr-x (octal 6755 - read/write/setuid for owner, readonly/setuid for group members like you, and readonly/execute for others)

Commands for correct permissions:

Please Login or Register to see this Hidden Content

[MrFrankRazr]

Some apps have SU access but any new apps try and are not able to gain SU access. I also tried to update SU and failed. Not able to install BB either.
Maybe if i install ICS again.....?

[Aixelsyd]

I took a very different route to get to the same place.

Now I'm bored.

I can't imagine why people are going all the way back to 744... Just remove the two "oem" operations in the 173 fastboot xml, and RSD that.

Agreed it makes no sense and a waste of time going all the way back to .744. I've fastbooted directly to .173 my device 4 times this week and messing with ICS leak without issue as I figured out my dumbass mistake I was making on loosing root

[Giblet535]

Some apps have SU access but any new apps try and are not able to gain SU access. I also tried to update SU and failed. Not able to install BB either.
Maybe if i install ICS again.....?

Maybe, but I would try to understand the problem before doing something as drastic as reflashing. You'll likely wind up right where you are now, trying again, and maybe yet again, and finally, looking into why root wasn't correctly preserved/restored.

The command line interface can be intimidating, but we either post complete/correct commands or we get banninated by the modmins.

[MrFrankRazr]

Maybe, but I would try to understand the problem before doing something as drastic as reflashing. You'll likely wind up right where you are now, trying again, and maybe yet again, and finally, looking into why root wasn't correctly preserved/restored.

The command line interface can be intimidating, but we either post complete/correct commands or we get banninated by the modmins.

Yeah i'm familiar with the commands. I check via Root Explorer and the SU perms were -rwsr-sr-x.
But I'm gonna download Terminal Emulator and run the above commands and see what happens.

[Aixelsyd]

Some apps have SU access but any new apps try and are not able to gain SU access. I also tried to update SU and failed. Not able to install BB either.
Maybe if i install ICS again.....?

Curious what Superuser.apk icon is in your app drawer. Green icon or the Skull & Crossbones

[Giblet535]

Agreed it makes no sense and a waste of time going all the way back to .744. I've fastbooted directly to .173 my device 4 times this week and messing with ICS leak without issue as I figured out my dumbass mistake I was making on loosing root

Guessing: I think the OP went that route because of the errors in RSD with stock 173 FB files.

And the only reason to RSD is to get rid of any custom recovery mods (SafeStrap in my case) that prevent the leak from installing.

It took a surprisingly long time to figure that out... Moto should publish a README or INSTALL doc with their leaked updates!

[MrFrankRazr]

Curious what Superuser.apk icon is in your app drawer. Green icon or the Skull & Crossbones

Green icon 3.0.3....when i try to update it show the 3.0.3.2 is newer to install... but fails.

Edited by MrFrankRazr, 06 April 2012 - 11:23 AM.

[Giblet535]

Green icon 3.0.3....when i try to update it show the 3.0.3.2 is newer to install... but fails.

The failure on update points at a permissions problem.

Long-click /system/bin/su in root explorer, select Properties...: Owner should be "root", group should be "root", Permissions should be rwsr-sr-x (6755 octal for chmod command).

/system/xbin and /system/bin directories: owner root, group shell, Permissions rwxr-xr-x (755 octal for chmod)

If any of those three are different than the above, then that's probably the problem.

[Aixelsyd]

Guessing: I think the OP went that route because of the errors in RSD with stock 173 FB files.

And the only reason to RSD is to get rid of any custom recovery mods (SafeStrap in my case) that prevent the leak from installing.

It took a surprisingly long time to figure that out... Moto should publish a README or INSTALL doc with their leaked updates!

The error in the .173 FB is an easy fix tho. Just need to swap out the small *.xml in the full .173 fastboot file and then it will install just fine using RSD Lite without issue

[abrarey]

That's probably the Smart Actions app because you have a low battery.

Sent from my DROID RAZR using Tapatalk

Yup it was about the Smart actions I disable one of the task to extend battery life and seems to be fine so far.
Thanks!

[Giblet535]

The error in the .173 FB is an easy fix tho. Just need to swap out the small *.xml in the full .173 fastboot file and then it will install just fine using RSD Lite without issue

Really? I only had one XML file in my full fastboot: VRZ_XT912_6.5.1-167_DHD-14_M2-5_CFC_1FF_01.xml

I used vi on it. There are two <step operation="oem".... There's no such operation in RSD-Lite. Those lines get deleted.

[Aixelsyd]

Green icon 3.0.3....when i try to update it show the 3.0.3.2 is newer to install... but fails.

Hit DDX up he has a thought. not sure it will do the trick as I got updated and would have tested first. I ran into the troubles you are having until I got to the point of making sure su & Superuser were updated and current PRIOR to protecting root using rootkeeper

[Aixelsyd]

Really? I only had one XML file in my full fastboot: VRZ_XT912_6.5.1-167_DHD-14_M2-5_CFC_1FF_01.xml

I used vi on it. There are two <step operation="oem".... There's no such operation in RSD-Lite. Those lines get deleted.

for sure is a fix for it to work without issue. Here is the link to the thread where DirtyDroidX has the info in the OP. I have yet to ever use the .744 or .748 FB files on my device strictly using .173 FB without issue along with RSD Lite5.6

Please Login or Register to see this Hidden Content

[Giblet535]

for sure is a fix for it to work without issue. Here is the link to the thread where DirtyDroidX has the info in the OP. I have yet to ever use the .744 or .748 FB files on my device strictly using .173 FB without issue along with RSD Lite5.6

Please Login or Register to see this Hidden Content

I reinvented a lot of "wheels" this week. That's another one!

[Aixelsyd]

I reinvented a lot of "wheels" this week. That's another one!

lol..... been there done that many times over the yrs messing with this stuff.

[money mike]

Fyi, widgetsoid works correctly with ics if you want a pull down notification toggle.

Sent from my DROID RAZR using Tapatalk

[rexboe]

You don't have to put both files in cache just the zip will work. I've done it twice with just the zip and it works fine.

[Aixelsyd]

You don't have to put both files in cache just the zip will work. I've done it twice with just the zip and it works fine.

Not always and the one is very very small anyways. So i would NOT suggest ppl doing it with the one file only. IMO better safe then sorry using both so you don't have to fully start over again