yashsingh1/xdaforums huggingface dataset:
[Magisk] dcarvil:
I'm not sure what you mean by "bootloop w/ clean A13 and standard flash on P2XL". I did a clean install of A13. It bootloops only with the Magisk patched image. I extracted boot.img from the same LOS ROM using payload_dumper.

I suspect it may have something to do with other changes in the unofficial version, so I will be going back to LOS 19.1 until the official version is released. There are other problems with this ROM, so it is not quite ready for prime time yet.

Thanks.
[Magisk] pndwal:
If a ROM cannot work properly w/ enforcing selinux today it has unresolved issues, possibly many, and should be considered only good for development purposes, not as a daily driver... Making ROMs available publicly w/ selinux permissive is a dubious practice anyway... Setting enforcing will reveal ROMs fundamental issues (bypassed by lax/no Linux security enforcement) as in your case...

Consider using a properly tested ROM to avoid issues and for your own security... I'd go with official LOS if available for your device (you didn't say device) of at least an ROM with Security-Enhanced Linux (SELinux)...

https://twitter.com/i/web/status/1359054108339040261

https://twitter.com/i/web/status/1318841119942168576

https://twitter.com/i/web/status/1318839675180625921

👀 PW
[Magisk] pndwal:
What you did... Clean install of A13 and patch/fastboot flash magisk-patched.boot.img from that...

... All good here...

Likely for the best...

Similar issues above... Hope your LOS 20.0 was selinux enforcing at least... 😬

Only the most privileged among us can have our choice of cake and eat it too! 🙂 PW
[Magisk] RubyRose:
Using an unofficial build on a Raspberry Pi 4 :D

I'm trying to make a "full" android out of it.

That is, these points cannot be corrected?
[Magisk] pndwal:
... So you're a bit of a geek then!?... Nice kit...

Android TV 13 comes to the Raspberry Pi 4 courtesy of unofficial LineageOS 20 ROM

Give your Pi a taste of Android TV.

www.xda-developers.com

... Is it PI 4B? This ROM?:

https://xdaforums.com/t/dev-rom-uno...3-for-raspberry-pi-4-b.4516545/#post-87752445

There will be reasons for these issues:

Not working:

Hardware video decoding & encoding (software decoding & encoding works, option to test highly experimental H.264 hardware video decoding)

Issues:

Camcorder (i.e. recording videos) & some third party camera apps don't work with official Pi camera modules (works with UVC USB webcams)

SELinux is in permissive mode

Encrypting userdata is not supported

and more…

as stated, and you should treat this as an experimental rom under development... For passing S/N and PI deviceIntegrity, enforcing selinux is going to break stuff (unless you can fix issues before dev does...

Seems you need to compromise for Android TV 13 currently and wait for fixes, or consider an older ROM w/ proper selinux / encryption working... 🙂 PW

Edit: Seems most Android ROMs for this are limited by selinix permissive mode... This article discusses hardware/other limitations for this experimental platform:

Developer ports Android 13 to the Raspberry Pi 4 B, Pi 400, and Compute Module 4

The Raspberry Pi 4 Model B, Pi 400, and the Compute Module 4 can now run Android 13, thanks to an unofficial port. Read on to know more!

www.xda-developers.com
[Magisk] RubyRose:
rpi4, bro. 8GB

I used exactly Android, not Android TV.

This ROM.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

konstakang.com

Is it possible for me to hide these errors in any way?

In principle, the necessary applications are launched for me. All other checkers go through. But still I would like to bring to the ideal.
[Magisk] pndwal:
Ah yes, you did say A11...

Well you've forced enforcing and seen some issues... You may not be able to do much better...

Re 'ART parameters are abnormal', I believe this got fixed w/ latest LSPosed (I don't have it now and made no edits)... If you're on latest LSP it may have a different cause... I'm not aware of how to fix the other Momo detections either, but it's rare to see a perfect result; I'd urge you use Momo only for comparison purposes when troubleshooting how to bypass detection for a specific app you need... Are you useing bank apps on the Raspberry?... Which apps polling integrity attestations do you need?

Others here may have suggestions, but one of the @KonstaT forums here on XDA will probably be your best bet... PW
[Magisk] RubyRose:
It's a pity.(

Yes, I'm using the latest version of lsposed, and I can't find system.prop. It simply doesn't exist.

In this topic, a person already wrote a similar problem. I have exactly the same.
[Magisk] zgfg:
New versions of Zygisk-LSPosed do not use system.prop anymore, instead all the props handling is in the Zygosk native so

You may try your luck with an older version of Zygisk-LSposed:

Releases · LSPosed/LSPosed

LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.

github.com

You could download the zips, unzip and find an older version that contained the system.prop file
[Magisk] huskydg:
No, it is handled by wrapper dex2oat binary
[Magisk] huskydg:
Afaik this problem is not caused by dalvik.vm.dex2oat-flags=--inline-max-code-units=0 only
[Magisk] martyfender:
Is this device or Android version dependent? On one of my Android 9 tablets with the latest, official, canary debug build, every time I install the latest test version of zygisk lsposed, a new, clean copy of system.prop file is created in the lsposed module folder. The latest version is 1.8.5-6656.
[Magisk] zgfg:
With Zygisk - LSPosed v1.8.5 (6649), I don't have system.prop in my /data/adb/modules/zygisk_lsposed

However, I see that there is a system.prop file in the installation archive Zygisk_-_LSPosed-v1.8.5(6649).zip, containing a single line:

dalvik.vm.dex2oat-flags=--inline-max-code-units=0

Also, the installation script customize.sh looks for the prop ro.maple.enable, if the prop exists with the value 1, it will be disabled by appending the system.prop:

if [ "$(grep_prop ro.maple.enable)" == "1" ] && [ "$FLAVOR" == "zygisk" ]; then

ui_print "- Add ro.maple.enable=0"

echo "ro.maple.enable=0" >> "$MODPATH/system.prop"

fi

However, I don't see anything else in the scripts to control wether the system.prop file will be kept in the /data/adb/modules/zygisk_lsposed folder or not

That must be controlled by the binary parts - to analyze the logic you would need to study the module's sources from GitHub - if available (frankly, I didn't search on GitHub, I automatically update the module when Magisk, Modules show that an Update is available)

See also the post/answer #2548 about the dex2oat wrapper (you will find in the module's bin subfolder)

Btw, you could check which of the two lines (or both) do you have in your system.prop:

dalvik.vm.dex2oat-flags=--inline-max-code-units=0

and/or

ro.maple.enable=0

The second line will be present only if you otherwise had

ro.maple.enable=1, but the logic behind the need of the first one (probably dependent on the Android version and so) should be in the sources for the module's binaries
[Magisk] patrickdrd:
no shamiko for android 7 nougat?

it says only android 8.1+?

what can I do?

edit: I would also need lsposed zygisk (also not supported :( )

edit2: it seems I can't use lsposed, since it's 8.1+, so what should I do?

ditch zugisk and use xposed as before? or use zygisk but then what about shamiko?
[Magisk] samhhmobil:
You should downgrade, if you use a 5years old Android version.

For Android 7.x you should use Magisk not newer as 23.x (maybe even older)...

samhhmobil
[Magisk] zgfg:
Consider Magisk Delta - with Delta you don't need Shamiko (you will use Zygosk + MagiskHide)

However, there maybe other modules you may need, like LSPosed (same devs like Shamiko) that are also limited to the newer versions of Android
[Magisk] pndwal:
Why?... PW
[Magisk] samhhmobil:
Because... it runs stable and without issues with that (best is IMHO to combine software of same generation).
[Magisk] flaystus:
Kind of a stupid question probably but I just rooted my phone with Magisk / Zygisk and I'm wondering if I'd make anything NOT work if I just black listed every app including system stuff then only "unblacklisted" the few things I want to have root access.

Basically I'd prefer a white list but short of that will I break anything if I just whole sale black list?
[Magisk] pndwal:
John supported A4.2 till 23.0 when he bumped support to 5.0 due to difficulties supporting earlier versions...

We still have 5.0 support... I haven't seen reports/indications of instability w/ 24+... Are there any? (Usually later versions fix bugs and are more stable, not less)... PW
[Magisk] patrickdrd:
well ok but oddly magisk 23 fails to pass any safetynet tests,

while it passes both with magisk 25.2 :rolleyes:

edit: I even updated my device to android 9 which is the latest it got,

but I still failed to make outlook work (posted on another thread as well),

so I though to give 7.1 a try
[Magisk] pndwal:
Were you using Zygisk USNF module?; Won't be working w/ 23.0... Also, you'll need to toggle MagiskHide on (and use Riru/Riru_USNF etc)... PW
[Magisk] patrickdrd:
no, I didn't, it isn't available for 23 anyway I think
[Magisk] pndwal:
I meant 'were you using' as in before you downgraded... Also I've added to last post... PW
[Magisk] prokiller1199:
Getting black screen on latest v1.7.86 of this app. Suspect is new detection mechanism. Anyone can test?

Touch 'n Go eWallet - Apps on Google Play

Spend, Save, Earn, and Invest conveniently - all in one app!

play.google.com

Before this version is fine (v1.7.84). Pass safetynet, Shamiko, Added to deny list it just wont work on latest version.

Pixel 6 Pro Latest Nov patch, Magisk 25.2
[Magisk] 73sydney:
ill have a crack, also Pixel 6 Pro, though on A13

Update:

No bueno...even with Hide My Applist

Perhaps a Magisk Delta user will test for you.....
[Magisk] pupido:
A few years ago I installed Magisk v. 22 on my Note 9 (Android 10). Today I tried, using Magisk Manager, to update both the app and Magisk to the latest version (via direct installation).

However, while the app updated to v. 25.2, instead, Magisk updated to v. 23. Is this normal?

I thought Magisk would also update to v. 25.2 just like Magisk Manager.
[Magisk] zgfg:
It's not normal but there are SO MANY differences in Magisk v25 (starting with v24) compared to your old v22 or v23) that I really suggest you:

- search on XDA for Magisk Zygisk thread and carefully read OP posts to be aware what has changed, and what would you need to configure manually from scratch , etc

- since you have happily lived so far with that ancient Magisk v22, maybe you don't need to jump to all the new things (Zygosk, DenyList instead of MagiskHide, no more Modules repository, optional Shamiko, USNF, Hide My Apps), and/or maybe you have an old version of Android that Magisk or important new modules (Shamiko, LSPosed) will not support
[Magisk] pupido:
Thank you for your response.

I am interested in installing the Pixelify's module and I think with Magisk v. 23 it is not possible.
[Magisk] Mr.Jlu:
Hello Guys,

[UPDATE]

I was able to bypass the root detection of this app using the following magisk module but it stopped working post reboot.

Magisk Module Name:

InitRcHider

Reference URL:

https://xdaforums.com/t/module-initrchider.4369285/

XDA Download Link:

https://xdaforums.com/attachments/initrchider-zip.5472273/
[Magisk] prokiller1199:
Thank you for your effort, at least I know that its not my problem
[Magisk] Eagleman71:
FYI what to do post Android Security Update if wallet stops working (I don't know if someone else already wrote it or if it is so obvious that nobody needed to, LOL).

My Case:

Xiaomi MI 11 Ultra, Magisk 25.2 (33) installed and working. Banking apps and Wallet working.

Updates to new version with latest Android Security Patch.

Banking apps and Wallet NOT working anymore.

Just patch the new version of the boot.img, reflash and check once again the DenyList because sometimes some goolge servicer gets unflagged.

Al back to normal.
[Magisk] anubisjack:
Fellow Malaysian here, and also before this new update, there are error code keep popping up, u notice? Like not even 1 second then it closed, maybe that was the detection mechanism but its not working yet, I installed the previous version of it for it to work temporary lol
[Magisk] prokiller1199:
Hey, u mean the stopped working dialog that appears and gone in seconds right. I solved that one by hiding all process in denylist, if not mistaken by default it only tick the first one.
[Magisk] anubisjack:
My one still popping out even tho I alredi deny all the processes lol, even game like undecember still detected the root even I hide it also
[Magisk] prokiller1199:
fine here
[Magisk] anubisjack:
I only can hide it with shamiko, was on normal zygisk previously
[Magisk] prokiller1199:
I am on shamiko too, maybe they strengthen their security.
[Magisk] pndwal:
Still haven't been able to do this on Xiaomi RN8T... Please say your device / OS... Thanks, PW
[Magisk] ajlir:
Model: Xiaomi Mi A1 (tissot)

OS: Lineage (19-20221206-NIGHTLY-tissot)

Magisk version: 25.2

Magisk Modules:

Advanced Charging Controller (ACC)

Shamiko

Systemless Hosts

Universal SafetyNet Fix (Displax)

Zygisk - LSPosed

LSPosed Module: Hide My Applist

Tested with Ruru and Momo (attached)

Not working with TnG ewallet (stuck at logo)

Will find resolution on Momo's findings and update here.

After reading through last 4-5 pages, I do not see anyone with my issues with Momo detection.

I'll keep looking in the meantime but can I get someone to help me on this, please?
[Magisk] prokiller1199:
Another TNG user here, I submitted a report to their developer team because I think it is app issues on latest version of TNG.
[Magisk] anubisjack:
I have just recently came across shamiko since undecember, sword art online VS, TnG being detected, previously the old magisk hide and zygisk had no problem for me
[Magisk] xabu:
Lollipop or Android 5 is not supported and it's a wonder that you have Zygisk enabled and running.
[Magisk] Umbardacil:
Hi again

Although I'm passing secure net:

Google pay detects root on my phone:

What am i missing here? Please help 🆘 🙏

Lucas
[Magisk] Slim2none4u:
Clear cache of apps detecting root and reboot
[Magisk] Umbardacil:
Ok. Now it doesn't show that monit anymore, instead it says:"not configured"(yes NFC is on)

Edit: intune and any work app which was working with Magisk hide now detects root. Is there a way to revert to old Magisk with Magisk hide?

Great improvement, this new Magisk... I guess Google money makes the difference, huh?
[Magisk] mingkee:
Is this app in Deny List and enforce it?

Make sure you reboot the phone after updated
[Magisk] LuisCarlosHK:
I am using oneplus 5 with LineageOS 18.1. After I updated Magisk to 24.1, the previous way to bypass root detection (riru + LSPOSED + Hide myapplist) is no longer working for HSBC HK app (the app crash immediately). I tried remove all module and magisk, the app (HSBC HK) wouldn't crash and not root detection was shown but other apps (Pulse) got root detection warning. This app (Pulse) can use Zygisk with denylist. I heard someone use Zygisk + Shamiko can bypass root detection, but I still got detected by HSBC HK app. Anyone know how to bypass the root detection? I tried to run safetynet test and the result is both fail. I install the universal safetynet fix again, can pass safetynet but HSBC HK still root detected.
[Magisk] pndwal:
Perhaps Magisk main GitHub page could word it better, but support starts with 5.0, so 5.0 Lemon Meringue Pie (Lollipop) is supported.

Support for 4.4W.2 Key Lime Pie (KitKat) and earlier was removed w/ 23.0

• [General] Remove all pre Android 5.0 support

(see v23.0 release notes).

👀 PW
[Magisk] dohanin:
try freezing the magisk app (or uninstall it) before opening your bank app
[Magisk] LuisCarlosHK:
Which frozen app you would prefer?
[Magisk] pndwal:
Wondering if this may be a proper fix for your issue?

Make sure busybox can be executed recursively …

Busybox will execute itself. On some older Samsung devices, when it is located in /data, it will not have rights to execute other programs including itself. We should also relocate busybox in this case to workaround Samsung bull****.

See topjohnwu/ndk-busybox@bdc8655

Fix the "app doesn't detect installed Magisk" issue in #4174

canyie authored and topjohnwu committed 7 hours ago

Looks like we will finally see a proper fix for longstanding "Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices #4174" however! 🥳🎊👏

This has prevented a number w/ older armeabi-v7a devices from using newer Magisk.

Many thanks to @MartK87 for his dogged persistence, downdrading OS to test / supply needed logs etc, and to Canyie for her persistent efforts with this since October! - Many users will be grateful. 👍

Gotta love Open Source; brings out the best.

🙂 PW
[Magisk] HippoMan:
Thank you very much!

I went to the Bromite site, but I can't find this zip for the system app that you mentioned. Where can we find this zip file?
[Magisk] dohanin:
if u already have apps like swift backup, titanium backup, etc., simply use it or just run a shell command "pm disable-user <magisk_package_name>" through adb or termux.

since i use tasker, i automated this shell command
[Magisk] LuisCarlosHK:
I use Airfrozen and it works.
[Magisk] nacos:
Follow the embedded link above and download the Webview Manager's last version, as seen in the screenshot.
[Magisk] HippoMan:
Thank you! So now I understand that the zip file that you referred to is the WebView zip.
[Magisk] nacos:
Yes, that is correct. So is the apk file I also provided a link for (you need to download the WebView apk for your phone). Then follow the instructions.

They are basically the same application, however the system Bromite WebView can only be installed either by flashing it as a zip file in Magisk, or through the Magisk WebView manager (which is a Magisk module, a little trickier to work with). Lastly, install the apk on top of the system application.
[Magisk] dohanin:
anyone can help me out here?
[Magisk] HippoMan:
Thank you. I'll try downloading that zip file again a little later. At the moment, I keep getting the following from that site:

success	"false"
version	"ca43faad"
error
code	429
message	"Too Many Requests"

This is probably the same issue that others have been reporting about downloading problems with various SafetyNet checkers ... lots of people want these items and download limits get exceeded. But I'll be patient.

This latest WebView Manager zip file on the GitHub site is version 10.3.2. Do you see any downside to installing the earlier 10.1.2 version via Magisk? That one is the November 21 version.

PS: Never mind! I tried a 4th time, and this time I finally got 10.3.2.

Patience is a virtue!
[Magisk] HippoMan:
And now, after having installed the latest WebView and then Bromite on top of it, my banking app indeed has lost sight of the fact that my device is rooted!

Thank you again, @nacos, for this very useful suggestion about WebView/Bromite!

I'm not going to name my bank nor the specific banking-app features which previously were blocked but which are now accessible on my rooted device. I don't want to make it any more likely that someone working at that bank who might be reading this thread would recognize the bank and the app and then feel motivated to go back and try to "improve" (ha ha!) the app to override the root-hiding-and-Magisk-hiding capabilities of WebView/Bromite.
[Magisk] toejam119:
How are the prop values when you open MagiskHide Props Config? If you see any as "(enabled, not active)", the guide says you have to activate them.

See more info about props here (post #7 of this thread): https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86320349

edit: the guide doesn't tell you but you have to type "su" (without quotation marks) in the terminal app (such as Termux) in order to get the root privileges.

Also if you run Oprek Root Detector, does all sections pass and show green check? (you must add the app to the Denylist)

https://play.google.com/store/apps/details?id=com.godevelopers.OprekCek
[Magisk] prokiller1199:
I've been using shamiko for quite sometime but only TNG is breaking recently. Before that I need to use for my PBe and RHB app and had to uninstall magisk app for it to work
[Magisk] ajlir:
I have asked my colleagues on this and they have no problems (unrooted).

I'm not giving up yet.
[Magisk] anubisjack:
Oh, didnt know public and rhb so strict, cimb and maybank got no problem just using normal hide
[Magisk] prokiller1199:
oh ****t rip

yeah damn strict, and yes my cimb and Maybank very easy bypass
[Magisk] ajlir:
I actually tried with this version just now (apkmirror, pls don't bonk me) and it actually works. And let's just say that I'll never update this app again until it breaks.
[Magisk] prokiller1199:
Yes, I personally tested it and using it now. So the new one is hating root.
[Magisk] Mr.Jlu:
Hello @pndwal,

Device:

Nord

Model:

AC2001

Brand:

OnePlus

Android:

11

ROM:

[11.0.0_r46] AospExtended ROM v8.7 [OFFICIAL]

In my previous post, I mentioned that it only worked once, then stopped after a reboot.

As a result, I had a few sleepless nights over the weekend. I wanted to understand how the app could detect this. Finally this afternoon, I was able to bypass the detection.

My next post will describe the steps I followed because in this post your question was related to my device specifications.
[Magisk] Mr.Jlu:
Hello Guys,

I am back again. Finally, I found a way to bypass this app detection. My day was made after achieving this :giggle:.

Spoiler content hidden.

Spoiler content hidden.

Hello @73sydney ,

The above steps can be included in your guide if you wish.
[Magisk] click2abubakar:
I've a Galaxy S7 edge on latest stock firmware. Latest TWRP installed & rooted with Magisk 25.2.

Can't enable Zygisk (already tried rebooting multiple times)

Tried the latest Canary but same result, tried turning off Zygisk, re-enabling, rebooting but no luck.

Any help would be greatly appreciated in this regard.

Thanks.
[Magisk] 73sydney:
I would think whitelist mode would be the longest way around the issue, its been tested and working in blacklist mode, which requires selecting just the app and applying the root template to hide it from all the root related apps

If youre unable to pass it this way, assuming you have HMA setup as the guide suggests, then by all means let me know and ill consider adding it, but id rather not start adding one off solutions using a completely opposite mode (whitelist) which might only add to confusion, if the prescribed blacklist mode works

Also is MagiskHide Props Config needed?, if using Displaxs USNF mod 2.0 generally it shouldnt be required
[Magisk] m0han:
v3.0.6 is released

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/post-87847359

Says: No longer need the Magisk module, make sure to uninstall it, or you will bootloop
[Magisk] pndwal:
Re. Galaxy S7 Edge:

So you'll need custom, ported, fixed or newer Kernel; please check kernel version in use and read this pinned issue:

[Wontfix] Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) #5395

Basically, Zygisk was not turning in for S8 and earlier Sammy phones:

https://github.com/topjohnwu/Magisk/issues/5353

The issue was fixed here (by Shana) for most:

https://github.com/topjohnwu/Magisk/pull/5372

Merged:

https://github.com/topjohnwu/Magisk/commit/ff7ac582f013dbc27b27e4194424044ee79c3980

This fix worked around broken system calls (due to kernel restriction / exec limitation), but requires fexecve, and unfortunately this doesn't exist in 3.19- kernels. 😕

Nb. Some devices w/ 3.19- kernels successfully load Zygisk without fexecve workaround. As Canyie said there:

Nb. I see this was fixed in LOS 18.1+ using 3.18.140 kernel... Could be a good choice...

- https://github.com/topjohnwu/Magisk/issues/5395#issuecomment-1073746347

👀 PW