[WFX] Android ADB 8.8

Discuss and announce Total Commander plugins, addons and other useful tools here, both their usage and their development.

Moderators: Hacker, petermad, Stefan2, white

Post Reply
p.eter
Junior Member
Junior Member
Posts: 35
Joined: 2013-04-18, 08:43 UTC

Post by *p.eter »

@Li Yongzhen
thank you for your answer, but for installing busybox, root is required. Therefore that's no option for me (plz read my answer to jakub!).
Is there any other solution?
G
Peter
Top
Li Yongzhen
Junior Member
Junior Member
Posts: 64
Joined: 2010-04-04, 10:46 UTC

Post by *Li Yongzhen »

p.eter wrote:@Li Yongzhen
thank you for your answer, but for installing busybox, root is required. Therefore that's no option for me (plz read my answer to jakub!).
Is there any other solution?
G
Peter
you can install a mount tool, such as Multi Mount SD-Card, Dual Mount SD Widget, or stick mount, etc.
examine them one by one, maybe there is one without requiring rooted.
Top
User avatar
Tahattmeruh
Senior Member
Senior Member
Posts: 244
Joined: 2003-05-16, 13:35 UTC

Post by *Tahattmeruh »

I have one bug with Android ADB 6.4 and earlier which I don't have with TotalAndDroid. I have a very large (6GB) titanium backup folder on my sd-card with over 10000 files. TAD needs a long time and shows the content of the folder. AADB also takes a long time but finally shows me an empty folder. Can you fix this bug?
Top
cmlx
Junior Member
Junior Member
Posts: 19
Joined: 2011-01-31, 02:42 UTC

Post by *cmlx »

@jakubklos

I just found this plugin supported to show apk properties, including name, package, version and permissions. However the version is only VersionName, I want it to show VersionCode too, could you please add this?
Top
icfu
Power Member
Power Member
Posts: 6052
Joined: 2003-09-10, 18:33 UTC

Post by *icfu »

I just moved an APK file from HD to /system/app. The resulting file size is 0 bytes. The original file is gone.

Looks like files get corrupted when free space is lower than the copied file size.
This account is for sale
Top
jakubklos
Senior Member
Senior Member
Posts: 221
Joined: 2012-07-11, 14:48 UTC

Post by *jakubklos »

icfu wrote:I just moved an APK file from HD to /system/app. The resulting file size is 0 bytes. The original file is gone.

Looks like files get corrupted when free space is lower than the copied file size.
As always logs would help me. But I think this should be an ADB protocol issue. We will see
Top
icfu
Power Member
Power Member
Posts: 6052
Joined: 2003-09-10, 18:33 UTC

Post by *icfu »

jakubklos wrote:As always logs would help me. But I think this should be an ADB protocol issue. We will see
I don't have a log for the 0 bytes issue, sorry. My recent try to reproduce a 0 byte file has failed, but the file was truncated.

Code: Select all

2013-05-17 08:45:24 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:24 [1760] ADB Read:
2013-05-17 08:45:24 [1760] Connecting to ADB server...
2013-05-17 08:45:24 [1760] Connected
2013-05-17 08:45:24 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:24 [1760] ADB Read: OKAY
2013-05-17 08:45:24 [1760] ADB Write: sync:
2013-05-17 08:45:24 [1760] ADB Read: OKAY
2013-05-17 08:45:24 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:24 [1760] ADB Read: STAT
2013-05-17 08:45:24 [1760] ADB STAT: "/system/app/Launcher2.apk" does not exist!
2013-05-17 08:45:24 [1760] ADB Write: SEND   /system/app/Launcher2.apk,33206
2013-05-17 08:45:32 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:32 [1760] ADB Read: Read-only file system
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw /system
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw /system"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw /
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw /"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw rootfs
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw rootfs"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:32 [1760] ADB Read: STAT
2013-05-17 08:45:32 [1760] ADB STAT: "/system/app/Launcher2.apk" does not exist!
2013-05-17 08:45:32 [1760] ADB Write: SEND   /system/app/Launcher2.apk,33206
2013-05-17 08:45:40 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:40 [1760] ADB Read: Permission denied
2013-05-17 08:45:40 [1760] ADB Write: SEND   /mnt/sdcard/EB6905C8.tmp,33206
2013-05-17 08:45:49 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] Connecting to ADB server...
2013-05-17 08:45:49 [1760] Connected
2013-05-17 08:45:49 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Write: shell:busybox mv -f "/mnt/sdcard/EB6905C8.tmp" "/system/app/Launcher2.apk"
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Read Data: mv: can't create '/system/app/Launcher2.apk': Permission denied
2013-05-17 08:45:49 [1760] Connecting to ADB server...
2013-05-17 08:45:49 [1760] Connected
2013-05-17 08:45:49 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Write: shell:su -c "busybox mv -f "/mnt/sdcard/EB6905C8.tmp" "/system/app/Launcher2.apk""
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:59 [1760] ADB Read Data: mv: write error: No space left on device
2013-05-17 08:46:00 [12F8] Connecting to ADB server...
2013-05-17 08:46:00 [12F8] Connected
2013-05-17 08:46:00 [12F8] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:46:00 [12F8] ADB Read: OKAY
2013-05-17 08:46:00 [12F8] ADB Write: shell:busybox ls -lp -a -e --color=never "/system/app/"
2013-05-17 08:46:00 [12F8] ADB Read: OKAY
2013-05-17 08:46:00 [12F8] ADB Read Data: total 62739
This account is for sale
Top
jakubklos
Senior Member
Senior Member
Posts: 221
Joined: 2012-07-11, 14:48 UTC

Post by *jakubklos »

icfu wrote:
jakubklos wrote:As always logs would help me. But I think this should be an ADB protocol issue. We will see
I don't have a log for the 0 bytes issue, sorry. My recent try to reproduce a 0 byte file has failed, but the file was truncated.

Code: Select all

2013-05-17 08:45:24 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:24 [1760] ADB Read:
2013-05-17 08:45:24 [1760] Connecting to ADB server...
2013-05-17 08:45:24 [1760] Connected
2013-05-17 08:45:24 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:24 [1760] ADB Read: OKAY
2013-05-17 08:45:24 [1760] ADB Write: sync:
2013-05-17 08:45:24 [1760] ADB Read: OKAY
2013-05-17 08:45:24 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:24 [1760] ADB Read: STAT
2013-05-17 08:45:24 [1760] ADB STAT: "/system/app/Launcher2.apk" does not exist!
2013-05-17 08:45:24 [1760] ADB Write: SEND   /system/app/Launcher2.apk,33206
2013-05-17 08:45:32 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:32 [1760] ADB Read: Read-only file system
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw /system
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw /system"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw /
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw /"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:busybox mount -o remount,rw rootfs
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data: mount: permission denied (are you root?)
2013-05-17 08:45:32 [1760] Connecting to ADB server...
2013-05-17 08:45:32 [1760] Connected
2013-05-17 08:45:32 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Write: shell:su -c "busybox mount -o remount,rw rootfs"
2013-05-17 08:45:32 [1760] ADB Read: OKAY
2013-05-17 08:45:32 [1760] ADB Read Data:
2013-05-17 08:45:32 [1760] ADB Write: STAT   /system/app/Launcher2.apk
2013-05-17 08:45:32 [1760] ADB Read: STAT
2013-05-17 08:45:32 [1760] ADB STAT: "/system/app/Launcher2.apk" does not exist!
2013-05-17 08:45:32 [1760] ADB Write: SEND   /system/app/Launcher2.apk,33206
2013-05-17 08:45:40 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:40 [1760] ADB Read: Permission denied
2013-05-17 08:45:40 [1760] ADB Write: SEND   /mnt/sdcard/EB6905C8.tmp,33206
2013-05-17 08:45:49 [1760] ADB Write: DONEŒ¸ãP
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] Connecting to ADB server...
2013-05-17 08:45:49 [1760] Connected
2013-05-17 08:45:49 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Write: shell:busybox mv -f "/mnt/sdcard/EB6905C8.tmp" "/system/app/Launcher2.apk"
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Read Data: mv: can't create '/system/app/Launcher2.apk': Permission denied
2013-05-17 08:45:49 [1760] Connecting to ADB server...
2013-05-17 08:45:49 [1760] Connected
2013-05-17 08:45:49 [1760] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:49 [1760] ADB Write: shell:su -c "busybox mv -f "/mnt/sdcard/EB6905C8.tmp" "/system/app/Launcher2.apk""
2013-05-17 08:45:49 [1760] ADB Read: OKAY
2013-05-17 08:45:59 [1760] ADB Read Data: mv: write error: No space left on device
2013-05-17 08:46:00 [12F8] Connecting to ADB server...
2013-05-17 08:46:00 [12F8] Connected
2013-05-17 08:46:00 [12F8] ADB Write: host:transport:192.168.137.2:5555
2013-05-17 08:46:00 [12F8] ADB Read: OKAY
2013-05-17 08:46:00 [12F8] ADB Write: shell:busybox ls -lp -a -e --color=never "/system/app/"
2013-05-17 08:46:00 [12F8] ADB Read: OKAY
2013-05-17 08:46:00 [12F8] ADB Read Data: total 62739
Ok, got it. Will try to handle it
Top
walek75
New Member
New Member
Posts: 1
Joined: 2013-06-07, 11:57 UTC

Shell

Post by *walek75 »

Hi
It's possible to use mintty.exe {path to adb}\adb.exe shell instead plain adb on shell option ?
On my win 7 console from pure adb doesn't support terminal emulation control codes.
Top
jakubklos
Senior Member
Senior Member
Posts: 221
Joined: 2012-07-11, 14:48 UTC

Re: Shell

Post by *jakubklos »

walek75 wrote:Hi
It's possible to use mintty.exe {path to adb}\adb.exe shell instead plain adb on shell option ?
On my win 7 console from pure adb doesn't support terminal emulation control codes.
Hi,
I don't have any experience with mintty nor I am sure if it works well with ADB. If you think some option should be added in the config of the plugin let me know. But make sure mintty can work with device ids which means you simply start mintty with a device id param and it will connect to the correct ADB device (there can be multiple devices connected at a time)
Top
Aleq
Junior Member
Junior Member
Posts: 55
Joined: 2006-06-07, 07:24 UTC
Location: CZ, EU

Post by *Aleq »

Hello Jakub,
I have just noticed a problem with Nexus 10 TWRP recovery. Instead of files I see only ""file or directory (2) -"", I tried all "ls" variants without any luck.

The debug output:

Code: Select all

CONNECT \
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:ls -l "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:busybox ls -lp -a -e --color=never "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
By the way I check sh in terminal there:

Code: Select all

which sh
/sbin/sh
Thanks for looking, cheers,
Aleš
Top
jakubklos
Senior Member
Senior Member
Posts: 221
Joined: 2012-07-11, 14:48 UTC

Post by *jakubklos »

Aleq wrote:Hello Jakub,
I have just noticed a problem with Nexus 10 TWRP recovery. Instead of files I see only ""file or directory (2) -"", I tried all "ls" variants without any luck.

The debug output:

Code: Select all

CONNECT \
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:ls -l "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:busybox ls -lp -a -e --color=never "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
By the way I check sh in terminal there:

Code: Select all

which sh
/sbin/sh
Thanks for looking, cheers,
Aleš
Hi Ales,
it seems the TWRP recovery does not support the "-l" parameter. I will check and see what I can do about it
Top
jakubklos
Senior Member
Senior Member
Posts: 221
Joined: 2012-07-11, 14:48 UTC

Post by *jakubklos »

Aleq wrote:Hello Jakub,
I have just noticed a problem with Nexus 10 TWRP recovery. Instead of files I see only ""file or directory (2) -"", I tried all "ls" variants without any luck.

The debug output:

Code: Select all

CONNECT \
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:ls -l "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:devices
ADB Read: R32D102	recovery
Connecting to ADB server...
Connected
ADB Write: host:transport:R32D102
ADB Read: OKAY
ADB Write: shell:busybox ls -lp -a -e --color=never "/"
ADB Read: OKAY
ADB Read Data: - exec '/system/bin/sh' failed: No such file or directory (2) -
By the way I check sh in terminal there:

Code: Select all

which sh
/sbin/sh
Thanks for looking, cheers,
Aleš
Hi Ales,
what TWRP version do you have? It works for me fine.
I also have Nexus 10 with TWRP 2.3.2.3
ADB Write: host:transport:R32CA07N27P
ADB Read: OKAY
ADB Write: shell:busybox ls -lp -a -e --color=never "/"
ADB Read: OKAY
ADB Read Data: drwxr-xr-x 15 root root 0 Tue Jul 23 09:28:49 2013 ./
drwxr-xr-x 15 root root 0 Tue Jul 23 09:28:49 2013 ../
drwxrwx--x 5 system cache 4096 Sat Jul 20 04:30:50 2013 cache/
-rwxr-x--- 1 root root 244016 Thu Jan 1 00:00:00 1970 charger
drwxrwx--x 26 system system 4096 Thu Jul 11 08:59:15 2013 data/
-rw-r--r-- 1 root root 2532 Thu Jan 1 00:00:00 1970 default.prop
drwxr-xr-x 9 root root 2380 Tue Jul 23 09:28:48 2013 dev/
drwxr-xr-x 2 root root 0 Tue Jul 23 09:28:49 2013 etc/
-rw-r----- 1 root root 959 Thu Jan 1 00:00:00 1970 fstab.manta
-rw-r----- 1 root root 657 Thu Jan 1 00:00:00 1970 fstab.smdk5250
-rwxr-x--- 1 root root 105264 Thu Jan 1 00:00:00 1970 init
-rwxr-x--- 1 root root 1528 Thu Jan 1 00:00:00 1970 init.rc
dr-xr-xr-x 100 root root 0 Thu Jan 1 00:00:00 1970 proc/
drwxr-xr-x 4 root root 0 Thu Jan 1 00:00:00 1970 res/
drwx------ 2 root root 0 Thu Oct 18 21:44:59 2012 root/
drwxr-x--- 2 root root 0 Thu Jan 1 00:00:00 1970 sbin/
drwxrwx--- 42 media_rw media_rw 4096 Tue Jul 9 09:56:10 2013 sdcard/
dr-xr-xr-x 12 root root 0 Tue Jul 23 09:28:48 2013 sys/
drwxr-xr-x 3 root root 0 Thu Jan 1 00:00:00 1970 system/
drwxr-xr-x 2 root root 0 Tue Jul 23 09:28:51 2013 tmp/
-rw-r--r-- 1 root root 272 Thu Jan 1 00:00:00 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 6466 Thu Jan 1 00:00:00 1970 ueventd.manta.rc
-rw-r--r-- 1 root root 5075 Thu Jan 1 00:00:00 1970 ueventd.rc
-rw-r--r-- 1 root root 2107 Thu Jan 1 00:00:00 1970 ueventd.smdk5250.rc
drwxrwxrwx 2 root root 0 Tue Jul 23 09:28:49 2013 usb-otg/
Maybe there is a symlink to a non-existant file or something. The fact that your sh exists under /sbin/sh but busybox tries /system/bin/sh is weird.
How about you "adb shell" manually to the device and try some unix commands to fix the situation. Let us know

Jakub
Top
Aleq
Junior Member
Junior Member
Posts: 55
Joined: 2006-06-07, 07:24 UTC
Location: CZ, EU

Post by *Aleq »

Hi Jakub, it was TWRP 2.3-something (unfortunately I went to CWM now, but I'll go back and retest in future.
I remember "adb shell" failed (I opened it from start menu, command, so the console window just flashed and it was gone).

Maybe that recovery was broken, so we should not pay much attention to it. Somehow I have the feeling I used afterwards my (outdated) version of Sztupy's ADB plugin and it worked. Otherwise I use your plugin, which is better :wink:
Top
User avatar
sidefx88
Senior Member
Senior Member
Posts: 294
Joined: 2007-04-11, 17:07 UTC
Location: Argentina

Post by *sidefx88 »

Hi!

I'm having a little problem when capture the screen using ADB (i've tried several versions: 6.0, 6.7 and now 6.8 with same results).

It captures the screen, but the resulting PNG has the colors changed (i guess it is a palette offset). For example: the red icons looks purple, the orange icons looks light blue, my light blue wallpaper looks brown, and so on...

Any solution? Is it a bug?

Thanks!
I Love Total Commander!
Top
Post Reply

Return to “Plugins and addons: devel.+support (English)”