OpenGApps is a third-party open source project which automates the collection and generation of Google Services applications to install on devices under your control. More information about the project can be found on their website.

As part of Corellium's Android devices, we have included a streamlined way to download and install the latest stable pico OpenGApps files onto your device, which we have tested for the relevant Android version.

Note: Open GApps is currently in beta for Android 11 and is not yet available for Android 12.

Installing

The button to Install the package is located on the Connect tab, shown below. In order for this button to be enabled, the device must be active, meaning it is powered on and not paused. When you click Install, a Terms Of Service dialog will be presented.

After agreeing to the TOS, the button will become disabled and display the state of the installation, either "Downloading…" or "Installing…".

Once the installation is complete, the device will reboot and the button will indicate that the package is Installed.

After the device has rebooted, you will be able to interact with Play Services, sign in, and install other applications from the Play Store.

Advanced Installation

Warning: If you flash something that is not compatible for the Android version of the VM, or contains untested or buggy scripting, you may render the VM unbootable.

If you would like to install something other than the pico variant, or some other type of OpenGApps customized package, you may utilize the underlying utilities for flashing the archives.

Push the archive you want to flash, utilizing adb or the file browser tab, to the VM at /data/local/tmp/.

Get a shell through either adb or the console tab, then execute the flash-update.sh script with the target archive as the argument. You may optionally pass a second argument, a device build property, to fool the device into thinking it is not an emulator.

/system/bin/flash-archive.sh /data/local/tmp/custom-archive.zip "google/flame/flame:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05"

If this does not work, you may reference the the boilerplate /system/bin/flash-archive.sh file for what is being replaced, remounted and run - which may need to be tweaked for the archive you’re attempting to flash.

Did this answer your question?