yashsingh1/xdaforums huggingface dataset:
[Magisk] Oblias:
Many thanks! The provided link was unable to provide any mirrors for downloading, but because you provided the name, I was able to find it elsewhere. Buy a beer/soda on me! :)[/QUOTE]
[Magisk] Akinerts:
Need help.

I went to update magisk to version 22.0 and it is showing errors. After updating I can no longer see the installed modules and in the settings some of the settings are added, including where you hide the magisk apk. My phone is a J7 prime Android 8.0.1.

Can someone help me?
[Magisk] Oblias:
Thanks! My PC is running Arch Linux, and I have installed Python 3, so I believe I can get the job done now, with the help from this forum.
[Magisk] rwio:
Ok, thanks. Perhaps a stupid question, but do I need to download the stock boot image from somewhere, or can I pull it from my phone with adb? Preferably I don't want do downgrade my android version.
[Magisk] zigbye82:
my rom has been abandoned for some time now.

So i booted in recovery and deleted the magisk folder from system/app. i reflash magisk 22.0 and booted. the error is gone now and magisk "seems" to be working as normal. Could it be that simple or do you think ill encounter problems later on?
[Magisk] Oliie23:
IF YOU'RE STUCK ON FASTBOOT AND WANT TO GET YOUR PHONE UNBRICKED READ ON

I'm on OnePlus 6 btw but this wil llikely work for everyone.

Method 1 (confirmed to work for me)

1. Get ADB files on your PC (I'm assuming you know how to do this so I won't go into detail on it)

2. Get the boot.img of your current ROM into the ADB folder on your PC. I got mine from one of the threads here, but you might need to extract it from your ROM. Some say it's straight in the ROM file, while some require dump payload tool for that (like OnePlus).

3. Open CMD in your ADB directory. To do that just open CMD from the Start Menu (make sure to launch as admin) and then write: cd [path to adb folder]

4. Launch your phone into fastboot mode.

5. Write: fastboot devices

6. If your phone is detected then write: fastboot flash boot boot.img.

7. Start your phone

8. The phone should boot. Normally.

Method 2 (haven't tried it but should work)

1. Get ADB files on your PC (I'm assuming you know how to do this so I won't go into detail on it)

2. Get newest TWRP Recovery IMG file and the newest full ROM. Put the recovery in your ADB folder.

3. Open CMD in your ADB directory. To do that just open CMD from the Start Menu (make sure to launch as admin) and then write: cd [path to adb folder]

4. Launch your phone into fastboot mode.

5. Write: fastboot devices

6. If your phone is detected then write: fastboot boot [name of your recovery]

7. Once it boots, it should mount your phone into PC so put your newest ROM into your phone's main directory.

8. Install your ROM via TWRP like you normally would.

9. Reboot - it should work.

I suppose I'm not gonna bother with rooting again. Things like this are unacceptable in the Stable channel. Rooting just doesn't provide enough features to warrant having to worry every single time about bricking my phone...
[Magisk] curiousrom:
May I ask what those devices are exactly & the method you used?

***
[Magisk] cyril'u:
I had same issue , I found a magisk.apk in system/app. I just deleted it and reboot as magik was already installed well. warning message is gone now.
[Magisk] Lord Sithek:
These devices I listed in my descritpion, and I updated from Magisk Manager as always
[Magisk] pndwal:
Sorry about the delay getting on to this... Long day at work and w/ family.

Just set up Logcat Reader app, updated again to 22001 Magisk APK, started recording logcat, intended to log Select and Patch a File freeze/failure (firstly), but this time it completed without a hitch!

So I merrily attempted Direct Install, and have now happily advanced to 22001 with no further issues except having no explanation or useful logcat! 😬

I don't know what made the difference, and after recovering to 21410 earlier I did update APK again and try Patch a File, which duly failed, before returning to 21410... Perhaps an extra reboot was all that was needed to put it right. 🙄

So I'm still mystified, but would love to be able to help sort out what seems to be a common if capricious/fickle issue... Keep up the good work, PW
[Magisk] zgfg:
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
[Magisk] Colibridesmontagnes:
Hi,

Many problems like a lot of people today.

I wasnt able to to Direct Install and Magisk returned an error when I was trying to patch boot.img.

I've made the decision to flash it with TWRP but when I enter TWPR I can't see the files on my storage...

I am doomed ? I did the un-hide Manager procedure before doing all te previous steps.
[Magisk] curiousrom:
If you are talking about your XDA user signature, that info is not trustable because if you update it all the signatures in all your previous posts will also be updated on XDA so it will make your post above irrelevant.

Also the signature is not visible in the mobile version of the forum.

***
[Magisk] Lord Sithek:
At the moment the list is up to date

Xiaomi Mi Note 10, Samsung Galaxy Tab S5e, Xiaomi Redmi Note 4
[Magisk] pndwal:
Spare a thought...

Yeah, what about my brain? ... but it is FUN! eh? PW
[Magisk] curiousrom:
Lol. You wrote that no problems with your 3 devices and there are 4 devices in your signature @ the present.

Pro tip: i Keep my device models + setup description in a .txt doc & just copy/paste when I want to include them in a post.

For example I did not just type this: Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-14 + Open GApps Pico + Magisk 21.4 Stable + Magisk Manager 8.0.7 + TWRP 3.5.0 recovery.

***
[Magisk] dmarden:
I assume it should be safe, after updating, to re-enable the "MagiskHide" option?
[Magisk] Lord Sithek:
Right. Didnt try update on the watch yet.
[Magisk] Bielecki:
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?
[Magisk] HippoMan:
A number of people have this problem, but not everyone ... and I'm another person who had no problem. Here's what I did on my OnePlus 7Pro (GM-1917) running OOS 10.3.8 with TWRP 3.5.0_9-0, starting with Magisk 21.4 installed ...

* Unhide Magisk back to its original name

* In Magisk: update Magisk Manager

* In Magisk: update Magisk to 22.0 ... system reboots

* Re-hide Magisk and re-configure its settings

Under Magisk 22.0, everything is working fine, and I can still access recovery.

Perhaps the reported problem is related to the OS version or the way that Magisk was installed ... ???
[Magisk] okchinmaya:
I was trying the second option by myself, and now my device is simply not turning on. I get a red blinking LED whenever I press the power button. I assumed that the battery might have discharged but even after keeping it plugged in to the charger for 1-2 hours, I kept getting the same red blinking LED.

This sucks! I never update Magisk on day one, today was a holiday and I thought of tapping the update notification and I am now sitting with a bricked device. I'm a non IT/CS guy and don't understand Python. Some guys on this thread are blaming others for not reading the changelog before updating but this is totally not acceptable.
[Magisk] rwio:
I finally got my phone working again with the method didgeridoohan suggested in this thread.

First I tried to use the boot.img from my current system. It flashed fine, but the Magisk installation in TWRP failed (both 21.4 and 22.0). So I searched for the stock rom here on the forum and took the boot.img from there. After flashing it in TWRP and then flashing Magisk (21.4) my phone started normally again. I didn't try the 22.0 version again though it will propably work too. Since I got the phone up and running again I don't care. I'm about to change mobile anyway.
[Magisk] HippoMan:
One clarifying point: in my third step, above, when updating Magisk to 22.0, I selected Direct Install (recommended)
[Magisk] J.Michael:
(replying without reading to end of thread -- sorry)

It wasn't clear to me: After flashing the stock boot image, did you try booting to Android?

If you can get to Android, look at every app in the app drawer, maybe you have yet another hidden Magisk.
[Magisk] Newtype14:
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?
[Magisk] SonderTech:
I got the same result on the sm-t817t. I even made a custom ROM and had it install the apk as a zip. I'm gonna try one more thing
[Magisk] dope77:
What's your device model and which android version?
[Magisk] Smil3yWulf:
Patched Modded didn't flash my BootPatched . The bootpatched was made from magisk v22 see attachment, if magisk and odin Modded can work together for future features. it is flawless
[Magisk] Newtype14:
Samsung Galaxy S7 (SM-G930W8)

Android 8.0 Oreo
[Magisk] pndwal:
Well, generally Magisk resides in boot partition (recovery partition for those w/ ramdisk in boot = no). Did your nandroid include boot image?

Simply flashing Stock or previously patched boot image usually restores system (not /system! - Magisk is Systemless by definition!) PW
[Magisk] pndwal:
You most likely forgot to 'unhide' Magisk Manager, and now need to find/remove the renamed one, then reinstall it. PW
[Magisk] Newtype14:
All I see is boot.emmc. This backup was done before rooting with Magisk.

Not sure I understand what I should try doing. I don't have much experience since I just recently learned how to root.
[Magisk] Lord Sithek:
Ok then, successfull update on 3 out of 4 my devices :ROFLMAO: 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
[Magisk] BrikHaus:
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.
[Magisk] kiwigi:
@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
[Magisk] Newtype14:
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.
[Magisk] 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!
[Magisk] curiousrom:
Galaxy S7 TWRP Backup Restore Fail

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.

Is that stock Samsung OS? TWRP version?

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?

***
[Magisk] pndwal:
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
[Magisk] 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!
[Magisk] 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.
[Magisk] 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.
[Magisk] Newtype14:
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.
[Magisk] Lim_Dul:
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.
[Magisk] cyril'u:
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.
[Magisk] Didgeridoohan:
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
[Magisk] mrror:
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.
[Magisk] HemanthJabalpuri:
Someone confirm that issue tracker of Magisk is there or not.

I cannot able to see it in repo.
[Magisk] Didgeridoohan:
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
[Magisk] curiousrom:
"Don't throw the baby out with the bathwater" comes to mind. 🤪

***
[Magisk] okchinmaya:
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.
[Magisk] 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 :)
[Magisk] pndwal:
That's why I asked earlier if your nandroid included boot partition; this should fix if you also included boot when restoring. If so, there may be other issues either with TWRP (as others indicated), or with system generally...

I'd still try flashing boot image for reasons mentioned in official Installation Instructions:

The proper way to obtain boot image is also in the instructions (nb. don't use latest, use image from whatever ROM you use currently).
[Magisk] zgfg:
Magisk by itself will not make you pass SafetyNet

Depending on what Magisk app (formerly Magisk Manager, not App Manager) would show, you will have to check in other threads (and use the corresponding Magisk modules):

- MHPC, if without Magisk you fail SN, it would mean that your firmware is not certified and that you need to fake the device fingerprint from some (similar) device

- SafetyNet fix, if after installing Magisk, Magisk Manager would show that it passes Basic Integrity but failing on CTS Profile

Hence you can test what Magisk App (formerly Magisk Manager) shows when you attempt SafetyNet test (no matter if Magisk is installed or not).

There are also other apps to test SafetyNet but you need the one that can also properly report does it pass/fail Basic integrity and/or CTS profile and does it take Basic or Hardware attest for CTS.

Not just passing or failing SN, that is of no use

And only upon you would pass SafetyNet, then start looking if Device is certified (sometimes it passes SafetyNet but Google Play must be reset to accept it and to start showing that device is certified)

---

Magisk app can be installed manually, no matter do you see it or not after flashing Magisk zip in TWRP.

And Magisk app will show then if Magisk is installed or not

---

Unfortunately, showing Ramdisk or not in Magisk app is not fully relevant.

You should try to patch boot.img and then check on the screen and in the log, did it find Ramdisk or not

Btw, that is IMO a bug in Magisk app:

- on certain devices (like Xiaomi) Magisk app shows Ramdisk No

- but when you patch the boot.img it happily finds Ramdisk and reports successful patching

- even when you later flash that patched boot img (where it did find Ramdisk) and Magisk is then properly running, Magisk app still claims Ramdisk No

Hence try patching your boot.img and look to the screen and into the log to see was it successful or not.

If successful, then flash and check if Magisk app reports that Magisk is installed

If not, then try to patch recovery.img but in that case you will have to flash it over your custom recovery
[Magisk] J.Michael:
As I understood posts:

Ramdisk No means the image has no ramdisk.

Magisk is willing to try adding a ramdisk to an image. If the kernel uses the ramdisk, the patching succeeds. But somehow Magisk remembers that this is a Magisk-created ramdisk, and continues to report the Ramdisk No state of the pre-patch image.
[Magisk] apophis9283:
Has anyone had the issue where install magisk to inactive slot after OTA no longer shows?

@topjohnwu
[Magisk] Didgeridoohan:
And the issue tracker is back. But there are now some restrictions on who can start a new issue.
[Magisk] Didgeridoohan:
It's disabled on newer builds of Magisk, because of issues (I don't have the details, unfortunately).
[Magisk] apophis9283:
Thank you sir
[Magisk] Didgeridoohan:
Not a bug in the app or Magisk, but a "quirk" of how Xiaomi have decided to implement their bootloader.

https://topjohnwu.github.io/Magisk/boot.html
[Magisk] Zoki88:
Does anyone have same issues with hiding magisk actually not working after update from few days ago? Apps actually recognize root, even if all things are enabled magiskhide and hide the magisk app. I'm on LG H930DS Oreo Europe software
[Magisk] zgfg:
Ok, a quirk but if when patching it knows to recognize ramdisk in the boot.img, then Magisk app/mngr could also (by using the SAME method) recognize its existence for the purpose of displaying on top
[Magisk] Didgeridoohan:
It doesn't "recognise" a ramdisk. Whatever is needed is simply added to the image (apart from the "Boot shenanigans" I linked, also see @J.Michael's reply to your previous post).