yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Bit OT in [MODULE] Play Integrity Fix thread, so I've moved response to general Magisk discussion thread...

Seems Realme Widevine implementation/retention is an issue for many, and there are ongoing issues even for locked/stock device users...

Please say if you ever had L1 after unlocking, and when it was lost... And did you have L1 certification before unlocking (especially if China region device etc... Doubtful that you can get keys for China device 🤔)? And do you have Play Integrity deviceIntegrity?; Some OnePlus devices have L3 unless passing... This is not normal practice, but Realme may implement it with this requirement also...

Further, some implementations check fingerprint prop (and possibly others) and users needed to set a different one, so please say if the ROM matches original device region...

Assuming you had L1 locked and ROM region hasn't changed, and you have PI deviceIntegrity, note that some Realme devices have issue where Netflix reports L3 while DRM Info app indicates L1 please say if you are using the latter to detect; Realme have indicated that that indicator is correct (keys are valid) but they need to investigate why streaming apps reported L3 even locked!... See this thread for a dose of apparently unresolved realme reality on this from January 😬:

https://c.realme.com/in/post-details/1614211790961381376

(I note that many users are over Realme due to the priority (not) that they seem to be giving such issues for non-mod users...)

If DRM Info says L3, it may be that keys are voided and you need new ones... This is a safe assumption if you can lock B/L, have PI strongIntegrity (this can fail if there are /persist partition issues as stock persist images are generic and don't contain unique IMEI, BT, WiFi, mac, serial and other values), but still only have L3, assuming you did have L1 before unlocking... There's no easy way to check key validity that I'm aware of but others may know more.

In this case I believe you need service department help. Nb. Many MIUI device users can generate new DRM keys using a settings menu added for convenience after bad OTA updates caused voided keys on many devices (this is a common issue for DRM keys) but I haven't heard of any similar initiative from Realme...

So apparently service department would need to issue you a custom .apk to run after you send them your IMEI numbers (Nb. Running an .apk another Realme user received won't work as it needs to be customised for your device) to generate new device specific working Widevine/DRM keys... See this thread for the process:

https://xdaforums.com/t/requesting-fix-for-widevine-level-to-realme-apk-file-posted.4405783/

Nb. It's a bit old now so something may have changed in newer devices etc...

Hope this helps... 🤠 PW
[Magisk] pndwal:
Looks lttwo different hardware variants to me, but not clear...

If it's ROM for different hardware variant, generally you shouldn't use it... If it's just a regional variant (only), you can usually swap ROMs with bootloader unlocked...

Ok... guess you're flashing Magisk as .zip archive...

I was just concerned about flashing a pre-patched boot image from online source when I saw such offered in that thread...

👍 PW
[Magisk] m0han:
New Magisk
[Magisk] osm0sis:
A-only custom ROM with addon.d users, please note the loss in function:

Retain PREINITDEVICE during A-only addon.d by osm0sis · Pull Request #7284 · topjohnwu/Magisk

Just realized this was missing from our recovery dirty flash PREINITDEVICE support!

github.com

The workaround is to manually install the fixed addon.d script from my unmerged PR to /system/addon.d/99-magisk.sh and /data/adb/magisk/addon.d.sh:

Magisk/scripts/addon.d.sh at fix/addond-preinit · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] Neumii:
I found a Stock ROM online but i'm not sure if the ROM was clean and the site was trusted enough

the site was Mobifirmware (dot) com
[Magisk] pndwal:
Latest Magisk Stable:

Release Notes

2023.9.4 Magisk v26.3​

v26.3​

[General] Fix device information detection script

[General] Update BusyBox to 1.36.1

[General] Update toolchain that produces broken arm32 executables

[App] Fix root service unable to bind on OnePlus devices

https://topjohnwu.github.io/Magisk/releases/26300.html

👍 PW
[Magisk] pndwal:
OnePlus Users:

Nb. Issue:

Magisk app freezes when rooted on OOS10+OOS11 devices after commit 3938322 APP, Regression

is fixed in 26.3 with libsu update! 🎉👍 PW
[Magisk] legendebrune:
Thank you, for your detailed reply, much appreciated :)

I'll try my best to answer your questions accurately.

First, I do not know for sure whether had L1 with a locked bootloader, but I am certain that gt 2 pro users with a locked bootloader have L1 level by default. It is a chinese phone originally, and I changed region via full OTA, the OS is now EUEX C.20. I am also certain that some users who changed region from CN to EU via full OTA kept their L1 level when keeping a locked bootloader

I have tried harassing realme to get the app as recommended in this forum, and unfortunately they can't be convinved. I was really insistent, and they kept asking me to leave the phone in a technical center

I have PI device integrity, and I pass Safety net. Latest magisk alpha installed. DRM Info detects L3 and Netflix parameters only allow SD.

I have tried flashing CN Rom back with unlocked bootloader, and my device is still L3. What I di not understand is that my play store is certified??? I attach a few screenshots that might help diagnose the issue

Do you think my last option is to bring my phone to a realme certified repair shop? I would really like to avoid that if possible, but I would consider doing it if I had no other choice.

I have tried spoofing my bootloader using @chiteroman LSPosed module. I have tried to install Pixelify module to spoof my fingerprint props. Nothing has worked so far.

Realme phones are great in themselves and wonderful value for money, but support and software are unfortunately lacking?

Thanks again for your help, have a great day :)
[Magisk] No1sy B0y:
Device: Pixel 7 Pro

Android version: 13

Magisk version name: Stable

As soon as I saw that there was a new update in the Magisk app, I went ahead and did it. The app closed automatically and the icon disappeared. I still see root apps being granted root access, but the Magisk is nowhere to be found. I've tried reinstalling the .apk but the moment it finishes installing and I tap on "Open", it automatically closes and the app is not there.

I am unable to install and open the debug app either.
[Magisk] J.Michael:
Did you ever "hide the Magisk app"?

Did you unhide the Magisk app before installing the new Magisk.apk?

Look in your app drawer for the Magisk app and for whatever you renamed the Magisk app to. Uninstall the Magisk app. Try to run the renamed Magisk app and un-rename it. Failing that, uninstall the renamed Magisk app.
[Magisk] No1sy B0y:
This was it. I had forgotten I had hid it. Thank you for taking the time to reply.
[Magisk] pndwal:
I think it may be if DRM keys are voided... You'll need to determine if that's so; gave you some clues...

If L1 is restored when locked you seem to have other problems... Even if it's not restored is could be /persist partition tampering etc as I said...

I really don't know more, or Realme specifics...

Well you know as much as I do... Seems some users , even non-modders despair of a solution for L1 DRM on their devices... Others tell success stories... 🤷‍♂️

Welcome. 🙂 PW
[Magisk] mihalis1983:
Hello,

I'm facing bootloop when i'm trying to update from 26.1 to 26.3

Poco F1

Android 10 - miui12

ramdisk was N0, before i started flashing. It's yes now....

Also facing bootloop with the latest versions of Magisk-Alpha.

I tried everything:

Install directly through the magisk app -->bootloop (with and wihtout recovery checked)

Flash 26.3 via twrp --> bootloop

Extracted boot.img from rom, then patched with 26.3, then flashed through twrp --> bootloop

Restored un-rooted boot.img through twrp, then flashed 26.3 --> bootloop

Everytime i was recovering phone with boot.img (26.1 patched) backup (twrp). Also restored recovery,img...

Any help?
[Magisk] pndwal:
Please can you tell me if you still erroneously get Ramdisk = No or see Recovery mode option (checked) in Magisk Install menu after installing 26.3 App?... I want to know if this issue persists after fixes, and if it still needs un-checking in 26202+ or 26.3...

Anyway, yes; your issue is likely that Magisk has patched ramdisk in your recovery image...

The erroneous detection issue began occurring with 26105 Canary...

With Ramdisk = No, clearly you have another older legacy ramdisk boot-type ('type I') device being wrongly detected as a legacy SAR 'type III' device...

Further, as the Recovery Mode check box is erroneously appearing in these cases (it's only for A-only devices launched with Android 9 as these 2018, 2019 devices were the only type III devices made) and is checked by default, users are generally leaving it checked (as they don't know better) and Magisk is then patching ramdisk in /recovery partition when taking Direct Install, and recovery.img in Samsung AP binaries when patching these...

Taking Reboot will also cause many devices to boot via recovery (as it's trying to boot system with magiskinit in recovery ramdisk) where Recovery Mode is left checked...

If you/others here tried updating, you likely have both Magisk-patched boot.img and recovery.img now...

This issue should already be fixed with Fix device detection scripts and logic and Always check mounts to detect legacy SAR on bootmode in 26202 (Canary), but any who have used 26105 - 26201 builds and had this issue should start fresh with restored stock recovery.img or unpatched AP binary (if Samsung) to correct erroneous patching before installing 26202+... And if Recovery mode still appears, uncheck it! (... Unless you have a 2018, 2019 A-only legacy SAR device launched with Android 9 and actually need it.)

Hope this helps. 🙂
[Magisk] mihalis1983:
I'm getting ramdisk=yes

It was NO before i started flashing 26.3, or latest versions of magisk-alpha. All of them are causing bootloop... 26.1 working fine

Recovery mode option is not showing now.

Yes the device is 2018, came with Android 8 and i'm in A10 now..

I also restored stock boot.img (via twrp) and then flashed 26.3 (without rebooting), but still getting bootloop. I also restored recovery.img (twrp)

I read everything you said, but still i can't fix it.

Could you please give me instructions?

I also attatched stock boot.img . Could you identify if it's ramdisk YES or NO ?
[Magisk] pndwal:
Your device launched with Android 8.1... Please confirm it's A-only (not dual slots), but it almost certainly is NOT a Ramdisk = No (A-only legacy SAR) device, so Magisk installs in boot mode, NOT recovery mode... If pre-26105 Magisk showed Ramdisk = Yes, that would also confirm that you have working ramdisk in /boot partition...

Please say if you saw Recovery mode in Install options and if it still appears... If so you should NOT leave it checked... Patch new images with it unchecked...

It's possible you have another (new?) issue/regression... Many are reporting similar things here:

https://github.com/topjohnwu/Magisk/issues/7298

... I think you are Michael-R00T (this comment: https://github.com/topjohnwu/Magisk/issues/7298#issuecomment-1708096963) no?

See this issue too:

https://github.com/topjohnwu/Magisk/issues/7254

If you have the same results with restored /recovery and are patching stock boot.img, suggest you delete magisk directory and magisk.db file from/data/adb (with working 26.1 and root explorer), reboot (Magisk configuration will be rebuilt) and try direct update again... if still no dice, try dirty flashing your complete ROM before attempting again...

If none of these suggestions helps, baring suggestions from others it's likely it's a fresh regression... The two issues cited above are not resolved; I'd watch those, and if you don't think yours is the same (eg, you have QCom, not MTK soc), open your issue...

General advice: Please avoid seeking general advice in issues, or commenting unless your symptoms properly match; XDA is the correct place for that! 😜

Hope it helps... 🙃 PW
[Magisk] J.Michael:
I think you clearly have a ramdisk.

xxd -l 16 boot.img

shows a ramdisk size (4th longword) of 0x800000 = 8MiB.

You say things like you use an old, Magisk-patched, boot image to restore; you restore the stock boot image from TWRP and then flash Magisk 26.3 without rebooting. This leaves me wondering if you have the right "stock" boot image, if you are giving Magisk the right boot image to patch, if you are using Magisk to re-patch a patched image.

I know @zgfg reports routinely re-patching, but I think he also cautions that there are situations where it will not work -- some pairs of Magisk where one version cannot undo what the other did.

At any point in your flailing have you installed an unmodified system and confirmed that it works?

After doing that, I would reflash the unpatched boot image and again check that the system works.
[Magisk] zgfg:
I didn't follow your communication with @mihalis1983 but I can only comment the following:

- I have also an old (spare) phone Xiaomi Mi 9T, model from 2018 or 2019

- It does have separated Boot and Recovery, and it is the old A only phone

- Old versions of Magisk used to show Ramdisk No, although correct method for patching Magisk was always to patch boot.img, not recovery.img and without Recovery flag checked-in

- Now I run Magisk Delta 26301 and now, and this v26 offers me by default - which is WRONG, Recovery flag as checked-in when I want to patch/direct install (upgrade)

- Since I know that this phone needs to patch boot.img and not recovery.img, I did uncheck Recovery flag and I successfully installed Magisk v26 3 (Delta)

- I didn't try and I have no intentions to try installing Magisk (v26) with the Recovery flag checked-in, and also no intentions to Recovery

- @pndwal has a similar Xiaomi Mi 8T (I think) and he used to have the same case (Ramdisk No but Magisk must be flashed to Boot, not to Recovery, and without Recovery flag checked-in)

- As I said above, I use Delta 26301 but I think those changes (that Magisk now wrongly offersRecovery flag for those old A only phones) would be the same in Canary and Alpha
[Magisk] mihalis1983:
The boot.img that i'm recovering

I'm not recovering an old boot.img, but rom's stock boot.img patched with 26.1, saved in my recent nandroid backup. 26.1 working fine...

Magisk has the ability to update/repatch a boot.img that was patched with a previous version of magisk. That is the update procedure.

I also flashed the stock un-rooted boot.img (the one attached above, extracted from rom) , booted normally, saw that i had no root access, flashed magisk 26.3 through magisk app, reboot --> bootloop.

It seems that there is some kind of incompatibility between my A10 rom and magisk 26.3.

So, i think, i'll have to wait for a newer version, hopping that will work.
[Magisk] J.Michael:
Your first paragraph repeats everything that confuses me.

I think you eventually said what I wanted to hear: that you flashed an unpatched boot image and got a working system, although without Magisk.

Did you ever try @pndwal's suggestion that you delete /data/adb? I understand that the sequencing is tricky, but I think you can delete it while booted with Magisk 26.1, or you can delete it with TWRP.
[Magisk] J.Michael:
I understand that you have no interest in installing Magisk in recovery.

Do you remember whether everyone is free to install Magisk in recovery? I thought that in most cases, anyone could install Magisk in recovery, it is just that it is more convenient to install Magisk in boot.

I think I remember someone creating a problem by patching both boot and recovery.
[Magisk] mihalis1983:
Yes i tried deleting /data/adb magisk directory and magisk.db. Nothing changed.

Also i was asked above about slots. Yes, the device is A-only (not dual slots).

Please let me explain my 1st paragraph above:

When flashing 26.3 i'm facing bootloop. Then i'm booting in twrp (holding volume up + power). Then i select "restore" and i'm recovering boot.img from my nandroid backup. (That is a recent 26.1 patched boot.img). The phone boots normally with root access.
[Magisk] zgfg:
We had various discussions here, I don't remember everything

But I generally wouldn't leave Recovery option checked when installing new Magisk and specially when patching boot.img or direct upgrading (although other users may not observe or they wouldn't be concerned about)

Also I don't know how could that affect Uninstall Magisk if it wrongly assumes now that on the given device, Magisk was previously installed to Recovery or so
[Magisk] HippoMan:
This illustrates why I always want to be able to use a device upon which TWRP (or perhaps OrangeFox) is functional. As long as I've taken a proper full nandroid backup of a previous working system, I can easily nandroid-restore that working system after an upgrade, if I wish.

I am not happy with Google for continuing to "enhance" (ha ha!) Android as time goes on, thereby making it more and more difficult to get TWRP and OrangeFox working with newer Android versions.
[Magisk] amk316:
hi

my banking app detect vpn connectivity and dose not work.

is there a module to hide vpn connectivity?
[Magisk] EtoileLabrie:
how to mount /system RW ?

Device Umidigi C1 is arm32 binder 64

running Android 12 Go edition

Ramdisk Yes

using Magisk v26.3

adb shell df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 934M 2.4M 931M 1% /dev
tmpfs 934M 0 934M 0% /mnt
/dev/block/dm-3 1.0G 1.0G 0 100% /
/dev/block/dm-4 387M 386M 0 100% /vendor
/dev/block/dm-5 1.0G 1.0G 0 100% /product
magisk 934M 2.9M 931M 1% /debug_ramdisk
tmpfs 934M 8.0K 934M 1% /apex
/dev/block/mmcblk0p38 104M 416K 101M 1% /cache
/dev/block/dm-6 26G 995M 25G 4% /data
worker 934M 0 934M 0% /debug_ramdisk/.magisk/worker
/dev/fuse 26G 995M 25G 4% /storage/emulated

adb shell su -c mount -o remount,rw /dev/block/dm-3
mount: '/dev/block/dm-3'->'/system/bin/ziptool': I/O error

### Works
adb shell su -c ls /system

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

UMIDIGI_C1:/ $ su -c mount -o rw,remount -t auto $(magisk --path)/.magisk/mirror
mount: '/dev/block/dm-3'->'/debug_ramdisk/.magisk/mirror': I/O error
[Magisk] J.Michael:
You probably can't.

You probably shouldn't.

Look at the output you vomited at us: the root filesystem is at 100% used, it has little to no free space. You can't put anything else in it.

If you describe what you are really trying to do (i.e., the thing you want to do that you have decided you can do but first you "need" to mount /system rw), someone will probably explain how you can get a similar result by using Magisk's ability to "overlay" files under /system.
[Magisk] Lord Sithek:
NoVPNDetect

Prevent some apps detect your phone connected to VPN.

modules.lsposed.org

An LSPosed module, unfortunately it didn't work for me but maybe you'll get more luck
[Magisk] amk316:
thank you

but i am looking fore magisk module
[Magisk] lenoid:
I upgraded Magisk app on my Xperia X Compact (Android 8.0) from 26.1 to 26.3. After "Direct Install" I made a reboot but had no root anymore. Now the Direct Install option isn't offered anymore. I tried to downgrade to 26.1 and flash 26.1 and 26.3 zip via TWRP, but I'm not able to get root again. Any ideas how to get root again (I don't care about Magisk version, so an older version would be fine for me)?
[Magisk] zgfg:
First, when you say 'no root', do you mean that Magisk app is showing

"Magisk

Installed No"?

If so, then obviously, you cannot have Direct Install anymore BCS Direct Install requires root

However, your problem could be that you do have root but that Magisk app wrongly thinks that you don't have it

So test the following:

Use Terminal emulator and type:

magisk -c

Does it return the Magisk version like:

d4e55290: Magisk: R (26302)

Or what exactly it returns to you?

If it returns Magisk version but your Magisk app wrongly thinks 'there is no root', then please recall did you ever previously set Hide Magisk App

If you did, then you have to find (you have to remember what app name you gave it then) your previously 'hidden', renamed and repackaged Magisk app and delete it manually, and then reboot
[Magisk] lenoid:
@zgfg

Magisk says:

Installed: N/A

I used this Terminal Emulator and it shows "magisk: not found" after typing "magisk -c".

I never used the hide feature. At least I can't remember since I don't use apps, that don't work on rooted devices.
[Magisk] zgfg:
Then, Direct Install indeed uninstalled your Magisk

You should install Magisk as how you originally did, first time. Either through TWRP (if applicable to your device and ROM) or by patching and flashing the boot.img

There might be problems for your device with the latest Magisk c26.3, in that case try with an earlier version of Magisk (Stable or Canary)
[Magisk] lenoid:
@zgfg

OMG, rooting process was almost 5 years ago. :cowboy: I think I flashed a modified boot.img. Will give it a try.

Until 26.1 Magisk worked fine, I always updated via Direct Install.
[Magisk] zgfg:
If using v26.3, there is a chance (and that might be your issue when you did Direct Install) that Magisk app would by default (and falsely) check-in Recovery option

If you are patching boot.img (not recovery.img) then you must inspect and manually uncheck that Recovery option before patching (or before Direct Installing)

Unfortunately, for the last year or so, every single new Magisk version included some bomb/regression bug, ie, something that previously worked ok was messed up with that new version.

In the next version, that bug will be fixed, but something else would no more work properly.

Some versions affected modules, some had issues when patching stock boot images, Direct install, etc
[Magisk] J.Michael:
Your problem might include the Magisk database having been updated by the Direct Install, so the old version of Magisk cannot work.

The most straightforward approach is to wipe your phone and start over.

Since you have TWRP, you might be able to use it to delete "/data/adb". Then reboot. Your v23.1 Magisk might be back. Be careful which Magisk manager app you are using.

If, instead, you try flashing the v23.1-patched boot image, and that restores Magisk and root, I would be curious to know if you can confirm that your recovery has been modified.