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

[ermintrude]

Installing the March update today via the factory image and fastboot (as I usually do) I found that patching and flashing boot.img as I usually do didn't work: it booted OK (albeit slower than usual), but no root.

I eventually realised that this is the release-candidate issue mentioned above, now affecting regular updates (so beware!)

After a lot of fruitless experimentation with Pixel 7 boot images etc (none of which worked), I discovered to my relief that the latest Alpha of the Magisk app does the trick fine (usual method: patch boot.img on the device and then boot from it or flash it with fastboot as normal.)

I hope this saves somebody a bit of time (and that it solves the problem for them too.)

Apparently it may not get fixed in Magisk proper, as the issue seems to be a screwup by Google.

 

[digger16309]

Installing the March update today via the factory image and fastboot (as I usually do) I found that patching and flashing boot.img as I usually do didn't work: it booted OK (albeit slower than usual), but no root.

Interesting but haven't seen that elsewhere (yet) and curious if this can be confirmed.

 

[snovvman]

Installing the March update today via the factory image and fastboot (as I usually do) I found that patching and flashing boot.img as I usually do didn't work: it booted OK (albeit slower than usual), but no root.

I eventually realised that this is the release-candidate issue mentioned above, now affecting regular updates (so beware!)

After a lot of fruitless experimentation with Pixel 7 boot images etc (none of which worked), I discovered to my relief that the latest Alpha of the Magisk app does the trick fine (usual method: patch boot.img on the device and then boot from it or flash it with fastboot as normal.)

To what release-candidate issue are you referring? I was on QPR beta, and just flashed the March (release) update on P6P. Did my usual thing, patch the boot, flash-all, flash the patched boot, got root, no issues. I'm on Magisk 25210.

I have my own unrelated issue that I've seen in the past few months--after flash-all and flash patched boot, restart takes me to an corrupted image. To fix it, I simply re-flash again and everything works.

Interesting but haven't seen that elsewhere (yet) and curious if this can be confirmed.

Add me to the list of those who DID NOT have the issue @ermintrude had.

 

[ermintrude]

Not a release candidate at all, but the *regular* March update from Google's factory image site: it's
raven-tq2a.230305.008.e1-factory-def2deef.zip

What I was saying was not that I had installed a release candidate, but that I had run into the same problems with a regular update as those who *had* installed a release candidate.

It was posted on Google's site very late: only a day or so ago.

 

[iwearthebelt]

Not a release candidate at all, but the *regular* March update from Google's factory image site: it's
raven-tq2a.230305.008.e1-factory-def2deef.zip

What I was saying was not that I had installed a release candidate, but that I had run into the same problems with a regular update as those who *had* installed a release candidate.

It was posted on Google's site very late: only a day or so ago.

This is the first time I've ever run into issues updating the monthly on my P6P, Part my fault because I forgot to unhide Magisk (although I didn't think this would cause issues as it hasn't in the past) but somehow I lost root. Not all that big of a deal as I uninstalled Magisk and patched the new update and that fixed the issue but for some strange unknown reason I'm now showing Magisk Delta (which is what I installed), but I'm also showing the icon for the hidden Magisk app which I uninstalled prior to re-rooting. I'm guessing that one of the files must have been left behind. Strangely, everything is working perfectly, Passes root check and integrity, all my modules are there and working as well. Seeing everything is working as it should and I'm not having any issues I'm just going to leave it as is. I think if I try to uninstall the old Magisk app it might take a file with it that shouldn't be uninstalled and I don't feel like doing a full wipe if I don't need to. Anyone else have an issue similar to this please let me know.

 

[TheKum]

Following the OP Updated to Android 13 QPR3 beta T3B1.230224.005, lost root .
Tried several times with patching factory boot img without success.
Then I patched stock boot img from pixel 7 pro QPR3 beta, rooted without no problem.
Everything is working fine. Hope this helps.

 

[digger16309]

Edit - Definitely a cable issue - apologize for multiple edited posts.

Device version-baseband is 'g5123b-107485-221101-B-9242015'.
Update requires 'g5123b-112825-230302-B-9675756'.

 

[V0latyle]

Major issue flashing the march factory image. I'm using Platform Tools 33.0.3 and I'm getting this:

Sending 'radio_a' (94452 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (remote: 'failed to download image')
fastboot: error: Command failed
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-107485-221101-B-9242015
Serial Number........: ************
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' FAILED

Device version-baseband is 'g5123b-107485-221101-B-9242015'.
Update requires 'g5123b-112825-230302-B-9675756'.

fastboot: error: requirements not met!
Press any key to exit...

Double check and make sure you're using the correct files for your device. Remember, Pixel 6 is oriole, 6 Pro is raven. Try a different USB cable. Make sure you're using a type A to type C cable, as C to C cables don't seem to work correctly.

 

[digger16309]

I'm definitely using Raven. I don't know what to do. It's throwing an error looking for an updated radio I can't flash. -9675756.

I guess I could try updating OTA since I'm completely unrooted...

 

[digger16309]

-

 

[digger16309]

Try a different USB cable. Make sure you're using a type A to type C cable, as C to C cables don't seem to work correctly.

Thank you! This was it! I changed cables and ports on my PC.

 

[V0latyle]

I'm definitely using Raven. I don't know what to do. It's throwing an error looking for an updated radio I can't flash. -9675756.

I guess I could try updating OTA since I'm completely unrooted...

Just as a matter of information, if you wanted to force the system update to ignore the bootloader and radio versions, you'd use the --force flag: fastboot update --force image-device-buildnumber.zip

 

[Annil]

For me update on latest march update is not going to sucess with Root unfortunately
Till now I was using Magisk Delta and used Pixelflasher - worked everytime like a charm.

Now after march update I lost root and am not able to regain it. I patched boot image with Delta Magisk but when booting (live or flash), root is not present.

When selecting Canary Build from Magisk, Pixelflasher is telling
WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.

Anyone facing similar issues and is able to help to regain Root?

Edit:
There seems to be an issue between latest Magisk and March update...
I had to downgrade from 25210 to 25206 which works now flawlessly as usual.

 

[pa.pn2]

Btw, how do I downgrade correctly?
I downloaded 25206, uninstalled the magisk 25210 version and installed the app-release.apk.
When I launch magisk, it prompts directly an update to 25210...

 

[Annil]

I downgraded by renaming the lower version apk file to magisk.zip and installed this then as "new module install from zip file" in Magisk - this way always works for me easiest/fastest and is desribed in FAQ of Magisk.

 

[StanWiz]

........... Make sure you're using a type A to type C cable, as C to C cables don't seem to work correctly.

Good to know - I've always used the original C to C cable without issues. Guess it depends on the pc (my is fairly recent)

 

[iwearthebelt]

For me update on latest march update is not going to sucess with Root unfortunately
Till now I was using Magisk Delta and used Pixelflasher - worked everytime like a charm.

Now after march update I lost root and am not able to regain it. I patched boot image with Delta Magisk but when booting (live or flash), root is not present.

When selecting Canary Build from Magisk, Pixelflasher is telling
WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.

Anyone facing similar issues and is able to help to regain Root?

Edit:
There seems to be an issue between latest Magisk and March update...
I had to downgrade from 25210 to 25206 which works now flawlessly as usual.

I had the same exact problem, on delta and using PixelFlasher. After some trial and error I figured out how to get it back to where it was. It's actually really simple. Just uninstall any instance of the Magisk app you have installed, including any hidden magisk app you may have forgotten to unhide (uninstall them just like any other app by long pressing on the app and dragging it to the top where it says uninstall). Once you have all instances of the Magisk app uninstalled, just use PixelFlasher like you normally do. Download the March update, process and patch it, flash it and let PixelFlasher do it's thing. Thats it, you're back to where you were before you lost root except now you're on the March release. All your modules will still be there and enabled (just remember to keep data when flashing). Let me know how it goes.

 

[dilligaf56]

Hmmm. I'm still on the February update, rooted, with Magisk 25210. Given the issues above, I'm wondering if I should just wait until the issue with Magisk is resolved before updating to March (or April, when it's available)...right now everything works fine other than some screen weirdness (flashing) after a day or so, which resolves after a reboot. Is there any pressing reason to update to March at this point?

 

[iwearthebelt]

Hmmm. I'm still on the February update, rooted, with Magisk 25210. Given the issues above, I'm wondering if I should just wait until the issue with Magisk is resolved before updating to March (or April, when it's available)...right now everything works fine other than some screen weirdness (flashing) after a day or so, which resolves after a reboot. Is there any pressing reason to update to March at this point?

Personality, I just like running the latest builds with all the most recent updates. I've just always updated the nightlies on whatever ROM I was running so it's probably more of a habit than anything. If your device is running perfectly fine and you're happy with it, there's really no need to update other than security reasons or if you're wanting on some kind of fix for whatever issue you might be having.

 

[dilligaf56]

Personality, I just like running the latest builds with all the most recent updates. I've just always updated the nightlies on whatever ROM I was running so it's probably more of a habit than anything. If your device is running perfectly fine and you're happy with it, there's really no need to update other than security reasons or if you're wanting on some kind of fix for whatever issue you might be having.

I usually like to be on the latest build as well, so as soon as I see that there aren't any major issues, I upgrade (still using the OG CLI method, not PixelFlasher, though am going to look into it). It looks like there have been more problems than usual this month. Is there a link to the changelog for the March update anywhere? Thanks for the come-back.