yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
You do not mention installing Magisk after "upgrading" to Android 11. Samsung probably replaced your boot and recovery partitions, so after the change to Android 11, there is no Magisk. Even if Samsung did not destroy your /data, so you still have a Magisk Manager app.

You may need to unlock your bootloader again. You may have been "upgraded" to a bootloader that does not allow unsigned images (Samsung's lawyers have a creative interpretation of the phrase "unlocked bootloader".) If you install Magisk again, it may try to use the modules you had installed, and they may not work with Android 11.
[Magisk] ipdev:
Sorry all for some OT. ;)

I was referring more to what is overlaid into system.

mModule_sGapps [system] - GitHub - Link

This is what a normal basic/core flashable GApps package installs into system.

Since I was only using it to test GSI(s), I only trimmed it down as much as I had time for.

Could be trimmed down a bit more. ;)

---

I never ran into an issue when I was testing with mModule_sGapps active.

I had a few things on deck to fix.

I ran out of time to test GSI(s) and never looked into updating or fixing the small and big versions of mModule_sGapp. 🙃

Found my post in MHPC thread. Post # 3,594​

The Caution note I added was to warn users about a mismatch and/or when the core is missing.

This would be the same as updating a custom ROM (system) and GApps not being re-installed to system properly.

The permissions are lost and/or the app (update) becomes a user-app instead of a system-app (different permissions).​

Some times you can get away with it (debloating) but, you have to be careful for the same reason.

Bootloop and/or an infinite boot.

Cheers. :cowboy:
[Magisk] UltimateRayon:
Hi, can anyone help me?

I've magisk 23 stable version installed but my WhatsApp can't permit google drive for backing up data. The screen keeps loading where I have to allow for the permission
[Magisk] pndwal:
Yes, and I understood that (it demonstrates GApps setup well) / agree entirely / thank you for the extra clarity / insight! 😉

And while you weren't recommending using these systemless GApps, my comment was just a general caution to any considering doing so; just in case!

Out of interest, did Google Apps and any other apps calling SafetyNet API (w MagiskHide on) work fine with your systemless GApps?... Any special considerations to make it work with MagiskHide?

Yup, point taken too; core is in /system and may be corrupted / removed by a ROM update, debloating etc. Updated apps moved to /data and other data in /cache or /data may remain and cause issues if not manually / properly removed seperately.

Nb. I understand that this was meant to illustrate GApps installation in case of confusion.

It also demonstrates that original users problem caused by flashing Magisk-patched zip is NOT caused by such a corruption of core files or mismatch!

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

I am assuming Magisk flash or settings (hide, etc) are the source of Play services access issue in this case, or somehow Play services data / cache got corruped (simply clearing these may have fixed installation).

👍 PW
[Magisk] pndwal:
Please say device / ROM. There are various issues / fixes for WhatsApp on custom ROMs. PW
[Magisk] nostraslo:
Hmm, bootloader is still unlocked. I tried to installed Magisk again at Android 11, but nothing happened.

How should I install Magisk again ? Can you describe or post a video, please.
[Magisk] J.Michael:
I do not have Android 11. I have Android 9 on an SM-T290 (tablet). When I installed Magisk, I used @topjohnwu's instructions, with a hiccup to further modify the patched file -- a workaround developed by @gcrutchr for my device. (So, I used Odin to flash the modifications.)

I don't think you should allow automatic updating.

You need to search this thread and your device thread to find out if Magisk can work with Android 11 on your device.

If Magisk is installed in recovery, you might have installed Magisk correctly. Try booting towards recovery a lot of times. It's a really finicky step.
[Magisk] pndwal:
I'm guessing you must have flashed Magisk to recovery to root previously in accord with official Installation Instruction for Samsung devices.

You should therefore understand that you can't update using OTA any longer, so you should have downloaded complete new ROM and followed the same instructions again with the following exceptions: Use images from the new ROM, and use HOME_CSC instead is CSC to avoid factory reset. (ie patch AP .tar then flash magisk_patched.tar as AP together with BL, CP, and HOME_CSC. (Make sure “Recovery Mode” is checked in options.)

If that is in fact what you did / tried, you should already have root, but, of course on you device standard bootup doesn't use ramdisk and boots system without Magisk root. Booting with the amended use-recovery-to-boot-system-with-Magisk key combo and method for One UI 3.0 I mentioned above

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

will boot rooted system again.

If you didn't follow official Magisk Samsung SAR device "Upgrading the OS" section and flashed stock AP .tar file (un-patched), it seems you will need to do 'initial' Magisk install again, which requires a full data wipe.

You have Magisk app installed. Click the GitHub 'OctoCat' cat symbol for Magisk Home page, then 'Installation Instruction'. Scroll down to 'Samsung (System-as-root)'.

If you updated ROM without factory reset over previous Magisk installation (not uninstalled), modules will load again on booting with Magisk, and if any are incompatible with Android 11 you will likely get bootloop initially as a member told you above.

In this case, search for Safe Mode key combo (nb. for One UI 3.0 it will likely be the same as before with additional requirement to connect PC or earphone to USB), boot to Safe Mode which will disable Magisk module, then boot immediately to system again using amended use-recovery-to-boot-system-with-Magisk key combo and method for One UI 3.0. After this you should have system with Magisk root; compatible modules can be enabled and others uninstalled.

🤠 PW
[Magisk] bonedriven:
No, LOS does not provide boot.img.

Thanks above for all the help as I managed to finally install Magisk.
[Magisk] 3mel:
hello folks, I've got a question related pre V22 versions of magisk I need help with.

I have a cheap android TV box called a Yagala T95

https://www.amazon.co.uk/Quad-core-...eywords=yagala+T95+h616&qid=1627822904&sr=8-2

the box comes pre rooted via a root switch in it's settings but without a superSU app. a few of us from the allwinner forum have rooted with older versions of magisk because it's better than having any app that asks for root just getting it on a Chinese box thrown together in the sloppiest way like this thing is.

side note: don't buy a cheap TV box unless it has an AMLogic or RockChip SoC!

anyway, because it came rooted you can install magisk manager and have it flash magisk and then turn off the built-in root.

the problem is this box has zero custom recovery options.

if you factory reset and reinstall magisk manager like I have, you have root for your apps but magisk will ask for the additional setup every time and modules won't work. it asks that you reflash magisk (20.4 in this case).

so my question, updating the magisk app to v22 isn't going to work for me is it ? that's going to want to patch firmware and have me flash it isn't it ?

is there a way to either remove magisk without a recovery to flash the uninstall zip or is it possible to use something like flashify to flash magisk 20.4.zip ? seeing as the box is actually rooted ?

I have no backups and currently no way to reflash it's firmware if it goes wrong hence my caution and need of advice. TIA
[Magisk] justDave:
The recovery image is the boot image on a/b devices
[Magisk] BillGoss:
Not so on my OnePlus 8T.
[Magisk] justDave:
I thought he was talking about a Pixel 2. Interesting about the OnePlus 8T though. Why does each vendor have to do things differently :-(

I wish the outsides of the phones showed more imagination and the insides less ;-)
[Magisk] pndwal:
John's explanation:

This marked the introduction of "Method B - Legacy SAR" boot method (ie. SAR in the official sense), and included Pixel 1 and 2. Pixel 3 and 3a.

Numerous A/B as well as A-only (these launched without ramdisk in boot partition necessitating a new Magisk in Recovery option, although some devices do have bootloader support for such ramdisk to be added later to support Magisk in Boot, eg Xiaomi) "Method B" Legacy SAR devices followed.

Later, Google introduced what John calls "Method C - 2SI ramdisk SAR" (not officially considered SAR, but a form of SAR for Magisk's purposes, therefore in Magisk SAR = Yes) A/B seamless update devices including updated Pixel 3 and 3a (retrofitted to API Level 29, apparently the only devices to convert from B boot method to C) and A/B devices launched with API Level 29+.

Also, A-only devices launched with API Level 29+ are type C, as are the A-only Method A - Legacy ramdisk LV (Launch Version) <28 devices that are converted to boot method C with upgrades to API Level 29+ Android.

Google calls this "USES_RECOVERY_AS_BOOT" officially. The new method was necessary due to new Dynamic Partition scheme.

Further, while boot method C devices generally use a hybrid ramdisk in boot partition to boot into Android or recovery,

Also,

I guess late models also come with recovery partitions and match the Type I / boot method A devices converted to boot method C, and that these likely have both boot and recovery ramdisks.

https://topjohnwu.github.io/Magisk/boot.html#some-history

My conclusion:

Generally it is true that A/B devices use recovery in boot partition. This is almost certainly always true of official SAR A/B devices including the Pixel 2 in question.

With newer 2SI A/B devices (I think only High End / flagship models) there are exceptions to this as Google has made provision for dual recovery partitions. Seems OnePlus 8T is one such device.

🤠 PW
[Magisk] UltimateRayon:
Device: Pixel XL

Rom: Custom (Pixel Experience 11)
[Magisk] Didgeridoohan:
If your device is rooted and installing Magisk 20.4 through the app works, things should in theory still work the same with later releases.

If you can run Flashify you could use the uninstall zip or the Magisk zip there, and if you can't use Flashify you might have better luck with Franco's kernel manager.

The caveat is that there's of course always possibilities of things going wrong. Nobody can give you any kind of guarantee of the opposite... If you have no way of restoring your device when (not if) there's a failure you're just going to have to decide if it's worth the risk...
[Magisk] pndwal:
@3mel

And if those methods work (and assuming modules can also be flashed), shouldn't both Magisk named 'uninstall.zip' and 'magisk-xx.zip' work by flashing from Magisk App like a module also? - May even have a better chance of success. PW
[Magisk] Didgeridoohan:
If the modules tab is available, that would work. But I did not think the module tab is available if Magisk isn't installed, hence I did not mention that option... I would have to test that to confirm though.
[Magisk] pndwal:
It would appear from this post from same user:

https://xdaforums.com/t/t95-allwinner-h616-tv-box.4089091/post-83997983

that access to modules is available, although other posts there indicate there may be issues with some modules.

Further, it appears user was able to replace existing SU with Magisk 20.4 some time ago when this was current. He was unsure at the time if he had 2 root solutions at once as he apparently had conflicts, but, by turning off the native ROM's 'root switch' setting, Magisk apparently began working without conflicts / issues. He reported Systemless Hosts module was working fine.

https://xdaforums.com/t/t95-allwinner-h616-tv-box.4089091/post-83357191

I found this thread yesterday while trying to get my head around the issue presented, partly because not enough information was given here. I hadn't responded because I still haven't understood enough about this setup, but it does appear there is no glaring obstacle to updating Magisk, even simply taking update by direct install. (DON'T update App without unhiding / restoring if hidden, and DON'T update Magisk mask without disabling all modules... Just in case! 😉 )

This said, I'd still be wary as I'm unsure about ease of un-bricking... but I know I'd go for it as long as I was confident I could still clean flash ROM to recover. PW
[Magisk] pndwal:
Do you have device settings permission for WhatsApp like this?

I don't think it's a Magisk problem, although I initially hid root from WhatsApp in MagiskHide list and cleared data after that, but I have stock MIUI ROM.

If storage permission is 'allowed' you could try simply clearing WhatsApp cache: fixes Issues for some. Also, confirm Google drive is working without restrictions.

Also, Google "WhatsApp custom ROM" if you haven't already... This result may help:

https://xdaforums.com/t/fix-for-whatsapp-not-working-in-custom-roms.3760240/

Many other pages have helpful tips...

Official tips here:

https://faq.whatsapp.com/android/tr...ate-or-restore-a-google-drive-backup/?lang=en

😛 PW
[Magisk] 3mel:
@Didgeridoohan @pndwal thanks for the suggestions, just to be more clear on what happened...

I flashed magisk via magisk manager first time around because I had janky OEM root. after a recent reset most of what was flashed from v20.4 still remained. installing magisk manager showed 20.4 as installed and SU was working for granting apps permission but the module side was non functional. it would download modules and try to install them and then tell me I needed to flash 20.4...

some parts of that 1st manager flash survived the reset, others seemingly not so. trying to uninstall via the manager didn't take me back to a blank slate like I hoped (so I could repeat that 1st flash again). I'm in limbo, rooted for root access but not for magisk modules. every time I open the manager it asks for the download of additional setup files that never work. so I need to reflash somehow.

flashify installs and reviews say it still works for android 10 users but I've no idea how it would cope with a more complicated (presumably) script. I have Ex Kernel manager that has a script manager and a flasher. I just don't know if these are good gambles worth considering.
[Magisk] J.Michael:
When you had Magisk 20.4 installed, did you use MagiskHide? Did you rename the Manager?

Have you re-enabled the OEM root?
[Magisk] 3mel:
all is well now with @Didgeridoohan and @pndwal's help...

I hadn't used magisk hide previously no. I managed to fix the issue by updating magisk manager.

first I tried to flash a magisk uninstall zip via Ex Kernel manager as that sounded safest if it didn't work.

it said it had completed the script with success but upon reboot the manager was showing 20.4 still installed.

I reactivated the OEM root switch and updated the manager app to v22.01 I think, then I updated magisk itself and that has worked completely. I have a couple of modules installed already...

many thanks gents
[Magisk] pndwal:
Great! I was going to say sounded like nothing seemed wrong with Magisk mask itself, but likely reset corrupted Magisk data in /data/adb which should be fixed by reinstalling Magisk. (Sometimes needs deletion of files in /data/adb.)

Happy update worked; should be able to use latest 23.0 or 23001 now.

Do you need to restart after changing OEM root switch? Not sure what that enables exactly... guess you disabled after update. I was wondering about conflicting SU in boot ramdisk... I guess OEM could have used Magisk SU anyway... A root detection app may have given info.

In case you haven't read it, @Didgeridoohan has great (comprehensive) overview of issues / fixes here:

https://www.didgeridoohan.com/magisk/HomePage

(Time to 'Updatefor Magisk v23.0(23000)'? 😛 ) PW
[Magisk] 3mel:
regarding root switch, yeah once I've got magisk installed I turn it off which does reboot the box.

I might just stick with things the way they are now.

this TV box and similar boxes don't get updates from the so called manufacturers. one company produces the allwinner SoC board and ships it out to other companies who put a case and a kanged, limited OS on to it and call android TV (which it isn't).

right now it's running better than it ever has and I'm not gonna jinx it further.

thanks for what you guys do here!
[Magisk] AquilaDroid:
New topic/problem, probably discussed here before but in six hours of searching/trying things I'm unable to get Magisk installed on Pixel 5 after updating to August update. I forgot (I'm 80 yo, so am allowed to do that!) to delete/uninstall the few modules I had installed which is probably the cause of the boot loops after flashing "magisk_patched-23000_v5rmk.img". I've uninstalled everything, rebooted, installed Magisk Manager, patched boot image and flashed, etc. several times but can't get Magisk installed. Fortunately, I am able to flash the stock boot.img and get back to a working phone, but nothing I've tried has gotten Magisk to install.

I did try the "open a shell and type: adb wait-for-device shell magisk --remove-modules" but nothing was found at that stage.

Any and all suggestions appreciated!
[Magisk] zgfg:
Yes, it was asked/answered several times but let it be answered again 🤩

Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules

You have to flash your patched boot.img, then

a) Reboott to Android Safe mode, then reboot again to 'normal' mode.

All modules will be disabled but also you will have to re-enable Magisk Hide again

b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)

Then, Magisk will disable the modules and you can manage them from Magisk app (emable or uninstall)

You can find it also in a chapter about the modules in Magisk Wiki, available from Magisk Github (linked from Magisk apo)
[Magisk] pndwal:
Assuming you are sure you are patching image from updated ROM now in use, if you still have bootloop after flashing this I'd simply try boot to Safe Mode mentioned above to disable modules. Compatible modules can be enabled again later, others removed.

Also, did you have Magisk App/Manager hidden previously? If so, Magisk is likely actually installed despite N/A showing as long as flashing Magisk-patched image succeeded.

Especially if coming from pre 22.0, you need to UnHide / restore Magisk Manager before updating Manager / App.

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

In practice, failure to do this has also been an issue even updating from later 'compatible' builds.

Now, you simply need to remove hidden Manager app (found in device settings, Manage apps, likely named 'settings' if you didn't chose a custom name) as well as new App, then reinstall new App to overcome conflicts / initialise App properly.

Settings / modules etc are safe (don't run Uninstall options from within App or TWRP). PW
[Magisk] AquilaDroid:
No, I didn't have Magisk hidden. Thanks for all your support here! I recognize you and @zgfg from an issue I had several years ago!
[Magisk] pndwal:
Try booting to safe mode then. Next, simply reboot to system. This can be done before flashing Magisk-patched image again.

One guide here:

https://www.hardreset.info/devices/google/google-pixel-5/safe-mode/ PW
[Magisk] AquilaDroid:
I'll give "a" a try in the morning. It's a Pixel 5 - no TWRP unfortunately (I still miss it even after three Pixel phones!). Thanks for all your support here!
[Magisk] m0han:
Thanks for your presence here! I guess you're an inspiration for many.
[Magisk] jons99:
read this

https://xdaforums.com/t/bootloop-on-magisk-with-android-11.4170091/#post-83613203

also twrp

https://xdaforums.com/t/recovery-twrp-3-5-0_10-0-teamwin-recovery-project-redfin-testing.4240711/
[Magisk] AquilaDroid:
Just want to give the history of how I got here - I went through the normal monthly update routine (with the exception of removing all Magisk modules before starting). At one point I got the ugly screen with the option to "try again" or WIPE data. I made one last attempt to reflash the update and boot.img which led me to the "crippled" state I'm in now. Here's the result of this mornings (unsuccessful) efforts:

I booted to Safe mode, rebooted to normal mode, restarted and re-created magisk_patched file. (discovered that safe mode removes home screen widgets...) Flashed as below:

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot reboot

Rebooting OKAY [ 0.044s]

Finished. Total time: 0.055s

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb reboot bootloader

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot flash boot "C:\Users\aquil\Desktop\August Platform Tools\platform-tools\magisk_patched-23000_0Gs4k.img"

Sending 'boot_b' (98304 KB) OKAY [ 2.373s]

Writing 'boot_b' OKAY [ 0.340s]

Finished. Total time: 3.822s

Phone stuck with "G" logo

Flashed stock boot.img extracted from August Redfin factory image:

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot reboot

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot flash boot "C:\Users\aquil\Desktop\August Platform Tools\platform-tools\image-redfin-rq3a.210805.001.a1\boot.img"

Sending 'boot_b' (98304 KB) OKAY [ 2.363s]

Writing 'boot_b' OKAY [ 0.478s]

Finished. Total time: 3.942s

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot reboot

Rebooting OKAY [ 0.031s]

Finished. Total time: 0.062s

Phone boots normally.

I've been flashing roms (I miss you TWRP!) for years, never had so many issues before Magisk (which I love, and hope the "Boss" comes back!). I hope I'm missing something simple...

And, thanks for the support!
[Magisk] zgfg:
Sorry, I don't understand one thing - did you flash the patched boot img BEFORE booting to Safe mode?

That is the required trick - Magisk recognizes that you are booting to Safe mode and it is a signal for Magisk to disable all modules

If you booted to Safe mode with the stock boot img, then no use - Magisk is not initualizing, nobody will disable modules and next time you boot with Magisk, an enabled module will again cause the bootloop
[Magisk] vandyman:
There is a fairly new TWRP for redfin, Pixel 5. Just look in the Pixel 5 thread for it.
[Magisk] AquilaDroid:
I've tried several times, but when I flash the Magisk patched img it will never boot into safe mode when I press the vol up & down buttons (just sits there with the "G" and dim white line underneath). When I flash the stock boot.img it always enters safe mode . I've tried each one several times.

Maybe I should look into TWRP or is this indicative of a problem that will eventually require a wipe (NOOOOOOOOOOOOO!)?

Thanks for hanging in there...
[Magisk] J.Michael:
That post from @Incanity describes

flash unpatched boot image

boot to safe mode

interrupt booting to safe mode to flash patched boot image

resume booting to safe mode, so you end up in safe mode with Magisk installed

Just having it look like it works while in safe mode with Magisk is probably a good sign.

Then you reboot and hope to end up in normal mode with Magisk, but with all modules disabled.

It might be that when you are in safe mode with Magisk, you will be able to use Magisk Manager to confirm that Magisk is installed. You might have root privilege, and therefore be able to remove the modules (the /data/adb/modules directory tree). I don't know what's available in safe mode.