r/androidroot

Hi all,

I've been trying for months to bypass the xiaomi community permission things and finally I have reached a milestone. Read most of the discussions from r/androidroot and r/hyperos. Now I only have to wait 360 hours(sadly) to win freedom over my phone 😭.

My plan is to flash orangefox and Evolution X(Android 16).

Guys let me know if there are any suggestions you could give to me

Thank you for all your support 💖

https://github.com/inforcqb/susfs4ksu-lkm

https://github.com/matsuzaka-yuki/susfs-lkm-module

For some time now, the wallet has been failing verification; it always tells me that the device does not meet the security requirements. I have Strong certification; here are screenshots of my configuration:

I'm using KernelSU with temporary root on my Redmi Note 14 4G (HyperOS 3 / Android 16), and my bootloader is locked. I want to know which modules are safe to use in this setup.

• Which modules actually work with temporary root access?

• Which modules should I avoid because they could cause bootloops or brick my device?

• Are there any anti-bootloop or anti-brick modules that can help recover from a bad module?

• Are there any Xiaomi-specific modules that work well with HyperOS?

I'd especially like to hear from people who have used temporary root access with KernelSU on Xiaomi devices. Which modules worked for you, and which ones caused problems or aren't worth installing?

Thanks!

For people that want to know what i used to root it, i used the dirty frag exploit on it.

Im using the RMX3834export_15_H.07 rom on my realme note 50 (the most recent stock rom for it)

Lenovo only released the old 4.9 kernel source for the TB-X606F from its Android 9 days, which meant their Android 10 release was basically stuck with unusable/unbootable source. So I grabbed the 4.19 Android 11 kernel from the TB-X306F and ported that over to the TB-X606F running Android 10, with a lot of help from Claude and ChatGPT lol. that whole Android 9 to Android 11 kernel then back onto Android 10 explanation sounds confusing, but both tablets use the same SoC, which made the port pretty realistic. It’s a pretty big jump from 4.9 to 4.19 and most things are working fine so far. Still fixing/testing a few remaining bits, but Android 10 boots and is usable on 4.19 the majority of it, it only took a few hours too lmfao

• APatch -- The most unstable. While stealthy, it carries a risk of patch failure and it has less ecosystem. It's new and currently immature.
• ReSukiSU -- A fork of KernelSU. The most supported by the ecosystem. It improves upon KernelSU by adding redundancy, such as falling back to LKM mode or a different hooking method. For some kernels and ramdisks, it can still fail even with fallbacks, as it operates in kernelspace for stealth.
• Magisk -- The most stable. It operates in userspace, including POSIX and init, which is intended to be never changing. Because of this, it can run on many Android versions including those without GKI kernels. But it comes with a cost of rigidity, it doesn't support SuSFS or metamodules like KernelSU and APatch.

I want to build a a mobile phone a secret one with a wifi , mid camera, bluetooth , a good OS ,a bluetooth and a screen obv and can do bank payments (becuz whenever I try to use my phone my parents scolds me )so I am thinking of making one what components to use and can I use this pi zero ?

AlwaysStrong KeyBox has been updated

Integrity is now Strong again.

Note:

Don't be an idiot Like me

And check Integrity every chance you get

I apologize for my stupidity

I was one of these idiots

ALWAYS RELY ON THE KEYBOX STATUS WITHIN THE MODULE, NO NEED TO PING GOOGLE ABOUT YOUR STRONG INTEGRITY. THE WONT LIKE IT (Integrity checker apps are the worst. Use g play dev options to check Integrity when absolutely necessary.)

CHEERS.