Magisk has come a long way. I remember back in the CyanogenMod days where there was the built in su manager , or SuperSU
good ol days
How To Guide May 2022 firmware is out - Unlocking the Pixel 6 Pro bootloader & central repository of relevant links
- Thread starter roirraW "edor" ehT
- Start date
Magisk has come a long way. I remember back in the CyanogenMod days where there was the built in su manager , or SuperSU
good ol days
Magisk Canary 23018 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.
Unhide the Magisk app before updating.
Unhide the Magisk app before updating.
New magisk update
Last edited:
Do you usually re-patch the boot.img with the newest Magisk before upgrading Magisk itself? I know I don't but I wonder if I should. Although, I guess "direct install" in Magisk does that?
Last edited:
My steps for updating are:
- Unhide Magisk.
- Update from within the app.
- Then yes, I use Direct Install.
- Reboot and re-hide the app.
Modified the OP to indicate the official repair site is still being reported as not having been updated for the P6/P, and also to give a link to the official boot to safe mode instructions. Most other sites including major carriers only tell how to boot from safe mode from a working Android UI using the power menu - which is of no help for a boot-looping device.
I just used safe mode for the first time that I remember to solve a Magisk Module problem of mine - but I might've done so on my Pixel 1 before and it's just been too long ago. It's definitely the first time I did so on the P6P.
Please, anyone, let us know somewhere when/if the repair site has been updated for use with the P6P if you notice it first.
I just used safe mode for the first time that I remember to solve a Magisk Module problem of mine - but I might've done so on my Pixel 1 before and it's just been too long ago. It's definitely the first time I did so on the P6P.
Please, anyone, let us know somewhere when/if the repair site has been updated for use with the P6P if you notice it first.
Well, here's some good news... 
9to5google.com
February's Pixel 6 update should be available on the same day as other Google phones
Following schedule departures, the Pixel 6's OTA schedule is set to return to normal with the February security patch next month...
So uh quick question...
I have a Google-unlocked P6 Pro. Not tied to any carrier, I bought it purely unlocked from Google.
If I pop in a Verizon SIM will it disable OEM unlocking?
I have a Google-unlocked P6 Pro. Not tied to any carrier, I bought it purely unlocked from Google.
If I pop in a Verizon SIM will it disable OEM unlocking?
In short no it won't. I use a unlocked bootloader p6p on a Verizon sim no problem
Magisk Canary 23019 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.
Unhide the Magisk app before updating.
My steps for updating are:
This is sorta a manual updating procedure to promote the Canary release to an imaginary release channel between Canary and Beta. LOL!
Unhide the Magisk app before updating.
My steps for updating are:
- Unhide Magisk. Edit: I've heard it reported that this wasn't necessary for them. It's possible it was only a problem on Canary 23015, or it was fixed on one of the later Canarys (Canaries?). I still intend on doing it this way, though - it really doesn't hurt me.
- Update from within the app.
- Then yes, I use Direct Install.
- Reboot and re-hide the app.
This is sorta a manual updating procedure to promote the Canary release to an imaginary release channel between Canary and Beta. LOL!
Last edited:
What @Nergal di Cuthah said.
No. Personally, I would always unlock the bootloader first thing before I got through the process very far, though, since unlocking the bootloader factory resets the phone.
To note, i did root before i inserted the sim, so that might be a factor idk
It really shouldn't, I believe you were 110% correct in your post.
If it did gray out the OEM unlocking while using the factory unlocked Pixel 6 Pro and having a Verizon SIM in, I would consider it a very rare fluke that's probably easily rectified, or even self-rectified in a short time, but I've never heard of this happening. I am old, though, so every new thing I learn, something old has to fall out to make room.
You are probably right. The unlocked devices I’ve used all were under a different server (Google’s own server I believe) for firmware updates + OEM unlocking so I doubt a Verizon SIM would change that.
I haven’t had a Pixel since the Pixel 2 so I was getting extra clarification that everything was the same.
No problem, i came from a 2xl that was still on Android 8 because i was afraid of losing root and not having a software based helper (can't remember the name of it). So i came to p6p with worries over root
I'm under the impression that all updates still come from Google directly even on a Verizon variant - it's the IMEI of the device which changes the behavior, how soon you get the update, et cetera, according to the carrier's wishes, but I don't think changes where the update comes from.
That does make sense.
It can honestly get confusing. Especially since direct from Verizon variants AND Verizon variants you set up from Google themselves are permanently bootloader locked. It makes you think anything that touches Verizon can get fused shut, lol.
I had to do extra due diligence to make sure I got the right variant. This year it seems pretty easy to get the wrong one and from what I read it appears a lot of people have
Magisk Beta (non-Canary) v24 is out at Magisk Downloads on GitHub, or at the Releases page there, or direct download link https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk.
Unhide the Magisk app before updating.
My steps for updating are:
Unhide the Magisk app before updating.
My steps for updating are:
- Unhide Magisk. Edit: I've heard it reported that this wasn't necessary for them. It's possible it was only a problem on Canary 23015, or it was fixed on one of the later Releases. I still intend on doing it this way, though - it really doesn't hurt me.
- Update from within the app.
- Then yes, I use Direct Install.
- Reboot and re-hide the app.
Magisk v24.0 Release Info
topjohnwu released this 2 hours ago
· 3 commits to master since this release
v24.0
b34c477
It has been a while since the last public release, long time no see! A personal update for those unaware: I am now working at Google on the Android Platform Security team. Without further ado, let's jump right into it!
MagiskHide Removal
I have lost interest in fighting this battle for quite a while; plus, the existing MagiskHide implementation is flawed in so many ways. Decoupling Magisk from root hiding is, in my opinion, beneficial to the community. Ever since my announcement on Twitter months ago, highly effective "root hiding" modules (much MUCH better than MagiskHide) has been flourishing, which again shows that people are way more capable than I am on this subject. So why not give those determined their time to shine, and let me focus on improving Magisk instead of drowning in the everlasting cat-and-mouse game.
Sunsetting Magisk-Modules-Repo
Due to lack of time and maintenance, the centralized Magisk-Modules-Repo was frozen, and the functionality to download modules from the repo is removed in v24.0. As a supplement, module developers can now specify an updateJson URL in their modules. The Magisk app will use that to check, download, and install module updates.
Introducing Zygisk
Zygisk is Magisk in Zygote, the next big thing for Magisk! When this feature is enabled, a part of Magisk will run in the Zygote daemon process, allowing module developers to run code directly in every Android apps' processes. If you've heard of Riru, then Zygisk is inspired by that project and is functionally similar, though the implementation is quite different internally. I cannot wait to see what module developers can achieve using Zygisk!
Documentation
For developers, details about updateJson and building Zygisk modules can all be found in the updated documentation.
Magisk Changelog
Last edited:
This is interesting. I'm not on Magisk v24 Beta yet. Does anyone else have any observations about this?
I don't have a custom kernal, but with 240001 (canary 24) my fingerprint is read on AOD
Top Liked Posts
-
There are no posts matching your filters.
-
4NOTE! I had the wrong firmware pasted in my previous post (for the 5A instead of 6 Pro). Corrected now.
Edit: I would expect someone to hopefully have noticed if they used the link in what I pasted since the filename would start with barbet instead of raven but still sorry about that. Mea culpa!4May’s Pixel 6 and 6 Pro update primarily improves haptic feedback
Like last month, the May security update is rolling out for the Pixel 6 series on the same day as all other supported Google devices.
Compared to previous months, there are just three fixes. Exclusive to the Pixel 6 is haptic feedback “improvements” after complaints that emerged with Android 12L. Some found that vibrations were reduced so much that they missed calls, notifications, and other alerts, while tweaking settings did nothing to increase intensity. We noted at the time:
Sensors
- Improvements for haptic feedback under certain conditions and use cases *[2].
Display / Graphics
- Fix for issue occasionally causing display to wake without user interaction *[1].
- Fix for issue causing launcher crash after restarting device in certain conditions *[1].
The Pixel 6 series and older phones are on the same Android 12.1 build for this May update: SP2A.220505.002. -
53May firmware is out Pixel 6 Pro Factory Images.
Here there be dragons.
I am not responsible for anything at all. 
Likewise, when wanting to root you have to disable verity and verification, after which you'll need to wipe the phone, so best just to go ahead and disable these immediately after unlocking the bootloader. See the section below "A list of the other important guides".
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
Rooting-related
No longer applies -Things that make rooting more complicated on Android 12
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
Custom kernels for stock ROM(s)
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader)
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
1515The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.13Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.
Canary 23014
EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4
11SDK Platform Tools have been updated to v32.0.0 (January 2022). Update now before you forget and flashing the February update on the 7th gives you hassles.
Direct download for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
New posts
-
Moved my zoom slider, can't move it back - help!
- Latest: PaddyODawes
-
-
