yashsingh1/xdaforums huggingface dataset:
[Magisk] TraderJack:
Hey @pndwal . Hoping for some advice you can give me although I'm getting the sinking feeling that I'm not going to like the answers....

I've been on a Pixel 3XL for the past 4-5 years. Unlocked with Magisk and for the most part I've been able to use everything I need. Currently I'm on A11 (didn't go to 12 due to some issues with thread closing of apps like Tasker, etc). using Magisk, Riru, Zygisk, SNFix and all that good stuff. Normally if Google Pay/Wallet works for me and Netflix I assume everything else will normally work.... have to do the normal dance to hide root from these apps and banking apps, etc.

I'm at the point where I need to upgrade of the 3XL and was considering either the 8 Pro or the OP11. I'd like to move away from the Pixel due to various issues (battery life being a big one), but in my investigation I'm learning about this Widevine.

Apparently it isn't new, but since I never experienced an issue with it, I never looked into it before. I just checked on my device and DRM Info and Netflix both report my 3 XL is at L1. I don't know if it would normally report this with my unlocked BL or if the various Magisk modules and Zygisk hacks are making it show this.

In any event, I'm concerned that I won't be able to move to a new phone and retain Magisk as well as L1 DRM to be able to play HD video content.

There doesn't seem to be enough talk about this issue and it just seems strange that here at XDA where so many are running unlocked/rooted that everybody seems comfortable with making this trade-off.

Am I off base with my info/thoughts here?

Also do you have advice on which phone models may not suffer this issue, or have known workarounds? I'd like to upgrade to a current generation (5G) phone that is close to flagship status and keep it for another 4+ years. I've seen some posts for the OP 8 which seems like people might have gotten around this, but seems silly to make the jump only to an OP8 which is only 2 years older than my current phone and still 3+ years old.

Thanks for your input.
[Magisk] pndwal:
Well there's generally no trade-off here...

Widevine Content Decryption Module (CDM) certification/licence is provided (free) to vendors by Google, but implementations of device attestation to compliance with security level requirements varies as OEM is responsible for this...

As mentioned in the linked post, OnePlus and RealMe have a history of unusual issues, eg requiring ctsProfileMatch or DEVICEINTEGRITY pass to achieve an L1 security level status or of keys being lost/voided unexpectedly... There may be issues with other OEMs implementations too... Most devices simply retain L1 regardless of whether ctsProfileMatch or DEVICEINTEGRITY are failing etc however...

For instance haven't heard of those issues with Pixels or for many other devices... However it seems that simply a bad/buggy OTA can cause key revocation on many (all?) devices, and this has happened to users whether devices were bootloader unlocked or not and with various brands...

Fixing this is achieved in various ways also... It seems OnePlus and RealMe are willing to supply the customised app to regenerate keys in some circumstances... I don't know what Google does, but guess bad OTAs etc breaking L1 certificate keys may be rare on Pixels... Xiaomi, after many users lost working DRM keys / L1 after a bad OTA, implemented an innovative in-ROM facility that allows users to regenerate keys themselves in late MIUI ROMs using an added settings menu. This saves users time visiting service centres, and no doubt countless hours fixing streaming/decoding issues for Xiaomi... Further, many Xiaomi devices without official ROM support for this feature have gained it for modders/unlocked devices in the form of custom ROM (notably XiaomiEU) ports from supported devices...

I've posted various other relevant details about fixes/issues for L1 Widevine DRM security which you can find by searching XDA with my member name and Widevine, L1 etc as search terms...

Nothing really current/specific other than the observations above...

Given that Widevine DRM issues, L1 key voiding etc can occur for various reasons even on locked/stock devices, I'm impressed with Xiaomi's approach, and I have noted the frustrations of users of some particular brands that also seem (frankly) to have general issues with customer satisfaction and reliability in recent times... Can't say much more...

Welcome.

🤠 PW
[Magisk] mrjuniork:
So I have recently switched to KernelSU and it seems like that there are still some Magisk residues left.

Before dirty flashing the ROM I have uninstalled magisk app and then flashed the ROM zip.

KernelSU is up and running but I can still see the magisk folder in /data/adb.

I don't know if the presence of that folder or any other leftovers are the reason for the Raiffeisen banking apps not working, or maybe the apps themselves detecting the KernelSU app?

Coz tbchecker is definitely detecting "me.weishu.kernelsu" but Momo isn't detecting magisk nor KernelSU.

I do have shamiko and zygisk next installed.

When starting the Rai pay app, it states that device doesn't meet security requirements 🤔
[Magisk] chiteroman:
In Magisk there is an option to fully uninstall it.

I recommend you to backup original boot.img before flashing anything.

Also apps can't read /data/adb items.
[Magisk] zgfg:
Uninstalling Magisk app, does not uninstall Magisk - you had to fully uninstall Magisk

Btw, Magisk Installation and Uninstallation instructions are on the official Magisk GitHub site, just two clicks from the Magisk app

You may delete /data,/adb but if you had LSPosed modules, they put their files elsewhere and no guarantee that you won't have leftovers - you had to uninstall LSPosed modules yourself

However, I don't have KSU and don't know what and how do you have to hide, specially from your particular banking apps.

Nevertheless, make sure that you first pass Device and Basic Integrity - you will have to use PIF or USNF modules (just b having KSU, doesn't mean that you will pass)
[Magisk] mrjuniork:
Thx for your replies, but I figured out the culprit...

Silly me, but it was actually AdGuard which so restrictively worked in the background that those apps couldn't run properly 🤦🏻

All good now 👍🏻
[Magisk] Koffietijd:
I have:

- Magisk 26.3 (26300),

- Magisk App 26.3 (26300) and

- Shamiko v0.7.3 (174)

installed on my Fairphone 4 with

- LineageOs+MicroG 20-20231008-microg-FP4.

I see there is an update available for Shamiko 0.7.4 but when I try to install this version, or remove 0.7.3 and install 0.7.4 I get a message:

- Copying zip to temp directory
- Installing Shamiko-v0.7.4-188-release.zip
- Current boot slot: _a
- Device is system-as-root
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: module.prop
***********************
Shamiko
by LSPosed Developers
***********************
*******************
Powered by Magisk
*******************
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: customize.sh
- Shamiko version v0.7.4 (188)
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: verify.sh
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/update-binary.sha256
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/com/google/android/updater-script.sha256
- Extracting verify.sh
- Verified META-INF/com/google/android/update-binary
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: customize.sh
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: customize.sh.sha256
- Verified customize.sh
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: verify.sh
Archive: /data/user/0/iz.uzlqakjevitz/cache/flash/install.zip
inflating: verify.sh.sha256
- Verified verify.sh
- Installing from Magisk / KernelSU app
- Magisk version: 26300
*********************************************************
! Please install Magisk v26.3+ (26302+)
*********************************************************
! Installation failed

But as far as I can see I have the latest Magisk. What is the solution here?
[Magisk] shoey63:
Did you read the bit where it says ! Please install Magisk v26.3+ (26302+)?

Do that.

(Magisk Canary or Alpha)
[Magisk] Koffietijd:
Yes I did see that, but as far as I can find, 26.3 is latest Magisk version. link (that one is from 4 septembre) and there is no update available for Magisk from the app.

Suggestions where to find "Magisk v26.3+ (26302+)"?
[Magisk] Homeboy76:
Tap

Search This Thread

at the top of this page, type magisk canary or magisk alpha in the search box, and Tap the Search button.
[Magisk] Nergal di Cuthah:
Requires latest canary as the error says 26302
[Magisk] mrxtc89117:
You have Magisk v9, phh superuser and root switch? With root switch on disable, do you pass safetynet?
[Magisk] Captain_Throwback:
No. Magisk Hide cannot (currently) hide Xposed.
[Magisk] :
Root switch won't disable phh superuser.

So i could not pass SN.

But yes i tried that. Also tried with supersu and failed.

I tried first

Magiskv9

Phh superuser 266r2

Then

Magisk v9

Supersu 278sr3

Rootswitch 1.3.3.2

Then

Magisk

Phh superuser

Rootswitch

No luck yet but will try again soon.

Magiskhide is not working for me and i didn't have a log to review so i will do this again and hope to have a proper log.
[Magisk] la_people:
I just realise that when I enable or disable "magisk hide, it's show as if I don't have any root installed.
[Magisk] Setialpha:
This. Then in Magisk Manager to Settings > Enable MagiskHide and reboot, working perfect here.

[MENTION=4470081]topjohnwu[/MENTION] I tried installing Magisk v9, then PHH SuperUser 266r2, then I rebooted, there was no 'phh' in /magisk. Flashing again did solve the issue. I could reproduce this on my Lux (Moto X Play). So before flashing any module I need to reboot once after Magisk was flashed. Is this a known issue?

Edith: enabling the dark theme in Magisk Manager 2.5 also doesn't work (AICP 12.1).
[Magisk] SimplyCity:
Guys, hi. I am pretty new to Magisk, have my own success with it, but also have a failure and would kindly ask for help.

Problem is with installing my private app to system/priv-app...

History: I prepared a module (used magisk-module-template-master for that) by putting my app inside system/priv-app/my-app/myapp.apk

When I had v8 istalled, I just let Magisk Manager 2.1 to install my module, reboot, and my app was working just fine.

Now, I've upgraded to Magisk v9, and the same simple module (without any other modification, just my app in proper folder) gives me bootloop.

I've flashed whole system again to check it out and the same... Even when I remove apk file from my module (so theoreticaly it should just "make" a folder "my-app" in system/priv-app/) I got bootloop.

What is wrong with that? What could be the problem? Do I have to fill something into post-fs-data.sh? Or enything else?

I just cant make Magisk to push myapp.apk to desired folder in system/priv-app...

Please, could you help wiyh that?

ps. Pixel launcher module from within Magisk Manager 2.5 gives me bootloop, to. It should push two apps to system/priv-app and system/app, but nothing similar happen. I mounted magisk from recovery and it looks like whole folder structure for pixel launcher (or my app module) are correct.

It would be wonderful, if enyone could help, please.

ps. I will ask this in "Collection of Magisk Modules", too. I am desperated and need any help. Thank you.

Device: S7E 935F, Nougat beta, twrp 3.0.2-4
[Magisk] yochananmarqos:
Check out the App Systemizer module. It's been updated for Magisk v9, however it requires two reboots to work.
[Magisk] return.of.octobot:
Are there updated templates available that are v9 compatible? It seems as though I'm going to have to rewrite all of my personal system app and build.prop modules in order to get them running on the latest update. Either that or existing modules that mount apps to system as well as utilize the current post-fs implementation that I can work off of.

EDIT: Found a template I can work with for build.prop tweaks. Any updated v9 modules that install apps to system available yet?
[Magisk] AnDroiDHackxr:
Can you guys PLEASE fix the "this zip is not a magisk module" it's very annoying I can't update superuser or download any modules without this error PLEASE fix.
[Magisk] return.of.octobot:
I'm not exactly sure that I'm familiar with the error you're referring too but I would suspect that it's less of a Magisk problem and has more to do with the modules you're trying to use not being updated for compatibility with the latest release. That's why I tend to write my own, as they say, if you want something done right.
[Magisk] Captain_Throwback:
I don't have this problem, so I can't comment on how to fix it. I've made several modules that all install fine in the latest version of the app. If you're having a problem, where is the log?
[Magisk] mrxtc89117:
Can you write one that will hide xposed please. Much like what suhide does hding xposed 86.2
[Magisk] minieod:
Edith, works for me, see screenshot below

But what doesn't work is AP
[Magisk] Captain_Throwback:
I've said this several times - Magisk CANNOT (currently) hide Xposed.

Creating some Magisk module won't magically be able to do it, lol.

SuperSU + Suhide + RootSwitch is your ONLY option if you want to use Xposed and pass SafetyNet (if that method even still works).
[Magisk] Nomelas:
tried again and now it works fine... idk why its different now than before. maybe something to do with updating from older versions....
[Magisk] AnDroiDHackxr:
Here
[Magisk] fefuzzo:
i installed magisk manager and update magisk to last version, than i removed root from supersu, and rebooted...than i open magisk, went into download and download phh superuser, but i have problem to install, in app and with twrp doesn't works...where is the problem??
[Magisk] AnDroiDHackxr:
I'm on the latest magisk version I had to flash v9 manually because I was getting this error, also can't update superuser because of it.
[Magisk] Captain_Throwback:
There are no errors in that log. Do you have the advanced logging options in the app enabled? Can you pull a logcat?
[Magisk] photolarry:
I'm experiencing same thing. Once enabling hide then picking Android Pay, Google Play services, and NFC the root is lost and nothing functions at all. Help please. Am I doing something wrong? It's also unclear if using xprop zip file to change ro.boot.flash.locked is right way or using this new command within is better and how that's implemented
[Magisk] pndwal:
0fficial 26302 release version is Canary... Click Canary link in Downloads, main Magisk GitHub page... PW
[Magisk] Shun_5377:
The banking app in question is https://play.google.com/store/apps/details?id=com.citibank.mobile.hk. It is still detecting root even though it is running from Work Profile. Here is my environment:

Android 11 with Work Profile turned on

Magisk Canary (26302) + MagiskHide Pros Config + Shamiko v0.7.4(188) + Universal SafetyNet Fix v2.4.0-Mod 2.0 + Zygisk - LSPosed

Magisk settings:

Only owner has root access + Each root session will have its own isolated namespace

Magisk hidden, renamed and disabled (using App Manager) in Work Profile

Any idea how to get the banking app to work or should I get an unrooted phone for it?

Thanks.
[Magisk] zgfg:
You should not need MHCP - try using PIF module instead of MHCP and USNF

Also, what for do you use LSPosed - you need to hide LSPosed modules b using HMA
[Magisk] Shun_5377:
Thanks. I have tried (including removing Shamiko + LSPosed + HMA and then re-enabling Deny List) but no luck. The banking app in question is so smart 😅
[Magisk] veg-:
Hello, xiaomi mi 5s plus, I tried both SuperSU and Magisk, everytime i had stuck at mi logo (bootloop). I patched boot.img from magiskapp, flashed and it stuck at logo. MIUI 10.2, Android 8. Also tried install magisk zip from twrp, same. After every failed try I restored backup.
[Magisk] BillGoss:
Instead of flashing the Magisk patched boot image, use fastboot boot <patched boot>. And when that boots successfully use Magisk app to do a Direct Install to make the change permanent.
[Magisk] veg-:
It worked when I put a checkbox on dm-verity or something. 2 checkboxes were selected now it's installed.
[Magisk] Nekromantik:
are there any modules that can spoof region/country for apps that only work in US?

i dont mean Ip check.

I have app called omnipod 5 which is only released for pixel 7 series in US and canada and in UK if i install apk as soon as i start it it closes itself
[Magisk] chiteroman:
Try my Xposed module: https://github.com/chiteroman/BootloaderSpoofer

Maybe the app checks bootloader status.
[Magisk] sawdoctor:
Been reading on Reddit lots of posts about the app and incompatibility. I don't necessarily think it's a region issue as so many devices are having the same issue. You could use an app like app manager/innure/apk editor and see if there's anything in the manifest about region and remove it
[Magisk] Shun_5377:
Thanks. Tried but did not profit.
[Magisk] subham619:
SuperUser access dialogue box is not showing up and new apps(root) are also not showing in app's superuser applist tab. Magisk is not asking for any device permissions as well.

After 2 years I upgraded magisk from v23 to v26. Maybe that's the reason.

I tried installing the v23 but the installation failed.

Newly installed apps(root) are also not showing up in app's superuser applist.

When I checked the device app settings, Magisk is not asking for any device permissions as well.

Please help me fix this without losing my data.
[Magisk] J.Michael:
Does the first screen of the Magisk manager app say that Magisk is installed?

Did you hide the old Magisk manager app that was working perfectly well, and did you unhide before you installed a new manager app?

How did you install the new Magisk?

Which Magisk version did you install? It is not enough to say "v26", you need to say "v26.1" or "26302",... People reported problems going from 23 to 26, some problems have been fixed by 26302.
[Magisk] zgfg:
First, describe how you upgraded

Did you just upgrade Magisk app or also Magisk itself?

Attach the screenshot of the Magisk app main window (to see what exact version you use, did you successfully upgraded Magisk, does Magisk app recognize that Magisk is installed)

And btw, what is your device, ROM, Android version
[Magisk] devand11:
Hi,

I am struggling with installing magisk after upgrading my Xiaomi Mi 11 Pro from xiaomi.eu 14-0-9 to 14-0-11.

Phone: Xiaomi Mi 11 Pro

OS: xiaomi.eu 14-0-11 (Android 13)

Magisk Manager 26302

Whithout patched boot image everything works fine (except root of course).

After patching the boot image with the manager, google doesn't work anymore. Play store doesn't show up and I get a message every couple of seconds that Google play services app keeps crashing. If I switch back to the original boot.img, everything works again.

It all worked just fine on xiaomi 14-0-9 and all earlier versions.

Any help is highly appreciated.
[Magisk] Boulder08:
I am having root detection issues with one app which is required for using the concert tickets I have purchased.

Magisk 26302 installed, Shamiko v0.7.4 is installed as well, Zygisk enabled. The app is added to the DenyList and I've cleared its data. Still it detects root, or something else as it detects "a security issue".

I have tried installing it in Island, where the Island profile has no root apps and my one banking app works while in the normal environment it won't.

I have tried Hide My Applist, doesn't work in either Blacklist or Whitelist mode. The previously mentioned strict banking app works with the same template.

What could I try next?
[Magisk] iruiz2:
Try disabling usb debugging, some apps check that.
[Magisk] Boulder08:
Didn't help, same error.
[Magisk] J.Michael:
If you were not forced to wipe data as part of upgrading the ROM then you could have old Magisk modules still installed.

Try disabling all Magisk modules.
[Magisk] devand11:
Thanks. Upgrade was done with a bash script and not with twrp. The script does not wipe any data.

Problem is I can't go back to 14-0-9. After flashing it takes ages to boot and it looks as if it freezes (normally it boots quite fast after upgrading the OS).

I tried

adb wait-for-device shell magisk --remove-modules

but it says

/system/bin/sh: magisk: inaccessible or not found

Edit:

I tried this one: https://xdaforums.com/t/how-to-disa...agisk-and-twrp-recovery.4394991/post-86333733

Play store worked for a moment but everything else does not :(
[Magisk] J.Michael:
The details of the bash script might be of interest to others. I was just saying that it was possible you still had some modules installed, and modules sometimes stop working when Magisk is updated, and that might explain your problems.

I thought you said that you could boot with the new Magisk, but some apps weren't working. If you have root, you don't need adb or safe mode to disable modules. If the Magisk manager app won't help, you can just look up the magic name of the file to put in each module directory. (There might be a file you can put in the /data/adb/modules directory to disable all modules at once.)

So, are you saying that you disabled all modules and there is no improvement in the state of your device?

If you end up reinitializing the ROM and then reinstalling Magisk, maybe next time disable internet access first. The long first boot might be something downloading updates without asking permission.
[Magisk] devand11:
And that is a good point. It seems no modules are left.

The script only flashes img files:

$fastboot set_active a
$fastboot flash abl_ab images/abl.img
$fastboot flash aop_ab images/aop.img
$fastboot flash bluetooth_ab images/bluetooth.img
$fastboot flash cpucp_ab images/cpucp.img
$fastboot flash devcfg_ab images/devcfg.img
$fastboot flash dsp_ab images/dsp.img
$fastboot flash dtbo_ab images/dtbo.img
$fastboot flash featenabler_ab images/featenabler.img
$fastboot flash hyp_ab images/hyp.img
$fastboot flash imagefv_ab images/imagefv.img
$fastboot flash keymaster_ab images/keymaster.img
$fastboot flash modem_ab images/modem.img
$fastboot flash qupfw_ab images/qupfw.img
$fastboot flash shrm_ab images/shrm.img
$fastboot flash tz_ab images/tz.img
$fastboot flash uefisecapp_ab images/uefisecapp.img
$fastboot flash vbmeta_ab images/vbmeta.img
$fastboot flash vbmeta_system_ab images/vbmeta_system.img
$fastboot flash xbl_ab images/xbl.img
$fastboot flash xbl_config_ab images/xbl_config.img
$fastboot flash boot_ab images/boot.img
$fastboot flash vendor_boot_ab images/vendor_boot.img
$fastboot flash cust images/cust.img.0
$fastboot flash cust images/cust.img.1
$fastboot flash super images/super.img.0
$fastboot flash super images/super.img.1
$fastboot flash super images/super.img.2
$fastboot flash super images/super.img.3
$fastboot flash super images/super.img.4
$fastboot flash super images/super.img.5
$fastboot flash super images/super.img.6
$fastboot flash super images/super.img.7
$fastboot flash super images/super.img.8
$fastboot flash super images/super.img.9
$fastboot flash super images/super.img.10
$fastboot reboot

After flashing the patched boot.img, I can boot but the modules section in magisk manager is grayed out so I assumed that magisk is not successfully installed or working. Plus, aomehow these google services are not working properly.

I'll try to go back to 14-0-9 later today until there is a solution.
[Magisk] zgfg:
I think I asked you to post the screenshot of the Magisk app

And that asked you does Magisk app say at the top (that's why the screenshot) Installed NO or Installed <version>

It's a known and common issue, mentioned here many, many times that if you previously had your Magisk app/mngr hidden/repackaged, that you MUST uninstall that old hidden/renamed/repackaged Magisk app

If not, it causes the issue that new Magisk app displays Installed NO and all tabs and options related to root (Superuser, Modules, DenyList, etc) are disabled

So find your old hidden/renamed (you should know how you renamed it when doing Hide Magisk app) and uninstall it, and reboot