How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet

[iwearthebelt]

So I can tell you that you don't need to do a factory reset in order to get root back. I've made a few errors myself as of lately including forgetting to unhide magisk. Can't remember specifically what I did but I did lose root and used Pixel Flasher to dirty flash the latest factory image over the current slot I was using and it worked flawlessly. It went right back to where I was prior to losing root, even kept all my modules enabled and my settings intact. So just patch the bootloader, flash the latest image (or whatever one you were using) and you should be good to go.

 

[snovvman]

So I can tell you that you don't need to do a factory reset in order to get root back. I've made a few errors myself as of lately including forgetting to unhide magisk. Can't remember specifically what I did but I did lose root and used Pixel Flasher to dirty flash the latest factory image over the current slot I was using and it worked flawlessly. It went right back to where I was prior to losing root, even kept all my modules enabled and my settings intact. So just patch the bootloader, flash the latest image (or whatever one you were using) and you should be good to go.

Thanks. I've tried everything, using Platform Tools 33.0.3:

Flashing patched boot using Magisk 25205 and 25206
Dirty flashed image and flashed patch boot
Fastboot boot <patched boot>

Nothing is working. When I boot with the patched boot, Direct Patch is not an option.

Any other ideas?

By the way, is the disable verity thing still a requirement? Previously, unless that was done before first boot after flashing and flashing patched boot, root is lost and factory reset is required.

 

[Nergal di Cuthah]

By the way, is the disable verity thing still a requirement? Previously, unless that was done before first boot after flashing and flashing patched boot, root is lost and factory reset is required.

That hasn't been needed since before 13. i think at most 6 months into P6/P6P release but don't quote that it may be way off but no that's not needed. Though that you asked makes me wonder if you're missing a step in the steps to root. Are you allowing the update to fully finish (boot phone fully up without root) then patch the boot.img in your downloads folder then fastboot flash the results of that. Those steps have proven successful for me.

 

[iwearthebelt]

Thanks. I've tried everything, using Platform Tools 33.0.3:

Flashing patched boot using Magisk 25205 and 25206
Dirty flashed image and flashed patch boot
Fastboot boot <patched boot>

Nothing is working. When I boot with the patched boot, Direct Patch is not an option.

Any other ideas?

By the way, is the disable verity thing still a requirement? Previously, unless that was done before first boot after flashing and flashing patched boot, root is lost and factory reset is required.

If it comes to not having any other options, before you decide to do a factory reset, give Badabing2003's Pixel Flasher a try. Just follow the instructions to use the program. Everything you need is available within the program, download the December release, patch boot.img with the latest magisk and flash it to the current slot that you were using I have a feeling this will bring you right back to where you were before you lost root. If you haven't already used it, I think you'll be pretty impressed with it.

 

[snovvman]

That hasn't been needed since before 13. i think at most 6 months into P6/P6P release but don't quote that it may be way off but no that's not needed. Though that you asked makes me wonder if you're missing a step in the steps to root. Are you allowing the update to fully finish (boot phone fully up without root) then patch the boot.img in your downloads folder then fastboot flash the results of that. Those steps have proven successful for me.

Thanks. I too have read in many instructions where one should allow a full boot after flashing an update before flashing patched boot, but I never have. I have always immediately flashed the patched boot in bootloader after flash-all. It has worked for years among every phone I rooted. I did try what you suggested tonight but still got the same results--no root.

If it comes to not having any other options, before you decide to do a factory reset, give Badabing2003's Pixel Flasher a try. Just follow the instructions to use the program. Everything you need is available within the program, download the December release, patch boot.img with the latest magisk and flash it to the current slot that you were using I have a feeling this will bring you right back to where you were before you lost root. If you haven't already used it, I think you'll be pretty impressed with it.

Thank you. I just tried Pixel Flasher. Very nice tool, but same result--no root after going through the process. I followed the directions, and still no joy. This is puzzling as I have never lost root before. I think something happened during the December update, I just don't know what. I have removed all traces of Magisk, including the hidden one, still nothing.

I'm hoping that someone has seen this problem before and can shed some light.


Edit please see my post below #1487 apparently the latest QPR was the issue.

 

[snovvman]

Tried this, the same result.

Can I reset it/root/boot/whatever without wiping my entire phone? Is that a thing?

@kip256 did you ever find a solution to your loss-of-root issue? I'm seeing the same thing and went through your same steps, but have yet to find a fix. Thanks.

Edit please see my post below #1487 apparently the latest QPR was the issue.

 

[snovvman]

i would hold off for the moment and monitor....there are reports of issues patching the boot image

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread

forum.xda-developers.com

Thanks for this post. I followed the bread crumbs and solved my loss-of-root issue.

 

[V0latyle]

Thanks. I've tried everything, using Platform Tools 33.0.3:

Flashing patched boot using Magisk 25205 and 25206
Dirty flashed image and flashed patch boot
Fastboot boot <patched boot>

Nothing is working. When I boot with the patched boot, Direct Patch is not an option.

Any other ideas?

Are you sure you don't have two instances of Magisk installed? If you've hidden Magisk, it's possible to install it again, and because of the security features in Magisk, only the original app gets root access. This is done to ensure that Magisk alone has the authority to grant root permissions.

By the way, is the disable verity thing still a requirement? Previously, unless that was done before first boot after flashing and flashing patched boot, root is lost and factory reset is required.

No, this has not been required since Magisk 23016. It -may- be required with some custom kernels, but most of them either have patched vbmeta images you can flash, or have correctly updated their boot image headers.

Thanks for this post. I followed the bread crumbs and solved my loss-of-root issue.

Glad you got it fixed, might be a good reason to go back to Stable. I used to use Canary too, but decided that there wasn't really any point because I just want things to work, so I've been using Stable 25.2 on my P5 with no issues.

That's not to say there might still be issues with Tensor devices, though.

 

[Lughnasadh]

Thanks for this post. I followed the bread crumbs and solved my loss-of-root issue.

Oh, you are on QPR2 Beta 1? Your original post said you were on "December's QPR" so I think people assumed you were on the stable December QPR1 build, not the beta build. If you are indeed on the QPR2 Beta 1 build, then yes, as of now, the QPR2 Beta 1 build on the Pixel 6 series needs a patched boot image from the Pixel 7 series. Clean flashing the QPR2 Beta 1 build and then patching the Pixel 6 boot image (instead of the Pixel 7 boot image) may prove successful as well. Magisk team is investigating the issue.

Android 13 QPR2 Beta / 14 DP1 / 14DP2 on Pixel 6 serials requires patching Pixel 7's boot image · 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) Magi...

github.com

 

[snovvman]

Are you sure you don't have two instances of Magisk installed? If you've hidden Magisk, it's possible to install it again, and because of the security features in Magisk, only the original app gets root access. This is done to ensure that Magisk alone has the authority to grant root permissions.

Thanks for this. I did see your earlier post about this and I eliminated that. Obviously, my issue was that strange December. QPR release.

No, this has not been required since Magisk 23016. It -may- be required with some custom kernels, but most of them either have patched vbmeta images you can flash, or have correctly updated their boot image headers.

This was lucky for me. Otherwise having lost root, I might have had to wipe!

Glad you got it fixed, might be a good reason to go back to Stable. I used to use Canary too, but decided that there wasn't really any point because I just want things to work, so I've been using Stable 25.2 on my P5 with no issues.

That's not to say there might still be issues with Tensor devices, though.

There was a time when Canary was needed to get root with whatever the release of the time. I guess that's not the case any more. I will look into it. Thanks again!

 

[snovvman]

Oh, you are on QPR2 Beta 1? Your original post said you were on "December's QPR" so I think people assumed you were on the stable December QPR1 build, not the beta build. If you are indeed on the QPR2 Beta 1 build, then yes, as of now, the QPR2 Beta 1 build on the Pixel 6 series needs a patched boot image from the Pixel 7 series. Clean flashing the QPR2 Beta 1 build and then patching the Pixel 6 boot image (instead of the Pixel 7 boot image) may prove successful as well. Magisk team is investigating the issue.

Android 13 QPR2 Beta / 14 DP1 / 14DP2 on Pixel 6 serials requires patching Pixel 7's boot image · 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) Magi...

github.com

Yea, sorry I was not clear. Before I first posted, I started reading around the August 2022 posts, but did not find a solution. I guess I should have read more recent posts (like we tell all the noobs lol). Losing root was not fun as many of my functions stopped working. This has been a good thread--people are helpful and knowledgeable, unlike some threads that tend to get toxic. Anyway, thanks to all the help. I am back with root!

 

[V0latyle]

There was a time when Canary was needed to get root with whatever the release of the time. I guess that's not the case any more. I will look into it. Thanks again!

Yeah, that was Canary 23016 - 23010 was supposed to support Android 12, but the proper fixes weren't implemented until 23014; the Tensor specific fixes were committed in 23016. So, Stable 24.0 had everything necessary.

There's been a few more fixes along the way, so 25.2 should be sufficient, but there's some weird stuff with the beta that hasn't been figured out yet. I would suggest following the delta channel commits to see when the Tensor beta fix is implemented.

 

[dyval]

Is this way of preserving root would work for future updates? Anyone using this method? Thanks

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.

 

[V0latyle]

Is this way of preserving root would work for future updates? Anyone using this method? Thanks

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.

I believe it has been working, although I personally have never updated that way.

If it doesn't work properly, one of two things will happen:

• It will boot, but you won't have root
• It will bootloop back to the "old" slot, without root

In either case, you can easily regain root by reflashing a patched boot image.

 

[dyval]

I believe it has been working, although I personally have never updated that way.

If it doesn't work properly, one of two things will happen:

• It will boot, but you won't have root
• It will bootloop back to the "old" slot, without root

In either case, you can easily regain root by reflashing a patched boot image.

I appreciate your response brother.

 

[dyval]

I believe it has been working, although I personally have never updated that way.

If it doesn't work properly, one of two things will happen:

• It will boot, but you won't have root
• It will bootloop back to the "old" slot, without root

In either case, you can easily regain root by reflashing a patched boot image.

When you say bootloop back to the old slot that means I'll boot to the older build without root? Not endless bootloop? Thanks again.

 

[V0latyle]

When you say bootloop back to the old slot that means I'll boot to the older build without root? Not endless bootloop? Thanks again.

The way seamless updates are supposed to work, the update engine updates whatever the "other" slot is (inactive at the time), then once the write is successful, requests a reboot to that slot. If a boot failure occurs, the device will automatically recycle to the last known good configuration, which would be the "old" slot you're running on when you took the update.

If the boot process gets far enough before a kernel panic, it is possible for the device to get stuck in an endless bootloop. In this case, command boot to bootloader, and reflash the stock boot image.

 

[silocybin]

My P6P doesn't get the OTA updates is it safe to sideload the update and just reroot?

 

[Lughnasadh]

My P6P doesn't get the OTA updates is it safe to sideload the update and just reroot?

Yes. You can also use Android Flash Tool, Pixel Flasher, flash-all, etc. to update since your bootloader is unlocked.

 

[silocybin]

Yes. You can also use Android Flash Tool, Pixel Flasher, flash-all, etc. to update since your bootloader is unlocked.

i will look into pixel flasher it seems interesting thank you