# NexAlloy: an LSPosed module that patches YouTube, YouTube Music and eight other apps

> NexAlloy is ChsBuffer's LSPosed module, built on Morphe and ReVanced components, that applies in-app patches such as ad removal and SponsorBlock. Root is required, and the project is explicit that it is not an official Morphe or ReVanced release.

**NexAlloy/NexAlloy** — ChsBuffer's LSPosed module, powered by Morphe, ReVanced, and beyond. (formerly ReVanced Xposed)

- Repository: https://github.com/NexAlloy/NexAlloy
- Stars: 3,007 · Forks: 135
- Language: Kotlin
- License: GPL-3.0
- Published: 2026-09-24 · Updated: 2026-09-24 · Language: en
- Canonical page: https://hysenlabs.com/projects/nexalloy-nexalloy

## What NexAlloy patches, and who it is written for

NexAlloy is an LSPosed module maintained by ChsBuffer. The README describes it as "ChsBuffer's LSPosed module, powered by Morphe, ReVanced, and beyond", and the repository topics list android, morphe, revanced, xposed, xposed-module, youtube and youtube-music. The problem it addresses is narrow and concrete: stock builds of popular Android apps ship ads, tracking parameters in share links, background playback restrictions and subscription prompts that a user cannot switch off from the app's own settings. NexAlloy hooks into those apps at runtime and changes that behaviour.

The patch list in the README covers ten apps. YouTube gets the largest set, including ad removal, SponsorBlock, removal of background playback restrictions, stripping of the share-link tracking query parameter, navigation button changes, swipe controls, remembered video quality and playback speed, layout and action button hiding, Shorts resume behaviour, codec selection, auto captions, alternative thumbnails and image region restrictions. YouTube Music gets five patches, among them removal of music video ads and enabling exclusive audio playback. Reddit, Google Photos, Photomath, Instagram, Threads, Strava and AllTrails each get between one and three patches, ranging from hiding ads to spoofing a Pixel XL or unlocking subscription features.

The intended user is someone who already runs a rooted device with LSPosed installed. The README states that root access is "strictly required", so this is not a tool for a stock phone. It is also not a general ad blocker: the patches are per-app and per-version, which is why the README directs people who joined the YouTube beta program to try the nightly build before filing an issue.

## How the module hooks apps at runtime

The mechanism follows the standard Xposed model, with the repository layout making the pieces visible. The app/ directory holds the Android application, which is the module itself and the settings interface. The libs/, morphe-patches/ and morphe-patches-library/ directories point at the patch sources, and the stub/ directory holds the compile-time stubs that let the module reference target app classes without shipping them.

At runtime, LSPosed loads the module into the process of each target app. The module then applies the patches the user has enabled. Because the patches are applied in memory, the installed APK of YouTube or Reddit is never modified and does not need to be rebuilt or re-signed. That is the central difference from the ReVanced approach, where the patch is applied to the APK on disk before installation.

Two dependencies are named in the credits. DexKit is described as "a high-performance dex runtime parsing library", which is what lets a module locate methods and classes inside a target app whose obfuscated names change between releases. Morphe is credited as the patch framework. ReVanced is credited for continuing the legacy of Vanced. The README does not document which patches come from which upstream, so the split between Morphe-provided and ReVanced-derived patch logic cannot be confirmed from the repository text alone.

## Getting NexAlloy onto a rooted device

The README gives two download locations and no install command, because this is an Android application rather than a package. The release build is linked from the releases page, and the nightly build is linked from the nightly.link workflow URL. The README does not document a package manager install, a Gradle task for end users, or a checksum to verify the download.

Start by confirming that LSPosed is active. The README states root access is strictly required, so the module has nothing to attach to on an unrooted device. After installing the APK, the module must be enabled in the LSPosed manager and the target apps must be selected in the module's scope. The README does not walk through the LSPosed scope screen, but enabling a module without selecting its target apps is the most common reason a patch appears to do nothing. Force-stop the target app afterwards so the hook is applied on the next launch.

If you are upgrading from the earlier name, the README's migration notice is the part to read carefully. The project kept the original package ID, so the new build installs as an update over ReVancedXposed, but the README states that you "must manually export your settings from the old version and import them into the new one" to keep your configuration. Do that export before replacing the app. The README does not document a rollback path if the import fails.

## Where NexAlloy breaks, and when it is the wrong tool

The most predictable failure mode is app updates. A runtime hook depends on the internal structure of the target app, and when YouTube or Instagram ships a new version, obfuscated class and method names move. DexKit exists to cope with that, but it does not make the patch list version-proof. The README's own instruction that YouTube beta users should try the nightly build before reporting an issue is an acknowledgement that stable releases lag behind app updates. If you run beta builds of a target app, expect to run the nightly module as well.

The second constraint is root. The README states it in bold: root access is strictly required. On a locked-bootloader device, or a device where you are unwilling to root, NexAlloy cannot be used at all. There is no non-root mode and no virtualisation option documented.

The third is support expectations. The README carries an explicit notice that this is not an official Morphe or ReVanced project and that users should not ask those developers for help. Support runs through the Discord server, the Telegram channel, the GitHub wiki FAQ or a new issue. If you need a vendor with a service-level commitment, this is the wrong category of software entirely.

Finally, the patch list is the boundary of what the module does. There is no Spotify entry in the README's patch list, despite search interest in that combination, and no patch for apps outside the ten named. A patch that is not listed does not exist as far as the documentation is concerned.

## NexAlloy compared with patching the APK with ReVanced

The closest alternative is ReVanced itself, which the README credits. The difference is where the patch is applied. ReVanced takes an APK, applies patches to it on a computer or on-device, and produces a modified APK that you install in place of the original. The patched app is self-contained: once installed, it does not need a hooking framework, and it does not need root. The trade-off is that every app update means re-patching and re-installing, and the resulting APK is a rebuilt artefact that you have to manage yourself.

NexAlloy inverts that. The APK on disk stays untouched and the patch is applied at runtime by LSPosed. Updating the target app from the Play Store is normal, and the module is updated separately. The cost is root and a hooking framework, plus the version-coupling described above.

A second alternative is a system-wide ad blocker that filters DNS or traffic rather than hooking the app. That approach is broader and does not care about app versions, but it cannot change in-app behaviour such as background playback restrictions, remembered playback speed or subscription prompts, because those are not network requests. NexAlloy's patch list is full of exactly those in-app changes, which is the gap it fills.

## Maintenance, licence and upgrade cost

The repository is not archived, and the last push was on 2026-09-22. Recent releases follow a tight cadence: 2.0.108 on 2026-09-15, 2.0.109 on 2026-09-19, and a nightly autobuild (Nightly Build be1b443) on 2026-09-22. That cadence matters more here than in most projects, because a runtime hook has to keep pace with the apps it targets. Budget for updating the module when a target app updates, not on a schedule you choose.

The licence is GPL-3.0, stated in the repository and in the LICENSE file at the top level. For a module that links against patch code from Morphe and ReVanced, that choice is consistent with the upstream projects' licensing, but the README does not discuss licence compatibility or what it means for anyone redistributing a build. If you plan to ship a modified build, read the LICENSE file and the upstream licences yourself; this article is not legal advice.

The upgrade path has one sharp edge. Because the package ID was kept from ReVancedXposed, an update installs over the old app, but the README says settings must be exported from the old version and imported into the new one manually. The README does not document an automatic migration, a settings file format, or a rollback procedure. Treat the export as a required step before you update, not an optional one.

## Conclusion

Adopt NexAlloy if you already run LSPosed on a rooted device and want ReVanced-style patches applied at runtime rather than baked into a rebuilt APK. Do not adopt it if your device is not rooted, if you depend on an app the patch list does not cover, or if you want a project whose maintainers will answer support questions; the README states plainly that this is not an official Morphe or ReVanced project. Before installing, verify that your LSPosed framework is active, that you are downloading from the releases page or the nightly workflow link rather than a mirror, and that you have exported settings from any prior ReVancedXposed install, because the README says settings must be exported and re-imported manually.

## FAQ

### What is an Xposed module, and is NexAlloy one?

An Xposed module is a component that a hooking framework loads into another app's process to change its behaviour at runtime. NexAlloy is described in its README as ChsBuffer's LSPosed module, and the repository topics include xposed and xposed-module.

### How do I use NexAlloy?

Install the APK from the releases page or the nightly build link, enable the module in LSPosed, select the target apps in the module's scope, and force-stop the target app so the hook applies on the next launch. The README states that root access is strictly required.

### What is a NexAlloy alternative?

ReVanced is the closest alternative named in the project's own credits. ReVanced applies patches to the APK before installation and does not need root, while NexAlloy hooks the app at runtime through LSPosed and requires root.

## Sources

- [Issues](https://github.com/NexAlloy/NexAlloy/issues)
- [License: GPL-3.0](https://github.com/NexAlloy/NexAlloy/blob/main/LICENSE)
- [NexAlloy/NexAlloy on GitHub](https://github.com/NexAlloy/NexAlloy)
- [README](https://github.com/NexAlloy/NexAlloy/blob/main/README.md)
- [Releases](https://github.com/NexAlloy/NexAlloy/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/nexalloy-nexalloy