[Android Q&A, Help & Troubleshooting] robherc:
I noticed that you're running a 4.3 or newer Android OS on a samsung device. Please check into some tutorials about disabling Samsung KNOX for that specific device, if you haven't already. Once you have gotten rid of KNOX, please make sure your SELinux is set to "permissive," rather than "enforcing" and try again.

Once that's finished, and you've rebooted the device to make sure you changes took effect, if you still encounter the same problem, try running the bootcript.sh file from my website (should be version 9.0) from the command line. If it will start linux from the command line, but not through the CLI app, then that's a bug with the intercommunication between CLI and Terminal Emulator in Android 4.4.x. Zacthespack is currently working with the developer of Terminal Emulator to find & fix that bug. However, if it still won't run from command line after that, please let me know in here, and we'll find out what else we need to do for you. ;)

---------- Post added at 03:13 PM ---------- Previous post was at 03:04 PM ----------

Thank you for posting this useful information for everyone else to use :)

FYI, there is a new version of the bootscript.sh script supposed to be available sometime this week to update through the app (version 9.0). The line you showed there has been added, and is necessary for Lenovo tablets, as well as you Sony (also lines have been added for Samsung devices as well). The newest, stable version of bootscript.sh of which I personally am aware is hosted at:

www.robherc.com/hosted/linuxonandroid/bootscript.sh

If you want to look at the other scripts in that folder, feel free, but be warned that they are all *development* versions, and to be considered "pre alpha/unstable" at this time.

---------- Post added at 03:25 PM ---------- Previous post was at 03:13 PM ----------

First, can you please verify for me that your device is free of the Samsung KNOX, and has a "KNOX free" kernel installed? If not, then that could, unfortunately, have something to do with this problem. If you have already gotten KNOX off your machine, then this is a new error that I haven't seen yet, so I'd very much like to explore options for fixing it with you, in case others run into the same thing.

As a temporary workaround for this error, check under /dev/block in your device to see what loop devices already do exist; then comment out the lines in the bootscript.sh script which test for, then create /dev/block/loop255, and modify the line that loads $imagefile to /dev/block/loop255 so that it loads the file to a loop device that already exists on your system. You will also then have to change the loop device number in the line that mounts the loop device as well.

WARNING: DO NOT use /dev/loop0 as your loop device for LinuxOnAndroid, as this is a system device that mounts an ISO CD image, and can cause unstable behavior on some tested devices.

---------- Post added at 03:32 PM ---------- Previous post was at 03:25 PM ----------

What errors were thrown? Please post your errors in here as well, so I can see what other things might be causing problems on your system.

OK, this is a serious problem. The .md5 checksum file contains a number that was generated by running an md5 check on the original image file, before it was compressed. If your computer came up with a non-matching md5 sum (thus the error message), then it is guaranteed that your image file is not valid, and has been changed from the original version. If you haven't already mounted that image & made the changes yourself (such as by successfully booting into the image, then the image file must be replaced, and was likely corrupted in transfer when you downloaded it.