On 11/28/2011 12:09 AM, Voytek Eymont wrote:
On Fri, November 25, 2011 12:57 pm, scott wrote:
On 11/24/2011 07:56 PM, Voytek Eymont wrote:
That's what I would do.If it ends up that you can't put it on, you'll
just have to reroot. It's also possible that you end up with the same
problem afte
On Fri, November 25, 2011 12:57 pm, scott wrote:
> On 11/24/2011 07:56 PM, Voytek Eymont wrote:
> That's what I would do.If it ends up that you can't put it on, you'll
> just have to reroot. It's also possible that you end up with the same
> problem after the installation, in which case you'll h
On Fri, November 25, 2011 12:57 pm, scott wrote:
> On 11/24/2011 07:56 PM, Voytek Eymont wrote:
> That's what I would do.If it ends up that you can't put it on, you'll
> just have to reroot. It's also possible that you end up with the same
> problem after the installation, in which case you'll ha
On Fri, November 25, 2011 12:57 pm, scott wrote:
> On 11/24/2011 07:56 PM, Voytek Eymont wrote:
> That's what I would do.If it ends up that you can't put it on, you'll
> just have to reroot. It's also possible that you end up with the same
> problem after the installation, in which case you'll ha
On 11/24/2011 07:56 PM, Voytek Eymont wrote:
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".
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 rero
On 11/24/2011 01:42 AM, Voytek Eymont wrote:
On Thu, November 24, 2011 5:17 am, Troy Rollo wrote:
On Thursday 24 November 2011 12:42:17 Voytek Eymont wrote:
Sounds like you could have aegisfs or some similar evil getting in your
way. Just in case, though, try "mount" to find out what's mount
On Thu, November 24, 2011 5:17 am, Troy Rollo wrote:
> On Thursday 24 November 2011 12:42:17 Voytek Eymont wrote:
> Sounds like you could have aegisfs or some similar evil getting in your
> way. Just in case, though, try "mount" to find out what's mounted, and
> then use "mount --o remount,rw" on
On Thursday 24 November 2011 12:42:17 Voytek Eymont wrote:
> BUT, using say 'ghost commander' I can enter /system/bin (or xbin) and can
> see files there, BUT, when I try 'get info' on busysbox, I get 'permission
> denied'
Sounds like you could have aegisfs or some similar evil getting in your way
On Thu, November 24, 2011 10:37 am, scott wrote:
> On 11/23/2011 05:07 PM, Voytek Eymont wrote:
> Download a terminal emulator and su into it. "chmod 755 /system/xbin"
> should do it. Busybox was probably installed into /system/bin and not
> /system/xbin. Maybe a newer version tried to install t
On 11/23/2011 05:07 PM, Voytek Eymont wrote:
I have Motrix phone with CM7, CM7 was installed with no issues about 8
weeks ago, all worked fine since then
it has busybox by stericson sp?, that has fairly regular updates that get
installed as they come
BUT, the latest busybox update fails install
I have Motrix phone with CM7, CM7 was installed with no issues about 8
weeks ago, all worked fine since then
it has busybox by stericson sp?, that has fairly regular updates that get
installed as they come
BUT, the latest busybox update fails install with 'unable to mount xbin r/w'
as I noticed
12 matches
Mail list logo
