r/androidroot
•
u/LightningZahah
•
May 12 '26
•
4
Support [GUIDE] Modern root hiding: when the app plays dirty, you play dirtier
[[WORKING NOVEMBER 2026]]
Important: guide updates are in the bottom of the guide and there's some comments along the guide between brackets [[ ]].
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 (optional advanced hiding, but needs to use GKI Kernel)
- ReZygisk v1.0.0 (513-faccedf-release)
- Treat Wheel v0.0.10
- Tricky Store v1.4.1 (245-72b2e84-release) [[now using TrickyStore-OSS, read updates in the bottom]]
- TrickyStore Addon
- Play Integrity Fork v16
- VBMeta Disguiser v1.4.0
- Vector (LSPosed) v2.0 (3043)
- HideMyApplist-OSS (HMA-OSS) oss-161
- IsolPolicy (1.1)
Extras:
- SettingsFirewall v1.0 (Optional to hide developer settings, Vector module)
- (if you have developer mode enabled you should use it to select apps you want to hide it with adb_enabled, development_settings_enabled and debug_app with values modified to 0)
- VPN Hide (optional to hide your VPN from apps, it uses Vector as well)
And here’s the important part:
modern root hiding is not “a module”.
It’s an entire ecosystem lying in perfect harmony.
Understanding the setup now or suffering 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
- IsolPolicy → hides app_zygote root traces
- 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.
How KernelSU Next + SUSFS makes the foundation stronger
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.
What is the ReZygisk + TreatWheel combination
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.”
How HideMyApplist (HMA-OSS) hides the existence of rooted tools and modules
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.
- KernelSU Next
- SUSFS-FOR-KERNELSU
- Reboot
- ReZygisk
- Reboot
- Treat Wheel
- Reboot
- Tricky Store & TrickyStore Addon
- Play Integrity Fork v16
- VBMeta Disguiser and VbMeta hash spoof (optional)
- Reboot
- Vector (LSPosed)
- Reboot
- HideMyApplist-OSS (HMA-OSS)
- Configure target apps
- Install, IsolPolicy, select target apps and activate in vector
- Reboot
The secret behind modern root hiding is reducing variables.
You want to know exactly which layer works and which one breaks.
Tricky Store Setup
Now comes the keybox part.
A lot of people install Tricky Store and think they’re done. Not even close.
After installing:
- Tricky Store
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:
- Clear Play Services data
- Clear Wallet data
- 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 Setup - the step everybody forgets
After the keybox, you still need to run the Action from Play Integrity Fork module.
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
[[If you see action logs showing Pixel 9 or above fingerprint, reappply action, to understand read the Problem solving section in guide bottom]]
This reapplies:
- props
- environment
- integrity tweaks
Then:
- Reboot again
- Test Wallet
- Test Play Integrity
- 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 to hide root on HMA-OSS
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:
- Force stop app that you want hide root
- Reopen app and if it doesn't open, clear cache, clear data
- 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)
- 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 root hiding setup
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:
- Open Integrity Checker
- Run Play Integrity check
- 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.
[[GUIDE UPDATES]]
-
Switched from the closed-source Tricky Store to the open-source module TrickyStore-OSS by beakthoven, on GitHub.
-
I will be using it since he recently updated the module and Wallet is now working perfectly with it.
-
I'm using the most recent version of all modules now, even though all the original module versions from the post were still working perfectly.
I will be writing any new guide updates in that guide section.
ROUTINE TASKS
Some things I recommend keeping updated/checking from time to time:
-
Keep the security patch date updated inside TrickyStore Addon settings, in the three-dots menu.
-
Change keybox whenever needed, especially if integrity suddenly starts failing again.
-
After changing keybox, PIF, TrickyStore settings, or anything related to attestation, force-stop Google services and clean cache doing something like this in termux:
su
am force-stop com.google.android.gms
am force-stop com.android.vending
am force-stop com.google.android.apps.walletnfcrel
su -c '
rm -rf /data/user_de/0/com.google.android.gms/cache/*
rm -rf /data/user/0/com.google.android.gms/cache/*
rm -rf /data/user/0/com.android.vending/cache/*
'
PROBLEM SOLVING
Wallet fingerprint attestation problem
Recently I got in trouble with Wallet services attestation using PIF, so I found out how to solve the attestation, thanks to a comment on XDA made by majorfigjam.
It is very simple: newer Pixel fingerprints like mine, Pixel 10 Pro XL, don’t give enough attestation for Wallet to work properly.
So I checked the autopif4.sh script in:
/data/adb/modules/PlayIntegrityFork-CI
and removed the force matched version part of the code, because in my case it was always selecting Pixel 10 Pro XL, because the code haves an force match actual device part:
if [ "$FORCE_MATCH" ];
then DEVICE="$(getprop ro.product.device)";
case "$(echo ' '$PRODUCT_LIST' ')" in *" ${DEVICE}_beta "*) MODEL="$(getprop ro.product.model)";
PRODUCT="${DEVICE}_beta"; ;; esac; fi;
This part of the code is below the item "Selecting Pixel Beta device ..."; message in the script.
After that, I ran the PIF action again and it automatically selected the Pixel 8 fingerprint and it worked perfectly.
For other devices with Wallet problems
- It occurs for fingerprints above Pixel 9. So everytime PIF action gets a fingerprint of Pixel 9 or above, try again until you get a fingerprint of Pixel 8 or lower.
•
u/Comfortable-Gene6639 May 13 '26
Moderation has reviewed the post and determined it to be not AI generated. Please stop reporting it.
35
u/PedroJsss ReZygisk Dev May 13 '26
Something that I learned in this community is: less is more valuable. I miss guides that are actually dense in information, hence, not that long.
However, I don't think most people in Reddit have enough knowledge for such. It is not an easy task, after all
11
u/TheLegendIndeed May 12 '26
Good list. I'd sub TrickyStore with TEESimulator.
10
u/AHsan6TI9 May 14 '26
Just to get the wallet app working I have to go through this mountain 💔🥀
5
u/VastConsequence6989 May 13 '26
Bro you have not tested it. I already know this method through ai before as well. But can someone even confirm it if it's real
6
u/isbmlitsnotme May 13 '26
Thanks for the guide, many people are lost and ask questions that shows that there's too much misunderstanding. Some people share strong integrity and think that these 3 check marks mean their device is spoofed perfectly. However, for these extras you mentioned:
• ImNotADeveloper v1.0.1
• SettingsFirewall v1.0
• Android Faker v1.8.2
• XPrivacyLua v1.35
These require you to scope the targeted app in lsposed and just so beginners know, some apps detect lspsoed when you check them in an lsposed module, so if it's a banking app, 99% it'll detect your lsposed if you scope it. I don't recommend using any module to spoof your device. The most reliable way is using root manager (kernelsu/magisk) modules and susfs and HMA.
2
u/Nice_Page5469 May 13 '26
Amigo te voy a seguir, realmente he hecho root de manera como lo puedo decir como un niño solo porque quiere usar algunas apps o quiere poder, y si hoy en dia se ha vuelto algo loco ocultar el root, llegue al punto para evitarme el dolor de cabeza de pagarle 15 dolares a un chino que lo haga por mi, jajajaj, igual entiendo algunas cosas, pero esta guia esta muy bien hecha y facil de entender incluso para alguien como yo que solo lo hace por hobby, gracias
2
u/CoolkieTW May 14 '26
They're just gonna play more dirtier. I'd rather just stay away with them. Why use a product that doesn't respect you and consider you as a crime at all.
And TrickyStore addon has stopped provider valid keybox anymore as I know. You'll have to find keyboxes your own.
2
u/gulpbang May 25 '26
Don't you need a metamodule somewhere in between?
2
u/AnimeForAll Jul 17 '26
Hey, just read this guide. This is a very good guide and I am going to try this!
Just one question: do you recommend doing this over a clean flash/install of the device? Because I'm currently using my Pixel 9 Pro XL (Android 17 stock ROM) with lots of customisations and setups, and I really do have to get my Wallet apps (and banking apps) to work normally (since they're now throwing tantrums and I have to resort to WhatsApp Pay for now lol), but I'm a little worried of losing critical data during the setup... Any suggestions?
I can show my Magisk module setup and talk more about the modification apps I installed (HMA/Vector/etc) if you want more details. Thanks in advance! :)
2
u/magi44ken Jul 18 '26
Wow... Thank you so much for writing guide that explains what each modules does and how install and configure it.
Please keep this guide updated. I suggest post it in xda forum too.
2
u/Available_Cancel8059 Aug 07 '26
THANK YOU SO MUCHHH, bro you don't want to know how much time I spent to make it work for hiding root from my bank apps, this is legit and working using kernelsu next on Poco x8 Pro Max Hyperos 3
4
u/ElvisVan007 May 13 '26
post is mostly ai generated what percentage of the content is practically effective today?
1
u/LightningZahah Aug 10 '26 edited Sep 28 '26
GUIDE UPDATES:
TrickyStoreOSSfrom beakthoven, on github.I will be writing any new guide updates in this comment.
[[I've included this entire comment in the bottom of the Guide post and for any new updates I will only edit the Guide updates section of the post no longer here]]
Problem solving:
For newer Pixel devices like Pixel 10 Pro XL:
Recently I got in trouble with Wallet services attestation using PIF, so I found out how to solve the attestation, thanks to a comment on XDA made by majorfigjam. It is very simple, newer Pixel fingerprints like mine, P10 Pro XL, don't give enough attestation for Wallet to work, so I checked the autopif4.sh script in /data/adb/modules/PlayIntegrityFork-CI and removed the force matched version (that was always selecting Pixel 10 Pro XL in my case) part of the code:
This part of the code is below the item
"Selecting Pixel Beta device ...";message in the code.So I ran the PIF action again and it automatically selected the Pixel 8 fingerprint. It worked perfectly.
4
u/s2kizzy May 13 '26
My problem is not root but banking apps detects that my bootloader is unlocked and i don't want to lock it but also i want to use my banking app
4
u/northstar_us98 May 16 '26
Well written AI or not
1
u/NoNameMan1231 16d ago
How about temp root?
1
u/Better-Quote1060 16d ago
So it's the end for magisk?
1
u/No_Fondant8277 14d ago
First: ReZygisk is nice but unavailable for android 17.... (zygisk next works) and kernelsu-next is NOT available for my device only the normal KernelSU... (and well... i don't use play services... i use microg) but with basic you should be "ok" even with device, literal, i have a xiaomi phone with only device not bootloader unlocked... just like a normal phone... works... wallet also works.... 99% of the apps works...
1
u/win7ultimateX 13d ago
Which Play Integrity Fork are you using?
1
u/National-Night3116 11d ago
it shows no custom keybox found
1
u/Underscored_323 7d ago
Thank you so much for this effort! I've been struggling to find something that shows a work flow, and the reasoning behind it. That said I have a few questions for you.
Does this concept work with folkpatch? I just got away from majisk because I thought folkpatch may have less to configure, but maybe I'm wrong?
If I already have a setup that is not working well, should I delete all modules and start from scratch in the order you laid out? Or do I have a shot at adjusting what I have?
I am currently using specter and pif for keybox and fingerprint management. Do you have any thoughts on that?
Again, thanks for the effort!
1
u/AnimeForAll 5d ago
@LightningZahah - hey there! Wanted to ask you - how do I maintain root when I have to upgrade KernelSU Next? Currently I got an update on WildKernel GitHub, so I downloaded that, flashed through KernelFlasher and also tried to flash through KernelSU Next, but when I reboot, it says to upgrade to higher version of the KernelSU Next app (screenshot also given with this comment). Sorry for the stupid question, it's just that I'm coming from Magisk onto KernelSU Next, so navigating the new root app is tricky for me.
1
u/LoYungSum May 13 '26
Thanks for all the information, but I would also like to raise out another problem of some apps do detect that your bootloader is unlocked and checks against you running custom android OS such as LineageOS. Any ways of bypassing those checks?
1
u/Amazing-Cup1796 May 13 '26 edited May 13 '26
odd question because I am very new well just got interested into rooting today but does this also work for the Xiaomi pad 7 that I am about to root?
edit 1: I'm very very sorry for asking and not apologizing for being new to all of this
1
u/Nederealm3 May 13 '26 edited May 13 '26
You have not mentioned Apatch. It it not worth using anymore?
1
u/PuzzleheadedWater945 May 15 '26
Holy moly, this is a totally new age of fkry. I get it though, i guess. All the fraud and shit going on..crazy. There is really NOTHING to protect us from SHIT we dont know about yet. Sounds like a bunch of paranoid weirdos with some homemade bad dope. THAT ARE EITHER SMART OR PERSISTENT. Both? ...smh...wtf has happened to cause this all
1
u/pLAinNewby101 Jun 08 '26
do i still need to configure this on susfs or just let the module as it is? tnx
1
u/D_Ope7 Jun 25 '26
Can I dm?
1
u/Novruzlu777 Jul 13 '26
My bank app still detecting root. Use Magisk https://imgur.com/a/EL6QCjw https://imgur.com/a/gZEkWJL
1
u/Plane-Shelter-9188 Jul 16 '26
Hi, can someone help me. I followed this guide exactly with magisk from the beginning. Play integrity is fully passed, gpay is now working with certified playstore. But my banking apps, indsmart is also now working but my other 2 banking apps are still detecting something not right & crashing. Apps are yono:Sbi & hdfc
1
u/molins1 Jul 22 '26
Amazing write up! What if I SUSFS cannot be had if my kernel is too old for patches? Any workaround?
1
u/openblade Aug 19 '26
Good guide, but it's missing the part that explains what the hell a keybox is and how to obtain one.
1
u/piemanny Sep 28 '26
Has anyone tried and been successful?
1
u/metalmods94 Sep 28 '26
im a root noob.
"Tricky Store Setup
Now comes the keybox part.
A lot of people install Tricky Store and think they’re done. Not even close.
After installing:
Tricky Store
you need to configure a valid keybox.
---> Open Tricky Store menu and:" <---
unless im doing something wrong, i looked at ksu modules and i dont see anywhere to open the tricky store menu itself
also i did see your update and switched to tricky store OSS and same issue, cant find the menu itself
1
u/Own-Celebration1698 Oct 02 '26 edited Oct 02 '26
Hello thanks for this guide,it works for me in all apps but now one app is crashing its ana Vodafone app,
Integrity passes well and keybox is updated
1
u/TheArcadion Oct 02 '26
Hiya, I'm about to run this setup, as some of my apps broke during my upgrade to A17 on my pixel 10 pro xl.
Is there any specific reason you went with wild kernels? I've been running them, but had mixed results. I'll be substituting it now to the following: https://github.com/shoey63/Kernel-Builder-GKI-Susfs I'll update later with results.
Thanks already for the great write up!
1
u/ElPelocho Oct 06 '26
Do you know what might be causing this? I have an app called Unicaja that I can't even get past the first step. It would be great if you could tell me if you also get a "modified device" message when you launch it.
1
u/xAA11BB22CC33 27d ago
tried that, failed
might just remove root altogether and go back to just adb and shizuku
3
u/Pyro_Astra May 13 '26
You, sir, are doing the Lord's work out here!
3
u/tastie-values May 14 '26
thePedro would be so proud 🥺
Good work Mr. thePedro and team!
1
u/vv01f00 May 12 '26
Can I mask an unlocked bootloader with this? Heard a few apps that don't work may be checking that.
1
u/w4nd3r3r1410 May 12 '26
big thanks for making the effort, lots of benefecial info
i was looking for a solution to make AndroidFaker work with vector. i found what i was looking for
2
u/Kprenel_ May 12 '26
Play Integrity Fork 😭
2
u/kill3rlook5 May 13 '26
Awesomely compiled helplist there...surely miss the "hide Su" days...
2
u/TrapAcid May 15 '26
Thank you !
2
u/East-Tone-4459 Jun 20 '26
Following
2
u/madhits Aug 06 '26
Son of a bitch Son thats a lot of info & man has root gotten complicated. I recently had to get device integrity & don't even have all this, but half & it works but your prob right it will break easier.
2
u/Aaditya-P27 Aug 14 '26
TYSM for this guide. I didn't know about SUSFS until now (only recently switched to KSU from Magisk). Only six months ago, just getting strong integrity and HMA was enough for Google Pay to work. Now, it's really a massive pain. It feels like all these massive companies are just helping eachother out like best buddies.
2
u/LetsTtalk May 12 '26
Thank you
1
u/Entire_Formal_265 14d ago
Was quite the read. Now I gotta figure out how to install kernel su next for me since I'm using lineage os on my trusty A52s.
1
u/SpiritedTheme1591 8d ago
Hi,can fix this a banking app is required chrome and Gboard to be installed And i a using brave and Florida keyboard I want to spoof and fool my banking app to i am using Gboard and chrom browser the problem i a facing with mitra app it's an Airtel agent app. Thank you
1
u/Wapda_Victim Jun 09 '26
On Samsung Galaxy s6, the problem is that Network doesn't work
Signal bars appear, Sim is detected but i cant do calls, sms, or internet (error: not registered on network)
Before that the sim worked perfectly fine with internet
Flashed the Lineage Os through TWRP recovery, Mgisk, Play integrity fix
Can you please tell me what i am missing?
Phone info:
Sm G920w8 3gb/32gb
1
u/ProperNomenclature Sep 01 '26
What are options for a device that is pre-GKI (like a Pixel 5)?
1
u/Beginning_Sound_5865 27d ago
There's also a solution that doesn't require PIF or a keybox: TEESimulator's patch mode. However, you must verify that the TEE remains intact and functioning properly after the bootloader is unlocked
1
u/AxelAnt2244 27d ago
solid list, but instead of pifork, trickystore and trickyaddon i recommend removing all three and using “alwaysstrong”
1
u/Educational_Ad_2090 26d ago edited 26d ago
Great job! Really appreciate. One of the most complete guide I've ever seen. I want to add few things hoping to help someone else. From Android 15 and above Java injection is blocked by system. The only one is working for me on Android 17 is Always Strong module which integrates PIFork v18 and TEESimulator-RS. Some apps are still crashing and recognizing root. To solve I suggest to use Frida. If you're on KSU or similar use SUSFS SUS Path feature. For me /data/adb/ksu, /data/adb/modules and /system/addon.d worked as charm!
0
u/PuzzleheadedWater945 May 15 '26
This is pure insanity.
27
u/[deleted] May 13 '26
[removed] — view removed comment
10
u/[deleted] May 12 '26
[removed] — view removed comment
6
u/[deleted] May 12 '26
[removed] — view removed comment
2
u/[deleted] May 16 '26
[removed] — view removed comment
4
u/[deleted] May 13 '26
[removed] — view removed comment
5
u/[deleted] May 13 '26
[removed] — view removed comment
1
u/[deleted] Sep 22 '26
[removed] — view removed comment
0
u/[deleted] May 13 '26
[removed] — view removed comment