Magisk General Support / Discussion

[pndwal]

Yesterday I've updated my S21 to Android 13.
Switching to Magisk canary was necessary since the firmware patched with the stable version didn't boot.
Now when I open Magisk it asks for additional setup but, after confirmation, instead of reboot it goes in the install page.

Is the right / safe way to select select "direct install"?

Everithing seems to work btw (battery drain apart...)

Yes, it's part of the new changes that enforce app (apk) certificate check and same/newer version than that of running Magisk daemon. These will reject and forcefully uninstall any non-matching/old Magisk apps and force users to update the app.

It seems from your screenshots that you actually had Debug 25205 Magisk mask/core installed (nb. This is NOT Canary which is now built as release) but still had Stable 25.2 App (which is actually an older version)...

Normally you would update App first to ensure correct package is installed for updating Magisk mask/core... Did you install via custom recovery as .zip installer? Other?... or later downgrade App to stable?...

Nb. Debug Magisk mask/core will bypass the certificate/version enforcement mentioned above, but it seems daemon still ensures you are prompted to update older Apps...

PW

 

[c3k]

Yes, it's part of the new changes that enforce app (apk) certificate check and same/newer version than that of running Magisk daemon. These will reject and forcefully uninstall any non-matching/old Magisk apps and force users to update the app.

It seems from your screenshots that you actually had Debug 25205 Magisk mask/core installed (nb. This is NOT Canary which is now built as release) but still had Stable 25.2 App (which is actually an older version)...

Normally you would update App first to ensure correct package is installed for updating Magisk mask/core... Did you install via custom recovery as .zip installer? Other?... or later downgrade App to stable?...

Nb. Debug Magisk mask/core will bypass the certificate/version enforcement mentioned above, but it seems daemon still ensures you are prompted to update older Apps...

PW

Yes, you're right, I've patched the firmware with another device (since mine wasn't booting patched with stable), but I had and still have the stable apk on my device.

I'm not familiar with canary, here's the download link I use, found on XDA article: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

I now need to understand the difference between debug and canary before move on.

What you suggest?

 

[c3k]

I think I have to switch to canary release, but I don't know if signature verification could bring any problem in current situation.

Should I have to update the apk (and then a direct install if prompted?) or maybe is better than I flash again the firmare, but patched with the canary release (and then update the apk)?

 

[pndwal]

Yes, you're right, I've patched the firmware with another device (since mine wasn't booting patched with stable), but I had and still have the stable apk on my device.

I'm not familiar with canary, here's the download link I use, found on XDA article: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

I now need to understand the difference between debug and canary before move on.

What you suggest?

So Canary and Debug are both produced in same Canary branch as they build the same commits, just with different build flags...

Canary used to be built as debug, but recently separate Debug builds were provided as many users simply want latest commits for various reasons and use Canary for daily use, as a release build (despite limited testing).

Debug builds include verbose logging and latest Debug is required for GitHub issues for this reason as Devs don't want to wait for users to install and supply proper logs... They are used also but those doing Magisk development... They can also produce a performance hit on older devices... Debug builds also bypass signature (key) and version checks and enforcement as I mentioned...

app-debug.apk is now Debug build.
app-release.apk is now Canary build.

You can find older builds in GitHub repos, but since it is assumed that users will generally need only the latest builds John simply provides (correct) links to these under Downloads on main Magisk GitHub page; just click:

PW

 

[pndwal]

I think I have to switch to canary release, but I don't know if signature verification could bring any problem in current situation.

You'll have not problem direct installing any build from Debug as I've explained...

Should I have to update the apk (and then a direct install if prompted?)

Yup...

or maybe is better than I flash again the firmare, but patched with the canary release (and then update the apk)?

No need...

Just be aware that if you ever wish downgrade you'll need fully uninstall Magisk or install a Debug build to Direct install...

Moving back to Stable after the next release would be an upgrade however (and it will include all current tested Canary changes)... If you want to do that, just set Update Channel to Stable (or Beta) now to avoid Canary updates and seamlessly move back to Stable builds when available...

PW

 

[pndwal]

FWIW, LoveSy (Shana) has made a pull request for Zygisk v5 Api already merged in her Metagisk ('The Meta Magic Mask for Android') Magisk fork... The commit Add inode plt hook APIs includes this comment:

John has requested new XHook API use with Zygisk be deferred (stay w/ v4 for now) and Shana suggested fixing v4 Zygisk compatibility (Zygisk crashes whenever a module uses v4 api, see fixes #6402 and #6396) issue before revisiting this PR (it's been marked as draft for now)... This may also explain some recent Zygisk issues... Watch this space...

I have no idea about inode plt hook or what benefits it will bring... Any coders w/ XHook experience care to edify us?

CI Metagisk build is in Artifacts here (for mavericks):
Add inode plt hook APIs Magisk Build #2276...

PW

Zygisk V4 fixes now merged... PR for v6 (Add inode plt hook APIs) is now marked Ready for review... PW

 

[mcpite]

Hello guys, thanks for the replies!

J.Michael, zgfg, pndwal: Uninstalled both Magisk apps(the new was 'empty', the old did not really started, just told I should install magisk again), but after restarts root was lost. Next time I should'nt do this with hided Magisk.

The modifications not worked, and root checker also told there is no root. Seems like when I installed from the hided magisk app magisk again, it created a new, empty one, and after restart this magisk was 'stronger', se all modules are 'lost'. (Not sure this was the reason, but seemed like the fresh magisk manager had nothing, and after restart every mod was off.)
After uninstalled both magisk app, and made the flash and install again with pixelflasher (let ota to update, because I already had the november img -for my wife's phone- on my computer, and was easier to flash with that), after reboot the magisk find the setups, so modules was there, worked, and I had may deny list.

Now i know what I did wrong with magisk, I'll take care of it .

But would be also good to know, what can I do, when my phone will not seee the updates again?
I guess for the solution I need to uninstall/restore the magisk. When I see ota update (now it was not enough, it didnt find it) then clear how to continue. But should I continue the steps without the ota anyway? Once I made the opdate (the october ota) succesfully, wouldbe good the make this from the phones, and not flashing them on every month if it is not a must .​

Thanks for your helps!

 

[pndwal]

Hello guys, thanks for the replies!

J.Michael, zgfg, pndwal: Uninstalled both Magisk apps(the new was 'empty', the old did not really started, just told I should install magisk again), but after restarts root was lost. Next time I should'nt do this with hided Magisk.

The modifications not worked, and root checker also told there is no root. Seems like when I installed from the hided magisk app magisk again, it created a new, empty one, and after restart this magisk was 'stronger', se all modules are 'lost'. (Not sure this was the reason, but seemed like the fresh magisk manager had nothing, and after restart every mod was off.)

Maybe you took the in-app Uninstall Magisk option at some point?... That is not the same as uninstalling a Magisk App; it flashes backed up unpatched images and root is lost in that case...

After uninstalled both magisk app, and made the flash and install again with pixelflasher (let ota to update, because I already had the november img -for my wife's phone- on my computer, and was easier to flash with that), after reboot the magisk find the setups, so modules was there, worked, and I had may deny list.

Now i know what I did wrong with magisk, I'll take care of it .

​

But would be also good to know, what can I do, when my phone will not seee the updates again?​

This may vary per device but I believe OTA updates are seen w/ Magisk root for most devices; Nb. OEMs often stagger update rollouts...

You should apparently disable Automatic system updates in developer options on Pixel devices "so it won't install OTAs without your acknowledgement":
https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#prerequisites

I guess for the solution I need to uninstall/restore the magisk. When I see ota update (now it was not enough, it didnt find it) then clear how to continue. But should I continue the steps without the ota anyway? Once I made the opdate (the october ota) succesfully, wouldbe good the make this from the phones, and not flashing them on every month if it is not a must .​

As I said:

Yes, Install to inactive slot method used to work but it's broken at least for P6 and P7 series after late A12 updates... See this issue:
https://github.com/topjohnwu/Magisk/issues/5959
vv points to an article stating that as part of a Chrome/Android Update Engine change for A/B devices, after reboot the update_verifier program now runs and reads all dm-verity devices to make sure the partitions aren't corrupted... A fix would involve partition digest being re-calculated and overwriten to account for Magisk binaries in the newly flashed slot.
https://android.googlesource.com/platform/system/update_engine/
...

I'd fix first, then restore images before taking update (if you mean a delta OTA), but you'll need to reboot and fastboot flash Magisk again since preserve root through OTA method is broken...

Nb. Since updating with Magisk App hidden often fails it is advisable to take Restore the Magisk app before a Magisk update...

... Clearly with every Update you will need to restore unpatched images (use in-App Uninstall Magisk, Restore Images option) then take update, either OTA or full ROM, but you'll need to obtain new boot image from full ROM for patching (unless you use a custom recovery etc to obtain boot.img from a backup) in any case... Next, set up Magisk per instructions for a fresh install...

Unfortunately you have no other option until a fix for Install to inactive slot method (bypass for new partition digest checking) is found...

Thanks for your helps!

PW

 

[zgfg]

Hello guys, thanks for the replies!

J.Michael, zgfg, pndwal: Uninstalled both Magisk apps(the new was 'empty', the old did not really started, just told I should install magisk again), but after restarts root was lost. Next time I should'nt do this with hided Magisk.

The modifications not worked, and root checker also told there is no root. Seems like when I installed from the hided magisk app magisk again, it created a new, empty one, and after restart this magisk was 'stronger', se all modules are 'lost'. (Not sure this was the reason, but seemed like the fresh magisk manager had nothing, and after restart every mod was off.)
After uninstalled both magisk app, and made the flash and install again with pixelflasher (let ota to update, because I already had the november img -for my wife's phone- on my computer, and was easier to flash with that), after reboot the magisk find the setups, so modules was there, worked, and I had may deny list.

Now i know what I did wrong with magisk, I'll take care of it .

​

But would be also good to know, what can I do, when my phone will not seee the updates again?​

I guess for the solution I need to uninstall/restore the magisk. When I see ota update (now it was not enough, it didnt find it) then clear how to continue. But should I continue the steps without the ota anyway? Once I made the opdate (the october ota) succesfully, wouldbe good the make this from the phones, and not flashing them on every month if it is not a must .​

Thanks for your helps!

Since (AFAIK) you have Pixel, you can consider using a tool for OTA updating, Magisk reinstalling, etc:

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

forum.xda-developers.com

I don't have Pixel but the tool has a number of happy users and the author provides a great support

Regarding the tool, you can ask the questions in the corresponding thread

 

[mcpite]

pndwal:
"use in-App Uninstall Magisk, Restore Images option" - yes, I've used this. And the install was also started from magisk (but when it was hided!). The resore unpatched images way worked earlier (what was linked) - just earlier there was able to update, and I followed the instruction step by step. Now the update was not available - and I want to install back magisk on the wrong way.

I read what you linked about inactive slot problem; but now it didn't started (you are up to date, no update is avaiable).

OK, I can turn off auto updates when I cant do in the easy way.

zgfg: Thanks, I used the Pixelflasher; but only for the initial steps, for ota I tried to use again the magisk restore, install to inactive partition method.

 

[pndwal]

FWIW I did a bit of unashamed name-dropping here:
https://forum.xda-developers.com/t/hide-my-applist-a-brief-guide.4519731/post-87777717

It's a bit on History of Open-source Root that is Magisk and who are main Devs currently...

PW

 

[Anonymous V]

Good day everyone i have a problem in disabling my dm-verity using magisk, im trying to disable the dm-verity of my phone using magisk and after i flashed it i always ended up in bootloop it will only boot if the forcencryption option is enabled any solution how to solve this? Im still amatuer.


Device name: Oppo A71 CPH1717
Color Os: 3.1.0
Android version: 7.1.1
Magisk installed: Magisk 25.2 latest
Bootloader unlocked

 

[martyfender]

Good day everyone i have a problem in disabling my dm-verity using magisk, im trying to disable the dm-verity of my phone using magisk and after i flashed it i always ended up in bootloop it will only boot if the forcencryption option is enabled any solution how to solve this? Im still amatuer.


Device name: Oppo A71 CPH1717
Color Os: 3.1.0
Android version: 7.1.1
Magisk installed: Magisk 25.2 latest
Bootloader unlocked

When disabling forced encryption, you usually have to delete data or factory reset so a new, unencrypted data partition is created. At least that is what I had to do when I used it on older, Android 6 devices I used to have.

 

[Anonymous V]

When disabling forced encryption, you usually have to delete data or factory reset so a new, unencrypted data partition is created. At least that is what I had to do when I used it on older, Android 6 devices I used to have.

thank you for answering me sir, how am i going to factory data reset if im not able to boot up should i use stock recovery or twrp recovery?

 

[martyfender]

thank you for answering me sir, how am i going to factory data reset if im not able to boot up should i use stock recovery or twrp recovery?

Yes, you can use the stock or twrp recovery to do the factory reset.

 

[Anonymous V]

Yes, you can use the stock or twrp recovery to do the factory reset.

Thanks forbthe answer sir.

 

[PolyDave]

Help needed

I tried to update magisk from 23.0 to current latest version but failed (boot image extra was patched by old magisk, or something like that) , so i decided to update step by step. Went to 24.x just fine which i proceeded to go to 25.0. After a "successful" install i rebooted and now the device goes to fast boot instead, im unable to boot to the rom/system. Any suggestions? I don't wanna flash the rom from scratch.

Edit: i have twrp already installed if that helps.

 

[pndwal]

Help needed

I tried to update magisk from 23.0 to current latest version but failed (boot image extra was patched by old magisk, or something like that) , so i decided to update step by step. Went to 24.x just fine which i proceeded to go to 25.0. After a "successful" install i rebooted and now the device goes to fast boot instead, im unable to boot to the rom/system. Any suggestions? I don't wanna flash the rom from scratch.

Edit: i have twrp already installed if that helps.

Likely something is messed up in Magisk configuration; consider deleting everything in /data/adb (using twrp) and seeing if you can boot... This will remove all Magisk modules and settings so you'll need to set these (incl. SuperUser permissions, denylist etc) again in Magisk App...

Nb. If you can boot but see Magisk Installed: N/A, you likely still have a hidden (stub) Magisk App installed and need to locate and uninstall it...

If you still can't boot, say if you use a custom kernel or ROM... You may need to restore and re-patch vbmeta in this case, or simply restore stock vbmeta if on stock ROM due to refactoring of Magiskinit injection from 25.0... May need to dirty flash whole ROM if vbmeta restoration fails, and do initial boot image patch/flash Magisk installation again... PW

 

[Drahy]

L1 is good; means root is hidden properly to whatever key attestation widevine polls (there are several possibilities) and HD video / streaming is supported since attestation is indicating video decryption and processing is occurring in TEE (Trusted Execution Environment).

May not be bogus; seems this (network error message) may be your best clue to me...

I see you are Errorguy1991 on GitHub, and made this issue:
https://github.com/kdrag0n/safetynet-fix/issues/176
8 days ago... Yes, @kdrag0n will get to it, but he develops many projects / ROMs, utilities etc... and has a personal life... Please be patient!

It is possible this issue is USNF related, but you really need to demonstrate this... Have you checked behaviour of Netflix w/ USNF disabled (despite SafetyNet failing) for instance? Also, perhaps symptoms can be demonstrated to be comparable with issues currently getting attention (or lack of it) like this one?:
https://github.com/kdrag0n/safetynet-fix/issues/154

Other likely causes:

Not sure why you've added so many Google services in denylist! - This may well be causing issues; I am aware hiding Chrome broke webview for instance... Not sure what issues occur with your selection, but why do you need / risk anything Google other than GPay??

Also, selecting Netflix (without opening process view) selects only one default process for me (but I'm on Android 10), and this works fine! (*.playcore_missing_splits_activity processes aren't selected by default for me.)... You seem to have selected all possible processes for other apps too... Why?... Please deselect all but what you know you need!

Are you using any firewall, adblocker, VPN mods like wireguard or other network security protocols or mods (modules, apps) on your device?... These often block specific server access...

Have you tried disabling all modules except USNF (assuming OOS 12.1 is stock)?

Also, are you 100% sure your boot image (incl. kernel importantly) matches your current ROM? ... Those who take OTAs, then re-flash original Magisk-patched boot image sometimes have many issues especially with comms and other hardware, but sometimes only minor issues with mobile networks, wifi, bt etc...

This is doubtful; it doesn't affect other users.

He hasn't commented here in years... Highly unlikely he will comment now especially where methods to 'spoof/alter/manipulate non-Magisk related signals or traces to circumvent device state detection' are involved.

Hope this helps you. PW

I would like to continue with this thread here...

I am using Samsung Galaxy Note 20 Ultra 5G, Android 13 November update - original firmware rooted with Magisk + Universal Safetynet + Zygisk ...

I can install apps like Netflix, Disney+ etc no problem (I pass safetynet checks, device is authorized in GooglePlay etc all seems ok) BUT only Disney and HBO cannot play any streams (Netflix is ok) unless I install this: https://forum.xda-developers.com/t/...rm-protected-content-netflix-my5-etc.3794393/

It works then and only then - But it goes to L3 with bad quality streams. I tried MagiskHide to change fingerprint - no success, I tried Shamiko - same result still cannot play streams - I can open the apps - update them on Google Play but cannot play anything once I open the apps it just goes black with loading screen (location in EU) - I tried to disable Adblock if that can somehow blokc it but streaming works with Liboemcrypto modul instaled (on bad L3 quality) with adblock active so it must be somewhere else - anyone experienced anything like this and has any working solution?

Thank you!

 

[PolyDave]

Likely something is messed up in Magisk configuration; consider deleting everything in /data/adb (using twrp) and seeing if you can boot... This will remove all Magisk modules and settings so you'll need to set these (incl. SuperUser permissions, denylist etc) again in Magisk App...

Nb. If you can boot but see Magisk Installed: N/A, you likely still have a hidden (stub) Magisk App installed and need to locate and uninstall it...

If you still can't boot, say if you use a custom kernel or ROM... You may need to restore and re-patch vbmeta in this case, or simply restore stock vbmeta if on stock ROM due to refactoring of Magiskinit injection from 25.0... May need to dirty flash whole ROM if vbmeta restoration fails, and do initial boot image patch/flash Magisk installation again... PW

Thanks for the help, however removing magisk and its module in data/adb, but didn't seem to work, my phone still goes black after the logo and goes to fastboot.

My custom rom doesn't have a vbmeta file that i can restore.

I may try dirty flashing, (not sure what dirty flashing is, but i assume it's flashing my custom rom in its current state of my phone without wiping) but i want to ask, does dirty flashing usually delete all of the data, apps etc?