Modern smartphones on Android have long switched to 64-bit architecture, but many classic games have remained in the 32-bitformat. This creates a problem: the system simply does not recognize outdated applications, giving the error โApplication not installed.โ Fortunately, there are several working ways to get around this limitation - from using emulators to manually patching APK.
In this article we will look at 5 proven methodswhich will help you run your favorite game even on the latest Samsung Galaxy S24 or Google Pixel 8. You will learn how to determine the bit depth of a game, what tools you will need, and what pitfalls you may encounter along the way. From simple solutions for beginners to advanced techniques for experienced users, everything is here.
Important: not all methods guarantee 100% performance. Some games may launch with graphical artifacts or crash on loading, especially if they use outdated libraries. But in most cases, at least one of the methods will work.
Why 32-bit games do not work on 64-bit Android
Since 2019, Google Play requires developers to publish applications in 64-bit format. This is due to performance and security optimization. However, many old games (especially before 2017) were compiled only for 32-bit architecture.
The main reasons for incompatibility:
- ๐น Lack of ARMv7 support in new processors (for example, Snapdragon 8 Gen 3 completely abandoned 32-bit instructions)
- ๐น Outdated libraries
lib*.soin the APK file of the game - ๐น Limitations Android 12+, where 32-bit processes only work in compatibility
- ๐น Blocking the installation of unsupported applications via
package installer
Interesting fact: even if your device technically supports ARMv7, manufacturers often disable this feature at the software level. For example, OnePlus and Xiaomi actively clean their firmware from outdated code.
โ ๏ธ Attention: On some devices (especially with MediaTek Dimensity), attempting to run 32-bit applications may lead to overheating due to unoptimized emulation. Monitor the processor temperature!
How to determine the bit depth of a game before installing
Before trying to run the game, check its bit capacity. This will save time: if the game is initially 64-bit, then all manipulations with emulators will be useless.
Checking methods:
- Via APK file: Use APK Analyzer (built into Android Studio) or online services like APKMirror. Look for folders
lib/armeabi(32-bit) orlib/arm64(64-bit). - Via Google Play: In the game description, look for a mention of support ARM64 or x86_64.
- Via emulator: Try to install the game on BlueStacks in
32-bit- mode - if it starts, then the game is definitely 32-bit.
| Sign | 32-bit game | 64-bit game |
|---|---|---|
| APK folder | lib/armeabi or lib/armeabi-v7a |
lib/arm64-v8a or lib/x86_64 |
| Minimum Android version | Often up to Android 5.0 | Usually from Android 8.0+ |
| APK size | Less (no duplicate libraries) | More (includes both version) |
| Support for emulators | Works on NOX in compatibility mode | Requires BlueStacks 5+ |
If the APK file has both folders (armeabi i arm64), then the game is universal. In this case, it is enough to force the system to use the 32-bit version (more on this in the next section).
Method 1: Using Android emulators (the most reliable method)
Emulators like BlueStacks or LDPlayer create a virtual environment where you can run almost any game, regardless of the bit capacity of the main system. This is the most universal method, but requires a powerful device.
Step-by-step guide for BlueStacks 5:
Download BlueStacks from the official website|Install with the "Android 7 (32-bit)" mode enabled|Disable automatic updating of the emulator|Download the APK of the game via "Install APK"|In the graphics settings select "OpenGL" instead of "DirectX"-->
For other emulators:
- ๐ฎ LDPlayer: In the virtual device settings, select
Android 5.1 (x86)โit best supports old games. - ๐ฎ NOX Player: Activate the mode
Rootin the settings, then throughADBexecute the command:setprop ro.product.cpu.abilist x86,armeabi-v7a,armeabi - ๐ฎ Genymotion: Create a virtual device with Android 7.0 and architecture
x86.
Advantages of the method:
- โ Works even without Android 14 without root access
- โ Supports saving via the cloud
- โ You can assign control keys to the keyboard
โ ๏ธ Attention: Some anti-cheats (for example, in PUBG Mobile or Free Fire) block launching through emulators. If the game defines a virtual environment, try methods 3 or 4.
Method 2: Patching APK via Termux (for advanced)
If emulators are not suitable, you can manually modify the APKby adding support 64-bit. To do this you will need Termux several utilities.
Instructions:
- Install Termux from F-Droid (version from Google Play is outdated).
- Run the commands:
pkg update && pkg upgradepkg install wget unzip zip
wget https://github.com/iBotPeaches/Apktool/releases/download/v2.7.0/apktool-2.7.0.jar
wget https://raw.githubusercontent.com/krscript/termux-apktool/master/apktool
chmod +x apktool
mv apktool-2.7.0.jar apktool.jar
mv apktool $PREFIX/bin - Unpack the APK:
apktool d your_game.apk -o output - In the folder
output/libcreate a folderarm64-v8aand copy the files there fromarmeabi-v7a. - Collect the APK back:
apktool b output -o patched_game.apk - Sign the APK (install uber-apk-signer via
pkg install uber-apk-signer):uber-apk-signer -a patched_game.apk
This method works for ~60% of games, but can cause:
- ๐ด Graphic bugs (fixed by editing
AndroidManifest.xml) - ๐ด Crashes when loading (if the game checks the integrity of the files)
- ๐ด Loss of multiplayer (due to a change in the APK signature)
If the game after patching gives the error "Failed to load library", try replacing the files in lib/arm64-v8a to similar ones from another 64-bit game (for example PPSSPP). Sometimes this helps to trick the system.
Method 3: Install via ADB (bypass Android restrictions)
The Android system blocks the installation of unmaintained APKs through the standard installer. But if you use ADB (Android Debug Bridge), you can force push the application.
What you will need:
- ๐ฑ Enabled
Developer mode(7 taps on build number inSettings โ About phone) - ๐ฑ Resolution
USB debuggingin developer settings - ๐ฅ ADB Tools on the computer (download from Android SDK Platform Tools)
step-by-step guide:
- Connect your phone to the PC and do:
adb devices(your device should be displayed)
- Install APK:
adb install --force-queryable --fastdeploy your_game.apk - If an error appears
INSTALL_FAILED_NO_MATCHING_ABIS, use the flag:adb install --abi armeabi-v7a your_game.apk
An alternative method for devices with root:
adb shellsu
pm install -r -d --abi armeabi-v7a /sdcard/your_game.apk
โ ๏ธ Attention: On some firmware (for example, MIUI 14+) ADB installation of 32-bit applications is blocked at the kernel level. In this case, only flashing to custom software like LineageOS.
What to do if ADB does not see the device?
1. Check the cable - some USB cables are only for charging.
2. Install drivers for your device (for example Samsung USB Driver or Google USB Driver).
3. Try another USB port (preferably USB 3.0).
4. On your phone in the developer settings, enable Cancel USB debugging authorization, then connect again.
5. If you use Windowsrun ADB as administrator.
Method 4: Custom firmware with 32-bit support
If all else fails, the last option remains - installation of alternative firmware. Some custom assemblies (for example, LineageOS or Pixel Experience) retain support ARMv7 even on new devices.
Suitable firmware:
| Firmware | 32-bit support | Requires bootloader unlocking | Installation difficulty |
|---|---|---|---|
| LineageOS 18.1 | Yes (full) | Yes | Medium |
| Pixel Experience | Partial (depending on the device) | Yes | High |
| Havoc-OS | Yes (with core permissive) |
Yes | For experienced |
| MIUI EU (for Xiaomi) | Yes (in versions up to MIUI 13) | No (for some models) | Low |
Installation instructions LineageOS:
- Unlock the bootloader via
fastboot oem unlock(will delete all data!). - Install custom recovery (TWRP or OrangeFox).
- Download the firmware for your model from the official website.
- Flash via recovery, then install GApps (if you need Google services).
Warnings:
- ๐จ The device warranty will be void.
- ๐จ Risk of "bricking" (especially on devices with Exynos or MediaTek).
- ๐จ Some banking applications (SberBank Online, Tinkoff) will stop working.
Custom firmware is the only way to run 32-bit games on devices with processors Snapdragon 8 Gen 2/3 and Dimensity 9000+, where hardware support for ARMv7 is completely removed.
Method 5: Cloud gaming as an alternative
If all the previous methods did not work, consider cloud servicesThey allow you to play old games on. remote servers, broadcasting the picture to your smartphone.
The best services for retro games:
- ๐ฎ Vortex.gg - supports GTA: SA, Bully, Max Payne (there is a free plan).
- ๐ฎ Boosterroid - specializes in mobile games (including old versions Clash of Clans).
- ๐ฎ Shadow PC โa virtual Windows PC where you can install any game (from
$15/month). - ๐ฎ Rainway โstreams games from your home PC to your phone.
Advantages of cloud gaming:
- โ No need to modify the phone
- โ Works even on weak devices
- โ Support for gamepads and keyboards
Cons:
- โ Requires stable Internet 15+ Mbit/s
- โ Possible lags (depending on the server)
- โ Not all games are available in the catalog
For minimal lags Vortex.gg use:
- ๐ถ Connection via
Wi-Fi 5 GHzor4G/5G - ๐ฑ Performance mode in the phone settings
- ๐ฎ Gamepad (Xbox Controller or DualSense for precise control)
Common errors and their solutions
Even after successful installation, the 32-bit game may not start. Here are the problems and how to fix them:
| Error | Cause | Solution |
|---|---|---|
App not installed |
The system blocks unmaintained APK | Use ADB install with flag --abi armeabi-v7a |
| Black screen on startup | Incompatibility with OpenGL ES 3.0+ | In the developer settings, enable Forced use of GPU rendering |
Failed to load library"libil2cpp.so" |
The 64-bit version of the library is missing | Replace the file with a similar one from another game (for example, Among Us) |
| Crash when loading | Checking file integrity (anti-tamper) | Use Lucky Patcher to disable license verification |
INSTALL_FAILED_INVALID_APK |
Damaged or incorrectly signed APK | Rebuild the APK via APK Editor with a new signature |
If the game starts, but works with artifacts:
- ๐ง Try changing the screen resolution via
ADB:adb shell wm size 1280x720 - ๐ง Disable anti-aliasing in the graphics settings (if there is such an item).
- ๐ง Use GLTools to force it on
OpenGL 2.0.
โ ๏ธ Attention: On devices with Dynamic RAM Expansion (for example, Realme GT 2 Pro) 32-bit games can cause overrunning the RAM. memorydisable this function in the settings before starting.
FAQ: Answers to popular questions
Is it possible to run a 32-bit game on Android without root access?
Yes, but with limitations. The most reliable methods without root:
- Use emulators (BlueStacks, LDPlayer).
- Install via
ADBwith the flag--abi armeabi-v7a. - Use cloud services (Vortex.gg).
It will not work without root:
- Patch system libraries.
- Install custom firmware.
- Bypass integrity checks in games with anti-cheat.
Why does the game start, but crashes after 5 minutes?
This is a typical problem with:
- CPU overheating โ 32-bit games often load the cores suboptimally. Try limiting FPS through Game Tuner.
- Lack of memory - close all background applications or use Greenify.
- License check - some games (for example Asphalt 8) require connection to servers Google Play. Use Freedom APK to bypass.
For diagnostics, check the logs through:
adb logcat | grep -i"your.game.package"
What games definitely cannot be run on 64-bit Android?
List of "untouchable" games (problems at the kernel or anti-cheat level):
- PUBG Mobile (blocks emulators and modified APKs)
- Call of Duty: Mobile (checks integrity
libunity.so) - Genshin Impact (requires
ARM64i Vulkan) - Fortnite (uses Epic Online Servicesthat do not work in emulators)
- Games on Unity 2020+ (use
IL2CPPwith 64-bit optimizations)
For these games, the only option is cloud gaming or search port versions (for example, PUBG: New State instead of the classic PUBG Mobile).
How to transfer saves from the emulator to the real one device?
Saves are usually stored in:
/data/data/package name/โ for most games/sdcard/Android/obb/โ for additional files/sdcard/game_name/โ for some MMORPG
Transfer instructions:
- In the emulator, copy the save folder to the PC (for example, via ES File Explorer).
- Connect your phone to the PC and manually transfer the files to the appropriate directories.
- Set access rights:
adb shellsu
chmod -R 777 /data/data/package name/
For games with cloud saves (Clash of Clans, Brawl Stars) just log in via Google Play Games or Facebook.
Is it safe to use patched APKs?
The risks depend on the source of the APK:
- ๐น Self-patched APK (via APKTool) - are safe if you have not added third-party code.
- ๐น APK from torrent trackers โhigh risk of built-in miners or spyware.
- ๐น APK with modified purchases โmay contain Trojans (for example, Xavier).
How to check an APK for viruses:
- Upload the file to VirusTotal.
- Check the file hash via APK Analyzer โit must match the original.
- Install Malwarebytes to your phone and scan the installed application.
It is best to patch the APK yourself or download from trusted sources (APKMirror, APKPure).