Database Info

Noob Tutorial: Ubuntu on Transformer

I've been looking around for some good tutorials, but in my opinion, almost everything was pretty difficult to understand for me.
But finally I found out how things are working (except of wifi, can You help me?
http://forum.xda-developers.com/showthread.php?t=1295718)
So I want to share my knowledge with You all and try to make it easy to understand.
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
2. Get the required files on Your Linux machine:
http://forum.xda-developers.com/showthread.php?t=1191141
On this link, in the second post is written flash kit for linux:
klick on "here" to download the flash kit.
3. Extract the flash kit into a folder (e.g. Desktop)
4. Now download the Ubuntu root files. They are located here:
http://rootzwiki.com/showthread.php?1072-ubuntu-on-the-transformer
You have to scroll a bit down then You see
"ubuntu-rootfs:
is available here md5sum(95eda389e64461533c51fd1e4e237a30)"
Again, click on "here" to download the rootfiles. (It'll take a while, since the file is 950mb)
4. Once this is done, extract the rootfiles into linux-flash-kit/images. (This folder is the one You have extracted in 3.
5. When You want to Dual-Boot Your device with Andoid AND Ubuntu, read on, otherwise go to point 6.
You have to download a nvflashable rom like for example "PRIME!"
http://forum.xda-developers.com/showthread.php?t=1251044
There You download the NVflash version and extract the image files in it, to linux-flash-kit/images, like You have done it with the ubuntu image file.
6. Now You have to choose.
If You want only linux: remember flash-purelinux.sh
If You want linux and Android Dual-Booting with Android as default OS:
flash-linux-android.sh
If You want linux and Android Dual-Booting with Linux as default OS:
flash-linux.sh
If You want to restore back to android: flash-android.sh
If You want to get to factory state: restore-default.sh
Now You have to install the APX drivers. How to do this, You can read in other threads. Basically download the NVflash file from this thread, in it, You'll find the drivers: http://forum.xda-developers.com/showthread.php?t=1123429
So connect Your tablet to Your PC, turn it off, and turn it on while holding down the Power Button and the Volume+ button.
What You'll see is nothing. Now Your device is in APX mode.
In Your Linux Computer, open up the console and go to the linux-flash-kit directory (In my case it is on the Desktop)
so I do:
cd Desktop\linux-flash-kit
So now You are in Your linux-flash-kit directory. From here You have to type:
sudo sh flash-linux-android.sh
OR You type this in what You have remembered in Point 6.
e.g.
sudo sh flash-purelinux.sh
or
sudo sh flash-linux.sh
This will take a while because the files are transfered to Your device.
7.
When it's done, Your device will start.
Turn it off, and start into Your Ubuntu.
When Ubuntu is Your main system, You start it up normally by pressing the power button.
When Android is Your main system and You are Dual-Booting it, hold down the power button and the Volume down key until the device says that Your have to press the Volume-up key. Do this and You will see a Linux code with two penguins on the top running down Your screen. That's just good like it is.
Finally You should see the Ubuntu Setup with the language selection.
Now You can go on, and now You can set up Your Ubuntu PC!
FYI:
When You have not got a keyboard-dock, Connect Your tablet with Your pc and enter the adb shell
When You don't know how to enter it:
open up Your console, get into the directory of the android-sdk and into the platform-tools.
Then You type:
adb shell
Now You should be in the ADB shell
Now You can type:
DISPLAY=:0 onboard
Then a virtual keyboard should appear on Your tablet and You're ready to go!

Just to create a vocal point, This requires root doesn't it?

Also, is the wifi and stuff working? What's not working?

Mr.Ox said:
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
Click to expand...
Click to collapse
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.

roflcopterofl said:
Just to create a vocal point, This requires root doesn't it?
Click to expand...
Click to collapse
I don't think so, because everything is flashed via nvflash. This way, You can flash a rom without having it rooted, too.
But I'm not quite sure..
moseskim said:
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.
Click to expand...
Click to collapse
Oh, that's a nice one, I haven't seen this yet! Thank You!
asdfuogh said:
Also, is the wifi and stuff working? What's not working?
Click to expand...
Click to collapse
What's working and not You can read in the Q&A Thread, there is written everything, I just tried to explain it a littlebit easier.
The thread is here:
http://forum.xda-developers.com/showthread.php?t=1191141
There You can see what's working, what not, and how to connect to a WiFi network (For me it doesn't work...)

Thank for this, I am itching to try this... Is there any "easy" way to get back to stock honeycomb after i try this ?
(sorry for this stupid question, I do no know much about these things)

In my opinion it's very easy.
On the one hand, run the command
Flash-android.sh
Or
Restore-default.sh
Or your use nvflash to wipe the device and get a normal rom on it.
Sent from my HTC Desire using xda premium

Thanks, I will try this later today then

tombolek said:
Thanks, I will try this later today then
Click to expand...
Click to collapse
Yeah, when You get Your wifi working, please tell me how because mine does not work
Sent from my HTC Desire using xda premium

Hello yesterday i've try to put linux and android on transformer, all work's great but after 5 minut nvidia apx was disconnected because battery load 0%; i work on vmware machine; after I've charged my dock e tablet and run again the script but that's is the result
sudo sh '/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh'
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 2: /ubuntu/abootimg-i386: not found
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 3: /nvflash: not found
rm: impossibile rimuovere "linux.img": File o directory non esistente
why?
I've already tryed to restore with nvflash all partition and download all in new virtual hdd but not work.

Android 4.0.1 ICS Virtual Machine available for donwload

Updated on Aug-19-2012:
Download link: (4.0.4_r1.1)
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
we have built a virtual machine from the latest Android ICS 4.0.1 source code, Ice Cream Sandwich. You can download it free from our site.
It's created for virtualbox and vmlite, but can be converted to vmware format.
Unique features:
(1) mouse integration with host, no more mouse trapping
(2) shared folders
(3) auto mount sdcard
This is the full readme:
/////////// readme file ////////
VMLite Android 4.0.1 ICS virtual machine instructions
Copyright 2011 VMLite Corporation
1. Setup the virtual machine
(1) Using Winrar or 7zip to extract the zip file to a folder.
(2) Start VMLite Workstation 4.2 beta or VirtualBox v4, then go to menu Machine > Add, select Android-v4.vbox file to add the vm, you should be able to then
start the virtual machine.
(3) if (2) is not working for you, you can create a new virtual machine using Machine > New VM... menu, choose Linux 2.6 as guest os, add the two vdi files using
IDE controller to the vm. Android-4.vdi as Master, and sdcard.vdi as slave.
2. Using the virtual machine
(1) Drag the lock using the mouse to enter the Android screen.
(2) sdcard is now automatically mounted, if for some reason that it does not work well, you can do it manually as follows:
open a command prompt, and enter these commands: (adb.exe is included in the zip file)
adb connect localhost
adb shell
mount -t vfat /dev/block/sdb /mnt/sdcard
after the above, you should be able to use the sd card, which has 8G size.
If you can't connect using adb, and you are using NAT as network adapter, you need to run the following command:
VBoxManage modifyvm Android-v4 --natpf1 adb,tcp,*,5555,*,5555
If you are using bridged network adpater, you need to use the ip address of your vm to connect, e.g.
adb connect 192.168.1.10
If you have problems connecting to the vm, execute the following commands:
adb kill-server
adb shell
(3) Use shared folders to copy files between vm and host. This build includes shared folders additions, you can use the following commands to mount
the share.
adb kill-server
adb shell
mkdir /mnt/sdcard/c_drive
mount.vboxsf c_drive /mnt/sdcard/c_drive
ls /mnt/sdcard/c_drive
assume you have added a shared folder to the vm named as c_drive. You can ignore the error message from mount.vboxsf.

will continue to add more full screen, dynamic display resolution, emulations, such as GPS, Camera, remoting, etc.
We are determined to make it the best android vm and virtual phone you can even find.
We will also make it to boot a physical pc using the same virtual disk file via our unique VBoot technology, so same file can run as virtual as well as physical.

And what would be your website?

google "android v4 vm download", as I still can't post external links here.
refer to readme inside .7z for more instructions
100k download over last week after release.

I found the link:
http://www.vmlite.com/vmlite/Android-v4.7z
Some pics:
http://www.sevenforums.com/attachme...oid-v4-vm-available-download-android-v4-1.png
http://www.sevenforums.com/attachme...oid-v4-vm-available-download-android-v4-2.png
I will try it soon.

having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button

huisinro said:
google "android v4 vm download", as I still can't post external links here.
refer to readme inside .7z for more instructions
100k download over last week after release.
Click to expand...
Click to collapse
let me have a try!

yes, it's a bug we are fixing. the mouse moves inside 800x600 while display is 1024x768.
if you see this, try to reboot the vm.
if still like this, you can then disable mouse integration from menu.
elspanish88 said:
having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button
Click to expand...
Click to collapse

Android 4.0.1 ICS questions
Hi,
I do hope someone can assist me. I downloaded the .7z file, extracted and mounted the .vbox in VirtualBox v4.1.8. All good, it booted up perfectly but problems that arose are as follows:
1: no matter WHAT configuration I choose for networking I simply cannot get the VM to browse any webpages or even to see that there is a network connection. I do see briefly in the bootup that eth0 is loading though, so not sure where to look now as I cannot use ALT-F1 to get to a root shell to do a netcfg to diagnose. When booting the network indicator on the status bar of VBox shows activity, also once it is up and running but no internet access whatsoever.
2: I have noticed I cannot change the time, it defaults to whatever it was when it booted up, that is if the time says 13:20 when it booted up, I cannot change the hour to anything else. if I click set, it just reverts back to 13: or whichever hour digit was there before. Also, clock does not seem to run in this VM. Both the desktop clock and the digital clock on the status bar of Android stay at whatever time it was when it booted up, say 14:20. that is where it will stay, it never updates/moves/keeps time. In the settings page, it seems to be keeping time however.
If there is anyone who can assist me with these issues I would be most grateful.
Thanks in advance,
Mark.

i get an error at boot...
Code:
init: Timed out waiting for /dev/.cp;dboot_done
Kernel panic - not syncing : Attempted to kill init!
atkbd.c: Spurious ACK is isa 0060/serio0.Some programmight be trying to access hardware directly.

Is there any way to install more Apps?
Have send me one per mail but no way to install...

It works, but internet is only in the browser. And it still says that wifi isn't working.
By the way, I'm missing the market thats available in other android4.0 versions for X86:
http://code.google.com/p/android-x86/downloads/list
But these versions don't have internet at all, unless your doing some tricks that are explained here:
http://nil.uniza.sk/linux-howto/android-40-virtualbox-networking-issues
But keep on the good working

This is great! The only problem i am having is there is no Wifi avaiable. Also, if i may ask, how can i download apps to it? I have the apk files of the apps so i dont need a market either thanks!

sgtfoo said:
i get an error at boot...
Code:
init: Timed out waiting for /dev/.cp;dboot_done
Kernel panic - not syncing : Attempted to kill init!
atkbd.c: Spurious ACK is isa 0060/serio0.Some programmight be trying to access hardware directly.
Click to expand...
Click to collapse
Have you had any luck figuring out what was causing this? I'm having the same problem. I've tried different chipset, processor, and acceleration settings. None of which have worked.

Mouse Integration Fix!
elspanish88 said:
having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button
Click to expand...
Click to collapse
Hello, elspanish88! Two ways to fix this problem.
1. Double click on VirtualBOX and start your vm, then when you are logged on to Android, click on machine, at the top left corner, then click Disable Mouse Integration. Then you can move freely, around the screen.
2. The easy easy easy way! Type (Right Ctrl+I) .. there you have it!
Cheers,
ConnorTheHelpa!

This vm is updated to 4.0.4_r1 version, available here:
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
Our vmlite vm is very popular, more than 1 million downloads over last few months.
The latest Jelly Bean version, v4.1.1_r4 is being build, will release a vm when ready.

huisinro said:
This vm is updated to 4.0.4_r1 version, available here:
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
Our vmlite vm is very popular, more than 1 million downloads over last few months.
The latest Jelly Bean version, v4.1.1_r4 is being build, will release a vm when ready.
Click to expand...
Click to collapse
I have a noob dbt. Whts special in it than the original android avds??
send from Gods Own Country........

emulators are too slow, not for real work.
vm is 10x faster.

this is awesome, now i can have a real test environment rather than a test phone! kudos!

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows

The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.​ ​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

Will try thanks
Sent from my KFTT using xda premium

You, sir, are a wizard... Thanks for putting this together!
Sent from Hell™

Sorry, but I don't see a link for KFHD 7" package. Did I miss somthing?
Rootplus KF 7 is for Kindle Fire HD 7"?
Droid DNA

I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >

zuke66 said:
I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >
Click to expand...
Click to collapse
For now, use the restore option to restore the partitions that were saved when you chose the option to install the bootloader hack and TWRP.
In the meantime, I need to know what software version you're using, and whether or not you have edited your build.prop. Also, after you restore your system, use adb to access the shell and list the contents of your /system/etc directory and post it here.
Code:
adb shell su -c "ls /system/etc"

When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app

zuke66 said:
When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Okay, a few questions...
Do you have normal use of the device? Does it boot normally? Have you rebooted yet (if not, don't)
You still haven't told me what software version you are running or whether or not you've edited your build.prop...
What Linux distro/version are you using?
Is your Linux install a full install, LiveUSB, or VM?
Is it 32 or 64 bit?
Are you using a USB 3.0 port?
Do you have a factory cable?
What is the output of the following command?:
Code:
sudo cat /etc/udev/rules.d/51-android.rules

Thanks dude I got adb working plus with the old soupkit revived my kindle fire 1st gen
Sent from my KFTT using xda premium

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

3-16-2013: Fixed issue with permissions on the rootplus script

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.

Hello, I'm stuck at step 6. Until "installing stack" it works fine, but than came some "not a directory" Alerts. See here:
http://pastebin.com/3rk4Vksh
Even setting it manualy with a rebooter-app in fastboot mode dosn't works, because it was not listed.
My System: Linux Mint 14 Cinnamon 64 bit (regular install). I dosn't have a fastboot cable yet, but the rebooter app. I think this is the point. The tool want to reboot it into fastboot, but it wants to boot normally.
Edit: I testet my fastboot with the instructons fron the 2nd bootloader tread and it works. But I have to boot normally and than rebooting it from the app into fastboot mode.

When did you download this? The most recent version installs the 2nd bootloader through the shell, not fastboot. And was your device rooted before trying to install the 2nd bootloader?
[Edit:] I think I see what the problem might be. Download this copy of the RootPlus script, place it in your ~/bin/SoupKit/files folder and replace the one that's already there. Let me know if that makes a difference and I'll upload an updated version.

It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Edit: it was succsessfull ^^

Panixy said:
It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Click to expand...
Click to collapse
Renaming install-recovery.sh to install-recovery.sh.bak is a necessary part of the recovery install. Why your tmp directory was renamed, I couldn't say. I'm looking at the script now and I don't see anything of the sort. I'll keep looking at it to see if anything stands out at me.

Thanks for this. I have a friend is no friend to linux, but I am. I read some other posts about rooting a kindle on software 7.30. Is this possible, or no? It's weird because people are successful to obtain root, but in post #2, it says that it will not work. just need to know so i can tell him.
either way, thank you for all the work that you do

[tut]complete guide on installing linux on android [dual boot]

So , Hello everyone,
It will not remove or harm Android, it will just run Linux on top of android
This tutorial will guide you through installing Linux on mmx a116 with android side by side..
What is this all about?/Why put this on my device?
This projects aim is to bring a range of linux distros to your android device through a method known as 'chroot', see it has running a linux distro within a virtual machine on your phone (Although its not! its using native ARM ports and the Android kernel) . You can access this virtual machine and run it on your phone without causing any damage to your device, or having to overwrite anything. Why might you want this? well my apps are designed to make the install and set up process as easy as possible while still giving you some flexibility. Once you have the distro up and running then you can pretty much run and install any linux software you like (so long as there is a arm port or it is not architecturally dependent).
Wait this uses VNC why shouldn't I just VNC to a computer?
VNC is used to access the GUI as at the moment I have not yet implemented a native way of viewing the GUI. But the Linux distro itself is running within the phone and can be controlled via the terminal app so if your a seasoned Linux user you may never even want to use the GUI
What is Chroot?/How does this work?
"A chroot on Unix operating systems is an operation that changes the apparent root directory for the current running process and its children" - http://en.wikipedia.org/wiki/Chroot
This method of running linux distros with android has been around for some time. I have worked on my scripts to make the process more user friendly and give you far more options from the word go.
The scripts start by mounting the linux image file within the android file system and then mounts the sdcard and if you have it internal memory within the linux file system.
Chroot is then used to change the root directory to that of the mounted linux and a bash shell is then opened to allow you to control linux this is kind of like 'booting' the OS.
The likes of VNC and SSH are then set up when linux is 'booted' to allow you to connect to the GUI if you require it.
Note: This requires a lot of free space on sd cards(any)..atleast 2 GB ..
INSTRUCTIONS:
1-Go to play store and download 'Complete Linux Installer' and install it ..
2-if you have a custom or other kernel , you have to check wether it supports loop or not.So better be on Stock Kernel.
3- Now there are 2 ways to install and run distros(eg-linux,backtrack).One is easier but requires an internet connection on the phone.other is a bit difficult but can be done from PC also .
method 1 ( internet on smartphone )
Go to complete Linux Installer and select install guides and select the distro you want it will download and guide you further.(in the unzipping step , i recommend using a PC for it as its too slow on the phone.)
Method 2 ( using a PC )
Download the version and size of your preferable ubuntu from here -
http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/
After that, download androidVNC and terminal emulator from play store
now extract ubuntu.zip and place it in a folder called ubuntu on root of your SD card.Now you are ready to boot too ubuntu. select the launch menu from complete linux installer.
you will be redirected to terminal emulator . press n if you are asked to check boot.img from md5 as it gets stuck there. set screen size to 1280x720 after few seconds you will see a message [email protected] . this means you are succesful.
go to android vnc type in port option 5900 and password and username as ubuntu an color settings as 24 bit..
congratulations! you have booted to Ubuntu!:highfive:

Hmmmm.
That's not dual boot.:sly:
It runs Linux in VM.
Thanks!
-Dracula

And i don't see why anyone would want to do this, it's just killing your phone by overloading it with a Desktop OS in a VM!

Also perhaps providing credit to the person that did all the hard work might be a good idea .......
Oh and its not a VM guys, it uses chroot which means native ARM linux running with the Android kernel, within Android.

[GUIDE] Odin on Linux [VirtualBox]

Odin 3 running inside VirtualBox on PureOS, a Debian-based Linux distribution:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" and "Solutions to common problems" sections.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install" or something similar,
Install according to onscreen instructions,
NOTE: if you don't have an app like "Software Install", you can either install the downloaded file manually - How to install .deb, How to install a .rpm; or try to install VirtualBox with a package manager such as apt, synaptic, etc. However, VirtualBox may not be included with your distribution and it probably will not be the newest version. In either case, skip the above four steps.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
NOTE: If Microsoft gives you an error like: "We are unable to complete your request at this time. Some users, entities and locations are banned from using this service..." when you are using a VPN, then just start the download on a normal network, pause the download, switch to your VPN, and then continue - It worked for me!
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change the host-name to "Windows",
NOTE: You will need to remember your password, because even though you don't have to enter it every time, you will be required to change it every month, which requires your current password.
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to whatever meets your requirements (Just remember that Windows needs 20GB, Samsung firmware needs ~17 GB (You can store it on a USB drive though), and that the virtual drive does take up space on your computer),
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following (this unloads the "cdc_acm" module, which can be re-added by running "insmod cdc_acm"):
Bash:
sudo rmmod cdc_acm
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, click on the Windows logo in the bottom right, and then click on the power icon.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here. NOTE: If the VM is off, everything you plug in will open on the host OS, regardless of filters.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer from the Linux host onto the drive, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
Solutions to common problems:
If Odin is unable to see your device after following this tutorial try to unplug as many USB devices as you can from your computer (except your phone) and restart Odin.
If you encounter a "Kernel driver not installed" error when installing VirtualBox, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have any problems and/or questions, let me know.
Hope this helps!

@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.

bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.

ethical_haquer said:
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.
Click to expand...
Click to collapse
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?

bmwdroid said:
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?
Click to expand...
Click to collapse
No, the virtual machine is stored on it's own virtual disk on the drive. I have shut down my computer many times, and the VM still runs fine.

bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
Let me know how it goes when you do it.

Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?

Pierro29 said:
Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?
Click to expand...
Click to collapse
You can use more than one CPU if you'd like, see here, but sometimes people have problems setting it up, and you don't really need more than one CPU if you're just using the VM for flashing. That's why I didn't include it in this tutorial. If you want more than one CPU to be used, feel free to though. Let me know if you encounter any issues when following the directions.

ethical_haquer said:
Let me know how it goes when you do it.
Click to expand...
Click to collapse
I will but didn't have the necessity yet.
Realized although that I may have to get another key from somewhere.

bmwdroid said:
Realized although that I may have to get another key from somewhere.
Click to expand...
Click to collapse
What key?

ethical_haquer said:
What key?
Click to expand...
Click to collapse
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.

bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
Activation is mandatory for this method ?
Another question, Odin V3.14.4 is better? or is it safer to stay with V3.13.1 ?
Thanks

Pierro29 said:
Activation is mandatory for this method ?
Click to expand...
Click to collapse
No, I think @bmwdroid is talking about something with his phone.

ethical_haquer said:
No, I think @bmwdroid is talking about something with his phone.
Click to expand...
Click to collapse
I meant the Windows key

bmwdroid said:
I meant the Windows key
Click to expand...
Click to collapse
What Windows key? I can head over to the Windows website I linked to and download it without any key.

bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
You can use a KMS activator. Free and easy

ethical_haquer said:
What Windows key? I can head over to the Windows website I linked to and download it without any key.
Click to expand...
Click to collapse
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>

bmwdroid said:
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>
Click to expand...
Click to collapse
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.

ethical_haquer said:
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.
Click to expand...
Click to collapse
You do not need a product key to use Windows 10. I think you can skip the product key prompt.

ethical_haquer said:
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" section.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install", or something similar,
Install according to onscreen instructions,
# Note: if you don't have an app like "Software Install", you can skip the above steps and try to install VirtualBox with a package manager such as apt, synaptic, ect. However, VirtualBox may not be included with your distribution and it probably will not be the newest version.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change hostname to "Windows",
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to 20GB,
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following:
Bash:
modprobe -r cdc_acm
cd /etc/modprobe.d/
ls
In the output from "ls" there should be one file, named something like "dkms.conf" or "blacklist.conf".
In the terminal, run the following, replacing "yourfilename.conf" with the output of the "ls" command:
Bash:
sudo nano yourfilename.conf
Add the following line to the file:
Code:
blacklist cdc_acm
To safe your changes to the file, hit Ctrl+x, y, and Enter,
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, type "shutdown /s" in the PowerShell.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer to the drive from the Linux host, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
If you have any problems and/or questions, let me know.
Hope this helps!
Click to expand...
Click to collapse
Hello fellow Linux user,
Might I suggest another similar method: QEMU and Libvirt (VirtManager). The only difference is it's lighter and more configurable than Virtualbox. USB passthrough is much simpler to setup in my experience and setup isn't terribly hard. I seem to have an issue with VBOX drivers, so this became my workaround for anything VM related.
You can install using the following commands:
DEBIAN:
sudo apt update && sudo apt install qemu virt-manager
ARCH:
sudo pacman -Syu qemu-full virt-manager
FEDORA:
sudo dnf update && sudo dnf install qemu qt-virt-manager
GENTOO:
sudo emerge --ask --verbose app-emulation/qemu virt-manager
Best regards,
D'Tor Aelek of Romulus