[DEVS][INFO]That /sbin folder... - Galaxy Ace II Android Development

Hello devs,
while I was digging into update-binaries (i found out also this little trick) I crashed into that /sbin/sh thing...
I searched over the net but couldn't find any reference to this folder and its contents, so I took the DIY route.
Well, here is the content of that /sbin at CWM5 (GB) Recovery time:
Code:
lrwxrwxrwx 1 root root 7 Jun 23 08:44 [ -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 [[ -> busybox
-rwxr-xr-x 1 root root 142656 Jun 23 08:44 adbd
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ash -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 awk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 basename -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bbconfig -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 blkid -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bunzip2 -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 busybox -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bzip2 -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cal -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 catv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chattr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chgrp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chown -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chroot -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cksum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 clear -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cmp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cpio -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cut -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 date -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dc -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dd -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 dedupe -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 depmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 devmem -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 df -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 diff -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dirname -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dmesg -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dos2unix -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 du -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 dump_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 echo -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 edify -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 egrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 env -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 erase_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 expand -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 expr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 false -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fdisk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fgrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 find -> busybox
-rwxr-xr-x 1 root root 14795 Jun 23 08:44 fix_permissions
lrwxrwxrwx 1 root root 8 Jun 23 08:44 flash_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fold -> busybox
-rwxr-xr-x 1 system system 10660 Aug 7 2012 fota.png
lrwxrwxrwx 1 root root 7 Jun 23 08:44 free -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 freeramdisk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fuser -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 getopt -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 grep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 groups -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 gunzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 gzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 head -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 hexdump -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 id -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 insmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 install -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 kill -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 killall -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 killall5 -> busybox
-rwxr-xr-x 1 root root 409 Jun 23 08:44 killrecovery.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 length -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 less -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ln -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 losetup -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ls -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsattr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lspci -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsusb -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzop -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzopcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 makedevs -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 md5sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkfifo -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkfs.ext2 -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mknod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkswap -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mktemp -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 mkyaffs2image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 modinfo -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 modprobe -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 more -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mount -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mountpoint -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nanddump -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 nandroid -> recovery
-rwxr-xr-x 1 root root 216 Jun 23 08:44 nandroid-md5.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nandwrite -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nice -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nohup -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 od -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 patch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pgrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pidof -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pkill -> busybox
-rwxr-xr-x 1 root root 11 Jun 23 08:44 postrecoveryboot.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 printenv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 printf -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ps -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pstree -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pwd -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rdev -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 readlink -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 realpath -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 reboot -> recovery
-rwxr-x--- 1 root root 789784 Jun 23 08:44 recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 renice -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 reset -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 resize -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rev -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rm -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rmdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rmmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 run-parts -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sed -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 seq -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setconsole -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 setprop -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setserial -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setsid -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sh -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha1sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha256sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha512sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sleep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sort -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 split -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 stat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 strings -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 stty -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 swapoff -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 swapon -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sync -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sysctl -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tac -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tail -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tar -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tee -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 test -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 time -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 top -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 touch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 true -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ttysize -> busybox
lrwxrwxrwx 1 system system 7 Feb 4 22:00 ueventd -> ../init
lrwxrwxrwx 1 root root 7 Jun 23 08:44 umount -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uname -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unexpand -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uniq -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unix2dos -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unlzma -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unlzop -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unxz -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 unyaffs -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uptime -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 usleep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uudecode -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uuencode -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 volume -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 watch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 wc -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 which -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 whoami -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 xargs -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 xzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 yes -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 zcat -> busybox
I can't confirm this busybox in /sbin exists in the stock recovery (it should), but anyway who doesn't have CWM these days?
Bye

Related

[Q] Pairing a Bluetooth mouse using adb (broken screen,can view screen but not touch)

Hi all,
I've posted a question in the Galaxy S2 forums but realise it's probably a more generic issue.
http://forum.xda-developers.com/showthread.php?p=17892549
I've broken my screen and it no longer responds to touch. I can view it using an MHL > HDMI adapter but without any touch input I can't get past the pattern unlock.
I was hoping to pair a bluetooth mouse using adb or somehow so I can then use the mouse to pattern unlock and generally use my phone.
If anyone thinks they might be able to help with advice or techniques, please let me know!
Many thanks!
I think you can send touch events via adb, dig roung Google and you should find out how.
Sorry, I never tried it but I'm pretty sure its possible.
Sent from my HTC Desire using XDA App
It turns out that it's possible but it's not documented at all from what I can see.
My main hurdle at the moment though is that I do not have debugging enabled in normal mode so even if I worked out the correct sequence, I wouldn't be able to push it to the phone in normal mode through adb...
Also, it seems my sqlite3 is missing?!
If your rom supports init.d scripts you could add a script that starts the adb server on startup from recovery.
Sent from my HTC Desire using XDA App
That's a grand idea. Yeah there is an init.d directory so seems fine.
I know adb start-server from the pc side, however there are a few folders etc with adb in them and I've not found which is the right one to kick of debug mode. Seeing as I can't actually see the screen it's hard to play with trial and error Any suggestions on that would be great.
Code:
/system/etc/init.d # find / | grep adb | while read in
> do
> echo "${in}: "
> ls -lrt $in
> done
/dev/android_adb_enable:
crw-rw---- 1 adb adb 10, 57 Sep 27 12:06 /dev/android_adb_enable
/dev/android_adb:
crw-rw---- 1 adb adb 10, 58 Sep 27 12:06 /dev/android_adb
/sys/devices/virtual/misc/android_adb:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/misc
-r--r--r-- 1 root root 4096 Sep 27 12:12 dev
/sys/devices/virtual/misc/android_adb/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/misc/android_adb/uevent
/sys/devices/virtual/misc/android_adb/dev:
-r--r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/dev
/sys/devices/virtual/misc/android_adb/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/subsystem -> ../../../../class/misc
/sys/devices/virtual/misc/android_adb/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/misc/android_adb/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/power/control
/sys/devices/virtual/misc/android_adb/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/power/wakeup
/sys/devices/virtual/misc/android_adb_enable:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/misc
-r--r--r-- 1 root root 4096 Sep 27 12:12 dev
/sys/devices/virtual/misc/android_adb_enable/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/misc/android_adb_enable/uevent
/sys/devices/virtual/misc/android_adb_enable/dev:
-r--r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/dev
/sys/devices/virtual/misc/android_adb_enable/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/subsystem -> ../../../../class/misc
/sys/devices/virtual/misc/android_adb_enable/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/misc/android_adb_enable/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/power/control
/sys/devices/virtual/misc/android_adb_enable/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/power/wakeup
/sys/devices/virtual/usb_composite/adb:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/usb_composite
-rw-r--r-- 1 root root 4096 Sep 27 12:12 enable
/sys/devices/virtual/usb_composite/adb/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/usb_composite/adb/uevent
/sys/devices/virtual/usb_composite/adb/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/subsystem -> ../../../../class/usb_composite
/sys/devices/virtual/usb_composite/adb/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/usb_composite/adb/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/power/control
/sys/devices/virtual/usb_composite/adb/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/power/wakeup
/sys/devices/virtual/usb_composite/adb/enable:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/enable
/sys/class/misc/android_adb:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/misc/android_adb -> ../../devices/virtual/misc/android_adb
/sys/class/misc/android_adb_enable:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/misc/android_adb_enable -> ../../devices/virtual/misc/android_adb_enable
/sys/class/usb_composite/adb:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/usb_composite/adb -> ../../devices/virtual/usb_composite/adb
/sbin/adbd:
-rwxr-xr-x 1 system graphics 118004 Jul 11 05:25 /sbin/adbd
Think I've found it in /sbin/adbd ...

weird characters with ADB command: adb shell ls -la /

hello, I need some assistance regarding a strange characters when using ADB commands from MSDOS window.
In my tablet that is running Android ICS 4.0.4, and is rooted, I replaced most of the commands that TOOLBOX was assign to issue in /system/bin. I replaced them with BUSYBOX commands, and everything works fine from the standpoint of the tablet.
But somehow I started to get some weird characters when using the LS command in ADB shell from a PC. so it happened right away after the replacement.
So I did a listing of the root files and folders in the tablet form my PC with the command:
adb shell ls -la /
and this is what I got:
C:\Windows\system32>adb shell ls -la /
total 285
drwxr-xr-x 16 root root 0 Sep 12 11:59 ←[1;34m.←[0m
drwxr-xr-x 16 root root 0 Sep 12 11:59 ←[1;34m..←[0m
drwxr-xr-x 3 root root 0 Sep 12 11:59 ←[1;34macct←[0m
drwxrwx--- 4 system cache 4096 Sep 12 13:01 ←[1;34mcache←[0m
dr-x------ 2 root root 0 Sep 12 11:59 ←[1;34mconfig←[0m
lrwxrwxrwx 1 root root 17 Sep 12 11:59 ←[1;36md←[0m -> ←[1;34m/sys/kernel/debug←[0m
drwxrwx--x 25 system system 4096 Sep 6 23:22 ←[1;34mdata←[0m
-rw-r--r-- 1 root root 89 Dec 31 1969 ←[0;0mdefault.prop←[0m
drwxr-xr-x 12 root root 14240 Sep 12 12:09 ←[1;34mdev←[0m
lrwxrwxrwx 1 root root 11 Sep 12 11:59 ←[1;36metc←[0m -> ←[1;34m/system/etc←[0m
drwxrwxrwx 3 root root 16384 Dec 31 1969 ←[1;34mfirmware←[0m
-rwxr-x--- 1 root root 98736 Dec 31 1969 ←[1;32minit←[0m
-rwxr-x--- 1 root root 2344 Dec 31 1969 ←[1;32minit.goldfish.rc←[0m
-rwxr-x--- 1 root root 15813 Dec 31 1969 ←[1;32minit.qcom.rc←[0m
-rwxr-x--- 1 root root 11014 Dec 31 1969 ←[1;32minit.qcom.sh←[0m
-rwxr-x--- 1 root root 30858 Dec 31 1969 ←[1;32minit.qcom.usb.rc←[0m
-rwxr-x--- 1 root root 8786 Dec 31 1969 ←[1;32minit.qcom.usb.sh←[0m
-rwxr-x--- 1 root root 19420 Dec 31 1969 ←[1;32minit.rc←[0m
-rwxr-x--- 1 root root 3491 Dec 31 1969 ←[1;32minit.target.rc←[0m
-rwxr-x--- 1 root root 12760 Dec 31 1969 ←[1;32minitlogo.rle←[0m
drwxrwxr-x 6 root system 0 Sep 12 11:59 ←[1;34mmnt←[0m
drwxrwx--x 4 system system 1024 Jul 19 22:25 ←[1;34mpersist←[0m
dr-xr-xr-x 900 root root 0 Dec 31 1969 ←[1;34mproc←[0m
drwx------ 2 root root 0 Jun 27 05:47 ←[1;34mroot←[0m
drwxr-x--- 2 root root 0 Dec 31 1969 ←[1;34msbin←[0m
lrwxrwxrwx 1 root root 11 Sep 12 11:59 ←[1;36msdcard←[0m -> ←[1;34m/mnt/sdcard←[0m
drwxr-xr-x 12 root root 0 Sep 12 11:59 ←[1;34msys←[0m
drwxr-xr-x 14 root root 4096 Sep 6 23:20 ←[1;34msystem←[0m
drwxr-xr-x 5 root root 4096 Jul 19 22:25 ←[1;34mtombstones←[0m
-rw-r--r-- 1 root root 272 Dec 31 1969 ←[0;0mueventd.goldfish.rc←[0m
-rw-r--r-- 1 root root 8338 Dec 31 1969 ←[0;0mueventd.rc←[0m
lrwxrwxrwx 1 root root 14 Sep 12 11:59 ←[1;36mvendor←[0m -> ←[1;34m/system/vendor←[0m
But from the tablet when I issue the command ls -la / i get the normal listing but in shows in COLOR, so I''m guessing that <-[1;36m in ADB represents a color ([0,0m for white, [1;34m for dark blue, etc), but how do I go to show color listing in ADB shell in my PC ?
Before when TOOLBOX was handing the LS command there was not color in the listing, but now with BUSYBOX handling the LS command I get nice different colors for files/folders/scripts, etc.
Any way I can fix this from the standpoint of the Widows PC MSDOS window with ADB shell listing files with LS in also in color ???
much appreciated, regards.
UPDATE:
I found out that I can list with ADB shell without those strange characters (in other words with NO COLOR) with the following command:
adb shell ls -la --color=never /
but it would be nice not to have to type --color=never every time I want a listing and better find a way to list it with color from PC in MSDOS window.
you can use a utility like ansicon, which allows msdos command windows to interpret the colour codes. You could add this to windows startup if you want, or use some replacement command line utility that can automatically run an app on startup.
flshg said:
you can use a utility like ansicon, which allows msdos command windows to interpret the colour codes. You could add this to windows startup if you want, or use some replacement command line utility that can automatically run an app on startup.
Click to expand...
Click to collapse
thanks a bunch, it worked just great!

Could someone please type something in to terminal and send me the result

Hi all,
i am trying to make a dual boot kernel for the Galaxy note 2, using the siyah kernel source code.
I have to change the partition layout in his ramfs, but i need the Galaxy s3 partition layout so i can figure out what i need to change it to.
Would someone please be able to:
open a terminal on your rooted phone,
Type: "ls -l /dev/block/platform/dw_mmc/by-name" in to the terminal
And then copy and paste the Result you get from that to this post.
If someone could please do that, i would be very greatful
Thanks
Cheers
Corey
Anyone??
Cheers
Corey
Here you go:
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Dec 15 21:15 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Dec 15 21:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Dec 15 21:15 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 15 21:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Dec 15 21:15 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 15 21:15 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 15 21:15 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Dec 15 21:15 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 15 21:15 USERDATA -> /dev/block/mmcblk0p12
Verzonden door mijn GT-I9300 met xda premium
coolhof said:
Here you go:
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Dec 15 21:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Dec 15 21:15 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Dec 15 21:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Dec 15 21:15 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 15 21:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Dec 15 21:15 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 15 21:15 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 15 21:15 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Dec 15 21:15 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 15 21:15 USERDATA -> /dev/block/mmcblk0p12
Verzonden door mijn GT-I9300 met xda premium
Click to expand...
Click to collapse
Thanks heaps, that's just what I needed.
Thanks again
Cheers
Corey
Sent from my GT-N7100 using Tapatalk 2

TZ/RPM ?

saw some rom require TZ/RPM? what are they ?
optimusv45 said:
saw some rom require TZ/RPM? what are they ?
Click to expand...
Click to collapse
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
adfurgerson said:
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
Click to expand...
Click to collapse
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
All of the current Roms require it, the earliest cfx and possibly cm10.1 could run without it. I wouldn't recommend those as daily drivers compared to what's availible now.
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for catching my mistake @Shelnutt2. So I am clear, those can be flashed because they use LG based kernel? Also if you are saying you could make a zip to update partitions, that would be an awesome thing to have.
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Flashable zip would be awesome. I looked at the lgnpst thing a bit , it reminds me of RUU for my HTC phone. If I could I would rather not go back to 100 % stock and do everything all over again.
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
optimusv45 said:
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2411406
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
shelnutt2, can you put up a flashable zip for the TZ/RPM update ? i hope to have the capability to use all the available roms without having to learn lgnpst and teenybin. thanks.
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
A flash able zip would be awesome, I'm not sure if it would help me or not but I believe my rpm/tz partitions are messed up
Sent from my LG Optimus G using Tapatalk 4
anyone with internet can help ?...
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
pcexpress said:
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I understand there is teenybin. Flashable zip is just an easy way for people like me who don't want to learn LGNPST
adfurgerson said:
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
Click to expand...
Click to collapse
I'd be glad to, my adb is my best friend when I keep recompiling and breaking roms, what comands give an md5 of the actual partitions?
or just an md5 of the contents? I'll screw around rq and edit this if it's a no brainer.
random results, if this counts:
Code:
/dev/block/platform/msm_sdcc.1/by-name # ll
ll
drwxr-xr-x 2 root root 740 Sep 15 09:35 ./
drwxr-xr-x 4 root root 800 Sep 15 09:35 ../
lrwxrwxrwx 1 root root 21 Sep 15 09:35 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 Sep 15 09:35 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Sep 15 09:35 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Sep 15 09:35 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Sep 15 09:35 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Sep 15 09:35 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Sep 15 09:35 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Sep 15 09:35 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Sep 15 09:35 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Sep 15 09:35 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Sep 15 09:35 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Sep 15 09:35 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 Sep 15 09:35 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Sep 15 09:35 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Sep 15 09:35 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Sep 15 09:35 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 20 Sep 15 09:35 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Sep 15 09:35 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Sep 15 09:35 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Sep 15 09:35 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Sep 15 09:35 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 Sep 15 09:35 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Sep 15 09:35 userdata -> /dev/block/mmcblk0p24
/dev/block/platform/msm_sdcc.1/by-name # cd rpm
cd rpm
/sbin/sh: cd: can't cd to rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum rpm
md5sum rpm
b1fa2c29e99349abb7104ea87ee9c0e1 rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum tz
md5sum tz
9913d95fb8bc67e2942bcd491fd07af3 tz
/dev/block/platform/msm_sdcc.1/by-name #
And just to be sure, cat > both to a file for sanity sake and md5 on windows, same results.
Code:
C:\android\md5sums-1.2>md5sums rpm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
rpm.img b1fa2c29e99349abb7104ea87ee9c0e1
C:\android\md5sums-1.2>md5sums tz.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
tz.img 9913d95fb8bc67e2942bcd491fd07af3
C:\android\md5sums-1.2>
files attached:
View attachment rpm.img
View attachment tz.img
In case some of you hadn't noticed, this is a Q&A, Help and Troubleshooting thread...
If you've got nothing constructive to contribute, I suggest you move along and troll somewhere else.
bump
optimusv45 said:
bump
Click to expand...
Click to collapse
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
adfurgerson said:
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
Click to expand...
Click to collapse
4.4 lured me into updating using teenybins. you were right, its not bad

[HELP] Unable to execute the ./simg2img binary

Hello.
I am using a Virtualbox with Ubuntu 16.04 as guest and Windows 10 as host.
I have also got the guest additions installed in Ubuntu. But the problem is that whenever i try to run the command "sudo ./simg2img system.img sys.raw" i get an error stating "sudo: unable to execute ./simg2img: No such file or directory"
I also have the simg2img binary in the same directory as my system.img sparse image is in and i have also given the binary executable permissions by typing this command and i was successful.Here is the output of the ls -l command of the directory in which the simg2img binary is in:-
Code:
[email protected]:/media/base$ sudo chmod +x simg2img
[email protected]:/media/base$ sudo ./simg2img system.img sys.raw
sudo: unable to execute ./simg2img: No such file or directory
[email protected]:/media/base$ ls -l
total 2712719
-rwxrwxrwx 1 root root 374272 Apr 23 2015 AndImgTool.exe
drwxrwxrwx 1 root root 8192 Sep 15 18:37 android-simg2img-master
-rwxrwxrwx 1 root root 137008 Dec 14 2015 APDB_MT6735_S01_L1.MP3_W15.47
-rwxrwxrwx 1 root root 3593 Sep 15 17:39 append2simg.c
-rwxrwxrwx 1 root root 9119 Sep 15 17:39 backed_block.c
-rwxrwxrwx 1 root root 2498 Sep 15 17:39 backed_block.h
drwxrwxrwx 1 root root 0 Sep 14 16:25 Binaries
drwxrwxrwx 1 root root 0 Sep 12 23:38 boot
-rwxrwxrwx 1 root root 7696384 Dec 14 2015 boot.img
-rwxrwxrwx 1 root root 8238962 Dec 14 2015 BPLGUInfoCustomAppSrcP_MT6735_S00_MOLY_LR9_W1444_MD_LWTG_MP_V26_P23_1_lwg_n
-rwxrwxrwx 1 root root 8388912 Dec 14 2015 cache.img
-rwxrwxrwx 1 root root 758 Sep 15 17:39 defs.h
-rwxrwxrwx 1 root root 4307 Sep 15 17:39 ext4_utils.h
-rwxrwxrwx 1 root root 31711 Sep 12 23:38 file_contexts
-rwxrwxrwx 1 root root 5485902 Sep 13 18:14 img2sdat.exe
-rwxrwxrwx 1 root root 862 Sep 13 18:21 img2sdat.pyc
-rwxrwxrwx 1 root root 284028 Sep 13 18:20 img2simg
-rwxrwxrwx 1 root root 2488 Sep 15 17:39 img2simg.c
drwxrwxrwx 1 root root 0 Sep 15 17:39 include
-rwxrwxrwx 1 root root 296420 Dec 14 2015 lk.bin
-rwxrwxrwx 1 root root 1647621 Dec 14 2015 logo.bin
-rwxrwxrwx 1 root root 514152 Sep 12 22:38 make_ext4fs
-rwxrwxrwx 1 root root 1775 Sep 15 17:39 Makefile
drwxrwxrwx 1 root root 0 Sep 12 23:25 META-INF
-rwxrwxrwx 1 root root 9373 Dec 14 2015 MT6753_Android_scatter.txt
drwxrwxrwx 1 root root 0 Sep 14 23:14 output
-rwxrwxrwx 1 root root 16994 Sep 15 17:39 output_file.c
-rwxrwxrwx 1 root root 1560 Sep 15 17:39 output_file.h
-rwxrwxrwx 1 root root 151192 Dec 14 2015 preloader_l5460.bin
-rwxrwxrwx 1 root root 780 Sep 12 22:43 README.md
-rwxrwxrwx 1 root root 8888320 Dec 14 2015 recovery.img
-rwxrwxrwx 1 root root 10392 Sep 12 22:39 rimg2sdat
-rwxrwxrwx 1 root root 3881 Sep 12 22:43 sdat2img.py
-rwxrwxrwx 1 root root 135168 Dec 14 2015 secro.img
-rwxrwxrwx 1 root root 278374 Sep 14 15:56 simg2img
-rwxrwxrwx 1 root root 1947 Sep 15 17:39 simg2img.c
-rwxrwxrwx 1 root root 2634 Sep 15 17:39 simg2simg.c
-rwxrwxrwx 1 root root 5212 Sep 15 17:39 simg_dump.py
-rwxrwxrwx 1 root root 8383 Sep 15 17:39 sparse.c
-rwxrwxrwx 1 root root 6038 Sep 15 17:39 sparse_crc32.c
-rwxrwxrwx 1 root root 857 Sep 15 17:39 sparse_crc32.h
-rwxrwxrwx 1 root root 1391 Sep 15 17:39 sparse_defs.h
-rwxrwxrwx 1 root root 997 Sep 15 17:39 sparse_err.c
-rwxrwxrwx 1 root root 916 Sep 15 17:39 sparse_file.h
-rwxrwxrwx 1 root root 2219 Sep 15 17:39 sparse_format.h
-rwxrwxrwx 1 root root 11352 Sep 15 17:39 sparse_read.c
drwxrwxrwx 1 root root 0 Sep 13 18:36 system_
-rwxrwxrwx 1 root root 2707273812 Dec 14 2015 system.img
-rwxrwxrwx 1 root root 60928 Dec 14 2015 trustzone.bin
-rwxrwxrwx 1 root root 27812432 Dec 14 2015 userdata.img
So can anyone please help me with this.I want to extract the system/ folder from the sparse sysem image but i am unable to do so in windows after having followed all the instructions carefully.
Many many thanks in advance.
You're trying to run 32-bit binary on a 64-bit system.
Follow this guide to solve ur problem :
http://askubuntu.com/questions/133389/no-such-file-or-directory-but-the-file-exists

Categories

Resources