yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
No! (except possibly benefits of having boot to both system with root and system without it mentioned in following posts)... Booting system via recovery is also quite awkward ...

This mode was provided because most devices with no OEM ramdisk (A only legacy SAR) cannot support an added one, so there is no other option for running Magisk since it always resides in a ramdisk... John calls this "The worst type of device to ever exist as far as Magisk is concerned".

https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

Fortunately for you:

"Some Type III devices’ bootloader will still accept and provide initramfs that was manually added to the boot image to the kernel (e.g. some [actually all(?) or most] Xiaomi phones), but many device don’t (e.g. Samsung S10, Note 10). It solely depends on how the OEM implements its bootloader."...

Recovery mode is simply for installing it to ramdisk in recovery partition and Magisk app toggle signals system to reboot via recovery, patch recovery.img instead of boot.img when taking Direct Install etc... PW
[Magisk] pndwal:
This is correct... Normal bootup will boot system without Magisk, and this may have some limited-use benefits... PW
[Magisk] zgfg:
Not unless you want the following:

- Normal booting will boot to Android without Magisk

- Booting through Recovery (Vol+ & Power) to boot into Android with Magisk

Usually, it is not practical

Also, you may probably have troubles with OTA
[Magisk] Tech = Spy-Biz:
:LOL::ROFLMAO: So trueeeeeeeeeee.

NVM 450 services inside Play Services alone ..each a gem! As stated by Ed Snowden on Utube- Guugle does a brilliant job of shielding its users from others but guugle itself collects, analyses & sells private info on its users for ad revenue, and so does Appel and many others. Thats how they got so rich & powerful so fast. (sorry,off-topic though but living with the pain u knw)

@pndwal said:

Me replied :

:LOL::ROFLMAO: As a kid I was too young & naive to not realize that my parents were actually spying on me & even selling my data to AdMob , AdSense, Pentgon & agencies. Where did all that Ad money they received go? I didn't get any of if in the "Will" they left behind. My parents can't be so evil .:LOL::ROFLMAO:
[Magisk] pndwal:
Yup, your parents held your hand and spied on you but weren't (necessarily) evil. 😜...

Wadiya spect Tech = Spy-biz? 😁 PW
[Magisk] pndwal:
Not just zoomers... the olds too... at least the Googlers...

... well maybe I took some license with this. 😁 ... Here you go:

https://source.android.com/docs/core/architecture/kernel/generic-kernel-image 😛 PW
[Magisk] pndwal:
... But seriously, Magisk prepared for GKI (Generic Kernel Image) 2.0 w/ v 25.0:

[MagiskInit] Support Android 13 GKIs (Pixel 6)

- this:

Support GKIs without ramdisk …

Fix #5819

topjohnwu committed on 12 May

This is because

So users of Pixel 7(?) and future devices launching w/ A13+ will need to patch / flash new init_boot.img for Magisk installation instead of boot.img per vvb2060's note (Translated):

https://t.me/magiskalpha/530

Nb. Updated devices can use ramdisk in original boot partitions as per John's fix for Pixel 6...

👀 PW
[Magisk] zgfg:
Putting that simple, it probably means that if on A13 and higher init_boot img exists - patch the init_boot; otherwise patch the boot (or recovery) img as usual

I didn't check the doc - on a/b devices should there be again init_boot_a and init_boot_b?
[Magisk] CSX321:
Bit confused by that. There's no init_boot.img in the Pixel 6 Android 13 zip. When I updated mine yesterday, I just extracted and patched boot.img as always, and everything seems normal.
[Magisk] zgfg:
"Launching with" actually means future devices that will be initially launched with A13

IMO, as that it could not refer to Pixel 6 if it was originally launched with A12

That was a similar case with eg FBE - mandatory for devices launched with A10+, not those launched with A9- and just upgraded to A10
[Magisk] pndwal:
Correct.

I believe 1st stage init will still require a ramdisk for each slot so that is assumed. Pixel 7 series users may confirm this later...

Vv's statement is clearly refering to new partitioning for devices launched with A13 so the latter part (re non-manual patching) "... if not, then extract the boot.img" is ambiguous to me... Something lost in translation? Statement not properly thought through (like my edited one above 😬)? PW
[Magisk] pndwal:
Yes; Sorry! - I edited my remark!

It was based on John's release note:

v 25.0:

[MagiskInit] Support Android 13 GKIs (Pixel 6)

which was connected with:

- this:

Support GKIs without ramdisk …

Fix #5819

I initially assumed the fix meant p6 had the new init_boot image scheme, but it actually lacked ramdisk in boot.img due to this being moved to new vendor_boot!

John's chosen fix actually involved recreating ramdisk in boot.img for magisk.init. This:

So this fix actually allows implementations of Android 13 GKIs for updated devices (Pixel 6 etc) to work...

vv's note however, preempts Android 13 release devices, ie. Pixel 7+... 😬 🤪 PW
[Magisk] ipdev:
Same as you.

I am waiting for the new official release. 🙃

Is Hide-My-Applist actually shifting to Zygisk. :unsure:

ZygoteArgsHook for Android 11+

Cheers. :cowboy:

PS.

One of these days I will look up the tg channel. 😛
[Magisk] pndwal:
It's an LSPosed module... Already using Zygisk XHook (or Riru) ain't it? 😛

... Commit adds this:

Experimental
name="settings_force_mount_data">Force bind mount data storage for apps whose target API lower than 30
name="settings_force_mount_data_summary">This option is only available on Android 11 and above

and updates hidemyapplist.xposed.hook files etc. 😛 PW
[Magisk] traversone:
good evening all,

on a previously rooted mobile (now fully unrooted) the TB Checker app detects many errors in "Syscall FIle Detection" section. How to get rid of these errors? Thank you
[Magisk] 73sydney:
I actually caved in and tried it (the early version already posted), and thank god theres no save button anymore for one noticeable change....hands up who edited a list and forgot to hit save and had to go back and do it, and did that almost every time they added something (me too). I tested it using lsposed-riru under Magisk Delta....

In other unrelated news i just manually updated my S20+ 5G and for some reason, its decided i have a special purple edition S20+ 5G (i dont) and so its added a purple theme and links to BTS (Korean boy pop group) extras, imagine how thrilled i am about that as a 51yo male who hates any kind of pop music. I imagine its a thrill level shared by XDA mods when i decided to un-retire from posting here. They only have themselves to blame as one who likes to troll me whined about my signature saying "largely retired", easily fixed...now unretired and Powered by Ponkle and here much more:)
[Magisk] Stillhard:
You were and are ARMY!
[Magisk] m0han:
@73sydney,
[Magisk] pleiotropy:
Hi, I am currently on Canary 24.3 on Android 12, could someone tell me the best way to switch to Magisk Stable 25.2?
[Magisk] zgfg:
Generally, the following should work (if you are already on the new Magisk v24.3 with Zygisk, DenyList, corresponding modules, etc):

- Magisk app, Settings, Restore Magisk app (if you previously did Hide Magisk app - ie, If it shows that option)

- Magisk app, Settings, Update channel, switch from Canary to Stable

- Magisk app, first page, Update Magisk APP (it's second block)

- Magisk app, first page, Update (Magisk itself - first block), choose Direct method and then reboot

If you need then do Hide Magisk app

You should have then latest Magisk Stable, but keeping the same configuration (Zygisk, DenyList, modules) as you previously had with Canary 24.3

If you need to update modules (like installing USNF 2.3.1-mod by Displax) - that is not part of 'updating Magisk'.

Do it afterwards
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (4737c511) (25202)​

[General] Fix minor bug in module files mounting implementation

[MagiskPolicy] Fix minor bug in command line argument parsing

[Zygisk] Prevent crashing daemon in error

[Zygisk] Rewrite zygote code injection with new loader library approach

Diffs to v25.2​

[General] Fix minor bug in module files mounting implementation

[MagiskPolicy] Fix minor bug in command line argument parsing

[Zygisk] Prevent crashing daemon in error

[Zygisk] Rewrite zygote code injection with new loader library approach

https://github.com/topjohnwu/magisk-files/blob/16199d457212125951772aa73673fb0e1afcb06b/notes.md

👍 PW
[Magisk] scootley:
Hi,

Pixel 5 running Android 12 SQ3A.220705.003.A1. Trying to go from stock to vanilla root using Magisk Canary (25202).

Patched stock boot image just fine.

I am trying to just do a temporary root for a single boot using "fastboot boot ..."

Has worked fine many times in the past.

But after fastboot, it seems to try to boot, shows the Google logo, and then shuts down and is charging and showing the percentage charged.

fastboot -v boot magisk_patched-25202_eIqnE.img
Sending 'boot.img' (98304 KB) OKAY [ 2.688s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 1.560s]
Finished. Total time: 4.321s

Any ideas?

Update: Actually I just got it to boot. Same exact patched image as originally. All I did was pull the USB cable out of the phone right after fastboot completed (was using Linux)

Thanks
[Magisk] pndwal:
Didn't take any OTA since downloaded the ROM for boot.img? PW
[Magisk] scootley:
Actually I just got it to boot. Same exact patched image as originally. All I did was pull the USB cable out of the phone right after fastboot completed (was using Linux)
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (38ab6858) (25203)​

Update app to target API 33

Diffs to v25.2​

[General] Fix minor bug in module files mounting implementation

[MagiskPolicy] Fix minor bug in command line argument parsing

[Zygisk] Prevent crashing daemon in error

[Zygisk] Rewrite zygote code injection with new loader library approach

https://github.com/topjohnwu/magisk-files/blob/51c0843433aa90de75eafbe4e441a00ef94c5cb4/notes.md

👍 PW
[Magisk] pndwal:
Nb. • Update app to target API 33 = Adapt to Android 13. 😉 PW
[Magisk] Erfirya:
Hey just wanna ask. If I update magisk, do I have to reinstall the modules I've previously installed? Or will it remain installed on my device? Btw I'm using Magisk v25.2
[Magisk] BillGoss:
They happily survive an update.
[Magisk] Erfirya:
Oh that's good to know. Thanks
[Magisk] BillGoss:
And you don't need to reply just to thank someone. Simply tap the "Like" button on their reply.

This avoids filling up threads with "thank you" posts. 😊
[Magisk] zgfg:
Stressful experience:

https://xdaforums.com/t/bootloop-fastboot-stock-phone-locked-for-security-reason-xiaomi-eu.4484255/

The problem should have not been caused by Magisk (SAR is read-only, hence when booting without Magisk in boot.img, all changes by Magisk and its modules are reverted back to stock)

Maybe related to custom Recovery (but I was successfully running the same for months)

However, and that's for sure, the unlocked Bootloader saved my phone/ass
[Magisk] zgfg:
Settings, Security Status - do you see both Security Patch level and Google Play System Update?

And can you check System Update, and does it show correctly/normaly?

I was noted by s friend, I checked and by surprise found that Security Patch level was no more displayed there (usually it did)

Even worse, Google Systems Update told me that my phone (less than a year old) will no more receive updates. More/Help pointed to a Google page about Pixel

I was worried is it due to spoofing Pixel for CTS/SafetyNet/PlayIntegrity

Fortunately, it was not the cause - problem with a particular Google Play Store app version 31.9.13 or so

Found more info on AndroidHilfe forum

Updated Google Play Store app to 32.0.20 and now is ok, as on the screenshots
[Magisk] m0han:
Stock rom? That apart, Play Store says the app is up-to-date and the device is certified, but the version is 31.9.13.xxxx. How could that be?
[Magisk] zgfg:
My post was not about Device Certified or not (Certified should be immediately when passing SafetyNet)

But about the availability of future Google Play System Updates - don't know where is that in your ROM, my screenshot was from stock MIUI (Xiaomi)
[Magisk] m0han:
ok. i responded seeing the above, 'cos that's the version of play store i have.
[Magisk] zgfg:
Version of Playstore does not affect(ed) Device Certified

But do you have any setting about Google Play Device System updates - can you clock there for the newer update, and does it (not) fail you telling that your phone will no more receive (and then, if you have More button, would it display something about the old Pixel or so)

That was the problem I posted that I had with a particular Google Play store version (I'm not sure which version I had, I updated Playstore this morning to fix that problem)
[Magisk] m0han:
yeah. afaics, my rom does not have 'setting about Google Play Device System updates'. and, i can't get the v32.x.xxxxx update, which is strange(?).

Spoiler content hidden.
[Magisk] zgfg:
To update Google Play Store (or Services) you need to download APKM files (so-called split or bundle installations) from ApkMirror, and to install them by SAI (Open Source) or ApkMirror Installer.

They cannot be updated from the Play Store itself - by an action from a user

Playstore will (sooner or later) update itself (for me, on the other phone it already did, to the same v32.0.20)

To prevent anybody from commenting about ApkMirror blah, blah, blah - ApkMirror has official installations (not hacked, not with viruses or whatever) and bundle/APK split installation technology is also an official from Google (many apps on Playstore install from the bundle/split but user usually cannot see since the installation from Playstore goes seamlessly for the user)
[Magisk] m0han:
:) My time is gonna come. I'll wait.
[Magisk] samhhmobil:
Open PlayStore ==> select "Settings" ==> select "About" ==> scroll down to "Play Store Version" ==> tap on "Update Play Store" directly below, and it will do the update immediatly and silently in the background.
[Magisk] starbucks2010:
Hello good people,

I'm trying my luck here hoping that someone more knowledgeable with magisk can give me a hint about my issue.

I succeed to build a Samsung S22 Ultra (S908B) rom with f2fs rw partitions (stock rom has locked ro dynamic partitions) but it boots only on permissive kernel patched with magisk 24.3, more precisely 24301. I mention that it boots ok but zygisk cannot be activated. (activation ok in magisk app settings but it says Zygisk = No on magisk app home page)

As soon I update and patch the kernel with a higher version of magisk, the phone bootloops. Tried all v24 and v25 magisk versions and it bootloops on any version higher than 24301.

Here are the differences between magisk 24301 (boots ok) and 24302 (bootloop).

Diffs 24301 --> 24302

- Support multiple CPIO concatenated

- Use /data as tmpfs mount point in 2SI setup

- Cleanup inheritance

- Introduce new sepolicy injection mechanism

- Add hijack sepolicy support for rootfs devices

- Remove unused code

- Reorganize magiskinit code

- Fix #5589 (WARNING: linker: su unsupported flags DT_FLAGS_1=0x8000001 after typing su on terminal emulator)

- Log if failed to dlopen a zygisk module

- Use standalone magiskpolicy

- Make magiskinit not magiskpolicy

- SAR can also have monolithic sepolicy

- Also hijack plat_file_contexts if necessary

PS. On stock rooted rom magisk update to v24 and v25 is ok but all partitions are ro. Although it still need permissive kernel to boot.

Thank you in advance for any hint/advice.
[Magisk] pndwal:
... Shouldn't need permissive for stock Sammy ROM...

Can't give a lot of technical advice on your ROM build except to say you're probably going about this the hard way...

There are already Super Image tools available to 'Universally Mount System read write for Android 10+ ROM w/ SUPER or NO_SUPER' partitions / extract or make partitions RW in super partition... See this:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86243253

👀 PW
[Magisk] pndwal:
FWIW, I found older info I posted in addition to link above re. problems getting r/w /system at least w/ stock Android 10 or later any more due to shared blocks implementation:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85049195

... and re. Magic Mount, the new way to 'write' to /system w/ Magisk systemlessly.

Of course you can rebuild whole filesystem to overcome OEMs locking /system to read only (by using an automated bash script by XDA member @lebigmac to "Universally Mount System read write"... BUT (big but), you MUST be adventurous / maverick / a 'Power User' / know your stuff) as mentioned,

but you should be able to make just about any needed changes to /system systemlessly using Magisk

without the myriad issues/pitfalls inherent in R/W mounted /system

... Of course for simple property manipulation @Didgeridoohan's MagiskHide Props Config module is probably all you need, but you can overlay /system (hence Magisk description 'The Magic Mask for Android') with just about any files / code using Magisk Tools provided.

Interestingly, the link following refers to how John Wu has even overlayed a stock system with an entire custom ROM as Proof of Concept for a projected Universal MultiROM (Magisk powered custom ROM)... Unfortunately he didn't take that much further...

I posted (earlier) info on these two methods here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84859571

🤠 PW
[Magisk] starbucks2010:
Thank you very much for the reply but would be more interesting to find out what change in magisk 24302 is blocking my system to boot.
[Magisk] pndwal:
Appart from this:

between March 10 and March 18 Magisk underwent some major refactoring. You could have found these changes by searching commits between these dates (ie. between 24301 and 24302), but since a few are significant I'll enumerate them:

Several could be affecting your mileage, but as part of a move away from patching fstab in 2SI devices (completed in June with major refactoring of magiskinit injection) is this change in traditional mount point:

- Use /data as tmpfs mount point in 2SI setup…

Design credit to @yujincheng08

[*]Close #5146. Fix #5491, fix #3752

Previously, Magisk changes the mount point from /system to /system_root by patching fstab to prevent the original init from changing root. The reason why we want to prevent the original init from switching the root directory is because it will then be read-only, making patching and injecting magiskinit into the boot chain difficult.

This commit (ab)uses the fact that the /data folder will never be part of early mount (because it is handled very late in the boot by vold), so that we can use it as the mount point of tmpfs to store files.

Some advantages of this method:

- No need to switch root manually

- No need to modify fstab, which significantly improves compatibility e.g. avoid hacks for weird devices like those using oplus.fstab, and avoid hacking init to bypass fstab in device trees

- Supports skip_mount.cfg

- Support DSU

topjohnwu committed on 13 Mar

This is your obvious culprit, but there were also major changes in sepolicy and magiskinit code including:

-

Introduce new sepolicy injection mechanism

(check notes here)

- Reorganize magiskinit code

- Use standalone magiskpolicy

- Make magiskinit not magiskpolicy

- SAR can also have monolithic sepolicy

- Also hijack plat_file_contexts if necessary

(check notes here)

Spoiler content hidden.

🙃 PW
[Magisk] pndwal:
Finally were getting

Make stub patching 100% offline

topjohnwu committed 2 days ago

👍🎉 !

This means my shut-down issue for broken Hide the Magisk app function (where user doesn't update) after one or more updates are available (due to json pointing to latest & often incompatible stub) should be fixed, at least going forward...

My issue re. json calling incompatible stub (due to this being configured to call latest updates only) was previously closed with the comment 'old builds are not supported '

Nb. Proper custom channel json selection or disabling network will still be needed when selecting Hide the Magisk app in many older builds...

👍 PW
[Magisk] andrea0807:
if I want to patch the boot.img file with magisk and then flash it from recovery twrp, what should I choose in the options: "fix vbmeta in the boot image" or "recovery mode"?
[Magisk] zgfg:
Boot img corresponds to Boot partition, not to Recovery.

And when patching, you must not check Recovery if using boot.img

For vbmeta please check GitHub Magisk Documentation (usually you don't need playing with vbmeta- BUT it depends on your Device and ROM)
[Magisk] KaKi87:
Hello,

After peforming a clean install of crDroid v8.8 (Android 12) for dipper (Xiaomi Mi 8) with Nikgapps core v20220421 from TWRP v3.6.2 : flashing Magisk v25.x (tried v25.2 and v25.0) would make the device bootloop, while flashing v24.x (tried v24.3) would work.

Despite this, upgrading from v24.3 to v25.2 from the Magisk app didn't caused any issue.

Thanks
[Magisk] Chris4711:
I run into this problem (GMS disappears from the deny list every time I enable the Universal SafetyNet Fix module) too, thanks for the explanation.

But how to pass the SaftyNet check then? With only the module enabled, i pass only the basic integrity check (checked with YASNAC), CTS profile match fails. How to get that fixed too?

I use Lineage 18.1.
[Magisk] 73sydney:
you need this:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/page-91#post-87198517

Also safetynet checker isnt what you need to check with now (safetynet is dying, and integrity check is its replacement), you need this:

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com
[Magisk] Chris4711:
Great, that works! Thanks!

Though, what's left:

MEETS_STRONG_INTEGRITY fails (Play Integrity API Checker)

If I understand it right, this is not possible now with Lineage (or any other non-stock image)

Play protect certification

Any chance to get the device certified?
[Magisk] zgfg:
For Play Protect, Device Integrity is enough (for all of us here)
[Magisk] Chris4711:
Obviously not: although MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY checks of Play Integrity API Checker pass, Play Protect still says "device is not certified" (I cleared the cach of Play Store and Play Services and rebooted).
[Magisk] jons99:
you need to spoof your fingerprint to a certified rom in order to have the play store certified

https://xdaforums.com/t/module-magiskhide-props-config-safetynet-prop-edits-and-more-v6-1-2.3789228/
[Magisk] m0han:
my time did come - didn't know at the time :p
[Magisk] zgfg:
'Obvious"?!

Device Certified requires to pass the SafetyNet - it's still enough to pass CTS Profile with Basic attestation (that is equivalent to Device Integrity)

Make sure you do pass the SN.

After that, it may take up to some hours (for some) to obtain Device Certified - or wipe that Data (not just Cache) for Google Play Store
[Magisk] pndwal:
Yup, clearing cache only will be the issue...

But passing CTS Profile with Basic attestation is equivalent to deviceIntegrity... PW
[Magisk] zgfg:
Yes. Lapsus calami
[Magisk] Chris4711:
Yup, took a while but now Play Protect says "certified" :cool:
[Magisk] J.Michael:
For those of us playing at home, were you using an old version of the Universal SafetyNet Fix module?