yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Thanks, yes I found there the Magisk Canary zips 20422-20427

Json files point always to the latest, hence here come links to my json files that one can use for Custom channel in Magisk Manager to download or to patch any of those Magisk Canary versions 20422-20427:

20422

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20422.json

20423

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20423.json

20424

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20424.json

20425

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20425.json

20426

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20426.json

20427

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20427.json

I've checked and that (in)famous MagiskR.zip as used elswhere for installing Magisk to my Mi 9T (and probably some others) Xiaomi.eu A11 beta firmwares is exactly Magisk-61599059(20422).zip (the same checksums)

If I patch my A11 boot.img with v20422, I can boot and I have root

If I patch with v20423 or any newer, then (ofc, upon flashing the patched img) it boots to Fastboot.

(Good thing is that I can still reboot to TWRP and reflash another boot image)

If I first patch the boot.img with v20422 and then re-patch that patched img with v21101 (v20423 or any higher) then everything is also ok, I boot to Magisk v21101

Hence the issue was introduced with certain v20423 commit(s)

Tested also that Magisk alpha build from @wb2060 on my Mi 9T Xiaomi.eu A11 beta (20.12.10) - Qualcomm Snapdragon 730, not MTK

Again, to use for Custom channel, one needs a json file with working URLs, like this:

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-wb2060-alpha.json

Patching the originall Xiaomi.eu boot.img works (like with 20422),not causing bootloop to Fastboot (like 20423-21101)

For the moment I don't observe other differences compared to v21101 (it was branched from)
[Magisk] pndwal:
Funny, I haven't actually flashed, but any json I've tried (here or elsewhere on GitHub) works fine (points to the specific build associated) in Magisk Manager Custom channel!

... simply click the json to open, Click the 'Raw' button above, copy the URL you are now viewing from browser address bar (eg https://raw.githubusercontent.com/vvb2060/magisk_files/alpha/alpha.json), paste this! Doesn't that work for you?

Yeah, seems @vvb2060 checked that too as he mentioned.

Good to know he's included this fix. 👍

Many commits he authored have already been committed by John in his Magisk Master repo, a number 10 days ago (others are still being reviewed), so hopefully fix will make it to official Canary w/ next build or soon after. vv2060 may now be rivaling osm0sis! 😬 PW
[Magisk] papperlapapp:
On a device with a/b partitions (e.g. Moto G7 plus), does it make sense to use the

--slot all option with fastboot, e..g

fastboot --slot all flash boot magisk_patched.img

Would that be better in any way when installing Magisk?
[Magisk] zgfg:
It will 'work' but it will not install particular magisk_debug.zip (old, custom), instead it will install the latest official Canary

Open e.g. in browser alpha.json from wb2060:

https://github.com/vvb2060/magisk_files/raw/alpha/alpha.json

and observe that 'link'

"link": "magisk-debug.zip"

is not a valid URL to his

https://github.com/vvb2060/magisk_files/raw/alpha/magisk-debug.zip

If you use Install in Magisk manager, Download zip only, Manager will download the official Canary 21101, not his custom one

(maybe his own app_debug.apk manager would have hardcoded proper link, but it does not work for Custom URL in the official Manager, using Custom channel).

Download that way and download tjw's official v21101, compare the sizes and checksums

When you open 'my' json you will see:

"link": "https://github.com/vvb2060/magisk_files/raw/alpha/app-debug.apk"

and that will force downliading and patching really magisk_debug.zip from wb2060

And that's anothet problem that was introduced two months ago to Canary jsons - previously canary.json had a proper URL to the particular magisk_debug.zip, now debug.json does not and Manager itself uses the hardcoded link to the latest magisk_debug.zip

Similarly, go to

Commits · AnErW/magisk_files-1

Magisk File Host. Contribute to AnErW/magisk_files-1 development by creating an account on GitHub.

github.com

take it for Custom channel in Manager 315 any of those debug.json files - use Install and Download or Patch, Manager will do it but using the latest v21101, not that v2042x whose json you used for Custom channel

QUOTE="pndwal, post: 84136657, member: 7550078"]

...

https://raw.githubusercontent.com/vvb2060/magisk_files/alpha/alpha.json), paste this! Doesn't that work for you?

[/Quote]

So did you open yourself that your own json you mention in browser, where do you see the valid URL to the particular version - check the screenshot?!

Instead, there must be the URL like on the second screenshot to force it to really use particular msgisk_debug.zip for Install (Download, Patch or Direct)
[Magisk] pndwal:
Ah, yes, I see the problem now.

I just tried actually using, not just pasting now, and get 'errror downloading' even for changelogs!... Will check this out further later...

Thanks for detailed analysis. 👍 PW
[Magisk] zgfg:
I thought it would be more complicated to overcome that problem with nissing URLs in json files (need to setup my own web server), but this was an excellent tip:

Plus, you gave me the links for Magisk zip files, and I spent half a Saturday locked to the couch, testing with my A11 - #stayhome 😷
[Magisk] dekadude:
EDIT : Deleted as my issue seems more down to some corruption on device despite multiple formats and it seems to be sorted now.
[Magisk] pndwal:
I created an issue for this:

Entering URLs for Canary build jsons in Magisk Manager Custom Channel results in error · Issue #3584 · topjohnwu/Magisk

Flashing archived builds by Patching/updating from Magisk Manager requires valid URL in Custom Channel. URL for raw json for archived stable/beta release builds are working as they contain full/val...

github.com

... Probably won't go far... Just want to see what response we get. 😁

You may want to comment there too. 👍 PW
[Magisk] J.Michael:
Do you need an HTTP server? Have you tried the "file:///" protocol in the URL in the JSON? (And wherever you specify the JSON's URL.)
[Magisk] pndwal:
Latest Magisk Canary changelogs:

Magisk (d0896984) (21102)

- Make sure post-fs-data scripts never block over 35 seconds

- Make sure boot stages never run in parallel

- Improve device compatibility by detecting 2SI later on legacy SAR devices

- Handle Windows file endline more gracefully

- No longer uses logcat to dump logs to files. Directly log to files internally.

Magisk Manager (d0896984) (316)

- A large number of small patches here and there

👏👍💪😀

This official Canary update includes a profusion of commits authored by GitHub Dev @vvb2060, some seven about 10 days ago, and some eleven more over the last ten hours. Clearly John has been flat out reviewing these to get new Canary published.

Also, it seems that several issues apparently fixed in @vvb2060's recent Alpha builds, will now likely be resolved in official Canary, including at least some of the issues that have stymied MTK Magisk SU use... I hope to hear some positive reports from MTK SOC users soon! (I referred to those issues here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84127839 ) 👍 PW
[Magisk] zgfg:
Please read the conversation. It was not the point of creating an URL inside the json file (corresponding magisk_debug.zip files exist on Github, hence they do have links I could use them in my custom json files), but where to put that custom json to be able to use it for the Custom update channel in Magisk Manager

AFAIK (that would be a good feature I was also thinking about) Magisk does not support local json file (on the phone) for Custom channel via file:// protocol (you could test and report😎)

But all that was not needed, I simply uploaded my custom json file to my Github account (the tip was in already having my Github account and just use it for that - however, many users here do not have their Github accounts), get the link for my uploaded json from Github and set it to the Custom channel (btw, I first tried also by uploading json to Mega, but the link from Mega didn't work for the Custom update channel in Magisk Manager)

Edit: No need for you to test😌, just tried Custom update channel with

file:///sdcard/Download/debug-20422.json

and variations, did not work (Latest version showing as N/A)

And there is no really a point for the other test, putting json publicly to Github but defining inside the json magisk_debug.zip from the local phone via file:///
[Magisk] pndwal:
Haha, I just tried / failed with zackery same test... was hopeful... 😉 Well, it was/is a good suggestion! PW
[Magisk] pndwal:
Canary json issue got closed by John, but I'm hoping for further response. PW

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84138707
[Magisk] tmiller101:
Is it better? I dont know. I found on my G7, sideloading Magisk from TWRP into the slot the system boots from works fine. Easy, simple.

Not sure what advantage you would gain by running the above fastboot cmd...
[Magisk] zgfg:
Canary 21102, Manager 316:

- When patching, it shows now the target (patchung to) Magisk version, and current Manager version (not so important)

- Patched images now have random names like nagisk_patched_QFJw.img,

preventing that subsequent patcheding overwrites the previous

- Important:

It's fixed now for my Xiaomi.eu beta, I patched directly with 21102 my original boot.img (without pre-paching by MagiskR aka v20422), and it booted and worked (no more rebooting to Fastboot)👍
[Magisk] Arz_Ary:
How i can bypass this app?

I have enable magisk hide & add this app to magisk hide. My phone also pass safetynet
[Magisk] wallace108:
I can happily report that with the latest MM 316 and Magisk 21102 I was able to finally get root on my MTK device with Android 10 (namely Oukitel WP5 pro). Thank you @topjohnwu
[Magisk] pndwal:
Better thank GitHub Dev @vvb2060 especially for that. Great bit of progress! 👍

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84127839

Thanks for heads-up! ... See next post also. PW
[Magisk] pndwal:
Why so long John?

Well, you're only human!

Important fixes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84139323

New-commit Talley (57):

23 @topjohnwu

18 @_vvb2060

7 @RikkaW

2 @osm0sis

1 @_tzagim

1 @Antikruk

1 @_breakdowns

1 @_cocka11

1 @kubalav

1 @omerakgoz34

1 @_sn-o-w

MANY thanks to ALL the contributing Devs! It's a BIG one. 👍

... and so do we. 😃💪 PW
[Magisk] wallace108:
Hey, thanks for the heads up pndwal. So my big appreciation goes also to @vvb2060 for this so much anticipated fix.

Now I can only hope for a good working TWRP recovery for the WP5Pro. Whenever that is going to happen ...

Mike
[Magisk] T.A.R.D.I.S.:
21105 passes on 8T on 11.0.5.6

No bugs at all for the moment.

Thanks 👍👍
[Magisk] zgfg:
Fixed and closed'👍👍👍

MagiskR - patch for Xiaomi Mi 9T, A11 beta?! · Issue #3534 · topjohnwu/Magisk

As claimed elswhere (I didn't try A11 beta myself), the only way to install Magisk to Xiaomi.eu A11 beta for Mi 9T requires: flashing through TWRP MagiskR.zip https://mega.nz/file/R9lwQbaA#od4dnJOm...

github.com

and the new opened:

[Feature] File or Content type URL protocol support for Custom update channel · Issue #3588 · topjohnwu/Magisk

Please add file:// protocol support for URL to the json file in the Custom update channel for the "link" value in json file pointing to the magisk zip E.g., that we could set Custom update channel ...

github.com
[Magisk] sachaweb:
First-time user: the app stays incomplete after install.

All I see is the basic screen with the links to install Magisk and Magisk Manager. SafetyNet test fails.

I flashed Magisk.zip with TWRP, then rebooted to system and ran the Magisk Manager APK. From within the app, when requesting an install of M or MM, it all looks like it's running smoothly but afterwards the app is still the same: just that basic screen, no checks, just the SafetyNet check (which fails). My device got rooted though.

Any solution to that?

And can I just install a custom ROM (probably LineageOS) now? Or is it a problem that the SafetyNet test fails? I do want to be able to use banking apps.
[Magisk] eracet:
Searched for a while. Trying to figure out how to get magisk running on oneplus 7t

I always flashed with TWRP , but this is not an option right now. Since it has locked down data.

Installed magisk manager and have newest zip file.

Just not sure the easiest way to get it on phone and flash it.

Seen that you can flash it over with fastboot or adb. But it would be a zip file and that isnt correct.

Can someone help me get on the right path for this problem?
[Magisk] Slim2none4u:
Extract the boot.img from your factory software and transfer boot.img to your phone.

Open MM and select install. Then select "Select and patch a file".

Navigate to where you placed the boot.img and select it.

Then tap "Let's Go" .

It will output a file in your downloads folder named "magisk_patched.img".

Copy or move that file to your computer.

Open a command window and type adb devices and hit enter to ensure your computer sees your phone.

Then type "adb reboot bootloader" and hit enter.

Now type "fastboot flash boot magisk_patched.img --slot all" and hit enter.

Type fastboot reboot. Hit enter. Profit!

Peace! ✌

P.S. This assumes you have system wide adb/fastboot.

If not then place the magisk_patch.img in your adb folder and follow the same commands.
[Magisk] pndwal:
It's all clearly outlined in official Installation Instructions linked from Magisk main page. (Click GitHub (cat) symbol on Magisk Manager home page under Support Us, @topjohnwu.) Essential reading really. 👍

Patching Images (ie. boot/recovery image) method is now the preferred method. "The Custom Recovery (flash zip) installation method exists mostly for legacy support."

In any case, seems OnePlus 7T shipped with Android 10, and therefore there is no compatible TWRP for it. (TWRP has not been made compatible with any devices Launching with Android 10 / new Dynamic/Logical Partition file structure, but it may still be used if only booted from PC ADB Fastboot, NOT flashed (installed) on such devices.) 🤠 PW
[Magisk] Didgeridoohan:
What do you mean that it is incomplete? Maybe you missed the small navigation bar at the bottom of the app where you can switch between the different screens (main, superuser requests/MagiskHide, logs, modules). A screenshot might help if this isn't what you mean...

SafetyNet might be failing for a number of reasons, first being that MagiskHide needs to be activated. More on SafetyNet here: https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Installing a custom ROM is not affected by SafetyNet, but some bank apps might not work on a custom ROM (more on hiding root from apps here: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps).
[Magisk] wallace108:
I recently installed Flashfire on my Oukitel wp5pro after having successfully activated root access with the latest Magisk canary build.

However even if Flashfire detects and is granted root by Magisk (I double checked that), still it says it can't have access. https://ibb.co/SrwR2PC

Does anybody have an idea why is that?

My device runs Android 10 and is SAR.

Thank you.
[Magisk] Slim2none4u:
Flashfire is not android 10 compatible and says so when you first launch it. It's not been updated for some time and frankly is obsolete.
[Magisk] Didgeridoohan:
FlashFire is pretty much abandoned... It won't work with current Magisk releases.

For many things that FlashFire could do I'd suggest @franciscofranco's FK Kernel Manager.

Edit: Ninja'd...
[Magisk] wallace108:
rhewins2268 and Didgeridoohan

Thanks guys for clearing that up and your suggestions.

Cheers
[Magisk] flroots:
I'm using Magisk on my Moto G Stylus for first time. Does it matter whether I install it via apk file or zip file using TWRP? I'm especially interested in ability to download OTA's while retaining root. Thanks
[Magisk] zgfg:
OTA depend on your device - it's not part of Msgisk.

It doesn't matter how you install but Magisk Manager app is not Magisk itself, it's just UI to manage Magisk (as the name says)

Install Magisk Manager, find the link and open Documentation and Wiki on Github to read how-to install Magisk by use of patching through Magisk Manager app (for device specific details check on your device forum)

For the new devices, maybe there is no appreciate TWRP in which case Installation through TWRP may no more apply
[Magisk] eracet:
Ok I think I get what needs to be done. But having issues finding out how to get boot.img to modifiy.

Seen things like python I can extract from the newest oneplus site payload.bin. But not sure if this is the best option or is there another option I should try.

UPDATE: Flashed the magisk_patch.img VIA fastboot. But when doing safety check it comes up failed. So not sure if it installed correctly. From what I can tell the image flashed.

Basic integrety is checked CTS profile is - (looks like root was successful just not sure about the error)
[Magisk] pndwal:
- https://topjohnwu.github.io/Magisk/ota.html

- https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md PW
[Magisk] pndwal:
Extract boot.img from ROM Installation zip package...

Well done. Magisk setup should be fine if 'Latest' under Magisk (Manager home page) shows version number.

Not sure of your SafetyNet results. For instant relevant advice here, please say exact status of basicIntegrity, ctsProfile and evalType! 👍 PW
[Magisk] wfred:
Here's the 7T guide rooting guide, including Magisk instructions

https://xdaforums.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
[Magisk] itchyUnder:
Samsung Galaxy s20 Ultra, Snapdragon

Magisk 20.4 (20400)

Magisk Manager (8.0.3)(314)(14)

I just flashed up to Android 11. I had used Magisk to patch the AP, which I used in Odin.

My phone is set up and running. I started up Magisk Manager but I don't see the modules button. The settings seem like its missing some features as well.

Did I miss something in the configuration process?
[Magisk] Didgeridoohan:
Magisk v20.4 isn't compatible with Android 11... So far, beta or Canary would be the releases that work.
[Magisk] itchyUnder:
I went into the settings and switched to the beta channel. It updated Magisk to 21.1 (21100). Manager did not change.

Is this the correct way to switch to the beta version you speak of? I am still not seeing the modules panel and settings I am use to seeing.
[Magisk] Didgeridoohan:
That would be the correct update procedure. But it does sound like you had Magisk working properly, so I don't know that's going on there...

Are you simply referring to the ui change from Manager v7.5.1 to v8+? If so you'll find modules in the bottom navigation bar, the rightmost puzzle icon.
[Magisk] itchyUnder:
Magisk worked when I was on Android 10, now I am on Android 11.

I don't have the navigation bar at the bottom at all.
[Magisk] Didgeridoohan:
Is Magisk even installed? How about providing a screenshot of your Manager... Would remove some of the guesswork.
[Magisk] itchyUnder:
Now that I look at it, it says Magisk is not installed? How would I correct this?

I built the Magisk patched AP via Android 10. Could this be the problem? Do I need to repatch the AP with my current version of Android 11 and reflash in Odin?
[Magisk] Didgeridoohan:
Can't hurt...
[Magisk] flroots:
Thanks for the links. I like the fact they even show screenshots of each step. Hard to make a mistake :) I was also asking the following:

At github it's listed as an apk, but I've read discussion that state you should install it as zip file with TWRP. I'm guessing that both are equal and maybe apk is the newer and easier way to do it. I'd like confirmation going forward.
[Magisk] pndwal:
Sorry, this was already answered; my references were suplementary (but to official documentation)...

To clarify however, Magisk (SU) is NOT the APK. That's the Manager, and it can be installed before or after flashing Magisk (- Legacy Custom Recovery (flash zip) installation method usually installs both Magisk and Magisk Manager anyway).

You should read the official Installation Instructions before asking here as It's all clearly outlined there. These are linked from Magisk main page. (Click GitHub (cat) symbol on Magisk Manager home page under Support Us, @topjohnwu. to get there.) Essential reading really. 👍

This outlines the different device-dependant methods. In your case, you have a modern device that Launched with Android 10, and therefore there is NO compatible TWRP for it. (TWRP has not been made compatible with any devices Launching with Android 10 / new Dynamic/Logical Partition file structure, but it may still be used if only booted from PC ADB Fastboot, NOT flashed (installed) on such devices.) "The Custom Recovery (flash zip) installation method exists mostly for legacy support."

In other words, you should KEEP STOCK RECOVERY, and use Patching images (ie. boot/recovery image) method which is now the preferred one. Extract boot or recovery image from ROM Installation package, patch by selecting 'Install' (Magisk) from Magisk Manager (install that first from APK), then flash using PC ADB Fastboot to do this.

Whether you need to patch your boot or recovery image will depend on ramdisk functionality in boot partition as discussed in Installation Instructions.

Hope this helps, 🤠 PW
[Magisk] itchyUnder:
Repatching the AP and flashing it fixed the problem.
[Magisk] flroots:
Thanks so much for taking the time to respond. Wow, that's going to take some time to fully absorb. One point of confusion. I did flash an unofficial version of TWRP that maintains touch capability and seems to work in all respects. I have made a number of Nandroids with it and even restored from one as verification. I assume that without TWRP that would not be possible.
[Magisk] zgfg:
TWRP by definition works with touch: Team Win(dow) Recovery Project.

However, there are possible issues like TWRP not supporting encryption of Data and Internal storage, etc, or even that TWRP was not ported to the particular device

When you 'absorb' the given documentation 🤩 (follow also conversation here to other users, questions and answers) you will see that Magisk can be installed completely without the use of TWRP - by extracting the boot or recovery image, patching it in Magisk Manager and then flashing the patched image in Fastboot.

There is no word about TWRP and flashing the Magisk zip file in that method.

In fact, that is even the preferred method as mentioned in the Magisk documentation - in that case you don't depend on the existence or not of the TWRP port to your device and its possible issues.

Generally, for the new devices released already with A11, do not expect to have (the appropriate) TWRP and only that method with patching and flashing the image will apply
[Magisk] Listerine:
So quick question: let's say I install Magisk and install another ROM and clean flash the zip. I assume it will get rid of all traces of Magisk right? Or will it persist like TWRP recovery?
[Magisk] pupido:
After letting the 2 year warranty pass, today I decided to root my Note 9 with Android 10.

Well, after flashing the Magisk v. 20.3 zip I thought my phone was finally rooted.

Instead, using the Root checker app I discovered that the Note 9 is not rooted.

So, I open Magisk Manager for the first time and I get this strange message: "Your device needs additional configuration to make magisk work properly. The magisk zip file will be downloaded, do you want to proceed now?"

But is this normal? Since I haven't used Magisk for about 3 years, I remembered that all I had to do was flash the zip and that was it.

What should I do now?

However Magisk Manager confirms that v. 20.3's magisk is installed but invites me to update to v. 20.4.