Gapps Error Code 70 Fix: 5 Working Solutions

Gapps error code 70 appears when flashing a Google Apps (GApps) package in a custom recovery like TWRP, and it means the installer could not find a compatible Android version or architecture on your device. The fix is to download the correct GApps package for your device’s Android version and CPU architecture, then flash it again. Below are the exact steps and background to resolve it for good.

What Is Gapps Error Code 70?

Error 70 is a compatibility check failure that occurs during the GApps installation script. The script reads your device’s ro.build.version.sdk (Android API level) and ro.product.cpu.abi (CPU architecture), then compares them with the package you are flashing. If they do not match, the installer aborts with “Error 70: Wrong Android version or architecture.”

This is not a corrupt download or a hardware problem. It is a deliberate safety check to prevent you from flashing a package that would not work, which could cause boot loops or missing Google apps. The error is common among custom ROM users who download the wrong GApps variant by mistake.

Why Does Error 70 Happen?

Three main causes trigger error 70:

Mismatched Android version: You flashed a GApps package built for Android 13 on a device running Android 12, or vice versa.
Mismatched CPU architecture: Your device uses an ARM64 processor, but you downloaded an ARM or x86 package.
Outdated recovery or ROM metadata: A custom ROM might report an unusual API level, or your recovery might not read the build properties correctly.

Most users encounter the first two. The fix is straightforward once you know your device’s exact specs.

How to Fix Error 70 (Step-by-Step)

Identify your device’s Android version and architecture. Go to Settings > About Phone and note the Android version (e.g., 13). For architecture, install a simple app like CPU-Z or run adb shell getprop ro.product.cpu.abi in a terminal. Common values: arm64-v8a, armeabi-v7a, x86, x86_64.
Download the correct GApps package. Visit the official Open GApps website (opengapps.org). Select your platform (ARM64, ARM, x86, x86_64), Android version (e.g., 13.0), and variant (nano, pico, stock, etc.). The package name will clearly state these, like open_gapps-arm64-13.0-nano-20250301.zip.
Re-download the package. If you already downloaded one, delete it and download again to rule out a corrupted file. Use a PC and transfer via USB to avoid partial downloads.
Flash the correct package in recovery. Boot into TWRP (or your custom recovery), tap Install, select the new GApps zip, and swipe to flash. Do not wipe anything before flashing GApps—only wipe Dalvik/ART Cache and Cache after flashing.
If error persists, check ROM compatibility. Some ROMs (especially Android 14+ or unofficial builds) may report an unusual API level. Try a different GApps package like BiTGApps or MindTheGapps, which sometimes handle edge cases better.

Common Mistakes That Cause Error 70

Downloading the wrong variant: Users often pick “ARM” instead of “ARM64” because they confuse it with the more common term. Always check with a system info app.
Mixing Android versions: If you just updated your ROM from Android 12 to 13, you must download a GApps package for Android 13. The old package will not work.
Using a package for a different Android version than the ROM: Some ROMs are based on a different version than the official Android number. Check your ROM’s release notes to confirm the exact Android version.
Flashing GApps before the first boot: While not directly causing error 70, flashing GApps after you have already booted the ROM can cause other issues. Always flash GApps immediately after flashing the ROM, before rebooting.

What to Do If the Fix Doesn’t Work

If you have verified the architecture and Android version and still get error 70, try these in order:

Update your recovery. An outdated TWRP might not read build properties correctly. Download the latest TWRP for your device from the official TWRP site.
Check for a known ROM issue. Search your ROM’s XDA thread or official forum for “error 70” to see if other users have reported it. There may be a specific workaround or a patched GApps package.
Use a different GApps provider. Open GApps is the most common, but MindTheGapps (used by LineageOS) and BiTGApps are reliable alternatives. Download the one that matches your ROM’s recommendation.
Re-download the ROM and GApps from scratch. Sometimes the ROM zip itself is corrupted, causing the build properties to be read incorrectly. Re-download both files and flash again.

How to Prevent Error 70 in the Future

Prevention is about building a habit of checking before flashing:

Always note your device’s architecture and Android version in a text file on your PC.
Download GApps from the official Open GApps site—it generates the correct package name automatically.
After downloading, verify the file size matches the one on the website (a quick way to catch corrupted downloads).
If you flash ROMs frequently, keep a folder with the correct GApps package for your device and Android version, so you don’t have to re-download each time.

Frequently Asked Questions

Does error 70 mean my device is not supported?

No. Error 70 only means the GApps package you selected does not match your device’s Android version or CPU architecture. Your device is almost certainly supported—you just need the correct package.

Can I force-install GApps and ignore error 70?

No. The error is a safety check. Forcing the install (e.g., by modifying the script) will likely cause boot loops, force closes of Google apps, or a system that never fully boots. Always use the correct package.

How do I find my device’s CPU architecture without an app?

Connect your phone to a PC with USB debugging enabled and run adb shell getprop ro.product.cpu.abi. It will output something like arm64-v8a. You can also check your device’s specifications on the manufacturer’s website or a trusted review site.

What is the difference between ARM, ARM64, and x86?

These are CPU instruction set architectures. Most modern Android phones use ARM64 (64-bit ARM). Older budget phones may use ARM (32-bit). Intel-based tablets and some Chromebooks use x86 or x86_64. GApps packages are compiled for each architecture, so you must match yours.

Can I flash GApps after booting the ROM once?

Technically yes, but it is not recommended. Flashing GApps after the first boot can cause app conflicts and force closes. The safest method is to flash the ROM and GApps in the same recovery session, before rebooting.

Does the GApps variant (pico, nano, stock) affect error 70?

No. The variant only changes which Google apps are included. Error 70 is based solely on Android version and architecture, so any variant will work as long as those two match.

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 →