yashsingh1/xdaforums huggingface dataset:
[Magisk] farvehar09:
How to patch boot.img file on xiaomi redmi note 9 with magisk

I should uncheck "preserve force encryption"

And "preserve AVB 2.0 /dm-verity" before patch?
[Magisk] wbedard:
Same...OnePlus 6T running stock OxygenOS 10.3.5
[Magisk] palmbeach05:
As clearly detailed on github and across every major development platform, canary 20421 is damaged goods, and creates bootloops. We know this, its a well established fact. We do not need to keep going on about it, regardless of what device or rom you have. This release should be avoided.

Canary 20422 has the same amount of coverage, as it provided a fix to a limited amount of devices. Some devices have issues. Again, well documented, and should be avoided.

Canary 20423 is where the majority have no issues. Some still have issues, and the errors should be reported to topjohnwu's github page. I think he even said something to the effect of he's not checking xda much/anymore, and that he will primarily be operating from github.

Also, magisk manager issues are also being discussed on his github page, its a known issue that you guys are talking about

---------- Post added 5th September 2020 at 12:26 AM ---------- Previous post was 4th September 2020 at 11:43 PM ----------

Canary 20424 released. Fixes selinux rules on android 8 through 10

https://github.com/topjohnwu/magisk_files/blob/canary/magisk-debug.zip

All you magisk manager issues ppl can stop complaining now.

Released 2 hrs ago (at the time of this post going up). User below posts about it 3 hrs after release, and and hr after i posted about it.
[Magisk] pndwal:
Guys, we all want to have our cake eat it too, ie latest Android WITH root permission! (And SU Hide as long as it lasts!)

To have upcoming RVC (Red Velvet Cake https://www.xda-developers.com/android-11-red-velvet-cake/amp/ ) w/ MagiskSU, some hazardous test flying of untested engineering is required.

Our chief engineer is on a mission to ensure his customisation to the flight console is compatible with the latest model BEFORE it reaches production, and he has only has a few prototype (beta) airframes to work with.

One of the key problems he's now clearly working on is 2SI device checking (needed due to changes in ramdisk structure in Android 11) for affected SAR A-only devices, and changes to this logic seems to be affecting compatibility with older devices and platforms in Canary builds.

In any case, John Wu is aiming to produce v21 Stable quickly.

https://mobile.twitter.com/topjohnwu/status/1301011553819348992

This regarding leaked release date of Android 11 for Pixels, as well as Open Source code for AOSP:

https://www.xda-developers.com/stable-android-11-update-september-8th/

... and development accelerating for others:

https://www.xda-developers.com/xiao...g-beta-testers-respective-android-11-updates/

The fact that John is trying to beat a Sept 8 deadline for this, even if it's unlikely Google will deliver their Mark 11 (RVC) system by then, means test builds are being pushed out rapidly, and there'll no doubt be a number more before official RVC arrives, whenever that transpires.

This means it may be prudent to stay on stable ground, or at least a relatively stable Canary build till v21 arrives - unless you're a daredevil, love to be challenged, or simply want to be on the bleeding edge... test builds have a greater potential to crash and burn.

I'm waiting / watching while the intrepid do the test flying.

Remember, if you are carrying the canaries into the mineshaft, you are not only doing others the service of monitoring danger, but you need to be prepared to get out yourself when the canaries fall over.

"Son, your ego is writing checks your body can't cash." (Stinger)

If you're a wannabe Top Gun, or simply love the thrill, safe flying!

"I feel the need -- the need for speed." (Maverick & Goose) PW

Latest fix / build:

"Magisk (20424)

- Fix SELinux rules from Android 8.0 to 10"

Recent fixes:

20423

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83430277

20422, 20421

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83429365

For the Top Guns:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83427423

Likely reason for buggy releases:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83414511
[Magisk] zgfg:
Extract boot.img from the so-called recovery/zip package (must be exactly the same MIUI version and the same EI/CN/RU as you have installed on your phone).

Install Magisk Manager app to your phone (Magisk is not yet installed, doesn't matter), choose Install Magisk and then Patch the file.

There wil be three options: Preserve encryption, Preserve AVB, Recovery (all three are On by default).

Keep the first two On, but put Recovery mode to Off.

In the new Canary Magisk Manager there is only Recovery option (you must uncheck to Off), controls for the first two are removed ('hardcoded' to On).

Then navigate to your boot.img file and proceed, patched file will be saved to Download folder.

Reboot to TWRP and flash the patched image to Boot partition, or copy the patched image to PC and flash to boot from Fastboot

Reboot, Magisk Manager (MM) will show that Magisk is installed. Go to MM Settings and toggle Hide Magisk to On and reboot - then, you will be properly rooted
[Magisk] Thaiban:
Please some one update me
[Magisk] zgfg:
Asked and answered here a week ago, and a week earlier

Again (one method) - go to Manager settings, choose Custom for Update channel and paste the URL:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json

Go back, Manager main page will give you the options to update Manager and Magisk to the latest Canary

Given Custom link should always show to the latest Canary, but (upon switching to Canary) change the Update channel to Canary (just in case, if the structure on Magisk GitHub would ever change)
[Magisk] farvehar09:
Thank you, but why do people say in my phone forum to uncheck three options?

which one is correct

My phone does not softbreak or hardbreak
[Magisk] Didgeridoohan:
[MENTION=9312296]Thaiban[/MENTION] Keep in mind that the Canary releases are bleeding edge builds meant for testing and quite often have bugs that might render your device temporarily useless. What I'm saying is: be careful...
[Magisk] Thaiban:
Thank you [emoji4]
[Magisk] zgfg:
People unnecessary decrypt Storage.

Given instructions are ok if you patch the stock, and if you didn't decrypt Storage (that is absolutely not necessary for installing Magisk to stock firmware)

Otherwise, ask those guys on your Forum

(I'm on Mi 9T, MIUI 12, Android 10 - and I was rooting that way my phone since its original MIUI 10, Android 9, with no problems whatsoever)
[Magisk] Thaiban:
Than i will stay in normal in one , thanks for advice
[Magisk] dnsmo:
I am on 20423 and now magisk is no longer working, I mean the application itself just hang, I don't get to see the items inside the app now. Anyone else seeing this?
[Magisk] dope77:
[MENTION=2769491]wbedard[/MENTION]

Flashing 20424 will fix this issue
[Magisk] dnsmo:
I am on pixel 3, can't flash
[Magisk] Didgeridoohan:
That's a selinux issue and is fixed in 20424. You can temporarily set selinux to permissive to be able to open the Manager to update.
[Magisk] dope77:
Can't you just direct install it from the manager?
[Magisk] dnsmo:
the manager is not working as I stated, the manager application freezed.

---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------

How do I set it?
[Magisk] cnjax:
Problem is I believe the original intent of this thread was for support on stable versions of magisk. Soon the thread became flooded with canary build issues, irc there's a separate canary thread where these discussions should be posted. What users need to realize is canary versions are basically alpha releases so you should expect issues and be ready to troubleshoot your problem before flashing it.
[Magisk] dnsmo:
I have to reinstall the magisk using adb to flash the original boot.img then restart the installation process. Everything is good now. Thanks everyone for helping.
[Magisk] wurstherpes:
No matter which version I use, the problems are always the same.

I hide the name of the app and hide the desired app.

If I start s-pushtan the app will abort and a message will be displayed that the phone is rootet.
[Magisk] zgfg:
Very simple, if you didn't know yet, Canary Magisk thread is closed since March:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] palmbeach05:
I have to agree, since it got shut down this has essentially become the all in one magisk support thread, not just for stable.
[Magisk] Alxoom33:
I'm on Taimen (Google Pixel 2XL), running Android 11 Beta 3. Just my 2 cents- Happily, Magisk Canary v2024 seems to have done the trick! Booted up fine, MM opened and is working without a hitch. Thank you [MENTION=4470081]topjohnwu[/MENTION] :)

BTW, my Dragon-Pixel C tablet is running an Android 10 custom rom. I use Magisk Stable builds for this device.
[Magisk] pndwal:
Yes, Canary builds are very necessary for some, of course.

For example, Canary Magisk Manager is highly desirable to determine attestation type used by SafetyNet.

Canary MagiskSU is plumb necessary for some who need recent experimental features or new compatibility, eg for rooting Android 11 beta, but I'm sure many avoid more recent Canary updates once they're happy with MagiskSU functionality for good reason.

Some of the (frequent) builds are buggy, recently causing modules not to load, problems repackaging Manager, bootloops, and many other problems. These are usually resolved in short order, but, for me, stable MagiskSU and resetting chanel to Stable after installing Canary Manager gives the best experience. (we've had latest stable build since March.)

This, as well as the fact many are treating fresh Canary builds like tested software updates (expected to reduce bugs and improve experience), is why I said "This means it may be prudent to stay on stable ground, or at least a [relatively] stable Canary build till v21 arrives", meaning that once you are happy with system and stability etc, don't take FURTHER Canary updates "unless you're a daredevil, love to be challenged, or simply want to be on the bleeding edge..." (These updates will often ADD bugs and degrade your experience, at least for the short term.)

Note what John Wu said himself:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post77549897 PW
[Magisk] pkgnex:
Just posting to say 20.424 is working absolutely fine with direct install method from. 20.420 on Pixel 4 XL

I skipped 20.421/2/3 based on what I was reading on this thread..... thanks to those early adopters for posting.!
[Magisk] zzz2002:
20424 works for SM-T813 (gts210vewifi).

Thanks.
[Magisk] xunholyx:
Stable Canary build? wat?
[Magisk] pndwal:
Well, granted, this really embodies the whole point of the caution not to treat Canary releases like tested software updates, which I further clarified here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83439033 ... And it did occur to me that I may be picked up on this.

So point taken! My use of 'stable' in this instance may (fairly) be viewed as a contradiction in terms despite some Canary releases being patently more stable than others (some even containing less instabilities than some Stable releases).

It's worth noting however, that the dev himself said "Be warned: Canary can be unstable", not "is necessarily" unstable.

In any case, for the sake of clarity, I have edited the post to read "relatively stable" here. Thanks for the critical appraisal! :) PW
[Magisk] ipdev:
Just because everyone is wondering..

Yes the newest canary build is working on ..

Nexus 10 Google stock 5.1.1 :laugh:

Seriously though, I was testing a module for backwards compatibility and well, why not use the bleeding edge build of Magisk..

Cheers. :cowboy:
[Magisk] pndwal:
Good use/test of prototype controls in old airframe by seasoned professional pilot, knowing how to duck and eject safely in case of failure! ? :good: PW
[Magisk] m99570:
Just posting to say 20.424 is working fine with direct install method from. 20.420 on Nokia8 (oreo8.1)

but it isn't working on my Nokia5(pie).

It's looping in boot. So i flash back to magisk20240.mm297.patched.img.

That's working fine on Nokia5(TA1053) pie.(install option cancel recovery mode)
[Magisk] zgfg:
What kind of logs would be useful for failing Hide (repackage) Magisk Manager (Canary 297)

I checked in Magisk log (right after the failed attempt) - as copied and attached, but I can't find anything for: Hid, Repack, Fail or similar.

I also captured ADB log, did not find there either
[Magisk] Danis180:
guys, which modules u can recommend for android 11? about sound(viper not working) about performance and etc:)
[Magisk] sidamos77:
Sparkasse? You need Magisk Canary and older version of the Push Tan App. You can also try flushing the cache of that app.
[Magisk] Didgeridoohan:
A logcat captured during the repackaging would be ideal.
[Magisk] wurstherpes:
Yes i use magisk canary but version 20420 and it works with s-pushtan.
[Magisk] @kitokit:
Does anyone here able to run stc pay in KSA?
[Magisk] zgfg:
Thx, attached (I will later report also to GitHub)
[Magisk] xdam57733:
Today my mobile antivirus G-Data started identifying the com.<random-package>.apk of Magisk Manager as a trojan. That probably and hopefully was a false positive. I think I got the Magisk Manager from the correct source, but that was a few months back, so cannot really confirm, but I have uploaded to virustotal.com and metadefender and only K7GW in virustotal thinks this is a trojan too.

Looking closer at the apk with the random package though, I wondered why it was only 28kB, whereas the original Magisk Manager apk is much bigger. Is that normal? Is that only some kind of stub calling the "real" one (which I did not see on my phone, but maybe I just missed it).

Thanks for some insight by you more knowledgable folks.
[Magisk] zgfg:
Yes, stub only. That's why it asks to install the rest when you first time start the repackaged Manager

I think there was a similar question and a detailed answer few months ago (or more - time lapses quickly) maybe you could find it
[Magisk] mrbonine:
Haven't been able to reinstall Magisk

I don't have TWRP had tried to install but failed and had to reinstall Magisk. I got the typo release

(And I'm the type-o' guy who tends to hit or discover every minor thing). I assume the Magisk install erased the .img file after install (as it should). I'm still trying to follow the requirement to use only /fastboot or /adb to move the patched file back to phone but can't get fastboot or adb to respond on phone, even after reinstalling pc drivers. Win 10 is connecting but I'm not seeing the correct stack in devices & printers. I'm unclear about where the following is installed: phone or PC? <Installed adb+fastboot drivers (just google it and find the XDA link) and downloaded the option cmd.zip to easily access fastboot.> Would like to add TWRP (the only system backups that ever worked for me) but I'll settle for my root dependent apps to work again. I tried Samsung standard restore but was likely hitting those with a zip (can't remember) since I can't find img or tar on phone, but def have it on PC. I don't know that I asked for help when i reported the bootloop, but likely need it now. Advice? As complex as this has gotten (and everyone working and creating this are developer heros to me) I may need a single path detailed guide to survive dumb user-o, me.

Thanks, Mark

In
[Magisk] pndwal:
...

Might be good news for Samsung fans!

Looks like he's getting Samsung Galaxy Z Fold2! (£1665.74) ... Just cause Pewdiepie has one...

Nah :laugh: -

https://mobile.twitter.com/topjohnwu/status/1303139288112967682 PW
[Magisk] pndwal:
John Says Canary is "Stable enough" for most (Including many Android 11 beta users).

But he's going to miss his target date (8 Sept) for fully rewritten Public Release Magisk Manager due difficult issues with it.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83433173

The rumor is that Google will release Official Android 11 (RVC) by 8 Sept, but what's a week or three between friends?

Glad to hear new release is at 'wrap up' stage however. ... Rooting for you John! :good:

https://mobile.twitter.com/topjohnwu/status/1303211915091390466

John announced Magisk is at "Feature Freeze stage" for v21 about 2 weeks ago, so we won't be getting Custom Repos this time, but he's promised to add this as a feature "after the next stable [public] release".

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83341897 PW
[Magisk] JDubbed:
Magisk is failing safetynet checks. I'm on Magisk 20.0 and Magisk Manager 7.3.5. Do I need to update Magisk to correct the safetynet failure or is there something else I need to do? Based on posts I'm not confident I want to update in fear of boot problems and just don't want to deal with that mess right now. I'm using a Razor Phone 2. Thanks.
[Magisk] pndwal:
I recommend 20.4 Stable (recent boot problems have generally been in Canary versions post 20420), but that's probably not related to version.

Solution differs depending on how SafetyNet is failing, and you haven't said.

If you were passing till recently and it's ctsProfile fail, your device is likely triggering Google's new Hardware Backed attestation for bootloader unlocked status.

To check this, flash latest Canary Magisk Manager. Status is shown in SafetyNet Check. (You shouldn't have any problems with Manager only, but I'd avoid Canary MagiskSU unless you have a specific need.)

We can spoof passing device for now. Latest / versatile solution added to MagiskHide Props Config Magisk module:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83148385

If ctsProfile fail but newly installed ROM, you likely need to spoof a passing fingerprint prop. Same module has this function.

If basicIntegrity fail, you have a different problem. See here for starters:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469

Please say if this helped, and give more details if not. :good: All best, PW
[Magisk] pndwal:
And I doubted. Well, the rumor mill was right on! Official Red Velvet Cake is here:

https://blog.google/products/android/android-11

Not just for Pixel either:

https://www.xda-developers.com/android-11-update-tracker/

Pretty hard for a one man army to keep up! Go John! PW
[Magisk] bosox284:
Debating whether or not to plunge and attempt 20424 on my Pixel 4. I hate to be one of the first to attempt, but I would really love to give 11 a go.

Edit: Took the plunge. Downloaded and installed Canary build 20424 on Android 10, flashed it onto the Android 11 boot image, flashed Android 11, booted up the phone, waited until the update finished, flashed magisk_patched.img and I'm back up and running. So far so good.
[Magisk] stupdude2:
Pixel 3 here running Android 11 with magisk_patched.img. Root is working but magisk modules aren't showing up in Magisk Manager.
[Magisk] zgfg:
Use root explorer like MiXPlorer and check are there modules installed to /data/adb/modules

If not, they were lost from Data during the OTA
[Magisk] bosox284:
No issues with modules showing up for me. Did you do OTA or the full factory image? I dirty flashed the full image.
[Magisk] stupdude2:
Got it working: I had installed the Magisk Canary beside the previous Magisk, was able to patch the image with it but many of the settings were disabled, like modules. When I restarted, the Canary version disappeared, leaving the original version which was unable to see the modules. I uninstalled old Magisk, reinstalled Canary version and now modules are showing up! Thanks for your help!
[Magisk] Ch3vr0n:
Pixel 3xl up and running on A11 with latest canary, latest stable DOES NOT work.
[Magisk] zgfg:
It is expected that for now the latest Stable 20400 (pretty old, not containing changes for Android 11 made to Canary 20424) cannot work for A11
[Magisk] Ch3vr0n:
Yup, I just forgot to update to the latest canary before updating. It's not like we get a major os update every few months.
[Magisk] mk262:
edit: nvm I found
[Magisk] docluv01:
Hi Guys, for those of you using canary, does this version still have hide magisk manager? I can't seem to find it.

TIA!
[Magisk] RandomPooka:
If you open the manager settings, it's in the main settings page. It's the bottom setting in the second grouping of settings titled "Manager"
[Magisk] docluv01:
forgive me....this is what I see under Manager:

Update Channel

Custom Channel (greyed out)

CHeck Updates

Download Path

Clear Repo Cache

After that the next section is Magisk

I have Canary version 297 installed.....
[Magisk] Ch3vr0n:
Are you on the canary manager?

That said, any rust with a pixel 3xl having frequent kernel panics (I believe that's what they are. Device stops responding requiring a hard reboot). At least when the device is on/comes off a pixel stand after charing for a while (with screen on 'off when dark' mode)
[Magisk] ReservedName:
has anyone gotten a pixel 4a updated to android 11 with magisk?
[Magisk] palmbeach05:
Topjohnwu's device is updated to android 11 and using latest canary. Not sure what he has, obviously a pixel
[Magisk] xunholyx:
He has a Pixel 4 XL
[Magisk] bobafuzz:
I'm experiencing the same thing with my 3 XL, had to flash back original boot.img to be stable. No root for now =/
[Magisk] pndwal:
Pixel 4XL, had 3XL also. 4a should be fine... PW

...sorry answered above...
[Magisk] Fwaiiiz:
Just updated my pixel 4 to Android 11, and using Canary build

I'm not passing the cts profile.

Not sure if it's because of the canary or it's from Google's end ??
[Magisk] pndwal:
https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83454681
[Magisk] Cares:
I'm on a 4XL and I need Canary to patch boot and root otherwise I will bootloop with Stable. Are you saying I should switch back to stable after rooting?
[Magisk] Valiante:
Looks like this broke my Pixel's unlimited original photo and video backup. FYI
[Magisk] pndwal:
Well, cited post was a reply to a user on old 20.0 stable asking if he should update, and I recommended moving to 20.4 Stable...

I'm guessing you're on Android 11? If so, you need Canary. Most others should be fine with latest Stable.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83439033

My cautions are because John is moving fast to integrate a ground-up rebuild of Magisk in next stable which has, in turn, created more problems than normal in [experimental] Canary builds. This includes trying to fix 2SI device checking for affected SAR A-only devices, which is preventing even Canary MagiskSU working with A11 on these devices presently.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83433173

Many w/ A11 will wait for new Stable Build, which he couldn't produce in time for Official A11. And for those who don't want to wait, he's said [latest] Canary is "Stable Enough" for many users.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83453781

As I've said, if you have a 'relatively' stable Canary MagiskSU working for you, just don't take Canary updates (unless you really want to be on the bleeding edge)... PW

---------- Post added at 06:09 AM ---------- Previous post was at 05:42 AM ----------

Yes, it's known to break device specific functionality.

But new fix in MagiskHide Props Config module usually allows these functions to work by using older props from same OEM. And it allows for custom configuration & experimentation when default setting fails.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83148385 PW
[Magisk] dnsmo:
magisk 20.4 with Android 11 on Pixel 3 XL, after apply the magisk_patched.img to boot, the screen no longer accept input. Anyone else experience this problem?