Shouldn't the command you have listed:
./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
Actually be:
./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0p3
When I issue the command 'mount' it shows /dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0, among other items. Just trying to help... I don't see the mmcblk0 listed...
---------- Post added at 07:52 PM ---------- Previous post was at 07:11 PM ----------
OK - I just performed the steps in the link you provided above - for the A500 - and I have root. I can't get su permissions to work under adb shell, but I can get into root apps such as TiBu - running a batch job now.
I set up Superuser.apk by default to allow SU rights. Now I already gave TiBu SU rights before I upgraded to ICS - when I try to grant su rights to a new app, such as AppExtractor, it didn't work - I got an error - no root. If I try to mount /system/xbin or /system/bin with R/W in Root Explorer, it doesn't - the "mount r/w" button is at the top (I think because it was rooted prior to upgrade).
I do see su in /system/bin, but can't see or modify the permissions. Hope this info helps.
$((512 * 51200)) is the first sector of partition mmcblk0p3 on device mmcblk0 so it is correct. Mounting a partition at a sector would fail with an invalid argument, but losetup usually would not return an error. At the time the acer a200 was rooted similarly so that's why I posted it this way. Thanks for confirming that it's not needed, I'll change the OP.
/system can't be remounted as rw, that's why it has to be loop mounted, don't know why I'm still looking into it. So in the meantime loop mount it somewhere and then use root explorer to make any changes.