{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)

In this post, I’d like to share a list of the ecosystem of apps I use to support Morphe. I’ve named it “Morphe Workspace,” similar to “Google Workspace.” The goal is to make it easier for Morphe users who are still unsure how to manage patched apps. Feel free to save this post if you think it might help you find links to the apps mentioned here. I’ve grouped the apps into several categories based on their functions, namely:

A. Morphe Internal Suite (MIS): a list of apps directly related to the Morphe development team that are essential for ensuring Morphe patches run smoothly.
B. Morphe External Suite (MES): a list of apps that support the needs of users of patched apps, such as app managers, automatic update managers, and other supporting functions.
C. Morphe Advanced Suite (MAS): a list of apps specifically intended for advanced users to gain full control over the apps. If you’re a regular user, you can ignore this list, but if you want to explore it further and understand the consequences that will result, feel free to take a look.

The following is a complete overview of Morphe Workspace:
A. MIS:

1. Morphe Manager, the official Morphe patch app. For those who don’t know, Morphe Manager currently offers 3 official patches and over 800 community-created patches.
2. MicroG-RE, an app that must be installed alongside Morphe Manager. Its purpose is to ensure that the official Morphe patches for YouTube and YouTube Music can run.
3. PotHelper, the PoToken app for Youtube Morphe, is highly recommended for installation. With PotHelper, you can watch YouTube Morphe smoothly.
4. Morphe Desktop (An alternative if you prefer to apply patches using a PC), the Morphe Manager for PC. Both CLI and GUI versions are available. You can patch apps on your PC, and advanced users can install patched apps via the Android Debug Bridge (ADB).

B. MES:

1. Helper for Morphe is a utility app for downloading raw APK files that will be patched by Morphe Manager. In my opinion, this is the best app for making it easier to find the raw APK files needed for the patching process. Additionally, for security, VirusTotal API is provided to protect you from malicious APK files before the Morphe patch is applied. If you’re still having trouble finding the APK files needed for the patch, I highly recommend Helper for Morphe as your primary download assistant.
2. Obtainium is an app update management app. With Obtainium, you can update all apps outside the Play Store to ensure they always receive updates. For those of you who are still unsure how to automatically update MicroG-RE and PotHelper, this is the solution. I plan to create a more detailed guide on automatic updates in a future post.
3. Aurora Store is the best alternative to the Google Play Store. No ads, no sponsors, no tracking. It’s perfect for use alongside Morphe. You can install, uninstall, and update Google Play Store apps in Aurora.
4. YTDLnis is a video downloader app that uses the yt-dlp engine. It supports over 1,000 websites with additional features such as SponsorBlock , playlist downloads, batch downloads, and all yt-dlp features. It’s ideal for use with YouTube Morphe to download YouTube videos 100% free, without ads, and without any restrictions.
5. ML Manager is an app specifically designed to extract apps already installed on your device. If you want to save patched APK files or other apps locally, ML Manager can easily extract your apps for offline storage. (Update) There are alternative recommendations from ML Manager since it hasn't been updated in a long time, including APK-Extractor and Kanade.
6. F-Droid is a free and open-source app repository that serves as an alternative to the Google Play Store. If you want to explore more apps, this is the place to go. There are many clients of F-Droid, such as Aurora Droid, Droid-ify, IzzyOnDroid, and Neo-Store. F-Droid also offers a basic version. If you’d like a new variation of F-Droid, you can choose one of these forked apps.
7. Accrescent is an alternative app store similar to F-Droid. You can search for specialized, hard-to-find open-source apps. One of the most well-known is the IronFox browser, which is a hardened version of Firefox.
8. Komi Store is an app manager specifically designed for GitHub repositories. You can log in to GitHub, search for app repositories on GitHub, install them, and update them. You can combine it with Obtainium to get automatic updates.

C. MAS:
Important Note:
If you wish to use an app in the MAS category, always make sure you understand how it works. Learn about the potential consequences of using that app. Since this category is intended solely for expert or experienced users, I do not recommend that regular users use these apps. The advanced controls provided by the apps listed below have consequences for your device, whether positive or negative. Therefore, make sure you understand all the possibilities to keep your device safe.

1. Shizuku Fork by Thedjchi is a fork of the Shizuku app that gives you more control over Android apps without needing root access. This Shizuku fork uses a USB debugging connection without requiring a connection to a computer via a terminal. It features “start on boot,” “watchdog,” and “TCP Mode.” Morphe Manager supports Shizuku for installation methods other than the default Android installation. There are many other forks of Shizuku or the official Shizuku app, but I personally prefer Thedjchi’s fork because it’s simpler and works well. Please keep in mind that you can only use one type of Shizuku app per phone, so avoid using multiple Shizuku apps as this will disrupt debugging functionality.
2. InstallerX-Revived is the best replacement for the stock Android installer. You can install apps without any restrictions from Google and bypass Google Play Protect restrictions. This app requires Shizuku permission to function and can be set as the default installation method as long as Shizuku remains active. Its interface is clean, lightweight, and runs smoothly. You can sync InstallerX-Revived with Morphe for a seamless patched installation experience. One important note: if you want to revert to the default installation method, you must first disable the built-in installer option while the Shizuku service is still active so that the privileges can be turned off. If you disable Shizuku while those privileges are still active, you won’t be able to change the default installation method or install apps via InstallerX-Revived. The solution is to revoke those privileges in the advanced settings within your Android settings.
3. Universal Installer is a comprehensive, sleek, and easy-to-use app manager. Unlike the default Android app manager, you have options to customize the interface (Material You and AMOLED), update apps, and group installed apps (system apps, user apps, disabled apps, and blocked apps). You can even check app security in Universal Installer via the VirusTotal API, review app permissions, and extract apps.
4. Canta is the best app-removal tool that uses the Shizuku service without requiring an ADB connection. It features category labels indicating whether an app is safe or risky to remove, along with general descriptions of the apps in question. Canta is designed to remove Android bloatware or apps that are difficult to uninstall manually. Be aware of the risks involved in every action you take—the more control you have, the greater your responsibility for the actions you take. Never uninstall an app if you don’t understand the consequences. To stay safe, I only recommend Canta for experienced users.
5. Hail is an app for disabling, hiding, suspending, and uninstalling apps using the Shizuku service. It’s similar to Canta, but Hail offers the option to freeze apps without deleting them, making it safer from potential damage. Hail is ideal for those who want to disable unnecessary apps without having to delete them.
6. Shappky is an Android RAM management app that uses the Shizuku service to close apps running in the background. It works similarly to the Task Manager in Windows: it monitors RAM usage by system and user apps and closes those apps to free up RAM. You can exclude important apps that need to keep running in the background (such as MicroG-RE and PotHelper) so they aren’t closed. I highly recommend Shappky as a companion to Morphe for managing your RAM usage.
7. NoMoreBackground is an app that uses the Shizuku service to manage app permissions for running in the background. In addition, you can manage background data permissions. You can organize background permissions for the Morphe Patch app.
8. ShizuWall is an app for managing firewall connections for all your apps using the Shizuku service. ShizuWall does not require VPN access, DNS, or CA certificates to function. It’s ideal as a complement to Morphe for apps that don’t require an internet connection or for blocking internet access from specific apps that frequently display ads and track users.

That concludes my list of Morphe Workspace tools. To wrap things up, I’d like to explain how some of the apps above make it easier for me to apply Morphe patches, organize app updates, and manage apps as follows:

1. The Morphe Patch Ecosystem**:** I search for apps to patch using Helper for Morphe with VirusTotal protection, then process the patches. I use Shizuku + Installer X-Revived, so I don’t have to worry about restrictions on installing unverified apps. Once installed, I use Malwarebytes—with its real-time protection feature set to automatic—to scan all newly installed apps as well as any apps I’ve just installed. VirusTotal and Malwarebytes are my two main antivirus protectors on Android that comprehensively safeguard patched apps from dangerous threats both before and after patching, giving me better security than Android’s built-in antivirus alone.
2. The third-party app ecosystem outside the Google Play Store and the update system for all apps: I search for the apps I want on GitHub via the Komi Store, then import them into Obtainium to receive automatic updates. For other repositories, I search for them on Brave Origin (thanks to the Brave patch) and then copy the repository link into Obtainium. So far, I’ve integrated 30 open-source apps from various sources outside the Play Store into Obtainium (e.g., MicroG-RE, PotHelper, InstallerX-Revived, and others) to receive automatic updates without having to manually check the repository sources for each of the 30 apps. For apps that were previously installed from the Play Store, I prefer to update them using the Aurora Store because it has no ads and a minimalist interface.
3. App Control Ecosystem (Advanced): Since I’ve gained a solid understanding of Shizuku, I can further control app permissions and organize apps. For example, I freeze apps I don’t need with Hail, uninstall apps that are safe to remove with Canta, clear my device’s RAM with Shappky, control background activity with NoMoreBackground, and manage a custom app firewall with ShizuWall. I use Universal Installer to monitor the behavior of automatically installed apps (such as Android Safety Core and Developer Verifier). I’ll likely discuss these in more detail in another post.

That’s all I can write for now. In my opinion, all of these apps have been very helpful for my daily needs, improving device security, and increasing efficiency when applying Morphe patches. I hope this helps many people avoid confusion about how to update MicroG-RE. Below, I’ve included a list of Morphe repository links to make it easier for you to find the related apps you’re looking for. Thank you.

Link Library:

1. Morphe's Official Website
2. Morphe's Official GitHub
3. List of Morphe Community Patches
4. Awesome Morphe
5. Awesome Shizuku
6. Shizuku Apps Directory

On September 30, 2026, my country will be one of four countries subject to these restrictions, and in 2027, they will take effect globally. Although there’s a way to allow app installations by waiting 24 hours, I personally prefer a more flexible and controlled approach. After doing some research and browsing Reddit, I’ve found a method that I believe is easy, fast, and safe for gaining the freedom to install the apps I want. Morphe has helped me remove annoying ads in apps, especially on YouTube. I didn’t want to limit my Morphe installation, so I chose this method.

To be honest, I’m new to Shizuku, but after using it, I’ve found that I have better control over my phone. For me personally, the main purpose of Shizuku is to allow Morphe to continue installing apps as usual. That’s all. I’d like to share my experience with the Morphe and Shizuku workflow combination in this community. Hopefully, this will help those who are still wary of Shizuku and its various features. As long as we know what’s happening, our phones will remain safe. I highly recommend reading guidelines from experts and reliable tutorials. If you want to use a method like waiting 24 hours, that’s fine. It’s up to you; this method is just one option you can choose.

A. What do you need to download before doing anything?

1. Shizuku fork by Thedjchi (I’ll explain why I chose this fork in section C)
2. InstallerXRevived (I personally use InstallerX-Revived-offline)
3. Morphe (if you haven’t installed it yet)

B. Shizuku Configuration + InstallerXRevived & Morphe
To start with, I’m using a Xiaomi 13 5G (Android 13). You can adjust this according to your phone model

1. Enable developer mode on your device. Follow the steps specific to your phone model. Generally, you’ll find it under Settings &gt; About Phone &gt; Android Version (tap 7 times, and a message will appear saying “Congratulations, you’re now in developer mode”).
2. Go to Developer Options (on my phone, it’s under Additional Settings > Developer Options). There are four important settings you must enable for the Morphe and Shizuku combination to work properly: USB Debugging, Wireless Debugging, Install via USB, and USB Debugging (Security Settings). For Xiaomi phones, you must enable USB Debugging (Security Settings) for Shizuku to function properly. For other phone models, please read the complete guide in the official Shizuku documentation or the wiki from the thedchi fork.
3. Temporarily pause or disable Play Protect in the Google Play Store (open the Google Play Store—click the Google profile icon—click Play Protect—click the gear icon in the top-right corner—turn off the “Scan apps with Play Protect” option—click “Pause” (for 1 hour) or “Disable”). Make sure this step is successful because, in my experience, Play Protect won’t allow the Morphe installation. You can re-enable it after installing the Shizuku fork app.
4. Install the downloaded Shizuku fork file.
5. Open the Shizuku app and click “Pairing” under “Start via Wireless Debugging.” You’ll be automatically redirected to the wireless debugging settings we enabled earlier. Next, click to pair the device using the pairing code. You’ll receive a notification from Shizuku asking you to enter the pairing code. Enter the code and make sure the numbers are correct. If they’re correct, click the “Send” icon, and a message should appear stating that Shizuku has successfully paired. The next step is to press the “Start” button in the Shizuku notification, and you’ll be redirected to the Shizuku app. You’ll see a terminal window that initiates the startup process (don’t worry—it’s safe). If the process goes smoothly, you should see a message in the terminal indicating that Shizuku is running, and you’ll be directed to the Shizuku app’s home screen. If you’ve made it this far, congratulations—you’ve successfully enabled Shizuku’s core functionality. You can take a break here or proceed to the next step.
6. Install the downloaded InstallerXRevived application file. Once it’s successfully installed, open Shizuku and click “Authorized Applications.” Enable the option for InstallerXRevived. If you've already installed Morphe, turn it on for Morphe as well. Next, open InstallerXRevived, make sure “Shizuku (Shell)” is listed under “Authorizer Used,” and click “Default Installer.” Enable the options “Set Automatically as Default Installer” and “Set as Default Installer.” If the message “Functioning as the default installer” appears on the home screen, congratulations—you now have an app installation system free from Android verification restrictions.
7. You’ve now reached the main part: integrating the Shizuku + InstallerXRevived workflow with Morphe so you can install apps without verification restrictions. Now, open or install Morphe (if you’re new to Morphe). Before continuing, make sure the “authorized” option for the Morphe app is enabled in Shizuku. Next, click the settings icon in the top-right corner of the Morphe app, click the system icon in the top-right corner, then click “Default Installer” and select “InstallerXRevived.” Don’t forget to click “Confirm” so the installation settings are saved and activated. If you’ve succeeded, congratulations—for the third time—because you’ve completed the entire configuration process. Feel free to take a break or try testing the installation of the Morphe patch app without any annoying verification restrictions.
8. If you want to try a test installation, you can start installing the Morphe patch app as before. Once the patch is complete, click “Install,” and an InstallerXRevived notification will appear to continue the process. Click "Install," and if everything is in order (the patch matches your Android version and there are no conflicts between the old app and the patch), an "Install via USB" notification page will appear. On my phone, this notification automatically closes after 10 seconds if you don’t click "Install," so don’t forget to click it. You can enable the “Remember this option” setting so you don’t have to click the “Install via USB” confirmation for the same app again. This is my personal experience with a Xiaomi phone and may differ with other phone brands, so please adjust accordingly. If the installation is successful, congratulations for the fourth time—you’ve now gained the full rights that every Android user should have.
9. In addition, there are a few settings I recommend enabling so that this configuration works optimally: open the Shizuku settings and enable the following three options: Start on boot, watchdog, and TCP Mode. You can also enable the “auto-disable USB Debugging” option if you’re the type of user who uses Shizuku temporarily and wants to avoid the risks associated with USB Debugging (learn more in the Shizuku guide). If you’re a regular user who wants to keep USB Debugging enabled and understands the ins and outs of USB Debugging, you can ignore the auto-disable option. For the settings in InstallerXRevived, I personally enable the "Disable ADB Verification" option (optional). If you have an antivirus app separate from Play Protect or Android’s built-in scanner, you don’t need to worry. I use Malwarebytes with the Morphe patch to get real-time protection that’s more effective than Xiaomi’s built-in security. Always make sure to scan anything you download or install from the internet using VirusTotal or an antivirus program you trust. Avoid apps from unknown sources to prevent viruses or similar threats. If you’re concerned, you can enable Play Protect like most people do.

C. Important Note

1. The reason I chose the Shizuku fork by Thedjchi is that this fork includes a watchdog feature and TCP Mode, which allow Shizuku to continue running even if the Wi-Fi network is turned off. My workflow can keep running with Morphe & Shizuku without having to rely on Wi-Fi.
2. Specifically for Xiaomi users, based on my own experience, the wireless debugging menu automatically turns off about 30 minutes after it’s activated. However, this isn’t an issue for me because I can still install app patches from Morphe even if that option is disabled in the developer options. If you encounter installation failures, try enabling this option.
3. Additionally, for Xiaomi users, the built-in security app may disable developer options if you enable the “repair” option. You can re-enable developer options in settings, but in my opinion, that’s a waste of time. So, personally, I use a different app for security scans. You can also disable Xiaomi’s security settings under Features > Security Scan > Turn off root option.
4. All of these methods are based on what I’ve learned from various Reddit forums, Shizuku’s guidelines, and my personal experience. There may be some differences.
5. You can disable USB Debugging and Wireless Debugging if you don’t need to install via Shizuku + InstallerXRevived. According to the Shizuku guidelines I’ve read, there are security risks if you enable USB Debugging and Wireless Debugging outside your home or in public spaces (such as public Wi-Fi networks or office computers). For me personally, since I’m mostly at home using my private Wi-Fi and my personal laptop, keeping them enabled 24/7 shouldn’t pose much of a risk. However, if you frequently use public Wi-Fi, I recommend disabling Shizuku, USB Debugging, and Wireless Debugging when not in use as a security measure against threats arising from ADB. (Update)

That’s all I have to share. I hope this helps those of you who want to use the Morphe and Shizuku workflows without worrying about verification restrictions. Thank you for reading.

If the MV2 extension is at risk of being removed from the extension store, I created an automated archiving system that runs every day at 00:00 UTC to back up MV2 extension files into a single repository. I planned this project a month ago, and I’ve finally been able to set up the automated backup repository. The goal of this project is to make it easier for MV2 users who have trouble finding their extensions in the extension store and to protect the extensions from being removed.

The Manifest V2 Archive consists of:

1. A wiki consisting of: a. Guide to Installing Manifest V2 in Chromium-Based Browsers (Developer Offline Mode) b. Guide to Installing Chrome Extensions on Firefox-Based Browsers c. Tips for installing Firefox extensions in Chromium-based browsers d. Manifest V2 Database (Chrome Web Store, Add-ons Firefox, Microsoft Edge Add-Ons, Opera Add-ons)
2. Offline Archive, an archive containing the MV2 extension that does not include the Forge software and does not have the extension file in the releases section. You can download the extension here.
3. Online Archive, an archive that is automatically updated every day at 00:00 UTC. You can view the automatic updates for the MV2 extension in the releases section.

Thank you for visiting my project. I hope it helps many people.

This is my first GitHub repository. As a beginner, it’s very simple. Facebook Clean Experience is a simple guide to restoring a pleasant experience on Facebook, which includes:

1. Removing sponsored ads from Facebook pages

2. Removing AI elements from Facebook

3. Removing unnecessary elements from Facebook

I’ve tried it myself and was able to make it work thanks to a user script called “FB-clean my feeds.” I’ve made the guide as simple as possible without any complicated configuration. In the “releases” section, there’s a .json settings file that you can import to remove ads on Facebook without breaking the functionality of the Facebook homepage. Additionally, I’ve also added “Facebook My Filter” to streamline Facebook or make it simpler based on my preferences. Your feedback is very helpful to me in developing this first repository. I hope this is useful and helps more people.

This is a project I developed on Codeberg called the MV2_Extension Project to archive MV2-based extensions. The goal of this project is to make it easier for MV2 extension users to access the extension source links and to preserve the MV2 extension archive in case of removal from one of the extension stores (Chrome Web Store or Firefox Add-ons). Currently, it consists of a table with four sections: links to each extension store, links to the extension repositories, and Wayback Machine archives. So far, I have successfully recorded 17 MV2 extensions in this database. This project is open source and can be developed by the community and anyone who wishes to contribute to the maintenance of MV2 extensions.

If anyone has suggestions for improving this project, I would greatly appreciate them. I hope this will be useful for many people who want to continue accessing MV2 extensions more easily. Thank you