The modern ecosystem Android is constantly evolving, and standard methods of installing applications are gradually becoming a thing of the past. If previously the user only had to find one file .apk and click on it, today the package architecture has become more complex. This is where (Split APKs Installer) comes into the picture - a utility that has become an indispensable tool for advanced users and enthusiasts. SAI (Split APKs Installer) is a utility that has become an indispensable tool for advanced users and enthusiasts.
Many people are faced with a situation where an installation file downloaded from a reliable source refuses to install (refuses to install) through a standard package manager. Errors like INSTALL_FAILED_UPDATE_INCOMPATIBLE or messages about processor architecture incompatibility frighten beginners. Installation via SAI on Android solves these problems, allowing you to correctly deploy complex application structures consisting of several parts.
In this article we will analyze in detail why there is a need for such tools, how the mechanism works Split APKs and we will describe step by step the process of installing software through this manager. You will learn how this method differs from the classic one and in which cases you simply cannot do without it.
Why regular APK files are becoming a thing of the past
Traditional format .apk was a single archive containing all code, resources and libraries for all possible device configurations. This meant that the user was downloading gigabytes of unnecessary data: graphics for low-resolution screens, language packs that he did not need, and libraries for processors that he did not have. Google implemented a format to streamline this process. Now one large file is uploaded to Google Play, but only that part of it that is ideal for a specific smartphone model is sent to the user’s device. This saves traffic and memory space.
Google introduced the format Android App Bundle (.aab) to optimize this process. Now one large file is uploaded to Google Play, but only that part of it that is ideal for a specific smartphone model is sent to the user’s device. This saves traffic and memory space.
However, when you download an application from a third-party resource (for example, APKMirror), you often receive not one file, but a set of several. .apk. These are the so-called Split APKs. The standard Android installer does not know how to put them together automatically, requiring the intervention of special utilities.
⚠️ Attention: An attempt to install only the basic file from a set of Split APKs through a standard explorer will result in an error or installation of an “empty” application, which will immediately crash upon launch.
It was created to work with such sets. SAI. It acts as an intermediary that correctly reads the manifests of all parts of the package and sends them to the system installer in a single stream.
What is SAI and how does it work technically
Split APKs Installer is open source software with a license GPLv3that uses the system API PackageInstaller. Unlike root managers, SAI does not require superuser rights for its main function, although the presence of root access expands its capabilities.
The principle of operation of the application is based on creating an installation session. When you select files for installation, SAI asks the system to create a temporary container. Then it sequentially writes data from each selected file into this container: the base module, screen configuration, language resources and native libraries.
After recording of all parts is completed, the session is finalized, and the Android system perceives this set as a single whole. To the user, this process looks like a normal installation, but there is complex coordination of data flows going on under the hood.
It is important to note support for various file sources. You can select packages directly from the internal memory, through the built-in file manager, or even directly from cloud storage if they are connected through the system interface.
Use the "App Inspector" function inside SAI to see which modules an already installed application consists of. This will help you understand the structure of modern apps.
Step-by-step guide: installing an application via SAI
The installation process may seem complicated only at first glance. In fact, the algorithm of actions is extremely simple and takes less than a minute if you already have downloaded files.
First you need to launch the application itself SAI. When you first launch it, it will ask for permission to install unknown applications. This is a standard Android security procedure that must be confirmed in the system settings.
Next, click the button Install APK in the main menu. The system file browser will open. Here you need to select all the files related to one application. They usually have similar names or are in the same folder.
- 📂 Click on the base file (often called
base.apkor contains the name of the application). - 📱 Select configuration files (for example,
config.arm64_v8a.apkfor your processor). - 🌐 Mark language packs if they are in the archive (for example,
config.ru.apk). - ✅ Click the "Select" button or check mark to confirm the list.
After selecting the files, SAI will analyze their compatibility. If all parts fit together, the system installation window will appear. Click Install and wait for the process to complete.
☑️ Split APK installation algorithm
If the installation was successful, you will see a corresponding notification, and the application icon will appear in the launcher. In case of an error, SAI will provide a detailed log with the problem code, which greatly simplifies diagnostics.
Critical differences between operating modes: Shizuku and Root
Although SAI works in basic mode without additional settings, its functionality can be significantly expanded. There are two main methods of privileged access for this: Root and Shizuku.
Root mode gives the application full superuser rights. This allows SAI to install applications on the system partition, remove bloatware, and bypass some signature checks. However, obtaining root access may lead to loss of warranty and disruption of banking applications.
An alternative is to use the service Shizuku. This is a modern method that allows apps to use system APIs with elevated privileges without completely rooting the device. SAI uses Shizuku to speed up the installation process and work with more complex package formats.
| Features | Basic mode | Shizuku mode | Root mode |
|---|---|---|---|
| Requirements | No | Setup via ADB/Wi-Fi | Unlocked bootloader |
| Installation speed | Average | High | Maximum |
| Uninstalling system applications | No | User only | Full deletion |
| Security | High | High | Medium (risk of errors) |
For most users, the optimal choice is setting Shizuku. This gives a balance between functionality and security, without requiring deep intervention into the system.
How to activate Shizuku for SAI?
Download the Shizuku application from the Play Market. Launch it and follow the instructions "Run via wireless debugging". You'll need to enable Developer Mode on your phone, find "Wi-Fi Debugging" and enter the pairing code that Shizuku will show. After successful connection, return to SAI and select the Shizuku operating mode in the settings.
Possible errors and methods for eliminating them
Even when using advanced tools, failures may occur. Understanding error codes helps you quickly solve the problem without having to reset your phone.
One of the most common problems is a signature error. This happens if you try to update an application installed from the Play Market with a version from a third-party source, and their cryptographic signatures do not match. The system blocks the installation for security reasons.
An architecture incompatibility error is also common. If you downloaded the package for processors x86, and your smartphone runs on ARM, installation is physically impossible. SAI usually warns about this before the process begins, but sometimes the check does not proceed correctly.
⚠️ Attention: If you see an error INSTALL_FAILED_VERSION_DOWNGRADE, this means that you are trying to install a version of the application that is older than the one already installed on the system. Android prohibits rolling back versions without special rights.
To resolve problems with file access rights in new versions of Android (11, 12, 13+), make sure that you give SAI permission to manage all files in a special settings menu, and not just access to media.
Sometimes clearing the cache of the installer itself helps. Go to Settings → Applications → Show system processes → Package Manager and clear its cache. This will not delete your data, but will reset stuck installation sessions.
90% of installation errors via SAI are associated with either mismatched developer signatures or an attempt to install an incomplete set of Split APK files.
Security and file integrity check
The use of third-party installers increases the user's responsibility for the sources of files. SAI is only a delivery tool, it does not check the contents of the APK for viruses or malicious code.
Before installing any package, especially a complex Split APK structure, it is recommended to check the hash of the file (MD5 or SHA-256), if it is provided by the source author. This ensures that the file was not damaged during downloading or tampered with.
Avoid downloading applications from dubious forums or file hosting services without a reputation. Official mirrors like APKMirror or F-Droid conduct moderation and verification of signatures, which minimizes risks.
Remember that installing applications from unknown sources always carries a certain risk. Use anti-virus software to periodically scan your device, especially after mass installation of software from external sources.
⚠️ Attention: Never give the SAI application access to your personal photos, contacts or messages if it asks for it. The installer only needs rights to read installation package files and install applications.
Regularly update the SAI application itself. Developers are constantly closing vulnerabilities and improving compatibility with new versions of the Android operating system.
Frequently asked questions (FAQ)
Can I install SAI on Android without root access?
Yes, absolutely. The basic functionality of SAI fully works on regular devices. root access is needed only for specific tasks, such as deleting system applications or installing to protected memory sections.
What is the difference between SAI and the standard Google installer?
The standard installer cannot correctly process sets of Split APKs files, requiring installation of each one separately (which is impossible). SAI combines them into a single session, simulating the work of Google Play when installing an App Bundle.
Why does SAI ask for the "Access to all files" permission?
Starting with Android 11, the system severely limits app access to the file system. In order for SAI to see and read installation files in any folders (not just Download), it needs this extended permission.
Is it safe to use Shizuku mode?
Yes, Shizuku is a secure and open source tool. It provides temporary privileges through ADB debugging and does not provide permanent root access, which reduces the risk of system hacking compared to full Root.
What to do if the installation freezes at 90%?
Usually this means a problem with writing one of the modules. Try restarting your device, clearing the SAI application and Package Manager cache, and then try again. Also check your free disk space.