yashsingh1/xdaforums huggingface dataset:
[Magisk] dcarvil:
The size of the patched image is not an issue. Magisk 21.x no longer removes the zero padding in the patched image, so the patched image size should be the same as the original boot image.

Don't know why you are loosing root, but you will probably find the answer by searching this forum.
[Magisk] akxak:
With the update to Manager 8.0.7, the issue installing the Magisk update (boot image not recognized) is solved, I could install 21.4 without problems
[Magisk] zgfg:
Tried but did not work for me. After the clean installation of V4A I have again Status Abnormal

Btw, when you run V4A app, it installs the module first (it pops-up and after that V4A module is listed in /data/adb), hence it becomes the same as if first installing V4A module, then running the app

Sorry, I'm not going to compromise security with Permissive SELinux (also, not sure is it applicable for A11)
[Magisk] zgfg:
Yeah, I know - but if we follow his own rules of reporting the issues to Github, there will be also no fixes/improvements

I.e., when I open to report the issue with V4A having Status Abnormal since Magisk v21203 (with older Magisk versions it was ok for me), his instructions say as on the screenshot: Do not open issues if you have any module installed, otherwise the issue will be closed.

So how could I open an issue about the problem with V4A module?!

And what would be the purpuse for me of installing Magisk with no modules, etc - just to enjoy looking into the Root checker status: Your phone is rooted🤩

I need a full package, Magisk with some useful modules and root apps (minimal for me: V4A, AdAway, YouTube Vanced)

Btw, YTV root issue was fixed today. Vanced updated their Vanced Manager to v2.2.1 and with today's Magisk v21.4 it properly installs YTV root
[Magisk] zgfg:
You can also repatch your image previously patched with an older version of Magisk (in essence, this is like updating Magisk over the previously patched Magisk; not patching first time into the clean/original image)

That is, when you are selecting the image to patch, do not take stock image (big one) but some older image that was patched with the older version of Magisk and shrinked in size.

New Magisk will repatch that image, and it will remain small (without the MBs of padded zeroes).

I'm doing that since the time when Magisk started to leave these padded zeroes in the pstched images

The other way would be manually removing the padded zeroes by using od (to find where zeroes start) and dd (to cut off) commands in Terminal.

I did that too, but the first method is more elegant (second is also prone to error if you e.g. copy/,paste the wrong number of bytes when putting to dd command)
[Magisk] zgfg:
I already had A11 and Magisk versions up to v21202 Canary and everything worked correctly.

Things broke (as I explained, in my post) when I upgraded from Magisk 21202 to Magisk v21203 - keeping my same A11 and my same V4A that worked correctly with 21202

But if/when I simply flash my boot image patched with Magisk v21202 (I always patch images and keep them to simply be able to go forth and back through Magisk versions if i observe a new problem) then everything works fine again

Therefore, problem is not in V4A not adapted to A11, and 'solution' is not going to non-root versions or whatever "A11 adoption problem")?!

Problem simply became with Magisk update from 21202 to 21203 (Magisk Changelog says: f2fs changes)
[Magisk] sirucato:
Hello.

Yesterday I updated Magisk to v.21.3 directly with Magisk Manager.

Since then I'm having problems with some apps and I notice that a new version of Magisk was release just to fix this problem.

When I try to install the v.21.4 with the Magisk Manager there is an option unchecked but I do not know if I have to check it or no.

Keep AVB 2.0/dm-verity

I do not know what is this. When I update to v.23.1 I did not have that option, was direct but now when I want to update to 21.4 from Magisk Manager I have this option and I do not know what to do.

Thanks
[Magisk] zgfg:
Good news before the bed time - the same V4A FX module (on my same A11) works fine again upon updating Magisk to v21401

(Without 'non-root drivers', forcing SeLinux to Permisive or anthing else/additional -just like it worked up to Magisk v21202)

Hence both issues I started to have with v21203, V4A and YTV are resolved/back to normal with the latest Magisk 21.4 👍👍👍
[Magisk] pndwal:
Yeah, interesting problem.

Breaking device specific functionality, including proprietary camera features, is expected with mods that change props, especially model props.

Since you appear to be free of these, I have no good advice sorry... Unless call recorder fix alters props (try with disabled).

You could try disabling Systemless Hosts too, as this has caused various problems... Others may have more. PW
[Magisk] daddylonglegs:
I am having a bit of a crisis here and am hoping someone can help.

I've installed Magisk a ton of times on my Pixel 1 and even my current Pixel 3A without issue, but something happened today when I tried to update.

I was on Android 10 with Magisk running fine. I decided I wanted to upgrade to Android 11, so I downloaded the full firmware, edited the .bat file to remove the -w (wipe) flag, and ran it. Everything went fine and my phone was on Android 11 without issue.

Then I went into Magisk with the intent to re-root my phone. I was on the latest version of Magisk and I had it patch the boot.img file.

I got the patched_boot.img like I always do from my phone and put it on my Windows PC. I manually typed "fastboot flash boot magisk_patched.img".

Ever since then my phone has stopped working. The error I get is NO VALID SLOT TO BOOT

I have tried EVERYTHING. I re-flashed the stock boot.img. NO VALID SLOT TO BOOT. I tried downgrading to Android 10 again. NO VALID SLOT TO BOOT. I tried flashing the stock boot to both A and B, as well as installing Android 10 to both A and B as well. NO VALID SLOT TO BOOT.

I am out of ideas. I can't even get my phone to boot after re-installing the OS! I've read this issue is because I wasn't on the "canary" version of Magisk and the version I was on is known to corrupt boot files??

If anyone can please help me get my phone back and working again I would really appreciate it. I am kind of screwed without it. Again I am not a noob; I've used Magisk a bunch of times but apparently this is a known issue with the version I was using or something. I am desperate.

EDIT: Sideloading the OTA for some reason worked. I have no idea why that would work when the full firmware flash didn't, but it did.

Now I'd just like to know how to install Magisk without this happening again :)
[Magisk] :
Hit the bin icon. and be patient because it will optimise apps, like first run.

Its not here on mine because ive removed it ;p
[Magisk] Dante63:
I updated again with the latest 2021.1.17 Magisk v21.4, it kinda fixed it..? Or maybe I got lucky, I don't know...

I kept installing and uninstalling camera app and suddenly camera is working again, had a problem with nearby service too so I uninstalled it and reinstalled it and it's fine as well, no issues now...
[Magisk] Born<ICs:
Thank you for the zip. Works fine after clearing Google apps cache and reboot. Also made sure Magisk hide boxes were ticked like mentioned on pg 2169 or so.
[Magisk] daddylonglegs:
Any chance you can do this with Android 11 for the 3a? I keep getting NO VALID SLOT TO BOOT every time I flash magisk.
[Magisk] IlyaKol:
Here is the hardware off post:

Magisk General Support / Discussion | XDA Developers Forums (xda-developers.com)
[Magisk] daddylonglegs:
How do I know if I need to install that? Is it only certain phones or something?
[Magisk] pndwal:
You don't need it.

It was first fix for changing evalType from hardware to basic, and the basis for more complete MagiskHide Props Config 'Force Basic' fix, but neither work after new Google server end changes.

Solution now is Universal SafetyNet Fix module... Please read back. PW
[Magisk] pndwal:
Pobody's nerfect. 😁 PW
[Magisk] pndwal:
Latest public Beta / Stable:

15 hrs ago

Magisk Release Notes

2021.1.17 Magisk v21.4

Update: v21.4 adds more regression hot fixes.

Magisk Changelog

v21.4

- [MagiskSU] Fix su -c behavior that broke many root apps

- [General] Properly handle read/write over sockets (the broken pipe issue)

Magisk Manager Changelog

v8.0.7

- Fix sepolicy rule migration when upgrading

Latest debug Canary:

15 hrs ago

Magisk (f5593e05) (21401)

- Sync with public release

Magisk Manager (f5593e05) (4835)

- Sync with public release

Nb. Some are facing bootloop issues updating to 21.4... but not me. 😃 PW
[Magisk] pndwal:
It was likely 'Fix su -c behavior' commit that resolved this. Now synced w/ 21401 Canary also, as noted above. PW
[Magisk] curiousrom:
Thanks for the heads up but IMO you should always include a link when you repost other people's stuff.

May I ask where you got the "Magisk Changelog" from?

I don't see it in https://github.com/topjohnwu/Magisk/ nor in https://github.com/topjohnwu/Magisk/releases

***
[Magisk] zgfg:
Actually, I never go to GitHub for Changelog, it's all available from Magisk Manager

E.g., Update for Manager, Changelog and if I don't like, Cancel for updating

By switching Update Channels, latest Changelogs for Stable, Beta and Canary (if/when updates are available)
[Magisk] curiousrom:
Thanks for the explanations.

Found it: https://github.com/topjohnwu/Magisk/ >>> Magisk Documentation:

Release Notes

Magisk Changelog

Magisk Manager Changelog

***
[Magisk] bind.ing:
Hey guys, normally i don't have to ask questions in here, because the community is so good and tutorials are avaliable, but now i have to ask:

I've got a Onplus 6T with TWRP and root, nothing fancy, but working flawless. Until today where i did a magisk update. Now i am stuck in fastboot, with no TWRP no bootloader version no baseband version. I was not on the latest OTA update, because i didn't want to lose root again since it lost it a year ago after an update and i had to wipe everything.

I am now on my notebook (and not the pc where i normally do my fastboot adb stuff), but i can't even get the device to show up in adb devices.

Any advice (adb my not be the problem) on fixing TWRP, magisk and the bootloop?

If it is too crowded in here, i can open an new thread or a mod could move my post
[Magisk] pndwal:
You do like to keep me on my toes!... Guess it's just a natural curiosity! 😛

You'll see these for all public releases under Magisk Documentation on main page. Included here are:

https://topjohnwu.github.io/Magisk/

Another Heads-up:

The sections for Developers, especially Internal Details and Android Booting Shenanigans, are most enlightening to anyone trying to get a basic grasp on things Magisk.

Back to querie: The debug Canary build changes are from:

https://github.com/topjohnwu/magisk_files/blob/canary/notes.md

or:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/notes.md

Lastly, the reference to bootloop issues can be verified by checking most recent 'Issues' from Magisk main page.

I have included official Notes and Changelogs for recent Magisk updates regularly, as well up to the minute comments from John Wu frequently, for some time now in this Magisk General Support / Discussion thread as I feel this information is most relevant, especially since John stopped posting it here himself.

It's a given that these will be directly from his most recent Twitter and his GitHub pages as linked from any users Magisk Manager homepage.

When I've quoted from other sources, or old postings from his Twitter and his GitHub pages, I have been at pains to cite source pages... Sorry if it wasn't clear! 🙂

Kind regards, PW

Edit: I see you've found some of the links while I was responding. Goodoh 👍
[Magisk] zgfg:
Maybe it bootloops due to incompatible modules.

Search on Github Wiki

For that, you have two options:

1) May not work on all phones (if it does, it will uninstall all modules)

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

2) Boot to Android Safe mode, then to Normal. All modules will be disabled - you can manage them in Manager. You must also re-apply Magisk Hide option
[Magisk] pndwal:
Apart from suggestions above, did you happen to get 'system has been destroyed' message? PW
[Magisk] bind.ing:
Thanks for the answers.

Version 1 does not work because the phone is not recognised as a device in adb, but maybe that changes with an other PC.

Version 2 does not work because, PWR + volume up AND PWR + volume down get me into the fastboot menue

@pndwal: no, no such message. I had to klick update in the magisk manager 3 times, and nothing happend. Then it asked to reboot. After switching on again, it was in fastboot mode.
[Magisk] zgfg:
Yeah, for things like that it is good to certify your PC in advance for ADB.

Check to Wiki if there are other ways (there is, by TWRP, but you don't have)
[Magisk] Didgeridoohan:
Just to make sure... You say you're in the bootlooader (fastboot), but you're trying to use adb? That might be the issue, since in fastboot you need to use the fastboot command, not adb...
[Magisk] daddylonglegs:
I am having a similar issue.

Google Pixel 3A on Android 11 January release.

I take the boot.img from the firmware update and put it on my phone. I open the latest Magisk Manager and have it patch it. I flash the magisk_patched.img in ADB using the command: fastboot flash boot magisk_patched.img

I keep getting " NO VALID SLOT TO BOOT " error every single time. The only way to get my phone to boot again is to flash the OTA update over ADB.

I am desperately trying to get Magisk to work. I've never had issues getting it to work before now. Any advice on what I could be doing wrong I would greatly appreciate it.
[Magisk] Lughnasadh:
Not sure if this is your problem, but the name of the patched boot image is no longer "magisk_patched.img". He added a suffix to it so it would be something like "magisk_patched.xxx.img". So you need to use that name in the command, not "magisk_patched.img". Also, every time you patch your boot image, even if the same boot image, the name (suffix) will change.
[Magisk] daddylonglegs:
Thanks, yeah I was just talking in generic terms. I know the name is different now.

I don't understand. Every single time I flash the patched boot I get NO VALID SLOT TO BOOT errors. I see a TON of other people with the problem, but no one explaining how to get around it.
[Magisk] Didgeridoohan:
I don't have any Pixel device, but here's a thought...

In the past, I've seen many issues arise when flashing stuff using too old tools. Have you made sure you're on the latest release of the SDK Platform Tools?
[Magisk] BrimoFan123:
If you are in bootloader then run the command: fastboot oem get-product-model

Do you get anything?

If yes, then flash your stock ramdisk (or whatever partition you are taking to patch it with Magisk on Oneplus. In my case - Huawei Mate 10 with Android 9 it is called Ramdisk.img)

Then you should be able to boot your phone without Magisk.
[Magisk] Lughnasadh:
In addition to what Didgeridoohan said, it sounds like the slot it's trying to boot in is corrupted somehow or the status is not validated. Sometimes flashing the factory image (removing the "-w" from the flash-all.bat file so you keep your data) will reset the slot status and fix the problem. Just throwing that out there...
[Magisk] daddylonglegs:
Thanks. Unfortunately I have tried many times to flash the factory firmware with -w and it has not made a difference.

Every time I install Magisk I get: NO VALID SLOT TO BOOT

I tried the latest SDK Platdorm Tools just now. Flashed fastboot flash boot magisk_patched.img. I am still getting NO VALID SLOT TO BOOT

:(
[Magisk] drsaidalavi:
Hello,

I have upgraded the Magisk Installer to 21.4 and Magisk Manager 8.0.7 in my Galaxy note 8 on Stock Oreo rom, with xposed installed.

Before upgrading there was not much problems ,only few times at the beginning of a reboot, a message comes 'Google play has stopped working' then it disappears or I have to close the message. But after upgrading to the latest version, This not only become a persistent message, but also other google application also stopped working message comes. The google play store stopped working also. So what is the solution to over come this.

I switched back to version 20.4 , and the Magisk Manager is the latest 8.0.7 now there is no problem.

Kindly help me
[Magisk] bind.ing:
Yes, it is the only thing which works execept off.

I am now home at my main PC, where adb and fastboot was working, tried different drivers, different platform tools /adb/fastboot.

"adb devices" results in daemon starting and no list

"fastboot devices" results in nothing happening

Android drivers seem also not to work correctly

Edit: got it working at last with the Samsung Adnroid Drivers, choosing them manually in the device manager.

i think this is the last version i used on the phone:

10.3.0-OnePlus6TOxygen_34_OTA_042_all_1912142031_d9ef3-FASTBOOT

is there a way with MSM Tool or anything else i can do?
[Magisk] dcarvil:
Did you try "fastboot boot magisk_patched.img" without the flash? If that works, you should be able to install Magisk with the Direct Install method.
[Magisk] bind.ing:
Sry no, i always did the recommended update in Magisk Manager itself, so i got no *.img.

I got an oxygen os boot image and a stock android 10 boot image from last january where i wiped my phone for root. Also a find a boot.img in the "images.zip" from 10.3.0-OnePlus6TOxygen_34_OTA_042_all_1912142031_d9ef3-FASTBOOT

should i try that?

EDIT: woooo! Thanks for your help! using the boot.img from the 10.3.0 and flashing it with "fastboot boot magisk_patched.img "
[Magisk] shorbah:
hello guys I need your help pls

mgaisk was totally fine with me no issue at all on 21.0 or 21.1 i don't remember exactly.

after updating to 21.2 i always go for bootloop so i had to restore my backup by TWRP (old magisk 20.4) and wait for next update for it so I tried 21.2 + 21.3 + 21.4 all have the same issue. when I uninstall magisk from recovery it booting normally

-steps I did:

restored magisk

removed all module from magisk

uninstall edxposed and all modules and clean cash and data

i was on stable channel

modules I have in magisk

vancedtube

riru

riru core

syetemless host

modules in edxposed

minminguard

instaperfer

afwall+

edxpoded manager

my phone is asus ROG A9 original ROM
[Magisk] daddylonglegs:
Thanks so much for the reply.

I did fastboot boot magisk_patched_qfngE.img

It said

C:\adb>fastboot boot magisk_patched_qfngE.img
Sending 'boot.img' (65536 KB) OKAY [ 1.485s]
Booting OKAY [ 6.671s]
Finished. Total time: 8.253s

Then the Google logo showed up and the loading bar kept going. Then the phone rebooted into Recovery and said "Cannot load Android system"

What on Earth is going on? :(
[Magisk] dcarvil:
Try the following:

Run flash-all.bat without the -w.

Reboot without magisk and let the update complete.

Boot back to bootloader and run "fastboot boot magisk_patched_qfngE.img" (no flash).

Hopefully that will boot, then you can flash magisk with Direct Install.
[Magisk] daddylonglegs:
Thank you again so much.

When you say "reboot without Magisk" are you saying I should uninstall Magisk Manager?

Also when you say "then you can flash magisk with Direct Install", what does that mean? Isn't Direct Install the way I've been doing it?
[Magisk] dcarvil:
It is not necessary to uninstall Magisk Manager. Just reboot the phone normally after flash-all without a patched boot image.

After doing the "fastboot boot magisk_patched.img" (no flash) open Magisk Manager, select Magisk Install, Direct Install.

Also, did you have any Magisk modules installed? A bad module could also be causing your problem.
[Magisk] daddylonglegs:
Yeah I had a bunch of modules installed.

Unfortunately I have no idea how to remove them now because I uninstalled Magisk manager when trying to figure this all out, so now I don't know how to remove the modules from their location on the phone now that I no longer have root :(
[Magisk] bind.ing:
Me again...i have to install the magisk_pached.img every boot and root+twrp are gone. Should i reflash twrp. And then?
[Magisk] dcarvil:
You can re-install Magisk Manager without root after you do the flash-all.bat. I don't think that will help in removing the modules, though. I'll have to think about it, and get back to you.

In the meantime, see if my last suggestion works.
[Magisk] zgfg:
Uninstalling Magisk Manager does not uninstall modules

How to disable or uninstall modules (without Msgisk Manager) is described in Magisk Wiki on Github
[Magisk] Lughnasadh:
Try this command in adb...

adb wait-for-device shell magisk --remove-modules
[Magisk] FourSilver:
Hello,

My install of Magisk is causing bootloops, and I need help troubleshooting and fixing the issue. Here is what I have done:

- I got a brand new Unihertz Atom XL, which was loaded with Android 10. I downloaded a copy of the stock image for the device from Unihertz, so I have access to a copy of boot.img which I understand is required to complete the Magisk install. No additional software in installed on the Atom XL.

- I have the adb and fastboot packages installed on a fresh Windows 10 image, and installed the necessary vendor provided USB driver(s) to connect with the device.

- I successfully downloaded a copy of the Magisk Manager 8.0.0 apk from github, and moved it to the connected Atom XL after enabling USB debugging. I updated Magisk Manager after enabling internet connectivity.

- I then elect to install Magisk using the Select and Patch a File option as mentioned in the Magisk install documentation, where I select the boot.img file referenced earlier to create a patched image. This created image is then copied to the ADB directory, which contains the adb and fastboot packages.

- I invoke PowerShell inside the ADB directory, and issued '.\adb reboot fastboot' from the PowerShell prompt to reboot the Atom XL. From there, I am presented with a fastbootd menu with the option to reboot into the bootloader, which I select. I am then taken the bootloader prompt on the connected Atom XL.

- From PowerShell, I issue '.\fastboot flashing unlock' followed by '.\fastboot flash boot .\magisk_patched_PaLTk.img' in order to install the patched image on the Atom XL.

- Once the patched image process completes, I issue '.\fastboot reboot' from Powershell. The device then goes into an endless reboot that is only interrupted by flashing back to a stock image using SP Flash Tool.

What am I missing to have Magisk install successfully on the Atom XL?
[Magisk] truefriendcz:
Hi. I have two problems with latest Magisk:

1: Themes problem switch

not functional Theme change - after changing to Amoled or others stayed on white.

2: MagiskHide problem to Enable

After switch to Enable and reopen app stayed deactivated and Function is not enabled.

Both tested on latest Stable version 21.4 and Canary build

Tested on: Android 5.1.1 (original ROM with unlock bootloader and Magisk aplly only).

I reported both problems on GitHub, but for some reason unknown to me, both were closed to me. I have no idea what I did wrong and I apologize for breaking some rules of GitHub or the developer.

1: https://github.com/topjohnwu/Magisk/issues/3738

2: https://github.com/topjohnwu/Magisk/issues/3737

Thank you in advance if the problem is fixed in the near future. I can't access banking on Revolut because the author of Revolut has added another new feature that detects root and refuses to continue if root detects. And it cannot be accessed to account in any other way than via the mobile application.

This is addressed in the Revolut forum, but the author does not appear to plan to remove this check.

Revolut will start blocking jalbroken/rooted devices

Screenshot from the latest beta. Let me explain why this is a terrible idea: From the web-app you can’t do payments and stock stuff Removes freedom from devices The only problem for revolut with a jailbroken device is that the dumb user may install malicious stuff that steal money from his...

community.revolut.com