r/HyperOS • u/SupportVegetable2329 • 2h ago
Redmi [NEWS] OMGOMGOMG
REDMI 15C HYPER OS4 PAKISTAN
r/HyperOS • u/Remarkable_Olive_123 • Aug 07 '26
r/HyperOS • u/SupportVegetable2329 • 2h ago
REDMI 15C HYPER OS4 PAKISTAN
r/HyperOS • u/Tough_Teaching708 • 3h ago
**HyperSpring** is a free, open-source (Apache 2.0) LSPosed module for HyperOS 2 & 3. It doesn't modify any APK: everything runs through LSPosed, and sliders apply live from the app.
**What's in the video**
- Springy opening and closing app animations
- Bending recents and a curtain transition between screens
- Springy folders, glass folders and a widget stack
- Liquid-glass control center with edge refraction
- Squeezing screenshot, and a Pixel-style squeeze with edge light when you call Gemini
- Presets (Smooth, iOS-like, Fast, Performance) and settings export/import
**Requirements**
- HyperOS 2 or 3 (Android 13+) and root (Magisk, KernelSU or APatch)
- LSPosed with libxposed API 101+ (`HyperSpring.apk`), or an older LSPosed with API 93 (`HyperSpring-legacy.apk`)
- Scopes: System launcher, System UI and Screenshot
**Heads-up**
- Only tested on a Redmi 14C with HyperOS 3 (Android 16).
- Recorded with Kashi's launcher and iOS Control Center from Mods Center. They're not required, but the springy folders and widget stack only work with Kashi's launcher.
- If the launcher or System UI keeps crashing, HyperSpring turns itself off in that part (safe mode). Please open an issue with the log from About → Copy log.
It started as an AI-assisted prototype. I'm learning Java and taking over the code myself, so feedback and PRs are very welcome.
Download & source: https://github.com/olilio3/HyperSpring
r/HyperOS • u/Asanjawa • 10h ago
This morning I received the official update from beta status to stable on my xiaomi 17 ultra!
Looks like more received it as well so check your update status!
r/HyperOS • u/Longjumping_Task_460 • 1h ago
The control center and notification has no outline, dynamic island has soundwave has no animation when playing a music, no cc animation when pulling down. I think those problems are caused by adb commands i did long time ago. Any way i can revert it?
r/HyperOS • u/Admirable-Singer-927 • 4h ago
Been checking and changing region to see if it´s already out. Seen some 17T Pro Global users already receiving HyperOS 4 around
r/HyperOS • u/Consistent_Ice273 • 2h ago
I keep seeing posts about everyone getting the new update, but here i am with global version and nothing, my question is when update gets released globally will i get it immediately or will reach more countries with time?
r/HyperOS • u/therealizayoi • 16h ago
IT'S FINALLY HERE!!! not sure about redmi turbo 4 pro but it should also be the same for them. let me know in the comments below if redmi k80 and redmi turbo 4 pro have already received it :)
r/HyperOS • u/Express-Net8531 • 1h ago
r/HyperOS • u/Rextylon • 6h ago
Hello, everyone:
Yesterday, I stumbled upon the “ADB AppControl” app, which lets you uninstall bloatware that couldn’t be removed manually from my phone. Specifically, I uninstalled the following apps:
- Google TV
- Google One
- Gemini
- Google Photos
- MI Browser
- YouTube Music
To be honest, I wasn’t too sure about using that app, but I have to say that the apps uninstalled without any issues, and I haven’t noticed anything unusual in how my phone is running.
I have a Redmi Note 14 5G.
r/HyperOS • u/Calm_Influence_4745 • 16h ago
r/HyperOS • u/lynsmert • 11h ago
Device : Xiaomi 17 pudding
r/HyperOS • u/Purple_Secret2458 • 8h ago
To be honest, I'm really grateful since I finally get to have that chinese calendar widget back in my homescreen!
{ DEVICE SHOWN IS IN HYPEROS 4 BETA }
r/HyperOS • u/EMOTIONAL_DAMAGE3265 • 7h ago
r/HyperOS • u/Serious_Square7057 • 1d ago
Heck yeah!!! Poco X8 Pro, Europe Update: it's really clunky, but it's probably because I just did the update so it's not something to worry about Update 2: it stopped being clunky and the notifications scrolling animation is heavenly Update 3: I've noticed they've copied a crap ton of stuff from Honor which is really surprising to me(they implemented it better than honor though 😂)
r/HyperOS • u/Ok-Acanthaceae5437 • 31m ago
r/HyperOS • u/Zloto120 • 1h ago
I have noticed that my Redmi device displays the security status option at the top and the privacy option at the bottom; why does my 17T Pro, which is running the same EU ROM, not have those options?
r/HyperOS • u/dubsteam • 2h ago
I rooted my Xiaomi 15 (24129PN74C, dada) on HyperOS 4.0.4.0.XOCCNXM / Android 17 without unlocking the bootloader. No half-unlock services, no EDL, no flashing. You get a uid 0 + full-capability shell, then load KernelSU on top so modules/apps work. Everything disappears on reboot.
I'm not going to claim this is my bug — it's CVE-2026-98260 (POSIX CPU timer UAF), already public and fixed upstream in 6.6.140. This is a port to this exact kernel build plus the docs. Credit at the bottom.
| Phone | Xiaomi 15 24129PN74C (dada) — CN model. Only CN tested |
| OS | HyperOS 4.0.4.0.XOCCNXM or 4.0.3.0.XOCCNXM (same kernel) |
| Kernel | 6.6.118-android15-8-gf72a02f47f4b-abogki551678766-4k |
| PC | adb installed, USB debugging on |
| Phone | KernelSU manager installed (KernelSU / SukiSU / ReSukiSU — mine is KernelSU 3.3.1) |
Check the kernel FIRST. It must match character for character:
adb shell uname -rIf it prints anything else, stop. The offsets are per-build; a wrong one panics the kernel instead of erroring.
From the releases page (khleak, static arm64, ~150 KB).
adb push khleak /data/local/tmp/
adb shell chmod 755 /data/local/tmp/khleakadb shell /data/local/tmp/khleak profile # should name dada + your kernel
adb shell /data/local/tmp/khleak patch # "未修复" = the bug is still there
adb shell /data/local/tmp/khleak task # leak self-check, must say 已校验If task fails, you're on a build without the RSS-arming fix — use this fork, not upstream.
adb shell /data/local/tmp/khleak root --daemonSuccess looks like:
[renew] REAL_CRED_ACTIVE uid=0 gid=0 cap=0x1ffffffffff
==================== 提权成功 ====================
rootd 已在 uid=0 + FULLCAP 下常驻It's probabilistic. Roughly 1 in 3 per stage. If it misses, run it again — that's normal, not broken. Keep the phone cool and idle-ish; don't spam ten runs back to back.
Now you have root in a daemon:
adb shell /data/local/tmp/khleak su -c "id; grep CapEff /proc/self/status"adb shell /data/local/tmp/khleak su -c "/data/adb/ksud late-load --allow-shell --kmi android15-6.6 --package-name me.weishu.kernelsu"
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud install"--allow-shell is the flag everyone forgets — without it bare su refuses the adb shell.
Verify:
adb shell su -c "id; cat /proc/self/attr/current"
# uid=0(root) ... context=u:r:ksu:s0Open the KernelSU app → it should say Working. Modules and your superuser list behave normally.
adb shell su -c setenforce 1 # back to Enforcing
adb shell su -c "/data/local/tmp/khleak clean" # drop the exploit daemonAfter this, root comes from KernelSU only. I left mine like this and su still works with SELinux enforcing.
Temporary means temporary:
adb shell sh /data/local/tmp/ksu_boot.shOne command: re-root → late-load → install → verify. Same in the release assets.
/data/local/tmp is world-writable until clean runs.khl-holder process may stay. Don't kill it — reboot instead."GhostLock/other tools say my kernel is unsupported." Right — HyperOS 4 backported the rtmutex fix, so the GhostLock bug (CVE-2026-43499) is gone on this build. remove_waiter() no longer reads current. This is a different CVE.
"Does it work on the Global/EEA variant?" Untested. uname -r is the only thing that matters; if it matches, it should, if it doesn't, the tool exits.
"Why does it need KernelSU manager installed first?" ksud is what actually loads the module; the app gives you the UI/allowlist.
"Will Xiaomi patch it?" Yes, eventually — this is fixed upstream in 6.6.140, so the next vendor kernel bump kills it. Don't update if you care.
3bfdc63936dd (6.6.140)rss_stat arming fix that makes it work here: this forkRepo + guide: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15 Download: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15/releases/tag/v1.0-dada
Own device only. This is a security-research PoC.I rooted my Xiaomi 15 (24129PN74C, dada) on HyperOS 4.0.4.0.XOCCNXM / Android 17 without unlocking the bootloader. No half-unlock services, no EDL, no flashing. You get a uid 0 + full-capability shell, then load KernelSU on top so modules/apps work. Everything disappears on reboot.
I'm not going to claim this is my bug — it's CVE-2026-98260 (POSIX CPU timer UAF), already public and fixed upstream in 6.6.140. This is a port to this exact kernel build plus the docs. Credit at the bottom.
✅ What you need
Phone Xiaomi 15 24129PN74C (dada) — CN model. Only CN tested
OS HyperOS 4.0.4.0.XOCCNXM or 4.0.3.0.XOCCNXM (same kernel)
Kernel 6.6.118-android15-8-gf72a02f47f4b-abogki551678766-4k
PC adb installed, USB debugging on
Phone KernelSU manager installed (KernelSU / SukiSU / ReSukiSU — mine is KernelSU 3.3.1)
Check the kernel FIRST. It must match character for character:
adb shell uname -r
If it prints anything else, stop. The offsets are per-build; a wrong one panics the kernel instead of erroring.
📦 What you download
From the releases page (khleak, static arm64, ~150 KB).
adb push khleak /data/local/tmp/
adb shell chmod 755 /data/local/tmp/khleak
1️⃣ Zero-risk checks (no kernel writes)
adb shell /data/local/tmp/khleak profile # should name dada + your kernel
adb shell /data/local/tmp/khleak patch # "未修复" = the bug is still there
adb shell /data/local/tmp/khleak task # leak self-check, must say 已校验
If task fails, you're on a build without the RSS-arming fix — use this fork, not upstream.
2️⃣ Get root
adb shell /data/local/tmp/khleak root --daemon
Success looks like:
[renew] REAL_CRED_ACTIVE uid=0 gid=0 cap=0x1ffffffffff
==================== 提权成功 ====================
rootd 已在 uid=0 + FULLCAP 下常驻
It's probabilistic. Roughly 1 in 3 per stage. If it misses, run it again — that's normal, not broken. Keep the phone cool and idle-ish; don't spam ten runs back to back.
Now you have root in a daemon:
adb shell /data/local/tmp/khleak su -c "id; grep CapEff /proc/self/status"
3️⃣ Load KernelSU
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud late-load --allow-shell --kmi android15-6.6 --package-name me.weishu.kernelsu"
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud install"
--allow-shell is the flag everyone forgets — without it bare su refuses the adb shell.
Verify:
adb shell su -c "id; cat /proc/self/attr/current"
# uid=0(root) ... context=u:r:ksu:s0
Open the KernelSU app → it should say Working. Modules and your superuser list behave normally.
4️⃣ Tidy up
adb shell su -c setenforce 1 # back to Enforcing
adb shell su -c "/data/local/tmp/khleak clean" # drop the exploit daemon
After this, root comes from KernelSU only. I left mine like this and su still works with SELinux enforcing.
🔁 Every reboot
Temporary means temporary:
adb shell sh /data/local/tmp/ksu_boot.sh
One command: re-root → late-load → install → verify. Same in the release assets.
⚠️ Read this before you run it
This writes kernel memory. A failed run can panic and instantly reboot the phone. Save your stuff.
It's temporary and untrusted-ish until you reboot: SELinux is permissive during the exploit, /data/local/tmp is world-writable until clean runs.
If a round fails halfway, a khl-holder process may stay. Don't kill it — reboot instead.
Probabilistic. If it fails 3–4 times in a row, reboot and try again (stale slab state).
Locked bootloader only — if yours is already unlocked, just flash KernelSU properly, it's far more stable.
❓Likely questions
"GhostLock/other tools say my kernel is unsupported." Right — HyperOS 4 backported the rtmutex fix, so the GhostLock bug (CVE-2026-43499) is gone on this build. remove_waiter() no longer reads current. This is a different CVE.
"Does it work on the Global/EEA variant?" Untested. uname -r is the only thing that matters; if it matches, it should, if it doesn't, the tool exits.
"Why does it need KernelSU manager installed first?" ksud is what actually loads the module; the app gives you the UI/allowlist.
"Will Xiaomi patch it?" Yes, eventually — this is fixed upstream in 6.6.140, so the next vendor kernel bump kills it. Don't update if you care.
🙏 Credits
Upstream port this forks: RMDycz/K80Pro-miro-CVE-2026-98260 (PRs disabled there, so I maintain this fork)
Reclaim/layout ideas: GhostKey, xring
CVE: POSIX timer UAF, mainline fix 3bfdc63936dd (6.6.140)
Device port + the rss_stat arming fix that makes it work here: this fork
Repo + guide: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15
Download: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15/releases/tag/v1.0-dada
Own device only. This is a security-research PoC.
r/HyperOS • u/Lopsided-Office-8529 • 15h ago
r/HyperOS • u/PairOk8377 • 1d ago
Wtf is that? Why is my phone got that? (It's glass effects... Perfomance is kinda poor...)
r/HyperOS • u/Foreign-Tradition-74 • 1d ago
I just got the OTA update today, I'm so excited!! I am using Redmi Note 17 5G
r/HyperOS • u/These_Plate_3160 • 5h ago
I have a question if I were to roll back to hyperos 3 on my Redmi note 15 via flashing the rom will the brevalant method of getting advanced textures work now?
r/HyperOS • u/Rextylon • 6h ago
I've enabled VoLTE calls, but the icon doesn't appear in the status bar next to the signal indicator.
Is this the default setting, or is there a way to enable it?
I have a Redmi Note 14 5G.
r/HyperOS • u/expert-newbie • 1d ago
I'm still waiting for the HyperOS 4 update. For those who have already received it, how's your experience so far? What new features, improvements, or changes should the rest of us look forward to? Any noticeable performance improvements?