**Problem** I want to install Android in a VM to restore a backup using Titanium Backup. For this to work, I need Android to be rooted. **What I tried** I've tried to install Android-x86 4.3 in a Virtualbox VM. The installation seems to work. I made an 8GB partition disk (sda1), made it bootable, and installed Android in it from an ISO file. This all seems to work. Android starts, I can browse the internet, install apps, etc. Then I want to restart the VM, and guess what?! I go back to the installation screen, like starting up from the ISO live image. For normal stuff, I can make a snapshot, start that up, and do anything. My problem is that I need root permission to restore a Titanium Backup in that VM. And I cannot root this VM because the disk is not writeable. With Alt-F1, I become root and I can use a script to root Android. But my guess is that I'm still on the ISO and that is not writeable. **Update - another try with Android 4.2** As mentioned in the comments, 4.3 would have problems with root access. I tried 4.4, which didn't start at all. Then I tried 4.2, which has the same problem as 4.3 for me. I made a screenshot of what I see when I try to run the rootscript , which is described here . You can see the errors: **rm failed - Read only filesystem** How can I fix this? **My question** How can I install Android permanently on this VM, so it can reboot and then be rooted?

Waydroid, bliss os, pheonix os doesn't work, everytime i used cloning apps like dual space, super clone etc, the apps will crash,

I installed android-x86-8.1-r2.iso 64 bit version in VMWare Workstation 15.5.0 under Win10x64 1903. It starts into the linux command line prompt, and I tried Alt+Fx, there is no GUI. I tried all four boot menu(normal/debug/debug nomodeset/debug VIDEO=LVDS...), all the same.

I installed android-x86-4.2-20130228 as a live USB, but it doesn't read my partition of my hard disk. I tried with **Paragon UFSD Root Mounter**, but it doesn't work well in 4.2.2, and **ES Explorer** doesn't read any partition. How can I mount all partitions of the hard disk in Android-x86?

I have **Android-x86** alongside **Ubuntu 16.04**. I have installed Android in a 16GB partition on my hard drive. I was wondering if it is possible to access other partitions from Android, as it just shows nothing in the files app. It would be pointless because all my pictures, videos, and other files are in those other partitions. I am not an expert, so please let me know if additional information is needed.

I have installed Android 4.4.2 x86 on my PC that has 2 hard disks with 2-2 partitions each. I have installed Android 4.4.2 X86 on one of them, and I have data on the other 3. The problem is that I am not able to access any of my other three partitions. How can I access my other partitions?

I recently installed Android-x86 (Prime OS) on my pendrive. However, upon opening through different disk managers on PC & mobile, there is nothing inside my data folder. I can only see system.img and kernel file in /Android-86/Android-2.1 and nothing else. I suppose in the /data folder, we should be able to see /system, /vendor, and /user. Also, let me confirm this is not a limitation of mobile or whatsoever. I can see other pendrives and files perfectly in the same format. I also tried to open it on PC through Disk Genius, but it shows the same thing. Is there any way to access my data on Android-x86 on any device?

I'm new to VMs and Linux. I'm setting up an Android x86_64 9.0-r2--k49 on VirtualBox. This is the glitch. It showed up on the entire setup (haven't completed it). VM Settings: 4GB RAM, 4 Cores. 77.85GB Storage, 128 MB VRAM, VMSVGA Graphics Controller, 3D acceleration ON, Set OS: Other Linux (64-bit) Does anyone know how to fix said glitch? (Sorry if this is insufficient info, I don't know what to put in the description.)

I can install android-x86-8.1-rc1.iso, but when I boot it looks like this: What can i do to fix this? PS: I installed it directly to my Root-Server. Virtualization is activated and already works with VirtualBox and similar programs.

I am wondering if Android could grow beyond mobile devices and go on PC too. I know Samsung has Dex, and Google has ChromeOS. But do you think the Android project is compatible with the PC ecosystem?

I have installed BlissOS on a virtual machine. If I run with DHCP is ok, it gets the IP immediately. But I want to use static IP. On the internet, some people suggest using "ethernet manager", but this application is not available anywhere, searching on Google return network manager only. On another forum, someone said "use netcfg", but this command is also missing. Does anyone know how to configure a static network? It is not wifi, only eth0.

I have installed Windows as well as android x86 on my laptop. Everything was just fine until the LCD of my Laptop was not broken. Now with broken screen I use Specific key combination to project my screen to an external monitor. This feature works fine with Windows but the key-combination does not work for android x86. Monitor does not even detect a signal from laptop. Is there any trick to project the screen in android with parent screen broken?

After 1. Downloaded Android x86 64-bit ISO file from here 2. Created bootable installer USB drive using Rufus with this specs - Partition scheme : MBR - Target system : BIOS or UEFI - File system : Large FAT32 - Cluster size : 32kb 3. Booted from the USB drive and choose Android Installation from the Grub menu. Suddenly the screen turned black without no log text displayed like it supposed to. I was stuck there before Ctrl+Alt+Delete restarted the PC. So I believe I have to manually editing the Grub selection by adding something to it. But I have no idea what am I adding. This is the selection's execution. setparams 'Android-x86 9.0-r2 Installation' '' 'Android-x86 9.0-r2 Installation' 'INSTALL=1' savedefault set root=$android if [ ! -e $2/kernel ]; then search --no-floppy --set root -f $2/kernel fi set kd=$2 shift 3 linux $kd/kernel root=/dev/ram0 $src $@ initrd $kd/initrd.img I just want to at least seeing the log text or successfully boot into Android installation, without no longer stucked with the blank screen.

In my VM I loaded Android X86 and I gave access to the wi-fi card: But for some reason I see no way to have access towards it nor having wifi enabled. Is there a way for my AndroidX86 to manage directly the wifi card?

So, I've been wanting to play PUBG for a while now, but my PC is pretty awful, then Mobile came out, and TGB didn't work properly. I've been trying out several different Android OS, but all of them need a processor that supports SSE4.2+. So, I checked out this Android-x86 OS, the 32-bit version (the first one that booted, I'm pretty sure that the game wouldn't really work anyway since the version is 32 bits, but I wanted to give it a shot anyway), and well, I can't download anything from the Play Store or install any APK. I figured out a way to install APK from the terminal, and there I discovered the error below. Why can't I install any apps on Android x86?

130|x86:/sdcard/Download # pm install
1535771455810.jpg                         Pixel Dungeon_v.1.9.2a_apkpure.com.apk    RAR_v5.60.build63_apkpure.com.apk
130|x86:/sdcard/Download # pm install Pixel\ Dungeon_v.1.9.2a_apkpure.com.apk
Error: failed to write, posix_fallocate failed: ENOTSUP (Operation not supported on transport endpoint)
130|x86:/sdcard/Download #

I'm trying to install Android-x86 on USB for my new HP laptop. I have followed the instructions on Android-x86.org. My issue is that after the initial install, it never boots again, it just gets stuck on the Android logo. I have seen a few posts such as [this answer](https://android.stackexchange.com/a/214061/44325) : > when you change the internal frame where the UEFI firmware settings to the EFI framework setting change the boot order you have to make a small partition for grub go back and change it back otherwise it won't boot the second time but unsure of how to do this. I have also seen [this answer](https://superuser.com/a/1270769/356789) : > 6. In boot menu select Installation - Install Android-x86 to harddisk > 7. In Choose Partition menu select Create/Modify partitions > 8. **In Do you want to use GPT question select No** > 9. cfdisk program will open > 10. Select New and select Primary as partition type, set size to 100 MB and select Beginning > 11. Select bootable. Now the Flags column should say Boot for the new partition > 12. Select the free space and select New and select Primary as partition type, leave size as default to fill the remaining free space > 13. Select Write and type yes and press Enter > 14. Select Quit but I'm stuck in the fact when I click on create/modify on this, I get cgdisk not cfdisk, and it's not as easy to use. I don't know why this is happening. Before I realised what to do, I was accessing cfdisk, but now it's only cgdisk. I have purchased 4 premium USB sticks just in case the issue was due to a bad USB, but it's not the case and I'm just so frustrated. Any help at all would really be appreciated.

I just installed Android x86 9.0c and I don't know why it doesn't boot on GUI mode and it boots only in the command line. Then, after some seconds, I can only see just a dash appearing and disappearing. Below you can see that it has booted into command line, after some seconds it becomes black and all I can see is just a dash appearing and disappearing: > I have tried to put my graphics settings to VBox/VGA and disabled 3D acceleration, but it still doesn't work. What else can I do to fix this problem?

I previously used vga=ask and vga= in Android-x86 6.0 to set the display resolution in VMWare and now in QEMU/KVM. Now I downloaded and installed Android-x86_64 (CyanogenMod 13), in QEMU, in UEFI mode, to a GPT partition, and the option doesn't seem to work anymore. Instead it outputs: > error: invalid file name 'vga=ask' There doesn't appear to be much information about this elsewhere. But I could find: - What happened to vga=ask in newer kernels? (Unix.SE) - Grub: Legacy 'ask' parameter no longer supported (Superuser) - android-x86_64-5.1-rc1.img --- change resolution (Android-x86 at Google Groups) I tried wm size 1280x720 (in terminal emulator as root) and it *kind of* works. the resolution appears to change, but the display area doesn't and it becomes a pain to read anything. So I had it reverted with wm size reset. I also tried UVESA_MODE=1280x720 and it also reports "invalid filename 'UVESA_MODE'". There's a proposed solution at the 3rd url (debug.drm.mode.force 1280x720) but it also didn't work. So, how to change the screen resolution properly? **[Update]** I tested with a new, non-UEFI installation and the vga kernel option works there.

If I enter the Wi-Fi settings of Android-x86 (currently v8.1-r1) inside VirtualBox (currently v6.0.4) and turn it on, why does it just immediately get turned off? Some Android apps try to find devices inside the network so it's essential (e.g. if you want to use Chromecast and iRobot Home).

I recently installed Android x86 through VirtualBox onto my PC. It runs mostly fine (except for some weirdness with the mouse, which isn't really an issue) but for the fact that apps cannot detect the internet connection. I can access the internet through the included browser just fine, so I know that the connection is actually getting to the VM, but apps cannot access it. From https://android.stackexchange.com/questions/62371/ , I read that it's because I am using NAT or virtual ethernet that some apps detect that there is no WiFi or cellular and refuse to work. Is there a way to fix and/or get around this? If it helps, my host OS is Windows 10 Educational and I will do my best to provide hardware specs if that would help solve the issue.