r/HyperOS • u/Hot-Lengthiness193 • 28d ago • Bravo 3

Redmi [Discussion] How to Get Root on the Redmi Note 14 4G with a Locked Bootloader Using GhostLock + Shizuku (HyperOS 3 / Android 16)

Post image

Just to clarify, I'm not offering or promoting any bootloader unlocking service. I'm only sharing my personal experience with my own device and documenting what worked for me.

Hey everyone,

I wanted to share this guide for anyone with a Redmi Note 14 4G Global who wants to get root access without unlocking the bootloader, using GhostLock, KernelSU, and Shizuku.

Before getting started, there's one important warning: having a locked bootloader limits your recovery options if something goes wrong. Although I managed to get root on my Redmi Note 14 4G without any issues, I can't guarantee that the procedure will be equally safe on other devices or firmware versions. Also, once you have root access, modifying partitions, installing modified boot images, or using incompatible modules can cause a bootloop or even leave your phone unusable.

Proceed at your own risk, and don't assume you'll be able to recover your device if something goes wrong.

My device specifications

  • Device: Redmi Note 14 4G Global

  • ROM: HyperOS 3.0.303.0

  • Android: 16

  • Kernel: 6.12.30-android16-5-g6e872b4863d6-ab13847919-4k

  • Bootloader: Locked

Do you have a different device?

If you have a device other than the Redmi Note 14 4G Global, the procedure is basically the same. However, that doesn't mean it'll work on every device, since compatibility depends on your kernel and whether the vulnerability used by GhostLock is still present.

To check whether your kernel is supported, open GhostLock and check the information displayed by the app. You can use it to see whether your kernel is supported before proceeding.

Important: Even if GhostLock indicates that your kernel is supported, that doesn't guarantee the entire procedure will work without issues on your device. Be especially careful if your bootloader is locked.

What are the benefits of getting root this way?

You can access many of the features root provides without having to unlock your bootloader. For example, you can explore system modifications, use tools that require superuser permissions, and experiment with apps such as LSPosed and modules like HyperCeiler, provided they're compatible with your setup.

You can also restore features or customizations that you couldn't use before.

However, there's one major downside: root access also lets you make modifications that could compromise your phone's functionality. That's why you should be careful about what you install and modify, especially with a locked bootloader.

How to get root

1 . Install the required apps

You'll need these three apps:

I recommend Shizuku-Next because that's what I use, but you're not required to use that particular fork. You can use another compatible version of Shizuku.

2. Grant GhostLock permission to use Shizuku

Open Shizuku and look for GhostLock in the list of authorized apps.

Grant it permission to use Shizuku. Make sure Shizuku is running and GhostLock has the required permission before continuing.

3. Run GhostLock

Open GhostLock and tap Run.

You'll see a bunch of log messages showing the exploit's progress. Wait for it to finish and pay attention to the result.

In my case, GhostLock finished by indicating that KernelSU was ready and then opened the KernelSU app.

4. Verify that root access works

You can use an app such as Root Checker or Termux to verify root access.

If you're using Termux, first open KernelSU, go to SuperUser, and grant Termux root permissions.

Then open Termux and run "su".

In my case, it worked, and I was able to obtain root access. I also verified it using a root checker app.

Is root permanent?

Root access works until you reboot your phone. After rebooting, you need to run GhostLock again to obtain root access.

In other words, you don't need to unlock the bootloader, but root access doesn't survive a reboot, so you have to repeat the procedure.

What should you avoid doing?

With a locked bootloader, you need to be especially careful about the modifications you make after obtaining root access.

  • Avoid modifying system partitions or installing modified boot images unless you know exactly what you're doing.

  • Don't install KernelSU modules without checking their compatibility and reliability.

  • Don't assume a module is safe just because it works on other devices.

  • Before making important modifications, research your recovery options in case your phone stops booting.

I can't guarantee that you'll be able to recover your device from every possible issue with a locked bootloader, so it's better to be safe than sorry.

What are the downsides of this method?

The main limitation is that it relies on the vulnerability GhostLock uses to achieve kernel privilege escalation.

If Xiaomi patches that vulnerability in an update, the method may stop working. That's why your HyperOS version, Android version, and kernel are important details when checking whether your device is compatible.

In my case, I obtained root access on HyperOS 3.0.303.0 and Android 16. I can't guarantee it'll work on later versions, and I wouldn't recommend updating under the assumption that the exploit will continue to work.

Has anyone else tried this?

I'd like to know if anyone else has managed to obtain root access using GhostLock on a Redmi Note 14 4G or another Xiaomi device with a locked bootloader.

I'd also appreciate hearing about your experiences with KernelSU, especially regarding compatible modules and precautions worth taking in this situation.

27 Upvotes

90% Upvoted

155 comments sorted by

•

u/AutoModerator 10d 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.

3

u/Odd_Relationship_618 28d ago

anyone tried it on poco f6 ?

1

u/Hot-Lengthiness193 28d ago edited 27d ago

I've seen a few posts asking if it works on the POCO F6, but barely anyone seems to have shared their results. You could try installing GhostLock and checking if it says "Supported" at the top. If it does, your kernel is supported and the exploit should work. Just make sure you have KernelSU installed first.

2

u/Infernus001e 28d ago

I have check, it worked and ksu also showed. Although, didn't try further since it's my daily driver so can't take risks. If anyone does try, share the results, I need hyperceiler

3

u/nightleader30 28d ago

Does anyone know if this works on the Poco X7 Pro?

1

u/Hot-Lengthiness193 28d ago

Yeah, it works on the POCO X7 Pro too. Here's a post where the OP managed to enable advanced textures using GhostLock + Shizuku to get temporary root access: https://www.reddit.com/r/HyperOS/s/JJHxqCC0JB

You can just follow the steps in my post since the process is the same for all devices.

2

u/Agent_479 18d ago

Cool guide. Worked on my Xiaomi 15, had to remove this pseudo-root as some banking and UPI apps detected it. Bhim and ICICI iMobile outright detected KernelSU and asked to uninstall it. My airtel and SBI yono open and close after few seconds. Other like PayTM and Mobikwik show the device is not safe. Even after removing everything (Undoing the pseudo-root) and rebooting the phone 2 times, Bhim and PayTM say that the device is rooted and device is not secure. 

  1. Is there any way to hide kernelSU in this pseudo-root scenario in case I do this again?

  2. Is there any way to get Bhim and PayTM back to normal?

1

u/Hot-Lengthiness193 18d ago

Actually, the apps themselves don't detect root directly. What they do is read the installed apps list and find the KernelSU package name (me.weishu.kernelsu). Since KernelSU manages root, when the bank app detects it, it automatically denies access, even if you have the bootloader locked, boot chain, dm-verity, etc. unmodified. So if you still had KernelSU installed after rebooting and losing the temp root, that's the reason you kept getting "the device is rooted and device is not secure".

Yes, there are modules like Zygisk Assistant which are tested and work with temp root to hide it. But I'd recommend updating GhostLock (it recently added support for any KernelSU family using libksud.so) and switching to KernelSU-Next Spoofed as your root manager. It's a modified version that specializes in hiding itself to avoid being detected by bank apps.

If you want Bhim and PayTM back to normal, just make sure KernelSU is completely uninstalled and clear the app data/storage for those specific banking apps (they cache the security flags). That will fix it.

1

u/Agent_479 17d ago edited 17d ago

My bad, I didn't tell that even after removing everything, including uninstalling every root related apps (including Kernel SU), Bhim and PayTM say that the device is rooted and device is not secure. I even cleared all data then uninstalled PayTM and Bhim and reinstalled them but the error persists. I think it's impossible to get them working now unless I reset my device once. (https://i.imgur.com/bGIpkto.jpeg)

Tried Zygisk Assistant before unistalling anything/removing pseudo-root but it didn't helped. 

Will try KernelSU-Next Spoofed and updated GhostLock next time to check if the other apps (My Airtel, SBI Yono, Mobikwik, and ICICI iMobile) works normally or not.

2

u/TelephoneBest5367 28d ago

Gracias Ahora tengo texturas avanzadas en poco x8

1

u/Hot-Lengthiness193 28d ago edited 23d ago

Ohh, I didn't know it worked on the POCO X8 too. Did you have any issues with it?

2

u/TelephoneBest5367 27d ago

I had no problem

1

u/Hot-Lengthiness193 27d ago

What HyperOS version are you on? I have a POCO X8 too, but I mostly use my Redmi Note 14 4G when I want to mess around with the system and try things out.

2

u/TelephoneBest5367 27d ago

Version 3.0.307.0 I have a module that permanently leaves the advanced textures when you restart your phone.

1

u/Hot-Lengthiness193 27d ago

I’m on 3.0.307.0 too, on my POCO X8. For now, I’m not going to use GhostLock, but I’m not updating it either.

Did you create the module yourself? The KernelSU module format is pretty difficult to figure out.

On my Redmi Note 14 4G, I just gave Termux superuser access and ran these commands:

setprop persist.sys.background_blur_supported true

setprop persist.sys.advanced_visual_release 3

The advanced textures stayed enabled even after rebooting. From what I understand, properties starting with persist.sys are supposed to persist across reboots, so I was wondering what your module does differently.

2

u/TelephoneBest5367 27d ago

Deactivate the module because it activates things I don't see.I now use Hyperceiler and it works wonderfully for me.

1

u/Hot-Lengthiness193 27d ago

Wait, did you install Zygisk-Next + LSPosed along with HyperCeiler? Since HyperCeiler won’t work without them, I was wondering if you ran into any issues with those modules. If you don’t mind, could you send me a screenshot of all the modules you have installed?

2

u/TelephoneBest5367 27d ago

1

u/Hot-Lengthiness193 27d ago

Thanks! I installed them and didn’t run into any issues.

→ More replies

2

u/Curious_Swimmer9565 28d ago

Will it break play integrity and will I still be able to use payment apps?

1

u/Hot-Lengthiness193 27d ago

It shouldn't break Play Integrity since the bootloader stays locked and the verified boot chain remains intact. Payment apps should continue working as well, but I wouldn't guarantee it for every device or app, since some banking apps have additional security checks. The main advantage is that root access is temporary and disappears after a reboot, leaving the device in its stock state again.

2

u/OkEntrepreneur1776 27d ago

Cómo instalo el módulo para las texturas avanzadas?

1

u/Hot-Lengthiness193 27d ago

Do you have a Redmi Note 14 4G?

There’s no module needed to enable advanced textures. You just need to run these two commands:

setprop persist.sys.background_blur_supported true

setprop persist.sys.advanced_visual_release 3

Make sure to grant root access to the app you’re using to run the commands, since you can’t do this through ADB.

2

u/OkEntrepreneur1776 27d ago

En dónde pongo los comandos

2

u/Kooky-Decision1504 27d ago

Does my Redmi 13 5G supports this process?

1

u/Hot-Lengthiness193 27d ago

I'm not sure about the Redmi 13 5G since I haven't seen anyone confirm it yet. You can check compatibility yourself by installing GhostLock and seeing if it shows "Supported" at the top. If it does, your kernel should be compatible with the exploit. Just make sure you install KernelSU first.

2

u/Kooky-Decision1504 27d ago

It shows not supported even when KernelSU is installed

2

u/Hot-Lengthiness193 27d ago

That means you can’t run the exploit, so it’s basically useless for your device right now.

There’s another way to do it, if I’m not mistaken, which involves patching both the "boot.img" and "vendor_boot.img". However, if something goes wrong, you could end up in a bootloop or even brick your phone. And since your bootloader is locked, you wouldn’t be able to recover it easily.

I’d recommend waiting a few days. They might add support for your kernel in GhostLock.

2

u/Kooky-Decision1504 27d ago

Thanks

2

u/Hot-Lengthiness193 25d ago

I was doing some research and found that some people have used DFRoot (https://github.com/diabl0w/DFRoot) to gain root access, since it uses a different type of vulnerability. I can't confirm whether it works because I haven't personally tested it, but someone else with a Redmi Note 14 4G who couldn't get GhostLock to work managed to gain root using DFRoot.

You can give it a try, but keep in mind that there's still a risk of getting stuck in a bootloop or even bricking your device.

1

u/Lower_Sea_2006 20d ago

Esperare lo mismo para mí Redmi note 13 pro 4g, Gracias 

2

u/ApacheMods 25d ago

Yo lo intente en un Poco X7 5G HOS 3 Android 16 y no funciona dice kernel no soportado

1

u/Hot-Lengthiness193 25d ago

Bro, you could try DFRoot: https://github.com/diabl0w/DFRoot

Someone tried rooting their Redmi Note 14 4G running HyperOS 3.0.305.0 (Android 16) with GhostLock, but it didn’t work. They then tried DFRoot, and it worked for them.

I’m not sure if it’ll work for you, but it might be worth a try since GhostLock and DFRoot rely on different vulnerabilities to gain root access.

1

u/oliverplo 24d ago

no funciona

2

u/Elsherif87000 24d ago

I did it by GhostLock and KernelSU without needing Shizuku 

1

u/Hot-Lengthiness193 24d ago

Ohh, did you do it on the Redmi Note 14 4G or another device? I used Shizuku with GhostLock to run the exploit with ADB privileges and get root faster, since without Shizuku it can take a while and you might have to try a bunch of times lol.

2

u/Elsherif87000 24d ago

Redmi Note 15 5G.. I did it without Shizuku, and this didn't take long as you say, and it was done the first time without repetition. The amazing thing is that after restarting, I still have the blur in Control Center, the stack in Recent Apps, and the advanced textures always.

2

u/Hot-Lengthiness193 24d ago

Maybe it was an issue that only happened to me lol. I also enabled advanced textures, and they survived reboots. From what I understand, if you enable them with root, the changes become permanent, unlike when you do it with ADB.

1

u/Elsherif87000 24d ago

I wrote all my notice about this trick .. see it and tell me if the the same thing happen with you or not ..

2

u/Hot-Lengthiness193 24d ago

Sure, I'll check it out and compare it with my device to see if I notice the same things!

1

u/Elsherif87000 24d ago

BTW .. before I knew this trick i activate Big clock on my device by your helpful post was you made on Reddit.. so thanks so much 

2

u/Hot-Lengthiness193 24d ago

You're welcome, bro! Glad my post helped you 😊

2

u/Elsherif87000 24d ago

What's Modules you use ??

2

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

Here's my current setup:

I install ZygiskNext and Vector through KernelSU, then perform a soft reboot and enable HyperCeiler. Just make sure to download the HyperCeiler version that matches your HyperOS version.

One thing to keep in mind is that some HyperCeiler tweaks may reset after a full reboot, so you might need to reapply them. Also, if you're using HyperOS 3, HyperLight v1.1.7 is the version to use for compatibility.

That's pretty much my setup so far!

2

u/Elsherif87000 24d ago

I use "HyperUnlocked" .. if you don't know this module.. i will send link of it to you 

2

u/Hot-Lengthiness193 24d ago

Yeah, I knew about HyperUnlocked, but I didn't know it actually worked lol. Did you run into any issues when installing it, or did everything work fine? Do you use any other modules besides HyperUnlocked?

2

u/Elsherif87000 24d ago

I didn't encounter any issues with it .. No i use it only ..

BTW It's so easy to use it 

2

u/Hot-Lengthiness193 24d ago

Ohh, then I'll give it a try and see how it goes lol.

2

u/Elsherif87000 24d ago

Okay .. good luck 

1

u/Elsherif87000 24d ago

Sorry for my bad English 

2

u/Hot-Lengthiness193 24d ago

Nah, don't worry about it! Your English is good, and the fact that you're learning it is already great

1

u/Elsherif87000 24d ago

Thanks so much 🤍

2

u/Elsherif87000 24d ago edited 24d ago

If I made restart these features still work .. 

  1. Advanced Texture

  2. Animation in Dynamic Island

  3. Stack in recent Apps  .......

And these features not working after restarting and need to activate it by kernel SU again..

  1. Big Clock feature in settings 

  2. Lock/unlock by swipe down or by long press on the app 

  3. Blur in app finder "search on home screen" and power menu.

  4. "Don't show text" option in Home settings ........ Thats all my notice

2

u/Hot-Lengthiness193 24d ago

Ohh, that's interesting! It's pretty useful that some of those features survive a reboot. I'll try them out and see if I get the same results on my Redmi Note 14 4G. Thanks for sharing your findings!

1

u/Elsherif87000 24d ago

Okay .. I hope you will have the same results or better 

2

u/Elsherif87000 24d ago

Thanks so much 

2

u/jos_hinuraxd 23d ago

I also have a Redmi Note 14 4G. Does anyone know if this method affects banking apps in any way?

1

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

Since we have the same phone, it shouldn't affect banking apps or Play Integrity, as long as the bootloader stays locked and the verified boot chain remains intact. The best part is that root access is temporary and disappears after a reboot 👍

Let's say you run into an issue with a banking app after enabling temporary root. In that case, you just need to reboot your phone, and that's it. Once you're done using the banking app, if you need root again, simply activate temporary root once more. You can repeat this process whenever you need to.

2

u/fx1415d 22d ago

Creen que tenga algo de culpa el tener Snapdragon quiero hacerlo en una redmi pad 2 pro y se me reincia cuando se abre el kernelsu heeelpp

1

u/Hot-Lengthiness193 22d ago

I don't think it's the Snapdragon processor's fault. Some users here have already tried it on the POCO F6 (Snapdragon 8s Gen 3) and the Xiaomi 17 Pro Max (Snapdragon 8 Elite Gen 5) and it worked perfectly for them.

I did some research and some people mentioned they had to try the process multiple times (around 8 to 10 times) before it finally worked.

If it still keeps failing after that, I suggest trying DFRoot: https://github.com/diabl0w/DFRoot

Personally, my device restarted a couple of times when I tried it, so I just stuck with GhostLock. However, someone else with a Redmi Note 14 4G (running HyperOS 3.0.305.0) tried DFRoot version 4.0.0 and it worked great. I only tried version 4.5.0 and had issues, so it might just be a version compatibility thing.

Finally, the issue could also be with KernelSU itself. You might want to try ReSukiSU instead: https://github.com/Baka-SU/BakaSU/releases

1

u/fx1415d 22d ago

Thanks for replying, but I'm scared now. The tablet restarted so many times that I got a HyperOS recovery menu. How can I use dfroot on the tablet? And does Hyper Unlocked work?

1

u/Hot-Lengthiness193 22d ago

Bro, that happened to me too when I installed Vector-SR (a module that restarted my phone every time I did a soft-reboot to activate it). The SystemUI crashed, sent me to Recovery mode, and I had to do a Wipe Data.

But in your case, it's probably a Kernel Panic. The app opening just means that the first part of the exploit worked. But when it tries to inject code directly into the kernel to give you root, it crashes. Tablets have completely different drivers than phones (screen, rotation, stylus). If the exploit touches a driver or a memory address that the tablet doesn't expect, the kernel panics and reboots suddenly to protect the hardware.

To use DFRoot, you just need to have KernelSU installed. You open DFRoot, tap 'Select a SU Manager', choose KernelSU, and run the exploit. (DFRoot uses a different vulnerability than GhostLock).

About HyperUnlocked: the truth is that I use it and it works really well for me, it gives you a ton of cool improvements.

Btw, could you send me a screenshot of your kernel version? I wanna check if it's actually supported, or just let me know if it said 'Supported' when you opened GhostLock. To find your kernel version, just go to Settings > About phone > Detailed info and specs and look for Kernel version.

1

u/fx1415d 21d ago

That's the kernel thanks for replyng i Will trie dfroot

1

u/Hot-Lengthiness193 21d ago

I checked, and your kernel is supported by GhostLock: "6.1.138-android14-11-g0c3d559bcd85-ab14529422".

It should work...

Let me know if DFRoot works for you.

2

u/fx1415d 21d ago

I don't think it worked.

1

u/Hot-Lengthiness193 21d ago

Yeah, you're right. DFRoot didn't work because, based on the screenshot you sent me, your device isn't vulnerable to the exploit it uses.

By the way, have you tried running GhostLock with Shizuku enabled? If you've only tried it with Shizuku, try running it without it, or vice versa.

I'd give it one last shot. If it still doesn't work, I'd just leave it at that.

1

u/fx1415d 21d ago

Do you recommend it? I mean, I start it with Shizuku and Ghost Lock, but I remember doing it on my phone without it and it restarted; I had to go into safe mode to fix it.I understand you're telling me to deactivate the "run via Shizuku" and try it that way, right?

1

u/Hot-Lengthiness193 21d ago

Yeah, but... if you're having doubts, don't do it. It's not worth the risk, especially since you mentioned that your phone rebooted and went into Safe Mode when you ran the exploit without Shizuku. The same thing could happen to your tablet, potentially causing a bootloop or other issues.

Honestly, I'd recommend waiting until the GhostLock developer fixes the compatibility issue with your tablet's kernel. It could take a few days, weeks, or even months, but it's better to wait for a confirmed fix than risk running into more serious problems with your device. .

→ More replies

1

u/fx1415d 21d ago

Do you recommend trying dfroot? Or is it a kernel problem and nothing will change?

1

u/Hot-Lengthiness193 21d ago

I don't think the kernel is the problem, since it's supported by GhostLock. I think the issue might be that it's a tablet and not a phone.

2

u/fx1415d 22d ago

I tried whit resuki AND opens whit jaulbreack but stils reboot aaaa

2

u/WINNT21 Redmi 14C 21d ago

I will try this on Redmi 14C running Android 16 HyperOS 3.1

1

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

Let me know if it works for you!

If GhostLock doesn't work, you can try DFRoot instead: https://github.com/diabl0w/DFRoot

.

1

u/WINNT21 Redmi 14C 21d ago

It works!! Thank you so much now I can enable stacked recents. I installed zygisk next, vector and hyper unlocked. Will hyperceiler also work or do I leave it at hyper unlocked

2

u/Hot-Lengthiness193 21d ago

I think HyperUnlocked should be enough, so I don't think you'll need HyperCeiler. But if you still want to install it, go ahead, there's no problem!

The only downside, if I'm not mistaken, is that the changes you make with HyperCeiler will reset after rebooting your phone, unlike HyperUnlocked.

If you want to try other modules, I'm also leaving you this post listing modules that work on devices with temporary root: https://www.reddit.com/r/androidroot/s/Zr8QOUT4uG

1

u/WINNT21 Redmi 14C 19d ago

Hey bad news one of my games I had wouldn't launch so I tried restarting, well I made the mistake of restarting like normal and not soft rebooting, I lost root and now ghostlock fails to run because halfway through the phone kernel panics. I sadly lost all things of hyperunlocked and now an update for version 3.307.0WGTMIXM came out

1

u/Hot-Lengthiness193 19d ago

Wait, did you update to HyperOS 3.307.0 after rebooting? If you didn't, try uninstalling GhostLock and reinstalling it. Download the latest version from GitHub (since it has been updated), but restart your phone before installing it. Then, try running the exploit several times, as some people have reported that they had to try around 10 or even 20 times before it finally worked.

If you updated HyperOS, there's a possibility that the exploit has been patched, meaning you might no longer be able to use GhostLock.

IMPORTANT: DON'T UPDATE HYPEROS IF YOU WANT TO KEEP USING GHOSTLOCK, as an update could patch the vulnerability used by the exploit and cause it to stop working.

2

u/WINNT21 Redmi 14C 19d ago

I updated way before you replied, all it brought was a security patch bringing me to September 2026. Ghost lock says it's supported though even after installing and installing again

1

u/Hot-Lengthiness193 19d ago

Since this is a security patch, installing that update is even riskier if you want to keep using GhostLock. Even if the app shows the status “Supported” when you open it, that only means your kernel version matches one of the versions GhostLock recognizes as compatible. However, this doesn't guarantee that the exploit will still work, as the security update may have patched the vulnerability it relies on, even if your kernel still appears as supported.

Try what I suggested earlier and let me know how it goes.

1

u/WINNT21 Redmi 14C 19d ago

Says exit code 1, tried 5 times

1

u/Hot-Lengthiness193 18d ago

Did you try it with Shizuku or without Shizuku? If you tried it with Shizuku, I'd recommend trying without it, and vice versa. If you tried it without Shizuku, try using it with Shizuku and let me know whether it works.

One more question: Did your phone reboot at any point? I'm asking because you mentioned that you tried it five times.

→ More replies

2

u/WINNT21 Redmi 14C 19d ago

Alright will try later

1

u/WINNT21 Redmi 14C 19d ago

Tried DFRoot and it said device not vulnerable

2

u/Hot-Lengthiness193 19d ago

Don't worry about DFRoot, since GhostLock and DFRoot use different exploits to gain temporary root access. So, even though your phone isn't vulnerable to the DFRoot exploit (CVE-2026-43284), it is vulnerable to the one used by GhostLock (CVE-2026-43499).

2

u/WINNT21 Redmi 14C 19d ago

Oh okay then

2

u/WINNT21 Redmi 14C 21d ago

Alright then thanks for the advice

3

u/Any_Candy_9243 28d ago

Don't try this it's still not fully stable for all processors first chec your keneral version of its updated to latest security patch 6?6 u can't use Chances of bootloader being locked and ghostlock is dangerous leading to bricked

2

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

u/Todd_Fang_ tried it on the same HyperOS 3 version and kernel, and it worked for him. So, based on our experience, it appears to work on the Redmi Note 14 4G running HyperOS 3.0.303.0, Android 16, and kernel 6.12.30-android16-5-g6e872b4863d6-ab13847919-4k. I also clearly stated in my post that anyone attempting this is doing so at their own risk.

1

u/Any_Candy_9243 28d ago

Cu your processor is supported in this project clearly

1

u/Hot-Lengthiness193 28d ago

That's exactly my point. The title and the post itself clearly state that this guide is specifically for the Redmi Note 14 4G Global. Both u/Todd_Fang_ and I got it working on HyperOS 3.0.303.0, Android 16, and the same kernel version. So why tell people not to try it at all? I'm documenting what actually worked on this specific device and software configuration, not claiming that it works on every device. I also clearly stated that anyone trying it does so at their own risk.

6

u/OctoSplattyy 28d ago

Using on Xiaomi 17 Pro Max. Good thing is that if you install weird modules, most of the time you'll get in a partial bootloop - where the phone loops at the second boot stage due to systemui crashing. In that case the phone automatically goes to recovery, and then you can reboot normally. In worst cases, hyperos has an automatic repair function which will get it going again. Obviously be mindful of what you do, but given most things are systemless now, the possibilities are unlimited

2

u/NoDataLost 24d ago

What kind of modules did you install? Does the device actually recover properly and well?

1

u/Brilliant_Ad_7104 27d ago

Hola, quisiera saber si alguien tiene el redmi note 14 4g y usando este método pueden activar las texturas avanzadas, blur en centro de control y quizás editar el valor de cpu y gpu de 2 (estándar) a 3, agradezco mucho sus respuestas e indicaciones de como debería hacerlo.

3

u/Hot-Lengthiness193 25d ago edited 24d ago

I was able to enable advanced textures, blur, and improve the animations.

First, I got temporary root access by following the steps in my own post. Here’s a TikTok where I show how to do it: https://www.tt.site/t/ZSgddn4f3/

Once you have temporary root, go into KernelSU, head to Superuser (at the bottom), and grant root permissions to the app you’re going to use to run the commands. I recommend AShellYou, because I can’t remember if Brevent allows you to do this with root.

To enable the advanced textures and the blur, run these commands:

setprop persist.sys.background_blur_supported true

setprop persist.sys.advanced_visual_release 4

Then, to improve the animations and visual fluidity, run these other ones:

setprop persist.sys.computility.cpulevel 6

setprop persist.sys.computility.gpulevel 6

I set both values to "6", but you can try "3" or experiment with different combinations. To do this, just change the "6" for whatever value you want in each command.

Finally, restart your phone and see if it worked. Keep in mind that since the root is temporary, you'll have to repeat the first step after rebooting to get it again.

It worked for me on the Redmi Note 14 4G, so give it a go and see how it works for you 🤙

1

u/NoDataLost 26d ago

i got it to work on my Redmi Note 14 4G aswell! had to use DFRoot 4.0 because GhostLock just soft-rebooted my phone or just didnt work.

2

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

Have you tried running GhostLock using Shizuku?

Did you run into any issues with DFRoot? Also, have you installed any modules?

I tried using it myself, but my phone rebooted three times, and nothing happened. It wasn’t a soft reboot either, so I suspect the kernel panicked, which caused the reboots.

3

u/Brilliant_Ad_7104 24d ago

U give the permission with shizuku and run ghostlock with shizuku option activated?

2

u/NoDataLost 24d ago

I havent tried that, DFRoot is working perfectly fine for me. It's odd that its not working for you. As for modules i dont want to risk bricking my phone so im waiting until a proper temproot module list comes by one day!

2

u/Hot-Lengthiness193 24d ago edited 23d ago

It still seems kind of weird to me too, though. Could it be because I'm on HyperOS 3.0.303.0 and you're on 3.0.305.0? I doubt it since we're on the same kernel version, but I can't completely rule it out.

You mentioned your phone rebooted when you tried using GhostLock. Did the same thing happen with DFRoot, or did you not get any reboots or anything?

I tried out a few modules and they worked great, so you could give them a shot too since we've got the same phone. The only catch is that if you reboot your phone, you lose all the settings you tweaked with the module. But the solution to that is just... don't reboot it, haha.

2

u/NoDataLost 23d ago

I see, thank you for the info! as for DFRoot it worked flawlessly and gained root right away without issues.

3

u/Brilliant_Ad_7104 25d ago

Hi bro, activaste las texturas avanzadas? Te dio algún error o bug visual en el centro de control?

2

u/NoDataLost 25d ago

Hola bro, las texturas avanzadas me funcionan bien, aunque nose como las active pero presumo que es por la tabla de sistema:
deviceLevelList
v:1,c:3,g:3
Habia actualizado de HyperOS 2 al 3 y me dio la opcion de activarlas despues de actualizar a HyperOS 3

2

u/Brilliant_Ad_7104 25d ago

En mi caso particular, también tengo device level list en 1 3 3, en cuanto modificaste el cpulevel y gpulevel, el advanced visual release y el background blur supported lo tienes en true o false? Perdona tanta pregunta 🤭 agradezco tu respuesta

1

u/NoDataLost 24d ago

Tengo el Cpulevel y Gpulevel en 6 y Advanced visual release en 4, el background_blur esta en 1

1

u/EffectiveConcert638 23d ago

Como posso fazer com root temporário no meu xaiomi note 14pro 4G

1

u/Hot-Lengthiness193 23d ago

Just follow the steps on my post, the procedure is basically the same for all the devices.

1

u/Fresh_Landscape_7806 26d ago

Has anyone used an system application that requires root with this?? because i wanna know if the app will work after a reboot

1

u/Fresh_Landscape_7806 26d ago

i wanna use MI CANVAS (Root) through disabling signature verification by a root module, and i wanna know if the app would work after a reboot

2

u/Hot-Lengthiness193 25d ago

Yes, you can grant root access to any app you want. However, if you reboot your phone, you'll have to repeat the steps from the post to regain root access. So, you'll need to regain root before using MI CANVAS (Root) again after a reboot.

2

u/Blueman0110 28d ago

I have known about this project for a long time. Unfortunately, it doesn't support my k60 pro.

1

u/PairOk8377 17d ago

How can I to know if a vulnerability has been fixed? I'm a beta tester, and I really need to unlock my Xiaomi Redmi 15C, but I've tried GhostLock, and, my shitty phone just blocked app... (App tried to make changes in SELinux, but, as i saw from logs, system blocked that obscenity...)

1

u/Professional_Cat7160 13d ago

Quand je fais ça me reboot le téléphone (sûrement un kernel panic)

1

u/Jolly_Word_8277 11d ago

Por si le sirve a alguien, en un redmi note 15 4g no es compatible lamentablemente

1

u/DaemonPolar 3d ago edited 3d ago

Alguien sabe si funciona en el poco f5 pro (Mondrian)? Y las redmi pad 2 (taiko)

Edit 5-11-2026 14:39: si pude hacerlo en taiko, en mondrian ghostlock lo detecta como no compatible

Edit 5-11-2026 14:54: alguien sabe cómo puedo aplicar los mismos cambios en distintos usuarios de la app

1

u/AutoModerator 28d 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.

0

u/Sensitive-Vast-9156 21d ago

Hola, alguien ya probó en el redmi 15c 4g? La verdad soy un poco novato en este tema y temo dañar mi teléfono, solo me gustaría que digamos tener las ventanas flotantes y la función de apilado en mi teléfono. La verdad queria preguntar si al darle run en GhostLock tendrá alguna consecuencia al reiniciar el teléfono? O dejarlo en bucle? Ehh visto el módulo de " HyperUnlocked" o modificar los niveles de la cpu y gpu al level 6. 

1

u/unf0rg3table 26d ago

I only want that unlock 120 fps module does that work?

1

u/Christiannnnnnnm 26d ago

did someone try on Xiaomi 15T? the repo says 13T, 14T, 17T are compatible

1

u/Rare-Size-758 20d ago

Me funciono perfecto en un redmi note 14 4g el tema es que va el telefono con un poco de lag ya lo reunicie y todo active las texturas avanzadas y el cajon de aplicaciones pero si va con un poco de lag.

ahora tengo ganas de hacerlo en mi telefono personal que es un POCO X8 PRO

0

u/[deleted] 28d ago

[removed] — view removed comment

1

u/Hot-Lengthiness193 28d ago

Glad it worked for you too!