I actually can't say for sure since I really don't use any profiles, but I think it does.
How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
I use the full Pixel 6 Pro Factory Image to update each month. Use the same official latest ADB/Fastboot (SDK Platform Tools) you normally use. Edit the flash-all.bat (if on Windows - if on something else, edit the appropriate flash-all script file) and remove the "-w" and re-save it. If you want to keep the flash-all.bat from rebooting automatically after the update so that you can change slots and flash again, add
fastboot --skip-reboot in the flash-all.bat after the fastboot update image-raven-xyNz.YYMMDD.BBB.zip line. Thanks, @Homeboy76 and @Lughnasadh!Re-open the script file and confirm that you saved it with the "-w" removed, so it doesn't wipe your device.
From running Android:
Code:
adb reboot bootloader
(Let it reboot into Fastboot mode. Make note of which active slot is listed on the Fastboot screen, third item from the bottom.)
flash-all.bat
(WITH "-w" removed. Let it flash everything, will take several minutes.)
Let it boot up (and check the notifications for the update process to finish while Android is running)
adb reboot bootloader
On the Fastboot screen, change to the opposite slot with either:
fastboot --set-active=a
(If you're on slot b)
OR
fastboot --set-active=b
(If you're on slot a)
OR
[QUOTE="Homeboy76, post: 87298957, member: 4810220"]
I think you may want to use
[ICODE] fastboot --set-active=other[/ICODE]
it lowers the mistake threshold.
[/QUOTE]
flash-all.bat
(again)
Last edited:
I used the flash-all method. I was on slot b so I flashed A13 on it and let it boot up (I removed the -w from the flash-all.bat script beforehand to preserve data) Then went into fastboot and switched slots and flashed the factory image again and booted. Now booted on slot a with both slots having A13 on them. That's it.
Oh okay, thanks. I assumed you went straight from flashing the one slot to flashing the other slot.
I let it boot after the first flash-all. See post above.
What is the fastboot command to switch slots?
I thought when upgrading to a major release like 12.1 to 13 that is it was recommended to do a full wipe/fresh install.
No problem. Wanted to ensure everything booted up fine on one slot before doing the other just as a precaution.Oh okay, thanks. I assumed you went straight from flashing the one slot to flashing the other slot.
Thanks! When in the process do you do that? Before running the flash-all.bat? Cheers.
Recommended by who? I would only do that if you have problems doing the normal way, without a wipe. I haven't (purposefully) wiped a running and rooted device in 4-5 years.
fastboot --set-active=a (or b)
Yes, it is wise to do a full wipe when upgrading OS versions, imo. I had cleaned flashed the latest A13 Beta so that is why I didn't clean flash to A13 stable since there was not much change between the two.
Need a sticky telling people not to touch their phone for manual updates unless they've unlocked their bootloader (or at least set the toggle) and are comfortable working with fastboot for hours at a time before they even begin to think about restoring their Google backups.
Add it to the flash-all.bat script (after the update line)
It was me that recommended (in my threads) wiping your phone before doing an Android upgrade.
Why?
Something went, horribly, wrong during one of my upgrade to a new Android version. I don't remember which Android version it was. I just remember "recommending" members wipe before upgrading an Android version.
After, reading your post, I will be editing my threads.
Ah, I see. Years ago, I used to wipe before every single update, but that was on other OEM's devices, so didn't happen every month. I was often using someone's modified stock ROM, but not long after I started using the Pixel and stopped experimenting with ROMs, I no longer would wipe at all unless something catastrophic happened, or I goofed up the process.It was me that recommended (in my threads) wiping your phone before doing an Android upgrade.
Why?
Something went, horribly, wrong during one of my upgrade to a new Android version. I don't remember which Android version it was. I just remember "recommending" members wipe before upgrading an Android version.
After, reading your post, I will be editing my threads.
I think the last time I purposefully wiped (not counting bootloader unlocks or disabling Verity/Verification) was on Android 8.0. That would've been back when I was still experimenting with ROMs - or trying to troubleshoot a weird problem I used to have that ended up being my own fault.
Now, you have officially earned the dual title Fast Fingers/Keyboard Operator
I updated the flash-all.bat to reflect the changes mentioned above but have this error:
error: failed to load image-bluejay.....zip
What is that?
error: failed to load image-bluejay.....zip
What is that?
Do you have a Pixel 6A? That's what "bluejay" is. If you have a Pixel 6 Pro, then you downloaded the wrong factory image. Correct one for the Pixel 6 Pro.
Do you have all the necessary files extracted into the same folder with the latest SDK Platform Tools (ADB/Fastboot)?
I'm first updating my 6a. I'm using the correct image. But can't figure out what that error is.
Just FYI , those who haven't come across this issue: I was updating to 13 by means of adb sideload because google decided to push Android 12 again (Germany/EU), mistake on their end. Sideload failed at "verify update package", just sat there doing nothing for an hour before i killed it. I found this neat info on this thread that was a straight forward fix. using the only USB 2.0 port on my machine it worked right away. Not even 5 minutes. Thread author might point this out at the start of the thread? pretty general info though. Fastboot and ADB both appear to be working on USB-C to C, just not sideload. Dunno were this info could be posted best to save people hours of searching.
Top Liked Posts
-
There are no posts matching your filters.
-
32
I gather you're all good now?
In the future please create post PF issues in PF thread to keep this thread tidy and focused, and always provide a support file.22
I did go through and successfully flashed my PX6 pro to AP1A.240405.002 with KSU using PixelFlasher 6.8.3.0 -
66Pixel 6 Pro [Raven]
April 2, 2024:
Android Security Bulletins | Android Open Source Project
source.android.com
Here there be dragons.
I am not responsible for anything at all. 
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)
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)
Rooting-related
No longer applies -Things that make rooting more complicated on Android 12
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.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
Custom kernels for stock ROM(s)
Factory Images (requires an unlocked bootloader)
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):
16The 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
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 useupdate_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.1513Just 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
