yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
Great, thanks for reporting.

This suggests that somewhere along the lines, you did something differently.

You should check the PixelFlasher logs, it shows you everything it did,

see if you can spot a step where you did it differently.
[Google Pixel 6] Homeboy76:
This thread does have a link to PixelFlasher for XDA members that are uncomfortable with manually flashing the factory image.

Brief Comments/Discussions/Questions about the PixelFlasher will are ok.

Long Comments/Discussions/Questions about the PixelFlasher that border on

Hijacking the thread

are

NOT

ok.

These long Comments/Discussions/Questions about the PixelFlasher must/should be posted on the PixelFlasher thread for the developer @badabing2003, or other knowledgeable experts @V0latyle to Comment on/Discuss/Answer Questions.
[Google Pixel 6] V0latyle:
Me? An expert? Hardly! Lol

Since @takeshishen had asked for help here, I didn't want to divert his questions to another thread, especially not mine, because I didn't want to give the impression that I'm trying to promote myself
[Google Pixel 6] Homeboy76:
I understand you not wanting to divert @takeshishen to your thread. However, the questions were about the PixelFlasher tool and should have been diverted to that thread.
[Google Pixel 6] badabing2003:
To be clear,

I agree 100% , I didn't want to hijack the thread, hence I did one suggestion to try with PF to eliminate potential user error, for that I provided my response in PF thread.

All other back and forth posts here evolved around the manual steps @takeshishen had taken or should take to troubleshoot the error, nothing was PF related.
[Google Pixel 6] takeshishen:
Sorry, I don't understand the rules of this forum. I don't want to offend it. My question also involves ADB, SDK and Magisk Where should I classify my problems and other people's help? The author mentioned PixelFlasher in the tutorial. Can't I use this software in this topic? I just have confused questions.ADB, SDK, MAGISK, file path, and the cable for brushing. Do they need to be classified one by one?
[Google Pixel 6] Homeboy76:
Not mad at ya! :ROFLMAO:

I too have suggested PixelFlasher, that is why there is a link to it on my thread. :cool:

Your comment on this thread have been helpful.
[Google Pixel 6] Homeboy76:
No, you should not classify your problems. Yes, you can use Pixel flasher. Brief questions about ADB, SDK, MAGISK and file path are welcome. Long discussions about them are NOT welcome and should be posted on their respective threads or Google searched.

I don't know what

cable for brushing

is. o_O
[Google Pixel 6] takeshishen:
I'm glad to have solved the problem here and met so many enthusiastic people. This is enough. Have a nice day for all of you. I don't want to continue this topic. Thanks for all your replies!
[Google Pixel 6] tom1807:
A perfect example for Google translation doesn't know it either. Chinese / Japanese words are translated to "brushing" instead of "flashing"

And now in other news....

Cheers

Tom
[Google Pixel 6] 20GT:
hello i apoligise if im out of line but will the the latest Magisk Manager root a pixel 6
[Google Pixel 6] 20GT:
thanks, thanks you so much, two more questions - so just (me) buy one from ebay, get the APK on it and away i go?

is there a better phone that Magisk Manager will easily root? if this needs to be discussed somewhere else I understand
[Google Pixel 6] Homeboy76:
New

The

Developer Preview QRP2 Beta

Factory/OTA image links are in the

OP, Part I, NEW

.
[Google Pixel 6] Lughnasadh:
PSA: Seems at the moment people aren't able to root this beta on Pixel 6s.
[Google Pixel 6] Lughnasadh:
Apparently patching the Pixel 7 boot image and flashing it on the Pixel 6 will work for getting root as a temporary workaround.

Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk

After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...

github.com
[Google Pixel 6] noobie2022:
Hi there, I'm going to do my 1st ever Magisk rooting of Pixel 6a that carries Android 13. Updated non-rooted from Android 12 some time back.

Does this slot A slot B flashing apply to me?

Additionally, these guides do not mention slots A or B.

Here's how you can unlock the bootloader and root the Google Pixel 6a with Magisk

Looking to root your brand new Google Pixel 6a? Here's how to unlock the bootloader and root the latest mid-ranger Pixel smartphone!

www.xda-developers.com

https://www.getdroidtips.com/root-pixel-android-13-magisk/
[Google Pixel 6] Homeboy76:
Yes. because the Google Pixel 6a have two slots:

Active and Inactive or A and B slots.
[Google Pixel 6] noobie2022:
Thanks. I see.

Does that mean these guides have missing crucial steps?

Here's how you can unlock the bootloader and root the Google Pixel 6a with Magisk

Looking to root your brand new Google Pixel 6a? Here's how to unlock the bootloader and root the latest mid-ranger Pixel smartphone!

www.xda-developers.com

https://www.getdroidtips.com/root-pixel-android-13-magisk/

-----

In other words, they're missing these steps from

https://developers.google.com/android/images/

"To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:

Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image."
[Google Pixel 6] noobie2022:
@Homeboy76

Would it be safer to "install into inactive slot B" housing Android 12 before even installing into active slot A?
[Google Pixel 6] Homeboy76:
Option 2., is the quickest and easiest way to flash the bootloader to the inactive slot.
[Google Pixel 6] Homeboy76:
If you have android 13 installed to your phone, and it is booting to Android 13. Do not flash Android 12 to any slot.

You can check which slot is the active/boot slot by booting the bootloader: Power off the phone => press and hold the power and volume down buttons until you see start. Your active slot is the boot slot.
[Google Pixel 6] noobie2022:
Thanks @Homeboy76!

Using Magisk,

Is this "direct install" == flash the bootloader to the active slot?

Is "install to inactive slot (after OTA)" == flash the bootloader to the inactive slot?

My boot slot is B with Android 13. I wonder what's the Android version in the inactive slot A?

Can I avoid the below if I'm using Magisk? I presume there's more than 1 way to do option 2: using magisk on the phone OR using CMD on PC.

fastboot --slot=other​

flash bootloader bootloader_filename.imgfastboot​

set_active afastboot reboot bootloaderfastboot​

set_active bfastboot reboot bootloaderfastboot​

reboot​
[Google Pixel 6] Lughnasadh:
Magisk has nothing to do with flashing the bootloader. Magisk deals with the boot image. They are 2 different things. If you are trying to flash the A13 bootloader to your inactive slot (to make sure you have the A13 bootloader on both slots), just do as as @Homeboy76 alluded to:

fastboot flash bootloader --slot=other <bootloader image>

Since you have A13 on slot b, use that same bootloader image when flashing.
[Google Pixel 6] Homeboy76:
Are you rooted and trying to update Magisk?

why do I ask?

The latest version of Magisk Beta/Stable is 25-2

The latest version of Magisk Canary is 25205.

Yes, the inactive slot is A.
[Google Pixel 6] noobie2022:
@Lughnasadh thanks for enlightening!

I found out that I have the same bootloader version, i.e. Android 13 bluejay-1.2-9152140, on both slots A and B.

Do I still need to flash the same bootloader image on both slots A and B?
[Google Pixel 6] noobie2022:
@Homeboy76

Nope, I'm not yet rooted. I've only got to the 'bootloader unlocked' step.

I don't dare to proceed further until I figure out the need for 'flash image in both slots'.

I think I have latest Magisk version installed on my Pixel yesterday:

Magisk-v25.2.zip – Stable
[Google Pixel 6] Homeboy76:
@noobie2022

No.

I think you can proceed:

https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-6a/
[Google Pixel 6] noobie2022:
Thanks! @Homeboy76 @Lughnasadh

Is there a link where I can verify if bluejay-1.2-9152140 is truly Android 13?

I made the assumption because my bootloader version has a larger number than @mbk17 's.
[Google Pixel 6] Homeboy76:
What is the build #?
[Google Pixel 6] noobie2022:
The build is TP1A.220905.004.A2.
[Google Pixel 6] Homeboy76:
That is the September image.

13.0.0 (TP1A.220905.004.A2, Sep 2022)

Just install the December factory image: Factory Images for Nexus and Pixel Devices

"bluejay" for Pixel 6a

13.0.0 (TQ1A.221205.011, Dec 2022)
[Google Pixel 6] noobie2022:
I have done this below, but all I see is the Google logo on phone screen. Did something go wrong?

fastboot flash boot magisk_patched.img​

fastboot reboot​

Guide: https://www.xda-developers.com/how-...magisk-google-pixel-6a/#flashpatchedbootimage

Can I reverse the process?

How do I 'unflash' an image?
[Google Pixel 6] noobie2022:
[Removed]
[Google Pixel 6] noobie2022:
@Homeboy76 @Lughnasadh @V0latyle

According to https://www.getdroidtips.com/root-pixel-android-13-magisk/

They recommend fastboot boot magisk_patched.img instead of FLASH. Which one should I follow?
[Google Pixel 6] noobie2022:
I'm on Magisk v25.2 and build TP1A.220905.004.A2.

Do I do this? >>> "fastboot flash boot boot.img"

Or do I do this? >>> ""fastboot boot boot.img"

@V0latyle
[Google Pixel 6] V0latyle:
One live boots the image, the other flashes it.

fastboot boot <image> tells bootloader to immediately boot the image specified without flashing it to the partition. This is called a "live boot" because the image is being loaded directly into memory, instead of being installed on the device.

fastboot flash boot <image> tells the bootloader to flash the specified image to the boot partition.

As has been explained before, it's important to understand the context here.

fastboot is telling the command line to use the fastboot program to talk to your bootloader.

The next item is the command you're sending to the bootloader - boot to tell it to "boot" the image you specify, flash to flash a partition. There's other commands but that's another discussion.

Lastly is the file you're telling the bootloader to do something with, as well as any arguments that may be necessary.

It can be confusing because fastboot boot and fastboot flash boot look similar, but you have to understand what is going on.

If you want to test an image, or use it to boot the device (with the express understanding that it is NOT being written to the partition) you live boot it. We can do this with Magisk patched boot images to see if they boot; since that's what is running in system RAM, the Magisk app can use that image for root access, including patching the image already in the /boot partition.

Otherwise, you can flash the image, but understand that flashing an image to a partition overwrites everything that was in that partition. This is why users of TWRP cannot flash the TWRP.img to /boot, because it overwrites ramdisk and the system kernel, so now you only have TWRP in boot, meaning the device will only boot TWRP and is unable to load system. So, instead, you'd live boot the TWRP image, use it to flash whatever modifications you might want, then use the TWRP menus to reboot the device.
[Google Pixel 6] noobie2022:
Should I try to "fastboot boot" the image instead? Since "fastboot flash boot" does not work for me?

To overwrite my patched image with boot image, should I type "fastboot flash boot boot.img" or "fastboot boot boot.img"?
[Google Pixel 6] V0latyle:
You responded too soon. Go back and read my post. I had to switch from my phone to my laptop and didn't want to lose what I was typing
[Google Pixel 6] Homeboy76:
Yes, you are boot looping.

boot the bootloader then type:

fastboot flash boot --slot all boot.img

You are reading to many guides.

Use the guide in post #454 to root your Pixel 6a or use this guide.

If you use this guide you must use the Pixel 6a bluejay factory image.
[Google Pixel 6] noobie2022:
Thanks for expounding @V0latyle really appreciate this

A bit deep for me but I try my best to understand...

I surmise that fastboot boot <patched image> is what I should have done instead.

Now that I have erroneously done fastboot flash boot <patched image> based on the XDA guide, I can only continue to fastboot flash boot <boot image>. This will be the 'reset' I presume?

And then try to fastboot boot <patched image> and direct install via Magisk.
[Google Pixel 6] noobie2022:
Yes, the guide in post #454.

I shall try this.
[Google Pixel 6] noobie2022:
Done. Do I need to "fastboot reboot" after this step?

Sending 'boot_a' (65536 KB) OKAY [ 1.544s]
Writing 'boot_a' OKAY [ 0.151s]
Sending 'boot_b' (65536 KB) OKAY [ 1.544s]
Writing 'boot_b' OKAY [ 0.148s]
[Google Pixel 6] Homeboy76:
I wasn't asking you where you got the information from, I was asking you to make a choice which guide you want to use. Once you make that choice stick with that guide.
[Google Pixel 6] noobie2022:
Yep, that was what I followed.

I also read that verity + verification should be disabled on Google Pixel 6A before rooting or installing Magisk.

But this step isn't present in the guide I followed. Is this disabling step absolutely necessary?
[Google Pixel 6] TheNDFT1of6:
Hi, I followed the instructions and successfully rooted my new Pixel 6 (Android 13). However, after rooted, a Game App (that I must have) disappeared from Google Play Store. I found that the reason/error message was "This App is not compatible with your device". Before rooted my Pixel 6, I was able to install it from G. Play Store and played it normally. The unlock bootloader process wiped out all the installed Apps/data and I had to start all over again and ran into this issue.

Any thought/pointer/recommendation on how to solve this?

Thanks in advance!
[Google Pixel 6] noobie2022:
I tried multiple attempts to fastboot flash boot the boot.img but I keep getting the unresponsive Google logo.

In one attempt, I disconnected the type-c cable from my phone. Voila, the phone could finally boot instead of getting stuck at the logo.

Then I repeated the whole Rooting process each time disconnecting the cable whenever the phone needed to reboot.

I believe my device is now systemlessly rooted with Magisk.
[Google Pixel 6] noobie2022:
Thanks for the help @V0latyle @Homeboy76 @Lughnasadh
[Google Pixel 6] noobie2022:
I came across something online that might help you if you don't want the game app/Play Store to know that you have rooted your device (assuming this is the cause):
[Google Pixel 6] V0latyle:
Only with some custom kernels. The need to do this was fixed with Magisk v24

Check your Play Certification in the Play Store app

Either your cable is bad or something else is wrong. Is this a USB-A to C cable? You aren't using Minimal ADB are you?

Glad you got it working

SafetyNet is irrelevant so don't try to fix it. Focus on Play Integrity.
[Google Pixel 6] Homeboy76:
What OP? :)

I posted SafetyNet information in this OP: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...

, 5. Root/Reroot with Magisk and Pass SafetyNet.,

, •

Pass Safety Net with SafetyNet Fix
[Google Pixel 6] V0latyle:
Whoops. I didn't notice this wasn't my thread. Sorry about that.

But, it is important to note that SafetyNet is no longer relevant and was replaced by Play Integrity, with a full turndown scheduled for June '24. Most apps have already migrated to Play Integrity. The fixes for SafetyNet don't work on Play Integrity, and since the two work somewhat differently, it's possible to get a SafetyNet PASS but fail Play Integrity

More information here
[Google Pixel 6] TheNDFT1of6:
Thanks for pointing that out!

Here is what my Google Play Store shows:

How would I go about rectified this?

Thank you much in advance!
[Google Pixel 6] V0latyle:
Here's your answer (mostly)

To check your attestation status, use Play Integrity Checker on the Play Store. If you pass both BASIC and DEVICE integrity, try clearing data for Play Store.
[Google Pixel 6] TheNDFT1of6:
Thank you!

Followed Munchy's vid instructions: tweaked few Magisk's Zygisk options, then patched safetynet_fix, cleared Google Play Services & Play Store's data. That solved the problem and worked beautifully now.

Thanks for your pointer and Munchy's video. Much respect & appreciated!
[Google Pixel 6] 20GT:
Ok I've finally got my pixel 6 and got the Magisk app on it. Lughnasadh what do i hit to one touch root it? or did i missunderstand your answer. please help.. i'm a complete noob.

you are welcome to message me so its not messing up this thread
[Google Pixel 6] Lughnasadh:
You have to patch and flash the patched boot Image. Follow the directions on how to root in the OP.
[Google Pixel 6] 20GT:
Thanks for the reply. I totaly misunderstood your "yes" answer because i asked the wrong question. I mistaked Magisk with Magisk Manager. it one click rooted my stylo plus.

I'm screwed, doesnt anything do a "one click" anymore?

edit; nevermind found https://oneclickroot.com/
[Google Pixel 6] gazdajezda:
First, do you unlock your P6's bootloader already? If yes try Pixelflasher. But anyway, in your place I would read first.
[Google Pixel 6] 20GT:
It came unlocked. i understand what you are saying, but there a difference between reading and having the confidence to do it, plus knowing what not to do if it goes wrong. I promise this is not an ad but im leaving it to someones thats an expert at it.
[Google Pixel 6] Lughnasadh:
Um, I don't know what that is but you should really follow the instructions in the OP to root and not use some 3rd party one click root thingamajig.
[Google Pixel 6] 20GT:
Forget about the one click app, that apperently was when i used kingroot a long long time ago. it just happens that that link coincidentally has the words "one click" in it, they are 2 seperate things.

I remember now that 5 years ago, I used them to root my Stylo plus. Its just been so long ago that I forgot. They put and used the magisk app on my phone back then, that is why I thought I auto rooted my phone with it, which it doesnt do. They did all the stuff the OP is talking about.

I'm glad that they are still up and running and have no problem paying their fee to have them connect to my PC and root my new phone.
[Google Pixel 6] ne0ns4l4m4nder:
Hey guys, wondering is the P6 December build boot.img still corrupt. Or can I flash and patch normal?
[Google Pixel 6] badabing2003:
I think you're referring to the beta, not the standard December release.

It's not corrupt, just that Magisk patch does not work, you can use boot image from pixel 7
[Google Pixel 6] Poomsmart:
After the bootloader is unlocked with stock ROM google pixel 6 android 13. I can't install Netflix and can't use prime video app from the play store. Is there any way to bypass the bootloader unlocked detection?
[Google Pixel 6] badabing2003:
Install SafetyNet Fix module and clear data as instructed in any one of these great guides here and here
[Google Pixel 6] devilsshadow:
hey folks, trying to figure out why my November security patch is no longer available. I had the update notification nagging me for a while but I ignored it. Went to check for updates today and I no longer see the update. Any clues as to why this is happening? I'm rooted and bootloader unlocked and the "update failed" notification would pop up whenever I'd put my phone to charge (this is normal). But not that's gone too.
[Google Pixel 6] Homeboy76:
Canary Update

Magisk (831a398b) (25206)
[Google Pixel 6] Homeboy76:
Update SafetyNet Net Fix Mod

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517/

Displax's SafetyNet Fix Mod: v2.3.1-MOD_2.1

• Update module.prop
[Google Pixel 6] Homeboy76:
Update SafetyNet Fix

kdrag0n SafetyNet Fix V2.4.0

This version only supports Zygisk (Magisk 24 and newer).
[Google Pixel 6] krs360:
Anyone know if the boot image is fixed on the new beta? Or do we still need to use the image from the Pixel 7.

I'm on holiday with no laptop, and don't want to update it it's going to go wrong.
[Google Pixel 6] badabing2003:
It looks like it is not.

Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk

After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...

github.com
[Google Pixel 6] arsradu:
I'm not sure what's happening with the latest Android 13 Beta on the Pixel 6, but your comment to patch and flash the Pixel 7 boot image did the trick for me. I thought I was missing something. But nope, looks like the problem was somewhere else entirely.

Many thanks! :)
[Google Pixel 6] lzazyj:
huzzah!
[Google Pixel 6] luisgerardo01:
Hi, all

I bought a refurbished Google Pixel and imported to my (unsupported) country. While it arrived, I was searching for important info and found that I needed to root the device to make use of the VoLTE/VoWifi feature 😣, nothing that really mattered to me anyway as I've been rooting devices most of the time I've been using an Android phone.

I gathered the required info and even downloaded the latest device specific factory images. My only question here is: do I need to first allow the phone to do the first-time boot and wizard and even OTA update to the latest and then root or may I boot directly the device in fastboot, flash-all (script) the latest factory image and then flash the patched boot, all at once, before the first boot?

It's just to avoid downloading and erasing and then flashing everything again. BTW, I wouldn't be rooting the phone if I wouldn't need this phone feature. Also I usually root phones I want or need but after some weeks of use, so that's why I raised this short and maybe stupid doubt above.

Regards,
[Google Pixel 6] badabing2003:
Just go ahead and flash all, no need to waste time.
[Google Pixel 6] bdr127:
I have a Pixel 6 that I rooted and update using this great guide. (Thank you!) The phone uses Google Fi for service. I need to do the February 2023 update, and there are two -- a normal one and one for T-Mobile and T-Mobile MVNOs. Google Fi uses T-Mobile, Sprint, US Cellular, and Three (UK) networks, so I'm thinking maybe I should download the update for T-Mobile MVNOs, but I'm not sure since Google Fi uses multiple cell networks.... Anyone know for sure which update I should download?
[Google Pixel 6] tiiiit74:
Hi everyone, I'm on vacation, I don't have a computer and I have a problem with Safety Net. I can no longer pay in NFC on my Pixel 6 Root when it worked a few days ago in SafetyNet-fix 2.4.0. I haven't done anything in the meantime... Tried 2.3.1 mod, doesn't work either. Can you tell me if I can unroot from Magisk without going through a computer? Thank you very much, it's urgent. See you soon I hope.
[Google Pixel 6] Nightf0x_007:
Try updating to safetynet fix v2.4.0 mod 1.1 by displax
[Google Pixel 6] tiiiit74:
Can you give me the link please? I don't have a lot of network and I struggle. Thank you so much.

Édit : found ! Merci 😅
[Google Pixel 6] badabing2003:
If that does not work, see this
[Google Pixel 6] Lughnasadh:
As for the unrooting portion of this question, you can unroot by uninstalling Magisk via the Magisk app.
[Google Pixel 6] tiiiit74:
THANKS. I don't know if this can solve my problem with payments, I saw in the SafetyNet-fix thread that a lot of people seem concerned.
[Google Pixel 6] Homeboy76:
SDK Platform-tools r. 33.0.3

https://xdaforums.com/t/pixelflashe...g-managing-pixel-phones.4415453/post-88141667
[Google Pixel 6] Homeboy76:
Update Magisk Canary

app-release_e5641d5b-25208.apk

Notes:

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

Will not hide Magisk

Magisk Canary 25206

app-release_831a398b-25206.apk