On Fri, November 25, 2011 10:32 am, scott wrote:
> On 11/24/2011 01:42 AM, Voytek Eymont wrote:
> Sounds like permissions on su aren't set right. Try doing "adb shell
> chmod 4755 /system/xbin/su". Then "adb shell ln -s /system/xbin/su
> /system/bin/su". If that doesn't work, you may have to reroot the phone.
Scott, thanks for your help:
C:\motorola>adb shell chmod 4755 /system/xbin/su
chmod: permission denied
and:
C:\motorola>adb shell
# cd /system/xbin
cd /system/xbin
# ls
ls
ls: permission denied
# su --help
su --help
Usage: su [options] [LOGIN]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login make the shell a login shell
-s, --shell SHELL use SHELL instead of the default in passwd
-v, --version display version number and exit
-V display version code and exit. this is
used almost exclusively by Superuser.apk
# su --version
su --version
3.0
# su -v
su -v
3.0
> If you did an OTA update since it's been rooted, before you put CM7 on
> it, that's more than likely the problem.
I probably ? did, technically, not OTA as the phone didn't see it, but,
downloaded from Mot site, installed over USB, I guess 'same thing' in this
context ?
but CM7 and all stuff worked good, the problem really started couple days
ago. when certain things stopped working, like WiFi stopped connecting.
as it is, I can see there is a newer build of CM7, what's best path forward:
install the 'new' CM7 first, and start from there ?
--
Voytek
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
