Magisk General Support / Discussion

[Zincoshine]

My phone prompted me to update the manager to v22.0. now the manager crashes every time I try to open it. I still have root access apparently. I'm not sure what to do here. I haven't had a problem with magisk in years, the last time I had a problem was when magisk 17.0 bricked my phone. My phone is a oneplus 5t with Android 8.1.0 and oxygen OS 5.1.7.

Edit: is there any way to downgrade the manager to 21.4 without touching magisk itself?

 

[Homeboy76]

Update
SDK Platform-Tools: r31.0.0

 

[CSX321]

Ah, I hoped I wouldn't need the app.

Edit...still froze...see later post below

FWIW, the new kernel in the Pixel 3 March update hasn't frozen on me yet. I've tried to look up in which kernel version the f2fs deadlock bug was patched (if it has been), but I haven't had any luck finding the info yet. I'm currently using Magisk 21.4 with systemless hosts and the USF module, and everything is perfect.

 

[nowster]

FWIW, the new kernel in the Pixel 3 March update hasn't frozen on me yet. I've tried to look up in which kernel version the f2fs deadlock bug was patched (if it has been), but I haven't had any luck finding the info yet. I'm currently using Magisk 21.4 with systemless hosts and the USF module, and everything is perfect.

I had a freeze two minutes after booting March 2021 update with Magisk patch.

 

[CSX321]

I had a freeze two minutes after booting March 2021 update with Magisk patch.

Yeah, I guess I cursed myself with that post. Mine just froze. Back to ElementalX, I guess!

Edit...Man, it's weird how it worked fine for more than 24 hours, and now it freezes almost immediately when I reboot! What a pain that was to fix. Safety mode didn't seem to disable the Magisk modules; it still would freeze. I had to remove all modules with the adb command, then set everything back up.

 

[Sizzlechest]

My phone prompted me to update the manager to v22.0. now the manager crashes every time I try to open it. I still have root access apparently. I'm not sure what to do here. I haven't had a problem with magisk in years, the last time I had a problem was when magisk 17.0 bricked my phone. My phone is a oneplus 5t with Android 8.1.0 and oxygen OS 5.1.7.

Edit: is there any way to downgrade the manager to 21.4 without touching magisk itself?

If you updated Manager App to v22 and it now crashes, just uninstall the app and reinstall it. It should work even if you didn't update (or remove) Magisk.

 

[Fil76]

Last time i try to update 21.4 to 22 i bricked my op6t (direct install error)

Lost boot IMG and also twrp so only hard reset was in my skill with Mauronofrio tool

I'dont speak english well could someone check if this procedure Is correct

https://i.postimg.cc/9XdCg6zz/Screenshot-20210302-185827.jpg

Update magisk manager (app to 22)

Unhide magisk and restore magisk original name

Click update and do direct install ?

Is correct ? What about if i Lost again boot.img ? Push original boot.img via fastboot ?

 

[Zincoshine]

If you updated Manager App to v22 and it now crashes, just uninstall the app and reinstall it. It should work even if you didn't update (or remove) Magisk.

Thanks for the help and thanks to my phone for saving me from a Magisk 22.0 brick via this minor problem with the manager.

 

[dynamo1950]

Going to go out on a limb and post this before calling it a night.

Am having similar issues - not a stranger to magisk/roms/etc... - did spend the evening reading & trying various things.
Hoping it's something simple I am missing - but I am seeing others with my device/update having the same problem too. May just be too tired - but was unable to get any safe-mode to work.

Device - Google Pixel 4a 5G
OS - Stock Rom, running the March 1 2021 update (Android 11 - RQ2A.210305.006)
Prior OS - Stock Rom, running the Feb 1st Update

Had been on Magisk 21.4 without issues - and had been updated to/running v22 without issues as well since release

Since applying the March update, any version of Magisk I try (21.4, 22, 22 Canary) cause bootloops and require the stock boot.img to be reflashed.

Magisk App / Manager have been completely uninstalled and were also removed prior to flashing the patched boot.img - just in case anything was lingering in the background.

--------------------------------------------------------------------------------------------------------------------------------------------------------

Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???

 

[artlan]

--------------------------------------------------------------------------------------------------------------------------------------------------------

Experienced the same with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img from this update causes bootloop showing the blue Android logo indefinitely. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allow phone to boot successfully.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from Magisk v21.4 to v22.0 using direct install in the Magisk app successfully last month.

I suspect there may be some changes in the updated boot.img that conflict with the changes Magisk makes when patching the boot.img.

Any thoughts???

So, and I knew this would happen if I posted, I got mine working and it was of course my own fault.
I swore I had disabled all mods prior, but I must have double tapped one (a clock/navbar mod) and it was the culprit.
I was shown an alternate way to get into safe mode, which finally worked (pressing the power button before the reboot screen once the os tries to load, getting the reboot menu, long press restart option), and that let me start up just fine.
I'm now running v22 on the march update with safetynet/magisk hide/systemless hosts just fine again.

 

[Fil76]

Last time i try to update 21.4 to 22 i bricked my op6t (direct install error)

Lost boot IMG and also twrp so only hard reset was in my skill with Mauronofrio tool

I'dont speak english well could someone check if this procedure Is correct

https://i.postimg.cc/9XdCg6zz/Screenshot-20210302-185827.jpg

Update magisk manager (app to 22)

Unhide magisk and restore magisk original name

Click update and do direct install ?

Is correct ? What about if i Lost again boot.img ? Push original boot.img via fastboot ?

I take a Xanax and tried again

But this time i simple renamed apk to zip and installed via twrp

Really sad that Lost some photo in last brick

Next time i Will do a backup

 

[Smil3yWulf]

I patched my AP firmware file with magisk. As instructed to use Bl, CSC, And Patched AP on Odin. But I get unassigned file error in odin when doing the process.. when I look at my phone J7 2018 <J737T1> it's says secure check failed (Boot) .. Can someone Helped me out to Flash It. So I can have Magisk SU. I just wanna install Viper4Android, and Dolby Ultra Headphones x for my music listening and watching TV on spectrum TV app with magisk module's

 

[Smil3yWulf]

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread

I have a great issue problem, I cant flash Magisk patched file with Odin.. I get unassigned file error in odin .. I check on my phone and its says secure check failed (boot). How can I fixed the problem so I can flash it in and start using magisk .. my device is J7 Star 2018 (J737T1)

 

[pignose28]

Hi i want to ask, i just installed magisk v22.0 on Xiaomi MI A1 on Wave Os ROM, and i check the safetynet and its failed, how to passed the safety net test? pls help thanks

 

[mistermojorizin]

Hi i want to ask, i just installed magisk v22.0 on Xiaomi MI A1 on Wave Os ROM, and i check the safetynet and its failed, how to passed the safety net test? pls help thanks

MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0

Universal SafetyNet Fix Magisk module This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12...

forum.xda-developers.com

 

[mistermojorizin]

Sorry if this is the wrong place to ask, I'm trying to find a module.

It was a module that let you disable/manage magisk modules from ADB. It was separate from the one that lets you manage modules from TWRP.

I used to have it a few years ago and now I can't find it for the life of me. Any help would be appreciated.

 

[raphael_KcT]

Hi i want to ask, i just installed magisk v22.0 on Xiaomi MI A1 on Wave Os ROM, and i check the safetynet and its failed, how to passed the safety net test? pls help thanks

Same problem here with Redmi Note 7 and latest Android 10 LOS

 

[dynamo1950]

--------------------------------------------------------------------------------------------------------------------------------------------------------

Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???

------------------------------------------------------------------------
Anyway, I discovered the solution to my dilemma mentioned above by searching thru forums and Youtube. This may be helpful to those who have flashed the latest ROM update for their phone, then flashed the Magisk patched boot.img and now the phone is unable to boot to the OS.

It appears that the bootloop caused by flashing the 'Magisk_v22.0_Patched_boot.img' was due to installed Magisk modules. This is what worked for me:

1. Boot into TWRP from fastboot.
2. Using the File Manager in TWRP navigate to the '/data/adb/modules/' folder where the Magisk modules reside as folders. Delete all of them.
3. If Magisk is NOT installed then flash 'Magisk_v22.0_Patched_boot.img' as Boot or 'Magisk_v22.0.zip' in TWRP and boot phone to the OS.
4. Open the Magisk app to configure Magisk and install the Magisk modules.
5. Reboot.

The phone is now running the latest ROM, rooted with Magisk v22.0, passes safety net all without erasing user data...

 

[pndwal]

Need some help installing Magisk on an ancient Rockchip tablet. It's the Medion Lifetab E7312, based on Rockchip RK3066 SoC, running Cyanogenmod 12.1 (Android 5.1). This device got its own seperate kernel.img, instead of the kernel being part of boot.img. I tried to patch the kernel.img (and also boot.img and recovery.img, just to be sure) in Magisk 22, but always get the "Unsupported/Unknown image format" error message.

Any idea how I can get it to work? Maybe manually patch the image?
Here are the images:

Do you have a custom recovery for that?... And does Magisk app say ramdisk = yes? PW

 

[justjeepin]

I have a Samsung Tab S2 that I previously had Lineage OS 16 and recently installed an unofficial Lineage OS 17.1 rom. I got everything working but Netflix and Disney Plus are not showing up in the Google Play Store. So I installed Magisk and MagiskHide Props Config. After a reboot I now pass a Safety Net check.

Two questions:

1. The previously mentioned apps still don't show in the Google Play Store.

2. I read something about keeping your device certified by installing a configuration file. It says to do it before setting up your device but I already have everything setup. Can I still do it or will I have to clean install and start over?

With stock LOS I didn't have this issue but with this custom rom I am.