Magisk General Support / Discussion

[Lord Sithek]

Right. Didnt try update on the watch yet.

Ok then, successfull update on 3 out of 4 my devices Unable to get root on Huawei Watch 2 (custom rom and boot image). Nor through TWRP, nor by patching boot.img. The device is booting, but unrooted

 

[BrikHaus]

Actually I couldn't boot into recovery. Only fastboot was working so I flashed all partitions using fastboot zip stock rom but I do not recommend that as you will get everything wiped. Now I would try flashing just stock boot.img in fastboot and then boot into recovery to flash rom. This way I wouldn't wipe everything...

FYI
If you extract your update, remove the -w from the end of the flash-all.bat, it won't wipe your phone.
Then just run flash-all.bat with phone in fastboot.

 

[kiwigi]

Hoping someone can help me, my phone is stuck at the Samsung boot logo after updating Magisk.

At that point, I realized something had gone wrong, and since I didn't care about losing all my data, I did a force reboot into TWRP and did the following:

Formatted Data.
Wiped Dalvik, System, Data and Cache.
Restored a Nandroid backup that I had made before rooting my phone.

Once I did all that, I rebooted and the phone is still stuck at the boot logo. How is that possible?

@Newtype14
Would you mind telling me a couple of things:
have you flashed TWRP after complete magisk set-up ?
how did you do the Nandroid backup before rooting? have you used an app?
Thanks

 

[Newtype14]

@Newtype14
Would you mind telling me a couple of things:
have you flashed TWRP after complete magisk set-up ?
how did you do the Nandroid backup before rooting? have you used an app?
Thanks

I flashed TWRP before doing anything with Magisk, then booted into Recovery mode and in TWRP, I created a backup by selecting: "Boot", "System", "Cache", "Baseband" and "EFS".

For additional information: I did wipe my phone three weeks ago and used that backup to restore and it worked fine.

 

[daniel_loft]

Because every now and then another app needs Magisk hide (latest I noticed was Revolut) I was thinking about this little suggestion:
- When activating Magisk hide, why not set it to hidden to all apps? Or, if possible hidden to all exempt those that were specifically given root access.
or, if the above is not implementable...
- Could it be possible to have a way to export the list of selected apps from MagiskHide?
I happen to have installed Magisk relatively often lately and it's always annoying to repopulate the list in MagiskHide.
Thanks!

 

[curiousrom]

Galaxy S7 TWRP Backup Restore Fail

...I did a force reboot into TWRP and did the following:

Formatted Data.
Wiped Dalvik, System, Data and Cache.
Restored a Nandroid backup that I had made before rooting my phone.

Once I did all that, I rebooted and the phone is still stuck at the boot logo. How is that possible?

Many users including me reported fail to boot if you select install the TWRP app when asked in TWRP. That app is fluff, wants to start at boot, run in the background, collect data & is not necessary anyway because the TWRP updates are not frequent & it's easy enough to update manually.

If you did that, go to TWRP > Settings > and disable: Prompt to install TWRP app if not installed.

Samsung Galaxy S7 (SM-G930W8)
Android 8.0 Oreo

Is that stock Samsung OS? TWRP version?

I flashed TWRP before doing anything with Magisk, then booted into Recovery mode and in TWRP, I created a backup by selecting: "Boot", "System", "Cache", "Baseband" and "EFS".

For additional information: I did wipe my phone three weeks ago and used that backup to restore and it worked fine.

You only need to restore System, Boot (which is the kernel in fact & this gets modified by Magisk on your device) & Data. You did not backup the Data partition?

There is no need to backup or restore Cache as it is recreated by the system if needed.

The EFS partition can be restored if you have problems with unknown IMEI or no access to the network after checking the APN settings. No need to fix what is not broken. Don't restore Baseband. Are you sure that it's not labeled Modem?
***

 

[pndwal]

All I see is boot.emmc. This backup was done before rooting with Magisk.
View attachment 5231743

Not sure I understand what I should try doing. I don't have much experience since I just recently learned how to root.

Well, you just need to understand that being systemless, actual Magisk is flashed to boot image (assuming ramdisk [in boot image] = yes), so this is what got corrupted by bad flash.

Flashing patched boot image thru fastboot from PC is now the preferred method to flash Magisk, but, if you have TWRP you can generally flash boot partition from this (without PC) also.

The reverse is also true: to remove Magisk root (or corrupted Installation), simply flash back UNPATCHED boot image (download and extract from your current ROM package).

The details are all laid out for you in John's official Installation Instruction on the Magisk main page. Just click the GitHub (cat) symbol on Magisk app main page (or click here: https://github.com/topjohnwu/Magisk ), then Installation Instruction. Please read everything (especially Patching Images). Nb. some of the special instructions for Samsung may be relevant, but largely won't apply as your device did no launch w/ Android 9 or later (ie not SAR device).

Hope this helps. PW

 

[DrPhant0m]

NOW I'M STUCK IN DOWNLOAD MODE!!!

UPDATE: Being on DrKetan ROM, I flashed the BL + CP package in Odin, which allowed me to reboot into TWRP. I still couldn't reboot the system, so I dirty-flashed my current ROM, and it allowed me to start my phone without losing anything. I still want to know what the "like magic" part is about flashing the apk in TRWP, though. /UPDATE

So... the changelog for Magisk v22 said that you can flash the apk as a zip "like magic" so I changed the .apk to .zip and tried to flash it on my Note 9 (Exynos). The process failed in TWRP with ERROR 1 (IIRC), so I tapped Reboot System. The phone rebooted to download mode, and seems to be STUCK THERE. If I hold vol down + power the screen turns off for a second, and goes back to download mode.

I tried flashing my version of TWRP back in Odin with auto reboot turned on, and it succeeds, but still goes back to download mode. Do I really have to flash the stock ROM back to my phone because of this?

Someone please help. I have a business trip tomorrow and need my phone... I guess I shouldn't have tried this. Thanks in advance!

 

[golden7]

Serious issues with v22 update - MagiskManager shows the new Manager ver as being v. 22 I didn't see any changelogs, so I selected Updatefor Manager app (not Magisk) from MagiskManager - so v22 became the Manager version and Manager showed no Magisk or root, and all crapped out. Using old Xperia Z3 but running Android 10 - CarbonRom (Lineage variant, very nice btw)

Solution: First I downloaded older version of Magisk 21.4, latest Magisk uninstaller, and Manager 8.0.7 Second, unininstalled MagiskManager v22 app. Third reboot to TWRP and uninstalled Magisk with latest Magisk uninstaller. No reboot, directly installed Magisk v 21.4 from TWRP, booted to system, and installed apk for Manager v 8.0.7 and all runs fine - have root.

New development - Manager keeps "Checking for updates . . ." and not showing version installed or available. Guess the Magisk Team is on it. Now shows Manager is up to date.

Galaxy s9 is confused.

 

[Pandemic]

Updated from 21.4 to 22.0 and no issues at all on my Xperia 1 with Android 11, updated the magisk manager 1st then updated to magisk 22.0 with the manager with direct install.. So dunno what is wrong with the other people that have issues.

 

[Newtype14]

The reverse is also true: to remove Magisk root (or corrupted Installation), simply flash back UNPATCHED boot image (download and extract from your current ROM package).

I thought that when I was restoring with my backup, it was also restoring the boot to its pre-Magisk state, since I selected "boot" in TWRP when I created my backup. Am I wrong?

What's the proper way of getting this boot.img? I did some research and everywhere it says that to get the boot.img, you have to download the latest firmware for your phone model/carrier and extract it from those files.

 

[Lim_Dul]

Serious issues with v22 update - MagiskManager shows the new Manager ver as being v. 22 I didn't see any changelogs, so I selected Updatefor Manager app (not Magisk) from MagiskManager - so v22 became the Manager version and Manager showed no Magisk or root, and all crapped out. Using old Xperia Z3 but running Android 10 - CarbonRom (Lineage variant, very nice btw)

Solution: First I downloaded older version of Magisk 21.4, latest Magisk uninstaller, and Manager 8.0.7 Second, unininstalled MagiskManager v22 app. Third reboot to TWRP and uninstalled Magisk with latest Magisk uninstaller. No reboot, directly installed Magisk v 21.4 from TWRP, booted to system, and installed apk for Manager v 8.0.7 and all runs fine - have root.

New development - Manager keeps "Checking for updates . . ." and not showing version installed or available. Guess the Magisk Team is on it. Now shows Manager is up to date.

Thanks for sharing your fix / workaround. I'm on an old Xiaomi Mi Mix, Android 9.
Had the same symptoms when I updated to the newest Manager. Also, Magisk / Magisk Manager started crashing. Downgraded to 21.4 and 8.0.7 and everything is fine again. The update to 22.0 is now greyed out in the manager, so I guess I'll wait till a more stable version comes out before trying this one. The Manager is still showing an update for itself (22.0) but that can't be right. I think the repo URLs might have gotten mixed up or something.

 

[cyril'u]

It is known issue that Magisk Manager (now Magisk app) must not be installed as a system app (also not on external SD).
AFAIK, documented somewhere in Magisk docs or Wiki, it was also discussed here and under Github issues

You 're right . But Magisk was included in my Custom Pie ROM I've used for 2 years. Until r22 I didn't know that a file magisk.apk was into my system/app folder. Until r21.4 , all the updates didn't detect it. Now everything is back to the normal and it is running fine. Finally not a big issue. Thanks for your help.

 

[Didgeridoohan]

The Manager is still showing an update for itself (22.0) but that can't be right. I think the repo URLs might have gotten mixed up or something.

That is exactly as it should be. From v22.0 Magisk and the app are now merged into one:
https://topjohnwu.github.io/Magisk/releases/22000.html

 

[mrror]

Issues on MIUI Global 12.0.3.0(QFGEUXM) (Redmi Note 7 - Lavender), Android 10 QKQ1.190910.002
Magisk v22.0 doesn't work at all, seems to patch fine in TWRP, but boot stucks at MIUI logo, hangs there for a while, then reboots to recovery (TWRP 3.5.0_9.0-lavender).
Tried installing through patching and flashing stock boot image and recovery (one at a time), but none of these have worked.
I was able to install Magisk v19.0 (TWRP zip flash) and boot, but Magisk Manager nor Magisk app won't detect it (if I try to flash zip again it says "Detected magisk patched boot image" (or sth like that) and patches fine).
Any solutions?

Same exact problem on my Redmi Note 8T/willow (MIUI 12.0.2 QCXEUXM, Android 10) with Orangefox 11.0_1. I have to reflash the rom to boot to system again.

 

[HemanthJabalpuri]

Someone confirm that issue tracker of Magisk is there or not.

I cannot able to see it in repo.

 

[Didgeridoohan]

Someone confirm that issue tracker of Magisk is there or not.

I cannot able to see it in repo.

John got fed up with the spamming of low quality issue reports (and issue tickets that wasn't actually issues):

https://twitter.com/i/web/status/1364892377580642309

 

[curiousrom]

John got fed up with the spamming of low quality issue reports...

"Don't throw the baby out with the bathwater" comes to mind.
***

 

[okchinmaya]

May I ask what those devices are exactly & the method you used?
***

You are The Messiah good sir! Thank you, thank you so much. For almost everyone stuck with acquiring the boot.img file, if you are using any custom ROM, check its ZIP, it will have a boot.img file within it without fail. Simply flash it using fastboot flash boot boot.img and you're good to go.

 

[Nivan0611]

Hi All . . . I posted this in another thread, but it seems that it should have been posted here

If any can please Help . . .
"Quote"
Hi All . . .
I am running a Amlogic X96Air Box with Slimrom-Android 9

Can someone plz guide me on installing Magisk for Safety Net Pass on Uncertified Google Play Store "Uncertified Device"

Firstly i installed the App Manager to access if "ramdisk" is available . . it says "No"
I then uninstalled it . . then tried to go the route to flash the zip (v22) thru TWRP . . after reboot nothing showed up in all apps (no Magisk) . . not sure if I'm doing it correctly !!! . . . However, I then reset the box and also reinstalled the rom to have a clean installation.

Any guidance on installing Magisk for Safety Net Pass on Play Store to have a certified device would be greatly appreciated, if this is at all possible
Thanks