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 ...
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!
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
Hey,
my phone was upgraded to wrong region:
-I lost services.
-Can't install another firmware, getting oemsbl error.
After many things I'w tried, I'm ready to clean everything if it helps me to install update.app(original firmware)
Not sure about system and boot partitions.
I know deleting system, will delete my android system, leaving it bootable. But what about IMEI/SN? Is there something like ESF folder there?
Deleting boot, gonna leave me without boot (anyways if I won't reboot I think I can use ADB push then) but, does boot contains my bootloader info? (bootloader unlocked)
So my resources:
-Wrong region firmware installed;
-bootloader unlocked;
-Cwm/original(curent ROM) recoveries;
-update.app for my region, wich is older then that is installed in my phone right now (I can extract system.img boot.img)
-update.app the same is installed & very old nandroid backup from the oldest version of wrong region
-ADB sideload, cygwin on pc, terminal on phone etc. etc.......
& the screenshot maybe useful,
I can dd if=/dev/block//// of=mnt/sdcard2/file.img
or use adb or whatever leads to the right direction
up
up up up;
Come on, I need an expert consultations
dafas said:
up up up;
Come on, I need an expert consultations
Click to expand...
Click to collapse
Maybe you can try dd from adb your modem.img from update.APP to modem partition? Backup it before -also dd to sdcard.
mparus said:
Maybe you can try dd from adb your modem.img from update.APP to modem partition? Backup it before -also dd to sdcard.
Click to expand...
Click to collapse
hey,
Already tried something like that. But I can extract only system, boot, files from update.app only, the other ones left unknown. I also can get part of the cust
or maybe u mean push system img 1st, then use dd if=..of=..to get modem.img I think this could be possible if system contains modem files
dafas said:
hey,
Already tried something like that. But I can extract only system, boot, files from update.app only, the other ones left unknown. I also can get part of the cust
Click to expand...
Click to collapse
you can try check and find file modem from linux, maybe looks like this: (example from huawei g7)
file MODEM.img
MODEM.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", sectors/cluster 32, root entries 512, Media descriptor 0xf8, sectors/FAT 25, sectors/track 63, heads 255, sectors 196608 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
you can also mount this file:
mount -t vfat MODEM.img -o loop example_folder_mount
it contains files like this:
drwxr-xr-x 2 root root 16384 Jul 5 2011 image
example_folder_mount/image:
total 47072
drwxr-xr-x 2 root root 16384 Jul 5 2011 .
drwxr-xr-x 3 root root 16384 Jan 1 1970 ..
-rwxr-xr-x 1 root root 180 Nov 2 21:44 cmnlib.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 cmnlib.b01
-rwxr-xr-x 1 root root 110020 Nov 2 21:44 cmnlib.b02
-rwxr-xr-x 1 root root 4456 Nov 2 21:44 cmnlib.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 cmnlib.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 isdbtmm.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 isdbtmm.b01
-rwxr-xr-x 1 root root 39596 Nov 2 21:44 isdbtmm.b02
-rwxr-xr-x 1 root root 112 Nov 2 21:44 isdbtmm.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 isdbtmm.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 keymaste.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 keymaste.b01
-rwxr-xr-x 1 root root 17816 Nov 2 21:44 keymaste.b02
-rwxr-xr-x 1 root root 208 Nov 2 21:44 keymaste.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 keymaste.mdt
-rwxr-xr-x 1 root root 234240 Nov 2 21:37 mba.mbn
-rwxr-xr-x 1 root root 916 Nov 2 21:44 modem.b00
-rwxr-xr-x 1 root root 7304 Nov 2 21:44 modem.b01
-rwxr-xr-x 1 root root 4212 Nov 2 21:44 modem.b02
-rwxr-xr-x 1 root root 5376 Nov 2 21:44 modem.b03
-rwxr-xr-x 1 root root 139616 Nov 2 21:44 modem.b04
-rwxr-xr-x 1 root root 81920 Nov 2 21:44 modem.b05
-rwxr-xr-x 1 root root 172096 Nov 2 21:44 modem.b08
-rwxr-xr-x 1 root root 48704 Nov 2 21:44 modem.b10
-rwxr-xr-x 1 root root 46424 Nov 2 21:44 modem.b11
-rwxr-xr-x 1 root root 99524 Nov 2 21:44 modem.b13
-rwxr-xr-x 1 root root 115348 Nov 2 21:44 modem.b14
-rwxr-xr-x 1 root root 1660568 Nov 2 21:44 modem.b15
-rwxr-xr-x 1 root root 19436496 Nov 2 21:44 modem.b16
-rwxr-xr-x 1 root root 663520 Nov 2 21:44 modem.b17
-rwxr-xr-x 1 root root 7671376 Nov 2 21:44 modem.b18
-rwxr-xr-x 1 root root 3503784 Nov 2 21:44 modem.b19
-rwxr-xr-x 1 root root 76216 Nov 2 21:44 modem.b22
-rwxr-xr-x 1 root root 502429 Nov 2 21:44 modem.b23
-rwxr-xr-x 1 root root 8063672 Nov 2 21:44 modem.b24
-rwxr-xr-x 1 root root 385684 Nov 2 21:44 modem.b25
-rwxr-xr-x 1 root root 8220 Nov 2 21:44 modem.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 playread.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 playread.b01
-rwxr-xr-x 1 root root 121664 Nov 2 21:44 playread.b02
-rwxr-xr-x 1 root root 416 Nov 2 21:44 playread.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 playread.mdt
-rwxr-xr-x 1 root root 436 Nov 2 21:44 wcnss.b00
-rwxr-xr-x 1 root root 6824 Nov 2 21:44 wcnss.b01
-rwxr-xr-x 1 root root 13052 Nov 2 21:44 wcnss.b02
-rwxr-xr-x 1 root root 61440 Nov 2 21:44 wcnss.b04
-rwxr-xr-x 1 root root 3375740 Nov 2 21:44 wcnss.b06
-rwxr-xr-x 1 root root 52 Nov 2 21:44 wcnss.b09
-rwxr-xr-x 1 root root 655360 Nov 2 21:44 wcnss.b10
-rwxr-xr-x 1 root root 39864 Nov 2 21:44 wcnss.b11
-rwxr-xr-x 1 root root 7260 Nov 2 21:44 wcnss.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 widevine.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 widevine.b01
-rwxr-xr-x 1 root root 134420 Nov 2 21:44 widevine.b02
-rwxr-xr-x 1 root root 780 Nov 2 21:44 widevine.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 widevine.mdt
mparus said:
you can try check and find file modem from linux, maybe looks like this: (example from huawei g7)
file MODEM.img
MODEM.img: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", sectors/cluster 32, root entries 512, Media descriptor 0xf8, sectors/FAT 25, sectors/track 63, heads 255, sectors 196608 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
you can also mount this file:
mount -t vfat MODEM.img -o loop example_folder_mount
it contains files like this:
drwxr-xr-x 2 root root 16384 Jul 5 2011 image
example_folder_mount/image:
total 47072
drwxr-xr-x 2 root root 16384 Jul 5 2011 .
drwxr-xr-x 3 root root 16384 Jan 1 1970 ..
-rwxr-xr-x 1 root root 180 Nov 2 21:44 cmnlib.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 cmnlib.b01
-rwxr-xr-x 1 root root 110020 Nov 2 21:44 cmnlib.b02
-rwxr-xr-x 1 root root 4456 Nov 2 21:44 cmnlib.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 cmnlib.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 isdbtmm.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 isdbtmm.b01
-rwxr-xr-x 1 root root 39596 Nov 2 21:44 isdbtmm.b02
-rwxr-xr-x 1 root root 112 Nov 2 21:44 isdbtmm.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 isdbtmm.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 keymaste.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 keymaste.b01
-rwxr-xr-x 1 root root 17816 Nov 2 21:44 keymaste.b02
-rwxr-xr-x 1 root root 208 Nov 2 21:44 keymaste.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 keymaste.mdt
-rwxr-xr-x 1 root root 234240 Nov 2 21:37 mba.mbn
-rwxr-xr-x 1 root root 916 Nov 2 21:44 modem.b00
-rwxr-xr-x 1 root root 7304 Nov 2 21:44 modem.b01
-rwxr-xr-x 1 root root 4212 Nov 2 21:44 modem.b02
-rwxr-xr-x 1 root root 5376 Nov 2 21:44 modem.b03
-rwxr-xr-x 1 root root 139616 Nov 2 21:44 modem.b04
-rwxr-xr-x 1 root root 81920 Nov 2 21:44 modem.b05
-rwxr-xr-x 1 root root 172096 Nov 2 21:44 modem.b08
-rwxr-xr-x 1 root root 48704 Nov 2 21:44 modem.b10
-rwxr-xr-x 1 root root 46424 Nov 2 21:44 modem.b11
-rwxr-xr-x 1 root root 99524 Nov 2 21:44 modem.b13
-rwxr-xr-x 1 root root 115348 Nov 2 21:44 modem.b14
-rwxr-xr-x 1 root root 1660568 Nov 2 21:44 modem.b15
-rwxr-xr-x 1 root root 19436496 Nov 2 21:44 modem.b16
-rwxr-xr-x 1 root root 663520 Nov 2 21:44 modem.b17
-rwxr-xr-x 1 root root 7671376 Nov 2 21:44 modem.b18
-rwxr-xr-x 1 root root 3503784 Nov 2 21:44 modem.b19
-rwxr-xr-x 1 root root 76216 Nov 2 21:44 modem.b22
-rwxr-xr-x 1 root root 502429 Nov 2 21:44 modem.b23
-rwxr-xr-x 1 root root 8063672 Nov 2 21:44 modem.b24
-rwxr-xr-x 1 root root 385684 Nov 2 21:44 modem.b25
-rwxr-xr-x 1 root root 8220 Nov 2 21:44 modem.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 playread.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 playread.b01
-rwxr-xr-x 1 root root 121664 Nov 2 21:44 playread.b02
-rwxr-xr-x 1 root root 416 Nov 2 21:44 playread.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 playread.mdt
-rwxr-xr-x 1 root root 436 Nov 2 21:44 wcnss.b00
-rwxr-xr-x 1 root root 6824 Nov 2 21:44 wcnss.b01
-rwxr-xr-x 1 root root 13052 Nov 2 21:44 wcnss.b02
-rwxr-xr-x 1 root root 61440 Nov 2 21:44 wcnss.b04
-rwxr-xr-x 1 root root 3375740 Nov 2 21:44 wcnss.b06
-rwxr-xr-x 1 root root 52 Nov 2 21:44 wcnss.b09
-rwxr-xr-x 1 root root 655360 Nov 2 21:44 wcnss.b10
-rwxr-xr-x 1 root root 39864 Nov 2 21:44 wcnss.b11
-rwxr-xr-x 1 root root 7260 Nov 2 21:44 wcnss.mdt
-rwxr-xr-x 1 root root 180 Nov 2 21:44 widevine.b00
-rwxr-xr-x 1 root root 6568 Nov 2 21:44 widevine.b01
-rwxr-xr-x 1 root root 134420 Nov 2 21:44 widevine.b02
-rwxr-xr-x 1 root root 780 Nov 2 21:44 widevine.b03
-rwxr-xr-x 1 root root 6748 Nov 2 21:44 widevine.mdt
Click to expand...
Click to collapse
Thank You, gonna work on that
so far
Hey, happy holidays
So, MODEM.img from my device:
-mounted on linux & I can see those files;
Next,
(?) push modem.img from update.app to my device???
*Is it possible (anyhow, anyway) to mount update.app?
Or I got something wrong?
If yes, sorry for nooby, more details, please
Thanx
I'm trying to flash lineageOS on my Moto Z/XT1650 however it aborts with 'E2001: Failed to update vendor image.' and leaves the system in an unbootable state (which i have then to fix by restoring the stock image from backups) After having a closer look the error seems to originate from the updater script when it tries to patch the vendor/oem partition (/dev/block/bootdevice/by-name/oem or /dev/block/sdc9) because the partition is readonly.
Code:
block_image_update("/dev/block/bootdevice/by-name/oem", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
I also failed to mount the partition rw via adb shell.
Code:
~ # mount -w /dev/block/sdc9 /oem
~ # ls -al /oem
drwxr-xr-x 6 root root 4096 Jan 1 1970 .
drwxrwxrwt 31 root root 1040 Jul 26 09:25 ..
drwxr-xr-x 6 root root 4096 Sep 25 2018 app
drwxr-xr-x 6 root root 4096 Sep 25 2018 etc
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 146 Sep 25 2018 oem.prop
drwxr-xr-x 4 root root 4096 Sep 25 2018 priv-app
~ # touch /oem/test
touch: /oem/test: Read-only file system
How do i make the partition rw so that twrp/lineage installer can patch it?
Never mind, i found the solution: Booting directly into twrp causes these issues. Flash the twrp/recovery image and boot into recovery mode instead