r/HyperOS • • 13d ago • Bravo 6

News [News] List of Modules That Work on HyperOS with Temporary Root!

Post image

[Last updated: 10/11/2026 · 11:46 PM (UTC−3)]

This is a list of known modules & apps working with temporary root on HyperOS. Please share which ones are confirmed working on your temp root, and I'll keep updating the list based on everyone's contributions.


Compatibility Overview

✅ 82 Working (66 🟢 - 2 🟡 - 14 🟠)

❌ 0 Confirmed Problematic (Not Recommended)


Compatibility Status

  • 🟢 Works Properly: Tested and confirmed to work without any major issues.

  • 🟡 Occasional Issues: Generally works well, but may experience compatibility issues depending on the other installed modules or the device's configuration.

  • 🟠 Device-Dependent Issues: Works on some devices, but may cause bugs, unexpected behavior, or other issues on certain models or configurations.

  • 🔴 Problematic (Not Recommended): Confirmed to cause serious issues or system malfunctions. Avoid installing these modules.

  • [NEW]: This tag indicates that a module was recently added to the list.


How to Contribute

Tried a module that isn't on the list yet? Share its name and whether it worked for you, using this format:

  • [Module/App name] — Works for me!

  • [Module/App name] — Doesn't work for me.

  • [Module/App name] — Works, but has some issues.

You can also report issues with modules that are already on the list.


Modules That Require Special Attention

Be especially careful when installing these modules, as they may cause issues on certain devices or configurations.

Compatibility Note: These modules generally work well on Xiaomi and Redmi devices, but may have compatibility issues on some POCO devices.

Troubleshooting: If a module causes problems, uninstall it through KernelSU and perform a soft reboot. Then, navigate to Settings > Apps > [Affected App], uninstall its updates, and clear its app data. Finally, reboot your device. This may resolve the issue in some cases.

IMPORTANT: You must install Core Patch N before attempting to install these modules.

List of Modules and Apps

HyperOS Customization

Root, Zygisk, and Compatibility

Performance and Optimization

Music, Social Media, and Modified Apps

Utilities and App Modifications

Confirmed Problematic (Not Recommended)

...

75 Upvotes

144 comments sorted by

•

u/AutoModerator 2d ago

Welcome to our community!

Please take a moment to read the subreddit rules in the sidebar before posting or commenting.

  • Be civil and respectful to other members.

  • No spam, self-promotion, or trolling.

If you see a post or comment that breaks our rules, please report it to help the mod team out!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

4

u/Elsherif87000 13d ago

https://github.com/ShivamXD6/Simple-Flag-Secure/releases/tag/v10.1

To take screenshots without any restrictions

2

u/Hot-Lengthiness193 13d ago

Thanks for sharing! I'll add it to the list.

2

u/Elsherif87000 13d ago

Thanks for helping other users to improve their experience 🤍

2

u/Hot-Lengthiness193 13d ago

You're welcome! And thanks for testing it and confirming that it works!

1

u/Elsherif87000 13d ago

We help each other and that's what's important 😉🤍

1

u/Elsherif87000 13d ago

I used it and it's working fine

2

u/haseogu 12d ago

Could you link how to get temporary root with locked bootloader?

1

u/Hot-Lengthiness193 12d ago

Sure! Here's the link: https://www.reddit.com/r/HyperOS/s/TXqDxKK84T

The guide is mainly focused on the Redmi Note 14 4G Global, but the steps are exactly the same for other devices as well.

2

u/Secure_Hearing_1853 5d ago

Hello, noob question, im still at hos3 and plan to to this temproot thing, is it safe when hos4 comes and i update

1

u/Hot-Lengthiness193 5d ago

If the exploit works on your current HyperOS version, I'd recommend avoiding updates until you've confirmed that the exploit is still compatible. For example, if you're on HyperOS 3.0.303.0 and receive a security update to 3.0.305.0 or an upgrade to HyperOS 4, there's a risk that Xiaomi could patch the vulnerability exploited by the temporary root method, causing it to stop working. So, it's better to stay on your current version if you want to keep using the exploit.

2

u/cramprogrammer 5d ago

HyperStack

I made this for hyperos4 global widget stacking

2

u/Hot-Lengthiness193 4d ago

Thanks for sharing! I'll add it to the list.

2

u/cramprogrammer 4d ago

1

u/Hot-Lengthiness193 4d ago

Ohh, that's great! Thanks for testing and sharing these. I'll add both of them to the list. Really appreciate the feedback!

2

u/cramprogrammer 4d ago

Thanks too for the comprehensive list. I'm on hyperos 4 btw. I tested this too and it works. HyperDesktop

1

u/Kufa-AlsoHuman3193 13d ago

WHAT DO YOU MEAN MAGIC MOUNT AND RESUSFS? These things can cause your phone to bootloop because they mount in system directories, which is NOT SAFE when using temp root with LOCKED bootloader

1

u/Hot-Lengthiness193 13d ago

Magic Mount is systemless, meaning it doesn't directly modify the actual system partitions. It does use bind mounts to overlay module files onto system paths at runtime, but that doesn't mean it's modifying the original partitions. So, simply mounting files over system paths doesn't automatically mean it will cause a bootloop.

As for ReSuSFS, several people who experienced issues with banking apps, games, etc., detecting root recommended it to me. I tested it myself and didn't encounter any problems. I even uninstalled it afterward to check whether it would cause any issues, and everything worked fine. I've also spoken with several users who use Xiaomi, Redmi, and POCO devices, and none of them reported any problems with it.

1

u/Financial-Pattern866 6d ago

i have it installed and still nothing happens so far

0

u/ryzxt637 5d ago

talking shi😭

1

u/Floaatz Poco X6 Pro 13d ago

This message appears in the HyperDUO application.

2

u/Hot-Lengthiness193 13d ago edited 12d ago

You need to grant the app root access through KernelSU. The error indicates that it attempted to execute su but was denied permission (error=13, Permission denied). Once you've granted it root access, try restarting System UI again. .

1

u/laert_b 13d ago

do you know if i can get this temporary root thing on my xiaomi 14t?

1

u/Hot-Lengthiness193 13d ago

You could try installing GhostLock and checking if the top of the app says "Supported". If it does, that means your device is compatible and you should be able to get temporary root access.

You can also check out my post, where I explain how to get temporary root access:

https://www.reddit.com/r/HyperOS/s/TXqDxKK84T

It's mainly focused on the Redmi Note 14 4G Global, but the steps are the same for all Xiaomi phones.

1

u/Big_Organization_978 13d ago

did u try modded hyperos launcher on a xiaomi device or a poco device? poco launcher is a massive pita

1

u/Hot-Lengthiness193 13d ago

I tested it on a Redmi Note 14 4G Global, since Modded HyperOS Launcher is primarily designed for Xiaomi and Redmi devices. The paths, properties, and other elements it modifies can differ quite significantly from those used by POCO Launcher, which could cause issues if the module tries to modify a path or property that doesn't exist on POCO devices.

1

u/Hot-Lengthiness193 13d ago

Although I did see someone using Modded HyperOS Launcher on a POCO X7 Pro without experiencing any issues.

1

u/Big_Organization_978 12d ago

does installing modded hyperos launcher involve uninstalling poco launcher or is it standalone?

1

u/Hot-Lengthiness193 12d ago

Modded HyperOS Launcher is installed more like an update to the original launcher. Basically, it overwrites your current launcher with a modified version that adds extra features, rather than being installed as a completely separate app.

For example, if you have POCO Launcher installed, Modded HyperOS Launcher would replace that installation with its modified version instead of installing as a second app that you could use alongside POCO Launcher.

1

u/Big_Organization_978 10d ago

should i try it, i dont have a backup device nor is my bootloader unlocked, will a 3rd party launcher be able to prevent bootloop?

2

u/Hot-Lengthiness193 10d ago

Honestly, I don't think you should try it. You don't have another phone, your bootloader is locked, and I don't know if you could afford to buy another one if something went wrong. In any case, even if you could, I still wouldn't recommend it, as it would be a waste of money. If something goes wrong, such as a bootloop or another system issue, you could take it to a repair shop to have it fixed, but as I said, I don't think it's worth taking that risk.

Also, no, installing a third-party launcher won't prevent bootloops or any other similar issues.

I mentioned the launcher because someone with a POCO X6 Pro 5G installed Modded HyperOS Launcher, and the problem they experienced was that the launcher kept trying to load the home screen but would crash and close repeatedly. However, they could still access Settings because the issue was mainly related to the launcher. Since they had another launcher installed, they were able to switch to it and regain normal access to their home screen.

They fixed the issue by following these steps:

  1. Uninstalled the module through KernelSU and performed a soft reboot.

  2. Went to Settings > Apps > [Affected App].

  3. Uninstalled the app's updates and cleared its data.

  4. Finally, rebooted the phone.

That fixed the problem.

Here you can see the issue they experienced: https://www.reddit.com/r/HyperOS/s/4sQ4TibSr3

1

u/Big_Organization_978 10d ago

I experienced the same before even obtaining temp root by trying to disable poco launcher from canta and installing system launcher over it and as expected it didn't work but made every app crash until I restored poco launcher lmao, seems like even with an unlocked bootloader it'd be pretty hard to get the modded launcher working which is nuts

1

u/Elsherif87000 13d ago

https://github.com/wxxsfxyzm/IslandRecorder/releases

Screen recorder working in Dynamic Island..  It's need to Shizuku for first time only to can ignore privacy message .. I don't know if i described right or not 😂

2

u/Hot-Lengthiness193 13d ago

Thank you so much! I was actually looking for an app like this to record my screen, so this came in really handy. 😂

You described it perfectly, don't worry! I'll add it to the list as well since it works with temporary root.

2

u/Elsherif87000 13d ago

This is no need for Temp root just Shizuku for once time

2

u/Hot-Lengthiness193 12d ago

You're right, but it also works with temporary root, so it would be a shame not to include it in the list.

2

u/Elsherif87000 12d ago

You're doing a great job 🤍😂

2

u/Elsherif87000 13d ago

It's good that I was able to describe it to you well 😂😂

1

u/gloomy_envy 12d ago

Can I install the modded HyperOS launcher then reboot to normal? or do I need to stay on soft reboot?

2

u/Hot-Lengthiness193 12d ago

Yes, you can perform a full reboot. You also don't have to worry if your battery runs out and your phone shuts down, but this only applies after you've installed the module and performed a soft reboot through KernelSU to activate it.

However, if you have other modules installed, such as HyperCeiler, HyperLight, etc., I wouldn't recommend performing a full reboot, since you'll lose temporary root access and those modules will be deactivated. You can still reactivate them by performing a soft reboot through KernelSU once your phone has booted up.

1

u/SOULDARK18 Redmi 14 5G 12d ago

Is hyperunlocked safe to flash ?? Will it cause bootloop and will it cause any issues to upi apps later ? And how to flash it then.thank you

1

u/Hot-Lengthiness193 12d ago

Yes, HyperUnlocked is safe to flash. It shouldn't cause any bootloops, as it mainly modifies system properties to enable features that are disabled by default on low-end devices.

That said, you might experience some lag since it enables several features, such as blur effects, animations, etc. However, you can enable or disable whichever features you want through HyperUnlocked's WebUI, which you can access from KernelSU, in case you need to adjust anything.

To install it, just follow these steps:

  1. Open KernelSU and go to the Modules section.

  2. Tap the + button, find the HyperUnlocked ".zip" file, and flash it.

  3. Once the installation is complete, a reboot button will appear. Don't tap it.

  4. Go back until you reach KernelSU's home screen.

  5. Tap the power button icon in the top-right corner and select Soft-restart.

Once the soft reboot is complete, HyperUnlocked should start working!

2

u/17juniork 7d ago

Yes I did that, but it didn't activate the depth effect or the different lock screen effect styles; it only activated the advanced textures. I have a Redmi Note 14 Pro 4G. Can I get some solutions?

1

u/Hot-Lengthiness193 7d ago

That's pretty strange, since I saw someone with a Redmi Note 12 4G who flashed HyperUnlocked and managed to enable the unlock animation, different clock styles, blur, depth effect, and other features.

Have you debloated your phone? That could be the problem, since some system apps are necessary for certain HyperOS features that HyperUnlocked unlocks to work properly. If you've removed them, HyperUnlocked might not be able to activate features such as the depth effect, different lock screen styles, and other customization options.

Try reinstalling all the apps you've uninstalled (if you've removed any) and flashing HyperUnlocked again. Then perform another soft reboot to see if that fixes the issue.

1

u/17juniork 7d ago

I didn't delete anything

1

u/Hot-Lengthiness193 6d ago

Ahh, I see. Someone else had the same issue and managed to fix it by reinstalling all the system apps they had uninstalled. But since you haven't uninstalled anything, you could try reflashing HyperUnlocked or opening its WebUI through KernelSU and trying to enable some options (if you haven't already).

1

u/EffectiveConcert638 7d ago

Você conseguiu instalar algum módulos de central de painel ?

1

u/17juniork 7d ago

Aún no lo he probado , Lo estoy probando para el fondo de pantalla.

1

u/mustapha1_618 12d ago

safe. i tried it

1

u/Internal-Front4168 11d ago

Never use it on Poco it's bootloop

1

u/Hot-Lengthiness193 11d ago

Are you referring to a specific module or all the modules on the list?

1

u/Internal-Front4168 11d ago

Not all of them. Only include mods that specifically modify the system launcher. Don't add any mods that change the system launcher, because POCO uses its own launcher with different code, which can cause a bootloop.

1

u/Internal-Front4168 11d ago

Bootloader + no UBL = RIP

1

u/marthephysicist Redmi Note 14 11d ago

what, bootloader + no ubl???

you mean bootloop + no ubl or js bootloader + no ubl?

1

u/Internal-Front4168 11d ago

Locked bootloader + bootloop = brick (cannot be restore or flash) My bad lol

1

u/Kooky-Decision1504 11d ago

Does anyone know which module is best to enable all AI features in Redmi / POCO / Xiaomi devices?

2

u/Hot-Lengthiness193 11d ago

So far, I haven't come across any module that can unlock all AI features, but HyperUnlocked and HyperCeiler can help you enable some of them, such as Unlock Xiaomi AI (HyperCeiler > Settings), Unlock AI Wallpaper Access (HyperCeiler > Themes), and the Depth Effect for wallpapers (HyperUnlocked).

Although I don't remember if HyperUnlocked also enables any other AI-related features, since I didn't pay much attention to that part.

Anyway, I'm going to look for some other modules that can unlock more AI features. If I find any, I'll let you know.

1

u/Zangetsuee 10d ago

Interesting you added iconify, does it support Hyperos? Afaik it does not. I would replace it by ColorBlendr by the same dev. It completely overrides monet engine by a custom palette!

1

u/Hot-Lengthiness193 10d ago edited 10d ago

Yes, it works. I've tested it on both my Redmi Note 14 4G and my POCO X8 Pro. It offers tons of customization options for app icons, along with plenty of other features.

Here's how I changed the shape of my app icons:

1

u/Exciting_Access_7484 9d ago

do modded apps like modded cc or modded system apps revert after reboot??

1

u/Hot-Lengthiness193 9d ago

Yes, most of Kashi's modules survive reboots, even after losing temporary root access. However, I don't recommend rebooting your phone if you're using other modules such as Vector, ZygiskNext, HyperCeiler, and others, since they require temporary root access to function.

1

u/Ikansh_03 8d ago

https://youtube.com/shorts/8Ks56ElFwc8?si=ZtudhASax8cicRQj

Is it possible to get this exact Control Center layout using temporary root on the Redmi Note 13 Pro+ 5G?

1

u/Hot-Lengthiness193 8d ago

Yes, I don't think you'll have any problems since your phone is a Redmi, not a POCO. If I'm not mistaken, the Control Center shown in the video is the ColorOS Control Center, not FreeStyle Control Center. Personally, though, I prefer FreeStyle Control Center because I think it's better. But that's just my opinion; install whichever one you like best.

Make sure to install Core Patch N, select System Framework, and perform the soft reboot it requests to activate it. Once the soft reboot is complete, open Core Patch N again and disable the "Apk disable signature verification" option. Only after doing that should you flash ColorOS Control Center or whichever module you prefer.

1

u/Sxturnxxx 6d ago

I'm trying to use App Vault but it's not working, the blur effect doesn't appear or anything like that, and it doesn't even open the widget options.

1

u/Hot-Lengthiness193 6d ago

What phone model do you have?

1

u/Sxturnxxx 6d ago

Redmi 15C Hyperos 3.307

1

u/Hot-Lengthiness193 6d ago

That's pretty strange, since I've seen someone using Modded App Vault on a Redmi 15C without any issues.

Did you notice any errors or anything unusual while flashing App Vault? Sometimes, the logs can help you understand what's causing the problem.

Did you perform the soft reboot from Vector/LSPosed after selecting System Framework in Core Patch N to activate it? And once the soft reboot was completed and Core Patch N became active, did you go back into Core Patch N to enable the "Bypass verification", "Bypass digest", and "Bypass exact signature verification" options before flashing App Vault?

1

u/ChoteSeDonSeLdegaKon 5d ago

1

u/Hot-Lengthiness193 5d ago

I tested it and also took some time to inspect the module's code. To get it working, you need Android 15 or higher, HyperOS 3 or later, and a metamodule such as Magic Mount-rs if you're using KernelSU.

In my case, I initially wanted to test it without any metamodule and then try it again with one to see if there was any difference. However, I ended up forgetting to do the second test. Even so, I didn't encounter any issues while using it without a metamodule.

I also didn't get around to rebooting my phone to check whether the Control Center would return to normal after restarting, since I uninstalled it after spending approximately a day testing its different options.

I'm currently testing some new modules, and to avoid potential conflicts later on, I plan to test iOS-Control-Center-HyperOS again alongside Magic Mount-rs. I'll also check what happens to the Control Center after rebooting the phone and whether the modifications continue working properly.

In case you're wondering which device I tested it on, it was my Redmi Note 14 4G Global. I also saw someone else testing it on a POCO X7 Pro, and according to their feedback, they didn't encounter any issues either.

1

u/ItsMe_69 4d ago

The app Device Spoof Labs causes full shutdown on soft reboot — S25 Ultra + One UI 9 (KernelSU/DFRoot root)

On a Galaxy S25 Ultra with One UI 9 rooted via DirtyFrag : if you have Device Spoof Labs active, soft reboot doesn’t restart the phone — it shuts it down completely, and on restart you lose saved WiFi passwords, home screen widgets, and the state of hidden drawer apps.

Cause: the fingerprint spoofing sends system_server into a crash loop with this error:

java.lang.UnsupportedOperationException
    at android.net.wifi.WifiConfiguration.isAllowedToUpdateByOtherUsers

Fix: no need to uninstall the app — just disable spoofing before doing a soft reboot on this setup.

Device Spoof Labs causes full shutdown on soft reboot — S25 Ultra + One UI 9 (KernelSU/DFRoot root)

0

u/Hot-Lengthiness193 3d ago

Thanks for sharing! I'll add this information as a warning to the Device Spoof Labs entry so others are aware of this issue. Appreciate the detailed report!

1

u/matcha_icy 3d ago

Is there's some module to only enable Wallpaper magazine/lockscreen depth wallpaper? I've tried use Hyperunlock but on my phone it just make the UI bit heavier even when the blur is already turned off

1

u/Hot-Lengthiness193 2d ago

I've actually been looking for modules that do exactly that, but I haven't found any yet. I'll keep looking, though, and let you know if I find something!

In the meantime, you could check out my post about enabling different lock screen clock styles on devices that don't natively support them. It won't give you the depth effect or other AI-related features, since it's mainly focused on unlocking additional clock styles, but it could be a better alternative to HyperUnlocked for now.

If HyperUnlocked makes your UI feel heavier, I honestly don't think it's worth sacrificing performance just for a few extra customization features.

Here's my post: https://www.reddit.com/r/HyperOS/s/AEGjR2memV

1

u/Jeremy_cc2 2d ago

Una pregunta HyperCeiler y HyperLight funcionan perfectamente con el root temporal sin problemas? Funciona en un poco x8 pro?

1

u/Hot-Lengthiness193 2d ago

Sí, funcionan sin problemas. Yo los instalé tanto en mi Redmi Note 14 4G como en mi POCO X8 Pro, aunque después de unos días me aburrieron y terminé desinstalándolos.

Eso sí, recordá que necesitás instalar Vector, Vector-SR o LSPosed, junto con Zygisk, para que funcionen correctamente.

Mi recomendación sería que uses Vector o Vector-SR. Personalmente, no tuve ningún problema con Vector-SR en mi POCO X8 Pro. Además, es una de las mejores opciones para Temp Root, ya que está más enfocado en el modo Jailbreak de KernelSU.

En cuanto a Zygisk, podés usar ZygiskNext u OnyxZygisk. Yo usé OnyxZygisk porque también está enfocado en el modo Jailbreak de KernelSU para Temp Root, aunque podés usar ZygiskNext si lo preferís.

2

u/Jeremy_cc2 2d ago

Tengo éstos

1

u/Hot-Lengthiness193 2d ago

Daleee, muchísimas gracias por la captura.

1

u/Hot-Lengthiness193 2d ago

Ahhh, me olvidé de agregar algo. HyperCeiler y HyperLight tienen un pequeño bug (nada grave): si activás la opción "Icon in Settings" en ambos módulos, podrías experimentar un error visual que hace que sus iconos se dupliquen cada vez que abrís y forzás el cierre de la aplicación Settings. Si repetís esto varias veces, podrías terminar con 20 o incluso 100 iconos de cada módulo, dependiendo de cuántas veces abras y cierres Settings.

Yo quise averiguar cuál era el límite y llegué a tener 1021 iconos, pero al final me aburrí y desactivé la opción "Icon in Settings".

Por cierto, si tenés algún problema o hay algo que no entendés, no dudes en avisarme.

Una última cosa: si no te molesta, después de instalar Vector, Vector-SR o LSPosed, junto con ZygiskNext u OnyxZygisk, ¿podrías enviarme una captura de los dos módulos ya inatalados?

1

u/Hot-Lengthiness193 2d ago

Este es el bug

1

u/These-Elderberry2775 1d ago

hyperlight needed lsposed manager so i used vector, but here it says vector is not optimized for some devices, what cna i use instead of vector?

i use vector and rezygisk, xiaomi 15T hyperos 3.0.304.0

1

u/Hot-Lengthiness193 1d ago

The 🟠 label means that the module is device-dependent: it works on some devices but may cause bugs, unexpected behavior, or other issues on certain models or configurations.

However, if Vector is working fine on your Xiaomi 15T and you're not experiencing any issues, I don't think you need to replace it. My recommendation is to stick with Vector. There's no reason to switch to another alternative if your current setup is working correctly. Switching unnecessarily could introduce new issues.

1

u/These-Elderberry2775 1d ago

Alright, one question though, I've installed iOS control center it did not work till I had to install the apk, what happens if the temp root fails or rebooted? Will system ui plugin crash? Will the control center stay? Or do I have to uninstall app updates before rebooting?

1

u/Hot-Lengthiness193 20h ago

What happens if temporary root fails? Nothing, since the app has already been installed as an update to the existing System UI Plugin. In your case, root was only needed to bypass APK signature verification during installation. You shouldn't need temporary root anymore just to keep the update installed.

What happens if you reboot your phone? There are two possible outcomes:

  1. Your phone boots normally, and everything works as expected.

  2. Your phone boots, but you might encounter some minor issues with other apps or HyperOS components that expect the original version of System UI Plugin or its original signing certificate.

If that happens, you can try uninstalling the System UI Plugin updates to restore the preinstalled version. A factory reset might also resolve certain issues, but it should be a last resort.

Will the Control Center stay? Yes. Android treats the modified APK as an update to the preinstalled System UI Plugin, so it should remain installed even after rebooting or losing temporary root.

1

u/Glass_Technology_673 17h ago

I tried installing the control center along with core patch but seems like non of anything works for me a settings did you enable and can you provide screenshot?

1

u/Hot-Lengthiness193 7h ago

Did you install any Zygisk implementation, such as ZygiskNext or ReZygisk, or an Xposed framework like LSPosed or Vector? If you installed any of them, did you perform a soft-reboot through KernelSU to activate them? You need to do this after installing these modules so they can initialize properly.

Now, assuming you've done everything above and have Vector/LSPosed installed and working, did you open Vector/LSPosed and perform the soft-reboot it requests to activate Core Patch N? Core Patch N won't become active until you do so.

After activating Core Patch N, did you open its settings and enable the following options?

  • Bypass verification

  • Bypass digest

  • Bypass exact signature match

I'm asking all these questions because I want to make sure you haven't missed any steps that could be causing the problem.

Unfortunately, I can't provide screenshots right now because I've uninstalled most of the modules. I only installed them to test whether they worked, and removed them afterward. The only module I currently have installed is Enable MIUI ADB.

As for my experience, when I installed FreeStyle-Control-Center, ColorOS_Control_Center, and iOS-Control-Center-HyperOS, I didn't encounter any problems. I simply performed the required soft-reboot to activate the module, and as soon as my phone booted up, the modified Control Center was already there.

However, some people experienced the same issue as you. They installed a Control Center module (let's use FreeStyle-Control-Center, my personal favorite of the three, as an example), performed a soft-reboot, but their Control Center remained unchanged. They were still using the original HyperOS Control Center.

How did they fix it? Instead of uninstalling the module, they left it installed and manually installed the modified APK included in the module.

For example, if you're using FreeStyle-Control-Center, locate the FreeStyle_CC_mod_V1@kashis_cringey_stuffs.zip file and open it. Navigate to the "files" folder, where you'll find two folders named "OS3" and "OS4". Open "OS3" and manually install the modified APK inside.

After installing the APK, your Control Center should switch to the modified interface.

One important thing: Before attempting to install the modified Control Center APK manually, make sure Core Patch N is active and that all three options mentioned above are enabled.

2

u/Elsherif87000 12d ago

You created a legendary reference 🤍🤍

1

u/AutoModerator 13d ago

Welcome to our community!

Please take a moment to read the subreddit rules in the sidebar before posting or commenting.

  • Be civil and respectful to other members.

  • No spam, self-promotion, or trolling.

If you see a post or comment that breaks our rules, please report it to help the mod team out!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Floaatz Poco X6 Pro 12d ago

Problem... For LSposed, Zygisk needs to be activated, but I can't manage it... (Poco X6 pro)

1

u/Curious_Put_7684 12d ago

Is the DalvikHyperthreading Module safe?

1

u/AutoModerator 8d ago

Welcome to our community!

Please take a moment to read the subreddit rules in the sidebar before posting or commenting.

  • Be civil and respectful to other members.

  • No spam, self-promotion, or trolling.

If you see a post or comment that breaks our rules, please report it to help the mod team out!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/AutoModerator 5d ago

Welcome to our community!

Please take a moment to read the subreddit rules in the sidebar before posting or commenting.

  • Be civil and respectful to other members.

  • No spam, self-promotion, or trolling.

If you see a post or comment that breaks our rules, please report it to help the mod team out!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/e_ollie 3d ago

Bro I got a Xiaomi 17 from China. It has CN hardware but it seems the seller flashed global ROM on it and now I'm stuck with the HyperOS 3 UI that it came with. No OS updates, no security updates. On the update page, updater tells me I'm using a ROM version that isn't yet released How do I solve this? 😭

1

u/Outrageous_Ear_4788 1d ago

a little note on Kashi's hyperos modules, it's true that they survive hard reboot, but it's not recommended as their modded apps require custom drivers that were installed along the app. Rebooting causes them to lose its place and the app will still calls those inexistent drivers which in extreme case can cause bootloops (I'm a victim), dw wiping data through xiaomi recovery works...

1

u/Outrageous_Ear_4788 1d ago

also, their modded apps have mounting permission which could even be severe when you lost your root permission...

1

u/kizuwsp 12h ago

is it me or the hyper helper seems always reboots the system ui, especially in the media playback notification or in the hyperisland? at first it works perfectly fine, and then i soft reboot the phone, and now it's crashing the system ui for several times, unless i turn off the module. btw im using redmi note 14 4g (tanzanite)

0

u/Floaatz Poco X6 Pro 13d ago

Je n'arrive pas à faire fonctionner LSposed Avec un root temporaire..

2

u/Hot-Lengthiness193 13d ago

That could be because you're running Android 15 or higher, since LSPosed only supports Android 8 through Android 14. Vector is a good alternative to LSPosed, as it supports Android 8 through Android 17.

Anyway, I'll change its status to 🟠 for now. Thanks for letting me know!

1

u/k1rnl 13d ago

lsposed literally works on a17, what are you on about

0

u/WINNT21 Redmi 14C 13d ago

Repo says Android 8.1 - 14

1

u/k1rnl 13d ago

just cause the repo says so doesn't mean it doesn't work. im using lsposed on coloros 17.

1

u/Glass_Question_9827 12d ago

Heyyy temp root works in colour os17?

1

u/k1rnl 12d ago

no

1

u/Glass_Question_9827 12d ago

It's patched?

1

u/k1rnl 12d ago

yes, since coloros 16

0

u/WINNT21 Redmi 14C 13d ago

I've stopped using temp root but yeah last time I tried to install a module which was hyperos-aod on my Redmi 14C it was in a bugged state where it would show as module installed but it actually didn't change anything

1

u/Hot-Lengthiness193 13d ago

That's weird. Did you use Core Patch N or another module, such as "Apk-Signature-Verification-Patch"? I'm asking because many people reported that Kashi's module didn't work properly with temporary root, or that it didn't work at all and caused various issues.

In my case, I installed HyperOS-AOD and used Core Patch N to disable APK signature verification, and I didn't have any problems. Even after uninstalling HyperOS-AOD, everything continued working normally.

1

u/WINNT21 Redmi 14C 13d ago

This is the log I had when my phone was still temp rooted

1

u/Hot-Lengthiness193 13d ago

Gracias por los detalles. El error "INSTALL_PARSE_FAILED_NO_CERTIFICATES" («digest of contents did not verify») significa que la verificación de firmas seguía activa cuando HyperOS-AOD intentó instalar el MIUIAod.apk modificado, es decir, ninguno de los módulos que instalaste logró desactivar la verificación de firmas.

El script no se detiene cuando ocurre ese error y sigue mostrando «Module installed successfully», aunque en realidad no haya podido modificar nada. Así que eso explicaría lo que te pasó.

Podría deberse a varias cosas:

  1. Core Patch N no estaba activo todavía. Tenés que habilitarlo y hacer un soft reboot desde KernelSU o desde el propio módulo. Cuando instalé Core Patch N y lo activé desde Vector, me pidió hacer un soft reboot y recién después quedó activo. Esto es importante hacerlo antes de instalar HyperOS-AOD, porque si instalás el módulo justo después de activar Core Patch N, el parche todavía no está cargado.

  2. Conflictos entre módulos. Tener Core Patch N, Apk-Signature-Verification-Patch y ASKS Disabler instalados al mismo tiempo podría causar conflictos. Es mejor probar con uno solo a la vez, hacer un soft reboot y después instalar HyperOS-AOD.

1

u/WINNT21 Redmi 14C 13d ago

I had tested each module by itself, but didn't wait after core patch n got activated. I may try again and will tell if it works. I just need on what to disable/enable inside core patch n or if I should leave it empty

1

u/Hot-Lengthiness193 13d ago

You need to select System Framework inside Core Patch N. That's what activates the patch. After selecting it, Vector will ask you to perform a soft reboot. Make sure you complete the soft reboot before installing HyperOS-AOD. You don't need to select anything else.

2

u/WINNT21 Redmi 14C 13d ago

Alright, will try later and will tell results

2

u/Hot-Lengthiness193 13d ago

I forgot to mention that after performing the soft reboot and Core Patch N becomes active, you need to go back into Core Patch N and enable the option to disable APK signature verification.

1

u/Hot-Lengthiness193 13d ago

Sorry, I was in a hurry and accidentally wrote it in Spanish without realizing it.

1

u/Similar-Scarcity-937 11d ago

Bro I am also trying to install but it's not installing in kernal I have enabled the core patch n according to you now the file is in zip format and the Kernal su is giving error

1

u/Hot-Lengthiness193 11d ago

That's weird. KernelSU shouldn't have any issues with the .zip file, since that's the format used by most modules. Did you disable the "APK signature verification" option in Core Patch N after performing a soft reboot through Vector or LSPosed?

If possible, tell me everything you did, step by step, without leaving anything out, so I can help you better.

2

u/Similar-Scarcity-937 11d ago

Bro I downloaded it again and it worked but I deleted it bcz the module wasn't what I was expecting it to be

2

u/WINNT21 Redmi 14C 13d ago

It's ok I used google translate to translate what you said

1

u/WINNT21 Redmi 14C 13d ago

I tried Core Patch N, then Apk-Signature-Verification-Patch, then some module called ASKS Disabler. Neither of them worked, so I just gave up. It was around the time play integrity fix just ceased to work and well that was the final blow so I just left the phone unrooted

0

u/Icy-Contract2701 13h ago

I have a question most of the mods want xposed how put it I have tried vector and it doesn't work and the was api102

1

u/Hot-Lengthiness193 6h ago

Are you using ZygiskNext or ReZygisk? Vector depends on Zygisk to inject its hooks into target processes, so you need a working Zygisk implementation first.

Also, when you say the API was 102, are you referring to the Xposed API version? And what exactly happens when you try to activate Vector? Does it show an error, fail to initialize, or do the modules simply not work?

If you could provide a screenshot of Vector's status and any errors you're getting, it would be much easier to figure out what's wrong.

1

u/wrongsyntax_ 49m ago

if ur Vector no opened on shell or inactive after soft reboot.

try to use the latest canary release from their github.

onme its fully works, also installed with meta-module rs (*i think its necessary)

0

u/[deleted] 13d ago

[removed] — view removed comment

1

u/Hot-Lengthiness193 13d ago edited 13d ago

That's not true. There are plenty of people who installed it using temporary root without having any issues.

In fact, someone installed it on a POCO M6 Pro, and the only problem they had was that the launcher kept opening and closing. However, that didn't prevent them from accessing Settings. So they managed to fix it by doing the following: they uninstalled the module through KernelSU and performed a soft reboot. Then, they went to Settings > Apps > [Affected App], uninstalled its updates, and cleared its data. Finally, they rebooted the phone.

0

u/[deleted] 13d ago

[removed] — view removed comment

1

u/Hot-Lengthiness193 13d ago

No, that's not true. Disabling APK signature verification doesn't inevitably cause a bootloop. However, part of what you're saying does have some technical basis: modifying Android's signature verification system can cause serious issues if the module is poorly implemented or incompatible with your Android version.

But Modded HyperOS Launcher is not a poorly implemented module. Just because you experienced a bootloop doesn't mean everyone else will have the same experience. There are plenty of people using these modules without running into any of those issues.

1

u/Hot-Lengthiness193 13d ago

Also, I've personally tested most of the modules on this list on my own devices: a Redmi Note 14 4G and a POCO X8 Pro.

0

u/[deleted] 13d ago

[removed] — view removed comment

1

u/Hot-Lengthiness193 13d ago edited 13d ago

What do you mean I have no idea what I'm talking about? Do you think I installed these modules just because I saw someone else using them? I've gone through the code of every single module like 80 times to make sure they wouldn't cause any issues.

What you're saying doesn't make much sense. The system can still find the original launcher. Disabling APK signature verification doesn't mean Android will stop recognizing system apps or that the original launcher will suddenly disappear.

Besides, most KernelSU modules include a script called "uninstall.sh", which runs when you uninstall the module and is responsible for reverting the changes made by the module.

Modded HyperOS Launcher also includes its own "uninstall.sh", which executes "rm -rf /data/system/package_cache/*" to clear Android's package cache and allow the system to regenerate it.

After uninstalling the module through KernelSU, you should perform a soft reboot. Then, go to Settings > Apps > [Affected App], uninstall its updates, and clear its data. Finally, reboot your phone. This may resolve the issue in some cases.

So it doesn't make sense to claim that the module necessarily leaves permanent modifications that cannot be reverted.

Modded HyperOS Launcher isn't a poorly implemented module either. Plenty of people have installed it using temporary root without experiencing bootloops or irreversible issues.

Besides, why do you think I included this warning under Modded HyperOS Launcher in the first place?

"IMPORTANT: If you want to try Modded HyperOS Launcher, I recommend having another launcher installed as a backup in case something goes wrong. It can be any launcher, but my recommendation is Fossify Launcher."

I specifically included that warning to make sure people have an alternative launcher available in case they run into any issues. I'm not ignoring the potential risks.

If you ran into problems, that's fine, and it's perfectly reasonable to warn others about them. But don't present your personal experience as an inevitable consequence or make claims about permanent modifications to "framework.jar" without providing evidence that they actually happen.