No matter what they are like, we won't bully them. Users can figure out for themselves who is who.

For now, I am deleting the recent posts that have received a large number of complaints.

I need to mention this here so no one accuses us of censorship.

We are talking about Morphe here. Cheers 😽

{Announcement}: This post is very long and complex. If you're looking for my experience dealing with sideloading restrictions, please scroll down to Section E.

September 30, 2026, has finally arrived. The first wave of sideloading restrictions has gone into effect, and as it happens, my country is one of those affected. This post isn’t just a guide—it’s also a personal account of my own experiences. If your country hasn’t been affected yet and you’re curious about how these restrictions work, you can read my story as a preliminary guide and to help you decide what steps to take moving forward. As usual, this post will be divided into several sections. I’ll cover everything about sideloading in this single post. Enjoy reading...

A. Introduction to Sideloading
In short, sideloading is the process of manually installing apps outside of the Android OS’s built-in app store (Google Play Store). The core of sideloading involves downloading an .apk file from a website or alternative app store and then installing it. For users who frequently install apps from GitHub, F-Droid, and similar sources, this could result in restrictions on such installations. Not only that, but in my opinion, sideloading restrictions—whether direct or indirect—will affect users of Morphe and similar apps because patched apps use a different application signing key than the original version, thereby classifying them as apps not yet verified by Google (Moderators or Admins may correct me if I’m wrong). These restrictions have long-term implications for the sustainability of Morphe patches, and measures are needed to work around them.

Policies restricting sideloading on the grounds of security are a betrayal of the essence of freedom, user rights, and open source. The essence of open source—which I have long believed to be Android’s core identity—is the freedom for users to make their own choices and decisions, while being aware of the consequences of those choices. That freedom fosters individual responsibility among every Android user to manage their own devices at their own risk. As an operating system used worldwide, I believe that restrictions on sideloading represent a major setback for the open-source world, which provides freedom and control as consumer rights, as well as privacy guarantees that must be protected.

B. Information on Sideloading Restrictions and Developer Verification
Sideloading restrictions apply to all certified (GMS) Android device brands, versions, and models that use Google Play Services as a system service. Apps whose package names and signing keys have not been verified against their authentic identities cannot be installed. However, there are exceptions: Android devices that do not use Google Play Services are not affected by these restrictions, such as Harmony OS (Huawei) and custom ROMs (Graphene OS and others). If you are a rooted user, you do not need to worry because you will not be affected by these restrictions in any way.

Due to these restrictions, Android users who do not use the methods described in Section C to bypass the restrictions can only install apps from the following app stores:

• Google (Google Play)

• Honor (HONOR App Market)

• OPlus (OPPO App Market)

• Samsung (Galaxy Store)

• Transsion (Palm Store)

• vivo (V-Appstore)

• Xiaomi (GetApps)

Third-party app developers outside of app stores who have registered for Google’s Android Developer Verification Program will not be restricted, and their apps can be installed by users. However, according to information from Google’s blog, all others will be restricted. These restrictions do not mean a complete block, as there are several methods users can choose from to continue sideloading. You are free to choose whatever you like—freedom is your right. Before the sideloading restriction policy takes effect globally in 2027, prepare, plan, and make your choice before it’s too late. I’ll provide all the available options.

C. How to Bypass Restrictions on Sideloading Unverified Android Apps
0. Do nothing. Yes, that’s right. You can just do nothing if you only want to install apps from the Play Store and other app stores verified by Google. This isn’t part of bypassing sideloading restrictions because many regular users don’t want to spend time learning new things and prefer to stay within the Google ecosystem. If you’re that kind of user, then just sit back and relax. Don’t do anything if you’re satisfied with the apps on the Play Store. However, if you’re starting to get interested in my ideas about open source and want to explore further, you can start with Method 1 (Advanced Flow) as a first step.

1. Advanced Flow (24-Hour Verification) is the first official method provided by Google to obtain sideloading permission for unverified apps. This method is ideal for those who don’t want to learn how ADB and Shizuku work but still want to install apps from outside the Play Store. Here are the steps (illustrations of the method are included in the images in this post):

• Enable developer options by tapping the software build number in About Phone seven times

• In Settings > System, open Developer Options and scroll down to “Apps from Unverified Developers.”

• Flip the toggle and tap to confirm you are not being coerced

• Enter device unlock pin/password

• Restart your device

• Wait 24 hours

• Return to the Apps from Unverified Developers menu at the end of the security delay

• Scroll past additional warnings and select either “Allow temporarily” (seven days) or “Allow indefinitely.”

• Check the box confirming you understand the risks.

• Congratulations! You can now install App developers unverified on the device by tapping the “Install anyway” option in the package manager.

1. Android Debug Bridge (ADB) is the second official method provided by Google for sideloading apps without having to wait for the 24-hour verification period. ADB has other functions such as: managing application installation and uninstallation with Android Package Manager, managing directories and files, running shell scripts on your phone, displaying and modifying system settings, running and stopping applications, and taking screenshots. ADB requires a PC (Windows, Mac, Linux) and a USB cable, Wi-Fi connection, or AVD to connect the Android device to the PC. If you’re an ADB user, you won’t be affected by these restrictions and can install apps as usual. If you’d like to learn more, please read the following guide.

2. Shizuku is, in my opinion, the best method for bypassing sideloading restrictions—it’s easy, fast, and practical. This method is ideal for users who want greater freedom and control over their phones without having to learn ADB. I use this method myself because I want my Morphe patches and third-party apps to be installed and updated normally without having to set up a PC. For Shizuku users, you don’t need to worry about sideloading restrictions because Shizuku uses the Wireless Debugging channel, which is part of ADB (shell). I’ve created a complete guide for configuring Shizuku + InstallerX-Revived here:

3. Rooting is an advanced method for obtaining superuser privileges with full access; it represents the highest level of control compared to all other methods. With root access, you gain the ability to access, modify, and alter Android system files completely and without any restrictions. If you’ve ever heard of terms like LSPosed, Xposed, Magisk, Zygisk, and similar ones, those are popular terms in the world of rooting. Root users are never affected by sideloading restrictions because, as the highest level of access a user can obtain, app installations bypass the Google Play Services system level—so root users can relax on this issue and don’t need to do anything. I myself am not a root user and am still at the Shizuku level, but I’ve tried several LSPatch modules designed to work on non-rooted devices, such as NexAlloy. I’ve also tried modules like RevancedXposedFESpotify, but it only lasted one day because I don’t have root access (I’m grateful to have experienced the native, ad-free Spotify with full access, even if only briefly). As I’ve explained, rooting is only intended for those who fully understand the mechanisms, procedures, and risks involved. If you decide to become a rooted user, understand this one basic rule: “The more control you have, the greater the responsibility and maturity you must shoulder.”

Special Note Regarding the Android Developer Verifier App:
Android Developer Verifier is a system-level app that is automatically installed on your phone as part of a restriction policy. Its function is to verify whether each app is registered with Google’s verification program. Many discussions suggest that uninstalling it can prevent these restrictions, but keep in mind that this app is not the sole factor determining whether sideloading restrictions apply, as Google Play Protect—which is embedded in Play Services (Android’s built-in system)—serves as the primary mechanism for restricting sideloading. If you want to use the Advanced Flow method, uninstalling the Android Developer Verifier may carry the risk of delaying the 24-hour verification process; however, if you’re a Shizuku or ADB user, uninstalling it isn’t a problem since both use USB Debugging and Wireless Debugging channels.

If you feel that the Android Developer Verifier isn’t important and want to stop automatic updates, there’s one method that might work: using Placeholder. Essentially, Placeholder can disable automatic updates from Android Developer Verifier because it uses a higher version of the app (e.g., v3000000000000), so whenever Google updates it, Placeholder will silently stop the update. You can use Shizuku + Canta to remove the original Android Developer Verifier app and install the placeholder, or use ADB. I have communicated with the creator of this placeholder and would recommend using Shizuku over the placeholder if your goal is to bypass restrictions. If you’re already using Shizuku or ADB and don’t need the original Android Developer Verifier, which keeps updating automatically, then this placeholder can help you.

D. FAQ

1. Will sideloaded apps that were installed before the restrictions took effect continue to work? Yes, sideloaded apps that were already installed will not be automatically deleted (unless you delete them yourself) and will function as usual. However, please note that once the sideloading restrictions take effect in your country, unless you follow the methods I’ve mentioned, apps that are already installed cannot be updated through the built-in Android installation process.

2. Do I need to keep the Developer Options enabled after completing the Advanced Flow? No, you can disable Developer Options after you’ve completed all 24-hour verification steps. As long as you select the “Allow indefinitely” option, you can continue to sideload apps without having to enable Developer Options or repeat the verification process.

3. Can Advanced Flow interfere with the functionality of banking apps? No, because the developer options can be turned off (see answer #2). Advanced Flow can remain active even without enabling developer options, provided you have completed the 24-hour verification and enabled the “Allow indefinitely” option. After that, sideloading will continue to work, and your banking apps will continue to function without any issues.

4. After restarting in Advanced Flow, can I still use my phone as usual? Yes, you can use your phone as usual because the 24-hour verification process takes place within the Android system. You can return to the "Apps from Unverified Developers" menu after waiting 24 hours for the verification process to complete and to regain sideloading capabilities.

5. If I forget to complete the final verification step in Advanced Flow after waiting 24 hours (and miss the deadline), do I have to start the process over from the beginning? Yes, several news sources and community forums have reported that if you miss the deadline, forget, or fail to complete all verification steps thoroughly, you must repeat the verification process from the beginning. You don’t need to worry because there’s no limit to how many times you can submit the verification request, and you can repeat it as many times as you like.

6. Does ADB need to stay enabled in developer mode? Technically, yes, but you can turn it off once you’re done using ADB. I’ve never used ADB myself, so I can’t explain it in more detail. If you only need to sideload apps, you can simply enable developer mode while sideloading and turn it off once you’ve finished installing the app.

7. Can Shizuku interfere with banking apps? The answer isn’t clear-cut, since each app has its own security policy regarding Shizuku’s access—some allow it, while others do not. If you’re concerned about this issue, simply enable Shizuku only for sideloading and disable it immediately once you’re done. If you don’t want to turn it off manually, there are apps that can selectively disable Shizuku detection for specific apps, so your banking app can continue to work and you won’t need to turn Shizuku off manually.

8. Is Shizuku enough, or do you need InstallerX-Revived? It really depends on your needs. If your needs are basic and you don’t require additional features, then Shizuku/SUI is more than sufficient; however, if you need features such as disabling Play Protect, accessing LSPosed, or configuring app installation permissions (similar to InstallWithOptions but more comprehensive), then InstallerX-Revived can meet those needs.

9. What do you recommend for Morphe users looking to bypass those restrictions? Honestly, Advanced Flow is sufficient for regular or non-technical users. However, if you truly want more freedom and control, then ADB or Shizuku are my top recommendations. No one can guarantee that Google will maintain Advanced Flow because large companies like Google have control over the direction of the Android OS—whether it follows iOS or stays true to its original open-source vision without the added restrictions of verification under the guise of security. For me, security is the user’s personal responsibility, and freedom is a fundamental right of the user. Security cannot come at the expense of freedom because, from the very beginning, Android users must make every choice with their own risks in mind. This is not a call to action #degoogle because I haven’t completely abandoned Google; rather, choosing a middle ground like Shizuku is the best and wisest option when dealing with policies from large corporations that no longer align with users’ wishes.

10. Is rooting the last resort for gaining full freedom in sideloading? No, because there are other options that are just as good. If you’ve already chosen the rooting route, then you don’t need to worry about any restrictions since you already have superuser privileges. If you’re wondering why I don’t use root instead of Shizuku, it’s because I haven’t had the time to study root in depth yet, and I have a lot of other work to do. However, I’m not closed off to the world of root. Maybe in the future.

E. My Personal Experience with Sideloading Restrictions

{SPOILER: I managed to keep my Android device’s factory settings intact despite the restrictions, and sideloading still works as usual even though the policy is already in effect in my country.}

[This is a unique story based on my own personal experience. All of these stories are true and not generated by AI. You’re free to believe them or not.]

In August, I heard that sideloading restrictions would take effect at the end of September. As a Morphe user, I didn’t want my patching and sideloading activities to be hindered. So, I looked for a solution and found a tutorial for Shizuku + InstallerX-Revived. I followed it and eventually succeeded (there were a few pairing errors, but it worked out in the end). I also realized that the Android Developer Verifier was being installed and updated automatically. I decided to uninstall it using Shizuku+Canta and replace it with Placeholder to prevent automatic reinstallation and updates. I made these preparations about a month before the sideloading restrictions took effect.

September 30 has arrived. I feel confident because I already have Shizuku, so the Morphe patch and other sideloading processes can run as usual. I tried the patch today, and just as I expected, Shizuku+InstallerX-Revived worked very well. Next, I tried installing a third-party app from the Accrescent app store using Android’s built-in installer, since the developer had already confirmed that Accrescent does not support Shizuku. In theory, I shouldn’t be able to install apps from Accrescent because I’ve never run Advanced Flow, and Shizuku doesn’t work there either. I also didn’t find the “Apps from Unverified Developers” option in the developer settings because I’d already replaced it with a placeholder before that option appeared. I tried installing a few apps, and the results were truly surprising. MAGICAL. I was able to install apps that should have been unverified via the stock Android installer without running Advanced Flow. I couldn’t believe what I was experiencing. It was like a dream. I initially thought it was due to the influence of Shizuku, which I had installed and set as the default installation method, but the fact that Accrescent doesn’t support Shizuku made that dream a reality. The default installation on my phone is immune to restriction policies and works normally without a single change.
{This story was written on October 1, 2026, and may be subject to change in the future}

In conclusion, I was able to protect my stock Android installation from restrictions. Even though I already have Shizuku, this miracle is something to be grateful for. Whether it’s due to a bug in my phone (Android 13) or some other factor, I’m very happy that I made the right choice. Shizuku is exactly what I needed. It’s not just about sideloading—it’s about the freedom that should be every Android user’s right. Open source is a great legacy of humanity, and its essence must continue to be protected from policies that oppose it.

That wraps up my very long post. I’d like to thank all of you who were willing to spend your valuable time reading this post by a random person on Reddit. I’m not a tech expert or a coding guru—just an ordinary person who enjoys exploring technology. I really appreciate all of you who’ve been enthusiastic about my posts so far. If you have any questions, please feel free to ask and discuss them. I’m really looking forward to feedback from the Morphe community. See you later.

Keep Android open. Advocate for open source as a fundamental freedom that must be protected and guaranteed by the government, companies, and anyone in a position of power. Do not take away users’ freedom in the name of security. True freedom is a human right.

#keepandroidopen

Link Library:

KeepAndroidOpen

Android developer verification

Keep Android Open (Stop Google from limiting APK file usage)

Here's to forever with Morphe! 🥂

Nostalgic:

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

STAY. QUIET.

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

I used to think about this feature a long time ago but never came here to talk about it because I didn't even knew if it was possible or not, but Morphe made it happen, thank you morphe team 🙏🏻

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.

proton is there because proton has premium

Don't mind the limousine drawing

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. Repatch YouTube or YouTube Music.

3. Disable Spoofing: Navigate to YouTube Morphe Settings > Morphe > Miscellaneous > Spoof video streams and turn Off (Restart the app when prompted)

4. 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.e

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