Please help! I've spent many hours hitting every mistake and carefully following steps and fixes until finally i get this in terminal.
I have vnc, terminal, busybox, su, the cd fix for. 629 To root, and less time than i had at the beginning but more appreciation for what you do.
When I launch from Complete linux installer
Sent from my DROID2 GLOBAL using xda app-developers app
$
$ cd /sdcard/ubuntu
$ su
# sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
no: unexpected operatorChecking loop device... MISSING Creating loop device... OK
mount: mounting /dev/block/loop255 on /data/local/mnt failed: No such device
Error: Unable to mount the loop device!
Sent from my DROID2 GLOBAL using xda app-developers app
And I get a slightly different error when using the boot widget, possibly because of the path to .img file
$
$ cd /mnt/sdcard/ubuntu
$ su
# /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/ubuntu/ubuntu.img
no: unexpected operatorChecking loop device... FOUND
losetup: /dev/block/loop255
Error: Unable to attach image to loop device! (Image = /mnt/sdcard/ubuntu/ubuntu.img)
#
Sent from my DROID2 GLOBAL using xda app-developers app
nb26 said:
And I get a slightly different error when using the boot widget, possibly because of the path to .img file
$
$ cd /mnt/sdcard/ubuntu
$ su
# /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/ubuntu/ubuntu.img
no: unexpected operatorChecking loop device... FOUND
losetup: /dev/block/loop255
Error: Unable to attach image to loop device! (Image = /mnt/sdcard/ubuntu/ubuntu.img)
#
Sent from my DROID2 GLOBAL using xda app-developers app
Click to expand...
Click to collapse
Hi,
Did you ever manage to fix this? I'm getting exactly the same error!
Thanks
nb26 said:
$
$ cd /sdcard/ubuntu
$ su
# sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
no: unexpected operatorChecking loop device... MISSING Creating loop device... OK
mount: mounting /dev/block/loop255 on /data/local/mnt failed: No such device
Error: Unable to mount the loop device!
Sent from my DROID2 GLOBAL using xda app-developers app
Click to expand...
Click to collapse
ame problem for me, did you ever manage to get past this issue? If so, do share!
Sent from my Nexus 7 using xda app-developers app
....no, kernel not able to mount boot image
switched to droid 4, only $30 more on ebay.
vevmesteren said:
ame problem for me, did you ever manage to get past this issue? If so, do share!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Dude firstly try try try. . . facing all type of these problems after i checked my supersu logs in that it is clearly mentioned that supersu pro is needed. . . so i did download i think onhax.net will provide it. try it installing and updating it reboot and try by terminal. let me know any issues.
I have installed Googy Max dual boot kernel..i start terminal i installed busybox i unzipped ubuntu in ubuntu folder..and i have this error in terminal
Code:
[email protected]:/ $ su
[email protected]:/ # cd sdcard/ubuntu
cd sdcard/ubuntu
[email protected]:/sdcard/ubuntu # sh ubuntu.sh
sh ubuntu.sh
mkdir failed for /data/local/mnt, File exists
Loop device exists
ioctl LOOP_SET_FD failed: Device or resource busy
mount: Device or resource busy
net.ipv4.ip_forward = 1
ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
BusyBox v1.21.1-Stericson (2013-07-08 15:58:11 BST) multi-call binary.
Usage: chroot NEWROOT [PROG ARGS]
Run PROG with root directory set to NEWROOT
Shutting down ubuntu ARM
failed: Device or resource busy
losetup: /dev/loop7: No such file or directory
1|[email protected]:/sdcard/ubuntu #
Sent from my GT-I9300 using Tapatalk 4
g9savvas said:
I have installed Googy Max dual boot kernel..i start terminal i installed busybox i unzipped ubuntu in ubuntu folder..and i have this error in terminal
Code:
[email protected]:/ $ su
[email protected]:/ # cd sdcard/ubuntu
cd sdcard/ubuntu
[email protected]:/sdcard/ubuntu # sh ubuntu.sh
sh ubuntu.sh
mkdir failed for /data/local/mnt, File exists
Loop device exists
ioctl LOOP_SET_FD failed: Device or resource busy
mount: Device or resource busy
net.ipv4.ip_forward = 1
ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
BusyBox v1.21.1-Stericson (2013-07-08 15:58:11 BST) multi-call binary.
Usage: chroot NEWROOT [PROG ARGS]
Run PROG with root directory set to NEWROOT
Shutting down ubuntu ARM
failed: Device or resource busy
losetup: /dev/loop7: No such file or directory
1|[email protected]:/sdcard/ubuntu #
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Check this bro !!
http://forum.xda-developers.com/showthread.php?t=2194237
Thnks solved but now nothing..i wrote the code and the resolution then vnc not connecting
Sent from my GT-I9300 using Tapatalk 4
I could successfully install Ubuntu 13.10 via Complete Linux Installer under Android 4.4.2 (on a Nexus 5). If I reboot and then open Ubuntu 13.10, everything works fine. But if I close Ubuntu and open it again (without reboot), I get:
[email protected]:/ $
[email protected]:/ $ cd /sdcard/ubuntu
[email protected]:/sdcard/ubuntu $ su
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
[email protected]:/storage/emulated/legacy/ubuntu # sh /data/dcom.zpwebsites .linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[39]: dirname: not found
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Device or resource busy
Error: Unable to mount the loop device!
1|[email protected]:/storage/emulated/legacy/ubuntu #
What is the problem?
Hear hear. Same issue Galaxy S5 g900r4. SELINUX is permissive(finally).
[email protected]_T00J:/ $
[email protected]_T00J:/ $ cd /mnt/sdcard/ubuntu
[email protected]_T00J:/mnt/sdcard/ubuntu $ su
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/ubuntu/ubuntu.img
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/ubuntu/ubuntu.img
[email protected]_T00J:/storage/emulated/legacy/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/ubuntu/ubuntu.img
MD5 file found, use to check .img file? (y/n)
n
Checking loop device... FOUND
losetup: /dev/block/loop255: No such file or directory
Error: Unable to attach image to loop device! (Image = /mnt/sdcard/ubuntu/ubuntu.img)
1|[email protected]_T00J:/storage/emulated/legacy/ubuntu #
if you know this issue please help me thank for you time
Hey Guys,
i got a broken Tolino Vision 3 HD from a friend to fix the issues with the android. It´s a popular ebook reader in Germany.
At the moment I got the device it stuck in language selection and the partition for the ebooks wasn´t shown after USB connection.
So I downloaded the new software version from the vendor "mytolino" (I am not allowed to post urls). I tried to update via
fastboot update
Click to expand...
Click to collapse
but i got this error:
archive does not contain 'android-info.txt'
error: update package '..\update.zip' has no android-info.txt
Click to expand...
Click to collapse
. So I unpack the .zip and try to flash the images manualy. This didn´t work. After this is tried to copy the update.zip to /sdcard via adb push but this didn´t work, too.
Question:
Is there any way to flash the device with the given update.zip?
Regards and all good wishes from sunny Germany
Did you tried to do factory reset? Are you able to boot into recovery using key-combination?
The more heavy way I used yesterday to reanimate my Tolino page after trying to install OpenGapps on them (no, did not work oO).
I am not allowed to post URL's because of "Noob-Protection" in Forum. There is a "Tolino Vision 2 rooten" howto in web. Some parts of them you can use to solve your problem.
1. Create own ADB-Enabled custom recovery (Did worked for me only with 10.0.1 update package). Should be done on Linux
Code:
$ mkdir custom_recovery
$ cd custom_recovery
$ unzip ../update.zip recovery.img
$ mv recovery.img recovery.img.orig
$ abootimg -x recovery.img.orig
$ mv initrd.img initrd.img.orig
$ mkdir initrd
$ cd initrd
$ zcat ../initrd.img.orig | cpio -vid
Adjust default.prop with values "ro.secure=0", "ro.debuggable=1" und "persist.sys.usb.config=mass_storage,adb".
Code:
$ find . | cpio --create --format='newc' | gzip > ../initrd_adb_enabled.img
$ cd ..
$ abootimg --create recovery_adb_enabled.img -f bootimg.cfg -k zImage -r initrd_adb_enabled.img
You get error : "updated is too big for the Boot Image" with new size value. Calculate this value to hexadecimal and adjust the "bootsize" in "bootimg.cfg" to hex-value
Do abootimg again.
2. Use the custom recovery to trigger update manually
Code:
$ fastboot boot ../custom_recovery/recovery_adb_enabled.img
$ adb shell
# mount -t vfat /dev/block/mmcblk0p4 /sdcard/
# exit
$ adb push update.zip /sdcard/update.zip
$adb shell
# cd /sdcard
# busybox unzip update.zip META-INF/com/google/android/update-binary -d /tmp
# busybox chmod u+x /tmp/META-INF/com/google/android/update-binary
# /tmp/META-INF/com/google/android/update-binary 3 1 /sdcard/update.zip # Update installieren
# sync && sleep 5 && sync # sicherheitshalber, wenn man dran glaubt
# reboot
Source: google for "e-reader-forum Toolino vision 2 rooten"