[Discussion] Magisk - The Age of Zygisk.

[pndwal]

I'm not sure what you mean by "bootloop w/ clean A13 and standard flash on P2XL".

What you did... Clean install of A13 and patch/fastboot flash magisk-patched.boot.img from that...

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.

... All good here...

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.

Likely for the best...

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

There are other problems with this ROM, so it is not quite ready for prime time yet.

Thanks.

Only the most privileged among us can have our choice of cake and eat it too! PW

 

[RubyRose]

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)...

Using an unofficial build on a Raspberry Pi 4
I'm trying to make a "full" android out of it.
That is, these points cannot be corrected?

 

[pndwal]

Using an unofficial build on a Raspberry Pi 4
I'm trying to make a "full" android out of it.
That is, these points cannot be corrected?

... 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://forum.xda-developers.com/t/...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

 

[RubyRose]

Is it PI 4B? This ROM?:


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

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.

 

[pndwal]

rpi4, bro. 8GB
I used exactly Android, not Android TV.
This ROM.
https://konstakang.com/devices/rpi4/LineageOS18/

Ah yes, you did say A11...

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.

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

 

[RubyRose]

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

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.

 

[zgfg]

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.

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

 

[huskydg]

New versions of Zygisk-LSPosed do not use system.prop anymore, instead all the props handling is in the Zygosk native so

No, it is handled by wrapper dex2oat binary

 

[huskydg]

Re 'ART parameters are abnormal', I believe this got fixed w/ latest LSPosed (I don't have it now and made no edits)...

Afaik this problem is not caused by dalvik.vm.dex2oat-flags=--inline-max-code-units=0 only

 

[martyfender]

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

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.

 

[zgfg]

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.

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

 

[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?

 

[samhhmobil]

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?

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

 

[zgfg]

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?

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

 

[pndwal]

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

Why?... PW

 

[samhhmobil]

Why?... PW

Because... it runs stable and without issues with that (best is IMHO to combine software of same generation).

 

[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?

 

[pndwal]

Because... it runs stable and without issues with that (best is IMHO to combine software of same generation).

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

 

[patrickdrd]

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

well ok but oddly magisk 23 fails to pass any safetynet tests,
while it passes both with magisk 25.2

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

 

[pndwal]

well ok but oddly magisk 23 fails to pass any safetynet tests,
while it passes both with magisk 25.2

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

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