yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] V0latyle:
I'd like to point out that most companies will fight you tooth and nail over warranty claims if there's any evidence you've modified the product - Magnusson Moss Warranty Act be damned. This includes software. The bootloader unlock itself is a designed function, but since at that point the user can load unverified and potentially malicious software on the device, they can argue that warranty should not cover repair due to the potential that modifications caused damage.

Believe me, I've been over this. I own a 2012 VW GTI with APR Stage 2. It made 275hp/321tq on the dyno (+75hp/+114tq over stock). I've had the water pump replaced 3 times, the intake manifold twice, the engine speed sensor twice, the PCV valve once...And none of this was covered under warranty due to the mods. Granted, the mods didn't cause any of the failures - they failed due to faulty designs - but VW is adamant about not performing warranty repairs on modified cars. Sure, you can potentially take them to court, and they'd be hard pressed to prove that your modifications caused the failure, but they have a lot more money and better lawyers.
[Google Pixel 6 Pro] crescentmage:
That's what small claims courts are for. Pay ~$100 to file, no lawyers necessary, local court. Most companies would rather solve your problem then pay to fly a lawyer out to argue the case in front of a local judge, and even if they do the judge expects a self-represented case so you have a good chance of winning. As long as the issue's costs are under the court limit (varies by state, California is $10,000), it's just the time cost of showing up and gathering your evidence, which might not be worth it for some people but worth it for others.

Example of a blogger successfully suing Apple in small claims over Macbook warranty issues

Canadian man wins a small claims ruling for $8,000 against Volkswagen for warranty claims
[Google Pixel 6 Pro] Guy50570:
Of course this doesn't work, reminder that we're not working with a Qualcomm device. I figured it was safe to assume that *some* packages would still be reused but, no, this doesn't work at all, and I frankly feel a bit silly thinking it had any chance of working at all. Tried on an AT&T carrier locked device purchased on an installment plan, package doesn't even exist, get "Failure [not installed for 0]...

The hunt is still on folks, let's hope it doesn't take too long...
[Google Pixel 6 Pro] snovvman:
Is there a way to pass SafetyNet with bootloader unlocked but not rooting? The idea is that I can start using the phone with the bootloader unlocked and unrooted until [hopefully] a reliable process is established for both the monthly update-no wipe and SafetyNet, then root. This way, I won't have to wipe because of needing to unlock bootloader later.

Thanks.
[Google Pixel 6 Pro] Lughnasadh:
All the ways I'm aware of require a Magisk Mod(s) so I don't think so.
[Google Pixel 6 Pro] V0latyle:
Just to be clear, we did establish that force flashing Android 12 is possible on the new bootloader and it will boot - after Android 13 has been booted and increments ARB?
[Google Pixel 6 Pro] Namelesswonder:
It does, @bush911 has done it and booted Android 12.

However he is currently having issue with WebView crashing, and we don't know if it is because of his Magisk modules and LSPosed or something else.

I'm going to be flashing Android 12 to attempt to see if I have the same issue or if it is just on his end.
[Google Pixel 6 Pro] V0latyle:
Okay, I don't know if you already did but please document it as well as how you upgraded to Android 13.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks @Namelesswonder! Adding the most important parts of that to the OP.
[Google Pixel 6 Pro] Nergal di Cuthah:
So is google just following this thread and posting what we (you all) do without checking. Are we (you) figuring this out for them SMH.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I doubt if Google knows about this thread. It's a simple mistake. It hasn't been the first time it's been made, and won't be the last. :D
[Google Pixel 6 Pro] Namelesswonder:
I don't want to say they are following us, but they surely aren't testing, that much we know.

My previous post above listed the steps, and I tested both fastboot and adb and the result was the same with a phone that has Android 13 on all partitions on both slots.

Currently downgrading back to Android 12 right now, steps soon.
[Google Pixel 6 Pro] V0latyle:
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)
[Google Pixel 6 Pro] Namelesswonder:
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.
[Google Pixel 6 Pro] V0latyle:
Awesome, thank you for this information.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Done, thank you again!
[Google Pixel 6 Pro] Ghisy:
Honestly, that's a pretty bad move from Google! I mean, it's not like everyone wants to go back to 12 (heck, I wouldn't) but I don't like the fact they're getting more restrictive...
[Google Pixel 6 Pro] Namelesswonder:
The APEX changes are because they function as hardware abstraction libraries. I guess in this case the DRM APEX is talking to the bootloader, and because of changes in the bootloader in Android 13 the DRM APEX crashes. This is why HALs and firmware need to be kept in step with each other. This specifically wasn't intentional to block people from just forcing Android 12 on, just a symptom of HALs.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's for security reasons that you can't downgrade the bootloader. The fact that Android 12 doesn't actually work properly with Android 13's bootloader isn't an intentional act from Google, only the non-downgradeable bootloader.

Edit; I was ninja'd. :D
[Google Pixel 6 Pro] Ghisy:
Oh I understand the security reasons. So Google might actually fix Android 12 not working properly with A13 bootloader by upgrading to a newer bootloader at some point?
[Google Pixel 6 Pro] Namelesswonder:
No. Google has no motivation to allow Android 12 to be functional, which doesn't matter because then if they change the Android 13 bootloader to make it work with the Android 12 DRM APEX that could end up breaking the Android 13 DRM APEX or other things.

A modder at some point might be able to cook up a custom Android 12 ROM with patched APEXs, but who knows if it'll work or is worth the effort.
[Google Pixel 6 Pro] :
I agree. It was a bad move. ARB has been around since Oreo and in addition to some other devices seems it's happening more often that they are implementing it. All in the name of security... <cough>

If we ever get a firehose for the 6 (and others), that could potentially be a way around ARB..i dunno <fart> .
[Google Pixel 6 Pro] Namelesswonder:
It's not, the Android 12 bootloader had a vulnerability that would allow an attacker to do something major to the phone. Google hasn't disclosed the details, but they would only do this if there was a vulnerability that would allow an attacker to either bootloader unlock the device without wiping, compromise the Titan, or boot a malicious payload without unlocking the device. Google had to increment the anti-rollback counter on the bootloader or else a downgrade attack could be used to exploit the vulnerability.

You might view it as a hostile attack by Google on your freedoms, and in a way you would be a little correct. However Google sees it as the opposite, they have millions of Pixel phones in the world that have a vulnerability that most likely allows the private data on them to be compromised. What would you do in this scenario? Just allow the vulnerability to continue existing and a path an attacker could take to perform it?
[Google Pixel 6 Pro] :
Yes. They are only jealous the private date belongs to others and not just Google. <kidding>

Can you prove this exploit exists in the wild? Can you show that people are getting duped by malware that's unlocking/downgrading and/or updating their device with god knows what is on it? Like a fake update? This would be a very specific attack done under very specific instances. No. I don't buy it. Vast magority of people don't mod their phones. The phone is locked down (more so if carrier locked). Are you telling me that THOSE people could have their bootloaders remotely unlocked and/or downgraded/upgraded w/ malicious payload without any ACTION by the user? If so, then this goes way beyond the bootloader.
[Google Pixel 6 Pro] CRXed:
Most CVE's are under very specific circumstances. Does not mean they don't need fixing.
[Google Pixel 6 Pro] :
Food for thought: The Pixel 4's and 5's don't have the FRB issue. Are these devices also in danger due to this exploit? And if not, why? And if not, why the 6?

What I'm geting at is, ok an attacker can remote unlock the BL on a pixel 6. Can they do the same on the 4/5? And if they can, can't ARB be done on those devices? ARB has been around since Oreo so theoricially they could make it so the pixel 3s and 4s and 5s cannot downgrade to android 12 from 13, or android 11 from 12 if they did that.
[Google Pixel 6 Pro] Namelesswonder:
Most likely not, since Qualcomm Pixels uses Qualcomm's bootloaders which are fundamentally different from the bootloaders that Tensor Pixels use, which are an implementation of ARM Trusted Firmware.

And you're taking the speculation a lot farther than anyone else.

It's up to Google and whoever else discovered this vulnerability to disclose it, and not every vulnerability gets a disclosure.

Google could implement the anti-rollback counter on them, but they haven't. Because they probably aren't vulnerable.

In your grand theory of Google becoming draconian, wouldn't they want to prevent all Pixel phones from downgrading? Why just the Pixel 6s?

And everyone needs to stop bringing up the "Oreo added ARB"

Yes, Oreo added anti-rollback to Android Verified Boot.

This is not what is being used here.​

AVB-ARB is used to prevent the kernel from being downgraded.

What is implemented in the Pixel 6s bootloaders are anti-rollback to prevent a bootloader downgrade.

These are not the same things.​

If they were then I wouldn't have ever been able to boot Android 12.
[Google Pixel 6 Pro] badabing2003:
Thanks for the steps, Am I correct in stating that the above steps will not flash the System (image) onto both slots?

Although one can still switch the slot and flash

fastboot update image.zip
[Google Pixel 6 Pro] Namelesswonder:
The steps actually won't, but I just updated them.

It's just that update doesn't work properly with --slot all on the Pixel 6s, which is weird because I tested it on a Pixel 5 and XL and it works just fine. Android on both slots are flashed fresh from the update/sideload, reboot, update/sideload
[Google Pixel 6 Pro] Namelesswonder:
@roirraW "edor" ehT

Actually I just updated the steps, I forgot to add an --set-active=other, whoops. :cry:
[Google Pixel 6 Pro] :
All I'm saying is the days of rooting and modding on newer phones are numbered. All in the name of security. They found a exploit on a newer more powerful chip that wasn't found/applicable in the older snapdragons. It [Tensor], and its newer variants will be found in newer devices. Therefore Google is putting the gauntlet down now to control (possibly each and every way) their brand new shiny new chip. Embarrassing. Already there is a way an attacker can do this on a brand new chip. No more rooting. Or customizing. Kernels, recoveries, etc. Google is doing what any company does, covering it up any way they can. They are doing that by locking it down. Locking it down. Locking it down. The Tensor was supposed to be Google's escape-pod away from outsourced SOC and they have their own in house design and already, "somehow" it can be remotely exploited. So, if Google will be following this approach, one has to wonder how the future of modding will be. Hell, or even the notion of "owning" a device.

Yes you can root and put custom recoveries on A13 for now. No downgrading. I mean come on. Do you think it's going to stop at that? No. It won't. Sometime in the near future--"In the Name of Security", we will only be able to do this stuff on our "older" devices.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks, I'll modify the OP just as soon as I can. Done, thank you!
[Google Pixel 6 Pro] Nergal di Cuthah:
Why are you so agro about rollback, 13 it seems is 12L with minor spitshine. If some mods don't work give it some time and they will. If you didn't want 13 why even load it yet. Sorry to continue the verge from info. Maybe we can go back to working with what we have and not wishing for what, at this early point, we don't .
[Google Pixel 6 Pro] Homeboy76:
Yes, your excellent set of instructions confirmed

my thoughts for editing the flash-all.bat file :)

When I flash the September 2022 Factory Image, I'll edit the flash-all.bat file.

* * * * * * * * * *

@Echo off

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img --slot all

fastboot reboot-bootloader

timeout /t 5 >nul

fastboot flash radio radio-raven-g5123b-102852-220720-b-8851166.img --slot all

fastboot reboot-bootloader

timeout /t 5 >nul

fastboot -- skip-reboot update image-raven-tp1a.220624.021.zip

Note:

I replaced the -w with -- skip-reboot.

fastboot --set-active=other

timeout /t 10 >nul

fastboot reboot-bootloader

timeout /t 5 >nul

fastboot update image-raven-tp1a.220624.021.zip

echo Press any key to exit...

pause >nul

exit

Let the phone, fully, reboot

adb reboot bootloader

Then I'll boot the magisk_patched...img to the active slot.

fastboot boot magisk_patched...img

When Magisk boots I'll do a Direct Install.

Done!
[Google Pixel 6 Pro] :
I'm old fashioned. It's my device. I should be able to do what I please to it. Upgrade/Downgrade. Brick and Unbrick. Repair. Own.
[Google Pixel 6 Pro] Namelesswonder:
A couple issues is that you might need to add a delay after --set-active and will definitely need to add another after the second reboot because these commands will return immediately with the next command being sent and the device may not be ready in that time. The 5 second delay might work, but it might need to be increased. And man, I do not miss batch, pinging the loopback five times and abusing that ping has a default interval of one second all because Windows XP doesn't have timeout? Stupidest hack and it's recommended. Glad on Linux it's just sleep and it's been there since the 90s.
[Google Pixel 6 Pro] badabing2003:
You might want to add one more step

fastboot reboot-bootloader

between flashing the bootloader and the radio, I'm not sure if it is absolutely necessary but Google's flash_all.bat does that, and it would be safer to include that.
[Google Pixel 6 Pro] Namelesswonder:
It is unnecessary, been forgoing it since the Nexus 6P without issue. They can't change the location of the bootloader partitions or radio partitions so there isn't any issue unlike where the other partitions can change with them being removed or added so that's why you need reboot after a bootloader flash but before flashing Android system partitions.
[Google Pixel 6 Pro] Homeboy76:
What second reboot?

I know "batch, pinging the loopback five times" is a PIA.

What did you use in the updated instructions (Post # ?) to show the necessary time delay for windows users?

Good looking out, I edited my file. :)
[Google Pixel 6 Pro] Namelesswonder:
Sorry I meant the third reboot to bootloader.

You can switch out the ping for timeout, as I don't think fastboot works on Windows XP any more, didn't last time I tested in 2017.

What do you mean by showing the time delay? I would just keep with Google's assumption that the device will be ready within 5 seconds.
[Google Pixel 6 Pro] Homeboy76:
Your instructions # 4, 7, 8 (2) read

fastboot reboot bootloader

How would a XDA member with a windows computer know a time delay of n5 or greater is needed after that command?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Look at the phone screen. :)
[Google Pixel 6 Pro] Namelesswonder:
Because my instructions are under the assumption that you're putting them into the command line, not editing the scripts.

I wouldn't extensively modify and use the scripts anyway, as a command that fails will not stop execution and just move on to the next command, potentially putting the device into a bad state from a bad flash.

Whereas if a command fails after you enter it you know to stop and figure out what happened.
[Google Pixel 6 Pro] Homeboy76:
You got me (time for command to complete). :rolleyes: I should have quit when I was ahead. :ROFLMAO:
[Google Pixel 6 Pro] Homeboy76:
You got me too (Command line). :rolleyes: I should have quit when I was ahead. :ROFLMAO:
[Google Pixel 6 Pro] iamjimmy:
Could someone please advise about whether the OTA is flashed to the inactive slot?

Pixel 6 - manually sideloaded Android 13 OTA file using recovery. Assuming this means Android 13 is only on one slot. How do I get it on the other slot?

Pixel 6a - It was new. So I used the Google Flash tool to flash the factory image of Android 13. Assuming that means Android 13 is only on one slot. How do I get it on the other slot?

Thanks for the advice. Just want to make sure I am covered on both my phones.
[Google Pixel 6 Pro] Namelesswonder:
Flashing or installing an OTA always flashes to the inactive slot, and then switches to that slot after it is done.

Android Flash Tool and fastboot without any intervention will only flash to the active slot.

In order to get full coverage after an OTA or basic AFT/fastboot flash just sideload the OTA and you'll be good.
[Google Pixel 6 Pro] iamjimmy:
Thank you so much for the reply.

So for both phones, if I go into recovery and sideload the OTA manually, then I should be good as you said.

Appreciate the info. OTA goes to inactive slot but the Fastboot or flash tool flashes to active slot. Very interesting.

Thanks for all the details in this thread. Much appreciated.
[Google Pixel 6 Pro] HipKat:
OTA Finally came through last night. I haven't done anything with it yet but the fingerprint scanner is marginally faster. Woke up with battery on 28% and have had it on the charger for about an hour, slow charging and the phone doesn't feel warm like it has in the past
[Google Pixel 6 Pro] V0latyle:
It's not necessary, really.

The bootloader, like the boot image, loads from its partition and is active in memory while the device is running in bootloader mode, and it handles all flash commands to device partitions. This means that any changes to the bootloader partitions will not take effect until the next reboot - this would be analogous to live booting a boot image patched with an older version of Magisk, then using a newer version of Magisk to perform Direct Install to the boot image already in /boot.

I believe the radio update takes effect immediately because the device doesn't load radio firmware until system starts.

The way I've always done it is thus:

Update bootloader

Update radio

Reboot to bootloader (which loads the "new" bootloader)

Update system (which will now see the updated bootloader and radio)
[Google Pixel 6 Pro] nutzfreelance:
am i correct in assuming that this boot loader update will break all custom a12 roms out right now? grapheneos. protonAOSP etc ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Those of us who only run stock ROMs would have no way of knowing. You should consult the thread for the particular custom ROM(s) you're using. I can only answer "maybe".

I would also further advise you - just don't flash the Android 13 bootloader until you know for sure about your favorite custom ROMs being able to be used on the Android 13 bootloader.
[Google Pixel 6 Pro] nutzfreelance:
i don't plan to flash android 13 until i know.

honestly i don't plan to flash android 13 for a long time,#1 until i know exactly what issues has google forcing no downgrading the bootloader. #2 there are custom roms that are google free ,#3 android 13 is fully tested by the poor users that are being used as test subjects with their test devices ( never even heard of an android 13 release candidate before this roll out)
[Google Pixel 6 Pro] V0latyle:
I think it would be safe, but no idea whether the custom builds would be stable.

AFAIK the new bootloader doesn't actively prevent anything from running; it doesn't care what's in /boot or /system, it just does its job and loads the boot image at startup. So, if you already have a custom ROM installed, and update the bootloader, the only thing that might happen is instability. Further, without booting the stock Android 13 build, the rollback counter is not incremented.

The one thing it does do, as we have established, is increment the rollback counter once Android 13 is booted, preventing the bootloader itself from being rolled back.

The only thing that stops an older Android build from being flashed on the new bootloader is the update image's version checks, which can be bypassed with --force. Assuming a custom ROM doesn't require a specific bootloader or radio version, nothing should prevent it from flashing on the new bootloader.
[Google Pixel 6 Pro] :
Totally agree.

I'm still on A11 on my 4a5g,lol. I might get a 6a but that's staying on A12 (or 13 Beta since I think you can rollback safely on that). From various 6x threads I think I read people trying to flash everything but A13 bootloader, which is smart-esp for testing--I applaud those efforts. Unfortunately it seems some of those apps (browsers, etc) don't like the A13 system + old BL version that and will crash. This is all very good info to know. And to those who are guinea pigs, I salute you.

Anyone know if new-in-box Pixel phones ALWAYS come in the released Android version? In other words, the Pixel 6 was released with Android 12. Android 13 is now out. Google (Foxconn) still makes the 6a. Are those units that are/will be manuactured be released on Android 12 or will they be manuactured with the Android 13 build?
[Google Pixel 6 Pro] nutzfreelance:
if i read that right, i CAN update the bootloader and as long as i NEVER boot android 13, I CAN STILL downgrade the bootloader?

which would be good for testing.
[Google Pixel 6 Pro] Namelesswonder:
No, because Android 12 doesn't function properly on the Android 13 bootloader. It'll boot but things are broken. Either stay on Android 12 or completely upgrade to Android 13, don't mix and match.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I would expect that the 6A comes with Android 12, but you better be quick if you get one, to not let it update to 13. The Pixel 7 will probably be the first phone to be released with Android 13 as it's first Android version.