[Q] Help - adb shell permission denied, after Vega Tools problem

eclaro

New member
Jun 23, 2012
3
0
0
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.

When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.

So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.

After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.

I realized that the script ran by VegaTools did this "amazing" thing:

adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync

So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.

Ok, my situation now is:

I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:

C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -

So, I cannot get into the device to fix the permissions, and cannot do anything else.

Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:

C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device

Before that, only the emulator one appeared.

Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?

I am using adb on windows.

Thanks a lot for any help, in advance.

Eduardo


EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
 
Last edited:

eclaro

New member
Jun 23, 2012
3
0
0
No one can help me?

I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.

When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.

So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.

After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.

I realized that the script ran by VegaTools did this "amazing" thing:

adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync

So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.

Ok, my situation now is:

I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:

C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -

So, I cannot get into the device to fix the permissions, and cannot do anything else.

Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:

C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device

Before that, only the emulator one appeared.

Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?

I am using adb on windows.

Thanks a lot for any help, in advance.

Eduardo


EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
Please, any help?