Current ROM now:- Latest TRM Hyper TR

LOOK GUYS I SOMEHOW LOCKED BOOTLOADER WHILE ON TRM HYPEROS AND CHECK IT OUT!??111

/s jokes aside, yeah this is rooted, bl unlocked and all, do not DM me for how to

Please don't actually go ahead and attempt to lock bootloader on a custom ROM, or worse, flash sweet_k6a firmware on sweet/in

Okay so regarding latest native test
https://news.1rj.ru/str/LSPosed/279
There's this new "Partition Check Fail" check that will trigger on the following scenarios
A. You're using non-gki KSU, and it's not properly unmounting modules
Solution: SUSFS, or switch to MagiskAlpha+Shamiko
B. You are on a ROM that has avb stripped from fstab (usually to be RW)
Solution: there's a really wacky workaround but obviously it's not a permanent solution, a permanent solution would be to be on a ROM that has avb intact or patched (in the case to get normal on native test, that would be stock ROM)
C.You tell me....

And also, APatch is completely detected on latest native test even with cherish peekaboo, no solution but to switch to KSU+SUSFS or MagiskAlpha+Shamiko

Starting from now on
I'll not nuke ro.dalvik.native.bridge prop!
Reason: Appdome gets triggered over it being missing (that's what detected magisk code 2500000 means btw)

Update: sailfish FP is now banned and gives only basic integrity
If you're using PIF, update to latest one since that will use husky FP
If you're using trickystore, use spoof_build_vars files below and reboot

Here is husky fp one

Regards root solutions and their current detection
Magisk: only one app cares about it so far (DBS paylah and soon native test) but the rest of irl apps + detectors don't give a shit
Apatch: same as magisk (native test) though I believe this can be fixed in a newer cherish peakaboo update
Does that mean the best root solution is apatch? Yeah, since it's an overkill detector app that finds it but it suggests that soon irl apps will figure it out eventually
And magisk? As long as the anti-root dev on dbs paylah don't disclose it to other irl apps (or does, but by that time magisk would've patched it), I think it's safe
So the superior root solution is KSU+susfs? Yeah, but if you want to deal with EOL stuff (for non-gki) and have it break random stuff like usb otg that is

Also, not to mention but apatch and KSU+susfs have very limited kernels to support it (stock perf and skiddie perspectively), whereas magisk works on all kernels no probs

And some info regarding susfs
Susfs is not for newbies, but for intermediate root users with knowledge regarding mount points, as you'll have to configure susfs to hide those mount points. Susfs does not automatically hide them for you (like Shamiko and Cherish Peekaboo)

Updated latest one

To refresh trickystore and gms without rebooting after changing file

su
killall -9 TrickyStore
nohup sh -- /data/adb/modules/tricky_store/service.sh &
killall -9 com.google.android.gms.unstable

Again, PIF users just update and reboot

Damm, even latest husky_beta got killed quickly.... And there is no more betas for husky

I really, really don't want to use pixel 9 series props

If this one died really quick too then I don't think I got much of a choice...