How To Guide [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More

[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?

 

[noobie2022]

Overwrite it with a different image, like the unpatched boot image

What build are you on and what version of Magisk are you using?

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

 

[V0latyle]

@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?

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.

 

[noobie2022]

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...

Editing...

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"?

 

[V0latyle]

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"?

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

 

[Homeboy76]

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?

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.

 

[noobie2022]

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.

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.

 

[noobie2022]

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.

Yes, the guide in post #454.

I shall try this.

 

[noobie2022]

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.

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]

 

[Homeboy76]

Yes, the guide in post #454.

I shall try this.

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.

 

[noobie2022]

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.

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?

 

[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!

 

[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.

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.

 

[noobie2022]

Thanks for the help @V0latyle @Homeboy76 @Lughnasadh

 

[noobie2022]

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!

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):

 

[V0latyle]

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?

Only with some custom kernels. The need to do this was fixed with Magisk v24

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!

Check your Play Certification in the Play Store app

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.

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?

Thanks for the help @V0latyle @Homeboy76 @Lughnasadh

Glad you got it working

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):

SafetyNet is irrelevant so don't try to fix it. Focus on Play Integrity.

 

[Homeboy76]

...I already provided this information in the OP. SafetyNet is irrelevant so don't try to fix it. Focus on Play Integrity.

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

 

[V0latyle]

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

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

 

[TheNDFT1of6]

app

Check your Play Certification in the Play Store app

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!

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.

 

[V0latyle]

Thanks for pointing that out!
Here is what my Google Play Store shows:

View attachment 5786911

How would I go about rectified this?
Thank you much in advance!

Here's your answer (mostly)

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

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.