alternative way to get script.bin without android apps

[aus9]

Try at own risk

This is an alternative method of getting your script.bin without the slowness of downloading dropbear in android YMMV
AND
not having to tweak any firewall you may set up to disable any ssh etc

in TC, ensure you have a usb stick that is formatted a certain way
that is know what format it is eg ext2/3/4 etc

If you delay some commands you may lose the adb connection so just
run adb shell again

tc@box:~$ tce-load -i android

cable connect to OTG port on allwinner A10, usb male into TC

tc@box:~$ adb devices (result for me)

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
20080411   device

tc@box:~$ adb shell
root@android:/ # mkdir /mnt/1 /mnt/2
root@android:/ # mount -t vfat /dev/block/nanda /mnt/1
root@android:/ # ls -l /mnt/1

boot.axf
boot.ini
drv_de.drv
font24.sft
font32.sft
linux
magic.bin
os_show
script.bin
script0.bin
sprite
sprite.axf
vendor

I will grab the lot to look at and insert usb device into android spare usb port

root@android:/ #  mount -t ext3 /dev/block/sda1 /mnt/2
root@android:/ # cp /mnt/1/* /mnt/2 (I ignored the loss of the folder copying)

root@android:/ # md5sum /mnt/1/script.bin > /mnt/2/md5.txt
root@android:/ # cat /mnt/2/md5.txt                                             
daae85bcb6885240d6fdb1553b411fc5  /mnt/1/script.bin
root@android:/mnt/2 # md5sum /mnt/2/script.bin                                       
daae85bcb6885240d6fdb1553b411fc5  script.bin

root@android:/ # umount /mnt/1
root@android:/ # umount /mnt/2
root@android:/ # exit

drops you out of android shell.

insert usb stick back into TC and check what its new dev is

$ ls -al /dev/disk/by-path/

total 0
drwxr-xr-x 2 root root 180 Nov 23 12:47 ./
drwxr-xr-x 6 root root 120 Nov 23 12:22 ../
lrwxrwxrwx 1 root root   9 Nov 23 12:22 pci-0000:00:1d.7-usb-0:7.4:1.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root   9 Nov 23 12:47 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root  10 Nov 23 12:47 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root   9 Nov 23 12:22 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root   9 Nov 23 12:22 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  10 Nov 23 12:22 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 Nov 23 12:22 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2

I already know sda(s) are my internal
sr0 is my optical drive
sdb has no partition as its device is now removed
so sdc1 is my target

$ mkdir android  /tmp/android
$ sudo mount /dev/sdc1 /tmp/android
$ cp /mnt/android/* android
$ sudo umount /tmp/android

And that gives me my script.bin and other stuff to view in mc

good luck

EDIT I forgot to add a md5 check against your script.bin so that after you have copied it onto an usb stick you can prove that after the usb light stops flashing.....you have successfully copied the file across to stick

[vinnie]

Thank you, I'm not a person directly concerned (I do not have the allwinner10) but I found some useful stuff!

[aus9]

ok so first post has been amended to add a md5sum check for grabbing your script.bin

Next after you do a dd image find and mount your microsd/SD card to some folder
eg

Code: [Select]

mkdir /tmp/a
sudo mount /dev/sdb1 /tmp/a
cp -f /pathway2/script.bin tmp/a

md5sum /tmp/a/script.bin
daae85bcb6885240d6fdb1553b411fc5  /tmp/a/script.bin
tc@box:~/android$ cat md5.txt
daae85bcb6885240d6fdb1553b411fc5  /mnt/1/script.bin
 
change your pathways to where ever you saved your script.bin

good luck