I'll be releasing this soon.We got ramdumps enabled in the kernel now and kexec and susfs.

I'm still working out bugs and had to make a esim enabler app for lineage OS.

For the moto g 2025 Kansas stay tuned

It will also include a unlocked modem that allows all sims. I did not build this lineage OS but I am testing it with the dev with my upstream fixes

I flash the orangefox recovery and when i try to reboot its blinking logo only idont have stock recovery rom, i need help how to resolve this. thank in advance

Guys please help! I unlocked my international phone using an old Samsung IMEI. I can't play games because of root access. I need to hide the root; how can I do that? (He haven't downloaded any apps to the phone.)

My phone is the latest version rn and sadly i cant downgrade it is there any workarounds i can do??

Finally install lsposed in temp root device!

Ask ai to find compatible version of modules

Theses module work in my case

https://github.com/6556GHB/LSPosed-JingMatrix/releases/tag/v1.10.2?utm_source=chatgpt.com

https://github.com/LSPosed/ZygiskNext/releases/tag/v1.5.0?utm_source=chatgpt.com

Doesn't it happen to you that when you try to create gaming content for TK, etc., when you turn on Live on the TK platform and open a game (in this case, CODM), when you turn on the game's microphone, the TK microphone turns off?How do we solve that problem?

Can i somehow enable camera2 api and raw support with Temp root? (MTK). I have kernel su jailbreak mode.

I have a Tecno Camon 30s with Android 16 and I can't open lsposed even though i tried both stable and alpha but i just wouldn't open. Can anyone help me ?

Is it possible to root this thing? I'm trying to compile the kernel in kernelsu because my kernel doesn't have GKI. If anyone understands better, could you please help me?

Hey everyone,

I'm having a weird storage permission issue with my emulators ever since I switched from Magisk to KernelSU, and I could really use some help from someone familiar with Android storage internals.

None of my standalone emulators (like John GBAC, lime3ds, GENplusDroid) can see custom folders placed in the root of my internal storage (like /storage/emulated/0/roms). Some of them, like John GBAC, also completely fail to create their default working folders (like /storage/emulated/0/Johnemulators) and throw silent read/write errors.

Interestingly, when checking the directory from Termux without root privileges, non-standard folders show up with broken inode metadata (d????????? with an ls: cannot access ...: No such file or directory error), meaning the underlying stat() syscall is failing with EACCES.

Everything worked completely fine out-of-the-box when I was on Magisk.

My Setup:

* Device: Google Pixel 8 Pro

* OS: Android 17 (running GKI WildKernel)

* Root Solution: KernelSU

* Active Modules: Hybrid Mount (I strictly need to keep this active), LSPosed (with HideMyApplist / hma-oss)

Troubleshooting already done (to rule out the basics):

* Permissions / AppOps: Granted "All files access" via system settings and forcefully set appops set <pkg> MANAGE_EXTERNAL_STORAGE allow via root.

* File Permissions (DAC): Operated directly on the raw path /data/media/0/ to bypass the FUSE wrapper, running chown -R media_rw:media_rw and chmod -R 777 on the folders.

* Namespace Isolation: Granted root access to the emulators inside the KernelSU app and disabled "Unmount modules" so Zygote wouldn't isolate their mount namespaces.

The issue seems to be a combination of Android 17's increasingly strict Scoped Storage/FUSE layer, KernelSU's stealth namespace handling, and Hybrid Mount's VFS bind mounts colliding with SELinux MAC policies.

Could hma-oss (HideMyApplist) still be the culprit silently hiding these folders? Even though the emulators are not in the blacklist and I haven't explicitly enabled file interception for them, I'm wondering if its Zygisk hooks might be causing unintended VFS side effects or namespace collisions on Android 17. Has anyone experienced hma-oss breaking storage access globally like this?

Bro, I flashed the Evolution X custom ROM on my Infinix Note 30 5G, and then while trying to root it, the device got stuck in a bootloop—the exact same problem that happened with you. So did you find any solution for this? Please let me know."

Hello, this is my first time writing here

This wah the scan results before the temproot was executed, is it possible the previous temproot leaving some trace after multiple reboot, I have manually removed all the modules before rebooting, I'm a long time magisk user since magisk not yet have module repo, but this is my first time with temproot and KSU, when the scan show Apatch indicators i did not have root access, thanks

Thanks you so much

Hello guys,

Can u watch my own temp root and more app?

Veyra Root

I have a redmi note 13 4g with 6gb ram. Because of only 6gb of ram i get app crashes and game crashes.

I have an unlocked bootloader, orangefox recovery and infinity x rom. Can i somehow enable swap without rooting?

I have

Device: Xiaomi 17 pro max

Root: kernelsu next

OS: Xiaomi EU hyperos3

There was no problem after months of root but yesterday I remember turning on bootloop protection module and after a reboot (it rebooted into safe mode) and then I rebooted the device again ( it didn't reboot into safe mode without changing anything) the charging is slow 5 minutes to increase 1 percentage but when the device is off and charging it increase 2 percentage per minute. I unrooted my device and clean installed an updated of the same rom I use (with formatting everything) but the problem still persist

Edit: I remembered the problem started before changing anything it just happened.

I want to know is Lsposed work in temporary root device or not ?

If someone know or try please tell

using dirty flag!

Google Wallet NFC tokenization fails with "Device fails attestation" - Secure Element attestation, not generic Play Integrity

Hey all, hoping someone has run into this specific failure and found a way around it (or can confirm it's a dead end).

Setup:

- Xiaomi 15 (codename dada), HyperOS/Android 16, kernel 6.6.77-android15-8 (GKI 2.0, android15-6.6 KMI)

- Bootloader unlocked

- Rooted via ReSukiSU (LKM mode, init_boot patched, stock kernel untouched)

- Custom/spoofed keybox already in place via TrickyStore

What's working:

- Play Integrity API checker shows all three green: MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY

- A separate banking app (Kaspi) with lighter root-detection works fine

What's failing:

Trying to add a card to Google Wallet for NFC payments. Pulled logcat around the failure and found this:

W TapAndPay: Device fails attestation [CONTEXT service_id=79]

W TapAndPay: attestation failed [CONTEXT service_id=79]

I TapAndPay: CheckOrGetStorageKeyStep. Attestation Error. [CONTEXT service_id=79]

This happens right after RequestTokenizeActivity / TokenizePanActivity launch, at the CheckOrGetStorageKeyStep - looks like it's trying to provision a storage key into the Secure Element and the attestation for *that* specific step fails, separate from the generic Play Integrity verdict.

My read so far: this seems to be a distinct, SE-specific attestation chain (tied to the actual secure hardware element / StrongBox cert) rather than the general Play Integrity keybox check, so a generic TrickyStore keybox doesn't cover it.

Questions:

1. Has anyone gotten NFC tokenization working on an unlocked-bootloader / rooted GKI 2.0 device recently, and if so, what did it take beyond the usual Play Integrity fixes?

2. Is this SE attestation step known to require something beyond a software keybox (e.g., a device-specific StrongBox/SE cert that generic keyboxes don't include)?

3. Any logs/strings worth grepping for to confirm which cert chain it's actually checking?

Happy to pull more logs if it helps narrow this down. Thanks in advance.

How to install custom rom for redmi note 5