yashsingh1/xdaforums huggingface dataset:
[Magisk] lodufkah:
hi, got few qs about, if I may:

1. did you flashed the boot.img patched with canary version - like a normally patched boot via fastboot?

2. is safetynet ok & google pay works fine?

I'm on P2XL and with Android 11 thinking if I need to wait more for stable version, risk the canary or bite the bullet & [I don't believe I write this] to lock bootloader [but device wipe & losing all my different apps configuration would be a hard thing to recover I guess]. I need google pay to be working, but don't want to mess up with my daily driver as I don't have any emergency device right now at hand :(
[Magisk] Dunge2:
Pixel 2, updated to Android 11 successfully (booted to system), and then flashed Magisk 20.4 via TWRP ----> Boot loop.

Last time this happened I had a defective module, so I went in the terminal via TWRP and did a "touch disable" to create a "disable" file in every subfolders of /data/adb/modules, but it doesn't seem to help this time.

Flashing "Magisk-uninstaller-20200323.zip" recovered the phone, but of course Magisk won't work.

Canary and stable are the sames currently right (both 20.4)?

Any idea?
[Magisk] Lughnasadh:
You need to use Canary on Android 11. Stable and Canary are not the same versions. Install the Canary Manager, set channel to Canary and then install Magisk. If you need to use TWRP, boot it up but don't install it.
[Magisk] Dunge2:
Yeah I just realized the .zip you get from Canary Manager is not the same as the "beta" zip on the github page. So I did download the "Magisk-e66b0bf3(20425).zip" file and flashed it using TWP and still doesn't work. Instead of boot looping, it just goes straight to fastboot every time.

What do you mean by "If you need to use TWRP, boot it up but don't install it." ? Previously I always had to download the zip, boot TWRP and flash it to install Magisk. Via the manager I either have the choice to download the zip, or "Select and Patch a File" (whatever that is).
[Magisk] Alxoom33:
TWRP and Magisk are incompatible in A11. Only boot (fastboot boot TWRP.img), do not flash TWRP. Keep your stock recovery and you will be fine!
[Magisk] Lughnasadh:
With TWRP on Android 11 you can only boot it up with fastboot and then flash Magisk. If you use the installer to install TWRP and then flash Magisk you will end up in a bootloop or back to fastboot (can't remember which one).

"Select and Patch a File" is where you extract the stock boot image from the factory image, place in on your internal storage and then have Magisk patch that. After that you flash the patched image using fastboot. This is my preferred method. All the information can be found on the Magisk Github page.
[Magisk] DrunkUncas:
Installing without TWRP?

Just got my Pixel 4xl. Unlocked the bootloader, and installed Manager

Directions for installing are:

Open Magisk Manager, click "Advanced" >> "Recovery Mode"

Click the top "Install" button

But the Manager doesn't have an "advanced", "recovery mode", or "install" options. Just less useful stuff like download path, dark mode, etc under the hamburger and settings

What am I missing?
[Magisk] Lughnasadh:
The Recovery Mode option was removed for with devices ramdisk (includes Pixel 4 XL) because it's not needed.

Use the directions for Boot Image Patching and make sure you are using Canary Manager and to set the update channel to Canary first.

https://topjohnwu.github.io/Magisk/install.html
[Magisk] DrunkUncas:
But I don't have ANY install buttons. Boot img is in my download folder, but there's no way to patch it
[Magisk] Lughnasadh:
The install button is at the very top of the home page in the manager. Tap that and then choose boot image patching method. Then go to your boot image in your download folder and tap that and it will patch it. Then follow the rest of the directions for flashing it in fastboot.
[Magisk] DrunkUncas:
That's a negatory
[Magisk] Lughnasadh:
Are you connected to the internet?
[Magisk] DrunkUncas:
LOL. No.

Thanks for tolerating my stupidity. :o
[Magisk] eevanskiteboards:
question

hello. Maybe someone can solve my problem please. I just update to android 11 on my pixel 3A and successfully rooted it with magisk canary etc. i have root privileges thankfully but i am unable to download or install modules from the magisk app( dnscrypt, youtube vanced etc).

My attempt to fix the issue involved uninstalling the magisk canary manager app and install the latest non canary magisk manager app, but i am still unable to install the modules( the app lets me download and says it flashed but its not) weird. does anyone have any ideas or suggestions? thank you much
[Magisk] ipdev:
Normally that would be the case. ;)

I do not get a prompt asking to authorize the computer.

As I mentioned, this is an adb insecure device. (No adb key needed.)

First time I ran into this problem with MagiskHide testing on an insecure device.

Little time to test tonight.

It seems to be in early boot, before post-fs scripts are run.

If MagiskHide is disabled before the device is rebooted, using a service script to enable MagiskHide.

Insecure adb connection is authorized, SafetyNet passes and PlayStore stays certified.

Running a post-fs-data script to disable MagiskHide, disables MagiskHide like it should but, adb is still broken.

So MagiskHide needs to be disabled before reboot.

By manually copying my adb key to the device.

Normally this would be done when you agree to the authorize prompt on the device.

As expected adb is authorized when MagiskHide enabled before reboot.

This defeats the purpose of running insecure to be able grab logs when testing.

Cheers. :cowboy:
[Magisk] Didgeridoohan:
Without an install log it's hard to say anything for sure.
[Magisk] Didgeridoohan:
[MENTION=7280276]ipdev[/MENTION] What happens if you have MagiskHide enabled, adb unauthorized, and use resetprop to change some of the props that MagiskHide changes, back to the original values while booted or in late_start service? Debuggable, secure and type would be the usual suspects.
[Magisk] lividhen99:
Hmm... That's odd. You could try creating the module dir yourself. Unzip the module and copy the module.prop and system folders (just those will be good for most modules) to /data/adb/modules/(name of module). If you are able to write there with all the partition weirdenss that is now android.
[Magisk] eevanskiteboards:
I got everything to work by starting a fresh install of magisk canary etc. Thanks for your help everyone
[Magisk] joedp2:
I am currently rooted with Magisk on Android 10. I have been delaying updating to Android 11 on my Pixel 3a until I am sure that I can do it properly.

In the meantime, I installed Magisk canary and used it to create a patched boot image, so that I am ready to do the update.

My problem is that I don't see the su or hide options in canary that I see in the normal Magisk manager. If I can't hide the root, I won't be able to use a few apps that I need, so I don't want to update unless I can be sure that I will be able to do it.

Is the hide root feature absent from canary? Or is it reached some other way? Or is it somehow hidden? Is it related to the fact that I didn't uninstall the normal Magisk manager?
[Magisk] dcarvil:
Deleted - incorrect information
[Magisk] joedp2:
I must have missed that.

Thank you! Thank you! Thank you!

Good thing I didn't go through with the update.
[Magisk] Didgeridoohan:
As long as you patched the boot image from the A11 release you should be good. The issues people have been seeing has been from modules incompatible with A11 or having TWRP installed. TWRP can be booted on A11 and with Magisk, but it can't be installed (as of now).

Superuser, MagiskHide and other features like that are now reached through the little navigation bar at the bottom of the Manager. This is what it looks like with a working Magisk install (see attachment).
[Magisk] joedp2:
When I installed canary, those options were not active in the lower tool bar. Only the home and the log buttons were active.

And I did patch the A11 boot image. And I don't have TWRP installed.

---------- Post added at 03:07 PM ---------- Previous post was at 02:59 PM ----------

I just updated Magisk to canary using the custom update path. I thought I had done that earlier, but I guess I didn't. Now it is working the way it's supposed to.

---------- Post added at 03:35 PM ---------- Previous post was at 03:07 PM ----------

So I followed these instructions:

https://android.gadgethacks.com/how-to/root-android-11-using-magisk-foolproof-guide-0318066/

Now I am stuck on the white "G" loading screen.

---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------

Looks like I neglected to put the slot. I have tried both slots, and now I'm stuck in bootloader mode.

---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------

Looks like I neglected to put the slot. I have tried both slots, and now I'm stuck in bootloader mode.

---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------

Looks like I neglected to put the slot. I have tried both slots, and now I'm stuck in bootloader mode.

---------- Post added at 04:26 PM ---------- Previous post was at 03:55 PM ----------

Update:

It was a little nerve-wracking for a while. Eventually I was able to flash non-rooted A11 from https://flash.android.com/devices. Then I redid the image patching with Magisk and reflashed the patched image. Now everything is working well.
[Magisk] Fry-kun:
Interesting, just noticed that Play Store says my pixel 4xl is certified, and safety net passes.

I thought certification was happening in hardware now, without a possibility of bypass? Perhaps something was rolled back?

I'm on 10, btw
[Magisk] Lughnasadh:
Yeah, it happened to a lot of us about 2 weeks ago.

https://twitter.com/topjohnwu/status/1303845469798367233?s=20
[Magisk] Thorned_Rose:
I'm trying to download the latest version (zip via Magisk website) but the BytesTransfer file download is not working for me. Tried two different browsers, incognito mode... result is the same - clicking the button to download refreshes the page and no download starts.

EDIT: I was able to download via GitHub instead.
[Magisk] pndwal:
My comment

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

was based on reports users are getting different sized .img files patching same boot.img in Android 10 and Android 11 environments.

Please could you report if you A10 generated image has a different bit size compared to A11 generated one (for confirmation). I don't yet have Android 11. Thanks, PW.
[Magisk] Didgeridoohan:
Github

is

the Magisk website. Whatever other site you were visiting is not associated with Magisk and could possibly be scamming you.
[Magisk] Thorned_Rose:
Thanks! The site I tried with the dud link was magisk.me which was the first search result that comes up searching "magisk" with duckduckgo :/
[Magisk] Didgeridoohan:
There are plenty of shady websites and apps trying to profit from Magisk's popularity. And since we are talking about an open source root management system it is a very good idea to be careful with where you are downloading the installation files from... So far it seems like everyone's simply been trying to make a buck through advertising and similar, but anyone could upload malicious versions of Magisk and if you download and install that your device would be very much compromised.
[Magisk] vinayak.s19:
I am unable to install any magisk modules on android 11 via OOS 11. I patched my boot.img using the canary magisk manager.
[Magisk] teamgoogle:
Magisk not working on A11 pixel 4 boot image.

No matter what I do, it goes back to bootloader saying it has nothing to boot from. Have reflashed factory images, clean install, wiped all data etc etc etc, verified to work as soon as I flash stock boot image back.

GGWP
[Magisk] joedp2:
My patched file for A10 is 30,360 KB. The one for A11 is 32, 944 KB.

I just realized that's not what you were asking. I replaced the A11 patched image that I had generated in A10 with the one I generated in A11, so I don't know how big that file was. Sorry.
[Magisk] Yahoo1:
In A11 install Magisk Manager Canary, patch boot.img from stock android zip file, and then fastboot flash patched file. You can also use TWRP, but DO NOT install it, just boot it.
[Magisk] teamgoogle:
Confirm, canary not working p4. Tried latest canary, fully clean android, nothing installed, using patched boot image.

Loads google logo, then defaults to bootloader and fails to get out until i flash stock boot image.

Ive been at this for 2 days. I am pretty sure I know what I am doing (rooted n4,n5,n6,6p, p2xl and 3xl all working fine).

EDIT:

I DONT KNOW FFFING WHY

BUT after reinstalling magisk canary for the 3000000th time, and repatching the same exact boot image, for the 30000000000000th time. It decides to boot instead of go to boot loader.

THIS makes NO FING sense
[Magisk] pndwal:
Thanks!...

Just to be clear, the A10 one was the same original boot image? - extracted from A11 ROM, then patched in Canary Magisk but while still running A10? PW

Edit:

Just saw your additional info above... Oh well... Still guessing patching A11 images in A10 environment is messing things up for some... Seems to be what initially happened to you. PW
[Magisk] teamgoogle:
My patched a11 boot image was 33,120kb (so neither of the ones listed)
[Magisk] pndwal:
Quick check:

Are you doing patching from Android 11? Seems .img made in A10 or earlier environment is not working at least for some.

Also, as noted earlier, you need STOCK Recovery, not TWRP. (Boot TWRP only is ok. Don't flash.) PW

Edit:

Since everyone is adding edits, I'll follow suit... Seems congratulations are in order. Well done!

Pete: That don't make no sense!

Ulysses Everett McGill: Pete, It's a fool that looks for logic in the chambers of the human heart.

- Joel Coen, O Brother, Where Art Thou? PW
[Magisk] teamgoogle:
So my config was - updated from beta to stock 11 - then I unlocked boot loader, wiped, flashed factory image just in case. used boot image from said factory image (So I have not been on android 10 since beta1).

I patched in android 11 prior to doing all of the above. I also tried patching AFTER the wipe and reflash of factory images. I tried reinstalling magisk, and even rolling back to beta/regular version, no avail. Went back to canary, no luck.

This time however, I went ahead, uninstalled canary (for the millionth time) reinstalled AFTER a reboot (not immediately) then patched the boot image (same one that I have been using the whole time) and it came out larger. The first one was 33,120kb and the one that worked was 33,156kb. This is weird, before every single file came out at 33,120, but this last one, for some random reason, came out 33,156 and worked.

I have uploaded these files to my drive, feel free to take a look if you find anything. I labeled them working/not working. Again, I didn't do anything different each time. I would uninstall canary, reinstall, repatch, reflash, goes to boot loader. The one time I rebooted after installing canary THEN patched the bootimg, it worked.

https://drive.google.com/drive/folders/1W174Cl0uc5tuQL_v-LajozJQf8Gy12ht?usp=sharing
[Magisk] pndwal:
John Wu

1h

"Almost there. Magisk v21 incoming in a few days."

Great stuff! Many thanks John Wu. :good: PW

---------- Post added at 03:25 PM ---------- Previous post was at 03:12 PM ----------

Looking for logic...

Reboot may be the answer, but did you happen to update / load latest Canary Magisk Manager v300 for last (successful) attempt? This is probably the more likely reason it worked! (On MagiskSU 20426 now?)

Remember, it is Canary, and you're on the Bleeding Edge! Maybe not for long though - see above re imminent new Stable Magisk.

See below re. new Canary changes.

Thanks for reporting - may be useful for others. PW

---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------

New Canary:

Magisk (20426):

-Update SELinux rules to fix ADB root access on Android 8.x

Magisk Manager (300):

-Fix su request auto response

-Support theme switching pre Android 5.0

-Add settings for DoH (disabled by default unless device is set to China locale)

-More accurate device info detection

-Hide OTA option on Pixel devices as it results in bootloops

Thanks, n Go John!
[Magisk] teamgoogle:
Yep! I was on the latest one. I made sure this morning (8am) that I was and that is what got me all mad, because it was the latest version (I even made sure to download straight form github through the red canary tag). So once I dowloaded the APK, I never went to go download it again. I only double checked the version number, so yesterday, and today, I was using the same APK file the entire time (another wtf because If I redownloaded it then maybe that would be it, but alas, I did not, and simply continued reinstalling the same APK). So yeah, the only difference between the working time, and not working is that I 1) Installed apk 2) reboot 3)patch boot image instead of 1) install apk 2) patch boot image 3)try to flash it
[Magisk] pndwal:
So working Magisk was 20425? If so, guess it was the reboot then. PW
[Magisk] yaoruisheng:
Has this problem been solved?
[Magisk] zgfg:
Check the Change Logs, v17 was looooong ago.

Have you tried just on one of those phone, with Stable and Canary?

Which Android version, what exactly doesn't work, how you do it, logs
[Magisk] zgfg:
Xiaomi Mi 9T, MIUI 12/Android 10.

Updated (by patching and flashing boot img) to Canary 24946 and Manager 300, all ok:

- I left Manager 299 repackaged and didn't disable Play Protect before updating, no problem

- Manager shows now new info, Crypto: file

- Rebooting from Manager now boots to System, no more to Recovery/TWRP (it used to for my Xiaomi)

---

There is only one strange thing, it fails now CTS with Hardware attestation.

It passed for me just few days ago (also upon an abrupt change on the Google side), I didn't re-test before updating Magisk, but it's probably due to ever-changing Google side (hence I re-enabled fake ro.product.model to force Basic and SafetyNet is passing again)
[Magisk] MoL_82:
Same thing here. It passed the last couple of weeks, but it fails again.
[Magisk] Lughnasadh:
Apparently Google flipped their switch again. Lots of people all of a sudden failing this morning before updating Magisk.
[Magisk] chazall1:
+1 fail
[Magisk] abacate123:
Can someone explain to me that DoH option? I know what DNS-over-HTTPS means, I just didn't get this option there and there are no further explanation on what it does, I enabled it here and nothing changed, and my DNS stays the same.
[Magisk] ipdev:
I set adb to insecure before with the same results. (adb broken)

ro.adb.secure and ro.secure set to 0, ro.debuggable to 1

Little time to test last night.

I noticed MagiskHide did not change ro.adb.secure setting.

Set type and tags back to rom default values also.

ro.build.type userdebug, ro.build.tags test-keys

Same results, adb is still broken.

This device (rom) does not have ro.build.selinux set.

It has ro.boot.selinux permissive but, MagiskHide does not seem to change this value.

Quick test tonight.

Updated to Magisk 20426 and Manager 300, still the same results.

Still have some testing to do. I am guessing it is a device (rom) side issue.

Who would have thought I would be running Android 10 on a Nexus 10. ;)

It is also a device that needs MagiskHide toggled off-on after boot to pass SafetyNet.

Might be something to due with using an older kernel?

Kernel 3.4.67-followmsi-g5e791d1

When I have time, I will document it, grab logs and open a github issue.

Cheers. :cowboy:
[Magisk] hfam:
Hello all!

Pixel 2/A10/Magisk 20.0/no TWRP/no modules

(I passed on the P4a buy, gonna wait for a while longer and get a 5g model and milk my P2 for everything it's worth u til then ?)

Through all 8/9/and 10 updates, I have always used the following method:

Full factory image via adb (-w removed from flash-all to keep my data)

Patch boot.img taken from factory image using the currently installed version of Magisk via MM

Flash it into place using adb

...and all goes perfect, apps and data intact and rooted.

I've read back a ways in the thread and didn't see any confirmation posts that Pixel 2 A10 to A11 has been gtg. I read a post with a user on P2 with TWRP installed had probs, but no TWRP here.

It usually takes me a week or 2 to muster up the sack to do the major update and rooting, monthlies arent so stressful. Since I'm on Magisk 20.0 (I had no reason to update that to latest, it still works fine for me on P2) I guess I may need a newer version of Magisk for A11, but maybe not given I don't use modules? So;

- Is Magisk 20.4 ok, or do I need a canary release for A11?

- Will 20.0 still work? (I know.... but since I'm just using it for root and to hide a few apps, no modules, and it's currently installed it may still work in that capacity and I can update Magisk to 21 later if needed?)

- Can I still use the same full factory image update method (listed above) to update A10 to A11? (Maybe a successful P2 owner using the same method I use can weigh in as to how it went for them)

I know these Q's may seem rudimentary, but my phone is just perfect and these major updates are always a super stresser for me as I only have the single device. My plan is:

- do major update to A11 same method I've always used (listed above)

- Update Magisk (by setting selection back to "stable" version from my current "custom" which points to and keeps it at 20.0 version)

- Patch the boot.img taken from the same factory image package I will have just updated to A11 from

- push it into place using adb via the same means I always have using adb commands (again, no modules here)

You folks are my rock and a wealth of knowledge and experience on this, so as always I would appreciate any feedback as to if I'm fine, or need to take a different approach. (To keep it straightforward, let's not debate OTA, booting to TWRP via adb, etc. I just need to know if I'm ok using this method for the A11 update and Magisk still working, and if not and I *need* to go a different direction we can talk about those items.)

Thanks folks, and as always my sincere gratitude for any and all insights, input, comments and help. I ****** hate these major updates, I stress like mad. ?
[Magisk] Legendary Cryptid:
I have an issue with Earnin. The app keeps crashing. I've enabled Magisk hide and XPrivacyLua, but that has not helped. How can Magisk hide Earnin from detecting that my phone is rooted?
[Magisk] yaoruisheng:
ZTE BLADE A3

I have tried all versions above v16.7 ,

They still cause recovery-bootloop.

Just install magisk by twrp, no error report on it.

so only v16.7 can work correctly.

What's the difference between version 16.7 and version 17 that caused this problem？

https://archive.ztedevices.com/cn/support/detail?id=82F7D11446A84FC7AF2ED4D8FB9C4A4B
[Magisk] J.Michael:
I'm surprised it works at all. I thought I had seen a number of posts about people having problems that turned out to be the failure to remove the hidden version of Magisk Manager before installing a newer version of Magisk Manager.
[Magisk] Suavie103:
Thanks for this.. Worked as intended. Pixel 4 XL
[Magisk] GrandAdmiral:
Noob question that I can't seem to find in search, but may have missed....

I'm about to update the channel from normal Magisk 20.4 to Canary. Once done and Magisk is updated to Canary, do I need to re-patch the boot.img to functioned rooted or only worry about when i move from Android 10 to 11?