yashsingh1/xdaforums huggingface dataset:
[Magisk] loony_tuna:
I'm going to install Magisk, so I've opened the Magisk app and in the homescreen it says A/B No SAR Yes. What does that mean, and is it ok with it to proceed to root? (MIUI 12, Redmi Note 9 Pro)
[Magisk] Homeboy76:
It means you can use a recovery to root.

<Edit> Opps, Ramdisk=Yes means you can use a recovery to root. Thanks @pndwal :)

Yes.
[Magisk] loony_tuna:
I ha

I have no custom recovery to flash magisk root. So in this case, it is possible to do this in fastboot mode?
[Magisk] Homeboy76:
Yes.
[Magisk] loony_tuna:
Ok thanks.
[Magisk] SFCurley:
Thank you, both, @zgfg and @Didgeridoohan.
[Magisk] zgfg:
With Ramdisk=No, according to Magisk Github docs you should patch Magisk to Recovery

However, on MIUI it still usually works (I have Mi 9T, patching that way since A9 till now A11) to patch Magisk to BOOT (not to Recovery)

Therefore, you can try patching to boot img (without enabling Recovery mode).

If it doesn't report an error, flash to Boot partition - that way you will be able to use TWRP in Recovery and Magisk in Boot

If it reports an error, then patch recovery.img with Recovery mode enabled and flash to Recovery

If anything goes wrong, just flash orifinal boot img to Boot and/or original recovery.img to Recovery
[Magisk] pndwal:
Just uncheck it to try. 😉 PW
[Magisk] pndwal:
... if ramdisk = yes... PW
[Magisk] pndwal:
As above, yes... this is now official preferred method.

Please click 'Octocat' cat symbol on Magisk app home screen for Magisk main page on GitHub, and click official Installation Instruction link for most of the details you need. PW
[Magisk] Homeboy76:
You're right. :) My mistake. :(
[Magisk] loony_tuna:
Ok folks, thanks for replies. Ramdisk is Yes, so I've chosen to patch boot.img and fastboot flash it. Fingers crossed.

UPD: I have successfully flashed modified boot image via fastboot. Now I'm able to use Adaway and other useful stuff which made possible by gaining root access.
[Magisk] KRafi:
My device is Redmi 8A. Magisk Manager isn't detecting Magisk. Facing this issue not only in the latest version, but also in older versions.
[Magisk] loony_tuna:
So I'm able to open /system folder, but cannot mount it as -rw to change some system fonts. Any suggestions?
[Magisk] zgfg:
If filesystem is read-only, as usual on A11 (but can be also on A10 or even A9, depending on the firmware), that cannot be changed by root

Instead, Magisk provides systemless framework to make dynamical changes on the read-obly system, the way how Magisk modules work, Systemless hosts, etc

Consult Magisk development documentation from Github

Look into /data/adb/modules/* (supposing you have installed some Magisk modules, each one will have their folder there), and find if some folder/module contains system/* subfolder

E.g., for Systemless hosts,

hosts/system/etc/hosts is a file where AdAway writes its changes, and Magisk mounts that file to the read-only /system/etc/hosts on every reboot

You can make your own 'module' (it does not need to be installable like Magisk modules from Repo), but it will be probably easier for the beginning: find and install some module that changes the system fonts and if needed, make your own changes into its /data/adb/modules/*/system structure
[Magisk] loony_tuna:
Which of those are less bloated, EU or global? Can I flash them via fastboot?
[Magisk] pndwal:
If you mean Xiaomi.eu vs global stock, the Xiaomi.eu will be debloated as I understand that is a main aim of this custom unofficial ROM, not that I've ever used it. Bloat necessarily comes w/ official/stock. PW
[Magisk] Newbdroidd:
I don't know how none of the search engines can find anything on this, but i'm getting an error while trying to sideload magisk in twrp: "Insufficient boot partition size detected"

How do I fix this?
[Magisk] pndwal:
Without more detail, you likely just need to remove BOTH recent Magisk app and any hidden Magisk app/manager that you haven't removed previously or restored, that are conflicting. Then reinstall Magisk app. 👍 (Nb. Magisk uninstall options won't see / remove hidden app/manager.) PW
[Magisk] zgfg:
Off the official MIUI releases, there are Global and EEA - I don't know which one can be considered less bloated (btw, there is not much bloat, it mostly depends how much stuff one considers the bloat).

I would better suggest to check on XDA, for your oarticular Xiaomi device, which is preferred (and) why by users

To the other side there are unofficial Xiaomi.eu releases (btw, they are made off CN, not global or EEA).

There are Stable and Weekly - where Weekly is based on MIUI 12.5, A11 beta (if it applies to your Xiaomi model)

Generally, please find on XDA the forum for your Xiaomi model and check/ask there (Guides, Q/A sections), what are considered the best firmwares to use (it's out of the scope here; btw I have Mi 9T and I'm for months on Xiaomi.eu Weeklies, A11 beta; previously was on EEA official and Xiaomi.eu Stable)

All of them can be safely, systemlessly debloated - actually, it's not restricted to Xiaomi/MIUI firmwares/ROMs:, e.g:

https://xdaforums.com/mi-9t/how-to/magisk-module-systemless-debloater-t4180083
[Magisk] gil80:
Since updating to the latest magisk, V4A stopped processing.

I've tried using the Canary build.

Followed various instructions... nothing.

I'd appreciate if some guru here can please please help me!

Using OnePlus One, LinageOS 17.1

Thanks.
[Magisk] ineedroot69:
sadly V4A is deprecated so that's to be expected also going back to Magisk v21.4 would resolve your concern
[Magisk] gil80:
I wrote V4A as a short for viper4android, if that makes sense... how can I revert back please?
[Magisk] m0han:
this post might have something for you to try: https://xdaforums.com/t/rom-10-resu...-surya-karna-23-01-2021.4176023/post-84672305
[Magisk] zgfg:
I still successfully use V4A with Magisk Canary 22005 (and all previous versions), on my Xiaomi Mi 9T with Xiaomi.eu A11.

Used also on their official A10

Not to tricky to make it work, as in the following guide and particularly the following later post/comments

On every firmware update I have to re-do, cca 5-10 minutes (starting with disabling all audio modules and then going step by step):

https://xdaforums.com/t/guide-magisk-viperfx-for-miui-11-android-10.3994621/post-84319887

Cannot guarantee that it will work for your phone, but you can try (execute the steps exactly as described)

Screenshots:

Android, Magisk and V4A module version

V4A settings

V4A Driver Status Normal and Proccessing Yes (while playing music)
[Magisk] zzattack:
Perhaps silly question, but I'm finding some ambiguity in the Getting Started section on the github docs.

Which steps should be followed in care a device identifies with RAMDisk=YES

and

it's a Samsung with SAR=YES too? Do we then patch boot.img or follow the AP.tar patching path?
[Magisk] loony_tuna:
Hey whats up folks. Are there any special steps to perform OTA update, with installed Magisk? Should it be removed before updating?
[Magisk] zgfg:
Asked and discussed a day or two ago here
[Magisk] gil80:
didn't work for me.

Which V4A version are you using?
[Magisk] pndwal:
Above advice works for me.

Just to simplify, steps are:

After Installing ViPER4Android FX and Audio Modification Library Magisk modules from Magisk repo, Initial Driver status = Abnormal.

Next:

- Ensure Legacy mode is enabled in Settings.

- Disable Audio Modification Library module and reboot. (This will force Neon driver to reset correctly.)

- Run ViPER4Android FX, and allow Neon driver setup (incl reboot).

- Run ViPER4Android FX, --> Check: Driver status = Normal / working!

Nb. 1) Disabling Audio Modification Library module seems to reset Neon driver correctly, but needs to be done after initial ViPER4Android FX module setup.

Nb. 2) Anytime Driver status becomes 'Abnormal', simply enabling then disabling Audio Modification Library module should reset Neon driver correctly (as long as Legacy mode is also selected); no need to reinstall.

Nb. 3) It seems Audio Modification Library can be left off, or reactivated after such a reset, and Driver status remains Normal / Working.

Xiaomi Redmi Note 8T, MIUI Global 12.0.1, Android 10. 👍 PW
[Magisk] pndwal:
ViPER4Android FX from Magisk repo is 2.7.2.1 w/ Neon driver 2.5.0.4. PW
[Magisk] zgfg:
Check my post above - Idid put the screenshot. Magisk module Viper4Android FX v2.7.2.1 from Repo

And AML v4.0 also from Repo
[Magisk] ineedroot69:
I can install GLTools via browse as zip on latest Magisk previously I have no issue with it sad it's bonked
[Magisk] KRafi:
I don't have any hidden magisk app. I could never get Magisk to work on my device.
[Magisk] pndwal:
If you can detail OS/ROM, details for ramdisk, A/B , SAR from Magisk app main screen, etc, someone here can likely help you... without any clues, advice can only be general / guesswork... PW
[Magisk] pndwal:
Sorry, what? You can install? Sooo whaaaats prooobleeem? 🙃 PW
[Magisk] ineedroot69:
can't
[Magisk] pndwal:
Many commits / regression fixes, etc last few hours! (to be merged.) Thanks Magisk helpers!

PW
[Magisk] CrusardGameamos:
Hello everyone!

Two questions!

I have a Oneplus 7T Pro McLaren, and i've installe magisk without TWRP by patching and inyecting the boot img, today, i receive an OTA to upgrade from Android 10 to Android 11...

so... 1º - I opened Magisk app, and it said i don't have magisk installed O.o, but i have root access. i can access to system root, and use other root apps like adaway without any issue, but i don't see any "give root privileges" prompt, how i can fix it?

and... 2º - It's safe to upgrading from Android 10 to Android 11 with magisk installed? i mean, "install after OTA" option. (When i solve the first issue)

Thanks!
[Magisk] pndwal:
This doesn't show in Magisk repo for me (was previously there apparently).

Reports are that this mod has been sold on, and latest from original Dev don't work post Android 9:

https://xdaforums.com/t/app-2-2-gltools-1-99xda-graphic-optimizer-updated-20-3-16.2828630/ PW
[Magisk] gil80:
While I get the Normal status, it doesn't process.

I don't know what went wrong.
[Magisk] gil80:
How can I downgrade to a previous version of Magisk from 22?

I think magisk is causing me issues with viper4android.
[Magisk] zgfg:
It will process only when you start playing music.

And of course, you must enable Master limiter for speakerphone, BT - whatever you use for listening.

Open the attached screenshot
[Magisk] gil80:
oh yeah, I know that. I have it since 2015 :)

I figured it out.

I used titanium backup to trace any elements of v4a previous installations. I think I had a script that was messing up everything.

I removed all traces of v4a, followed the instructions and it's working, but with legacy mode only.

thanks.
[Magisk] pndwal:
Ok...

Have you turned on Master limiter (ie. On button), and have NewPipe or other background-capable audio app playing in the background?

If I don't do these two things, I see 'Processing: No' also. PW

Edit: As above, but see you've fixed it anyway. 👍
[Magisk] zgfg:
He made V4A working - post above yours

Btw, I use YouTube Vanced (root) to play in the background

And one thing I was always curious about, even when V4A is Processing, SE Linux is Enforcing (which is good)
[Magisk] pndwal:
... And the results are in...

Time for testing, all those w/ recent Magisk issues, especially module loading, processes not seen in MagiskHide, MicroG SafetyNet (that's been a while coming - hope it works!).

The early Canary catches the worm! PW
[Magisk] pndwal:
Latest Canary Changelog, including Release Notes:​

​

Magisk (66e30a77) (22006)

[App] Fix app crashing when download + install modules

[MagiskHide] Prevent possible deadlock when signal arrives

[MagiskHide] Partial match process names if necessary

[MagiskHide] Don't include MicroG SafetyNet process by default

[MagiskBoot] Prevent possible integer overflow

[General] Many scripts updates fixing regressions

Diffs to v22.0​

[App] Prevent multiple installation sessions running in parallel

[App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images

[General] Proper cgroup migration implementation

[General] Rewrite log writer from scratch, should resolve any crashes and deadlock

[General] Many scripts updates fixing regressions

[MagiskHide] Prevent possible deadlock when signal arrives

[MagiskHide] Partial match process names if necessary

[MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images

[MagiskBoot] Properly strip out data encryption flags

[MagiskBoot] Prevent possible integer overflow

[MagiskInit] Fix sepolicy.rule mounting strategy
[Magisk] pndwal:
Yeah, saw that... 'n you're too quick! 😉

Yes, I've used it in past too, but kind got used to / to like NewPipe of late... Seems either choice must be updated regularly however.

I haven't used subscriptions, but played with MicroG GSM component to enable this in Vanced just for fun... Now I notice NewPipe has Import Subscription function... May be of interest to many... or a few at least.

Yeah, I'd heard enforcing fix came a while back.

Thanks for the su command trick though... I tried getenforce in Terminal Emulator a while back and thought permission dental was a unique issue!

I know precious little about such tools, but I'm sure I'll use 'su' again. Makes perfect sense. PW
[Magisk] zgfg:
Modules installation is fixed (only bug I had with 22005)

And btw, good that it patches now by imprinting Magisk version into the image name, like:

magisk_patched-22006_MAqy9.img
[Magisk] pndwal:
Funny I never had this on RN8T... perhaps it was only w/ app hidden, etc. PW
[Magisk] zgfg:
Not hidden. It was a regression bug in 22005:

Magisk app does not install modules in the latest Canary build · Issue #4044 · topjohnwu/Magisk

Device: Poco M3 Android version: 10 Magisk version name: f152b4c Magisk version code: 22005 The problem of the Magisk installation screen not appearing was fixed in the last Canary build, but now i...

github.com
[Magisk] thameme:
hello, i need help with my poco x3 the problem is that it's really unstable this happened after i flashed magisk can anyone help?
[Magisk] pndwal:
Ah yes, I did have that, but not Impossible-to-install thru app issue by author. Didn't think much about it as Installation would continue on clicking completed download notification... PW
[Magisk] ineedroot69:
ahhh i guess i try to install Magisk Canary and see if i can now install GLTools via zip
[Magisk] ineedroot69:
you need to be more specific what do you mean by unstable?
[Magisk] thameme:
Apps don't open, random reboots.
[Magisk] thameme:
i can access to fastboot though
[Magisk] ineedroot69:
well that's really unstable 😂
[Magisk] ineedroot69:
ye just casually watching some youtube video before going to sleep you know the usual stuff
[Magisk] thameme:
cool
[Magisk] ineedroot69:
i have depression
[Magisk] zgfg:
Guys, this is really not a Telegram group

Btw, in 22006 search for modules in Repo works now
[Magisk] Hacker432:
What the heck happened in v22? It was super easy to install magisk
[Magisk] pndwal:
@zgfg, did you get ViPER4Android FX going again?... Not so simple for me this time. 🙁 PW
[Magisk] zgfg:
I just flashed my boot img patched by the new 20006 and V4A is still Normal and Processing

That's usually the case when I update Magisk - I don't need to re-do V4A

Only when I update the firmware - if Xiaomi.eu weekly comes this afternoon/evening, I'll have to redo (disable/enable AML and V4A, plus those few little things)
[Magisk] Lord Sithek:
You have to be very patient doing this once per week (if I understood correctly) :sneaky:

Just wonder: Did you try this solution: https://xdaforums.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/post-84121895

I use weeklies on Mi Note 10 and with this fix I don't need to do anything but reinstalling Magisk 🙂

PS. Granted, I don't know much about how this fix actually works 😅
[Magisk] zgfg:
Interesting

But I see the same ten sepolicy patches declared in the sepolicy.rule file (in the same V4A module folder).

IMO, Magisk should similarly take care to execute them on each reboot

Can you compare your modified post-fs-data.sh against the sepolicy.rule

In the first you will have:

magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'

that should be equivalent to the second file:

allow audioserver audioserver_tmpfs file { read write execute }

and the same for the other nine sepolicy patches
[Magisk] Lord Sithek:
Looks like you're right.

I don't know how, but I know it works 😅
[Magisk] pndwal:
Yes, I thought it should be the same using Direct Install, but Neon status was 'Abnormal' after, and forcing driver install by disabling AML (does force Install) doesn't fix 'Abnormal' any longer (with Legacy mode set).

This method fixed this every time before update, so guess there may be new regression with Magisk this time. Uninstalling both ViPER4Android and AML and starting from scratch doesn't work either for me...

UPDATE:

HOWEVER it looks like SEPolicy is the likely problem; it's broken in 22006! - Path to SEPolicy rules is not created, etc:

sepolicy wrong status on latest canary · Issue #4098 · topjohnwu/Magisk

On latest version its starts showing On LSPosed that message. API version 93 Framework version v1.3.4 (5501) Manager version v1.3.4 (5501) System version 11 (API 30) Device Samsung SM-G996B System ...

github.com

... BUT there's already a fix as of 30 min ago:

https://github.com/topjohnwu/Magisk/pull/4104

Hopefully this will sort ViPER4Android Neon driver fix for us!

It will hopefully fix Busybox issues, and make Riru / EdXposed / LSPosed users etc happy too! 😃

Looking forward to snappy Canary Update! PW
[Magisk] wedgehog:
Are there any bug reports regarding the Xiaomi Mi Note 10 latest firmware for global (MIUI 12.1.2, Android 11, 12.1.2.0.RFDMIXM) which was just released?

I've just updated from the former version (which was based on Android 10) which had no magisk problems what so ever.

Magisk can't be installed and the system thereafter booted however I've tried - installing from TWRP, or from magisk app by patching either recovery.img or boot.img and thereafter fastboot flashing either of the patched image. Whichever install method results in the system refusing to boot - it sits on MIUI boot screen for a minute or to, then crashes back to recovery. Reflashing untouched recovery.img or boot.img restores boot (but off course disables magisk again).

I've tried with magisk 22.0, 21.0-21.4 and latest canary (22006).

Have anyone else encountered the same problems on this firmware, or maybe on MIUI 12.X on Android 11 on other xiaomi devices? Are there any solutions or something else to try?

I've also searched the Mi Note 10 forums herr on xda but can't find anything regarding this, same on the https://xiaomi.eu/ forums.
[Magisk] ineedroot69:
screenshot your Magisk manager
[Magisk] wedgehog:
View attachment 5260593

Latest canary which is the last one I've tried (with recovery.img, restore, then boot.img, then restore, then with TWRP (rename to zip), then restore).
[Magisk] pndwal:
Have you tried patching/flashing boot image (image for boot if successful previously, or recovery) from fastboot with stock recovery intact (fully restored ROM, only mod = bootloader unlocked)?

There were many reports of Magisk failing to boot on early beta Android 11 w/ custom recovery, so might be worth a shot. PW
[Magisk] casouzaj:
Is the Magisk app residing in the internal storage? Otherwise, move it to there!
[Magisk] ineedroot69:
SAR is Yes and Ramdisk is No well that's like fire and ice it would be really tricky for your running Magisk

read this https://topjohnwu.github.io/Magisk/install.html

specially this since you have Ramdisk as No https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
[Magisk] wedgehog:
Yes, I've tried both patching boot.img and flashing that, then restore original boot.img because no proper boot, and then recovery.img and then restoring original recovery.img because of no proper boot.

The patched boot.img (and second attempt patched recovery.img) where flashed with fastboot. I've not tried flashing them with TWRP - I'll try this later today.

Custom recovery have not been installed, IE the device have had stock recovery.img through all my attempts. TWRP booted through cable to computer and fastboot boot twrp.img .

If you mean installed as an app in normal /data then yes. Through my attempts I have NOT "installed" it by flashing or patching in the magisk.apk in the system rom / system folder or something like that.

Yes, I've read those instructions too - therefore I've also tried patching recovery.img in all my attempts with Magisk 22.0 (then 21.0-21.4, then canary). Before trying with recover.img I've also off course restored boot.img and then booted my phone normaly before trying again with recovery.img.

Really strange this. Before the upgrade to MIUI 12.1.2, Android 11, 12.1.2.0.RFDMIXM, which is the first upgrade to Android 11, I've never had any problems with just flashing magisk.zip or magisk_apk_renamed_to_.zip with my Mi Note 10 from TWRP - either TWRP installed as recovery.img or with stock recovery.img and booted TWRP through fastboot. Unfortunately I can't go back to MIUI 12.0 Android 10 as a downgrade will risk a brick (read that on another thread regarding the Mi Note 10) to check which status Magisk App reported regarding SAR and Ramdisk before the upgrade. Also really strange that I can't find ANY reports from other users with the same phone. Android 11 and MIUI 12.1=< have been available a really long time for users using other regions than global and/or using stock beta roms.
[Magisk] pndwal:
Seems problem is getting patched image to boot.

On many (all?) Xiaomi type III devices, boot.img can be patched with Magisk and successfully booted despite FACTORY ramdisk = No. (Magisk adds basic ramdisk to image with Magisk root if it's missing. This generally won't help as most type III devices have incompatible bootloaders, but it seems this function was added when it became apparent that some devices, Xiaomi etc, retain bootloader/boot.img-ramdisk compatibility despite being unused in OEM booting.) PW
[Magisk] pndwal:
Patched boot.img with Recovery Mode UNCHECKED right?

I'd try w/ TWRP fastboot booted only for best chance.

Assuming you had stock recovery when taking OTA too then?

I'd try with canary 22005 too, as canary has many recent fixes, but 22006 does have some major issues / regressions currently being addressed.

Wouldn't bother going back either; Magisk status would have been the same, SAR, A only, no (factory) ramdisk. I've explained in post above why Magisk in boot.img (incl. by recovery zip Installation method) works (normally) for your device despite ramdisk = no.

Hope something here helps, PW