**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?

Can I run a virtual Android machine on my Samsung Galaxy S6 Edge? Or maybe can I run a custom ROM without flashing stock?

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.)

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?

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.

This may seem like an odd question but I cannot resolve it. I am using the Android-x86 emulator in VirtualBox (https://www.android-x86.org/documentation/virtualbox.html) . I open various apps like Firefox, Chrome, Maps, etc. Normally, I would click the 'x' or go to a menu which said 'exit'. But there is nothing like that. Swiping the app up / down / left / right does nothing. I use "Force Stop" in Settings but that doesn't close the program. In Ubuntu, I can ps aux | grep program_name and then kill the PID. But ps aux does not work in the Android Terminal. How can I close those apps? Can I use the terminal to close programs?

I was thinking about copying my phone to a VM for exploring and learning. Without rooting my device, can I somehow clone it? By cloning I mean dd / copying disk files and not downloading the same apps or recreating a similar environment. Once I have the raw.img file of the phone, can I boot it as a qemu guest VM? I wonder if there are any hardware issues that would prevent me from booting this new android VM, i.e. in case the android phone is Samsung then perhaps the whole Knox feature will prevent booting?

How is it possible to get VirtualBox ready with an Android-x86 ISO image which supports ARM v7 (armeabi-v7a)? Genymotion seems to do that, but as soon as I start the VirtualBoxfrom VirtualBox, it does only display the terminal. Same with all the other Emulators like AndyRoid. I've tried installing several x86 ISO images. Installed the ARM translator (libhoudini) and so on. I've tried to install the Buildroid image, same results. Some games work, but Clash of Clans doesn't. This is what I'm pointing at. Clash of Clans needs ARM v7. v5 does not work in this case. Has anyone ever handled installing Android X86 with ARM v7 or a way accessing the VirtualBox from Genymotion without GenyMotion?

Ideally, I am trying to gain root access to a Bliss OS (version 11.14) Virtualbox machine I have so that I can view saved PCAP files. Sadly, to get to the directory I have to be root. The only option seems to be installing a fake root module (https://www.crisisshelter.org/get-root-access-in-termux-without-root-fakeroot/) . However, this and several other things I have tried to do with Termux lead up to running apt-update and apt-upgrade. However, I keep seeming to get repository issues.

$ apt update && apt upgrade
Get:1 https://grimler.se/termux-packages-24  stable InRelease [16.8 kB]
Get:2 https://grimler.se/game-packages-24  games InRelease [9347 B]
Err:1 https://grimler.se/termux-packages-24  stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO PUBKEY B0076E4908716168
Get:3 https://grimler.se/science-packages-24  science InRelease [9360 B]
Err:2 https://grimler.se/game-packages-24  games InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BO076E4908716168
Err:3 https://grimler.se/science-packages-24  science InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B0076E490871616B
Reading package lists... Done
W: GPG error: https://grimler.se/termux-packages-24  stable InRelease: The following signatures couldn't be verified because the public key is not available: NO PUBKEY B0076E490871616B
E: The repository 'https://grimler.se/termux-packages-24  stable InRelease' is not signed.
N: Metadata integrity can't be verified, repository is disabled now. N: Possible cause: repository is under maintenance or down (wrong sources.list URL?).
W: GPG error: https://grimler.se/game-packages-24  games InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B0076E490B71616B
E: The repository 'https://grimler.se/game-packages-24  games InRelease' is not signed. N: Metadata integrity can't be verified, repository is disabled now.
N: Possible cause: repository is under maintenance or down (wrong sources.list URL?).
W: GPG error: https://grimler.se/science-packages-24  science InRelease: The following signatures couldn't be verified because the public key is not available: NO PUBKEY B0076E490B71616B
E: The repository 'https://grimler.se/science-packages-24  science InRelease' is not signed.
N: Metadata integrity can't be verified, repository is disabled now.
N: Possible cause: repository is under maintenance or down (wrong sources.list URL?).

I can't seem to find a fix for Termux anywhere online. Does anyone have a better solution to getting root access via Termux? UPDATE: I updated termux to a more modern version. However, I get "File has unexpected size" error when I try to run apt-get update, or when I try to install anything.

~ $ pkg install su
Checking availability of current mirror: ok
Get:1 https://packages . termux.dev/apt/termux-main stable InRelease [14.0 kB]
Get:2 https://packages . termux.dev/apt/termux-main stable/main x86_64 Packages [450 kB]
Ign:2 https://packages . termux.dev/apt/termux-main stable/main x86_64 Packages
Err:2 https://packages . termux.org/apt/termux-main stable/main x86_64 Packages
  File has unexpected size (451382 != 450311). Mirror sync in progress? [IP: 216.18.208.174 443]
Err:2 https://packages . termux.org/apt/termux-main stable/main x86_64 Packages
  File has unexpected size (451382 != 450311). Mirror sync in progress? [IP: 216.18.208.174 443]
Err:2 https://packages . termux.org/apt/termux-main stable/main x86_64 Packages
  File has unexpected size (451382 != 450311). Mirror sync in progress? [IP: 216.18.208.174 443]
Fetched 14.0 kB in 1s (10.7 kB/s)
Reading package lists... Done
E: Failed to fetch https://packages . termux.org/apt/termux-main/dists/stable/main/binary-x86_64/Packages File has unexpected size (451382 != 450311). Mirror sync in progress? [IP: 216.18.208.174 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Does anyone know a fix for this?

[Androidx86.org](https://www.android-x86.org/documentation/virtualbox.html#ref1_a:~:text=Enable%203D%20Acceleration%20may%20be%20checked) says that to use 3D acceleration for my Android-x86 virtual machine, I have to install Linux guest additions. I would like to know how to do that. I am using a - Ubuntu 20.10 (64-bit) - Intel Core i5 4th gen (@3.1 GHz) - NVIDIA GeForce GT 730 - Oracle VM VirtualBox 6.1

I have an Android O Virtualbox and when I go to set it up, it asks if I want to set it up with data from my old phone or start new. I've tried both options, and it says that the Google Play Services have stopped, every time I try. I don't know what to do.

I am trying to create a simple Android application to better learn about the Android platform. The first step was installing Android studio. Unfortunately, though, using Android Emulator was impossible, because my CPU has not VT-x support. In order to overcome this, I chose the other path I had available: I installed an Android system on a virtual machine using VirtualBox. And here's where I met my last problem: After the installation, which went OK, I rebooted the system, and now I am stuck in a panel where I have to choose the language, because I cannot seem to be able to do anything using my mouse or keyboard. The first thing that came to mind, was that I needed some kind of touch input, which I don't have on my laptop... Any advice to solve this in order to be able to use Android in the VM?

I'm using Android in a VM, namely VirtualBox. The reason for this is that my bank forces me to use the (very badly rated) banking app SecureGo, but I have no Android or iOS device. These things worked well: - Setting up the VM - Installing android - Installing the SecureGo app However, SecureGo refuses to work because it says that it detected a jailbreak or rooting on my device. Any ideas on how to fix this? Configuration * Virtualbox 6.1 * Android 8.1.0 (x86 64-bit iso from fosshub.com/Android-x86-old.html )

I've been using parallel space on my Android device for a while now but it's been having an issue with logging in to the Google Play services and thus backing up my game progress becomes hectic. I'd like to know where the progress files are stored in my file manager so that I can cut and paste it manually. Thanks in advance.

I am running Android 4.3 "jelly bean" in a VirtualBox VM. Google has released an ISO of an x86 port on code.google.com . It's a fairly straightforward installation, and easy to setup. You can find a tutorial here if you need help. But let's get back on subject. Anyways, I have successfully installed it. It does not seem to have mouse integration, which I *desperately need.* My laptop which I am running it on does not have a touchscreen. It is a 64-bit Dell something-or-other laptop I received from a friend, and it is running Ubuntu 16.10. Is there any available APKs or workarounds for the mouse? I can use the mouse, but no pointer displays. For example, I can click and drag the top menu bar that displays notifications, battery, etc. and open that, or click buttons (if I'm careful), or use it as if it were my finger. I simply need it to display the mouse pointer. The only workaround *I* can think of is unlock the developer tools and use the mouse tracking option that draws a line when you tap. However, that only works if I click and drag. The question: Are there any APK's or workarounds for displaying a mouse pointer or emulating a mouse, and if there is/are, how can I use/activate/install/get them? **edit**: This isn't something I can't live without. I'm just experimenting, maybe going to do a little android gaming just for fun. I can do most of the UI navigation with the keyboard, but a mouse would make things much easier. Also, I am looking for a *no-price, costless* workaround. That said, I'd rather not do anything like buy a controller. ~ P

I was trying to install android-x86 inside my virtualbox last evening. But I wasn't able to make it right. I'm getting a 'kernel panic' message. How do I overcome it? The following is a snapshot of what I got out of my installation attempt.

**Question How to PreRunning preloading pretesting custom/stock ROM in android virtual machine on mobile device** I Have many custom android custom rom (android 6,7,8,9,10,11) availabale for my device i want to check all roms and test their features (mainly adoptable storage or move app to sd and permission security features) and weather it's not a buggy or problematic rom before installing or flashing is there any app available which can load the android on virtual machine virtual box or android emulator on mobile device (not on pc computer) After google I founded a link quesion in the forum and answered by ash-ish which link and aswer I pasted below stating how to virtually load the custom rom through multi ROM app Before trying I just want to confirm and have following queries in mind **MY queries** Q1. Is multiboot app install multiple roms or single rom Q2. Does multiboot app safe and authenticated Q3. Does multiboot app really load virtually the custom ROM or it writes or install roms to the internal memory or does it touches any rom partitions Q4 does chances to brick the mobile if there is some buggy or corrupt custom rom image then can I corrupt the original firmware of mobile device while loading virtually Q5. Can later multiboot app be uninstalled and remove do it leave any leftovers in rom.. if I take NANDROID backup of recovery system userdata and boot partition through twrp ir adb pull can I r cover back the mobile or recover from bricked stage of mobile device Q6. As the suggestion in the following link answer for multiboot is for samsung galaxy edge will it work on all android mobile will it work on my lyf water 7 device Q7. Any more advice opinion suggestion expert advice **My findings** **Android emulator** **Multiboot app** > Question Running a stock or custom ROM in a virtual machine on Android⠀ android-emulator samsung-galaxy-s-6 virtualbox Can I run a virtual Android machine on my Samsung Galaxy S6 Edge? Or maybe can I run a custom ROM without flashing stock? **Answered by Ash-Ishh** > Part 1: Using Multiple ROMs without flashing again and again > App required: MultiRom > Introduction: > MultiRom powerful utility that installs itself into your Custom Recovery. > First Step: "BACKUP" It is recomended to make a nandroid backup of your current ROM in case something goes wrong you can just restore it. > Procedure: > Once you have installed MultiRom open up the app. MultiRom will ask for Root Access. After granting it, you should see Multirom and its current version, the recovery that is required to manage Multirom with, and the MultiRom Kernel (Kexec-hardboot patch) > Just tick all 3 boxes to install Multirom, the recovery patch, and the kernel. Once it’s finished installing, MultiRom Manager should prompt you to reboot into Recovery to complete the installation. Once you’ve entered the Custom recovery, it should complete the installation and will soon reboot itself. > A message will appear saying something similar like the device will boot into the internal rom in 5 seconds, unless you click cancel. You haven’t installed another Rom into MultiRom yet, so you should only see one option to boot into, and that should say Internal. Internal is pretty much your current Rom, or whatever you were using before installing Multirom. If you do not click cancel, your device will boot into the Internal Rom by default, so click cancel in the event you decide to boot into a different Rom. > Now, in order for you to boot into a different Rom, first you have to download the different Custom Roms you want. > ONLY DOWNLOAD THE CUSTOM ROM THAT’S SUPPORTED BY YOUR DEVICE > Note that once you install your Custom Rom, Google Apps and Services will not be installed on it, so you will have to download something called GAPPS (Google Apps) for the respective Android version. so now download the GAPPS zip file. > Once you are back into your device’s Stock Rom, we will be using TWRP Recovery, as it is the default Custom recovery supported by MultiRom. Once you are in TWRP, click advanced. You should see a new option called MultiRom. Click that, and you can configure settings, as well as install your Custom Rom to boot from. > Assuming you now have your Custom Rom downloaded on your device,click “Add Rom.” You will see many settings on the screen. For Choose ROM type, leave it by default, which is Android. Share Roms with Internal ROM, just leave that as don’t share. You can also see where the Custom Rom will be installed to. By default it will list your internal memory, but if you have an SD card, or even a USB Flash drive that is plugged into your device VIA OTG cable, it will be listed there as well. So just pick the destination of where you want your Custom Rom to be installed/saved on. > Click next, and select your source of installing your custom Rom. 3 Options will appear, which include Zip File, Backup, and ADB Sideload. You should have downloaded your Custom Rom earlier in for form of a .zip file, so just select ZIP File. Next, you will navigate to the place where you downloaded your Custom Rom, which most likely will be located in your Downloads folder. So find that and select it. Once you have it selected, you will reach a page where it shows you to confirm flash. So swipe the bar to confirm the Flash, or installation of your Custom Rom, and let it install on its own. Once the installation has ended, do not be so quick as to click reboot. > Click the back button on the bottom right hand side, and head over to the List Roms option from earlier. Then, click on the Rom that you just installed, and click Flash Zip, which will flash the Zip file for that individual Rom. Now, flash Google’s apps and services that you have downloaded now Reboot>system. > You should be prompted with the same interface as earlier when you installed MultiRom where it asks you which Rom you want to boot into. Click Cancel, as we do not want to boot into our internal rom. Now you should see your brand new installed Custom Rom name listed in the Boot options. Click on that, and confirm you want to boot into it. > Now the Custom Rom’s default boot animation should appear, so that indicates you’ve done everything right. Note that this simulates the process of a brand new fresh operating system being booted up for the first time, so the boot process should take a while longer, just wait a few minutes until you reach the device setup screen. > In the case that you want to uninstall MultiRom, just boot back into your Internal rom and head over to the Multirom Manager app, and click on the big trash can at the top right corner, as this just means the removal and deletion of MultiRom. Click on confirm delete, and follow the on-screen instructions for uninstallation.

I have installed android x86 in virtualbox. But its not booting now. After installation it pop up a message "Android x86 installed successfully". Then I power off the vm and remove the iso image from it and then power on. When booting the os it only shows this. (This display has been there for 1 hour.)

I am running Android x86 on Virtual Box 5.2.0. After disabling mouse integration and setting up Pointing Device to PS/2 Mouse, I have a mouse when I start Android OS but it is so slow that it is impossible to click on any icon. Is there any solution? Thanks, T