yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] :
after you do that. I wonder if you can edit /fstab to make sure it never boots.

Yeah I figured I had until Sept 24th or so to get one. Unless you meant it doing it's sneaky OTA. Oh yea. That thing's going in airplane mode so it wont update on me. And after rooting/custom recovery 1st thing I'm doing is a dd partition dump (mainly for EFS backup) and general backup of as original state as possible. I bought a (another) 4a5g that I'll use as a trade in for a 6a. Provided they don't stop the tradein/amounts in the next month or so. Fine print seemed to indicate Sept 24th? so hopefully I'll be ok/within timeframe.
[Google Pixel 6 Pro] Namelesswonder:
Pixel 6 / 6 Pro are most likely no longer being manufactured or are about to leave production this month, as the Pixel 7 should be entering mass production now. Any unopened Pixel 6 / 6 Pro will only come with Android 12, as usually the firmware that is being loaded onto the device is only changed out every few months or so. They have to validate the firmware to make sure they aren't producing thousands of phones that don't work properly. My Pixel 6 Pro was manufactured sometime in December but still had the original firmware that units produced before launch had.

The Pixel 6A for the next few months should have Android 12 until the supply chain depletes and ones with Android 13 preinstalled begin filling up the supply.
[Google Pixel 6 Pro] :
Thank you! Appreciate it!

that /fstab comment was in error. I don't think uses /fstab and when I wrote that I forgot that I wrote it and that it was just there when I posted. opps.
[Google Pixel 6 Pro] nutzfreelance:
so if i wanted to develop an android 12 that works on the android 13 boot loader..

DONT. JUST STOP IT RIGHT NOW!!!!!!!

????

that seems a bit wrong. for a device that is used a lot for testing.
[Google Pixel 6 Pro] Namelesswonder:
Well if you know what you're doing then go ahead.

But most people don't know what they're doing so it's best to tell them to not try so they don't end up breaking something.

You're free to go experiment on your own accord.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ninja'd again. :D

Please don't use all capitals. :)

You can do whatever you want with your device. You were asking questions and we answered.
[Google Pixel 6 Pro] :
It's like Verizon charging an additional $12 maintenance charge on older plans (I got 999gb w/ rollover on old 2gb plan) to get people to unlimited. And they will prob keep increasing it to get me to go to the slower tier. A company has an inherent right to change things. You may like it. You may not. (you know where I stand). But in the end a company isn't duty bound or required make things accessible to the user. You do have the right to reverse engineer, however.

Here Google is making an adament stand, for security reasons. And yes making it harder for devs/modders/tinkerer's/the curious, etc. It's their phone, their design, their patents. But that doesn't mean we arn't allowed to try to evade it. A forever cat and mouse game.
[Google Pixel 6 Pro] whatsisnametake2:
has this been confirmed? the last 13 beta has no ARB?
[Google Pixel 6 Pro] :
I cannot confirm it. But I thought I saw posts in one of the 6x threads that you can "easily" roll back to android 12 from beta 13. Having ARB on a beta would be kinda counter-intuitive since beta in nature is testing. And to have test subjects on a one way experimental trip would be insane. Only the US Military would be so dumb..lol (and they have. you can "volunteer" for experiemental injections, but beside the point..lol).
[Google Pixel 6 Pro] V0latyle:
Potentially, because Android 12 won't trigger the anti-rollback.

Eh...Limiting in a sense that the only way is forward, but as most devs are generally focused on porting the cutting edge, I don't think this will be much of a problem in practice
[Google Pixel 6 Pro] nutzfreelance:
is there any known issues with running android 12 on the android 13 boot loader and never booting android 13?

any issues running android 13 on the android 12 bootloader?

( as i recall there never used to be an issue with running any android with a newer bootloader, i recall running android 6 7 and 8.1 on a bootloader that came with android 8)
[Google Pixel 6 Pro] Nergal di Cuthah:
I believe this is the DRM crashes spoken of earlier
[Google Pixel 6 Pro] nutzfreelance:
it would be interesting to know what would happen if DRM was disabled.

I dont support DRM and for me that would be a good thing.
[Google Pixel 6 Pro] V0latyle:
Someone, I forget who, tested this, but not extensively, so stability is unknown.

As yet untested and unknown. Feel free to try.

Generally no...although there's a reason why updated builds specify a particular bootloader version.
[Google Pixel 6 Pro] Namelesswonder:
Yes, I tested it and there are several issues that prevent it from being daily driven. Potentially more issues may be discovered.

Alternate APEXs can be installed and have the ability to be pinned to a specified version. This might have some potential to be used, but I don't know if will be applicable to user builds, as the documentation on APEXs alludes to userdebug or engdebug being required to do modifications to them, along with the build explicitly requiring configuration to be able to, which user builds won't. There's also the question of whether Android would even work without the media DRM library since it's becoming more relied on in day to day use.

Someone has actually unintentionally tested Android 13 on the Android 12 bootloader.

https://xdaforums.com/t/has-anyone-...bootloader-i-have-tried.4481347/post-87312899

They didn't realize that they had to update their bootloader when they built AOSP on android-13.0.0_r2, so they were still using their April bootloader. The fact they didn't brick is interesting.

Apparently for them they don't have the same crashes that Android 12 on Android 13 bootloader has, but the fingerprint sensor HAL does appear nonfunctional. Can't recommend people still on Android 12 go out and try this unless they understand the possibility of making their phone a brick.
[Google Pixel 6 Pro] V0latyle:
The thing is, bootloader generally doesn't care what's in /boot or /system, so if system fails to boot, bootloader will remain accessible. The only way bootloader gets screwed up is if somehow flashed with a corrupt image, or, as is the case here with the Pixel 6, the anti rollback counter prevents it from starting. So, I honestly think trying to flash Android 13 on the 12 bootloader only really risks a data wipe.

I don't consider a device "bricked" until one is unable to access bootloader whatsoever, because the tools necessary to get the device back to a functional state using the bootloader are available to everyone. Technically, EDL/QPST mode isn't a brick either, but since the tools aren't readily available to the general public, it might as well be.
[Google Pixel 6 Pro] Namelesswonder:
But Android 13 when it does successfully boot will then attempt to increment the anti-rollback counter. We know that the July Android 12 bootloader is able to recognize this incremented counter and will refuse to boot. The entire bricking situation is because if the Android 13 slot becomes unbootable and the phone tries switching to the slot with the Android 12 bootloader it bails out of booting it and bricks.

I don't know why his phone didn't have this issue and wasn't bricked, maybe it has something to do with the mystery second July update? Maybe that was the starting point for Google adding in the counter check and appropriate firmware to allow setting the counter? Maybe it was sometime between May to the first July update? Don't know, all we know is that we have people with bricked devices that are from a stale Android 12 slot and Google has acknowledged this, and we have someone with a device on the April Android 12 bootloader that has used Android 13 without bricking.

But someone in this situation of recent Android 12 bootloaders on their device booting Android 13 could end up in this situation of their phone becoming unusable.
[Google Pixel 6 Pro] V0latyle:
So if I understand you correctly, you believe the Android 12 bootloader might still have the anti-rollback capability, and if Android 13 is booted, this could increment the counter even without the updated bootloader, thereby rendering the device a brick?
[Google Pixel 6 Pro] Namelesswonder:
That's what Google makes it sound like on the factory image page.

Google is using the anti-rollback counter as a versioning scheme. The old bootloaders maybe are expecting a 0 or another number on the counter, however it has now been set to 1 or something else by Android 13, so they won't boot because they are outdated. The newer bootloader won't let you flash the older bootloader because it requires the counter to be 0. These older bootloaders have the check but may or may not have the capability to advance the counter. I would love to be able to verify if this is truly the case, but the bootloaders are closed source, so the only way to verify is to put at minimum $449 on the line.
[Google Pixel 6 Pro] :
Since all the other official apps/binaries are built on a framework, trust, etc.,I think it would fundamentally alter the operation of the OS. We are seeing that with how some apps don't seem to like being on an older bootloader but are running a newer OS--things you wouldn't think would matter regarding the BL version, like in the old days, but do now matter since seems eerything more intertwined and innerdependant. You would prob have to be running DRM free android, built and compiled from scratch. But even ROMs run on top of the underlying OS, so unless one is able to get around that, I really don't know if it will be possible. Give it time. I'm sure we'll know more as this plays out.

I don't like DRM either. I've never bought any song off any itunes/similar. And I never will. Ironiclly enough, the last music I ever purchased was around 2002. I bought a CD of System of a Down's album "Steal this Album". Last movie I bought was at Costco around same time. A copy of Patton starring George C. Scott. It was next to the socks for sale and it caught my eye.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Namelesswonder I agree.

And welcome to wall of text anonymous. I'm not the founder but definitely a member. 😁

The detail and breakdown is awesome.
[Google Pixel 6 Pro] Lughnasadh:
The just released Magisk Canary 25202 working fine on A13.
[Google Pixel 6 Pro] drpudding:
Where's the info on said vulnerability? I don't see it anywhere

I assumed that would be the only thing to make Google take such a drastic step like blowing a fuse to prevent downgrade attacks. I might keep my pixel on the older bootloader to check out what said vulnerability is for research purposes 🧐 since my pixel isn't my main phone and I like tinkering with it
[Google Pixel 6 Pro] Ghisy:
Which app do you use to calibrate your display (with root)? I use EX Kernel Manager on my P4XL but, on my P6P, the Kirisakura kernel doesn't support color calibration.

I installed CF Lumen but I also want to adjust the contrast and saturation of my display. Any recommendation?
[Google Pixel 6 Pro] HipKat:
I wouldn't say that you're missing much. So far, even looking up A13 Features shows this is a very, very small change from A12. The location of Power/Menu buttons, the way cards are used and updates to the media player are hardly ground-shaking. The fingerprint scanner does work faster, though.

Battery life still sucks and Cell signal is still weak. Android should take some of the WeBoost technology and apply some of it their devices
[Google Pixel 6 Pro] HipKat:
Same, I can't think of the last purchased music. For me, that has to be sometime in the 90s. I did pay to watch a movie that my kid wanted to see that I couldn't find in "other" ways
[Google Pixel 6 Pro] whatsisnametake2:
so do we know whether android 13 beta 4 had this ARB? if not seems like that may be the best way to test ride 13 before committing.
[Google Pixel 6 Pro] bush911:
It would be great to think carefully before updating to Android 13. I updated then force downgraded.

Now it seems that I am so far suffering: web browsers keeping closing themselves within minutes, audio playing always no sound, SMS reception delaying hours, automatically dark theme not work
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, it's a known consequence of trying to downgrade now.
[Google Pixel 6 Pro] Dave Lister:
Is it "--slot all", "--slot=all" as V0latyle put in https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356231/post-87293009, or does it not matter??
[Google Pixel 6 Pro] Lughnasadh:
Either one should work..
[Google Pixel 6 Pro] Dave Lister:
Thanks. That's what I thought, but better safe than sorry!
[Google Pixel 6 Pro] V0latyle:
Apparently this doesn't seem to work properly on the Tensor devices. If it doesn't, simply flash the bootloader twice and use the --slot=other argument the second time.

Alternatively, I believe you can flash each partition by itself:

fastboot flash bootloader_a <bootloader image>

fastboot flash bootloader_b <bootloader image>

fastboot reboot bootloader
[Google Pixel 6 Pro] Lughnasadh:
I thought the --slot all or --slot=all arguments didn't work only when flashing the whole factory image on the Pixel 6 series? They don't work when only flashing the bootloader?
[Google Pixel 6 Pro] Lughnasadh:
Just wondering how flashing the bootloader to both slots worked out for you? Also curious if you used --slot all or --slot=all? Thanks.
[Google Pixel 6 Pro] V0latyle:
Oh I may have missed that.
[Google Pixel 6 Pro] Dave Lister:
I used --slot=all, and the console output from fastboot showed it writing to both bootloader_a and bootloader_b. I should have thought to copy it or take a screenshot, but it should be easy enough for anyone to run just that command to verify.
[Google Pixel 6 Pro] Lughnasadh:
Awesome! Thanks for the info 👍
[Google Pixel 6 Pro] roirraW "edor" ehT:
Platform Tools has been updated slightly to v33.0.3:

Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip

No release notes yet (would be here https://developer.android.com/studio/releases/platform-tools).
[Google Pixel 6 Pro] cmh714:
Interesting since its not up on the site yet..... https://developer.android.com/studio/releases/platform-tools

OK so the webpage wasnt updated properly, but the links do get the latest update.....
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm pretty sure when 33.0.2 was released, the release notes were delayed as well. But who knows, with my memory. :)
[Google Pixel 6 Pro] Lughnasadh:
And as you mentioned, they'll even update/alter release notes even when not updating to a new version, so who knows with them, lol.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Maybe Google should be renamed Loki.
[Google Pixel 6 Pro] LLStarks:
I wouldn't be surprised if the tools are being adjusted to account for ARB.
[Google Pixel 6 Pro] roirraW "edor" ehT:
My suspicion too. I'm waiting like Gollum for the precious release notes.
[Google Pixel 6 Pro] proac:
thanks
[Google Pixel 6 Pro] Lughnasadh:
Newly released Magisk Canary 25203 working fine on A13.

Changelog:

- Update app to target API 33
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://developer.android.com/studio/releases/platform-tools​

​

33.0.3 (Aug 2022)​

adb

Don't retry adb root if first attempt failed.

Fix track-devices duplicate entry.

Add receive windowing (increase throughput on high-latency connections).

More specific error messages in the "more than one device" failure cases.

Reject unexpected reverse forward requests.

Fix install-multi-package on Windows.

fastboot

Remove e2fsdroid as part of SDK platform-tools.

Print OemCmdHandler return message on success.
[Google Pixel 6 Pro] Taker18:
Can I flash Android 13 again with Android Flash Tools from Google ? Or is there anything special I need to do before ?

I Updated from A12 to Android 13 with OTA.
[Google Pixel 6 Pro] Lughnasadh:
I mean, you can if you want. Not sure what the purpose would be unless you want to clean flash. However, before you do anything you should flash the bootloader, at a minimum, to the other slot (preferable you flash the full OTA though). You still have A12 one 1 slot and after flashing A13 again with Android Flash Tool you'll still have A12 on one slot since you'll be updating the slot you already flashed A13.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes.

No.

If you plan on wiping data, have everything backed up you want to keep. If you don't plan on wiping data, then make sure you have Wipe Data and Force Flash All Partitions both unchecked.

In all cases, make sure Lock Bootloader is unchecked.
[Google Pixel 6 Pro] Taker18:
okay, but I can also just side load the OTA in recovery mode, so I get the other slot active right ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
There are several ways to get the update onto the other slot. There are some instructions in the OP. I don't do the OTA method ever, so I just never recommend something that I don't do myself. I always use the factory image, and the one time I had some particular problem that the factory image didn't solve, I used the Android Flash Tool.
[Google Pixel 6 Pro] Lughnasadh:
He should really flash the A13 bootloader to the other slot, at a minimum (flashing full OTA is preferable) because he still has A12 on his inactive slot. I wouldn't be flashing anything until I had the A13 bootloader on both slots, including using Android Flash Tool. Maybe I'm missing something here???
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, I don't think you're missing anything. I agree, I like having the 13 Stable bootloader on both slots first too, but no matter which method of updating the other slot is used, @Taker18 should be fine.

I didn't update my second slot at all until the day after I put Android 13 on my current (at the time) slot. When I did manually switch to the second slot the next day, I then just used the flash-all.bat again. Unless you think I was just lucky and you think there's a risk there, but since the very first step of the flash-all.bat is to flash the bootloader, I think it's fine.

If you recommend the OTA method instead, I have no particular advice against it. I just don't suggest others use any method that I don't personally do, since I don't keep up with the method, caveats, et cetera. But coming from someone who does use that method is something else.
[Google Pixel 6 Pro] Lughnasadh:
The thing is, when that person uses Android Flash Tool that person is just going to be flashing A13 on his current slot, which is already 13. He still has an inactive slot with A12 on it and using the Android Flash Tool isn't going to update that inactive slot to A13 unless he specifically switches slots beforehand.

If they are trying to use Android Flash Tool to flash A13 to the inactive slot with A12 on it, it's not going work because Android Flash Tool will be using his active slot, not his inactive slot, to flash A13 on. And his active slot is already A13.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I agree. That's one of the reasons I pointed to the instructions in the OP.
[Google Pixel 6 Pro] Lughnasadh:
It was just confusing because it seemed like that person was trying to update his inactive slot with A12 on it to A13 using Android Flash Tool and that just isn't going to work unless he specifically switches slots beforehand so he's flashing on his A12 slot. He'd just be updated the same A13 slot, lol.

Anyway, carry on 🤪
[Google Pixel 6 Pro] Taker18:
The Sideload option isn't working because I dont get the command

adb reboot fastboot

fastboot getvar current-slot

is not working. idk why ...

At a minimum, do this first: fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img (or change the name of the bootloader file to the one for your device if not Pixel 6 Pro), then you *should* be much safer than without doing that first.

so I only need to do this command right?

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

thats it?

sry, but my English isn't the best so im not able too understand it to 100%
[Google Pixel 6 Pro] roirraW "edor" ehT:
adb reboot bootloader

not

adb reboot fastboot

and then, yes:

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

is all that's needed to be "safe".

But again, I don't deal with the OTA method, only the factory image.

@Lughnasadh?

Disregard, I think.
[Google Pixel 6 Pro] Namelesswonder:
You're booting into userspace fastbootd, if you want to sideload then you need to

adb reboot sideload to reboot directly into the sideloading part of the recovery, or adb reboot recovery to just boot into the base of the recovery to then select the sideload option.

And as what @roirraW "edor" ehT says you need to be in fastboot mode properly to flash the bootloaders, as userspace fastbootd can't flash the bootloader.
[Google Pixel 6 Pro] Taker18:
and after this, what' I need to do? I now have A13 on both slots right ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
After that, you have the Android 13 bootloader on both slots. You only have Android 13 ROM on one slot, but that's 100% okay and normal. Just don't change slots manually. Once you have the 13 bootloader on both slots, you are "safe". Just reboot as normal to boot into the Android 13 you were already using. You're done.
[Google Pixel 6 Pro] Taker18:
anybody knows why I can perform: fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img

says every time: command Faltboot cannot be found ... but I have installed everything
[Google Pixel 6 Pro] Nergal di Cuthah:
Are you command prompting in the platform tools folder
[Google Pixel 6 Pro] roirraW "edor" ehT:
Got everything in the same folder? You have the bootloader-raven-slider-1.2-8739948.img in the same folder with adb and fastboot? You did:

adb reboot bootloader

correct?

The screen does not show fastbootd, correct?

Can you copy and paste the error when you try the command(s)? Start with the "adb reboot bootloader" - show us the complete output if you don't mind.

You got the VERY latest Platform Tools (has been updated to v33.0.3 just yesterday)?

Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
[Google Pixel 6 Pro] Lughnasadh:
Does everything include this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
And to add, install the driver not just when the phone is running, but also when it's in Bootloader. If you install the driver while Android is up and running, that won't help when you're in Bootloader.

Edit: Also, you definitely have a Pixel 6 Pro (Raven), correct? If not, the filename of the bootloader.img has to match the correct one from the Android 13 firmware zip that's provided for your particular Pixel. And for that matter, you downloaded the correct firmware zip for your particular Pixel as well?
[Google Pixel 6 Pro] Nergal di Cuthah:
I assume that's a typo on the forum but just incase is it saying exactly this. Could you provide either a copy paste of your commandline or a screenshot
[Google Pixel 6 Pro] Taker18:
Now:

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb reboot bootloader

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img

< waiting for any device >

nothing happens ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You installed the USB driver @Lughnasadh pointed you to a few posts up (while you're in bootloader)? Because if not, then this is what you'd see.

Otherwise, try a different USB port, a different USB cable, try rebooting the PC.
[Google Pixel 6 Pro] Taker18:
can I try to reboot the phone ?
[Google Pixel 6 Pro] Lughnasadh:
Universal Adb Driver??? Are you using Platform Tools as @roirraW "edor" ehT suggested?