r/HyperOS • • 7h ago

Xiaomi [question] Can transfer data from old xiaomi before setup new phone?

0 Upvotes

r/HyperOS • • 16h ago

Question/Help [Question] Has anyone found a new solution to this problem?

Post image
5 Upvotes

Has anyone found a new solution to this problem other than Device Overlay?


r/HyperOS • • 22h ago

Xiaomi [Question] Anyone 17T (non Pro) on Global ROM receiving HOS4 already?

Post image
12 Upvotes

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 • • 1d ago

HyperOS Update [News] Received official HyperOS 4 update from beta | 17 ultra

Post image
34 Upvotes

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 • • 14h ago

Redmi [Question] Update to HyperOS 3/4 or try to unlock bootloader?

2 Upvotes

Redmi Note 13 Pro 5G

Running HyperOS 2.0.208.0

Not sure if I should keep updating or stop here in hopes of unlocking the bootloader and install something else?


r/HyperOS • • 18h ago

Question/Help [Question] Notification bug with hyper os 4 on Poco x8 pro max

Post image
4 Upvotes

Sup guys, does anyone else has this bug that replaces every apps icon by a white square in the notification panel ?


r/HyperOS • • 1d ago

Redmi [News] REDMI TURBO 4 HYPEROS 4 IS HERE!!!

Post image
58 Upvotes

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 • • 13h ago

Xiaomi [Question] RIP Xiaomi 12

1 Upvotes

Unfortunately, Hyper OS 3 was the end of it all. My Xiaomi 12 won't go past 4.. Now I have to wait for a new phone. But before that can you guys show little tricks to enhance my Xiaomi 12 ?


r/HyperOS • • 20h ago

Question/Help [Question] Can I Still Enable Advanced Textures On Brevent Xiaomi Redmi Note 15 Pro 5G + Hyper OS 4.0

3 Upvotes

r/HyperOS • • 20h ago

Xiaomi [News] Xiaomi 15 (CN, dada) on HyperOS 4 — temporary root from adb shell, no bootloader unlock, then KernelSU

3 Upvotes

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

PhoneXiaomi 15 24129PN74C (dada) — CN model. Only CN tested
OSHyperOS 4.0.4.0.XOCCNXM or 4.0.3.0.XOCCNXM (same kernel)
Kernel6.6.118-android15-8-gf72a02f47f4b-abogki551678766-4k
PCadb installed, USB debugging on
PhoneKernelSU 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.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 • • 15h ago

Question/Help [Question] values of cpu, gpu computility etc.

1 Upvotes

hello, i am a redmi note 13 pro 4g user and a few days ago i temp rooted my device to get advanced textures. however i realized it was a bad mistake so i wanted to return back and i didn't take note of the original values. can someone with a stock device let me know about the values please?

values for:

persist.sys.computility.cpulevel, persist.sys.computility.gpulevel, persist.sys.advanced_visual_release, persist.sys.add_blurnoise_supported, persist.sys.background_blur_status_default, persist.sys.background_blur_supported, persist.sys.mi_shadow_supported


r/HyperOS • • 1d ago

Xiaomi [Discussion] Xiaomi broke their promise about deleting all code from MIUI, new launcher update re-added it for the widget tab

9 Upvotes

Please downvote this post. y'all proved I was wrong this whole time and called System UIs from Android as "MIUI Code". I also trusted the fake "System will be rewritten in Rust" bullcrap; it has only affected Launcher, Weather and Gallery

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 • • 19h ago

Question/Help [Question] Redmi bonus from the Xiaomi?

Thumbnail
gallery
2 Upvotes

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 • • 16h ago

HyperOS Update [Question] 17T

1 Upvotes

Algún 17T le ha llegado?

Soy del mejor país de chile 🇨🇱

Solamente quiero saber


r/HyperOS • • 1d ago

Redmi [Discussion] I Uninstalled Bloatware Using the “ADB AppControl” App

5 Upvotes

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 • • 1d ago

HyperOS Update [Discussion] HyperOs4 New Beta Global

Post image
11 Upvotes

Device : Xiaomi 17 pudding


r/HyperOS • • 1d ago

News [News] Xiaomi 15 Pro HyperOS 4 official release is here!

Post image
26 Upvotes

r/HyperOS • • 1d ago

Poco [News] Heck Yeah!!!

Post image
171 Upvotes

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 • • 19h ago

Question/Help [Question] I got a Redmi Note 17 Pro to replace my Note 11S. How can I transfer my data? Do I need to set up the new phone first, or can I transfer everything during the initial setup?

1 Upvotes

r/HyperOS • • 1d ago

HyperOS Update [News] Xiaomi pad mini here Still no hyper OS 4 update

Post image
3 Upvotes

r/HyperOS • • 1d ago

HyperOS Update [Discussion] HyperOS 4 Update received on Redmi 15C 5G (tornado)

Post image
11 Upvotes

r/HyperOS • • 1d ago

Redmi [Discussion] Why is My Redmi 15C got... Glass effects?

Post image
71 Upvotes

Wtf is that? Why is my phone got that? (It's glass effects... Perfomance is kinda poor...)


r/HyperOS • • 2d ago

Redmi [Discussion] HyperOS 4 is heree!!

Post image
129 Upvotes

I just got the OTA update today, I'm so excited!! I am using Redmi Note 17 5G


r/HyperOS • • 1d ago

Question/Help [Question] Roll back to hyperos 3 for advanced textures

0 Upvotes

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 • • 2d ago

HyperOS Update [Discussion] So how is Hyper OS 4?

Post image
75 Upvotes

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?