This is a post in progress, this post will be updated with my install experience and notes for getting BT5 working on the Advent Vega
errr no idea wtf happened, my whole post got NUKED! 31/05/2011 ~ 21:00 BST, In short nothing I have yet tried has worked so I am looking at shrinking the image <= 4GB to fit on a fat32 /sdcard/ (could not get a single rom to accept none fat32)
Using your favorite linux distro uncompress and mount the image file
gunzip bt5.img.gz
mkdir /mnt/bt5 && mount -o loop bt5.img /mnt/bt5
You will notice there is a fair amount of free space in the img file,
Code:
/home/oneiroi/bt5/bt5.img
4.9G 2.6G 2.0G 57% /mnt/bt5
So we have 43% free space causing the image to be > 4GB
Create a new 4GB img file
Yeh this is a lazy image atm it crates a 3.7GB IMG I may re-visit this later to get as near 4GB as much as poss.
Code:
dd if=/dev/zero of=./bt5_new.img seek=4000999999 bs=1 count=1
mount the new image and mkfs
setup a loop devices on loop1 (loop0 will be used by the bt5.img, you can check if you don't believe me! this is a ext2 filesystem, check using parted if you like)
(
I have removed this but if you want you can
losetup /dev/loop1
mkfs.ext2 /dev/loop1
mount /dev/loop1 /mnt/bt5_new
)
Code:
mke2fs -F bt5_new.img
mkdir /mnt/bt5_new && mount -o loop bt5_new.img /mnt/bt5_new
Use rsync to copy everything with the right user/groups and permissions
Code:
rsync -gioprtuv /mnt/bt5/* /mnt/bt5_new/
and go grab a beer this will take a while, add --progress if you like (267097 files based on what I am running now 31/05/2011 ~21:28)
Follow the instructions in the README file, with one difference copy bt5_new.img to /sdcard/BT5/bt5.img
Workarounds
Code:
# sh bootbt
This Script Needs Root! Type : su
The 2.2 rom I am running does not come with the "cut" binary
So replace the top line
perm=$(id|cut -b 5)
with
perm=$(id | busybox cut -b 5)
For the same effect
Now working through these ...
/dev/block/mmcblk0p5 needs to be replaced with /dev/block/mtdblock3
Constantly getting ioctl LOOP_SET_FD failed: Device or resource busy when trying to mount the image ...
OK here's where I am at
Code:
busybox losetup /dev/block/loop2 /sdcard/BT5/bt5.img
losetup: /dev/block/loop2
yup got bt5.img assigned to block device /dev/block/loop2, working through each step now with these new paths crossing my fingers to get this working before I fall asleep at my damn keyboard
Code:
busybox mount /dev/block/loop2 /data/local/mnt
mount: mounting /dev/block/loop2 on /data/local/mnt failed: Device or resource busy
(*!&^&*!£%!!!!
As per Muts' post, any apps running on the sdcard can cause this issue, moving all my apps back to the device has gotted around this issue and presented a new one
Code:
# sh bootbt
mkdir failed for /data/local/mnt, File exists
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
hmmm
Update 02/06/2011 ~ 12:48 BST
Mnaully stepped through each step up to the chroot in the boot bt script
Code:
busybox chroot /data/local/mnt sh
This got me an "ash" shell inside a new chroot of /data/local/mnt
Code:
/bin # which bash
/bin/bash
/bin # bash
sh: bash: not found
/bin # /bin/bash
sh: /bin/bash: not found
/bin # ls -la /bin/bash
-rwxr-xr-x 1 root root 617344 Apr 19 2010 /bin/bash
/bin # id
uid=0(root) gid=0(root)
/bin # whoami
root
clearly need to spend more time on this and figure out why it can't execute bash even though it is there :S