yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Switching to the older version of Magisk

For going back to an older version of Stable or Beta Magisk versions, you must use:

- Magisk Manager Settings, switch Update Channel to Custom

- Open Custom Channel and paste in the URL for json file for coresponding to that older version of Magisk

For Magisk Stable (and Beta) it is relatively easy to find the corresponding json files on Github and to pick up their URLs - see below.

For Canary it's much more complicated hence not diving here to the Canary case (I did it too and posted few times during the last month or so about - it can be found by scrolling back, but sorry it was not as a comprehensive how-to guide like here for Stable)

Generaly, it does not matrer which Magisk Manager version you use (don't use Canary Manager because the latest is integrated with Magisk and it has different architecture).

Switching to the old Manager like 7.5.1 will not help you to install the old version of Magisk. Only the Custom channel will do

To obtain the URL for the json file corresponding to that old, Magisk, e.g. v20.3, follow through the attached screenshots:

- Open in browser: (mobile phone, I use Chrome):

magisk_files/stable.json at master · topjohnwu/magisk_files

(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.

github.com

- It will show you the latest stable.json

- Click on History

- Scroll down to e.g. Magisk v20.3 and open

- It will show you the difference in stable.json between Magisk v20.2 (preceeding) and that v20.3

- Click on three dots and take View file for that second stable.jsom correspinding to the 'new' v20.3

- Now you are looking to the stable.json for v20.3, long press on Raw and take Copy link address

Then paste that URL to the Custom Channel field in Magisk Manager Settings, go back and on the main screen Magisk Manager will now show that you e.g. have Magisk v21 installed (or Magisk not installed) but that 'latest available' is v20.3, following the json file you just have put to the Custom channel

And Install Magisk will install (e.g. will Patch) that old v20.3, not the really/currently latest Magisk

Later if/when you want to switch to the up-to-date Magisk version, switch Custom Channel back to Stable and Install that newest Magisk version
[Magisk] C5Longhorn:
Thank you, I saw the custom option but didn't understand the URL requirement.

Rick
[Magisk] zgfg:
I've updated now my previous post above with instructions and screenshots how to e.g. go back to Magisk v20.3 by use of Custom Update Channel
[Magisk] C5Longhorn:
This worked. Thank you for taking the time to post. I learned something new and copied it for later.
[Magisk] zgfg:
Sorry, I didn't follow all your story, can you please summarize:

- You have Huawei (some model)

- EMUI 5.1 firmware (even if you use custom ROM, you patch boot/ramdisk/recoveey image corresponding to your last stock version because custom ROM affects only system)

- Latest Stable and Canary Magisk does not work (no root or bootloop?)

- Which older version of Magisk worked for you?
[Magisk] 2_i:
I do not know who yo turn to with this, but I have second Moto Z2 Play phone that does not boot after the last update to Magisk. Both phones worked for several years rooted. The symptom is that the phone just does not start with the Power Button pressed. The boot into Bootloader/recovery still works, but the boot into the system goes to nowhere. One of the phones had Nandroid backups, so I seem to be getting to somewhere there, but the other is now destined for trash. The system was Android 7.1.1 in my memory.
[Magisk] 2_i:
Update: It appears that Magisk was not updated for a while on both phones, so the problem could be tied to an earlier Magisk update than just the very recent. Since I have access to TWRP on both phones, I guess I should flash an earlier version of Magisk from a zip, right? It seems that the version 1y back ran fine.
[Magisk] IlConsiglieri:
Hello,

I have sent the dev of the app my magisk log. I will update his findings here. It concerns the mobile tracker free app.

mobile-tracker-free.com
[Magisk] Didgeridoohan:
After a quick look: That's an app I would

never

give root permission... Or even install in the first place.
[Magisk] IlConsiglieri:
How so? Does it do something other then described on the website? I am fully aware of the fact that this is a tracking app.
[Magisk] Didgeridoohan:
Apart from the shady nature of tracking apps, there's just no way to know what it does once it has full access to the device (without some serious analysing)... But this is getting off-topic, so if this is something you'd like to discuss further you can open a new thread in an appropriate forum or contact me in a private conversation.
[Magisk] vinokirk:
Hi all, i've just updated Magisk on my Note 10+ 5G, now it wont boot. It gest stuck on the 'Samsung Note 10+ 5G' screen.

HELP!

I can get it into TWRP. Has Magisk written a bad bootloader or something?
[Magisk] Didgeridoohan:
Magisk does not touch the booloader, only the boot/recovery image.

You've got TWRP, so in theory you should be able to fix things. Restoring the stock boot image, either manually or by using the Magisk uninstaller (you can find it on Github), would be a first step. After that you can try installing the same Magisk version again (sometimes updating Magisk to a newer version can cause issues, possibly caused by Magisk internals or modules, that you can fix by doing a clean installation). If that still doesn't work, you can always try with a previous release of Magisk (again, found on Github).

If you've still got issues after all that it's usually a good idea to take a look in your devices forum. That's where you find the most amount of people that know your devices particular ins and outs.

Lastly, if it turns out to be an incompatibility between your device and current releases of Magisk, it's always appreciated if relevant information regarding hunting this down is provided in the proper manner as a Github issue.
[Magisk] Bobby_Turboto:
Hey there,

I'm rooting with Magisk for the first time and I followed this guide for the OnePlus Nord:

How to root the OnePlus Nord with Magisk

If you have gotten your hands on the new OnePlus Nord, here are the steps you can follow to easily unlock the bootloader and root the Nord with Magisk.

www.xda-developers.com

I do not have wifi, I can't call, my phone is crashing and restarting after every 2 min use.

I thought that I needed to restore it back to OxygenOS and I used this guide:

How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide

In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…

www.thecustomdroid.com

After it didn't work I simply tried https://www.xda-developers.com/how-to-root-unlock-bootloader-oneplus-nord-magisk/ (the first guide) in order to root again but without any result.

Is there a way to restore my phone without any problems?

Model AC2003

Oxygen OS 10.5.10.AC01BA
[Magisk] Uluru25:
Dear ZGFG, fortunately not having needed to follow your valuable guidance, I nevertheless assume it could be very helpful for a plenty of guys. But it might be hard to find this guidance within this very very big thread. Maybe it is possible that you open a new thread for this issue and put a link to the postings here?
[Magisk] zgfg:
Thanks. That special thread might also get 'lost'.

I'd suggest if @Didgeridoohan could add a section to the Magisk Wiki 🤓
[Magisk] Didgeridoohan:
I've had that particular kind of section on my to-do list for quite some time.
[Magisk] Taranis01:
Hey, I am missing the SafetyNet Check button in Magisk Manager. Can't find any information about why that would be the case. Do you have any idea?

I am using an old Samsung Galaxy S6 with LineageOS 17 (Android 10). Installed Magisk by flashing in TWRP.
[Magisk] Didgeridoohan:
My first guess is that you don't have any Gapps installed. SafetyNet is Google's and need their infrastructure...
[Magisk] Taranis01:
Thank you very much, that really is the case :-) I haven't installed microG yet.
[Magisk] x.trinity:
It's not microG.

It's GApps.
[Magisk] pndwal:
...but microg should contact the necessary 'gapps':

https://github.com/microg/GmsCore PW
[Magisk] kiwigi:
S7 Exynos, sm-930f:

Please can someone tell me if that link shows the correct install for my phone. I'm slightly confused with the entire page installation instructions( grey hair are catching up on me ;)).

Thanks
[Magisk] franz72:
Hi, all.

I'm trying to root my Samsung SM-J415FN (Samsumg J4 Plus/Prime), but, once doing everything (installed TWRP, applied needed patches, etc.) and especially flashed Magisk zip, my phone keeps being unrooted! I don't know why, sincerely. I'm in a cleft stick...

The phone is an Android 9 "Pie" that I completely re-flashed with Odin using original Samsung/Sammobile images for Italian ITV version (last one: 2020-12-20 CSC J415FNXXS6BTK2 J415FNTIM6BTG1).

What am I doing wrong?!

Thanks for your help,

Franz
[Magisk] nikiDUA:
Hi..

What is this really means??

This screenshot taking from my Vivo Z1 Pro..
[Magisk] Didgeridoohan:
You're on the stable update channel, but haven't installed Magisk yet. Your device doesn't have a ramdisk in the boot image, so you'll most likely have to use the recovery image instead (there are always exceptions). Your device doesn't use the A/B partition setup (so it's called an A-only device), has system-as-root (SAR) and is using a block based encryption.
[Magisk] Didgeridoohan:
There are so many things that seem to be able to go wrong on Samsung devices (because of this, the best place to ask for help is usually in your device's forum), but there's one guess I can make.

If your device has an external/adoptable storage, make sure the Magisk app isn't installed there. It needs to be installed to the internal storage to work properly.
[Magisk] Didgeridoohan:
That should be correct yes, but I don't do Samsung so better check your device's forum to verify. You can usually find info on this kind of stuff there, or at least someone who knows.
[Magisk] Didgeridoohan:
But if I remember correctly, and unless something has changed recently, microg can't do a SafetyNet check.
[Magisk] dc_01:
Hi there, I tried several times to install new magisk, but not successful. From previous version i got the message, update availble, chose direct install, but since that, magisk is not present. tried via twrp, tried uninstaller, no success. what do i do wrong? phone: huawei P10 with android 8.1.
[Magisk] pndwal:
Bit out of my depth here, but I think it can, and 'Check SafetyNet' shows in Magisk [Manager] with GmsCore, GsfProxy, RemoteDroidGuard etc installed.

Passing has been an on-again off-again affair however, and it seems it has been failing since June 2019 with Google changes.

The microG component needing a fix is apparently RemoteDroidGuard, and there's not been much progress due to lack of (devs) time, but SafetyNet API functionality is currently listed as 'partial':

https://github.com/microg/GmsCore/wiki/Implementation-Status

Two issues are cited, one still open:

https://github.com/microg/RemoteDroidGuard/issues/24

Interestingly, after 14 months, this:

PW
[Magisk] Didgeridoohan:
Yup... That's what I was thinking about (I have never played around with microG, it's on the infinitely long to-do list): SafetyNet can't pass on microG. Thanks for clarifying.
[Magisk] Didgeridoohan:
Similar reports, of v21.4 not working on Huawei devices have been made a few times. But, just a couple of days ago another P10 user reported that the latest Canary works:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84397903
[Magisk] xunholyx:
I'm using Vanced YT Music, and Vanced Manager installed MicroG. I'm passing SafteyNet.

Maybe I'm misunderstanding what's being said here......
[Magisk] oslo83:
Any magisk updates to support huawei's emui10.x and later ?
[Magisk] Didgeridoohan:
That's just a tiny microG component so that you can log into the rootless variant of Vanced (IIRC). You still have the regular Google services installed, so that's what is being used for SafetyNet. If you would degooglify your device and only use microG for everything you wouldn't pass SafetyNet.
[Magisk] nowster:
Heads up!

Hold off updating to the latest security update.

Current Magisk canary (21407) cannot patch either the January 2021 or the February 2021 boot.img for Pixel 3a.

- Device platform: arm64-v8a
- Installing : 0646f48e (21407)
- Copying image to cache
! Installation failed
[Magisk] dcarvil:
No problems with Magisk stable 21.4 on my Pixel 3. There are a couple of workarounds for Magisk Canary in this ticket.

Unable to patch boot.img · Issue #3811 · topjohnwu/Magisk

Pixel 5 on January 2021 patch. Unable to patch February 2021 boot.img on Magisk 21407 Copying image to cache Installation failed I looked at the app permissions and there are no permissions request...

github.com
[Magisk] xunholyx:
Worked just fine on my Pixel 5. So did January's.
[Magisk] J.Michael:
@nowster Do you have Magisk hidden?

Did you try unhiding Magisk and then patching?
[Magisk] CSX321:
(Edit...I think I replied to the wrong person.)

Seems like it is probably a canary issue. I have MM hidden, but also had no problem using stable to patch the February update on my Pixel 3.
[Magisk] 2_i:
OK, one more update even though I am conversing with myself. However, someone may run into the post while trying to solve similar problems. Advice to go to device specific forums does not work for older less popular devices as such forums dry out with time. I managed to resurrect both Z2 Play phones that quit booting after the Magisk update. One got resurrected from a TWRP backup. Magisk will not be updated there from the version that worked. The other phone had no backup, but I managed to uninstall Magisk there using the Magisk-uninstaller-20210117.zip. Surprisingly just flashing the file removed Magisk. It is easy to run into instructions for uninstalling that are outdated and do not work, but this file did it for me. The experience of the near loss of the phone was so traumatic for the owner of that phone, that I was asked not to install Magisk ever again not just on the particular phone but any future one that the person might own.
[Magisk] nowster:
Yes, that worked. Note that it's hiding the app, not MagiskHide.
[Magisk] AquilaDroid:
Pixel 5 on January update here. Is it still necessary to uninstall Magisk or remove installed modules before flashing February factory image? I've run into issues in the past if I didn't do that step. Currently on Magisk Manager 8.0.7 (4834) and Magisk 21.4 (21400). TIA!
[Magisk] Homeboy76:
Yes.

Why? Sometimes Google makes changes to the firmware that breaks some modules. This causes bootloops. So, it is better to be safe than sorry.
[Magisk] Boggle247:
I'm having an issue where magisk no longer provides root and the module selection appears to be missing. I've got a pixel 1 running lineageos 17.1 without any gapps flashed nor micro g. This seems to have happened after I updated to magisk 21.4. I've uploaded a screenshot of my magisk maganger app. How can i fix this ?
[Magisk] Homeboy76:
@Boggle247

<Edited for clarification>

Download the latest LOS zip, LOS recovery, GApps zip (pico/nano) and Magisk Canary (magisk-debug.apk) to your platform-tools folder on your computer.

(rename magisk-debug.apk - magisk-debug.zip

Install LOS Recovery/Boot LOS Recovery

Boot bootloader

Attach phone to computer via USB cable

Open a Command prompt in the Platform-tools folder on your computer.

Type fastboot flash boot lineage-17.1-20219999-recovery-marlin.img

ADB Sideload, LOS zip file:

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using:

adb sideload lineage-17.1-20219999-nightly-marlin-signed.zip

Reboot to Recovery

DO NOT reboot the phone

.

Reboot to recovery

makes the other slot active

LOS was installed on the other slot

.

ADB Sideload Gapps zip:

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using:

adb sideload open_gapps-arm64-10.0-nano-20219999.zip

If prompted that signature doesn't match, select Yes to continue.

ADB Sideload magisk-debug apk.

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using:

adb sideload magisk-debug.zip

If prompted that signature doesn't match, select Yes to continue.

Reboot

These should be installed: LOS, Gapps and Magisk
[Magisk] zgfg:
Did anybody with Magisk Canary 21407 tryt to Hide Magisk Manager (btw, why is the option still named that way, whereas Magisk Manager is now merged with Magisk and renamed?!) and then to patch the image?

Seems that it fails (at least) on A11 - it does for me (Xiaomi Mi 9T, Xiaomi.eu A11) and I found the same comment on Github:

Unable to patch boot.img · Issue #3811 · topjohnwu/Magisk

Pixel 5 on January 2021 patch. Unable to patch February 2021 boot.img on Magisk 21407 Copying image to cache Installation failed I looked at the app permissions and there are no permissions request...

github.com

Seems that Storage permission is missing (but in Settings /Apps I cannot give it to my hidden/renamed app)
[Magisk] Boggle247:
Just to be clear I don't have gapps installed. So I'd follow this minus the bits about gapps I assume.

I was planning on just extracting the boot.IMG from the Los version and release I am running, then patching it with magisk as outlined on the magisk github. Then adb fastboot flash boot patched.IMG, would that work?

Would either method preserve magisk so this doesn't happen again? Or do I have to do one of these every time there is a LOS or magisk update?
[Magisk] zgfg:
Also, what is the use of (changing) the Update channel in Canary 21407?

I changed the Update chanmel to Stable and it showed as the latest Manager version was then 21400 (which is not quite correct - 21400 is the last Magisk but not Magisk Manager version for Stable)

When I tried to install Manager - it failed with package parsing error (frankly, I didn't expect that downgrading the app could work)

But more important, image can be patched, but instead of patching with 21400 (Stable) it still patches with 21407 Canary

Before that merge of Magisk and Manager it was perfectly possible to patch from e.g. Canary Manager app with an older Stable Magisk (or vice versa), etc
[Magisk] Homeboy76:
Yes, skip. The Gapps section.

The method I posted works. I do it every time I update LOS. If @zgfg is commeting on my post, you have two options. The method I suggested or his method. Choose one.
[Magisk] Boggle247:
is there a solution so I don't have to redo this with every LOS nightly update? Seems a bit ridiculous....
[Magisk] Homeboy76:
I use that method because it works, it takes 5 minutes max. I do not update every time there is a new nightly build.

There may be another solution to your problem: You could try posting your question on the lineage 17-1 thread or google for solutions.
[Magisk] zgfg:
Sorry, this post here was my wrong experiment with the Custom channel in v21407, hence I deleted the post

There is the same problem with Custom Channel as when setting the Update channel to e.g. Stable (no additional issues for Custom), as in the quoted post above
[Magisk] Didgeridoohan:
@zgfg That boot patching with a hidden app fails is known and there's a PR available with a fix already.

And the "Manager" in settings will surely be changed in future releases...

And since the merge of Magisk and Manager is quite a big change I would not expect that patching with old releases work. Until this change has been pushed to stable/beta it's not strange that the update channels on the Canary app are a bit wonky.

Although, I do not see the behaviour you describe with the custom channel. Using that link I get v21.4 (21400).
[Magisk] zgfg:
But suppose generally, one day when Stable also goes to the merged Manager app and Magisk

Canary is usually higher version than Stable - hence you could not install older Stable Magisk (Manager) app from the newer Canary app

And if patching (and direct update) is tight with your installed Magisk app version, then you could also not go to an older Magisk (service) by playing with the Update channel, so I wonder should that option be removed
[Magisk] Didgeridoohan:
Shouldn't be a problem, because then the update infrastructure should be compatible.

If you need an older stable apk release they're all available on Github...

Why should it be removed? The update channels (even a custom one) will still be valid, just with the new infrastructure. If you need older releases, see my answer above. For current and future releases there will be no problem.
[Magisk] zgfg:
I know very well how to go with older releases (with the old infrastructure) but I'm talking about the new infrastructure, 'updating' to an older merged Magisk app + Magisk (even inside the Canary - try yourself from v21407 to v21406)

But we'll see when things stabilize
[Magisk] Didgeridoohan:
Ah... Now I see what you mean. The issue is that the new Magisk/app setup installs the Magisk internals from what's included in the app. If the update channels are to be preserved for future releases then it would be expected that those take precedence over what's available in the app and downloads the matching internals. You might want to update your GitHub issue to make that clearer. And maybe do something about the size of those screenshots (they're massive and makes it hard to find the text)...
[Magisk] zgfg:
Yeah - that was my point what should drive the patching/direct installing target version, Update channel or the installed Magisk app version

Btw, I deleted the part about Custom channel (also that post here), I had pasted the wrong URL causing the strange effect with v20.3

Screenshots were edited in Github issue to mark the point, but ok I also cut them off now to get them smaller:

Issues with Update channel in Canary v21407 · Issue #3818 · topjohnwu/Magisk

If I change the Update channel to Stable, it will show as the 'latest Manager' 21400 (which is not quite correct - 21400 is the latest Magisk but not Magisk Manager version for Stable) Anyway, when...

github.com
[Magisk] Homeboy76:
@zgfg @Didgeridoohan

This conversation is interesting thank you both for sharing. I have learned a lot. :)
[Magisk] rgawenda:
Same issue for me. I've even flashed system, magisk2, phh's root v2 and magisk's xposed clearing dalvik cache.
[Magisk] kraoc:
Can I get logfile after fail boot if I reinstall v1 or is the log overwritten ?
[Magisk] Gungrave223:
Dude you are a god sent.... :) its not much but i sent a little something your way...thanks again. ;)
[Magisk] nomadism:
Also had the same problem, but glad to know there is a solution! Could you clarify what exactly we need to uninstall first? TIA.
[Magisk] kirby2ig:
I think that your issue has something to do with verity. The verity patch was fixed in v2, so try flashing that and see if it works.
[Magisk] devilloki:
bug report

A proper bug report needs to contain the following:

Device Model: huawei honor 7 ,PLK-TL01H,china mobile

Android Version: 6.0

What mods you installed:no , my rom is stcok boot ,stock system.

magisk.log :no magisk log,because i am stuck in RECUSE MODE.

but i have rec log.

upload stcok boot,and Magisk patched boot. becasue the file is very large,so upload to netdisk.

http://yunpan.cn/c6XUPSUY9cTm8 （code：4ffe）