FiorenMas Non-Root Builds: Pre-Patched APKs for ReVanced, Extended, and Morphe

What This Repository Actually Solves

ReVanced and its forks patch official apps by applying a set of patches to a stock APK. The official tools, such as the ReVanced Manager or the CLI, require the user to download the correct base APK, select patches, and run the patching process. That workflow is a barrier for many people. This repository removes the patching step entirely. It hosts pre-patched APKs for a long list of apps, including YouTube, YouTube Music, Facebook, Twitter, Instagram, TikTok, Twitch, Reddit, Discord, and many more. The README states its purpose directly: the scripts are open-source but difficult for most users, so the author created an easier way. The target audience is the non-technical Android user who just wants a modded app and does not care about the patching internals.

How the Build Pipeline Works

The repository is a set of shell scripts that automate the patching process. The description says it builds in real time, about 10 minutes after a patch release. That means the maintainer or a CI workflow watches the patch repositories for new releases, downloads the corresponding base APKs, applies the patches, and uploads the resulting APKs to the GitHub releases section. The README clarifies that this repository does not create new releases; it only releases new files. So the release page is just a bucket of APKs, not a versioned release with changelogs. The patching sources are three: Morphe patches, ReVanced Extended forked by anddea, and the older ReVanced patches, which the README marks as "Outdated patches." The user does not need to know which patch does what, only which app and architecture to pick. The README also notes that APK files used for patching are downloaded from a trusted site, though it does not specify which site.

Getting the Right APK: Architecture and Variants

The download process is deliberately simple. You pick the app, then choose between ReVanced or ReVanced Extended, then select your phone's CPU architecture. If you do not know the architecture, the README says to choose All Architectures. That option produces a universal APK that works on any device, at the cost of larger file size. For each app, the repository provides separate APKs for arm64-v8a, armeabi-v7a, x86, and x86_64. For YouTube, there are also lite versions, which the README defines as versions with unnecessary things removed, such as only an English interface and removed unused screen DPI from split APKs. There is also a stable and a beta variant for each. The README warns that beta versions use dev patches, not beta APK files, and that beta versions share the same package name as stable, so installing one overwrites the other. That is a practical detail worth remembering before you install both.

The MicroG Requirement for Google Apps

A key constraint applies to YouTube, YouTube Music, and Google Photos. These apps rely on Google Play Services for authentication. The patched versions cannot use the standard Play Services, so the README instructs users to download and install MicroG RE from the MorpheApp repository. MicroG is a reimplementation of Google's proprietary services that provides a compatible login and push notification layer. Without MicroG, the patched YouTube app will not let you sign in to your account. This is an extra step that the README mentions in a note, but it is easy to miss. For users who only want ad-blocking and background playback without logging in, MicroG may not be necessary, but for full functionality it is mandatory. The repository links to the MicroG RE releases page, not to the original microG project, which is another sign that this project is tied to the Morphe ecosystem.

Trust, Safety, and the Absence of Verification

The README claims the repository is safe because all code is open-source and the APK files are downloaded from a trusted site. That claim is not verifiable from the repository alone. The user has no way to confirm that the patching process produced exactly what the scripts intend, or that the downloaded base APKs were not tampered with. The repository does not provide checksums or signatures for the APKs in the README, nor does it describe a reproducible build process. This is a genuine limitation. If you are security-conscious, you should treat these APKs as you would any third-party binary. The GPL-3.0 license applies to the scripts, not to the patched APKs, which contain proprietary code from Google and other vendors. The README also includes a note that the license is owned by the creator and asks users to support the original authors if they like a modded app. That is a legal gray area, though the project itself is not claiming ownership of the patched apps.

Maintenance Status and a Real Alternative

The last push to this repository was on June 1, 2023. That is over two years before this article. The release page shows a single release from that date. The project appears unmaintained. The README still lists apps and links, but the underlying patch repositories, such as Morphe and anddea, have likely moved on. New Android versions and app updates will break these APKs. The "real-time" claim in the description no longer holds. A real alternative is to use the official ReVanced Manager or the ReVanced CLI directly. The official tools let you apply the latest patches to the current version of an app, and they let you choose exactly which patches to include. The trade-off is complexity: you need to source the base APK, manage patch versions, and run the patching process. For a user who is comfortable with a command line, the CLI is a more sustainable path. For a non-technical user, this repository was convenient when it was active, but its age makes it unreliable today.

The Bottom Line for Different Users

If you are a casual user who wants a patched YouTube APK and you found this repository through a search, the first thing to check is the date of the last release. A June 2023 build will not work with the current YouTube app version, and installing it may trigger a forced update or simply fail to run. If you are a developer or a tinkerer, this repository is not useful to you except as an example of how to automate patching with shell scripts. The real value of this project is historical: it shows a simple distribution model for patched apps. But as a practical tool, it is stale. The README's promise of a build within 10 minutes of a patch release is no longer true. Verify the last commit date before downloading anything, and if you need current patches, use the official ReVanced Manager or build your own with the CLI. The repository is a snapshot, not a live service.

Editorial conclusion

Adopt this repository if you want patched YouTube, YouTube Music, or any of the listed apps without running the ReVanced CLI or manager yourself, and you accept the trust model of downloading pre-built APKs. Do not use it if you need the latest patches immediately or if you require a specific patch configuration beyond stable or beta. Before installing, verify the APK's signature against the repository's checksums (if provided) and confirm the patch source (Morphe, anddea, or ReVanced) matches your preference. The project stopped receiving pushes in June 2023, so check the last commit date before relying on it for current versions.

Official sources

1. Official README
2. Project repository
3. Release notes