Ah, you need to say, otherwise it will be assumed you have a TJW build.
These are my findings or lack thereof concerning the 'head scratching' on the OP8 5G UW OOS 11:Progress also on the other front:
TheHitMan7 (aka MagiskCustom) 95a4a4b8 from yesterday now works with LSPosed
I've tested with GravityBox-R and CustoMIUizer, with some mods there and it works just fine as with Magisk Alpha
- there is MagiskHide (not DenyList)
- MagiskHide can work with or without Zygisk
- Modules Repo is available
- SafetyNet checker is also integrated to the Magisk app (yesterday it was removed from the latest Alpha).
(All together, more like the old Magisk Stable v23)
Otherwise, it is also based on the latest TJW's commits for Magisk
Btw, to make LSPosed working, you must use TheHitMan7's LSPosed build - he had to remove dependency of DenyList as built into the newer LSPosed (official) builds (since his MagiskCustom has MagiskHide, not DenyList).
Otherwise, his LSPosed build was built based on the latest LSPosed 1.6.2 (18.104.22.168)
However, I cannot make Momohider working - I enable isolated option but MagiskDetector still detects su in the path (on Alpha, that isolated option helps to hide su from the path)
Good night. I've been reading last pages but haven't found anything... I was affected by September Safetynet CTS profile failure, but in Google Play my device appeared as Certified so I did nothing. Today I checked Safetynet by mistake and it has passed. Tried in Root Checker and passed too. WTF?? Sorry... Could someone explain it to me?
Thank you and regards
How do you expect anybody can explain anything to you if you don't provide absolutely no info about your phone, ROM, Magisk modules you use, what did you change, etc.Good night. I've been reading last pages but haven't found anything... I was affected by September Safetynet CTS profile failure, but in Google Play my device appeared as Certified so I did nothing. Today I checked Safetynet by mistake and it has passed. Tried in Root Checker and passed too. WTF?? Sorry... Could someone explain it to me?
Thank you and regards
When did you update Xiaomi.eu last time?@zgfg Redmi Note 9 Pro, xiaomi.eu 12.0.2, Magisk 23. In September CTS profail failed in Safetynet but my device continued been Certificate in Google Play Store and my bank apps worked so, as someone posted here, did nothing (didn't installed Magisk Alpha, nor Displax or kdrag0n safetynet fix). Yesterday I updated Busybox and, not sure why, checked Safetynet, and it passed. Tried with Root Checker and passed too. I have tried right now and keep on passing. Read some pages trying to find someone in the same case and didn'f find anything...
That's strange because (I think it was) in Sep when Google did changes on the server side, it caused SafetyNet failures@zgfg I don't remember when I updated, at least one year ago. And no, I haven't installed EdXposed, MHCP nor Universal SafetyNet Fix. I didn't touch anything because it worked, I thought it would stop working sometime and then I would have to install Riru+kdrag0n safetynet fix, but now it works, don't know why. All I have installed in Magisk is Busybox and Systemless Hosts.
Haha, I wouldn't know; I usually update before deciding I need to downgrade!
Well it should.
I'm on 8276a077-alpha myself. But, SN fails for me. I'm attaching screenshots of my setup. Please advise on how to get SN to pass. My device is POCO X3 (non-NFC) and I'm on the latest AICP 16.1 (A11). Thanks.
Generally, with (not-certified) custom ROMs (no matter which device and Magisk version) you first need to spoof fingerprints for e.g. same device but stock ROM (MHPC module - see the corresponding thread)
It just got released. Be patient.
You honestly think @topjohnwu won't be updating his Pixel devices to Android 12 and see the issue first-hand? You guys have filled this issue up with so much pointless chatter in the meantime instead of just waiting like I originally suggested back in May.
Also,Taking Things More Seriously
Although I always spent a lot of effort on Magisk, the project in my opinion is still more on the non-professional side. I would like to start taking things more seriously. Continuous integration is setup on GitHub recently, and I will start focusing on deeper integration with AVD to regression test changes before releases.
https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458Also, after open sourcing Magisk for so long, in the past year or so I finally start receiving a higher volume of serious external contribution to the core components of Magisk. These wonderful developers have helped find and fix many bugs in the Magisk code base, and also expanded compatibility with devices that I’ve never encountered before. The beauty of open source!
In addition to @zgfg's advice, please see this:
Anyone seen Happy Momo before?
Hiding Zygisk may be possible! ...
View attachment 5472595
"The environment is normal, no changes to the environment have been found"
Seems Shamico may be the answer, but early days... (according to this user / dev: nu11ptr)
I know nothing about anime, Manga, demon-girl characters etc, and this may or may not be relavent:
Anyway, looks like a genuine POC FWIW.
Simple hide based on zygisk.
Configure inheritance denylist. After installing Shamiko, configure denylist and close denylist, Shamiko will automatically take over and hide.
Theory supports Android 8.1+, but only tested on 11
You need to use the version of magisk after this pr: https://github.com/topjohnwu/Magisk/pull/5010
This one might be a bit more confusing.Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through!
I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. ...
Thanks for the method. PW
While catching up last night, I missed that you are not rooted.
unzip app-debug.apk lib*
adb push lib/YourDeviceArchitecture/* /data/local/tmp/
adb push boot.img /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*.so
/data/local/tmp/should be an empty directory.
PSA: MagiskHide of Magisk v23.0 no longer passes SafetyNet, even with BASIC evalType. Tested on my Pixel 4 XL running stock Android 12 with vanilla Magisk v23.0.
MagiskHide is *officially* dead. If you need any kind of root hiding, it's the perfect time to find alternatives.
There are already plenty of "root hiding" modules out there that I'm aware of, some even utilizing the latest features of Magisk canary.
I'm obligated to distance myself from any tamper detection circumvention, so I will not assist/promote any modules. Do your own research