Don't phone about True Phone Stub but your V4A version looks suspicious.
Yeah, as I said, you must set both to get setns (setns now doing the job faster etc instead of isolated). With setns but without isolated, nothing is working. PWWith or without setns I have no difference. For me only isolated works (hiding su from the path)
With setns but without isolated - su is visible again in the path
Sticking with isolated - it worked to me with all flavours and Magisk versions (of course, without Zygisk and with Riru)
Back to USNF 1.x series + MHPC Force Basic if affected by September Google server end changes.
As I wrote, isolated without setns works excellent, I never had any problem
I flashed the test2 USNF module and it still fails. I'm unsure what the September Google server end changes are. I have stable Android 12 and it worked fine with the previous canary without zygisk + Riru + latest USNF, Google Pay and everything worked.
Which app?Do anyone know what can trigger ART parameters are abnormal in momo?
I have one app that seem to detect root no matter what I do, so I temporarily moved over to magisk alpha to try and use old magisk hide, Riru and Riru-momohider. To try and make momo don't detect root and see if that fixed the app, before I start decompiling the app to figure out what sort of root detection it does.
Update: the cause for art parameters are abnormal, was lsposed. Disabled lsposed and now momo are happy. Didn't fix my other app though, so back to drawing board I guess.
View attachment 5442733
Fix for September changes was added to 2.x, so if affected 1.x series incl. test versions may actually be working, but you will need MHPC fix in addition to see results. PW
Generally, Riru cannot help you for SafetyNet. If you properly enabled Zygisk rebooted, Configured DenyList (GMS and GMS unstable), rebooted, you should pass SN.
If not, then you would need USNF and/or MHPC
As mentioned several times here, Riru is broken with Zygisk. And in your Canary, you need Zygisk for DenyList (hence for SN).
Therefore, if you really want Riru, you would need to switch to Alpha or Custom (many posts here how/where/what, etc) and use them as: Zygisk No, MagiskHide Yes (not the new DenyList)
And to avoid troubles when switching the Magisk flavour, better completely uninstall Magisk before you go
Well I didn't say you had a problem.As I wrote, isolated without setns works excellent, I never had any problem
However, with isolated + setns (or just setns) the phone looses fluidity
Hence again, for me setns does not bring any value, but brings troubles (isolated does not and makes the job)
Hence excellent, you can quote the author (I read myself, too), but setns is no use for me
Yup, it was a hurried / not fully considered reply.Thank you for your quick answer! I Just -mmmh - I am not on stock, I am running a Custom Rom; to flash all AP files means being forced to flash all the other stock rom files - as far as I understand the installation guide. Are you sure? I tried different apk and different zip - only the old magisk23 apk did finiish (direct method and patching img), no other apk did manage that. Maybe the attached logs are clearer than me to show the difference. I can get Magisk classic, AND i would like to understand WHY it fails to run everything POST-magisk classic
Freja eid, a Swedish application.
i'm on the latest alpha. i have only gravitybox module in lsposed v1.6.2 (6152). screenshots of my other modules are here. i added setns and initrc, so i have isolated+setns+initrc now. on the github page i read initrc config would 'hide' the modified traces of init.rc. but, magisk detector continues to show init.rc has been modified by Magisk.
Delete Cache and Data for Magisk Detector and test again - once it helped me, but only for a short timei'm on the latest alpha. i have only gravitybox module in lsposed v1.6.2 (6152). screenshots of my other modules are here. i added setns and initrc, so i have isolated+setns+initrc now. on the github page i read initrc config would 'hide' the modified traces of init.rc. but, magisk detector continues to show init.rc has been modified by Magisk.
thanks. had done all that before posting. and, i'm hoping @Eng.Raman would respond if he has a different take on this.
Are you using USNF 2.x? These need Riru to work, and that is disabled in recent TJW and vvb2060 builds if Zygisk is enabled due to conflicts arising from last changes to make Zygisk compatible with LSPosed.
Can I assume you are on Android 11 ATM? And did root with full data wipe & all image files as prescribed for Sammy devices?
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.
There are way too many people that update just for the sake of updating...
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