yashsingh1/xdaforums huggingface dataset:
[Android Software Development] abgder:
hello guys,

need help..stuck at

u0_a109@850p:/ $

u0_a109@850p:/ $ cd /mnt/sdcard

u0_a109@850p:/mnt/sdcard $ su

card/kali-linux-1.0.7-armhf.img

Checking loop device . . . FOUND

mount :mounting /dev/block/loop255 on /data/local/mnt failed

: Invalid argument

error: Unable to mount loop device!

any solution?
[Android Software Development] robherc:
abgder please use the instructions in my FAQ to upgrade to bootscript v9.0

The error that you just posted is frequently encountered when using the older (sorry, we haven't gotten them updated in the app yet) bootscripts to mount the ext4 images that the newer android versions require. That is actually the first glitch that was repaired during my re-writing of the bootscript with version v9.0 being the final result ;)
[Android Software Development] abgder:
already update bootscript but then im facing

u0_a109@850p:/$

u0_a109@850p:/$ cd/sdcard

u0_a109@850p:/sdcard $ su

d/files/bootscript.sh/sdcard/kali-linux-1.0.7-armhf.img <

/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh

:not found

/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh

:not found

Error : /sdcard/kali-linux-1.0.7-armhf.img

/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh

:bad number
[Android Software Development] FriedBacon:
I'm having an issue getting this to run on my Sm-t520.. Not sure what to do. Happens with every distribution. Loop mount issues I think. Checksum is never valid. No matter how any times I download. I have checked the md5 manually and it is the same... So there may be an issue with the shell script. I can't read she'll scripts tho. (other than echo lol)
[Android Software Development] robherc:
If the checksum fails, then it's most likely a problem with your extraction program. For whatever reason, many extraction programs seem to "not like" the format those images were saved in (the "default" extraction programs in my android 4.2.2 tablet and phone worked fine, and I got checksum passed with every image I've tried on either...for what it's worth). That would be the first problem that I would recommend working on, as an invalid extraction can cause any number of unexpected problems later, if any data was corrupted.

As for the "device or resource already in use" error, that usually just means that something got "stuck" in memory (i.e. from an earlier attempt to start LinuxOnAndroid), and is as simple to fix as simply rebooting your device.

Also, if you have not done so yet, please use the instructions in my FAQ to update your bootscript.sh file to the newest (v9.0) version (sorry, but our lead developer's getting married, so we haven't been able to get the updated bootscript uploaded to Google PlayStore updates yet). The previous bootscript versions conatined several errors, one of which caused them to attempt to mount all images as ext2 filesystems, which caused very many people to get mounting errors with them on the first attempt, and "device or resource busy" errors on every attempt to load LinuxOnAndroid after that.
[Android Software Development] FriedBacon:
thank you the updated scripts solved the issue. :)
[Android Software Development] FriedBacon:
any ideas how to get unity running as default on the 13.10 ubuntu image? im just being lazy and dont want to google.
[Android Software Development] nvo2411:
I am using omni ROM on my galaxy r. I downloaded ububtu 13.04 core image and did everything according to the instructions.

Everything went ok and when I started vnc viewer and connected it got connected but only showing small black and white checks. The mouse pointer works but the screen is only showing small black and white checks.

Please help
[Android Software Development] robherc:
Interesting that you got a "normal" mouse pointer...most people only get an "X" for a mouse pointer on that screen.

Anywise, can you tell us *exactly* which image you used? If you used an ext2 image, then the newer ROMs don't work right with ext2 filesystems, and many people have exactly that problem when using ext2 images. You'll want to download an ext4 image, then update your bootscript.sh file to v9.0 using the instructions in my FAQ.

Once you've downloaded an ext4 image, and updated to the new bootscript, that problem should go away. As far as the error you got about "can't mount /storage to $mnt/external_sd" .. that just means you don't have an sd-card installed, and is not a problem.
[Android Software Development] nvo2411:
I am using Ubuntu 13.04 core ext4.v2 file.

About the boot file I will be updating and hopefully it may work. I will reply then. Thank u for the prompt reply

---------- Post added at 04:02 PM ---------- Previous post was at 03:50 PM ----------

Look at this after updating to v9
[Android Software Development] byohaserd:
Weird ubuntu

Aftef much trial and error I finally got Ubuntu 13.10 up and running. It looks like thia though, not the GUI I was expecting. Any ideas?

Im on a Nexus 7(Grouper) running C-Rom 7.1, Android 4.4.4
[Android Software Development] fastguy:
This is KDE. You got Kubuntu installed.
[Android Software Development] AnonVendetta83:
Unable To Mount Loop Device error

I'm attempting to run Arch on my Note 3 (SM-N900T). I followed all the instructions in the app's (copying the IMG and md5 then setting the path, installing the VNC and terminal emu app). But the error hits when I try to launch, first it says loop device is missing and being created. But instead of seeing root@localhost I instead see "unable to mount the loop device". I have tried editing the .sh script, a suggestion I found was changing ext2 to ext4, but it was already set. I also manually updated to latest bootscript.sh v9.0, same result. I am using SlimROM with the latest Temasek kernel. I have also tried flashing LeanKernel, but I doubt that either of the kernels are at fault since the loop device is created but not mounted. I just want access to real Linux commands/utils in a terminal, maybe even an extremely lightweight desktop/window manager like OpenBox or LXDE.

Thanks for any help!
[Android Software Development] Galaxy droid fan 7:
Finally I found the right thread, I'm having trouble with it where it won't boot up in vnc no matter what I try it says connection refused
[Android Software Development] robherc:
What error messages are you getting in the Android Terminal Emulator window?

---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------

AnonVendetta I know of many people who have gotten LinuxOnAndroid running successfully on Samsung devices, so I think we should be able to get yours running as well. First off, please confirm that the image file you downloaded is an ext4 filesystem image, as many newer devices do not "like" the ext2 images. Next, assuming you are already using an ext4 type image, and have downloaded and installed the v9.0 bootscript.sh file following the directions in my FAQ, please upload a screenshot of the terminal window from when the error occurs, just in case there are other messages in that window which we can use to help solve your problem. It may be that your device/ROM combination will be one of the few which requires a custom-modification to the bootscript.sh file. There are not many such combinations which I've found, but I have had to modify custom bootscripts for 3-4 others.
[Android Software Development] Galaxy droid fan 7:
I was able to get my desktop environment up and running . But I think whatever version of Ubuntu I am running is missing a few key system files it's the Lite version you can get from following the links and complete Linux installer from SourceForge I didn't have enough room to install the large version anyway I noticed the built-in web browser was not working at all so I did an apt get to try to install firefox. But mid install it could not complete:
[Android Software Development] xda23:
Who's all running Linux on there tmobile Gs5 and what version are you running? And how is it running pretty good. Thanks In advance!!!
[Android Software Development] vpwrf:
I am using Ubuntu 13.04 small image and also now getting the 404 not found problem with apt-get. It's because Ubuntu has stopped supporting 13.04. I have done a workaround by editing /etc/apt/sources.list and changing "raring" to "precise". This makes apt-get use packages from Ubuntu 12.04 instead of 13.04. Does anyone know a better workaround until 14.04 gets fully released for Linux-on-Android? I tried old-releases.ubuntu.com but still get the 404 error.
[Android Software Development] xda23:
Anyone any information would be greatly appreciated. :)
[Android Software Development] Galaxy droid fan 7:
I have a problem with the large build of 13.10 Ubuntu making my applications disappear when I install a new program or update it's a bug if you google it and a friend of mine suggested to recompile the kde enverment only problem is I'm a linux noob so can anyone help me out?
[Android Software Development] robherc:
The easiest workaround for this, and the 13.04 404 errors is to use the 13.10 Small image. that version is still supported (last I checked), and the lxde desktop doesn't have KDE's stability issues ;)
[Android Software Development] Galaxy droid fan 7:
Yes but when i try to install JDK or the ubuntu software center it messes up my desktop environment where I can't do anything any workaround?
[Android Software Development] Galaxy droid fan 7:
Thanks I'll do that but where do I go to find it?
[Android Software Development] mascondante:
Is Knox preventing SELinux mode change still an issue on KitKat Samsung devices? I'd like to know before I try downloading that large Ubuntu package again.
[Android Software Development] fastguy:
It's not knox (only) but also the kernel itself. You need to disable Samsung security features like setuid limitations. Then you can disable selinux when in android and these Linux chroot works properly.
[Android Software Development] alexischino:
I been trying to run ubuntu for a couple of weeks now without luck! The only thing i get is a grey screen i have also try debian, and when i download the small image and i try to extract it i get an error this happen with debian,arch linux,ubuntu 13.10-13.04 small image i'm only able to use the core images i'm using a Smsung galaxy mega 6.3 gt-i9200. Is anyone else having this issue? any help would be awesome!
[Android Software Development] alexischino:
This is what I get with Ubuntu 12.04 and 13.10
[Android Software Development] mascondante:
You might as well said open heart surgery. Well guess that's what google is for.
[Android Software Development] wrsg:
Just flash a kernel like the Nadia kernel where SELinux is disabled. This has been repeated several times now.
[Android Software Development] robherc:
That gray, thatched screen is often a symptom of using an ext2 filesystem image file on a system that "prefers" ext4 images. First step, find a program that will *correctly* extract the .zip of your image file (for some reason, many extraction programs do NOT accurately extract those files, I don't fully know why yet, but it's something to do with the zip format). Once you get an ext4-type image unzipped, and passing the md5-check, please use the instructions in my FAQ to download and install the v9.0 version of the bootscript.sh file (v7.8, v7.9, or v8.0 got installed when you installed the app), then try to boot your image, and let us know how it goes :highfive:
[Android Software Development] alexischino:
Thanks for the quick reply, i have download the (ext4-type image) and the (script v9.0) i have copy the script in the right folder. i run the comands in the terminal emulator correctly my phone go to the home screen and then i reboot my phone i launch the linux installer app and run the vnc viewer app but i get the same grey screen ??? i have also download the (debian ext4-type small image) and repeated the same process but the result was the same. what i'm doing wrong?
[Android Software Development] alexischino:
[MENTION=4148474]WEM97[/MENTION] I have 3.23gb of free space in my internal storeage and i wait several minutes on the grey screen but it never go away. My phone have 1.50 gb of ram and a 1.70ghz Qualcomm Snapdragon 400 procesor.
[Android Software Development] nvo2411:
Are you charging the phone while executing this process.Keep your usb port free during this process. It had happened with me.
[Android Software Development] alexischino:
No!! I always charge my phone to 100% before i set up the environment, i try with diferents rom's and kernels. what i really don't understand is that i have a old galaxy s blaze 4g and it runs debian! and it has a very low storeage memory and ram, i think this has to be something with the new knox bootloader.
[Android Software Development] robherc:
Can I ask you to please try booting into a fresh extracted .img file (i.e. re-extract from the downloaded .zip, then boot LoA again) and copy+paste a screenshot of all of the terminal feedback that gets displayed during the boot process? I think it would be easiest for me if we tried this with the Ubuntu core/small image, as those are ones with which I am more familiar.

I do not think that your problem is being caused by a lack of free resources, by anything to do with the USB charging status, or even necessarily by the knox garbage that Samsung has been cramming into their new devices (although that may be a piece of the problem). Most likely, it's a minor issue, like an incompatible binary filetype or a bad command in the init.sh script, that we can resolve fairly painlessly, once we find the "culprit." ;)
[Android Software Development] alexischino:
[MENTION=5818021]robherc[/MENTION]

Sure no problem! I'm going to download the ubuntu image again and take the screenshots of the terminal emulator booting process. I will post everything later.
[Android Software Development] alexischino:
I finally get it working i use the ext2-type image and it work!!
[Android Software Development] Samuelgames:
Has the LoA team considered libhybris for hardware enablement?
[Android Software Development] thenashy:
The device list link is dead.
[Android Software Development] robherc:
Yes, sorry, the website needs updated to simply remove the link, as that list is no longer necessary. All known/tested devices that ship with android 2.2.4 or newer on them are capable now.
[Android Software Development] makgun:
lg g2 with stock kk rom (4.4.2) Ubuntu has an error

I have an error which is "ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored" when I running to linux (Ubuntu ) on complete linux installer v2.8. How can I solve this problem? I am using Dorimanx v7.1 d802.

This error caused by creating loop service... What is your advice?

Thanks a lot from now.... See soon
[Android Software Development] robherc:
Try downloading and installing the bootscript.sh file from: http://www.robherc.com/hosted/linuxonandroid/loop4/bootscript.sh

You can install it using the instructions in my FAQ; just using the download link I posted in this post, rather than the one in the FAQ.

This version of bootscript.sh doesn't create its own loop device, and instead uses one that most devices already have; thus avoiding loop device creation errors, but at a slight risk that the chosen loop device could already be in use, which would cause this script to error and abort (without harming anything else).
[Android Software Development] morr22066:
Fedora bad download?

Hi. I have tried multiple times to download Fedora 20 and it keeps telling me that the file size is bad / wrong so it will not extract the files. I have tried it about a dozen times now with the same results.

I want to run it on a Toshiba Thrive which is currently running a modified CM10 ROM. I have plenty of storage on the device, it is a Tegra 2 processor and there is normally around 300 MB of RAM remaining. From what I have read in this thread it "should" run alright on the Thrive Tablet, but I cant seem to get a good download of Fedora 20 so that I can try it. I do have my own working copy of Fedora 20 that I run on my PC so I also wanted to know if I need to install "this version" of Fedora 20 or if it can be any working copy of Fedora 20? Does anyone have any suggestions?

Thank you.
[Android Software Development] xda23:
Is this stable and what's a good version to run on T-Mobile Gs5? Thanks :)
[Android Software Development] robherc:
Unfortunately, unknown to any of us when the images were first created, there seems to be some "room for creative translation" in the ZIP standards, resulting in some extraction programs extracting the image files perfectly, while others fall flat and will never achieve a successful extract+verify. The best thing I can suggest for now would be to try extracting the image file with a different extraction program, or maybe a few different ones, until you can get an extracted image that passes the md5 check.

---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------

Yes, this is stable for *most* devices. The version that's available from Google Play store should work, but you'll want to manually update to the v9.0 bootscript.sh file after you've installed & run the Complete Linux Installer program for the first time.

In order to update, you'll need to follow the instructions detailed in my FAQ. There's a link in the FAQ to the newest (v9.0) version of the bootscript file for you to download as well.

The biggest glitch currently known is with CM11 and some PA-based ROMs. A security "feature" in the newest versions of both CyanogenMod, and Paranoid Android ROMs prevents the Complete Linux Installer app from communicating further commands to the Android Terminal Emulator app after switching to root usermode; thus requiring a manual input of the command to start the bootscript.sh script in the Android Terminal Emulator window in order to start linux on either of those ROMs.
[Android Software Development] makgun:
I had tried your bootscript.sh but it doesn't work again.

Full log with terminal is

"u0_a156@g2:/ $

u0_a156@g2:/ $ su

/data/data/com.zpwebsites.linuxonandroid/files/busybox chroot /data/local/mnt /root/init.sh

/data/data/com.zpwebsites.linuxonandroid/files/busybox chroot /data/local/mnt /root/init.sh

ox chroot /data/local/mnt /root/init.sh <

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

Start VNC server? (y/n)

y

/root/init.sh: line 110: [: ==: unary operator expected

Start SSH server? (y/n)

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

* Starting OpenBSD Secure Shell server sshd ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

[ OK ]

If connecting from a different machine on the same network as the android device use the address below:

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

eth0: error fetching interface information: Device not foundSave settings as defaults? (y/n) (You can always change it later in the app)

y

Config saved to /root/cfg/linux.config

To shut down the Linux environment, just enter 'exit' at this terminal - and WAIT for all shutdown routines to finish!

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.

root@localhost:/# "
[Android Software Development] xda23:
So will there ever be a Ubuntu flash rom that can be flashed onto your like a regular rom? Thanks :)
[Android Software Development] deviouskind:
Help connecting to GUI through vnc

Hey all, was wondering if someone could help me out with this.

I finally was able to boot into Kali Linux terminal.

I followed directions from the app.

My issue is trying to access the GUI from VNC.

I try connecting to 127.0.0.1:5900 and I get an error saying ...

ECONNREFUSED (connection refused)

I tried using a few other IP addresses but no luck.

Does a VNC server need to be installed through command line before running VNC?

This is not in the directions. So I'm lost on what to do at this point.

If I do, can someone please help me with commands that will install vnc and ssh.

I tried installing yum and apt-get but these commands are not recognized.

How can I verify I'm even running off Linux?

Please help if you can. I'm real excited about this. I've tried for the longest time to at least reach the shell

And never had luck. Now I believe I'm in! Thanks
[Android Software Development] Galaxy droid fan 7:
Download SE linux permissive from g play store grant it root access, set it to permissive from se linux app reboot tablet and try again.

Hit the thanks button if I helped you
[Android Software Development] deviouskind:
Thanks for the response. Appreciate it.

So I tried that and no luck. This is what I'm getting.

I watched a few YouTube videos and everyone shows a lot more stuff going on like "would you like to enable vnc", "would you like to enable ssh"... Mine sits with...

u0_a104@t0ltespr:/ $

u0_a104@t0ltespr:/ $ cd /sdcard/kali/kalilinux

u0_a104@t0ltespr:/sdcard/kali/kalilinux $ su

root@t0ltespr:/ #

Any thoughts?
[Android Software Development] Galaxy droid fan 7:
Take it from me I've tried practically every version of Linux from that and the only versons that work are the ubuntu small images and the Fedora image. They have their drawbacks if you install certain programs on the ubuntu image you run the risk of messing up the desktop I call it the grey screen of death. And even though all the other versions have a gig and a half of space Fedora only seems to have seven hundred megabytes go figure? I wish you the best and if you can figure out how to get any of the other versions working correctly let me know
[Android Software Development] deviouskind:
Well thats some decent news to know... that only Ubuntu and Fedora works.

I tried Arch today and same thing happened.

So i will try Ubuntu and Fedora to see if i have different results.

I hope thats the key! Thank you for your help either way!
[Android Software Development] Galaxy droid fan 7:
The ubuntu 13.10 large image does work but if you install any program it completely cleans out your application list and you're unable to access any applications I wish I could fix that . I've pretty much given up on that app all have wanted to do was to play runscape on my tablet and the html 5 beta does not work .
[Android Software Development] deviouskind:
Well it didn't work for fedora or Ubuntu 10.3 small image

Same thing as before. I get root@t0ltespr and that's it.

Is it my device or ROM? Maybe still doesn't support bootloop?

Sprint Note 2 running Baked aosp rom by jlmancuso.

Any one else have ideas? Thanks again
[Android Software Development] Galaxy droid fan 7:
Oh make sure USB debugging is enabled you may have to enable the hidden developer options menu to get to it go to Settings about device and click on biuld number 10 times you should see pop up all throughout telling you you are a few clicks away from activating developer mode