FiorenMas/Revanced-And-Revanced-Extended-Non-Root: prebuilt patched APKs without the patcher
Real-time repository build Morphe, Revanced and Revanced Extended about 10 minutes after patch release
At a glance
- What is it?
- This repository does not build anything at patch time for you. It publishes finished APKs for ReVanced, Morphe and ReVanced Extended variants, split by CPU architecture, and the README explains how to pick one. The last push was on 2023-06-01, so treat it as a static download index rather than a maintained pipeline.
- Who is it for?
- Adopt it if you want a patched YouTube or YouTube Music APK on a non-rooted phone and you are willing to trust a third party's build instead of running the patcher yourself. Skip it if you need a currently patched build, if you want to control which patches are applied, or if you cannot verify the provenance of a downloaded APK.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 10 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 25, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What the repository actually ships
The README is explicit that this is not a patcher. It says the repository "does not create new releases; it only releases new files." The project description frames the scripts as open source, but the user-facing product is a set of APK files attached to a single release named "all", dated 2023-06-01. There is no build you run, no patch selection screen, and no local Java toolchain to install.
The intended audience is someone who wants a patched YouTube or YouTube Music on a phone that is not rooted, and who does not want to work through the ReVanced patching workflow themselves. The README says the underlying scripts are "very difficult to use for most users. That's why I created this repository to provide an easier way." That is the whole value proposition: the patching work is done upstream and the result is handed over as a file.
The app list is long. Beyond YouTube and YouTube Music the jump list covers Facebook, Messenger, Twitter, Instagram, Threads, TikTok, Twitch, Reddit, Lightroom, Tumblr, SoundCloud, Duolingo, Viber, Discord, Proton Mail, Prime Video, Telegram, Google Photos, Adguard, Smart Launcher, WPS Office, Proton VPN, Psiphon, Google News, Photomath, Truecaller, EyeconCaller, Zalo, CamScanner, Battery Guru, Brave Browser, RAR, TeraBox, Strava, Waze, Pixiv, Bilibili, Solid Explorer, Nova Launcher, Tasker, FX File Explorer, MyFitnessPal and Google Recorder. Whether every one of those entries still has a live file behind it is not something the README states.
How the download matrix is organised
For YouTube the README presents a table with two columns, Stable version and Beta version, and rows for All Architectures, Arm64-v8a, Armeabi-v7a, x86 and x86_64. The filenames follow that pattern directly, for example youtube-morphe.apk for the Morphe all-architecture stable build and youtube-beta-arm64-v8a-morphe.apk for the beta arm64 build. The Extended variant forked by anddea uses a different naming convention, inserting "stable" or "beta" after the app name, as in youtube-stable-anddea.apk and youtube-beta-x86_64-anddea.apk.
One detail worth reading carefully: the README states that beta versions mean using dev patches, not beta APK files. So the beta column is not a beta of YouTube. It is the same stable app patched with development patches from the patch repository. The README also warns that beta and stable share the same package name, so installing a beta build will overwrite the stable one. There is no side-by-side install.
A Lite variant exists for YouTube under a collapsed section. The README describes it as "a version with unnecessary things removed. For example, it might only have an English interface and remove unused screen DPI from split APKs." Only arm64-v8a and armeabi-v7a appear in the Lite table, so Lite is not available for x86 or x86_64.
Installing a prebuilt APK and the MicroG RE dependency
There is no build step, so installation is a download followed by a sideload. The README's own instruction is to choose the app, then choose the phone's CPU architecture, and if you do not know the architecture, choose All Architectures. The files live under the release tag all, in the repository's releases download path.
The one hard prerequisite the README states is MicroG RE. For YouTube, YouTube Music or Google Photos you must download and install it first, from the MorpheApp/MicroG-RE repository. Without it the patched apps have no account layer to sign in against. The README does not give a command for this step; it points at that repository's releases.
This repository documents no command-line install at all. Everything in the README is a link to a file, so the download and the install happen through the browser, a file manager, or whatever sideloading tool you already use. Treat the release page as the entry point rather than expecting a documented CLI. Expect the install to fail with a signature mismatch if a differently signed build of the same package is already present. The README's note about stable and beta sharing a package name is the relevant warning here: you may need to uninstall the existing copy first, which also removes its local data.
The staleness problem is the main limitation
The last push to this repository was on 2023-06-01, and the only release is tagged all on the same date. Patch repositories move; the README itself links out to MorpheApp/morphe-patches, anddea/revanced-patches and revanced/revanced-patches for the actual patch sources. When those upstream projects change their patch sets, this repository's attached APKs do not change with them, because the README says it does not create new releases.
That has practical consequences. A patched YouTube APK is pinned to the YouTube version it was built against, and YouTube's server-side changes and client updates can break patches over time. A build from mid-2023 is old by any measure. If a patch stops working against the current YouTube backend, nothing in this repository fixes it.
The second limitation is trust. The README asserts that "the APK files used for patching are downloaded from a trusted site, so it is totally safe for you to use." That is an assertion, not a verifiable claim from the reader's side. You are installing a binary that someone else compiled and signed. The source scripts are in the repository's src/ directory, but reading them does not prove that the attached APK matches what those scripts would produce. If you need that guarantee, this is the wrong tool and you should patch locally.
The third limitation is scope. This is Android-only, non-root oriented, and there is no desktop, iOS or web component. It also cannot help you if your target app is not in the jump list.
ReVanced Extended versus the standard patch set
The README offers two patch lineages for YouTube side by side. The Morphe column links to MorpheApp/morphe-patches. The other column is labelled "Revanced Extended forked by anddea" and links to anddea/revanced-patches. A third, collapsed section labelled "Outdated patches" points at revanced/revanced-patches.
The difference that matters to a user is which patch set is baked in, and the README does not enumerate the patches in either. Extended historically carried a larger set of customization options than the standard patches, but that is a property of the upstream patch repositories, not of this download index, and you would need to read those repositories to know what you are getting. What this repository gives you is a filename that tells you which lineage produced the APK: the -morphe suffix versus the -anddea suffix.
If you are choosing between the two, the honest answer from what is documented here is that you cannot decide from this README alone. The README links the patch sources and stops there. Pick based on the upstream patch repository you actually want, then come back for the prebuilt file.
How it compares with patching locally or with NewPipe
The direct alternative is running the patcher yourself, which is what the ReVanced tooling is designed for. The difference in approach is who compiles and who signs. Patching locally means you supply the base APK, choose the patches, and the resulting binary is built on your machine, so you know exactly what went into it. This repository inverts that: you trade control and freshness for not having to run a Java-based patcher and manage apk sources. If you can run the patcher, the local route removes the trust question entirely.
The other alternative is NewPipe, which is a separate client rather than a patch applied to the official app. NewPipe does not reuse Google's client and therefore does not need MicroG RE or a Google account for basic playback. The trade-off runs the other way: you lose the official app's UI, its account integration and anything that depends on Google's playback stack. A patched YouTube APK remains YouTube, which is precisely why it needs MicroG to sign in. Neither approach is a superset of the other.
Licence and the cost of staying current
The repository is licensed GPL-3.0, and the LICENSE file sits at the top level. That covers the scripts in this repository. It does not automatically cover the APKs attached to releases, which are built from patched third-party applications. The README makes a related point in its own words: "License owned by creator. If you like any modded app, please support the original author." Treat the licence status of any individual APK as something to check at its upstream patch repository, not something this repository settles. This is not legal advice; if redistribution matters to you, read the upstream licences.
The upgrade cost is the part people underestimate. Because the repository does not publish new releases, there is no upgrade path inside it. Upgrading means going back to the upstream patch repositories, waiting for a new patched build to appear somewhere, or building it yourself. Each install also carries the package-name collision the README describes, so moving between stable and beta channels means uninstalling and losing app data. Budget for that friction, not just for the initial download.
Editorial conclusion
Adopt it if you want a patched YouTube or YouTube Music APK on a non-rooted phone and you are willing to trust a third party's build instead of running the patcher yourself. Skip it if you need a currently patched build, if you want to control which patches are applied, or if you cannot verify the provenance of a downloaded APK. Before installing anything, check the release timestamp on the file you pick, confirm your phone's CPU architecture rather than defaulting to All Architectures, and install MicroG RE first for YouTube, YouTube Music and Google Photos.
Frequently asked questions
Is ReVanced Extended legal to use?
The repository does not address legality. It is licensed GPL-3.0 and the README notes that licence is owned by the creator, asking users to support the original author of any modded app. Questions about whether patching a given app is permitted in your jurisdiction are not answered by the README.
Is ReVanced Extended open source?
The README states that all the code is open source and the repository carries a GPL-3.0 licence with a LICENSE file at the top level. The patch sources it links to, such as anddea/revanced-patches and MorpheApp/morphe-patches, are separate repositories with their own licensing.
Is it safe to use ReVanced microG services?
The README says the APK files used for patching are downloaded from a trusted site and calls the repository totally safe to use, and it directs YouTube, YouTube Music and Google Photos users to install MicroG RE from MorpheApp/MicroG-RE. That is the project's own claim rather than an independent verification, and the README gives no further detail about MicroG RE itself.
Which is better, ReVanced or NewPipe?
The README does not compare them. What it does show is that the patched apps here are built on the official clients and require MicroG RE for YouTube, YouTube Music and Google Photos, whereas NewPipe is not mentioned anywhere in the repository.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/fiorenmas-revanced-and-revanced-extended-non-root)