yashsingh1/xdaforums huggingface dataset:
[Magisk] mcpite:
Hello guys.

I have a Pixel 6a, and (was) rooted with magisk (for volte).

My phone didn't see the november update, so I tried to uninstall/restore magisk, maybe then I can see. Earlier it worked me once this method (right after rooting): P6 OTA with magisk

The phone didn't fint the update, so I installed back magisk...

But I forgot, that magisk is hidden/renamed, so the magisk install was a new magisk! After restart, root lost, and the old, renamed magisk says: The hidden magisk app cannot continue to work because root was lost. Please restore the original apk.

:(

1, Should I uninstall both magisk?

2, I need to do all setups again for magisk?

3, Can I solve this without flashing, or when root is lost, I need to patch again? (I made it with pixelfalsher originaly)

+1, Now I can see the november pacth - should I upgrade it now, or only after maisk/root works again?

Thanks for any help!
[Magisk] c3k:
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...)
[Magisk] J.Michael:
Are you distinguishing between Magisk and the Magisk manager app?

If you installed a new Magisk manager app without dealing with an old, renamed, manager app, the first step is usually to uninstall the old app. After reboot the new Magisk might be working.

If you don't know whether Magisk is installed at all, you can uninstall all manager apps and reboot. Reasonably recent versions of Magisk will not tolerate having no manager installed, and will install a manager -- if you uninstall all manager apps and have a manager app after rebooting, you have a Magisk installed.

If you installed originally with PixelFlasher, I think you can use PixelFlasher again. I do not know if PixelFlasher helps with the dance to restore Magisk-less system, take update, reinstall Magisk (except that last step).
[Magisk] zgfg:
You have to uninstall Magisk APPLICATIONS (uninstall both apps) and install once again

But be aware, that Magisk APP (aka manager) is not Magisk (service, mask, 'root', whatever you call it), hence you should not uninstall Magisk (as you wrote), but only uninstall Magisk APP(s) (as I wrote above)

---

About terminology (translation between your names and mine)

Ie, when you say 'root' that is actually Magisk (service, mask, 'root') - how I call it

When you say 'magisk' that is actually Magisk App or Manager - how I call it above

Because, Magisk is more than root, and Magisk app is actually only the user interface or Manager for that Magisk

Hence, in your case, you have single Magisk (mask, service 'root') installed, but you have two Magisk applications where the old one was hidden/repackaged/renamed and that one still communicates with Magisk, while the new Magisk app does not 'see' Magisk

However, your Magisk still works (you didn't loose root). If you previously granted root to some root apps, those root apps should still be able to use root

Also, Magisk modules that you previously installed should also still work (no matter that your new Magisk app does not see them)
[Magisk] pndwal:
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/

Nb. I don't much like the 3rd party source for instructions... Here's the official doc (albeit broken for you):

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

Yes (Apps, not core/mask as already discussed); easiest way to fix issues with competing apps especially if you accepted a Superuser request for an app (nb. this is a symptom of the issue (

No, just uninstall full App + hidden (stub) app per custom name, then reinstall full App and take Hide the Magisk app if you wish...

Yes, you shouldn't need to flash again and it's unlikely root was actually lost when you simply have app conflicts...

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

Welcome. 🙂 PW
[Magisk] pndwal:
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
[Magisk] c3k:
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?
[Magisk] 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)?
[Magisk] pndwal:
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
[Magisk] pndwal:
You'll have not problem direct installing any build from Debug as I've explained...

Yup...

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
[Magisk] pndwal:
Zygisk V4 fixes now merged... PR for v6 (Add inode plt hook APIs) is now marked Ready for review... 👀 PW
[Magisk] 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!
[Magisk] pndwal:
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...

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

As I said:

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

🙂 PW
[Magisk] zgfg:
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...

xdaforums.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
[Magisk] 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.
[Magisk] pndwal:
FWIW I did a bit of unashamed name-dropping here:

https://xdaforums.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
[Magisk] 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
[Magisk] martyfender:
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.
[Magisk] Anonymous V:
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?
[Magisk] martyfender:
Yes, you can use the stock or twrp recovery to do the factory reset.
[Magisk] Anonymous V:
Thanks forbthe answer sir.
[Magisk] 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.
[Magisk] pndwal:
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
[Magisk] Drahy:
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://xdaforums.com/t/magisk-modu...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!
[Magisk] PolyDave:
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?
[Magisk] pndwal:
Yup... I covered a few bases since you didn't give details re. device / ROM... Please give this info as I don't know it's age, boot type or even if you have 2SI booting (affected by the 25.0 refactoring I mentioned)...

You can try restoring unpatched boot.img (or recovery.img if you have A-only legacy SAR device Magisk in recovery ramdisk) only using fastboot to see if booting is restored... Or dirty flash complete ROM (Nb. fastboot type ROMs are more complete than recovery ROMs)...

Yes, dirty flash means no data wipe/factory reset... Apps etc will usually be preserved fine... and you've already wiped the data that may cause bootloops w/ Magisk installed, ie. in /data/adb, so fresh Magisk install after ROM flash should be fine... PW
[Magisk] pndwal:
"Netflix is ok" meaning you have HD decoding or only low definition?...

You shouldn't need fingerprint set by MHPC if you have @Displax modded USNF fork module w/ Play Integrity hardware based verdict enforcement bypass as this sets an old but passing fingerprint to target gms...

So Netflix is no longer using SafetyNet or Play Integrity APIs to restrict usage directly... I'm not sure about Disney, HBO etc but may be similar... L1 Widevine does depend on S/N or PI deviceIntegrity pass on some devices (but not on my RN8T MIUI device) as well as a number of other factors... I'll put more in a following post...

Please confirm you are passing new PI API deviceIntegrity verdict as this may affect those apps even if Widevine is not using this verdict on your device... Give results from Play Integrity API Checker and DRM Info apps...

If you have L1 Widevine you shouldn't need module you mention... PW
[Magisk] pndwal:
@Drahy,

Here goes:

--- Part of a recent conversation pasted: ---

You are correct that this occurs now... Big change from v5.0:

... Things are a bit strange/unusual since that update; Store will show app if manually installed but still says "app will not work for your device"... App otherwise still appears per CTS Profile match pass, and now apparently per deviceIntegrity verdict...

It appears that the statement "many devices that are not Google-certified or have been altered will no longer work with our latest app" is not strictly correct; many not passing S/N / PI deviceIntegrity won't decode HD streams however... L1 and L3 are both Google certifications but Widevine is part of AOSP, not just proprietary code, and even uncertified China region devices have L3 certification (I don't think L3 can be lost or any Android don't have at least that) meaning Netflix does work w/ SD streaming on any device since 5.0...

As I said a while ago:

Most Xiaomi devices seem to retain L1 Widevine with or without passing CTS Profile match (which of course requires GApps; nb. deviceIntegrity may well now be polled by those devices after updates since June also), but other devices have it only when passing and some devices seem to prevent L1 restoration w/o relocking bootloader... Still others require service department specialist software to generate new keys for CDM if ever they're lost, and some OEMs refuse to help... Since post 5.0 Netflix 'fully relys on the Widevine DRM provided by Google' and OEM implementation is so inconsistent, Netflix is still affected differently by S/N (and PI deviceIntegrity?) per device at least in respect to HD stream decoding ability assuming a device is certified for L1 Widevine in the first place...

A recent post about this:

https://xdaforums.com/t/...p-edits-and-more-v6-1-2.3789228/post-87737559

Despite knowing this stuff I found a couple of my posts where I'd misremembered details and I've made some needed corrections... 😜

--- End of conversation ---

Hope this information helps content streaming service users... 🤠 PW
[Magisk] PolyDave:
Dirty flash did the trick, after i flashed the rom again, i reinstalled magisk and everything seems to be working fine with no issues.

Thanks!
[Magisk] Erfirya:
can someone help me with my disney+ app issue. so I have:

Xiaomi POCO X3 NFC

xiaomi.eu MIUI v13.0.1

Android 12

Magisk v25.2

USNF v2.3.1 (Displax mod)

my problem is I can't watch any of their content on FHD, it only shows up to HD quality even though I've subcribed to premium. I've tried logging in the same account on the same device model but w/ locked bootloader and stock rom and it has a FHD quality option. I've also added disney+ to denylist but the issue still persist. I've checked if my device is certified using Play Integrity API Checker (Nikolas Spiridakis). Here's the result:
[Magisk] pndwal:
My Last two posts above may help you... Check Widevine security level... PW
[Magisk] Erfirya:
sadly its not showing in mine. I don't think I can get it back.
[Magisk] 73sydney:
I maintain my L1 Widevine on rooted Pixel 6 Pro. First device ive ever personally seen this happen on. I just assumed once you unlock bootloader you lose it. I keep wondering why people seem surprised by this....this has just been the way it is since forever...

I personally weigh this up as the cost of rooting, just like no OTA or warranty on Samsung....
[Magisk] asripath:
Had similar issue...

Cloned Disney to workprofile and

Uninstalled main profile Disney.

In work profile clear cache/data

Of Disney and relogin..HD started working again
[Magisk] m0han:
I used to have L1 widewine on my 'bootloader unlocked' device for a long time.

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

https://xdaforums.com/t/app-2-2-mix...y-featured-file-manager.1523691/post-86844883

Sadly, not anymore. I don't know how I lost it. I'd sure like to get it back if I can.
[Magisk] Erfirya:
cloned using what? can you please elaborate, I'd like to try this. btw HD is working, FHD is what I need to work
[Magisk] inhirz:
I got this error line in magisk log : stat /data/data/com.android.systemui failed with 2: No such file or directory

Any idea of what it is ?

Device : Oneplus 9

Rom : OxygenOS 13

Magisk : Canary 25205
[Magisk] pndwal:
🤔.. what's not showing?.. you showed screenshot of lockscreen??? Are you confused about something?

... Widevine implementation varies wildly across OEMs / devices... Follow links back from my posts above to discover various fixes and cautions...

Nb. Poco F2 Pro, Note 8 Pro, 9S and other users can use Xiaomi's embedded fix to restore lost keys / certification for Widevine... Not sure if it's available in X3... Probably need to restore stock to fix too... Some Poco models got fix before 9S and others... Method should be the same if available... Here's post w/ instructions for 9S...

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-87737559

See also link to April post there... 9S (others?) fix was available with MIUI 11.0.11.0 OJWMIXM but fix isn't automatic; requires you to follow steps to generate new keys / certificate... PW
[Magisk] pndwal:
Poco?... See my post above too... Didn't check which model you have as limited time ATM... PW
[Magisk] Erfirya:
I was trying to show you that in my device, widevine (L1) settings isn't there. This is a screenshot from another device (same model) that has a locked bootloader and stock rom. There's no hope in fixing it anyway so yeah, I'm just gonna stick to custom ROM with root.
[Magisk] asripath:
Using island.

You can use any workprofile app and

Install Disney in it to check.

Disney might be checking for root.

I could use Disney within browser of the phone with fhd but the app streams at a lower resolution and changing resolution option does not work.

There seems to be a emerging current trend of apps not only checking for root/lsposed

But also checking for root checker apps presence like momo/root beer etc.
[Magisk] asripath:
You can use apps like drm info or device info HW to check for widevine status.