The complete Linux installer doesn't execute code when you press launch or start Linux...
The terminal is left blank with only some letter and no first time setup. I destroyed my sdcard a week ago and i run it from internal storage.
I have tried debian ; Linux 13.04 core, small now testing large; Linux 13.10 small ;
I am sure i can use loop devices because i moved some apps to my sdcard some time ago, i heard it requires loop devices.
It has knox and i rooted it without knox 0x1 it stays at 0x0. I used SELinuxModeChanger because some tutorial says that android 4.4 needs it...
Please help. Using the Samsung s4 gt-i905 :crying:
Related
Started to mess about with this earlier today, finally got the damn thing to work Turns out it is quite easy..
First, to get one thing straight, this will only boot the kernel, it will dump you at a shell which you have to remotely log on to via telnet over usb. There will be some (not so) fancy text appearing on your phone's screen but that is about it. Also, it only works on unlocked phones.
This is what you get:
On your computer you'll get this:
Cool, huh? Btw, this is running from a memory card, your OS will be untouched so as soon as you reboot the phone it will boot right back into WM2003/5/6.
1. What you need
* A HTC Typhoon running any rom of your choice (I did it on WM6).
* A miniSD memory card
* A Linux distro - I downloaded the Ubuntu Live CD and ran it through VMWare, no need to install anything or reboot your computer.
* miniSD image of Xanadux - this is the linux port for HTC devices. Grab the latest version here: http://rapidshare.com/files/92218185/Linux.zip.html
(these files are extracted from the miniSD image file found here: http://vivien.chappelier.free.fr/typhoon/download.html)
2. How to run linux on the Typhoon
1. Instead of installing linux properly on your phone which requires partitioning of the internal memory etc (a lot can go wrong) we'll put it on the memory card then a Windows Mobile program called HaRET will boot linux for us from WinCE. Completely non invasive in other words.
This bit is dead easy, just extract the Linux.zip file you just downloaded and copy the files to the root of your memory card (must be memory card, can't do this from the internal memory afaik). Next, go to the File Explorer on your phone and find the file HaRET.exe. Run it then press the run button (this button has focus when you execute HaRET.exe so just press the joystick when the windows appears) and you will see a message saying "Booting linux", then after a few seconds your screen will go black and some text will appear.
Voila! That's linux running on your phone!
2. Connect to the phone via telnet
If read the last line of text that appeared on screen you'll see that it says "Press enter to activate this console" but no matter what buttons you press on the phone nothing happens, some gibberish appears but that's it.
Solution: telnet to the phone from your computer.
Get Ubuntu to boot on your computer, then go to Applications->Accessories and run the Terminal. Next type in the following commands:
Code:
modprobe cdc_ether
modprobe usbnet
ifconfig usb0 up 192.168.9.1
and finally
Code:
telnet 192.168.9.10
Login with username root and you'll find yourself at a shell like the screenshot above. Everything you see from now on is coming linux from your phone!
I've noticed that Xanadux doesnt always initialise the USB port unless it is connected via USB when booting up so make sure you always have your phone connected via USB when you run HaRET.
Now I'm going to try to figure out how to get the GSM module to work...
LINUX based ROM??
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
ryanchanmd said:
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
Click to expand...
Click to collapse
Hey, well, I don't know enough to make a linux rom for smartphones. I'd love a working linux distro for Typhoons & Windows Mobile phones in general but it is way out of my league unfortunately.
Btw, I probably should clarify that I only wrote the tutorial, the actual linux port is made by someone else.
for the past couple of days i have been trying to install Ubuntu 13.04 on my nexus 7 but unfortunately, i keep running into problems. i have a laptop with Ubuntu 13.04 installed on it, but when i run the desktop installer it gives mean error for checksum validation. then i found a way that you could do it on a windows PC however when i go to download the cd images it bring me to a 404 (page not found) website. i would give the link but i am not allowed due to my account restrictions. if anyone could call me via Skype or team-viewer and could help me or perhaps provide an alternate way of installing Ubuntu or even tell me what i am doing wrong it would be much appreciated.
thanks in advanced, Kevin.
http://cdimage.ubuntu.com/releases/...3.04-preinstalled-desktop-armhf+nexus7.img.gz
dont i also need the boot img?
kevinperyea said:
dont i also need the boot img?
Click to expand...
Click to collapse
If you are installing it as the lone system, than yes, you will need the boot image. If you are using multirom to multiboot, than no, you wont need the boot image.
Sent from my Nexus 7 using xda premium
Its not very hard actually..First decide that do you want to remove android and replace it with android or yoou want to keep android untouched while multibooting ubuntu on your device as a secondary OPERATING system...
If you want me to I can write a full guide describing both procedures....I RECOMMEND MULTIBOOTING....
I need some help too
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
Thank's in advance,
GGgamer16
* one more thing ,i saw someting about multibooting, does it work like in windows(when you boot up it's asking you which os to run) or how does it work, and tell me hwo do i do it.
Ubuntu 13.04 on Nexus 7 2012
Posting in wrong spot... couldn't delete :/
hello forum users,
I bought the Samsung Galaxy S4 2 month ago and I want to run Backtrack 5 ARM version on it, but everytime is want to start BT there are mount errors or other issues so that backtrack wont start, and my question is what do i wrong ?? i rooted my phone already and tried to start linux with the complete linux installer from the playstore. I installed busybox and vnc viewer and terminal emulator already. Even tried to start BT with the boobt sh command but it failed to on mount issues etc. my phone
Samsung galaxy s4 GT-I9505 with 16 GB and 32 GB Sdcard
jelly bean 4.2.2 and rooted device
Can anyone help me ?
Backtrack on S4
itworksfine said:
hello forum users,
I bought the Samsung Galaxy S4 2 month ago and I want to run Backtrack 5 ARM version on it, but everytime is want to start BT there are mount errors or other issues so that backtrack wont start, and my question is what do i wrong ?? i rooted my phone already and tried to start linux with the complete linux installer from the playstore. I installed busybox and vnc viewer and terminal emulator already. Even tried to start BT with the boobt sh command but it failed to on mount issues etc. my phone
Samsung galaxy s4 GT-I9505 with 16 GB and 32 GB Sdcard
jelly bean 4.2.2 and rooted device
Can anyone help me ?
Click to expand...
Click to collapse
I'm having issues as well, however I can at least get it to boot. Have you tried setting it up by following these instructions? http://forum.xda-developers.com/showthread.php?t=1079898
My problem is starting the gui with vnc. All I get is a grey box. Also, I'm not sure why but I'm missing tools like airmon, aireplay etc. which should be in /sbin. Also when ever I attempt to run any of the programs from terminal emulator I get a message:
ifconfig is available in /sbin
The command could not be located because /sbin is not included in the PATH environment variable. This is most likely caused by the lack of admin priviledges associated with your user account.
i am sorry i tried to delete the poste (wrong adress ) but i can't
if any one tells me how to delete it
Ps : or how to make the script work on galaxy s4 it would be great, thanks
Solutions to installing Linux on CM11 on my OnePlus One
So, I wanted to install Kali on my phone and encountered many issues. I have found solutions to my issue and thought I would share the solutions for those who also encounter my issues.
1. Unable to change root password.
This issue was solved by installing com.mrbimc.selinux from play store (Sorry, I hate the rules and wish I can skip them and post a URL) and changing to permissive mode.
You may need to run this in Linux after you configure it
Code:
apt-get install selinux-policy-default
2. After running upgrade, I saw that PostgreSQL could not start causing the upgrade to fail "could not create IPv4 socket: Permission denied" and found the solution to be using the following command
Code:
usermod -a -G android_inet postgres
Now I got everything working properly.
So you're installing pure Linux kernel to android? Sorry I don't follow you
norpan111 said:
So you're installing pure Linux kernel to android? Sorry I don't follow you
Click to expand...
Click to collapse
I think he is doing a CHroot install where the linux distro shares the same kernel as android but runs all of its processes within one process executed on the host kernel
I also struggled with installing Kali linux at first but Robherc's LinuxOnAndroid/Complete Linux Installer FAQ helped me.
http://www.robherc.com/hosted/linuxonandroid/FAQ.html
What it doesn't say there is Kali linux' init VNC pass is kalilinux
I don't see a significant performance impact from running kali linux on the One.
The overall goal is to run debian or a linux distribution with LXDE on a Samgsung Galaxy Tab 4 (8", SM-T330NU).
I've been doing some research for a last week but if there are readers who can point out any obvious pitfalls, any constructive feedback will be greatly appreciated.
Please shout out if I'm straying off in a wrong direction or a time wasting dead-end.
Device:
- Samsung Galaxy Tab 4, 8", SM-T330NU.
- Android 4.4.2
- Build number: KOT49H.T330NUUEU1AND4
- SE for Android status: Enforcing
- Knox Enabled device
- Boot loader is locked?
- device has been rooted with CF-AutoRoot, automatic updates disabled.
------------------------------------------------
The story up to now:
Of all the interesting debian install options out there, I'm interested in Sven-Ola's Debian on Android Kit, which allows Debian and Android to run "side-by-side" without chroot.
http://sven-ola.dyndns.org/repo/debian-kit-en.html
-> various Debian on Android options can't install, installer scripts fail, likely due to SELinux status set to Enforcing by Default.
->
Code:
setenforce 0
does not work.
Apparently the stock kernel was compiled with flag
Code:
EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true
which prevents changing the SELinux status.
-> Proceeded to build the kernel from source (http://opensource.samsung.com/) according to online documentation and turn off the flag for enforcing SELinux.
http://graemehill.ca/compiling-permissive-android-kernel/
-> Kernel build was successful. Outputs:
Code:
zImage
and module drivers as
Code:
*.ko
-> I needed to repackage the new kernel into a boot.img to flash to device via ODIN.
Utilities that I found included:
- bootimg_tools_7.8.13.zip from xda forum
http://forum.xda-developers.com/showthread.php?t=2319018
- abootimg (from linux repository)
https://gitorious.org/ac100/abootimg/source/7e127fee6a3981f6b0a50ce9910267cd501e09d4:
- mkbootimg scripts by xiaolu
https://github.com/xiaolu/mkbootimg_tools
- The tools create a
Code:
boot.img
which I've made into a tar and attempted to flash to device.
-> So far, the only BOOT file that successfully downloaded was the one from stock. Any customized ones don't download properly.
-> Customized boot.img attempts results in "
Code:
Cannot do normal boot
" or "
Code:
Unsupported dev_type
" errors on the tablet screen in download mode.
So far I have not bricked the device. In all cases, I was able to re-flash with the stock boot.img and the device still works.
-> after a week of research and trying out different attempts, could it possible that the bootloader is locked?
I see QUALCOMM SECUREBOOT Enabled.
Is it true that new Samsung devices with Android 4.4.2+ come with locked bootloaders?
http://androidforums.com/samsung-galaxy-s4/788644-knox-security-locked-bootloader-new-firmwares.html
----------------------
For those who've read the long story. Thanks
Is the bootloader indeed locked? Is this a real dead-end?
Any suggestions?
I have returned to square-one and started debugging lines in the Debian for Android Kit Installer scripts.
I am able to make baby-steps, altering lines of code to get incrementally closer to a Debian installation, but it will be pointless if userspace programs on Debian don't work in the end.
Can anyone provide insight if Debian on Android is possible on Samgsung Galaxy Tab 4 ?
Thanks,
garrooo said:
The overall goal is to run debian or a linux distribution with LXDE on a Samgsung Galaxy Tab 4 (8", SM-T330NU).
I've been doing some research for a last week but if there are readers who can point out any obvious pitfalls, any constructive feedback will be greatly appreciated.
Please shout out if I'm straying off in a wrong direction or a time wasting dead-end.
Device:
- Samsung Galaxy Tab 4, 8", SM-T330NU.
- Android 4.4.2
- Build number: KOT49H.T330NUUEU1AND4
- SE for Android status: Enforcing
- Knox Enabled device
- Boot loader is locked?
- device has been rooted with CF-AutoRoot, automatic updates disabled.
------------------------------------------------
The story up to now:
Of all the interesting debian install options out there, I'm interested in Sven-Ola's Debian on Android Kit, which allows Debian and Android to run "side-by-side" without chroot.
http://sven-ola.dyndns.org/repo/debian-kit-en.html
-> various Debian on Android options can't install, installer scripts fail, likely due to SELinux status set to Enforcing by Default.
->
Code:
setenforce 0
does not work.
Apparently the stock kernel was compiled with flag
Code:
EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true
which prevents changing the SELinux status.
-> Proceeded to build the kernel from source (http://opensource.samsung.com/) according to online documentation and turn off the flag for enforcing SELinux.
http://graemehill.ca/compiling-permissive-android-kernel/
-> Kernel build was successful. Outputs:
Code:
zImage
and module drivers as
Code:
*.ko
-> I needed to repackage the new kernel into a boot.img to flash to device via ODIN.
Utilities that I found included:
- bootimg_tools_7.8.13.zip from xda forum
http://forum.xda-developers.com/showthread.php?t=2319018
- abootimg (from linux repository)
https://gitorious.org/ac100/abootimg/source/7e127fee6a3981f6b0a50ce9910267cd501e09d4:
- mkbootimg scripts by xiaolu
https://github.com/xiaolu/mkbootimg_tools
- The tools create a
Code:
boot.img
which I've made into a tar and attempted to flash to device.
-> So far, the only BOOT file that successfully downloaded was the one from stock. Any customized ones don't download properly.
-> Customized boot.img attempts results in "
Code:
Cannot do normal boot
" or "
Code:
Unsupported dev_type
" errors on the tablet screen in download mode.
So far I have not bricked the device. In all cases, I was able to re-flash with the stock boot.img and the device still works.
-> after a week of research and trying out different attempts, could it possible that the bootloader is locked?
I see QUALCOMM SECUREBOOT Enabled.
Is it true that new Samsung devices with Android 4.4.2+ come with locked bootloaders?
http://androidforums.com/samsung-galaxy-s4/788644-knox-security-locked-bootloader-new-firmwares.html
----------------------
For those who've read the long story. Thanks
Is the bootloader indeed locked? Is this a real dead-end?
Any suggestions?
I have returned to square-one and started debugging lines in the Debian for Android Kit Installer scripts.
I am able to make baby-steps, altering lines of code to get incrementally closer to a Debian installation, but it will be pointless if userspace programs on Debian don't work in the end.
Can anyone provide insight if Debian on Android is possible on Samgsung Galaxy Tab 4 ?
Thanks,
Click to expand...
Click to collapse
I have the same device - Linux would be cool. What about Ubuntu? You should delete that Knox stuff??
Sent from my SM-T330NU using XDA Free mobile app
debian noroot offers some linux experience on Samsung Galaxy Tab 4
Thanks for your reply, rsktkr1,
I have installed the pelya's "debian no root" app in Google Play Store
It is not exactly what I am looking for, but it is one step closer.
From debugging the installation scripts of Debian on Android Kit, I've been executing the lines of the scripts in shell one by one. It is a good learning experience of learning linux commands. The line that fails is the busybox's "chroot" command, which is used to safely install the linux environment using "debootstrap". The command fails due to security constraints of SELinux=Enforcing.
That got me researching along the lines of chroot and fakechroot.
pelya's "debian no root" works using fakechroot, which doesn't need as many permissions and thus can be deployed on the T330NU with straight forward installation.
(an interesting video is hosted on the google play website as well)
Once the app is installed, it appears to be a Wheezy installation of Debian with a XFCE desktop. The app has some learning curve to it to make it easier to use (not many people have the patience for it, hence the 3.7 star rating at the time of writing).
If you use this app to get a running linux distribution on your Galaxy Tab 4, here are a few things to try:
- back button = onscreen keyboard.
- there are also onscreen buttons for special keys like Alt, Ctrl, etc
- use terminal and apt-get install <packages of your choice; (packages may be named slightly differently than Canonical's/ubuntu's repository)>
I personally got a text editor (leafpad) so that I can write into a text file and save in a known location than to write in Samsung's Memopad that saves to some unknown location on the device.
----------------------------------------------------------------
Plans to come:
- debian noroot is good but has some limitations that affect me: no audio support.
- fakechroot has a few things that aren't supported. I was unable to properly install openjdk and openjre as it still requires some high privileged backend features, unfortunately also blocked by SELinux=Enforcing.
Workarounds in mind:
- get a hold of another ARM-powered android device and unpackage debian by executing the "debootstrap" command on it, maybe onto an SDCard, then insert into my device.
- Cyanogenmods have been known to release custom mods even on top of locked bootloaders. I might wait for that, yet it might be a long while. Developers at Cyanogenmods must have lots of hurdles to overcome.
It's been fun looking at code for ARM processor (armel/armhf), though SELinux and locked devices are restrictive.
For now, I'm happy with running full Lubuntu Linux installation on x86 Acer Iconia.
Here is a tip: Use 'Complete Linux Installer'. It lets you run Debian, Ubuntu with LXDE. Everything works. Has everything you need and has instructions. It should work perfectly in the Tab 4 becuase last time I ran it, it was in my 1st Generation Kindle Fire and it has horrible specs compared to this tab, and it ran fine in the Fire with almost no hiccups
Sent from my SM-T230NU using XDA Free mobile app