Reboot Android-x86

The Android-x86 project provides ISO installation images of Android that can be installed on personal computers, which is cool, because that makes it possible to use the most popular operating system on the planet without buying an Android tablet or smartphone.

The latest stable release is Android-x86 4.4-r2. This tutorial shows how to install it on a USB stick, so you can have an Android device that you can boot and use from any modern computer.

What You’ll Need:
If you want to follow along, you’ll need two USB sticks, one to use as the installation media, the other as the installation target. The ISO installation image is less than 400 MB in size, so a 1 GB USB stick will do as the installation media. You may download the latest ISO installation image from android-x86.org/download.

The target USB stick should also be at least 1 GB, because a fresh installation of Android-x86 takes up about 1 GB of disk space. For this tutorial, I used an 8 GB USB stick.

How To Do What To Do:
1. Transfer the installation image to a USB stick: Assuming that you downloaded the ISO image to a Linux computer, you may transfer it to a USB stick using the dd command like this:

# Using the dd command 
# /dev/sdc is the USB stick

dd if=android-x86-4.4-r2.iso of=/dev/sdc bs=1M

2. Format the target USB stick: To make the installation easier, be sure to format the target USB stick, or just wipe it, if it contains data. Then Insert both USB sticks to free USB ports on the computer and reboot. If you did not set the computer to boot from external media, press the F key that will bring up the computer’s boot menu and select the right one to boot into.

Related Post:  Dual-boot Fedora 15 and Ubuntu 11.04 with either side on an LVM partitioning scheme

Figure 1 shows the entries in the boot menu of the computer used for this tutorial. The USB: PNY USB 2.0 FD 1100 entry is the USB stick that holds the installation image, while the USB: SanDisk Cruzer Glide 1.26 entry is the target USB stick. The computer has an internal 250 GB hard disk with Linux Mint 17.1, Ubuntu 14.10 and Windows 8 installed in triple-boot fashion.

Linux computer boot menu
Figure 1: Boot menu of computer showing detected storage media

This is the Android-x86 boot menu. You have the option to boot into a live desktop or straight to the installer. The latter option seems to be the most appropriate thing to do here.

Android-x86 4.4-r2 boot menu
Figure 2: Entries on the boot menu of Android-x86 4.4-r2 installation image

You’ll then be shown a window that shows the disks and disk partitions detected by the installer. In this case, sdb1 belongs to the target USB stick. The sdc entries belong to the installation media.

Android-x86 disks
Figure 3: Disks detected by the Android-x86 installer

After selecting the target disk, you’ll be given the option to format it. You definitely want to format it. I chose to format mine using the Ext3 file system.

Android-x86 ext3 file system
Figure 4: File systems supported by the Android-x86 installer

Yes, we are sure.

Android-x86 format USB stick
Figure 5: Options to format the target USB stick.

Yes, install the GRUB boot loader to the USB stick. A plus for the installer is that it does not mess with the contents of the internal hard disk, which is good to know, because in a future tutorial, I’ll show how to dual-boot Android-x86 4.4r2 and another popular Linux distribution.

Android-x86 install GRUB
Figure 6: Install GRUB boot loader to the USB stick

Yes, I think it’s better to install the /system directory read-write.

Android-x86 /system directory
Figure 7: Make the /system directory read-write

This image just shows the writing process. Less than 750 MB of data is written to the USB stick.

Android-x86 /system
Figure 8: Writing to the /system directory.

Installation should take less than two minutes. I did not encounter any problem, so next thing I had to do was reboot.

Reboot Android-x86
Figure 9: Reboot newly installed Android-x86 from a USB stick

On rebooting, you’ll be presented with the GRUB menu. Selecting the default option, I was able to boot into the Android-x86 desktop. My test computer does not have a wireless card, but the system was able to auto-configure the Ethernet card.

Android-x86 4.4-r2 GRUB boot
Figure 10: GRUB boot menu of Android-x86 4.4-r2

So I now have Android 4.4 installed on a USB stick, which I can use from any personal computer. And that’s awesome, because I don’t have any Android device.

Related Post:  Managing BURG with BURG-Manager

Share:

Share on facebook
Facebook
Share on twitter
Twitter
Share on pinterest
Pinterest
Share on linkedin
LinkedIn

Hola! Did you notice that LinuxBSDos.com no longer runs network ads?  Yep, no more ads from the usual suspects that track you across the Internet.  But since  I still need to pay to keep the site running, feel free to make a small donation by PayPal.

Subscribe for updates. Trust me, no spam!

Mailchimp Signup Form

Sponsored links

1. Attend Algorithm Conference, a top AI and ML event for 2020.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.

10 Responses

  1. “1. Change the Hostname: In the process of installing your brand new Fedora 19 desktop, I’m sure you noticed that Anaconda, the Fedora system installer, did not give you the option of setting a hostname (if it did, then I need more than a new pair of specs).”

    It’s in the Network panel. I’ve booked you an appointment with the optometrist 🙂

    1. That’s funny. But why did you have to “hide” it in the network spoke? This becomes a design issue. Remember that in the hub, the network spoke is not marked as an item that needs to be configured, in the same manner than the installation destination spoke is.

      You know, just before I published that article, I installed a system just to look for that feature. Your design guys should be working for Booz Allen Hamilton 🙂

      Where did they hide the option to install the bootloader in a custom location? 😉 I looked for that, too.

      1. “But why did you have to “hide” it in the network spoke?”

        What spoke would you *expect* it to be in? Software Selection? Installation Source? Installation Destination? Keyboard? None of those appears to make a whole deal of sense. “Network” seems the perfectly logical place for it, to me. A system’s host name is only of any interest in the context of a network, after all.

        “Where did they hide the option to install the bootloader in a custom location?”

        That depends on what you mean by ‘custom location’. You can pick which disk it will be installed to from the “Full disk summary and bootloader…” link on the Installation Destination page. (I’d figure the word ‘bootloader’ should be adequate indication of that.) You cannot choose to install the bootloader to a partition header when doing a BIOS install. See https://bugzilla.redhat.com/show_bug.cgi?id=872826 for that bikeshed.

        1. Not sure where to begin with something this wrong. A machine without a hostname is WRONG, WRONG, WRONG. Network or no network.

          Or do you call your pet, “dog” instead of giving it a name, because you probably only have one, right?

          1. Arguments welcome, bare assertions tend to be ignored.

            The machine is not ‘without a hostname’ if you don’t set one explicitly. It gets the hostname localhost.localdomain.

      2. “Remember that in the hub, the network spoke is not marked as an item that needs to be configured, in the same manner than the installation destination spoke is.”

        Indeed. It does not *need* to be configured. You can *choose* to configure it if you so desire. One of the main points of a hub/spoke design is that you are not forced through steps you don’t need to modify, but choose which you do and don’t want to use.

        1. But considering that the hostname is something that most users like to personalize, shouldn’t there be an indication that there’s something in that spoke that needs to be modified?

          1. “But considering that the hostname is something that most users like to personalize”

            I don’t agree with that assertion.

            “shouldn’t there be an indication that there’s something in that spoke that needs to be modified?”

            No. It doesn’t need to be modified. The indicators indicate that you *have* to change something on that spoke in order to proceed. The lack of an indicator isn’t meant to indicate ‘there’s no reason to come in here’. If there was no reason the spoke wouldn’t _be_ there at all.

  2. You can set the hostname during the install by clicking the network icon. I change my hostname and also add nameservers.

Leave a Reply to naveen Cancel reply

Your email address will not be published. Required fields are marked *

Get the latest

On social media
Via my newsletter
Mailchimp Signup Form

Partner links

1. Attend Algorithm Conference, a top AI and ML event for 2021.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.
Hacking, pentesting distributions

Linux Distributions for Hacking

Experts use these Linux distributions for hacking, digital forensics, and pentesting.

Categories
Archives

The authors of these books are confirmed to speak during

Algorithm Conference

T-minus AI

Author was the first chairperson of AI for the U.S. Air Force.

The case for killer robots

Author is the Director of the Center for Natural and Artificial Intelligence.

Why greatness cannot be planned

Author works on AI safety as a Senior Research Scientist at Uber AI Labs.

Anastasia Marchenkova

An invitation from Anastasia Marchenkova

Hya, after stints as a quantum researcher at Georgia Tech Quantum Optics & Quantum Telecom Lab, and the University of Maryland Joint Quantum Institute, I’m now working on superconducting qubit quantum processors at Bleximo. I’ll be speaking during Algorithm Conference in Austin, Texas, July 16 – 18, 2020. Meet me there and let’s chat about progress and hype in quantum computing.