yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release_2717feac-25209.apk

Notes:

Tap 3 dots (...) across from 10.x MB, Tap Download
[Google Pixel 6] Homeboy76:
Magisk Canary

app-release_2717feac-25209.apk

Note: Not fixed!

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

https://xdaforums.com/t/pixelflasher-for-google-pixel-7-pro-support-thread.4505287/post-88240637
[Google Pixel 6] defrag44:
FYI - You do not need to root to enable VoLTE/VoWIFI, check this thread for simple solution

Enable VoLTE/VoWiFi in unsupported countries without root (requires Shizuku)

Hi all, Bellow you can find some info on how to attempt to enable VoLTE in unsupported countries (tested in Romania, Digi carrier) using Shizuku and Pixel IMS app for it. This assumes that you have ADB and drivers properly setup beforehand. 1...

xdaforums.com
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release_981ccabb-25210.apk

Notes:

Tap 3 dots (...) across from 10.x MB, Tap Download
[Google Pixel 6] Homeboy76:
Not another broken Magisk Canary release

Magisk Canary - app-release_981ccabb-25210.apk

breaks

all modules

:

25210 breaks module loading · Issue #6688 · topjohnwu/Magisk

Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...

github.com
[Google Pixel 6] Homeboy76:
Magisk Canary Fixed

Magisk Canary - app-release_981ccabb-25210.apk

https://github.com/topjohnwu/Magisk/issues/6688

https://github.com/topjohnwu/Magisk/pull/6690
[Google Pixel 6] vlucchetti:
Nope, not fixed
[Google Pixel 6] Homeboy76:
I know the Adaway module is not working.

You may have to wait for Magisk Canary 25211
[Google Pixel 6] deusfaux:
what would cause my Device Certification status in Play Store to not even show up?

I tried the airplane mode safetynet fix steps and no difference. also failing CTS profile in YASNAC

I just rolled back from .210 canary to 209, and on Feb Android and Play System updates. kdragon safetyne fix 2.4 module still installed from previously

edit: changed to displax's safetynet fix and got YASNAC passed, but still zero device certification status showing in play store and apps like Netflix not showing up

edit 2: after repeating the steps enough times it's showing as device certified in play store. still no Netflix app, but I think I'm remembering something about how it does a further check than safetynet and I have to manually update the .apk? gonna go research that one...

edit 3: weird. after some time passing, Netflix starting showing in Play Store search, with update button that would fail 'device not compatible' and THEN eventually showed up in installed apps with pending updates, and update worked. bizarre. but seems I'm all settled then

edit 4: homeboy could you put a note in the OP about how to check Play Integrity - assuming that's what I was still failing until I wasn't
[Google Pixel 6] Homeboy76:
SDK Platform-tools Update

SDK Platform-tools r34.0.0 and r34.0.1 are not working.

Use SDK Platform-tools r33.0.3.
[Google Pixel 6] Homeboy76:
Magisk Canary

These versions of Magisk Canary are all broken: 25207, 25208, 25209, and 25210.

The last working Magisk Canary 25206 - app-release.apk can be downloaded here.
[Google Pixel 6] Homeboy76:
SDK Platform-tools

SDK Platform-tools r34.0.1 has been released.

There is a link in the OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~, 2. Prerequisites, • A Computer with the latest SDK...
[Google Pixel 6] Homeboy76:
SDK Platform-tools Update

SDK Platform-tools r34.0.0 and r34.0.1 are not working.

Use SDK Platform-tools r33.0.3: https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4388733/post-88261749
[Google Pixel 6] Murmel2k:
Just wondering: Is taking the OTA now possible without corrupt boot partition warnings?
[Google Pixel 6] badabing2003:
Looks like Pixel 6 and Pixel 6 Plus March updates are missing, all the other devices already got their updates.

I'd be curious to know why.
[Google Pixel 6] Lughnasadh:
https://xdaforums.com/t/pixelflashe...ng-pixel-phones.4415453/page-36#post-88281673
[Google Pixel 6] vlucchetti:
From another thread : It seems like they are having some issues again, as a Google Support person has told on the chat that the March 2023 update for the Pixel 6 series devices will come on the 20th of March 2023. This from the Kirisakura-Kernel for the Pixel 6/Pro posting.
[Google Pixel 6] Homeboy76:
Google Pixel 6 series updates are up.
[Google Pixel 6] vlucchetti:
So no root with 25210, or jyst the issues already known with it?
[Google Pixel 6] Homeboy76:
Issues already known with it.
[Google Pixel 6] deusfaux:
March updates on factory images site.

what's the WINDTRE/CANADA version ...?
[Google Pixel 6] Homeboy76:
Carriers: WINDTRE - Italy, CANADA - Canada

Click

Which one do I use?

Link in OP
[Google Pixel 6] deusfaux:
They didn't seem to detail at the update changelog the difference so it begs the questions:

1. If I (in Canada) waited for the OTA system update - which would it choose for me?

2. What exactly is a fork like this doing? What if I spend my time on Canadian and American networks?

3. What happens next month if there is a single global update? Does that mean the Canada specific changes in the March version got folded into the April update?
[Google Pixel 6] Homeboy76:
"They didn't seem to detail at the update changelog the difference so it begs the questions:"

Google wrote the

update changelog

.

Google Pixel Phone Help - Help Center
[Google Pixel 6] MatMew:
Maybe I'm getting old, but the instructions in the first post in this thread are super confusing for me. So so so many options. I've accidentally touched "Upgrade to Android 13" in my notification bar and am now on 008.E1 and root has dropped off (no surprise there). In searching for a way to regain root by patching and flashing, even using PixelFlasher, I'm really scared to try anything in this guide in case I've missed a pre-requisite.
[Google Pixel 6] Homeboy76:
It is ok to be apprehensive about trying something new: ...In searching for a way to regain root by patching and flashing even using PixelFlasher...

My suggestions to you is, start by reading the OP (Original Post): ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 5. Root/Reroot with Magisk and Pass SafetyNet.

If you have questions about the Root/Reroot instructions, ask them I or other members of XDA will answer them.

If you have questions about the Pixel Flasher app ask them here. @badabing2003 or other members of XDA will answer them.
[Google Pixel 6] badabing2003:
Agreed, If any part is confusing to anyone, the best way to approach it is ask precise questions regarding the command / part that is causing the confusion, and that helps in identifying areas that could confuse people which could be improved.

Saying the whole thing is confusing, is a dis-service to the guide author, if following a guide is complex, imagine writing it.

You can't imagine all the permutations and different steps people take to arrive to a particular state, anticipating all those and writing a guide that easily provides the details and yet keeps it a simple is a nightmare task.

Kudos to all guide authors who manage to maintain these wonderful guides.
[Google Pixel 6] darkerm:
I just got a new pixel 6. It's a Verizon verison. So can I unlock bootloader? If not can I root with locked bootloader and by pass safety net?
[Google Pixel 6] Homeboy76:
No.

No, you cannot root and pass Safety net with a locked bootloader.
[Google Pixel 6] darkerm:
will it be possible in future?
[Google Pixel 6] Homeboy76:
¯\_(ツ)_/¯

You can wait and see if Verizon will allow their phones to have an unlockable bootloader in the future.
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release_69529ac5-25211.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.9 MB, Tap Download

...[General] Bump minimum supported Android version to Android 6.0

Google Android 14 Codename is

'Android U' or 'Upside Down Cake'

...[MagiskPolicy] Update rules to support Android U...

...This fixes boot image patching issues on Android U preview...
[Google Pixel 6] Homeboy76:
:oops: Not

another broken

Magisk Canary

Notes:

Magisk Canary 25207, 25208, 25209 (some devices), 25210 and 25211 are broken.

Magisk 25211: Some, are reporting

Systemless host

is still not working in this thread:

Magisk General Support / Discussion - starting at Post #55137

Use Magisk Canary 25206

Tap

the 3 dot menu across from 5b2934603f

Tap

Go to file

Tap

app-release.apk

Tap

the 3 dot menu across from 10.9 MB

Tap

Download

<<Edit>> Fix for Module loading, System less Host is still broken.

Waiting for Magisk 26001.
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release_e2545e57-26001.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB, Tap Download

Magisk Beta Update

Magisk-v26.0.apk
[Google Pixel 6] darkerm:
whats the difference between Canary vs Beta? whats is the current stable version?
[Google Pixel 6] Homeboy76:
The Beta version is more stable than than the Canary version which is the testing version for Magisk. The Stable version is 25.2.

If you are look for it a technical description of the differences between the three Magisks Beta, Canary , and Stable visit this thread and search each version.
[Google Pixel 6] darkerm:
I have Stable version Installed with latest A13 build. Should I install Beta or stay with stable?
[Google Pixel 6] darkerm:
is there any custom Recovery like TWRP for Android 13?
[Google Pixel 6] Homeboy76:
AFAIK there isn't any Custom Recovery like TWRP for Android 13.
[Google Pixel 6] darkerm:
is there any way to take Full backup before flashing a new ROM and restore it If something went wrong?
[Google Pixel 6] Homeboy76:
If it ain't broke don't fix it.

However, if you decide you want the latest and greatest Magisk.

Open Magisk Stable 25.2 Manager app

Tap the Setting Icon

Tap Channel

Set it to Beta or Canary

Wait for update notification

When update notification arrives :)

Tap Update ==> Direct Install
[Google Pixel 6] Homeboy76:
I'm assuming you are referring to updating your Google Pixel 6 Factory firmware, when you wrote "flashing a new ROM". If the answer is yes, try this: Back up or restore data on your Pixel phone
[Google Pixel 6] darkerm:
I want full backup. everything just like how TWRP make your whole system backup.
[Google Pixel 6] Homeboy76:
AFAIK, there is no way to do a full image backup like TWRP.
[Google Pixel 6] r00tcracker:
Does this work correctly?? Or still broken like all the previous ones.

I'm still rocking 25206 here...
[Google Pixel 6] vlucchetti:
I'm on 26001 Canary, no issues.
[Google Pixel 6] Homeboy76:
Magisk Beta Update

Magisk-v26.1.apk

Magisk Canary Update

app-release_d0c93842-26101.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB, Tap Download

Magisk Stable Update

Magisk-v26.1.apk
[Google Pixel 6] Marcop880:
Buongiorno ragazzi premetto che ho sempre utilizzato le guide su xda per sbloccare boot, eseguire root e flashare rom e mi sono sempre trovato bene. Da pochi giorni sono possessore di un Google Pixel 6 liscio. Dopo i vari Xiaomi moddati, questo Google mi sta facendo impazzire. Vorrei gentilmente capire se con android 13 installato posso sbloccare il boot ed eseguire il root....vorrei un modulo magisk per Google foto e usufruire dello spazio illimitato pre pixel 6....penso conoscete tutti la storia ahimè..... un'ultima cosa, come mai nella prima pagina non riesco a cliccare sui link ?? È stato bloccato il thread ? Grazie a tutti e buona domenica.

Mod translation: Hello guys I start by saying that I have always used the guides on xda to unlock boot, run root and flash roms and I have always found it good. I have been the owner of a smooth Google Pixel 6 for a few days. After the various Xiaomi modded, this Google is driving me crazy. I would like to kindly understand if with android 13 installed I can unlock the boot and run the root .... I would like a magisk module for Google photos and take advantage of the unlimited space pre pixel 6 .... I think you all know the story alas ..... one last thing, why on the first page I can't click on the links?? Has the thread been locked? Thank you all and happy Sunday.
[Google Pixel 6] Homeboy76:
Please use English

Yes you can unlock the bootloader on your Google Pixel 6 phone on Android 13 (OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 1. Unlock Bootloader/Return Phone to Stock/Lock Bootloader, • Unlock Bootloader). After, you unlock the bootloader and set up your phone. Read the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Manually Install/Update Factory Image keep data or wipe data before proceeding to root your phone.

If you are referring to the links in the OP (post#1), I just checked them and they are working. No, the thread has not been locked.
[Google Pixel 6] Marcop880:
Homeboy76 hai perfettamente ragione,errore mio che vedevo il thread sul pixel che inibisce la funzione dei collegamenti.....non so il perchè. Ho visto da PC e tutto ok. Ho alcune domande....nella parte 2 istruzioni, dopo il passaggio numero 1 posso passare al numero 5 ? O serve necessariamente seguire anche i passaggi 2-3-4 ? Perchè non li ho capiti sinceramente. Io ho attualmente installato la rom android 13 stock nessuna beta. Grazie mille

Mod translation: Homeboy76 you are absolutely right, my mistake that I saw the thread on the pixel that inhibits the function of links..... I don't know why. I saw from PC and everything ok. I have some questions....in the part 2 instructions, after step number 1 can I go to number 5 ? Or is it necessary to follow steps 2-3-4 as well? Because I didn't understand them honestly. I have currently installed the stock android 13 rom no beta. A thousand thanks
[Google Pixel 6] Homeboy76:
@Marcop880

Please use English
[Google Pixel 6] Rogia89:
Homeboy76 you are absolutely right, my mistake that I saw the thread on the pixel that inhibits the function of links..... I don't know why. I saw from PC and everything ok. I have some questions....in the part 2 instructions, after step number 1 can I go to number 5 ? Or is it necessary to follow steps 2-3-4 as well? Because I didn't understand them honestly. I have currently installed the stock android 13 rom no beta. A thousand thanks
[Google Pixel 6] Rogia89:
So guys I'm trying to unlock the bootloader but I already see something wrong in the commands .... I have the drivers installed, the related platform tool r33 and obviously I activate the unlock flag eom and debug on the pixel. what do you think it could be?
[Google Pixel 6] Homeboy76:
@Rogia89,

Try ./fastboot devices

Why?

When you open a Windows PowerShell the fastboot commands must be proceeded with a ./
[Google Pixel 6] Homeboy76:
Did you read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2.?

Yes, after 1 you can go to 5.

~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~

(The Instructions listed below are not

steps

, they are

individual sets

of instructions.)
[Google Pixel 6] badabing2003:
You probably have older fastboot in your path environment.

Type fastboot --version

Assuming that the current directory has the correct fastboot, this is correct, you just missed the dot in front of the slash to indicate the current directory, without it, fastboot should exist at the root of the filesystem.

./fastboot --version
[Google Pixel 6] Homeboy76:
He has r.33.0.3. You are right the . was missing. It was a casualty of a cut and paste operation. :)
[Google Pixel 6] badabing2003:
Yes but he probably also has an older version in the path which got picked up because the current directory one was not explicitly referenced.

One should remove all of versions of at least remove them from the path environment otherwise during the execution of flash_all they could be picked up and cause issues.

I personally do it differently, I keep one for version (right now 33.0.3) in the path , example c:\android\platform_tools

I don't unpack anything in there other than the best platform tools.

From that point on wherever I issue adb / fastboot command, they always pick that version.

Unpacking of the firmware can be done anywhere without needing to coexist with platform tools.

Just my preference.
[Google Pixel 6] Homeboy76:
@Rogia89,

Did you run the ./fastboot --version?

What version was it?
[Google Pixel 6] Marcop880:
Homeboy76 I think I have a problem with Windows because my old Xiaomi doesn't even recognize me anymore 😔 tomorrow I'll reinstall Windows and reset the pixel and let you know as soon as possible. Thank you all really.
[Google Pixel 6] Homeboy76:
You're right he might have an older version of fastboot.

I agree "One should remove all of versions of at least remove them from the path environment"

You're right he might have an older version of fastboot.

I agree "One should remove all of versions of at least remove them from the path environment"
[Google Pixel 6] Homeboy76:
Ok.

Run this command when you get it working to check for duplicate fastboot.exe files:

./fastboot --version

Are you using Windows 10 or 11?
[Google Pixel 6] Marcop880:
I reinstalled Windows 11 and tomorrow I will install the adb and fastboot files and the pixel USB drivers .... I'll update you 👍🏻
[Google Pixel 6] LineArc:
My IMEI is showing 0000, need help. The recent update ruined it. I have my phone's box with me. Anyway to bring my IMEI back.
[Google Pixel 6] Marcop880:
Good evening guys, so after resetting both win 11 and my pixel I managed to unlock the bootloader with the boot commands. Now what steps should I take to install magisk ? I go straight to step 7 satlting all the others?? Thanks a lot to everyone.
[Google Pixel 6] Homeboy76:
Go straight to OP, Part II Instructions, 5. Root/Reroot with Magisk and Pass SafetyNet,

• Patching the boot.img - to root/reroot.
[Google Pixel 6] jakey1995abc:
Just rooted my Pixel 6 again after the latest OTA update removed root. Is it safe or necessary for me to do "Install to inactive slot (after OTA)" in Magisk, to prevent the same thing happening with the next OTA update?
[Google Pixel 6] badabing2003:
yes
[Google Pixel 6] Lughnasadh:
People flashing kernels builds over another kernel build without going back to the stock images (e.g. boot image, dtbo image, vendor_boot image, vendor_dlkm image) is definitely one of the problems that does mess people up, unless the kernel developer has said it's ok to flash their kernel over another.

Dirty flashing a factory image (with the -w removed), however, shouldn't be a problem as that method replaces everything with stock, including the kernel (just preserves you data). I've done this almost every month for years with no problems, including on the Pixel 6 Pro with a custom kernel installed. It seems that for whatever reason, however, some people have ran into the corrupt message while doing this, especially on the December build.

Also, some people get a corrupt message but everything still works, and some people can't even boot their phone after getting it.
[Google Pixel 6] Homeboy76:
Update

Magisk Canary 23018
[Google Pixel 6] phoenixpb:
Is it not safer to uninstall magisk, reboot the device, do a normal update on the air and install magisk again ?

i never had problems with this method.
[Google Pixel 6] Homeboy76:
Update

Magisk Canary 23019
[Google Pixel 6] Lughnasadh:
Stable Magisk apparently imminent...

Magisk Changelog

The Magic Mask for Android

topjohnwu.github.io
[Google Pixel 6] bobbarker2:
No I am not. Every time I reboot I get a message in red stating "your device is corrupt" along with some other text and must press the power button to continue. Then I get the typical "bootloader unlocked" warning which displays for a few seconds, then the phone boots. As I've said previously I'm on the latest Magisk Canary, rooted, safetynet passing.
[Google Pixel 6] bobbarker2:
I did not try a dirty flash. Flash-all of January without data wipe, flash Magisk patched boot img, attempted to flash custom kernel made device soft-brick.

Any custom kernel I've tried hasn't worked or forced me to do a factory reset. Tried flashing with EXKM and FKKM.. no difference.
[Google Pixel 6] Lughnasadh:
I'm curious. Did you disable vbmeta verity and verification at anytime in the past and do you currently have it disabled? Because that screen you are encountering is an indication of a dm verity corruption.

Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up.

But what I'm wondering is how you got that message to begin with and if it's related to disabling vbmeta verity and verification in the past, or currently.
[Google Pixel 6] bobbarker2:
Actually now that you mention it, someone said they had the same problem I was having at the time and they recommended I try --disable-verity --disable-verification arguments in the flash-all.bat, even though it shouldn't be needed. I've done so many flashes on this device trying to fix something, I can't even remember what it was I was trying to fix by doing that.

Currently verity isn't disabled in the slot that boots to January/rooted. So I think you're right, the only solution is a factory reset to erase the /data partition. I'll try it when I have the time/feel like rebuilding my phone.

I miss Titanium Backup, I wish it was maintained. Swift Backup works pretty well but Titanium was better.
[Google Pixel 6] Lughnasadh:
Yeah, disabling verity & verification by itself shouldn't cause the problem, but I'm wondering if when going back to having verity and verification enabled while doing a dirty flash (removing the -w from the flash-all.bat file) may have caused it. Not really sure, just trying to fit some pieces together.
[Google Pixel 6] vandyman:
Your systemUI is corrupt somehow from flashing. This can happen with simple mistake as flashing a December kernel on top of the January factory image.

The only way to fix this is to a factory reset or

Install the January full factory image with a complete wipe. Use the flash-all command in adb. This will wipe the system data as well, that is where your problem is. If you do not wipe data, it will keep your storage data and system data settings. You need to get rid of your system data.....
[Google Pixel 6] Nimueh:
Erm ... while TiBu might not be maintained it still works. But try Migrate instead, I've been using it across 3 devices (incl. this Pixel) and it works great :)
[Google Pixel 6] mixtapes08:
magisk 24 just got release. Is it the same as the canary version?
[Google Pixel 6] t-ryder:
For those of you who - like me - always prefer flashing their rooted Pixel 6 by using the factory images, you can try my wrapped 0riole_Flasher script. Made this for fun and because it's convenient.

0riole_Flasher
[Google Pixel 6] Homeboy76:
UPDATES!

Magisk 24.0 Beta App

Magisk Canary 24001
[Google Pixel 6] Lughnasadh:
Pretty much the same as Canary 23019 except for some translation updates, typo fixes and updated guides. Canary 24001 has a couple extra commits, but nothing of significance. The new release is a Beta release by the way. If everything goes well, he'll release it to stable in a few days.
[Google Pixel 6] Lughnasadh:
I think 24.0 is actually the Beta App. If everything goes well, he'll release it to Stable, according to John on Twitter.

https://twitter.com/i/web/status/1486284286927859712
[Google Pixel 6] gazdajezda:
Hmm, so SQ1D.220105.007 is still not recommended to be flashed without -w (wipe) in flash-all script? Eh, until i find a way how to quickly and without much effort return all settings / apps to the fresh system i will stay on november (SD1A.210817.037) update. I not have time to play with it after flash. But also I need root, since I use rsync on my phone to backup images, swift backups and rest to my home server. Tricky Google, tricky...