yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] mclarence:
For the hide magisk app greyed out issue, you will need to wait until the next official canary version is released. Simply using an apk from a recent commit will hide magisk with the current canary release which does not include the december update fixes.

Also I just realised that app-debug.apk should be used (instead of app-release) from the build artifacts as the debug apks are the canary versions whilst the release ones are the latest stable version. Though this shouldn't change anything at the moment and you should wait for the next canary release to hide the magisk manager app.
[Google Pixel 6 Pro] swieder711:
Can you attach the recommended APK to this thread? Thanks.
[Google Pixel 6 Pro] MArtyChubbs:
Done
[Google Pixel 6 Pro] Phascinate:
Anyone else unable to hide Magisk? It's grayed out for me.
[Google Pixel 6 Pro] pndwal:
Any of you guys try the (newest) test build from 'master' Magisk, or just LoveSy's build?:

https://github.com/topjohnwu/Magisk/actions/runs/1577670575 👀 PW
[Google Pixel 6 Pro] Prey521:
UPDATE - Nevermind, found the problem......it was the USB cable! SMH!

I'm getting the following error when trying to update to the December patch via Fastboot, any ideas?

I'm unlocked on Tmobile and tried both the 017 and 016 December updates with the same result, thank you.

Sending 'radio_a' (80212 KB) FAILED (Write to device failed in SendBuffer() (Too many links))

fastboot: error: Command failed

< waiting for any device >

Rebooting into bootloader FAILED (remote: 'failed to download image')

fastboot: error: Command failed

--------------------------------------------

Bootloader Version...: slider-1.0-7892371

Baseband Version.....: g5123b-92009-211008-B-7805583

Serial Number........: 19011FDEE000Q8

--------------------------------------------

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.000s]

Checking 'version-bootloader' OKAY [ 0.000s]

Checking 'version-baseband' FAILED

Device version-baseband is 'g5123b-92009-211008-B-7805583'.

Update requires 'g5123b-93368-211124-B-7943060'.

fastboot: error: requirements not met!

Press any key to exit...
[Google Pixel 6 Pro] MArtyChubbs:
November update had no issues?
[Google Pixel 6 Pro] Prey521:
I updated the OP, it was the USB cable.....all is well now LOL
[Google Pixel 6 Pro] Dave Lister:
There are multiple posts in this thread about that issue.
[Google Pixel 6 Pro] Phascinate:
I figured out how to fix it. First, if you're having issues with Zygist not turning on, go into Magisk settings and do a Direct Install. Reboot. Now, uninstall Magisk (the APK, not the entire framework) and install the latest Magisk Canary. Now you'll be able to hide the APK and everything works as it should (root and all). I'm even passing SafetyNet with the SafetyNet fix module now.
[Google Pixel 6 Pro] Lughnasadh:
You can also use John's debug test build that has the "Hide the magisk app" option working, as @pndwal has already pointed out.

Load fstab from system/etc · topjohnwu/Magisk@56eb1a1

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] V-Ripper:
Hi

I have the December update on it.

From November root to December no root.

I downloaded the image. patched with the new Magisk version, then Boot in Bootloader.

Here

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

reboot Bootloader

fastboot flash boot magisk.img

reboot

Bootloop after Google goes to G

where is the mistake???

Even without restarting, without flash vbmeta...

Written with google translator
[Google Pixel 6 Pro] RetroTech07:
I'm no expert here, but I see a couple of things.

The line where you flash vbmeta is written incorrectly. It should say:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Once you flash vbmeta, allow the system to boot into Android. Once that happens, reboot into bootloader, then apply the patched boot img.

fastboot flash boot magisk.img

I've done your way of trying to flash vbmeta without allowing the OS to load first, followed by patching the boot img only to end up in a boot loop. Allowing the system to boot into the OS first is critical. I could be wrong, and if I am, hopefully someone will correct me, but doing it the way I mentioned has resulted in no errors or boot loops.

Try flashing the stock boot img and see if you can load into the OS.
[Google Pixel 6 Pro] Nergal di Cuthah:
If you let it boot it will require a wipe and you will not have root as far as I've followed the rooting and the before you update threads.
[Google Pixel 6 Pro] ajsmsg78:
It's still there in my Magisk Manager. Try flashing the app-debug.apk version and see if you have it again.
[Google Pixel 6 Pro] RetroTech07:
I guess it depends on if you're coming from stock / non-root, never had a data wipe and if you've flashed vbmeta already? I'm not 100% sure, but I remember following other directions mentioning to flash vbmeta, allowing the OS to load then rebooting back to bootloader to finish the remaining steps.
[Google Pixel 6 Pro] zhuanyi:
I must be really stupid or crazy or both but for the life of me I can't get Magisk to work on Dec patch despite others reported success.

This is what I have done:

1. Start off with either original boot.img or magisk_patched.img (patched with 23015 Magisk). The APK file used later was downloaded every time I click on install.

2. Uninstall Magisk

3. adb reboot-bootloader

4. fastboot flash boot magisk_patched

5. fastboot reboot

6. install Magisk (23015) using direct APK file (Magisk-5d6d2417(23015).apk) downloaded, launched from the Files app.

In the end I see App is installed (5d6d2417(23015)) but Magisk installed is still N/A.

I used the Android Flash Tool with disable-verification and variety, using the "normal" version (i.e., not region-specific one). Previously on rooted November patch version.

What did I do wrong?

******************************************************************************************************

UPDATE: Using app-debug from the link above seems to work!

Load fstab from system/etc · topjohnwu/Magisk@ecea07b

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Download the zip under Artifact on that page and get app-debug.apk.

Then essentially repeat the above but with app-debug.apk

0. install app-debug.apk (if you previously have 23015 you can uninstall that first).

1. patch boot.img to get magisk_patched.img using app-debug.apk.

2. Uninstall Magisk

3. adb reboot-bootloader

4. fastboot flash boot magisk_patched (make sure it is the one that you modified using app-debug.apk)

5. fastboot reboot

6. install app-debug.apk

I managed to get my root back this way, although have to re-add all my credit cards in Google Pay since I have to wipe data for Google Pay to work again (anyway to avoid that?)

If you have done everything correctly for app version in Magisk Manager you should see Installed is 65e020f6 rather than 5d6d2417 (although both (23015)).
[Google Pixel 6 Pro] Homeboy76:
If your phone is a Pixel 6 this is the temporary solution to the Pixel 6 root problem. I think you have to join Github to download the fix.
[Google Pixel 6 Pro] wolfeyes30:
Not sure if it's a typo but you did include .IMG after fastboot flash boot magisk_patched?
[Google Pixel 6 Pro] zhuanyi:
Yap I did, sorry got lazy there to type the full file name :)
[Google Pixel 6 Pro] wolfeyes30:
Me bad. I just seen your update that you got it working now 👍👍
[Google Pixel 6 Pro] zhuanyi:
No worries at all...Just super happy it worked!!!
[Google Pixel 6 Pro] SailorOfTheMind:
thanks
[Google Pixel 6 Pro] MArtyChubbs:
I attached the magisk manager 65e020f6 (23015) to the OP.
[Google Pixel 6 Pro] Homeboy76:
Please accept my apology, I was not trying to hijack your thread. I do not have a Pixel 6 or Pixel 6 Pro yet. I did not know the magisk- app 65e020f6 (23015) beta was in the

65e020f646ee5b2e9803d11059d2a70c57107316.zip (26.7 MB) file because I didn't download it.

Nice thread! :)
[Google Pixel 6 Pro] Cares:
Hmm so I successfully rooted with this new Magisk but my option to "Hide the Magisk app" is blocked. I'm passing SafetyNet so I guess it's not a big deal.

I wonder what happened that we have to get on this temporary Magisk version and when will it be merged into the main version.
[Google Pixel 6 Pro] Nergal di Cuthah:
After rooting you can go back to regular canary magisk (uninstall debug apk install latest canary) if I've read correctly that'll fix the hide grey out (fixes definitely the saying app isn't installed bug)
[Google Pixel 6 Pro] V-Ripper:
Hi

I did the same thing, but unfortunately still bootloop.

It's not the classic boot loop, but a little later in my opinion.

Can it be that another module is loaded from the old Magisk or something.

phone always starts when the original boot.img is flashed.

it is always written in slot b.

is that correct?
[Google Pixel 6 Pro] V-Ripper:
sorry double post
[Google Pixel 6 Pro] foobar66:
https://twitter.com/i/web/status/1470993874923388933

versionCode='23016' versionName='92546e8a'
[Google Pixel 6 Pro] pa.pn2:
same Problem here.

Patched the Boot.img with latest Magisk23016), booted the patched kernel all fine, in magisk i choosed direct install, this was fine, phone rebootet succesfully.

In Magisk all Modules where deactivated, so i activated them and rebooted, bootloop again.

Had to boot up with stock image again.

Shall i flash the vbmeta with disabled flags again?

Any ideas?

Its also not the Classic Bootloop i guess, you see the Progress Bar and then it reboots

Or Shall i remove all modules and start from Scratch?
[Google Pixel 6 Pro] DanielF50:
Does no one read threads anymore?

As people have said multiple times on previous pages, reboot to safe mode (hold volume down @ "G" logo) then reboot.

Booting to safe mode will disable all your Magisk modules and your phone will boot on next reboot - you will then need to spend some time figuring out which module is causing the bootloop (turn one module on, reboot, turn another on, reboot etc until you get bootloop), then boot to safe mode again, reboot, uninstall or update the bad module & then reboot again (for example, Tulsadriver UI mods modules needs to be updated to December release otherwise you will get a bootloop).
[Google Pixel 6 Pro] pa.pn2:
I had no Problem with any Module on November build, no Tulsa Module installed

Maybe i should first delete all Modules as you said, ill give it a try
[Google Pixel 6 Pro] DanielF50:
And? I'm not trying to be rude, but if you can boot with all modules disabled, then it's quite obvious that one of your modules is causing the bootloop.

Some particular modules are device specific: they're built using November assests which are now incompatible with the December build - some modules will absolutely become obsolete after major (& minor) Android updates.

Just like you can't run a the Nov kernel the Dec build, some modules just do not work on the latest build, yet.
[Google Pixel 6 Pro] pa.pn2:
i dont feel offended at all, i just had the usual modules installed like busybox, adaway, substratum...

will try later
[Google Pixel 6 Pro] DanielF50:
Ah ok, I would still try enabling each seperately anyway - I think someone on a previous page said they had problems with substratum. Iirc, substratum changes system ui/overlay files so can ocassionally cause bootloops after a update 👍
[Google Pixel 6 Pro] kornball:
Anyone else having issues installing the new canary magisk manager? When I attempt to install, I get a popup that says "Magisk - Upgrade to full Magisk to finish the setup. Download and install?" I click OK, it tells me to relaunch, I relaunch, and it's the same message
[Google Pixel 6 Pro] roirraW "edor" ehT:
If I remember correctly, I had a similar problem if I had Magisk still "hidden" when I tried to update the app, so I unhide it, update the app, then update Magisk in the boot.img via direct install, then reboot, and re-hide Magisk.
[Google Pixel 6 Pro] somethingsomethingroot:
I think the last time I got in that loop, I declined the install from the prompt and did everything in the app like normal.
[Google Pixel 6 Pro] kornball:
Thanks! I do have the app hidden. Any idea how I unhide Magisk if I cannot get into the app? Is there an adb command or something? I have the manager renamed "Random-isk"
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't know particularly how to unhide without getting into the app, but the way around it should be to just uninstall the app, then reinstall (you could opt to just install the new version if you download it directly at that point). Of course, you'll have to re-do your deny lists and such.

See @pa.pn2 's two posts below. Better advice, but my above advice is always good for a very last-ditch effort.
[Google Pixel 6 Pro] pa.pn2:
pm unhide com.topjohnwu.magisk

in adb shell on pc with admin permissions, please try
[Google Pixel 6 Pro] pa.pn2:
hey, I can help you: command is from windows pc (power shell works awesomely): adb uninstall (& here you add the little code under the magisk app version on the start page of magisk) without ( ) ?!

magisk manager will successfully be uninstalled.

then, when the command succeeded simply reinstall magisk manager & everything's back again, magically!
[Google Pixel 6 Pro] NippleSauce:
Also, to keep things a bit more simple, he can just long press the app icon, select "App Info," and then press "Uninstall". Similarly, he can also just do the classic Android uninstall method by long pressing the Magisk icon (even if it was renamed) and then dragging it to the top-right corner of the screen where is says "Uninstall".

Now, I'm not saying that using adb is bad at all, but he can do the same thing without having to be near a computer and having access to a USB cable :).

Take care, good sir!

*Edit* - Furthermore, after this update everyone has to be aware of the fact that they *might* need to flash the patched magisk boot.img twice after the update. I manually update via CMD (using fastboot), however, after flashing the patched boot.img I still didn't have root until I went back into fastboot and flashed the patched boot.img a second time. Only then did I manage to have root access.
[Google Pixel 6 Pro] kornball:
I realize this is a very dumb question, but how do I ensure I have given admin privileges? I am getting an error in the command prompt saying 'pm' is not a recognized as and internal or external command. I know my phone is connected via adb since adb devices returns the device name
[Google Pixel 6 Pro] V0latyle:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, so make sure you back up your data and photos before you do this!

Q: "If verity/verification are disabled, do I need to enable them now?"

A: No. The only thing you have to do is update to Magisk 23016.

Q: "Will enabling verity/verification wipe my data?"

A: No.

Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.
[Google Pixel 6 Pro] hugehead83:
I'm running through this now--just installed latest Canary Magisk build.

So, for my flash-all.bat update command, I can remove --disable-verity --disable-verification ?
[Google Pixel 6 Pro] V0latyle:
Should be able to.

That being said, this isn't confirmed so make sure you back up your data in case you have to go back to the old method and wipe.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you already disabled them before, you have to keep disabling them otherwise you'd have to completely wipe your device. Each time you go from disabled to enabled, or enabled to disabled, you have to perform a factory reset.
[Google Pixel 6 Pro] NippleSauce:
Hey there. Read my posts above yours as you presumably don't need to use adb for this.
[Google Pixel 6 Pro] rester555:
That's excellent news

EDIT: After reading all the replies to this, I am going to wait to do this if you have to do a full factory wipe for removal of command line for verity and verification...
[Google Pixel 6 Pro] kornball:
Thank you! So I should just be able to uninstall the repackaged "hidden" Magisk manager app and install the new canary build of it? This won't create some redundant instance of Magisk on my phone?
[Google Pixel 6 Pro] NippleSauce:
I'm just gonna add the few extra bits of text whenever I update just to be safe. It only takes around ten additional seconds if you always include the "--disable-verity --disable-verification" part.
[Google Pixel 6 Pro] V0latyle:
Not entirely true...

You should be able to go from disabled to enabled without a wipe.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oh! I was under the impression that you had to wipe going either direction. Thanks!

Still not taking any chances here, yet. :D
[Google Pixel 6 Pro] NippleSauce:
It shouldn't, as that is what I did and it worked without issue. But I think you can also probably just open Magisk and search for an update within the app. If it asks you to install the update, just agree and push it though. That reinstallation will also disable the hidden package setting.

There are lots of different methods for removing and reinstalling Magisk that are easier and quicker than always using CMD on your PC =)
[Google Pixel 6 Pro] V0latyle:
For sure.

Hopefully this is the fix we need, and we'll never have to worry about wiping data again.
[Google Pixel 6 Pro] swieder711:
To update from Canary 23015 to Canary 23016, do we uninstall the Magisk app and the install the new app-debug.apk?

Is there a way to update from within the Magisk app by using a Customer update channel?
[Google Pixel 6 Pro] V0latyle:
Yes. If you have the app hidden, and attempt to separately install the new APK, you'll have a double instance.

Update from within the app if possible.

I don't have Magisk hidden or renamed so in my case I could just install the new APK as an update.
[Google Pixel 6 Pro] kornball:
That's what's difficult - currently, I cannot get in to Magisk no matter what I do. I continually get that pop-up about installing Magisk, and when I do so, it loops and asks me to install again.
[Google Pixel 6 Pro] kornball:
That was my concern. Since I cannot get into Magisk manager, I don't really know what to do now.

I keep getting this message loop, even if I tell it to install...
[Google Pixel 6 Pro] V0latyle:
Do you have root? If so, perform Complete Uninstall from within the app; reboot, remove Magisk, then reinstall 23016, repatch the boot image and try again.

If this doesn't work, I don't know of any way to recover root without wiping /data. There's a known issue where the signatures between the manager and the boot patch can get confused, and there's no way to clean it up without a data wipe.
[Google Pixel 6 Pro] kornball:
I do have root, but I cannot get into Magisk manager. If I click on the repackaged "hidden" app, I get that pop-up telling me to install Magisk. If I click OK and then relaunch the app, I get the same pop-up
[Google Pixel 6 Pro] V0latyle:
Hmm.

Uninstall the app, then install the 23016 canary and see if it works.
[Google Pixel 6 Pro] kornball:
Thank you! The first time I did that, it did not work. I tried again, and it looks like everything is okay? I will try to patch the Dec boot.img and try to update a little later. I really appreciate your guidance!
[Google Pixel 6 Pro] swieder711:
Can you post the URL for the Custom channel so that I can update from Canary 015 to 016 from within the Magisk app?

Thank you!
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://github.com/topjohnwu/Magisk#downloads

Click the "Magisk [Canary]" (third one from the left). If you're updating from within the app, you can do so from the main screen, however. 23016 was published to Canary, so you don't need the custom channel right now.
[Google Pixel 6 Pro] hugehead83:
Update edit for resolution: I was using an incredibly old version of fastboot and adb binaries from the old "minimal ADB & Fastboot" version I was using. I updated those from the developer platform tools site and my update worked.

I may have borked my Pixel 6.

flash-all.bat failed on the system image. If I was supposed to remove latest Magisk Canary build after patching the new boot.img but before flashing, that's where I goofed.

I cannot get into Safe Mode. I've held the volume down button for 2 minutes at the boot animation, but it never leaves the G screen. I have to hold the power button for 30 seconds to reboot, then I can hold volume down to get to recovery.

Is this recoverable without a wipe? Is there a "Safe Mode" from fastboot/recovery that I'm unaware of?
[Google Pixel 6 Pro] V0latyle:
Just switch the update channel to Canary.

But, I'll humor you:

https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Removing Magisk is not necessary before an update.

I'm not sure how to fix this other than using the Android Flash Tool to force flash all partitions, which will require a data wipe.
[Google Pixel 6 Pro] kornball:
After installing the new canary magisk manager build and uninstalling the "hidden" magisk manager app, I am getting the attached pop-up when I enter the Magisk app. It says "Requires Additional Setup. Your device needs additional setup for Magisk to work properly. Do you want to proceed and reboot?"

So far, I have hit 'cancel.' I have patched the December boot.img using the canary build and will attempt to update later today. I think it should be okay to continue hitting 'cancel' until then. I appear to still have root access, pass safetynet with USNF 2.2, and my denylist is in tact. Anyone think I need to proceed and reboot prior to updating via fastboot and patched boot.img?
[Google Pixel 6 Pro] rester555:
So how does one get into recovery with holding buttons now with the P6 and P6P?

EDIT: Nevermind, it hasn't changed...
[Google Pixel 6 Pro] hugehead83:
Just updated my previous post!

My issue was my incredibly ancient ADB/fastboot binaries on my computer. Updating those fixed my flashing issue.

Thanks for your help everywhere here.
[Google Pixel 6 Pro] roirraW "edor" ehT:
When you hid Magisk, what did you call it? Find it by that name in your apps list and uninstall it. Then manually install the 23016 Magisk Canary, and if you still need to (redo) - patch the December boot.img and flash that.

Personally, I rename it "Mag Settings isk", so it's easier not to confuse for other Settings apps.
[Google Pixel 6 Pro] hugehead83:
Holding volume down at power-up got me to the recovery menu.
[Google Pixel 6 Pro] rester555:
So has anyone successfully tried flashing the new magisk 23016 boot image over their current root without disabling the verity and verification to see if it doesn't corrupt system?
[Google Pixel 6 Pro] V0latyle:
Yes

He had an issue with the debug Magisk, couldn't install or run the new Canary. Reflashed vbmeta without disabling verity/verification, then reflashed the patched boot image.

Disabling verity/verification doesn't corrupt /system; the issue is with user data encryption in /data. Restoring verity/verification to default should have no impact as long as you patch using 23016.
[Google Pixel 6 Pro] kornball:
I renamed mine "Random-isk." I uninstalled it before installing the new canary build. I have patched the December boot.img, and the patched file has 23016 in its file name. I think I'm good to flash *fingers crossed*
[Google Pixel 6 Pro] rester555:
Thanks for pointing to the other thread... so for someone that is wants to update to 23016, what are the process steps @pa.pn2 took? Is it flash the magisk patched then vbmeta or vice versa?

EDIT: Disregard, I can't read... sorry
[Google Pixel 6 Pro] V0latyle:
Just to make it clear:

If you're already on Magisk Canary, simply update Magisk from within the app. Ensure your update channel is set to Canary.

Alternatively, download the new Canary release and install it; it will update your configuration.

If you're on the debug version, uninstall the app, then install Canary 23016.

In both cases, make sure you update your boot patch using Direct Install after updating Magisk.