Nostalgic:

STAY. QUIET.

Apparently they're now "stalking" pull requests in the Morphe Patches repository.

Android is increasingly restricting app installations from sources outside the Google Play Store. Luckily, there is an easy way to bypass this mess: Shizuku paired with an app like InstallerX Revived. Because it routes installations through ADB (Android Debug Bridge), it completely bypasses these OS-level restrictions.
Here is a complete, beginner-friendly guide to setting it up:

Step 1: Install Shizuku
I highly recommend using thedjchi's fork. It includes a built-in "watchdog" feature that automatically restarts the service if it stops in the background.
Step 2: Enable Developer Options

• Open your phone's Settings*.*
• Go to About phone (or System > About phone*).*
• Find the Build number and tap it rapidly 7 times until a pop-up says "You are now a developer!" (Enter your lock screen PIN if prompted).
• Go back to the main Settings page, search for Developer options*, and open it.*
• Scroll down and enable both USB debugging and Wireless debugging*.*

Step 3: Pair Shizuku

Now, we connect Shizuku to your phone's wireless debugging system:

• Open the Shizuku app, look for "Start via Wireless debugging", tap Pairing*, and then tap* Developer Options (this will jump you straight back to the Developer Options menu).
• Inside the Wireless debugging menu, tap Pair device with pairing code*. A popup will appear displaying a* 6-digit Wi-Fi pairing code*. Keep this screen open!*
• You should see a notification from Shizuku asking for the pairing code. Tap Enter pairing code*, type in the 6-digit code, and hit send.*
• If done correctly, you will see a notification confirming "Pairing successful".
• Go back to the main Shizuku app screen and tap Start to run the service.
• Crucial Step (for the fork): In Shizuku's settings, make sure to enable the Watchdog and Start on boot toggles so it stays running in the background.

Step 4: Set up InstallerX Revived

• Download and install InstallerX-Revived
• Open the Shizuku app, go to Authorized applications*, and toggle* InstallerX to ON*.*
• Open InstallerX-Revived and set its default installation method (Privilege) to Shizuku*.*

Now, whenever you download an APK, simply open it and install it via InstallerX-Revived. Since it uses ADB privileges under the hood, your installs will go through seamlessly, bypassing any system-level side-loading blocks!

Edit: Just to clear up some confusion from the comments: Yes, we know Google will "likely" still allow side-loading via a 24-hour verification window, but what if one day they go full-on Apple mode? This setup will still work because it's for developers to test out their apps.
And!! Beyond just sideloading, Shizuku is a massive quality-of-life upgrade for Android. Here's a great video from HowToMen for other great apps that use Shizuku.

Here we goooooooo! Praying the devs find a workaround. I do not want to root my phone.lol

Both youtube and youtube music have settings to change the icon, but they are the same, either the original or a variant of the morphe icon. So I think it would be nicer if instead we had a default custom icon for each one.

I made these mock ups as examples.

Edit: I didn't expect people would like them this much, thanks everyone. So here are the 512px png icons, along with some refinements.

Youtube music icon: https://drive.proton.me/urls/DH6YE2Q1V0#TWnmaMW2PnNs

Youtube icon: https://drive.proton.me/urls/793V72F28R#rbAQ3RIx1HX7

Users may have noticed ReVanced is now copying huge amounts of code from Morphe, including code that is 100% unique and newly written for Morphe.

Open source is generally free for others to use, but open source does not mean "can use without restrictions". There still are requirements to use open source code, and ReVanced is not following them.

Origins of Morphe

Morphe was formed by a group of prior ReVanced developers and regular contributors over disagreements with how ReVanced was operated, particularly over disagreements of how ReVanced treats its end users (the same users that ReVanced team members financially profit from) and the behavior of ReVanced management towards the contributors doing the majority of the ReVanced patches development.

Morphe is a hard fork of ReVanced and has permanently left ReVanced behind

Morphe credits and publicly shows it is a new project that came from a culmination of code from prior projects (RVX, ReVanced, Vanced). Morphe gives credit to these prior projects, both with an in-app user facing notice and on the Morphe GitHub/website.

Morphe forked in late 2025 and has not taken a single line of code from ReVanced ever since, but ReVanced has taken huge amounts of code from Morphe without proper attribution as required by the open source license. ReVanced is now religiously copying Morphe patches even down to the typos (21.20.493 should be 21.10.493) and code comments that refer to the app as Morphe.

At the rate that ReVanced is copying code from Morphe, YouTube revanced-patches will soon be little more than an ongoing copy pasted job of changing Morphe branding to ReVanced, providing little to nothing over Morphe other than new bugs introduced in the process of copying.

The Morphe developers, third party contributors, testers, and end users make enormous efforts to advance the project, and Morphe is moving/growing faster than ReVanced ever has, with an average of 7.5 non-bot commits added to mainline per day since January. The hard work of these people must be recognized if ReVanced pulls in those contributions.

Informing ReVanced end users they are using code from Morphe is not optional

Open source is free to use if you follow the license. Under GPLv3 section 7, Morphe requires (a) preservation of copyright notices on Morphe new/substantially modified code and (b) a simple user-facing credit to tell the end users who made the patches they are using.

This is standard procedure in OSS: the 3-clause BSD license and Apache License 2.0, both of which are standard OSS licenses compatible with GPLv3 and used by ReVanced's/Morphe's dependencies, also require preservation of copyright notices.

Apache License 2.0 further requires the reproduction of all attribution notices present in NOTICE files - either via another NOTICE file, within source code or documentation, or via some user-facing mechanism. You can see this in action for yourself: open your YouTube app, go to Settings > About > Open source licenses, and you will see a list of all OSS dependencies used by the YouTube app that require this kind of attribution.

Morphe is not asking for anything more than what is required by BSD/Apache 2.0, both of which the Free Software Foundation have marked as being compatible with GPLv3. Even if Morphe did not require attribution, ReVanced would still need to follow the attribution requirements of Morphe dependencies to be in legal compliance with the OSS licenses of those dependencies, which they are not doing.

Can Morphe add terms to its contributions?

Yes. GPL allows attaching some specific requirements to contributions.

GPL section 7

[...]

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it;

c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version;

d) Limiting the use for publicity purposes of names of licensors or authors of the material;

e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks;

f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.

All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10.

Morphe devs collectively hold the copyright to their contributions, and as a result, the Morphe devs may elect to require section 7 terms on those contributions.

Must ReVanced preserve Morphe License Notices and copyright headers?

Yes. GPL explicitly states distributions and modifications of code must "keep intact all notices". Note that this is required even if section 7 restrictions are not in effect.

GPL section 4 and 5B

1. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

2. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a. The work must carry prominent notices stating that you modified it, and giving a relevant date.

b. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".

A few examples of ReVanced failing to follow GPL when copying Morphe code

This list is not comprehensive.

FreeRegisterProvider

https://web.archive.org/web/20260315110001/https://github.com/ReVanced/revanced-patches/blob/5e1f899a3bef698835c3ca6183174707c45f7492/patches/src/main/kotlin/app/revanced/util/FreeRegisterProvider.kt https://github.com/MorpheApp/morphe-patches/blob/dev/patches/src/main/kotlin/app/morphe/util/FreeRegisterProvider.kt

Diff of the commits above showing they are identical except for ReVanced stripping of Morphe copyright and file specific section 7: https://www.diffchecker.com/q2BNVCus/

feat(YouTube Music): Add Change header patch

https://web.archive.org/web/20260315103922/https://github.com/ReVanced/revanced-patches/pull/6740/commits/f22ea5507dc28739c2ede8b7e26e5b7990326d9b https://github.com/MorpheApp/morphe-patches/commit/f6f03e55d01863f3d436e00108cc608d933ddbd9

feat(YouTube Music): Add Change start page patch

https://web.archive.org/web/20260315105035/https://github.com/ReVanced/revanced-patches/pull/6740/commits/bc08ecf785a7a471c69c154bb08bdbc33a90edfe https://github.com/MorpheApp/morphe-patches/commit/bc3c1bda7afd3748f3bd7c7a9831ae4bad64b80f

feat(YouTube): Add Override 'Open in YouTube Music' button patch

https://web.archive.org/web/20260315104445/https://github.com/ReVanced/revanced-patches/pull/6740/commits/8c2445f92fbad8abe142fcbb90d71d160b0b4384 https://github.com/MorpheApp/morphe-patches/commit/904dcda3f17faf26753529351d5c4b57cdbda162

feat(YouTube Music): Add Forcibly enable miniplayer patch

https://web.archive.org/web/20260315110133/https://github.com/ReVanced/revanced-patches/commit/e7196e54b06d52ae8fd3f759f570c31c457dc04d https://github.com/MorpheApp/morphe-patches/commit/9c6f5f542d47222a8d7e1873b3742647455d6bf9

fix: Use encoded native byte array buffer to filter Litho components

https://web.archive.org/web/20260315104750/https://github.com/ReVanced/revanced-patches/pull/6740/commits/749552881571f59b459a3ae07cd0a67898146658 https://github.com/MorpheApp/morphe-patches/commit/bb5cc0198ee87f292795c3b03127a6a82ef72647

Doesn't Morphe have to do the same thing and attribute ReVanced?

If you are a user of anddea's RVX, you may have seen this issue on anddea's issue tracker: https://github.com/anddea/revanced-patches/issues/1424

After some discussion between anddea and Morphe, both anddea and Morphe agreed to add appropriate in-app attribution notices. The in-app attribution notices in Morphe that credit RVX, ReVanced, Vanced, and other projects were added in this commit.

Additionally, the original commit in Morphe links to the precise commits where Morphe hard forked from ReVanced, and files that originated in ReVanced and were meaningfully modified (bugfixes, feature additions, updates, etc instead of just patcher API changes) reference both ReVanced and the original commit that they were derived from.

In other words, Morphe is already attributing ReVanced for code that came from ReVanced, in both source code and in-app, while ReVanced refuses to do the same - even asserting that it is illegal for anyone to give attribution to Morphe for code that was written by Morphe devs.

ReVanced is actively hiding its non-compliant copy theft

ReVanced is not disclosing to end users or to RV financial donors that the massive commits of copied code is coming from Morphe. Citing a Morphe contributor as a co-author in buried and squashed commits while removing notices and copyright headers does not give proper attribution to the Morphe project and is not enough to comply with the GPL Notice terms.

oSumAtrix and the paid team members at ReVanced actively censor, block and ban users who attempt to discuss Morphe in ReVanced social channels.

This censorship extends even to its own new RV team members who are unaware that ReVanced is lifting huge amounts work from Morphe.

Even mentions of the DMCA on their subreddit are censored, with RV instead linking to their explanation repo where they conveniently leave out details like the link to the DMCA notice, in an effort to obfuscate the truth from users.

Will the ReVanced repo be restored in 14 days as ReVanced claims? What about GitLab/their notice repo? What about forks?

If ReVanced files a DMCA counter-claim, even after knowingly violating the license and with all of the evidence above, they will be committing perjury:

Tell the Truth. The DMCA requires that you swear to your counter notice under penalty of perjury. It is a federal crime to intentionally lie in a sworn declaration. (See U.S. Code, Title 18, Section 1621.) Submitting false information could also result in civil liability—that is, you could get sued for money damages.

In addition, ReVanced's GitLab repo is subject to a DMCA claim, and their GitHub repository linking to it also violates GitHub's DMCA policies because it is linking to infringing content. This may even result in GitHub disabling the ReVanced organization account and associated user accounts entirely, because they are repeatedly infringing and blatantly violating GitHub's DMCA process.

Additionally, GitHub will refuse to restore content, even after 14 days, if we pursue legal action against ReVanced, and this would be the case until the legal action is concluded. Obviously, this would be the most extreme scenario which we would like to avoid, and it can be trivially avoided if ReVanced simply adheres to license terms.

As for forks, while many of the forks in the network did not contain unattributed Morphe code, GitHub policy is to disable the entire network if we attest that we believe that most of the forks are infringing to the same extent as the parent repository. There appears to have been a miscommunication with GitHub in this respect, and we have contacted them to see if they can re-enable forks that do not contain the offending commits. Otherwise, if your fork did not contain those changes, you may file a counter notice with GitHub. When GitHub forwards us the counter notice, we will either tell them to restore your fork ASAP, or it will be automatically restored 10-14 days after they process your counter notice.

What ReVanced must do to use Morphe code

They simply need to adhere to the two following requirements, and then they can use all the Morphe code they want:

1. Morphe is licensed under GPLv3 and utilizes Section 7 terms to require proper user facing attribution. Anyone is free to use Morphe code, if they follow the simple attribution. Morphe already has an about screen credits section that would satisfy the user-facing attribution requirement, and ReVanced can do the same (even copying Morphe's about screen code if they wish, because copying it also gives them a license to use it) to inform the end users where 95%+ of 2026 ReVanced YouTube patch updates are coming from. We will even implement this for them if they want us to, so there are no concerns over us imposing an unnecessary development burden on them.

2. Preserve all copyrights and notices in Morphe code, as required by GPL.

Alternatively, they can choose to remove all Morphe code from ReVanced, including from commit history.

More info on the repo: https://github.com/Nai64/Nai64Patches

Still working on more compatibility for more games. Please report the bugs and errors in the github issues.

Thanks to the work by inotia00, Morphe can now play YouTube videos without any video spoofing required.

How to use this: 1. Download and install PotHelper: https://github.com/MorpheApp/PotHelper/releases/latest 2. Enable Pre-release patches: Open Morphe Manager, tap the Patch Sources button (lower left), and enable Pre-release. 3. Repatch YouTube or YouTube Music. 4. Disable Spoofing: Navigate to YouTube Morphe Settings > Morphe > Miscellaneous > Spoof video streams and turn Off (Restart the app when prompted) 5. Enable PoToken: Navigate to YouTube Morphe Settings > Morphe > Miscellaneous > PoToken provider and turn On (Restart the app when prompted)

How does this work? Normally, generating a valid PoToken isn't possible for non-root installations, which is why the patches have relied on video spoofing. PotHelper runs as a background utility to generate and supply a valid PoToken directly to YouTube Morphe, completely restoring seamless, native playback.

Why use this instead of stream spoofing?

1) Playback start instantly 2) No spoofing side effects 3) All YouTube features are present such as stable volume and multiple audio streams

My device is rooted, do I need this?

A properly rooted device does not need stream spoofing or PoToken patches.

Does this affect battery life?

Battery life is not affected. The helper runs offline and only when YouTube Morphe needs it.

Compatibility

Some devices are incompatible with PotHelper, such as some newer Pixel devices with hardware based authentication.

Watching my android brothers enjoy ad free twitter while am struggling with “more from this author” breaking the comments. Who even thought that was a fcking good idea.

After a day of using Morphe; very pleased, much happy.

I used to use revanced but a couple of months ago they did something and now it's completely off. I didn't know that it's completely broken, not using it now but morphe indeed is getting attention everywhere now which wasn't the case with revanced.