sodcalculator

10 Tech How-To

Install Android Q Beta GSI on Non-Pixel Devices

Guide 10-57918 · Updated · Step by step

Yes, you can install the Android Q beta on many non-Pixel devices using a Generic System Image (GSI), provided your device has an unlockable bootloader and an active Project Treble implementation. This guide explains what a GSI is, how to check compatibility, and the exact steps to flash it, along with the risks and limitations you must accept before starting.

What Is a GSI and Why Does It Matter?

A Generic System Image (GSI) is a system image built from the Android Open Source Project (AOSP) that is designed to run on any device that supports Project Treble. Project Treble, introduced in Android 8.0, separates the Android OS framework from the vendor implementation (drivers and hardware-specific code). This separation allows a single system image to boot on a wide range of devices without needing device-specific modifications.

Google releases official GSI builds for its beta programs, including the Android Q beta. These builds are intended for developers to test apps and compatibility, but they can be flashed by enthusiasts on supported devices. The key requirement is that your device must be Treble-compatible and have an unlocked bootloader.

Checking Your Device’s Compatibility

Before you download anything, verify that your device meets the necessary conditions:

  • Project Treble support: Your device must have shipped with Android 8.0 or later, or received an update to it. You can check by running adb shell getprop ro.treble.enabled – if it returns true, Treble is enabled.
  • Unlockable bootloader: Most devices from Google, OnePlus, Xiaomi, Sony, and Nokia allow bootloader unlocking. Carrier-locked devices or those from Huawei, Honor, and some Samsung models may not.
  • GSI variant matching: Your device’s system partition must be either arm64 or arm (check with adb shell getprop ro.product.cpu.abi), and it must support either aonly or ab system-as-root partitions. You can find this in the device’s partition table or by checking online forums for your specific model.

If any of these checks fail, flashing a GSI will likely result in a bootloop or a non-functional device.

Downloading the Correct GSI Build

Google publishes official GSI builds for the Android Q beta on the Android Developers website. You will see several variants, typically named like arm64_ab, arm64_aonly, arm_ab, and arm_aonly. Choose the one that matches your device’s architecture and partition type. For most modern devices (2018 and later), arm64_ab is the correct choice.

Always download the GSI from the official source (developer.android.com) or a trusted mirror. Avoid random builds from forums, as they may be modified or contain malware. The file will be a compressed image (usually .img or .img.gz). Extract it if needed.

Backing Up Your Current System

Flashing a GSI replaces your entire system partition. This means you will lose all data on the system partition, but your personal files (photos, downloads, etc.) on the data partition are usually preserved. However, it is strongly recommended to back up everything before proceeding:

  • Back up your photos, videos, and documents to cloud storage or a PC.
  • Use the built-in backup feature (Settings > System > Backup) to save app data.
  • If your device supports it, create a full backup using adb backup or a custom recovery like TWRP.

Also, make sure you have the stock firmware for your device downloaded. You will need it if you want to revert to the stable version later.

Step-by-Step Installation Guide

Follow these steps carefully. The exact commands may vary slightly depending on your device and bootloader (fastboot vs. heimdall), but the general process is the same.

  1. Unlock the bootloader: Go to Settings > Developer Options and enable OEM unlocking. Then reboot to bootloader (adb reboot bootloader) and run fastboot flashing unlock (on most devices) or fastboot oem unlock (on older ones). Confirm on the device screen. This will wipe your data.
  2. Reboot to bootloader again: After unlocking, the device will reboot. Go back to bootloader mode.
  3. Flash the GSI: Use the command fastboot flash system .img. For ab devices, you may need to flash to both slots: fastboot flash system_a .img and fastboot flash system_b .img.
  4. Wipe data (recommended): Run fastboot -w to wipe data and cache. This avoids conflicts with the old system.
  5. Reboot: Run fastboot reboot. The first boot may take several minutes – do not interrupt it.

If you encounter a bootloop, try booting into recovery and doing a factory reset from there. If that fails, you may need to flash the stock firmware again and start over.

Common Problems and How to Fix Them

Even with a compatible device, you may run into issues. Here are the most frequent problems and their typical solutions:

  • Bootloop: This is the most common issue. It usually means the GSI variant is wrong or the vendor partition is incompatible. Double-check your architecture and partition type, and try a different GSI build (e.g., aonly instead of ab).
  • Wi-Fi or Bluetooth not working: Some devices require vendor-specific drivers that are not in the GSI. This is a known limitation. You can try flashing a different vendor image from your device’s stock firmware, but this is advanced and risky.
  • Camera fails: Same as above – camera HALs are often proprietary. Some devices have community-made patches, but they are not guaranteed.
  • No sound: Audio HALs are also device-specific. Check if your device has a known working GSI build on XDA forums.
  • Google Play Store shows “uncertified” device: This is expected because the GSI does not pass Google’s certification. You can still use it, but some apps may refuse to run.

Risks and Safety Precautions

Flashing a GSI is a developer-level operation. It carries real risks:

  • Bricking your device: If the flash fails or you flash a wrong image, your device may become unbootable. In most cases, you can recover by flashing stock firmware, but there is a small chance of permanent damage.
  • Loss of warranty: Unlocking the bootloader typically voids your warranty. Some manufacturers offer a way to re-lock it, but not always.
  • Data loss: The unlocking process wipes all data. Make sure you have backups.
  • Security: A GSI is not as thoroughly tested as your device’s stock ROM. It may have bugs that expose you to security risks. Do not use it as your daily driver if you rely on your phone for sensitive tasks.

If you are not comfortable with command-line tools or do not understand the risks, it is safer to wait for the stable Android Q release for your device.

Alternatives to GSI

If a GSI seems too risky or your device is not compatible, there are other ways to try Android Q:

  • Custom ROMs: Many popular devices have custom ROMs based on Android Q (like LineageOS or Pixel Experience). These are often more stable because they include device-specific drivers. Check XDA forums for your device.
  • Android Emulator: You can run Android Q beta in the Android Studio emulator on your PC. This is completely safe and great for testing apps.
  • Wait for the official update: Most major manufacturers will release Android Q (Android 10) for their devices within a few months of the final release. This is the safest option.

Frequently Asked Questions

Will installing a GSI void my warranty?
Yes, unlocking the bootloader and flashing a GSI will almost certainly void your warranty. Some manufacturers allow re-locking, but it is not guaranteed.

Can I go back to my original ROM after flashing a GSI?
Yes, you can flash the stock firmware using fastboot or a tool like Mi Flash (for Xiaomi) or Odin (for Samsung). You will need to download the correct firmware for your device model and region.

Will I get OTA updates on a GSI?
No, GSI builds do not receive over-the-air updates. You will need to manually flash a new GSI when a new beta is released.

Is it safe to use a GSI as my daily driver?
It is not recommended. GSI builds are for development and testing. They may have bugs that affect battery life, performance, or core features like phone calls and mobile data.

What is the difference between arm64 and arm GSI?
arm64 is for 64-bit devices (most modern phones), while arm is for 32-bit devices (older or budget phones). Check your CPU architecture with adb shell getprop ro.product.cpu.abi.

My device is not listed as supported. Can I still try?
You can try, but the risk of bricking is much higher. Only attempt if you have a backup and are prepared to recover with stock firmware.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →