[Guide] Debian Kit & Limbo PC Emulator (QEMU x86) for Dual-booting Linux on Android

Search This thread


Senior Member
May 19, 2014
Hate to necropost,but I am stuck at selecting the premade qcow2 image on ShieldTV with version 2.11 armv8 64bit because it only has "Documents" listed which doesn't show the qcow2 file and "None" is the only other option.
I stumbled on a post in Geforce forums in the Shield TV subforum that someone said Limbo was surprisingly fast.

Edit: Found the solution which was to pick "Documents" and select SHIELD on the left pane which shows all file types. DERP

Hope this helps others who get stuck in this way.
Last edited:


Senior Member
Feb 10, 2022
Samsung Galaxy A52s 5G
Hate to necropost,but I am stuck at selecting the premade qcow2 image on ShieldTV with version 2.11 armv8 64bit because it only has "Documents" listed which doesn't show the qcow2 file and "None" is the only other option.
I stumbled on a post in Geforce forums in the Shield TV subforum that someone said Limbo was surprisingly fast.

Edit: Found the solution which was to pick "Documents" and select SHIELD on the left pane which shows all file types. DERP

Hope this helps others who get stuck in this way.
idk, i never got that

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    [Guide] Debian Kit & Limbo PC Emulator (QEMU x86) for Dual-booting Linux on Android

    Note to mobile readers: view in light mode with XDA app (settings, near the top), view online with a browser (press menu and view online), or download google drive from the marketplace and follow the link to the main document in this guide, you should be prompted what to open that link with, choose google drive and you'll be greeted by an very friendly formatted and constantly updated guide. You can also check a box within the google drive app that allows you to view offline... and on with the show.Legend/Key/Guide for Guide
    Yep that's happening. This is designed to avoid most questions about the excessive use of colour coding throughout the guide.
    Orange text=
    chapter titles & section titles.
    Yellow text=
    things that are partly under construction but complete enough to be used with caution
    Red text=
    under construction and for education purposes only when used in the table of contents
    Red text=
    example command that should be modified based on system that you are running on before being used
    Green text=
    complete aside from a missed or stray preposition.
    Cyan text=
    text that can be copy/pasted into a terminal without any modification except for 2 cases

    • Cyan_text&Red_text=the red text should be modified for your system before use
    • # and $ should be ignored when copying as that symbol will already be on your terminal
    Blue text=examples of what your terminal will output when using a supplied command. This is contextual to the guide and I try to include the command once in the document and a second time near the top of the dump.
    Blue text=
    when used in table of contents denotes things that likely are completely aside from making additions and are low on the priority list to update for the author of this guide.
    Grey text=
    are full dumps of what a command should output and do without errors. These dumps have a reference pointer at the beginning of each so that you may find where in the guide they their relevant to
    Pink text=
    when used in the table of contents this is to show what sections are completely new.
    Note to mobile readers: view in light mode with XDA app (settings, near the top), view online with a browser (press menu and view online), or download Google drive from the marketplace and follow the link to the main document in this guide, you should be prompted what to open that link with, choose Google drive and you'll be greeted by an very friendly formatted and constantly updated guide. You can also check a box within the google drive app that allows you to view offline... and on with the show.

    Link to Full Guide on google docs:


    Link back to XDA thread


    Public Editable doc


    [Guide] Debian Kit & Limbo PC Emulator (QEMU x86) for Dual-booting and more
    Draft2 Linux android multi-node cloud computer tutorial.
    1.Setting up base system(functional/\under construction)
    1:1 Updates (05202013) XDA Sync happening 8:30pm- added subsection 5:10. added descriptors to section 4:4:* Added/Completed two new mini guide to section 1:5:1:*{{XDA content sync happened 05182013} google document sync will happen after some time}
    1:2 - Downloads for android device (functional)
    1:3 - Installing Linux system to Android Device (functional)
    1:3:1 Verify no major errors are present (functional)
    1:3:2 Start ConnectBot (functional)
    1:4 Manual install (functionally complete/partially under construction)
    1:5 Other methods of running Linux alongside Android (All sub sections Under Construction)
    1:5:1 Using Limbo PC Emulator (QEMU)
    1:5:1:1 Apps & Files to download for QEMU
    1:5:1:2 QEMU Linux Install Guide
    1:5:1:3 QEMU Linux Setup Guide(new)(functional)
    1:5:1:2-1 Method one: Install to virtual hard drive with QEMU(new)(functional)
    1:5:1:2-2 Method two: use a computer to make a virtual install(new)(functional)
    1:5:1:4 QEMU Integrating with the rest of Main guide
    1:5:1:5 QEMU tips and tricks
    1:5:2 Using Complete Linux Installer
    1:5:2:1 Apps & Files to download for Complete Linux Installer
    1:5:2:2 Complete Linux Installer Installer Guide
    1:5:2:3 Complete Linux Installer Setup Guide
    1:5:2:4 Complete Linux Installer Integrating with the rest of this guide
    1:5:2:5 Complete Linux Installer tips and tricks
    2:1 installing packages before devstack or openstack (Under Construction)
    3. Setting up cloud system(Under Construction)
    4:0 Sites that have been exceptionally (updates contently)
    4:1 apps for android that make things easier (functional)
    4:2 linux software and or packages that I've tested (under construction)
    4:3 commands for apt-get and others I've found useful (functional)
    4:3:0 Android command line commands (new)
    4:3:1 Apt-get commands (functional)
    4:3:2 Command line commands for linux (functional)
    4:3:3 Connectbot optimization guide (functional)(newly modified)
    4:3:3-1. Linux Boot/Mount automation (newly modified)
    4:3:3-2 Linux Un-mount/Kill automation (newly modified)
    4:3:3-3. Connectbot “Local” SSH setup (newly modified)
    4:3:3-4. Other good combos to use after using 'linuxBoot’ (newly modified)
    4:3:4 Remote RDP debian kit guide (functional)
    4:4 Rom Tool Box user Tips (brand new and no where else)
    4:4:1 Scripts (new content)
    4:4:2 Performance Mods (under construction)
    4:4:3 General guidelines (under construction)
    4:4:4 Useful tips (under construction)
    5.Debugging\Known issues with solutions(Constant Construction:Completion Relative)
    5:1 debian install problems
    5:2 debian manual install issues
    5:3 additional packages problems
    5:4 reinstallation problems
    5:5 How do I solve [My device/linux] issue(s)?(functional)
    5:6 How to do a dump like the author?(functional)
    5:7 Can I use this to completely replace my Android OS(new/\functional)
    5:8 How do I add repositories to Debian?(new/under construction)
    6:1 Introduction
    6:2 Disclaimer
    6:3 Note to forum Moderator
    6:4 Statement of long term goal for this project
    6:5 Distillation of current project completion
    7:1 Connection Methods(under construction)(Mini-intro added)
    7:1:1 Connecting locally
    7:1:2-2.1 Connecting wirelessly through wifi(functional)
    7:1:2-2.2 Remote RDP in from a second computer (New)(functional)
    7:1:3 Connecting wirelessly through bluetooth(Mini-intro added)
    7:1:4 Connecting wirelessly through data network
    7:1:5 Connecting wirelessly through atana directly
    7:1:6 Connecting through USB with computer
    7:1:7 Connecting through USB with USB host mode
    7:1:8 Connecting through visible light spectrum
    7:1:9 Connecting though invisible light spectrum(New links added)
    7:1:10 Connecting though directed/focused light
    7:1:11 Connecting through audible sound
    7:1:12 Connecting though inaudible sound
    7:2 Customization of GUI(under construction)
    7:2:1 Saving Electrons(functional)
    7:2:2 Making it Pretty(functional)
    7:3 Making things happen without excessive user input(under construction)
    7:4 Methods of installing or unpacking(under construction)(New)
    7:4-4. Installing from sources.(functional)(New)
    7:4-4.1 Unpacking tar.gz files(functional)(New)
    7:4-4.2 Installing Java for ARM from source(functional)(New)
    7:4-4.3 Adding Commands to Bash(functional)(New)
    7:4:4.1- Installing Map Tools(under construction)(New)
    7:4:4:2 Solved Installing jMonkey on Android(functional)(New)

    8.Sources of information and content(functional, nearly up to date)
    8:2 Dumps I’ve taken and Pictures worth sharing (under construction)
    8:2:1 example: installation without errors (complete)
    8:2:2 Example of running fdisk -l (complete)
    8:2:3 Example of running mk-debian (complete)
    8:2:4 Example of the first time you run deb command (complete)

    1:1 Updates

    Here I’ll try to keep you up to date with where I am with this project. (Date) in the table of contents reflects the last time that I made a significant update to this guide. {notes} in the table of contents states the nature of the update, if the change is significant it will be referenced here so that you may find the modifications to the guide quicker.
    UPDATES APPENDED: see Main Doc for full list of all updates.

    05182013- manual install of java has issues with running '.jar' files from the command line, there seems to be another version or method to try or it may be a matter of downloading and applying new libraries to the java install itself, I'll be trying bothe (first the lib or dependency search) but will also end up doing a reinstall of the entire debian os again. Installing from source packages is very use at your own risk and running ontop of a rooted android which you've already been warned is use at your own risk; seems like it be risky, yep, but I've yet to re-root my device for what feels like 2 months (I tell you this because I believe the install instructions to be nearly complete and completely reliable) installing things after that seems hit and miss but so long as you're not foolish much of this guide elsewhere is safer than instructions found elsewhere.
    Did some polishing of section 7 and added usefull links that I hinted in the past.
    Moved section 6:6 Legend/Key/Guide for Guide to the top of the guide, mostly so I can keep the formatting consistent without loading back and forth between sections. Going to Update the XDA forum posts tonight, Google to google sync still pending...
    05192013- Added some links to section 4. The commands in section 7 with red text in only one spot cannot be trusted and the commands right now are suspect right now, they'll be updated as I figure out what's wrong and this statement will be struck though. Java support with development tools and install instructions not far off now...in unrelated news, added new sections 1:5:* & 4:4:*, these right now are place holders for what is to come in the future, I'll be focused on the Java thing that's a bit weird on my system and wrapping up the install from source as well, just bouncing round the other places we'll go. Added new section with a little content; 4:3:0 Android command line commands, I'll be adding more as eventually I'd like to have linux tell android what to do and android to be able to do the same.
    05202013- added new subsection to section 5:10 to help update answers to questions received through XDA. Added a bit of content to sections 4:4:* mostly intor fluff so I don't forget where I was going. Did some work for money so new content is still pending for the guide, will likely end up with more time tomorrow...
    05212013- currently adding some content to 1:5:1, just couldn’t leave it alone added a bunch of content to that section... think I can call the two new guides functional for Limbo QEMU Linux Installation, comments welcome if it barfs on your device... so yeah made/completed a new section “7:4:4:2 Installing jMonkey” you can now install and run jMonkey naively on Android using Debian Kit and openjdk packages installed on your rooted phone or tablet, using directions in section ‘7:1:2-2.2 Remote RDP in from a second computer’ you can connect into it and develop on your Android device but with the full keyboard experience, then if ya need to go on the go you can save your work and reconnect locally on the device with directions from section ‘4:3:4 Remote RDP debian kit guide’ and continue your development project anywhere you’ve got time :) hope this helps game makers and app developers as this program outputs in formats that can then be run on the android side with full graphical bliss ... back to work on java compatibility?, looks like I might have to re-install Debian as I've mucked around in the system in a bad way :p but that's what the guide is for and I'll be working almost all day on the guide, check back often as content will be flowing in. XDA postings updated today 05212013 sorta, the character limit on XDA is now a limiting factor, I will split the document between posts for now and work on making the sections in the Google doc split correctly or something... Updates successful to all educational postings on XDA thread, google drive internal sync still pending but I've been at this for 14 hours or so today so I’ll be off my computer for a little while to let it cool down.
    06122013- Section 3 nearly completed, script runs for installing cloud services to android but returns a few errors and is ready for others to test with me, send a PM, e-mail, Google+, what ever and I'll hook you (the reader) up with a preview of the draft script that I've been writing to install openstack to android. Still under heavy development and re-writing but should work now, I'll be posting the beta version publicly when I've done enough testing or had enough testers confirm that it works without problems.

    ____Update: Bellow Link
    ____ https://docs.google.com/document/d/1A64GMgcVUKbZrTG2WDWfY_g9vABuRx78ULULu-Ir-kE/edit?usp=sharing
    ____is a script to be tested for controlling the Crazyflie Quad-Copter with Android using Debian Kit's Squeeze or others
    ____for now see Page 10 for the discussion related to this development.
    ____if found to work, then merging into the Main Guide and full description on how to get started will be included as well.
    1:5 Other methods of running Linux alongside Android

    _______SPLIT FOR POSTINGS______

    1:5 Other methods of running Linux alongside Android
    These sections that follow ( 1:5:* ) will detail the other methods the author has installed Linux Environment.
    Note: at this point I've only one device that is capable of developing a guide to install and integrate cloud services; if you wish to see that change you may make additions on the publicly editable version of this document, or, research it on your own time, or, make a donation to the author; my time can be purchased ;), or, wait for me to document it in my own time.
    1:5:1 Using Limbo PC Emulator (QEMU)
    Note: I did not originally include this method as it is a slower way to run linux on android. Its good but emulation always comes at a cost. There are many devices on the market now that will support this app smoothly but like I've said you'll still see a cost.
    Note: run-on list of “Cost”
    Slow: The nature of emulation causes this. To understand the details of this one will have to delve into some of the details of how machines talk to one another and within themselves, machine language(s), and, the details of what a processor actually does.
    I’ll try to sum it up though; a processor type (CPU - ARM/Pentium/AMD and even GPU - Nvidia, iSBX 275, S3 89C911) has a specific structure in how the components and pathways are laid out. This causes each manufacturer to have their own way of sending electrons across the internal structure that makes up the processor, this is usually kept private or proprietary (Xbox, Playstation, Nintendo are good examples of this) to the manufacture, which is the machine language that I was talking about. Compatibility with the other components that the processor connects to is usually achieved by standardization of “shape” meaning the little wires that come off of CPU chip itself and connect to the rest of the circuit board, and the internal firmware of the CPU chip.
    To make a processor process a “native” task one must be speaking its language or a language that it understands (many come with what’s called ‘channels’ that handle; Flash, Java, or other human readable programming language) and tell it where to get information and how to handle it and where to send it and what to do next and have all that on the “native” hardware. To make a processor process a “alien” task one must have a way of translating all the processor’s calls for data and handling of data to a completely different set of physical pathways and methods of handling data; this would be like if you and I were placed in completely different parts of the same city and were given the exact same set of instructions (north 5 kilometers, east 12 meters, south east 1 kilometers) and be expected to arrive at the same location; just doesn’t compute, you would end up in a location relative to your start point just as I would but the relative distance wouldn’t change between us. And more than likely one of us would run into an obstacle not far from the start and where we programs and not humans the one of us to hit an obstacle would, like a lemming, just keep failing until killed off.
    An emulator bridges the language and hardware divide (visual here: like an octopus wriggling through a small hole when viewed through x ray photography) by wrapping up the data being handled in such a way that another processor doesn’t try to natively run the data being wrapped up (visual here: like the internal organs, of the before mentioned imaginary octopus, not rupturing through the skin and spilling out into the water that it’s entire body is encapsulated in) and then giving the data within a way to communicate with other data that has been wrapped up.
    It's not an exact description of emulation but an analogy and how I think about it.

    Electron Expensive: The very act of emulation causes the processor that is running the emulation to pull double duty. For every task that has to be carried out by the emulated machine. a task must first be started on the host machine, then the emulated task is started, then the emulated task makes a call for more data or tries to write data, that emulated task ‘call for more’ is sent back to the host machine, the host machine then must make the required translations to compute the request, after computing the request the task is performed, if the task being performed makes ‘calls for more’ then those are then handled just like the parent task (making more calls and translations back and forth) and so on. When done coded properly; emulators can emulate a processor very near the host’s megahertz level and the emulated tasks show very little lag from all this back and forth that the data must first go through, however, due to the closed source nature of hardware and internal firmware, making a well coded emulator is very difficult and usually involves trial and error combined with a little reverse engineering. In most cases when running an emulator, you’ll want a host machine capable of much greater megahertz range than the machine you are trying to emulate (it’s why next gen console emulation is so difficult for most home PC’s) to allow for the back and forth that happens with emulation. This back and forth that the data goes through is what will cost you in battery life because data is transmitted with electricity and there is a finite amount that your battery will store and output.
    Hair Puller: As wonderful as it can be to run emulators; eventually things just go wrong and debugging how to work around it can be an exercise in futility.

    Note: run-on list of “Benefits”
    Extended Compatibility: Being able to run non-native machine code and system tasks gives an enormous amount of flexibility to the host machine. With QEMU you can even emulate the old floppy disk drives on Android and I doubt most households have a fiscal one of those anymore.
    Development Options: Emulating hardware allows for development to take place on a set of hardware that doesn’t need to be physically owned thus reducing the cost of development to time, education, and workforce.
    Hardware Virtualization:Because the operating system is running on virtualized hardware you are more free to convert the image file that the OS is saved to and run on multiple devices or computers with very little work once you’ve got an installed OS image. I’ve even seen work done to sync system files between clones so that one can login to each clone and after a few minutes have the exact same programs to access and run between devices.
    Games:Yep you can play games with this, like mine sweeper and other low memory intensive games, but further development and a faster device will alow for many more titles to be added to the list of “working and fun” that I’ll be compiling here.

    1:5:1:1 Apps & Files to download for QEMU
    Limbo from the Google Marketplace
    Limbo in my opinion is of the one of the best apps out there for novice on up to master rooted phone users. In short its like a "game console" emulator for your pc only with a big twist the "game console" Limbo emulates is actually normal PC processors like a pentium 3 and it runs on android so you can play pc hardware dependent content such as windows if you've got the specs on the go.

    Pick A Linux Distribution
    The links provided are here for convenience and should be considered untested unless accompanied by a statement that it has worked on android. I will try to test as many as possible and document the; pros and cons; methods of installation if they varied from the main QEMU install guide provided in this main guide.

    DSL (Damn Small Linux)

    Worked for me on my Epic 4Gs

    Ubuntu (12.04)

    Kali (like backtrack)
    There is a live boot ISO for PC, a ARM variant that’s being tested by others, and a network install that I’ve found. For this method (QEMU) I would suggest the PC version; I’ll be testing the network install in the future so I can attempt a “Debian Kit” port for the ARM native version of their distribution.


    Just ran across this one. It’s android for PC processors instead of the ARM processor. But QEMU is a PC emulator, so if we want a slow Android OS running on top of the normal one for that could be possible. Don’t know yet if it will work but it’s worth a shot as this would allow developers to mobily develop for this variant of Android and normal root users the chance to make drastic changes to the emulated Android environment without too much fear of fouling up their main Android environment.

    1:5:1:2 QEMU Linux Install Guide
    1:5:1:2-1 Method one: Install to virtual hard drive with QEMU
    1. Download Limbo from the market place
    2. Download a Linux distro to start with or try an ISO that you already have if you're feeling adventurous
    3. Open Limbo
    4. Tap on ‘Load VM’ and choose ‘New’
    5. Name your new Virtual Machine and tap ‘Create’
    6. Scroll down to ‘RAM Memory (MB)’ tap ‘64’ and choose 512
    7. Scroll down to ‘CDROM (*.iso)’ and tap ‘None’
    8. Tap ‘Open’ in the new pop up and using the folder navigation window that pops up; navigate the the ISO file that is on your device (usually in your downloads folder) and tap it
    9. Back in the main Limbo app screen scroll down to ‘Hard Disk A(*.img/*.qcow2)’ and tap ‘None’ and tap new
    10. In the new pop up (Image Name) title your hard disk somthing that will tell you that it’s an emulated hard drive of that distribution, such as ‘DSLhdEmu’ and set a size that you’re willing to sacrifice to running Linux and tap ‘Create’
    11. Scroll down to ‘Boot from Device’ tap ‘Default’ and in the pop up choose ‘CD Rom’
    12. Scroll down to ‘Network Configuration’ and tap ‘None’ and choose ‘User’
    13. Scroll down to ‘VGA Configuration’ tap std and choose ‘vmware’
    14. Scroll up, all the way up, on the Limbo main screen and choose start. If everything goes well you’ll be presented with a linux live boot environment that you can then use to install onto the virtual hard drive that you made. Once you install you can remove the ISO from the parameters in Limb and change the boot order to the virtual hard drive.
    1:5:1:2-2 Method two: use a computer to make a virtual install
    and then converting it to a qcow2 file and install linux to it before moving it over to the device to run it. This is a bit round about but it's my method when I can't run the install but can run the OS due to emulation not being perfect and my device not being powerful enough.
    1. Download and install ‘VertualBox’ to your PC from:
    Note: You’ll want to choose the one that is for your PC’s hardware and operating system
    2. Open ‘Oracle VM VirtualBox Manager’ and click ‘New’
    3. Click ‘Next’ and title it something you’ll remember is for this purpose, such as ‘DSLforQEMU’
    4. Mouse over to ‘Operating System’ and click on ‘Microsoft Windows’ choose ‘Linux’ in the drop down
    5. Mouse over to ‘Version’ and click on ‘Ubuntu’ choose ‘Other Linux’ in the drop down
    6. Mouse over to the ‘Next’ button and click it
    7. Mouse over to the box with ‘256’ click it and input 512; mouse over to next and click it (unless you’re computer has less than 2 gigs of RAM)
    8. Click the ‘Next’ button again because we’re creating a new ‘Start-up Disk’
    9. Mouse over to the ‘VHD (Virtual Hard Disk)’ and click the little circle next to it to select that option and mouse over to the ‘Next’ button and click it
    10. Click the ‘Next’ button again unless you really want a ‘Fixed size’ image taking up a bunch of space or if you’ve had issues with ‘Dynamically allocated’ option not converting to qcow2 format properly.
    11. This next page titled ‘Virtual disk file location and size’ you’ll want to set up yourself based on how much space your hard drive has and how much space your Android device has. I shrank mine down to 3 gigs though and left everything else alone.
    12. Mouse over to the ‘Next’ button and click it then ensure everything looks ok and click the ‘Create’ button too. If there is a second window behind that go ahead and click the ‘Next’ and ‘Create’ buttons too to set up the virtual machine
    13. Mouse over to the new virtual machine that you’ve created and ‘right click’ it and select settings or select the new virtual machine and select the ‘Settings’ button which should be between the ‘New’ and ‘Start’ buttons
    14. In the new ‘Settings’ window, you’ll find oodles of things to tweak and feel free at a latter time, for now mouse over to the ‘Storage’ and click it
    15. In the storage settings mouse over to the ‘Storage Tree’ part of the window and look for a disk icon that says ‘Empty’ and select it (this is the virtual machine's CD drive)
    14. With the virtual CD drive selected mouse over to the ‘Attributes’ part of the window and select the checkbox to enable ‘Live CD/DVD’, mouse over to the disk icon just to the right and a little above the checkbox and click it to set up where the ISO is for installing Linux, select ‘Choose a virtual CD/DVD file...’
    15. Use the new window titled ‘Choose a virtual CD/DVD file’ to navigate and select the ISO file that you wish to use to install Linux to the virtual hard drive image that was created in step 11
    16. Mouse over to the ‘Open’ button and click it then click the ‘Ok’ button in the ‘Settings’ window that was behind it.
    17. Back in the main window for VirtualBox titled ‘Oracle VM VirtualBox Manager’ ensure that the virtual machine that we’ve been making is still selected and then mouse over to the ‘Start’ button and click it.
    18. Interrupt the boot with one of the function buttons on your keyboard when the new window pops up and starts to paint in what will look like a computer starting up in a window (usually ‘F2’ or ‘F10’ or ‘F12’)
    19. In the interrupted boot menu within the “VM” window choose the option that corresponds with the CD drive to make the virtual machine boot from CD this time around only
    20. Let the live boot process process for a bit and eventually you should be presented with a window that looks like a linux desktop is inside of it
    21. Follow the instructions for installing your specific distribution to a hard drive and when that guide states to install to a hard drive just remember to be selecting the virtual hard drive that was created in step 11
    22. After installation to the virtual hard drive has finished test that it installed correctly by shutting down the virtual machine and getting back into the settings described in step 15 and “eject or remove or unmount” the linux ISO file from the virtual CD drive
    23. Start the virtual machine again and check that it boots correctly from the virtual hard drive image. If it does shut it down again properly. If it doesn’t try again or try a different distribution.
    24. Open the ‘Settings’ window again and select ‘Storage’ again, this time though under the ‘Storage Tree’ part of the window select the virtual hard drive image (its the *.vdi file that was created in step 11) and mouse over to the disks icon to in the ‘Attributes’ part of the window to the far right of where it says ‘Hard Disk’ and select ‘Choose a virtual hard disk file...’ and make a note of the full folder path to the *.vdi file; somewhere like in a notepad or scrap of paper or memorize it.
    25. Open a terminal window on your PC and convert the *.vdi file to a *.qcow2 file with the following command structure
    Example : Syntax
    # qemu-img convert -O qcow2 *.vdi *.qcow2
    Example : useable
    # cd /home/dev/dumps
    # qemu-img convert -O qcow2 DSLforQEMU.vdi DSLforQEMU.qcow2
    26. Let the converter convert and come back to it after a few minutes
    27. Once the converter has converted it’s time to transfer the qcow2 file to your Android device, use a cable or a SD card adapter to get it over to the folder that Limbo saves virtual hard drive
    28. Start up Limbo and create a new machine much like the steps in method one but you’ll not need to select a ISO file, instead select the virtual hard drive image as the hard drive to boot from and set the other setting the same as method one and start the virtual machine to test it on your Android device.

    Setting up base system (partially under construction)

    1. Setting up base system:

    1:2 - Downloads for android device.






    1:3 - Installing Linux system to Android Device

    1:3:1 Verify no major errors are present

    • Open Debian Kit: check that there are no red X's; tap on anything in the list for more info and/or press menu and tap read me for the developers original doc.
    • Check that you've enough memory: from the home screen press menu and tap settings; Scroll down to application settings, tap it and view storage use; try to have as much available memory as possible by, moving/removing apps, ruffly 100MB+ worked for me. Note after the initial install you should be able to reinstall/restore the removed apps with little ill effect.
    • Remove data consuming tasks from the equation either by freezing them with an app like rom tool box or turning off their sync options or uninstalling them. Mainly this step helps insure that while you're downloading the necessary data that your connection doesn't flip out and cause an error that could have been avoided.

    1:3:2 Start ConnectBot (rom toolbox terminal emulator also works well for this part with some modification)

    • Tap on the lower left corner where ssh button is and select local instead.
    • Tap in the text field next to the bottom now displaying local and type in a nickname like 'debInstall', hit enter and be presented with-

    • Type su, hit enter, and permit superuser permissions.
    $ su

    • Unpack the installer with sh /sdcard/download/debian-kit-* note: if downloaded with dolphin browser or some other browser then you'll need to change the file path to reflect that.
    # sh /sdcard/download/debian-kit-*
    # sh /sdcard/Dolphin_Browser_Mini/download/debian-kit-*
    # sh /mnt/sdcard/download/debian-kit-*
    See 8:2:1 for example of what your screen should look like without errors.

    • Choose your path:

    • Input 2s will install a debian.img file 2gb in size to your sdcard. Note: this option is suggested as for the first try as this will allow for a stable and fairly sized environment to test and play with, furthermore I will be writing this guide first for the debian squeeze option and later add the others as I've the time. If choosing this option scroll down to step 6. when the installer starts asking questions.
    • If 2gb sounds to small and you're willing to brave the manual install, then you'll want to abort the auto installer at this point and scroll further to step 1:2 Manual Install

    • Once the install has finished you'll be given three options yes, ovpn, q choose one and only one. When yes or ovpn is used things will be removed, when q is used the debian image is unmounted just as it will be automatically unmounted at the end of either yes or ovpn option. Note: when I install to debian.img file I choose ovpn as this allows for the most amount of space to be freed.
    • Now providing everything is error free the debian.img can be remounted with either of the two commands
    # deb
    # /data/local/deb/deb
    Note: to see what it will look like the first time you run deb and not encounter errors see section 8:2:4

    • Now to first

    • update the list of packages currently installed,
    • second upgrade everything,
    • third install andromize for compatibility,
    • forth install andromize-lxde for a gui,
    • fifth install ssh,
    • sixth auto remove unnecessary packages,
    • seventh clean up,
    and all that in one step that will take more than a few minutes to complete. Note: andromize at some point is going to request input from you;

    • tap on your screen and tap on the control button that briefly shows up in the lower corner, the hit the 'i' button on either you hard keyboard or onscreen keyboard. This will put you in insert mode so that with a d-pad and the spacebar or enter key you can select a highlighted option, I suggest: ctrl+i then space (or enter) as that has worked everytime for me.
    # apt-get update; apt-get upgrade; apt-get install andromize; apt-get install andromize-lxde; apt-get install openssh-server; apt-get autoremove; apt-get clean

    • So you're set to rock and roll as root and have a lot of options if ya know what you're doing.
    At some point with all this you may feel uncomfortable with running under sudo root user. Scroll down to '4:3:2 Command line commands for linux' and run those commands to secure yourself some.

    • Start your new ssh server. Now that the basic requirements to run linux have been met and you've a clean OS we need a way to 'open and 'close' terminal windows that aren't going to remount the system a bunch or run us into out of memory or space errors.

    • Start ssh with one of the following commands
    # deb s

    • Stop ssh with one of the following commands (when you're done)
    # deb S

    • Once ssh is on you can connect to your device from any other ssh compatible device. For now we are going to use identical directions, almost, to section 4:3:3-3

    • Make or open a new or existing ssh connection with connectbot with your username that you want to log in as then the @ symbol followed by "localhost"
    • Make sure that in the lower corner that the option is set to ssh and hit the enter key

    • Connectbot or whatever local running ssh app you're using (I'll be testing or hearing about a few I'm sure) should now prompt you for a password. Put in the one you (I hope setup before in step 4:3:2... yeah I'm going to have to fix that...) set up and you should be greeted by a few lines of text and a # with your username before it. This is where many of the linux commands should be run.
    Note: this method is prefered because you can connect and disconnect without sending multiple "deb" commands in the local connection that we only should use for installation and starting the system (first boot and after reboots). Sending multiple "deb" commands can cause all sorts of issues without sending "deb u; deb k" commands between. The other issue that arises with sending multiple "deb" commands followed by a "deb u; deb k" is that you can fill folder structures on the linux OS and your SD card that are designed to rescue unintentionally deleted files, cache, and junk files, which in other circumstances is really good to know like when a picture disappears from your gallery, but in this case is a real pain. You'll get all sorts of errors so remember one "deb" command per boot and connect through ssh or remote RDP once your system has mounted linux and you'll have a happier experience. Okay moving on.

    1:4 Manual install

    • Unmount and eject the sd card from your device
    • Plug the sd card into enough adapters to plug it into your computer. I've used micro to sd adapters and then plugged that into yet another adapter sd to usb with success.
    • Backup all data. You're about to delete it all.
    • Using gParted on ubuntu 12.04

    • Ensure that gParted has selected the sdcard and not your hard drive... don't select your hard drive that would be bad.
    • Check out the current partition layout, perhaps even make note of it somewhere incase something goes wrong. My sandisk started out with a 4mb empty zone and a fat32 partition for the rest.
    • Reformat original partition to fat32 by either write clicking the main partition or selecting the partition drop down menu at the top of the window.
    • Resize first first partition (pay close attention to not accidently remove, overwrite, or move over the little bit reserved at the start of your sdcard) to the desired amount of space for the android side of your device such as space for; downloads, app cache, apps to sd, photos, and music. This space is all that my android recognizes by default so think about it.
    • Second make a second partition filling up the trailing bit left over, you can try something fancy but I chose a fat 32 bootable.
    • Apply the three operations with the green checkbox in the upper left quadrant of the window and let it run.
    • When gParted finishes unmount and eject the sd card, wait a second or two and plug it all back into your computer.
    • If you left gParted open then your sdcard and it's partitions should now show up as selectable in the drop down for devices. Close gParted.
    • Open a file browser or two; one for your sd card's first partition and another for where you saved the backup of your sd card's contents.
    • Copy your backups back over to the first partition of your sdcard. I'd advise copying the important things first, app backups folders and system and/or nandroid backups. The things you can live without for a day or two you can come back for because you're here to get to the next step.
    • Unmount and eject from computer. Plug back into phone and remount.

    • Run through the first part of the guide and about when given the option to make a debian.img file.
    Run the following commands in connectbot under superuser to figure out what the installer uses to identify the second partition on your external sdcard, format it and install linux to it.

    • This may show the uuid, drive letter, date modified. Make note of todays date and check for three dates in the list that match from when you were repartitioning. Take note of everything.
    /data/local/deb/armel/busybox fdisk -l /dev/block/vold/*
    Results may vary try navigation to /dev/ with a root browser on the android side of things, take a look around and adjust the bit after 'fdisk -l' to reflect your device's folder scheme and rerun till you get something that looks like this: (or see section 8:2:2 for full example)
    Device Boot Start End Blocks Id System
    /dev/block/vold/179:0p1 1 1279 10264576 c Win95 FAT32 (LBA)
    /dev/block/vold/179:0p2 1279 1925 5189632 b Win95 FAT32

    • Now to run the mk-debian -h script and change settings until satisfied. Note: I had one issue when I didn't tell the installer what 'drive' letter to install to;the letter preceding 'Win95 FAT32' in above example or in the below example command you can see the drive letter delineation specified at the end with '-L b' because on my device setup that's the letter in which I need to install to. (see section 8:2:3)
    # /data/local/deb/mk-debian -i /dev/block/vold/179:2 -s 5310 -L b -h

    • Which if configured correctly will look like the dump took and pasted below.

    Script to format a loop disk file or disk partition with ext2/3/4 and install a Debian Linux there.

    mk-debian [Options]

    -d <distro> specify squeeze/lucid/precise
    -m <path> specify mount point for disk/device
    -s <megabyte> specify size for new loop disk file
    -i <file|dev> specify loop disk file name or device
    -t <ext2/3/4> specify file system to be created
    -L <label> specify disk label for formatting
    -D <ip> specify DNS server to be used
    -M <url> specify Mirror URL for downloading
    -u update /system/bin/deb script and exit
    -U uninstall Debian kit (not debian.img!)
    -C clean files not required to run Debian
    -h display usage text and settings

    -d squeeze
    -m /data/local/mnt
    -s 5310 Mb
    -i /dev/block/vold/179:2
    -t ext4
    -L b
    -M(squeeze) http://ftp.de.debian.org/debian
    -M(lucid/precise) http://ports.ubuntu.com/ubuntu-ports
    Action: install

    For creating a loop disk file, you may want to change the default size (in Mb, 512-2047). For formatting a device (-i /dev/xxx) or if overwriting an existing loop disk file, the size is ignored. The loop disk file name or the device name will be written to the bootdeb script's IMG= line if this script succeeds.

    If you specify a device, the UUID of the formatted device is instead saved into bootdeb (IMG=uuid:<hexid>). With this, the correct device can be found even after some mixed USB drive/SD card eject-insert sequences.

    Check your settings by adding '-h' as the last switch.

    Remove the '-h' from the tail end of the command to run when you believe all is good and if all is good then scroll back up to step 7 of the main install guide where it talks about remounting debian.
    4. Aditinal notes Part 1

    4. Additional notes
    The following sub sections are dedicated to the more common tasks: interacting with android linux as a whole, helpful links, linux command line commands, and helpful tips for the apps that you’ll be using to set up and interact with your linux android system that would have broken the flow of reading the main install steps.

    4:0 Sites that have been exceptionally helpful
    This section has the following organization patterns:
    new links = descending order, older links near the top newer links towards the bottom
    small font with link embedded = older links that likely are up to date between all versions of this guide
    medium font with link embedded = links that I’ve formatted but have yet to update to other mirrors of this guide
    medium font with link not embedded = links that I’ve most recently added and likely have not been updated anywhere else


    4:1 apps for android that make things easier

    Note: these apps are not necessary to follow the guide as of yet, so don’t go paying without considering all the good it’ll do you.










    4:2 linux software and or packages that I've tested

    Very powerful programing and development toolkit for programing, if you run into issues after installation go to help update in the jmonkey window and that should resolve it, the developer states it on the download page but i and many others have filled google search bars with error searchs when mostly that one step will save you a lot of heartache, after of course resolving the other dependencies... I’ll be updating this in a bit with full directions on how to install .sh packages from the downloads folder in android to a full programing environment.

    Wireshark (linux & android? yep)
    updates eventually. so far I’ve been able to use wireshark from the android market to capture my home network info’s, saved it and then using wireshark on the linux side of things to view and interact with the pcap files as I at this moment don’t know how to resolve all the dependencies for running wireshark on the linux side solely.

    4:3 commands for apt-get and others I've found useful
    4:3:0 Android command line commands
    Here will be commands that can be run from the Android command line, independent of the Linux system, some in fact many will also work on the Linux system. At this point the "____" will be the break between subsections for sectio 4:3:0:* as organization will have to happen after there's enough content to organize.
    Download from web to a specific directory and attempt to reconnect if connection is interrupted.

    • The -cO = 'c' to reconnect if interrupted, 'O' to 'output' to a specific file path.
    • The '/sdcard/Download*' = path you want to save the file to; adjust it based on where your device saves downloads to by default or change it to a custom path.
    • The 'http://' = the web address you wish to download from. Some may not support it but most should.
    Example : Syntax

    # wget -cO /sdcard/Download/[Name-of-file-you-are-downloading].[file-extention-of-the-file] "http://domain.com/path/to/file/to/download.zip"

    Example : Usable

    # wget -cO /sdcard/Dolphin_Browser_Mini/download/photobomb-cat1fxb.jpg " http://www.justsaypictures.com/images/photobomb-cat-1fxb.jpg "

    4:3:1 Apt-get commands:

    Search for package or package description (still working on condensing and organizing this part)

    #apt-cache search "web server"| grep something

    Install commands

    #apt-get -i {package-name}

    Removal commands

    #apt-get remove <package_name>

    Removes an installed package, leaving configuration files intact.

    # apt-get purge <package_name>

    This command completely removes a package and the associated configuration files. Configuration files residing in ~ are not usually affected by this command.

    If you want to remove package1 and install package2 in one step:

    # apt-get remove<package1> <package2>+

    Remove unnecessary or abandoned data that isn't necessary to keep

    # apt-get autoremove

    This command removes packages that were installed by other packages and are no longer needed.
    #apt-get autoremove <package_name>

    This command removes an installed package and dependencies.

    While there is no built in way to remove all of your configuration information from your removed packages you can remove all configuration data from every removed package with the following command.

    # dpkg -l | grep '^rc' | awk '{print $2}' | xargs dpkg --purge

    auto-apt commands

    # auto-apt run<command_string>

    When invoked, the auto-apt command automatically installs packages upon missing file access. If a program tries to access a file known to belong in an uninstalled package, auto-apt will install that package using apt-get. This feature requires apt and sudo to work.

    Auto-apt keeps databases which need to be kept up-to-date in order for it to be effective. This is achieved by calling the commands auto-apt update, auto-apt updatedb and auto-apt update-local.

    Usage example

    You're compiling a program and, all of a sudden, there's an error because it needs a file you don't have. The program auto-apt asks you to install packages if they're needed, stopping the relevant process and continuing once the package is installed.

    # auto-apt run./configure

    It will then ask to install the needed packages and call apt-get automatically. If you're running X, a graphical interface will replace the default text interface.

    dpkg command to get package information such as description of package, version etc. The syntax is: dpkg --info {.deb-package-name}

    Pull up the man page for adding repos to apt-get

    # man add-apt-repository
    Note: at this point this command doesn't work, will look into it at some point soon.

    At some point if you don’t know better you’re going to try and make apt-get install more automatically than it really needs to; you may succeed. Before you waste your time like I did and then go searching round for ways to undo safely the same way take a look at this quoted and condenced from hear (http://www.linuxquestions.org/questions/debian-26/how-to-configure-apt-get-to-install-suggested-packages-169746/)
    I think that automatically adding all suggested packages would put a lot of cruft on your system. However, if you want it, you can get that behavior by adding a line to /etc/apt/apt.conf: Code: APT::Install-Recommends "true"; APT::Install-Suggests "true";

    The second line will automate suggests and the first would automate installation of recommends. You can use either or both, though again, lots of cruft. If you don't yet have an /etc/apt/apt.conf file,you can create it and add just the one line.

    If you have apt.conf setup like this, you can avoid installing recommends via: Code: apt-get --no-install-recommends install package

    This will prevent apt from considering recommended packages as dependency for installing,even if apt.conf is configured to do so via "APT::Install-Recommends".

    you can also specify the option on the command line, like this: sudo apt-get install <package> -o APT::Install-Suggests=true but apt-get install will follow the "suggests" for all installed packages, not just the one you are adding now.


    4:3:2 Command line commands for Linux (part 2)

    4:3:2 Command line commands for Linux

    Set password for root
    # passwd

    Add a normal user. This command will also start a chain of user input requests to set up the user's "profile" its easy and better than running round as root all day.
    # add-user[new-user-name]
    # adduser[new-user-name]

    Give normal user sudo permissions. Note depending on which environment you run this command you will need a password for root or the user's password for the sudo permissions or the password for the user, try'em all till one works and make a note of it.
    # add-user sudo[user-name]
    I've also used
    # adduser [user-name] sudo

    Login to new user. It will then request a password from you. Note when you type in your password there will be no indication on your display, this is a security feature.
    # login[user-name]

    Install packages to new user once logged in
    #sudo apt-get install [package-name]

    Get a list of installed packages
    #dpkg --get-selections

    Get some help with dpkg
    #dpkg --help

    4:3:3 Connectbot optimization guide
    By this point I hope you've poked around in Connectbot and seen some things. We're going to use some of them here to make the boot and shutdown processes a bit easier. For theses steps you’ll want to follow steps 4:3:3-1 though 4:3:3-4 and then scroll down to the specific automation example and copy/paste it.

    4:3:3-1. Linux Boot/Mount automation

    • Open Connectbot
    • Make a new local connection and title it 'linuxBoot' or something that will remind you not to open it more than once (if you do, don't worry, we can fix it)
    • Disconnect from 'linuxBoot' and then press and hold on it until a dialog pops up.
    • Select Edit Host, scroll down to ‘Post-login automation’ and select that too.
    • Past the following lines with the line breaks intact (you may have to go in with your finger and hit 'enter' in order to have the correct line breaks between commands) if your device took well to the system shortcut that the installer attempted to place for 'deb'.
    deb s; deb x

    • Past the the following if you get errors saying that 'deb isn't recognized'. This is usually to do with not having full read/write permissions while your device is operating (sOff and sOn for example on some HTC devices)
    export PATH=/data/local/deb:$PATH
    deb s; deb x

    • The deb s causes linux to mount and start openssh-server so that you can connect to it from any ssh compatible device and get to the command line.
    • The deb x starts up lxde, which gives you a graphical user interface to interface with.
    • The export path command is kinda like a short cut. You can use that one for many things and is well worth experimenting with.

    • Save your settings by hitting 'ok' and backing out to connect bot's main screen.
    • Make a new local connection and title it something like 'linuxShutdown'
    • Repeat steps 3-5 or 6 and past one of the following

    4:3:3-2 Linux Unmount/Kill automation

    Paste the following lines into the separate new local connection’s ‘Post-login automation’ titled ‘linuxShutdown’ for a quick connection that you can use to safely shut down your connections, unmount the OS from where it hooks into the android system, and kill any remaining tasks.
    deb S; deb X; deb u; deb k
    export PATH=/data/local/deb:$PATH
    deb S; deb X; deb u; deb k

    • capitalizing the 's' and 'x' from the 'linuxBoot' example sends the shutdown command to those two services
    • Unmount from system is what 'deb u' does, sometimes you'll see some errors
    • And 'deb k' forcibly kills whatever's left (usually whatever was causing the errors from running the 'deb u' command
    • Save and back out yet again to the main connectbot screen.

    4:3:3-3. Connectbot “Local” SSH setup

    Make a new connection, this time select ssh, if its not already selected by default and title it something like 'debian@localhost' just change the debian part to the name of the user you want to login as, such as root perhaps.
    1. If you've left ssh running then skip to step 4:3:3-2. If you haven't started it then start it by

    • Selecting your 'linuxBoot' let it do its thing for a sec or hit 'enter' on your keyboard and let it do its thing for a second.
    2. Once you've got ssh server up you can connect to it one of two ways that I know of.

    • First to test and daily for quick command line access: click on the ssh connection that was made in step 4:3:3-3 of this mini-guide and type the password for that user... and your in.
    • Second way is to connect with a different device: see section 7:1:2-2
    Once you're in you may interact with it like a terminal window and most linux commands will work here with little to no modification. So utilize linux specific sources of information as I'd exhaust myself enumerating and cataloging all the things you can do.

    4:3:3-4. Other good combos to use after using 'linuxBoot’

    these are connections that I set up with connectbot to quickly run other repetitive tasks that I've saved and used as their own separate local connections. These can also be copy/paste into the command line usually too.

    • upgrade, update, start a search for something new to install
    apt-get upgrade; apt-get update
    apt-cache search

    • Clean out temp and cached files, remove unnecessary junk
    apt-get clean; apt-get autoremove; apt-get update

    • Displays the manual for displaying manuals and the "| less" should make it display a bit frienlyer.
    man man | less
    4:3:4 Remote RDP debian kit Guide
    1. Open Remote RDP, Press menu, Tap add and input the following modifications to the options:

    • Host=localhost

    • User=[your-user-name]
    • Password=[please-don't] can be a security risk
    • Color=24-bit
    • Screen=800X600 (though try others based on the physical size of your device)
    • Compress=checked On
    • Name=[user-name@localhost] (think you can name it whatever you like)
    2. Back out to main Remote RDP screen and tap on the new connection you've set up.
    3. There you will be greeted by either an error prompt (in which case check your settings in step one of this mini guide or run the boot commands described in step 4:3:3-6, specifically deb x) or you will see part of a desktop, window, and or mouse cursor. At this point; verify the username is correct, input your password for that user name, and hit enter.

    Note if when you tap or drag on the screen and the mouse cursor follows your finger and not the gesture:

    • Back out to the main screen on Remote RDP
    • Press menu, tap settings; or tap the gear icon
    • Scroll down to Touchpad mode and either enable or disable
    • Familiarize yourself with some of the other settings while you're here as there are many user interface tweaks you can use.

    4. Once you've successfully made a connection, chill for a sec. You're going to at first see a grayish screen, maybe a window bar at the bottom, and then (depending on the speed and available memory of your device) all the sudden it'll paint in a desktop for you to poke around in.

    5. On the desktop that Remote RDP has wonderfully supplied; let's get rid of one pesky thing, the screen saver, its a resource and battery drain.

    • Mouse over to the lower left corner of the screen
    • There you will see a little 'symbol' click it and in a second it'll pop up a dialog.
    • Mouse over to options, then screen saver settings, and tap it
    • In the upper right quadrant of the new window you'll find a drop down menu with disable screensaver being one of them.
    • Select your choice, then exit out.
    Note if logged in as root in Remote RDP you'll receive an error pop up window. In which case instead of mousing over to screensaver settings; mouse over to disable x screensaver under the other directory of the 'start bar' menu and click it. That should resolve having the screen saver coming on in the background while the screen is off and in no need of saving. Other methods welcome.

    4:4 Rom Tool Box user Tips
    If you've got it then you know its the best; if not, then try the free version and see if it will meet your needs before making the plunge to pro version.

    4:4:1 Scripts
    Here I will document scripts that I use or am working on.

    Boot script

    : '
    starts the remote desktop protocol server and openssh server services and exits the bash automaticly
    written for personal use by strangerthanbland 05182013 Use at own risk.
    see guide for details on why this script is useful
    Comments and suggestions can be directed to either of the above links
    _set this to run at boot with rom tool box by copy/pasting in a new script file and tapping on it and selecting Run At Boot Option
    _add a new script to rom tool box by opening the app on your device
    __scrol down to scripter under the tools tab and tap it
    ___tap on add then create
    ____title it what you want and copy past this example from hash sine to the exit command
    export PATH=/data/local/deb:$PATH
    deb x; deb s

    ShutDown Script

    : '
    Listens for the device's shutdown command and executes this as one of the shutdown processes


    4:4:2 Perfomence Mods
    The mods explained here are as always a "use at your own risk" sort of affair. What will be contained here? Governors, overclocking and undervolting, memory management, ad blocking, and many more when time permits.
    4:4:3 General guide lines
    The things that I suggest for ROM Tool Box are only from a user's perspective and are here for easy reference, documentation purposes, and to offer a different perspective. The guide lines for using the material found in sections 4:4:1 - 4:4:4 may be modified but are as follows:

    • Don't be foolish; this app can be dangerous
    • Understand your device(s) and my device(s) are different
    • Comments/problems about the app itself likely should be directed to the developer of that app
    • Comment/problems about the content here should be directed here to this document or one of it's mirrors
    4:4:4 Useful tips