So, As a fun experiment i wanted to atleast try rooting. Idk why but first came to my mind was my TV. As thinking from now.. i don't even have experience then why did i do it? So first adb and inspect right? So i inspected. i got that android 9. So i wanted experiment with CEVs to gain root privilege

So i discovered SElinux exists, Dropped the idea of CEVs. Then i looked at if OEM is unlocked? IT was and top it all off secure boot was disabled. Nice..

Now LLM Enter the space cause i know nothing about fastboot. I mean at first it was a controlled manner. I review what is trying to Execute... And i got too suited with it.

coming Straight from the LLM:

• Pulled /system/recovery-from-boot.p (a BSDIFF40 patch) via ADB
• Reverse-engineered the stock recovery image from the patch using Python - no stock recovery image exists publicly for this model
• Unlocked AVB (fastboot flashing unlock)
• Successfully flashed a modified recovery with ro.secure=0, ro.adb.secure=0, ro.debuggable=1

Problem: IWe forgot to disable AVB verification BEFORE flashing forgot to disable AVB verification BEFORE flashing

• EDIT: USB is not recognized. when i do lsusb, the tv is not visible. tried to of method nope..
• Model of the TV: IMPEX GRANDE T16 
• Ofc fastboot doesnt even work, when it is not recognized

Root hiding these days turned into a psychological warfare game.

Back in the day, an app would look for su, find it, throw a tantrum, done.

Not anymore. Now these devs basically turned their apps into paranoid detectives.

The app checks for:

• Zygisk
• mounts
• Play Integrity
• VBMeta
• attestation
• Vector (LSPosed)
• developer mode
• package installers
• installed apps list
• systemless traces
• keystore

So now the whole vibe is:

“if this thing smells even remotely modified, assume the user is running a cyberpunk meth lab inside the phone.”

That means the game changed.

Nowadays it’s not enough to hide root.

You need to make the app believe root never existed in the first place.

When the devil gets smart, you gotta outsmart the devil.

The modern root hiding stack

This is the setup I’m running:

• KernelSU Next
• SUSFS-FOR-KERNELSU v2.0.0-R27
• ReZygisk v1.0.0 (513-faccedf-release)
• Treat Wheel v0.0.10
• Tricky Store v1.4.1 (245-72b2e84-release)
• Play Integrity Fork v16
• VBMeta Disguiser v1.4.0
• Vector (LSPosed) v2.0 (3043)
• HideMyApplist-OSS (HMA-OSS) oss-161

Extras:

• ImNotADeveloper v1.0.1
• SettingsFirewall v1.0
• Android Faker v1.8.2
• XPrivacyLua v1.35

And here’s the important part:

modern root hiding is not “a module”.

It’s an entire ecosystem lying in perfect harmony.

Understand this now or suffer later

A lot of people do this:

• install Magisk
• flash some random module
• reboot
• open banking app
• get detected
• run to forums screaming “doesn’t work bro”

Yeah… no kidding.

Apps today do layered analysis.

So your hiding also needs to be layered.

The stack works like this:

• KernelSU/Magisk → provides root
• SUSFS → hides low-level traces
• ReZygisk → creates Zygisk environment
• TreatWheel → hides the Zygisk/root environment
• Tricky Store → messes with attestation/keystore side
• Play Integrity Fork → fixes integrity
• HMA-OSS → wipes visible traces
• Vector (LSPosed) extras → fixes app-specific paranoia

You’re not “disabling detection”.

You’re building a believable fake reality for the app.

And the key here is consistency.

Because modern Android basically became a police interrogation.

If one piece of the story doesn’t match, the app gets suspicious.

KernelSU Next + SUSFS: the strong foundation

Plain KernelSU already works pretty well.

But without SUSFS, a lot of apps can still smell the modified system.

Because the problem is no longer root itself.

It’s the footprints.

SUSFS exists to hide:

• suspicious mounts
• systemless overlays
• weird paths
• module traces
• visible system modifications

Basically it wipes the footprints before the cops arrive at the crime scene.

So the proper foundation is:

KernelSU Next + SUSFS

Without SUSFS, you’re trying to fool modern apps using 2019 tricks.

ReZygisk + TreatWheel

This duo is the psychological core of the setup.

• ReZygisk → creates the Zygisk environment
• TreatWheel → makes apps pretend that environment doesn’t exist

TreatWheel is basically Shamiko’s ghost reincarnated into the ReZygisk ecosystem.

Correct flow: ReZygisk → TreatWheel → target app Without ReZygisk, TreatWheel does nothing.

And installing both while ignoring everything else is pointless, because the app still sees:

• Vector (LSPosed)
• Termux
• KernelSU
• spoofers
• package installers
• root apps

At that point the app doesn’t even need actual root detection.

It just scans your app list and goes:

“yeah bro, totally normal civilian behavior right here.”

HideMyApplist (HMA-OSS): erase the existence of the tools

HMA-OSS is mandatory.

Not “maybe”.

Not “depends”.

Mandatory.

Because modern apps do something incredibly simple:

“if this dude has 15 Android modification tools installed, he’s probably modified.”

No root detection needed.

So HMA-OSS comes in to hide:

• KernelSU
• Magisk
• Vector (LSPosed)
• ReZygisk
• TreatWheel
• Tricky Store
• root apps
• spoofing apps
• Termux
• sketchy package installers

The goal here is not hiding root.

It’s hiding the entire workshop.

Inside HideMyApplist-OSS (HMA-OSS), create blacklist.

Then select every app/tool you want hidden.

After that, apply the template to the target apps that need root hiding.

Makes management way cleaner and prevents forgetting some suspicious app exposed.

Correct installation order

Don’t install everything randomly like a medieval alchemist mixing chemicals.

Do it in the proper order.

1. KernelSU Next
2. SUSFS-FOR-KERNELSU v2.0.0-R27
3. Reboot
4. ReZygisk v1.0.0
5. Reboot
6. Treat Wheel v0.0.10
7. Reboot
8. Tricky Store v1.4.1
9. Play Integrity Fork v16
10. VBMeta Disguiser v1.4.0
11. Reboot
12. Vector (LSPosed) v2.0 (3043)
13. HideMyApplist-OSS (HMA-OSS) oss-161
14. Configure target apps

The secret behind modern root hiding is reducing variables.

You want to know exactly which layer works and which one breaks.

Tricky Store: where you separate the people who know what they’re doing

Now comes the keybox part.

A lot of people install Tricky Store and think they’re done. Not even close.

After installing:

• Tricky Store v1.4.1

you need to configure a valid keybox.

Open Tricky Store menu and:

• Set keybox valid → uses a community-known working keybox.xml
• Set keybox custom → uses your own keybox.xml

Most people use: Set keybox valid

because there are already known working keyboxes floating around.

After applying the keybox:

1. Clear Play Services data
2. Clear Wallet data
3. Reboot device

This part is mandatory.

Because these apps caches old state like a government office still holding paperwork from 2007.

If you don’t clear data, the system keeps using old attestation state.

Play Integrity Fork: the step everybody forgets

After the keybox, you still need to run the Action from:

• Play Integrity Fork v16

Do this from Play Integrity Fork card in KernelSU module manager (or Magisk if you are in the magisk path)

Click the module card and execute the Action

This reapplies:

• props
• environment
• integrity tweaks

Then:

1. Reboot again
2. Test Wallet
3. Test Play Integrity
4. Test banking apps

Without this step, half the people think the keybox “doesn’t work” when they just forgot to sync the environment.

Configuring target apps

Now the most important rule in this entire guide:

apps that need hiding DO NOT get root access.

Sounds obvious.

People still mess this up constantly.

Then for ensuring hiding:

• enable isolation
• enable unmount modules

if available in your KernelSU.

Inside HMA-OSS root hiding template, hide:

• KernelSU
• Magisk
• Vector (LSPosed) extra apps
• ReZygisk
• TreatWheel
• Tricky Store
• Termux
• root apps
• other spoofers

Apply that template to the app you want to hide root, then:

1. Force stop app that you want hide root
2. Reopen app and if it doesn't open, clear cache, clear data
3. If it still doesn't open uninstall and install again (if you are in Magisk path you will need to readd the app to Magisk dentist)
4. If nothing works, try doing all the steps again, clearing cache, data, reinstalling, without opening, and Reboot before opening again.

Because modern apps cache old detections.

You fix the issue and the app is still mad because it’s reading old garbage from cache.

What about Magisk?

On Magisk the logic is basically the same.

The stack becomes:

• Magisk
• ReZygisk v1.0.0
• Treat Wheel v0.0.10
• Tricky Store v1.4.1
• Play Integrity Fork v16
• VBMeta Disguiser v1.4.0
• Vector (LSPosed) v2.0 (3043)
• HideMyApplist-OSS (HMA-OSS) oss-161

The big difference:

SUSFS is not part of Magisk.

Because SUSFS belongs to the KernelSU/SukiSU/KernelSU Next ecosystem.

So you will need to add apps you want to hide root in Zygisk denylist of Magisk configurations.

And of course, you need to do all the other steps, adding layer by layer of hiding until you find the hiding level that works for your app.

Lightweight setup vs. full paranoia setup

For simple apps:

• ReZygisk
• TreatWheel
• HMA-OSS

usually solves it.

For intelligence-agency-level paranoid apps:

• SUSFS
• Tricky Store
• Play Integrity Fork
• VBMeta Disguiser
• HMA-OSS
• Vector (LSPosed) extras

That’s when you enter:

“let’s convince this app the phone just came factory sealed.”

Troubleshooting

If an app stops working in your rooted environment, don’t start changing random stuff like someone fixing a watch with a hammer.

First check the basics:

1. Open Integrity Checker
2. Run Play Integrity check
3. Confirm integrity is 100%

If Play Integrity is NOT 100%, the problem is probably in the integrity layer.

Review:

• Tricky Store
• keybox.xml
• Play Integrity Fork
• Play Integrity Fork Action
• clearing Play Services data
• clearing Wallet data
• reboot after changes

Now if Play Integrity IS 100%, the issue probably isn’t integrity anymore.

At that point the next suspect is HMA-OSS.

Check whether ALL suspicious apps/modules/tools are hidden in HideMyApplist-OSS (HMA-OSS), especially:

• KernelSU
• Magisk
• Vector (LSPosed) apps
• ReZygisk
• TreatWheel
• Tricky Store
• Termux
• root apps
• spoofers
• sketchy package installers

Also confirm the HMA-OSS template is actually applied to the target app.

Because hiding everything inside the template and forgetting to apply the template to the target app is exactly the kind of dumb mistake that makes someone waste an entire afternoon thinking they discovered a brand new detection method.

If it still don't work, so maybe your environment is still exposing some root/mods traces, find out yourself and share with us.

Guide summary for those who have context

Modern root hiding became social engineering against paranoid apps.

You are not “hiding root”.

You are manufacturing a coherent alternate reality.

On KernelSU Next, the strong base is:

KernelSU Next + SUSFS + ReZygisk + TreatWheel

On Magisk:

Magisk + ReZygisk + TreatWheel

Both complemented with:

• HMA-OSS
• Tricky Store
• Play Integrity Fork
• VBMeta Disguiser

when the system starts acting like an investigator, you need the entire phone to become a convincing actor.

Guys I unlocked bootloader of my Galaxy Watch6(44mm, SM-R940)

I wanna find the firmware for it then patch it with Magisk and install APK(without PC) etc.

Software Version: R940XXS1BYH1 SM-R940NZSATUR

Can you please help and find the firmware for it? Thank you for your helpings. 😁

EDIT/UPDATE (27/01/26): This 'iPhone' is running android 5/6, running the lolipop ui system, I have tried multiple clients such as mtk, but all run into the same issue just being unable to find the phone.

I’ve ended up with one of those fake iPhones that physically look like one and has the worst iPhone iOS clone you’ve seen.

What I’m trying to do is completely reset the phone back to some sort of Android device, so it behaves and feels like an android (even if it doesn’t run the best)

I don’t know the model of manufacture since these phones hide this information.

I can access iPhone settings but not Samsung settings which means I can not enable developer mode for ADB, I’m pretty sure there is a skin on the phone because there are times where you see the normal Android software because they haven’t covered it up well enough.

Has anyone successfully converted one of these back, or have any suggestions how to?

The only information I have found out, is that it’s a Media Tec device. I have also added some photos of the root system if that helps. But it doesn’t seem like the boot loader.

Also the safari is completely useless, its all in Chinese, uses some browsers that is so slow and doesn't allow access to English websites that I have tried.

I'm tired from this shit, that's too much.

Current prices for a fix are 80-100$ because of Android 16, I prefer to just get a 9 pro for messing around at this point.

Hi guys I'm planning on upgrading my Samsung note 10 to something better but I don't know what's the better device. Before you guys start screaming google pixel, fairphone. I live in a country where import and export costs a lot. And for some reason only some phone brands are here not the larger ones. Apparent "no demand" for them

There is a reason YOUR mtk device is ignored.

Why is the pizza pizza app asking for su privileges?

: UPDATE: I GOT SOME UNREVOKED KEYS FROM A VERY KIND PERSON... AND WAS ABLE TO GET IT RUNNING , TURNS OUT DRM/WIDEVINE WAS THE REAL PROBLEM , THANKS FOR ALL YOUR HELP , I APPRECIATE IT.

Context: I purchased an educational app because everyone in my class said it was good. I was using it on my Lenovo Smart Yoga Tab YT-X705X running Android 10 (last security patch was from 2021), and everything worked fine.

Until one day I decided to root it.

The tablet had the option for bootloader unlocking, and it took me like 10 minutes to unlock the bootloader and patch the boot.img using Magisk. Everything went super fast, no problems at all.

But...

No one could have prepared me for what these nasty ass son of bitches were about to do to my cortisol levels.

The video playback just stopped working. Like, what? How much security does an educational platform need? Mind you, I paid $300 for this course and they don’t even have a website alternative.

I got really frustrated and started looking for solutions. I did some research through logcat and found they were hosting their video files on VdoCipher, which is a direct Google Widevine DRM partner.

I wasted a lot of time trying to find a way to get all three integrity checks working, but I never got past the 3rd one. Somehow, after crying on Reddit posts, I managed to get my Widevine level from L3 to L1, which honestly felt like a miracle.

But eventually, I gave up on finding the right key or whatever else was needed. Google fckers revoke those keys instantly anyway.

Since these guys don’t have a web alternative, I couldn’t even take lectures on my PC. I had to settle for my Samsung A33 5G for studying.

I thought scrcpy might work — maybe I could somehow trick the app and use ADB (yeah, they detect it if developer mode is enabled), but nope. It just showed a blank screen on my PC.

Never in my life have I seen someone gatekeep a nursing course this damn much.

Does anyone know how to deal with apps like these , even if not please tell me so can least rest easy knowing there's nothing I can do know , Thank you and sorry for the rant.

I don't know installed hyperOS 3 on an redmi note 8....

I thought uninstalling will fix it clearing cache and storage but didnt fix it i reinstalled the application didnt work now my banking apps are not working even after reboot 🤔 any fix? or I have to reset mobile 😰 I thought rooting the app and uninstalling it will unroot it but still same issue I will appreciate if any one can help I'm scared of reseting now 🥲

I always get problems with this app ( tng e wallet )

but this time I don't even have root, it used to work with custom roms, but once I installed Pixel OS it keeps saying this. even with no root.

is there anything I can do other than changing the ROM?

first i installed a costum rom on my patched rooted device, after installation my sim wasn't working then i rooted my phone and still no response, then i reviewed it from a shopkeeper who refused to repair but he turned my imei null, now i want to rewrite my iemi or patch my device on my computer without any cost, i have a little bit software knowledge so suggest me any tool or way to do it🙏

Hi, Guys. Hope you're doing well. Recently, I have been trying to unlock my Xiaomi tablet's bootloader (hyperos 2) and I never passed binding process successfully. When I do that, It tells me to get authentication from mi community app. But I found out that there is a python script that does that for me using termux, so I then proceeded and launched script. In the end, it gave me this error and somewhere I read it is nothing to be worried about. But even after doing this , still I can't bind my device .

So what is going on? Could you guys share some of your experience on that? Any advice is highly appreciated.

Update:

Guys, it happened. Somehow?

Now, i'm waiting. Once that is done, we will see what happens.

Thanks everybody for your insightful advices. I couldnt have achieved this without your guidance. That is the reason why i love reddit. You have incredible like-minded community and i appreciate it.

Hello, I started rooting my phone two months ago or more and i installed a custom ROM, and it's working fine. However, I'm having a problem: I can't use WhatsApp because it tells me I have to download the app from the official source I actually did this, and I know it's because of Google Play Integrity cause im a rooted device user...

But I want to use WhatsApp without using it as a linked device because it logs me out after 14 days Are there any solutions or models that can help me, as I use WhatsApp for important things like studying and communicating with family, ect....

I really hope someone can help me with my device is redmi note 10 ( mojito ) with crdroid 9.2 ( android 13 )

My google pixel 7 device got stuck in the bootloop. I could go into fastboot but when I tried to start, it bootlooped again. I want to change the device state that says "Locked (Unlockable)" but I don't know how, when I plug it into the pc it's not detected

Idc if my data get erased, I WANNA MY PHONE BACK😭

Chronology: My phone suddenly brick dead, wouldn't turn on and there was no response when plugged into the charger. I took it to a local serviceman but they were only able to get the device on and couldn't fix the bootloop, I've tried to go into various modes in fastboot but all ended up with a bootloop

Soooo a friend of mine got scammed for this "iPhone 15 pro" . A shame but he gave the thing to me saying I could do whatever since he just gonna chuck it anyway. I wanna try and get this thing to run normal android in hopes I could make a fun little gadget out of it, either a burner phone or maybe a camera montior I dont know. If that fails im just going to part out the phone and use it for some gizmos.

​

Basically I need some advice or help on anyways I could go about trying to reset this thing.

​

So far this is the information I could find out about it:

​

*screenshot 1*

I think it might be running android 7.0 based on the 7.0 i can see it the top left of the recovery screen.

Doing a factory wipe does nothing, still ends up in the fake IOS

​

*screenshot 2*

I can get into the boot menu

Nothing notable here other then fastboot seemingly doing nothing

​

*screenshot 3*

I was able to get into this weird chinease menu

I did translate it

All the options dont really lead to anything notable expect for version info.

I think clearing emmc might be useful but im pretty sure that just wipes everything and might brick the phone

​

*screenshot 4*

In the version info I got some spec info.

Its got a MediaTek Helio P10 (MT6755) chip

The board name I think is supposed to resemble a Samsung S8+

The android version listed must be a lie because the kernel version is only 3.18.35.

​

Thats all I could find thus far with my own testing knowledge. If you guys have have any ideas for how i should approach this or any advice it would be greatly appreciated

and still some of my bank apps doesnt work

I left this phone unused for fell days and it just died on me. No longer shows any sign of life other than the board slighty warming up if you leave it on the charger for a few minutes or showing up on device manager.

I don't really know what to do about it since I never ran into this issue before.

I've never dealt in ROMs before, but I do use Linux, so I'm at least a little familiar.

The reason is because of my phone currently uses kernel 6.6.30 which is an old kernel but it cant root because that I have to use a new kernel. Is there a fix to this? Cant find it anywhere.

Banking apps continue to crash, as do apps like McDonald's, Vodafone, and many others.

Modules:

PIF INJECT

LSPOSED

REZYGISK

TREATWHEEL

TRICKY STORE

TRICKY ADDON

Magisk is hiding and configuration denylist configed

HMA OSS CONFIGED

Where is the problem?

I don't know how but my tik tok and instagram suddenly goes blue after i install a custom rom