Yes, having the A13 bootloader flashed to both slots is the minimum required to keep you safe from the new ARB.
How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
FYI, Partition is NOT the same as a Slot. So don't confuse the two.
Each slot has multiple partitions.
Okay, you know, but I see stuff like this being posted and it's hella confusing for people not in the know.
Is this going to be a concern with every bootloader going forward or just this initial one for A13?
We cannot tell the future.
Seriously, though, the only information we have is about what's currently available. The reason that Google did it was very specific, and I agree that it was justified. Since Android 12 runs just fine on the Android 13 bootloader, if you decide to downgrade everything but the bootloader (since the bootloader can't be downgraded), there's no real issue except for the users who, unfortunately, try to boot Android 12 (including Android 12 bootloader) on the other slot after the active slot is upgraded to Android 13, which is when a permanent brick is encountered.
Further in the OP are shared posts regarding the reasoning why Google did it.
Having said all that, it's fully expected that the answer to your question is "just the initial one for A13". The reason my explanation is complicated is that we have no way of knowing if, for example, a serious downgrade vulnerability will be found to exist in this build of Android 13's bootloader. If that is discovered eventually (days, weeks, months...years from now), then it won't surprise me if they implement the same non-downgradeable bootloader policy yet again.
I hope this all makes sense.
Last edited:
gpvecchi
Senior Member
I did this: phone updated to A13 and booted, then I flashed full OTA via adb. Now I should have the full image on both slots, right?
Last edited:
Sounds right. I don't use OTAs at all though, I prefer full images so that I know what's being flashed where.
@roirraW "edor" ehT Check out the new instructions on the factory image download page. Maybe a day late and a dollar short but at least it's there now.
D
Deleted member 6200352
Guest
I would like to think Google is learning the errors of their ways from this debacle and we will probally see the next ARB on A15. I can see them not doing it for A14. But we cannot see the future. It's ironic that Google is going after Apple over the whole "we need to make SMS between IOS and Android better"--as if it's come kind of closed vs open dichotomy, which it seems Google is becoming more like Apple every day in that respect.
My wife's unlockable but locked, stock, and non-rooted Pixel 6 Pro is getting the Android 13 OTA right now. It's been taking a while, but our Wi-Fi has also been a little funky the last few hours, so I think it's been interrupted at least once.
Thanks! Putting this in the OP (with a modified URL to point to the "Updating..." section).@roirraW "edor" ehT Check out the new instructions on the factory image download page. Maybe a day late and a dollar short but at least it's there now.
New news for you.
From @Lughnasadh's update linked below:
Check out the new instructions on the factory image download page. Maybe a day late and a dollar short but at least it's there now.
You did exactly right (according to Option 1 at the link):
D
Deleted member 6200352
Guest
Wow. They (Google) wrote a whole essay on this **CENSORED**. Yeah that's good and all for those with good attention spans. This is NOT going to go well for Google. I see way more bricks to come unfortunately. What google should do is take the firmware links off that page. Then force the user to read ALL the steps and their essay then click button to go to the image downloads. Help try to minimize people who may have their own way of flashing things but not how Google wants/needs you to do on ARB builds. Yeah this is gonna bite them. Most people will be on A13 ok. But I think you will have a larger than usual percentage with bricked devices. Not just from rooters/modders but just everyday users. I think google F'd this one up on their lack of communication. The fact they had to update the steps and include that essay speaks volumes. Just my $0.02.
*Thank you to the moderator for NOT even giving me a chance to edit my post to conform to your questionable policies. Proof: You remove the 'CF' but not the 'F'd" up. I expect you to further edit this against my will. As you can see I censored the previously censored "CF".Why? to prove my poiint. Have a good day.
Last edited by a moderator:
@roirraW "edor" ehT @Lughnasadh @V0latyle
So after reading some threads of people failing to flash their devices with
Extremely weird, because on every other Pixel device they can flash all partitions to all slots no problem.
Well it turns out this is what is causing the issue:
The super partition holding the sizes of each partition is used, however the opposite slot for each partition is being resized to the same size and this isn't leaving enough space left. With several opposite slots being larger than they should be, like the system slot, or other slots being included when they shouldn't is messing things up.
A proper dynamic partitioning should be these:
So with this in mind the proper instructions would be to update from Android 12 with fastboot:
There's actually one minor issue with Google's steps for option 2:
>
They're having people reboot into fastbootd which can't flash the bootloader, so if the people try to continue from within fastbootd they'll have that issue.
So after reading some threads of people failing to flash their devices with
--slot all update I decided to update as I'll probably be getting a Pixel 7 before the disclosure on the vulnerability in the bootloader is released. After trying it I found that the Pixel 6 can't have update use --slot all.Extremely weird, because on every other Pixel device they can flash all partitions to all slots no problem.
Well it turns out this is what is causing the issue:
Code:
Sending 'super' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.015s]
Resizing 'product_a' OKAY [ 0.003s]
Resizing 'product_b' OKAY [ 0.002s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_ext_b' OKAY [ 0.003s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_b' OKAY [ 0.004s]The super partition holding the sizes of each partition is used, however the opposite slot for each partition is being resized to the same size and this isn't leaving enough space left. With several opposite slots being larger than they should be, like the system slot, or other slots being included when they shouldn't is messing things up.
A proper dynamic partitioning should be these:
Code:
Sending 'super' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.013s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
Resizing 'vendor_dlkm_a' OKAY [ 0.002s]
Resizing 'vendor_b' OKAY [ 0.002s]So with this in mind the proper instructions would be to update from Android 12 with fastboot:
adb reboot bootloaderfastboot --slot all flash bootloader bootloader.imgfastboot --slot all flash radio radio.imgfastboot reboot bootloaderfastboot --skip-reboot update image.zipfastboot --set-active=otherfastboot reboot bootloaderfastboot update image.zip- If using Magisk instead use
fastboot --skip-reboot update image.zip fastboot reboot bootloader- Use the flash or boot method on your Magisk patched boot image.
- If using Magisk instead use
sideload:adb reboot sideloadadb sideload ota.zipadb reboot sideload- can be done from within the recoveryadb sideload ota.zip
@roirraW "edor" ehT Check out the new instructions on the factory image download page. Maybe a day late and a dollar short but at least it's there now.
There's actually one minor issue with Google's steps for option 2:
>
adb reboot fastbootThey're having people reboot into fastbootd which can't flash the bootloader, so if the people try to continue from within fastbootd they'll have that issue.
Last edited:
So they're following the unfixed instructions and putting everyone where i was yesterday ?
Last edited by a moderator:
Top Liked Posts
-
There are no posts matching your filters.
-
32Platform-Tools is updated to 35.0.1:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for...
developer.android.com
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
