How To Guide March 4, 2024 AP1A.240305.019.A1 Global - Root Pixel 6 Pro [Raven]

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
@beaverhead your post above is blank other than containing a quote of another user's post. Do you want to Edit your post above, or Report it to be deleted if it was a complete mistake? Cheers!

Edit: My bad, didn't realize your post had been inserted within the quote of @Lughnasadh's post. :)
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
theres-a-name-ive-not-heard-in-many-years.gif
 

shoey63

Recognized Contributor
Just curious what Magisk version you used? For what it's worth, it's been really hit or miss when using the "Install to inactive slot method" on this device. Some have no problems doing it, while it seems most do have problems. I think some of the problems, at least, come from people modifying some partition and then not restoring it back to stock beforehand.

But yeah, it certainly isn't a reliable way to update and keep root.
Latest canary. Hasn't worked for the last 3 updates, even while on A12.
It has worked with some variants of Magisk in the past, but I saw on GitHub that it's no longer supported for Pixel 6/Pro
 

Lughnasadh

Senior Member
Mar 23, 2015
6,096
7,538
Google Nexus 5
Huawei Nexus 6P
Latest canary. Hasn't worked for the last 3 updates, even while on A12.
It has worked with some variants of Magisk in the past, but I saw on GitHub that it's no longer supported for Pixel 6/Pro
I didn't realize he removed that support again. I know in, I think it was, late 2020? he removed support for Pixels because it was leading to bootloops, but then he re-added support in Jan. 2022 with the release of Magisk 24.0 when he updated the bootctl binary. In May he removed the temporary note about OTA update no longer working on Pixels in the document instructions, but I don't see that he's updated those instructions to say it no longer works on the Pixel 6 series and didn't see anything in the changelogs referencing support removal.

Interesting....Oh well.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
6,096
7,538
Google Nexus 5
Huawei Nexus 6P
"Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule."

Don't see downloads for the factory images yet, though.

@roirraW "edor" ehT Wasn't sure if you were going to create another thread for this (I think you mentioned that you may do that) or use your old thread (I was too lazy to find it 🙃), so I just posted it here.

 

roirraW "edor" ehT

Forum Moderator
Staff member
"Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule."

Don't see downloads for the factory images yet, though.

@roirraW "edor" ehT Wasn't sure if you were going to create another thread for this (I think you mentioned that you may do that) or use your old thread (I was too lazy to find it 🙃), so I just posted it here.

Done, thanks! I'm just repurposing my Android 13 Developer Preview / Beta thread: Android 13 QPR1 Beta 1 (September 8, 2022) is available via (opt-in) OTA - still looking for (full) firmware image zip
 

roirraW "edor" ehT

Forum Moderator
Staff member
Does anyone know what happened to the MVK kernel? The thread was locked and OP was deleted.
I do not, at least any further than the statement at the end of the thread:
Thread closed on request of OP ctfrommn who also removed the content of the opening post.

I am curious too, but that information would be private between the OP and @Oswald Boelcke, and I have no true "need to know" so I won't ask them.

If I did have a need to know, I wouldn't be able to share that information, though, same as my esteemed teammate.
 
Last edited:
  • Like
Reactions: Oswald Boelcke

roirraW "edor" ehT

Forum Moderator
Staff member

rester555

Senior Member
Oct 27, 2010
766
398
Google Pixel 6 Pro
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Is the radio any different?
I haven't bothered downloading it (I'm not on Verizon). You can download it, extract the radio.img, then do a MD5, SHA1, or any other hash check and compare the results with the radio.img from the non-A1 September update to see if there are any changes. I'd say it's likely there are differences in the radio.img because that's mostly what the different carrier versions are about - I think.
 
  • Like
Reactions: rester555
Is the radio any different?
Yes, the radio has a different version number on it.....havent flashed it, not sure I will

***EDIT - I want to correct my comment......I was looking at the QPR.

The VZW radio is the same as the Non-VZW image radio. The QPR has a different radio. just for correctness.
 
Last edited:

swieder711

Senior Member
Argh. Stable 13 Worldwide is running nicely on my P6P. Now there is a Verizon variant. Not sure if it worth the update. I am on Verizon's network.

I will probably dirty flash the VZ version over the WW version with the hope of better cellular coverage. Maybe I will just flash the modem file. Be nice to know if there are any other differences between the two versions.
 

hpower1

Senior Member
Jan 24, 2012
218
112
Argh. Stable 13 Worldwide is running nicely on my P6P. Now there is a Verizon variant. Not sure if it worth the update. I am on Verizon's network.

I will probably dirty flash the VZ version over the WW version with the hope of better cellular coverage. Maybe I will just flash the modem file. Be nice to know if there are any other differences between the two versions.
post if you try and see any difference. Maybe i'll try using my P6P again....
 
  • Like
Reactions: roirraW "edor" ehT

swieder711

Senior Member
post if you try and see any difference. Maybe i'll try using my P6P again....
I dirty flashed the VZ update over the WW and everything went to hell. Got repeated System UI crashes. Temporarily lost root. I am back on the WW release and things are stable again. I am going to just flash the Vz modem on to the WW release as an interim upgrade.

EDIT: The file names for the modem are the same in the WW and Vz versions, radio-raven-g5123b-102852-220720-b-8851166. Huh?
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,725
1,929
Google Pixel 6 Pro
I dirty flashed the VZ update over the WW and everything went to hell. Got repeated System UI crashes. I am back on the WW release and things are stable again. I am going to just flash the Vz modem on to the WW release as an interim upgrade.
Did you try google's flash tool. I used it to convert from ww to vzw and no errors, no difference i can see, though my house sits in a low signal 4G when I'm out and about i get strong 5G and 4G signals.
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Am i wrong or is battery optimization gone and replaced by allow background battery use?

    View attachment 6077774
    Tap the "Allow background usage" text and you should see Optimized and Unrestricted options.
    3
    Just a heads-up: on march update iconify refuse to work if trying to hide navbar. Probably because of laposed incompatibility.Pixel expert also doesn't help but mmersive gesture module still alive.

    Thanks!

    I've been using the following since Iconify broke on QPR1, although I had thought about returning since it had been fixed.
    • @DanGLES3's thread Fullscreen/Immersive Gesture Tweaks for Android 10-14 (most up-to-date version available at the GitHub link in his OP). You configure it while flashing the module using the volume keys. I choose:
      • - (Immersive)
      • + (Hide keyboard buttons - Back/Switch keyboard)
      • + (Reduce the size of the keyboard bar)
      • + (Pick the gesture sensitivity - Low/Module Default)
      • + (Enable Gcam fix)
      • - (NOT Wish to disable the back gesture)
    2
    Your kernel version is not going to change.
    oh your new pixel flasher supports kernelSU patching now .. im currently sitting with sweaty palms as its OTA flashing :)
    Edit: wow, that was so easy. The only issue i experienced was the timeout issue when rebooting after flash, but it was just a bit slow to come back up.
    Pixel Flasher is amazing work :)
  • 65
    Pixel 6 Pro [Raven]

    March 4, 2024:







    Here is the blog post with more in-depth info


    February 16, 2024:

    ADB/Fastboot (SDK Platform Tools) v35.0.0

    Direct Windows download link:

    No changelog yet.

    Regarding Developer Support Android 12 images, see @Lughnasadh's post here.

    I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search Developer Support Android images if you want to find them.

    TL;DR regarding the PSA. If you update one slot to Android 13, you can fastboot reboot bootloader after and then fastboot --set-active=other to change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.

    At a minimum, do this first: fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img (change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.

    IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.


    You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.

    My tiny, early, very mini-review of Android 13 is here.

    Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.

    Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.

    Here there be dragons. 🐉 I am not responsible for anything at all. 😹

    Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.


    Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.

    There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.


    All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
    If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​


    Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
    Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)

    Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

    Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
    Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
    OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.

    ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
    • You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
    • For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
    • Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:


      The unlock process works like this:

      1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
      2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
      3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
      4) Back --> Network --> WiFi and connect it.
      5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.

      Using the Platform Tools previously mentioned in command line/terminal:
      6) #
      Code:
      adb reboot-bootloader
      7) #
      Code:
      fastboot flashing unlock

      Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

      Official Instructions for Locking/Unlocking the Bootloader
    Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
    I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).

    Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.

    Fastboot/ADB Driver Interface - Official Download Link:
    When flashing a full image or unlocking your bootloader, the fastboot interface is being used.

    First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.

    Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.

    Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
    Official Download Page
    "Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"

    It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

    Rooting-related


    No longer applies - Things that make rooting more complicated on Android 12
    @V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

    A list of the other important guides - be sure to thank the respective OPs
    For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.


    TWRP (not made for the Pixel 6 Pro yet - will update when it has)
    I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.

    Custom kernels for stock ROM(s)

    Factory Images (requires an unlocked bootloader)
    It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.

    Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available

    Full OTA Images (doesn't require an unlocked bootloader)

    The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.

    Regarding P6P 5G model numbers and capabilities - post #3 below.

    List of all Pixel monthly security bulletins and Play System Updates - post #4 below.

    How I root and update (which is identical whether rooting the first time or updating):
    • Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
    • Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
    • Extracted the new boot.img
    • Copied new boot.img to the phone
    • Patched the new boot.img with Magisk Stable
    • Renamed Magisk'd boot.img so I know what version of firmware it's for
    • Copied the Magisk'd boot.img back to the computer
    • Disabled all my Magisk Modules
    • Removed the "-w " from the flash-all.bat
    • Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
    • Open a Command Prompt, navigated to S:\platform-tools
    • adb reboot bootloader
    • flash-all.bat
    • Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
    • adb reboot bootloader
    • fastboot flash boot kernel.img (renamed Magisk'd boot.img)
    • fastboot reboot
    • Unlock, check everything's working
    • Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
    • Reboot, unlock, made sure everything's working
    Back to modding!

    I may append these first four posts with further useful information or links as needed.
    16
    The unlock process works like this;

    1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
    2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
    3) Settings --> About --> Build number. Tap it until it says you're a developer.
    4) Back --> Network --> Wifi and connect it.
    5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
    6) # adb reboot-bootloader
    7) # fastboot flashing unlock

    Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
    16
    I'm less concerned about the steps/commands as I am with how you updated (auto OTA, sideload, factory image), whether you booted to Android 13, and what happened when you rolled back (I assume using the factory image)
    Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both use update_engine. I did boot into Android 13 so the ARB counter did get incremented.
    Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:

    Android 12 doesn't work properly on the Android 13 bootloader.

    It boots up just fine, appears to work just fine, made and received calls and texts, however the issue @bush911 had with WebView crashing is true. It's more than just WebView, the media DRM APEX immediately crashes. WebView crashes sometime after launch when it tries to find out if ClearPlay or WideVine are functional, and DRM Info crashes immediately when I try to launch it. Without DRM working that means you won't be able to play some music or movies and won't be able to use Netflix or any other streaming app.
    There might be more systems or modules nonfunctional, but without working browsers your smartphone isn't going to be more useful than a dumbphone.

    @roirraW "edor" ehT
    So I guess it's time to retract that you can revert to Android 12, because until a modder comes along to cook up a custom Android 12 ROM with Android 13 APEXs or patched ones it won't work.
    15
    SDK Platform Tools updated to v33.0.1 (March 2022):

    33.0.1 (March 2022)​

    • adb
      • Fixes Windows mdns crashes.
      • Fixes enable-verity/disable-verity on old devices.
      • Fixes "install multiple" on old devices
      • Improves the help output to include all supported compression methods.
    13
    Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.

    Canary 23014

    EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍