yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
I believe you're referring to this.

But in my tests, which I reported here I was able to flash May OTA on Pixel 5 while I was on June, so it didn't block me.

Perhaps the blocking is only for different OS versions.

In any case, although flashing older OTA flashed fine, I was not able to boot to it.
[Google Pixel 6] badabing2003:
Is this still the case for Pixel 7 series?

If yes, then there really no case of a required wipe, right?
[Google Pixel 6] V0latyle:
I'm not talking about flashing, I'm talking about booting an older slot. So as you experienced, because you'd already booted into June, the system refused to boot into May because it's an older version and you'd already had a successful boot into June, hence anti-rollback in a sense.
[Google Pixel 6] Lughnasadh:
For the Pixel 7 series, both flags require disabling, unfortunately. As far as I know, no one has found a workaround.
[Google Pixel 6] Freak07:
Nothing to do with the boot image header.

the problem is vendor_dlkm, which is part of the kernel (vendor kernel modules go there) and that's avb checked also on unlocked bootloader.

P6 series allows patching vbmeta image on the fly while flashing kernel so the expected hashes match again.

Same approach on P7 still requires a wipe after patching vbmeta. So for the end user nothing is gained.
[Google Pixel 6] V0latyle:
Gotcha, thanks for clearing this up
[Google Pixel 6] badabing2003:
New Release:

June 16, 2003 v5.3.1.2 release

Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.

Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.

Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.

Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.

Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
[Google Pixel 6] bush911:
I would like to report back:

Just finished updating my Pixel 6 to latest update using this new release together with platform 33.03 and Magisk 26.1.

Everything is fine. Hats off to the developer 💯
[Google Pixel 6] Galaxea:
I wanted to use this tool to move from the beta programme back to stock, so I selected "full-wipe" as I have always read that this is a requirement. The tool ran successfully and a few seconds later I was on the latest stock version and everything else was the same (all apps still there and nothing else changed except the Android version).

Is this possible??
[Google Pixel 6] badabing2003:
If you provide a support file and I can check what went on
[Google Pixel 6] Galaxea:
I still have the tool open, so please advise how to extract the log, etc. that you need.
[Google Pixel 6] Galaxea:
I have the log files. How do I get them to you?
[Google Pixel 6] badabing2003:
Press the big support button, or do it from the help menu.
[Google Pixel 6] Galaxea:
Submitted
[Google Pixel 6] badabing2003:
They are not submitted to me, they are generated locally.

You have to attach here so that I get them.

By the way, sensitive data is automatically redacted when generating support file.
[Google Pixel 6] Galaxea:
The other one I submitted on GitHub, but here it is.
[Google Pixel 6] badabing2003:
As pointed out in Github, and for the benefit of others.

You're using Android Platform-Tools 34.0.3-10161052

Switch to 33.0.3 and you should be fine.

You can blame Google for that.
[Google Pixel 6] Galaxea:
It is great not having to do a full wipe when moving from beta to stock, I just thought the tool might have been the issue. Thanks for the update. This is a really great tool by the way.
[Google Pixel 6] badabing2003:
You could have just chosen to Keep Data

The wipe is enforced by OTA, you chose firmware update, and as far as the phone is concerned it just flashed the partitions.

The fact that you asked for wipe but it didn't perform the wipe is a bug.

There is no guarantee that your apps / system would work smoothly after a downgrade, that is why OTA enforces wipe.
[Google Pixel 6] badabing2003:
New Release:

June 21, 2023 v5.3.2.0 release

Added support for Pixel tablet (tangorpro).

For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.

Disable Patch buttons if device is not in adb mode.

Reboot to system after lock / unlock bootloader if No Reboot option is not selected.

Increase sleep after reboots to various modes to assure that slow devices have time to be detected.

Updated Readme and screenshots.

Minor improvements and bug fixes.
[Google Pixel 6] badabing2003:
New Release:

June 23, 2023 v5.3.3.0 release

#79 Bug-fix: Package Manager column stays unsorted when filtered.

Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.

Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3

Package manager bug fixes and improvements.
[Google Pixel 6] badabing2003:
New Release:

July 03, 2023 v5.4.0.0 release

Add Pixel Fold (Felix)

Add sorting capability to boot list.

Add warning about Magisk a8c4a33e:26103

Improved auto-resize of boot columns.

Improved internal DB management.

Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.

Improved tracking the origin of a patched image.

Display Kernel version as part of device details

Refresh package manager list when packages are updated to reflect the changes.

Miscellaneous other improvements.

Update Readme.
[Google Pixel 6] tom1807:
Pixel 6, flashed with PF 5.4.0.0. Al;l went smooth.

One question though, previous flash took around 4 minutes, now all is done under 3 minutes since the June update.

Optimization of PF? (Not that I am complaining, it's just awesome)

Cheers

Tom
[Google Pixel 6] XGX5309:
This tool kinda saved me, so thank you for taking the time to make it!!

My experience with my Pixel 6 has been nothing short of making me want to pull my hair out. None of the tools would even recognize or admit there was even a partition structure. This tool allowed me to flash something that I still don't understand how it sent the command when it wasn't in fastbootD. I do not understand the command it sent to actually get through to the device and flash dtbo and vendor_image. It did. Which helped immensely.

So now I have TOTAL control over my Pixel. 🥹

Thank you @badabing2003 - I really am going to scrape that Git and understand what you did there. Everything Android has changed since I was developing until Android 10, then I got an iPhone. So, I have a little homework. Hah
[Google Pixel 6] badabing2003:
Welcome back to the good side :)

As much as I would like to take credit for PF doing magic, that is not the case :)

Anything PF does, it can be done manually, which is basically what the app is, performing the sequence of the steps one would otherwise do it manually.

Without seeing your logs, if I had to take a guess based on your explanation, you seem to have had an issue getting your phone into userspace fastboot (fastbootd) and hence was not able to flash dtbo / vendor ...

By any chance are on MAC ? M1?

You probably were using Android platform tools 33 before and with PF you used version 34.

To understand why 34 would work but not 33, that's because with 34 fastbootd is not needed.

An excellent technical explanation is provided by @Namelesswonder. See this post.
[Google Pixel 6] XGX5309:
Ahhhhhhh. Thank you.

I know the app is a kinda UI/UX wrapper for explicit adb/fasboot commands, but even with that known the commands themselves have changed. Like the fastboot flashing command. It used to be simply fastboot flash.

So I really just need to relearn all my adb/fb commands. I've been out of the game for a while. Google really pissed me off with their devices at that time so I went for the iPhones because of the simply insane build quality and general quality, but best believe I paid for it. $1600 512GB 13 Pro Max and a few before it. I basically side-eyed eBay until I found a steal of a brand new P6 that hadn't even been booted or registered or anything for less than $200. I jumped on it. I thought I had to. Too good a price. I do still use the iPhone as my main phone but the pixel 6 is rapidly approaching daily driver as I know have full control over it. Your tool or by extension the person that may have helped or team, has done an amazing job with this. I fully expect to be using my pixel as my daily driver very soon and ditch the iPhone because the pixel 6 that I found is actually 256 GB. Basically a steal of a deal.
[Google Pixel 6] badabing2003:
Yep, you got a steal of a deal, good for you.

You can inspect the pixelFlasher logs or the console output, if you set the verbose flag you even get the full command details, which would help you quickly learn what you forgot.

As for the big team, it's me, myself and I, we work well together and compliment each other ;)
[Google Pixel 6] XGX5309:
Good guy and good on you. A lot of people don't quite get the thanks for their time and talent for free thing.

The GIT, once I fork and dig through it, I'd be happy to push some things over to you if I see anything or maybe a worthwhile addition, and offer all the help I can. I would be happy to help with this once I am up to date.

I've been working on a tool to very easily flash LineageOS to the Pixel 6/Pro so that the process of moving back and forth from complete control or all locked and very secure Google signed OS with a locked bootloader. Still working on that locally though. VS project atm.
[Google Pixel 6] badabing2003:
Other than few odd ones here and there who expect everything handed to them on a platter and still complain, most XDA members are courteous, appreciative and supportive.
[Google Pixel 6] badabing2003:
New Release:

July 13, 2023 v5.5.0.0 release

Added a patch method Other Magisk App to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.

UI improvements

Added Kill Application in Package Manager.

Added Clear Application Data in Package Manager.

Now that Full OTA flashing is the preferred method, added a direct link to the device's full OTA download page from Google.

While flashing, disable the Flash Pixel Phone button to avoid accidental clicking.

Improved root detection.

Bug fixes and other improvements.
[Google Pixel 6] badabing2003:
Bug Fix Release:

July 14, 2023 v5.5.1.0 release

Bug fix #85 Can't enable/disable Advanced option in v5.5.0

A little improvement #84 UI elements not optimized for monitors with low screen resolution
[Google Pixel 6] kiwigi:
Nice...I hope you won't drop the factory image users:)
[Google Pixel 6] badabing2003:
New Release:

July 16, 2023 v5.5.1.1 release

#84, further UI improvements for smaller screens.

Better dark mode handling for MacOS and Linux.

#86, improved handling of space characters in paths.
[Google Pixel 6] mangurian:
Hello. Where can I learn what I gain by rooting my Pixel 6? Thanks,
[Google Pixel 6] XGX5309:
LOTS. What do you want it to gain is the question. Once you have full control over the hardware, it's up to to your heart's desire.
[Google Pixel 6] pndwal:
Guess you mean the various boot images in both slots are compatible with B/L... No part of B/L is in any dual partition AFAIK... only one version of B/L is installed...

Boot image sets (a or b) will often become incompatible with a newer B/L, so must be supported by the current B/L. However I'm pretty sure there's only ever one B/L version...

🤠 PW
[Google Pixel 6] badabing2003:
There are indeed two bootloaders. a and b

See my response here

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88822001
[Google Pixel 6] a_bug:
Hey, smart Pixel People. I just used PixelFlasher to update to the July update.

Everything appeared to work great. The phone rebooted. I was able to get in and stuff. And then a few moments later the phone appeared to reboot and get stuck in a Recovery page. I get the following message:

Android Recovery

google/oriole/oriole

13/TQ3a.230705.001/10216780

user/release-keys

(in red):

Cannot load Android system. Your Data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

I then choose the 'Try again' option. The phone boots into the system for a few moments then shuts off again bringing me back to the above.

Any thoughts or additional information I can provide?

Thank you,

A (freaked) Bug :eek:

Okay, so I have an update.

Things appear to be working now.

I'm not sure if it was going through the entire process from the beginning again (reprocessing the Full OTA) or that I (may have) changed the Boot slot to A (I didn't note if that was the primary slot or not).

Regardless everything seems to be working, except the loss of root. I expect I can figure out how to get that back again.

I would like to know what I may have done wrong in the first place as I expect I'll be going through this process again.

A (relived) Bug
[Google Pixel 6] badabing2003:
If you provide a support file, I can take a look at it and see if I can find out what might have happened.
[Google Pixel 6] a_bug:
I've attached a support file.

Thank you in advance.

A Bug :)
[Google Pixel 6] badabing2003:
What's your current state,

I looked at your support file and I don't see anything obvious that would indicate an issue.

Let me know your current state and we'll take steps to get you where you want to go.
[Google Pixel 6] badabing2003:
New Release:

Aug 07, 2023 v5.6.0.0 release

Added configurable toolbar.

Added device controls buttons to the menu.

Added feature to Magisk Manager, ability to install modules from the PC.

After flashing OTA, detect if the slot switched as expected, if it didn't, skip patched boot flashing (if selected).

Added feature to Package Manager to be able to manage (add, remove, list) Magisk denylist.

Added export csv formatted package list feature.

When sanitizing DB, wipe write-ahead logs (WAL) for better privacy.

Under the hood optimizations.

Verity / Verification status check.

Counter in package manager.

Added a quick link to Android security and update bulletins.
[Google Pixel 6] badabing2003:
New Release:

Aug 09, 2023 v5.7.0.0 release

Rework the settings window: code refactoring and bug fixes.

Bug Fix: In some cases log files were not saved.

Bug Fix: Custom font size changes were not always applied.

When getting device details, get battery details.

Don't set ASH_STANDALONE=1 when using busybox, it encounters selinux related issue.

Extra check to make sure the created patch is not zero bytes long.
[Google Pixel 6] badabing2003:
New Release:

Aug 13, 2023 v5.7.1.0 release

Print available memory when starting PixelFlasher.

Option to sacrifice speed in favor of using less memory (used when processing large firmware files, turn it on only if you run into out of memory errors).
[Google Pixel 6] badabing2003:
New Release:

Aug 15, 2023 v5.7.2.0 release

Regression Bug fix: Refresh UI to display / hide flash options after changing advanced settings.

Use Python 3.11 instead of 3.10
[Google Pixel 6] badabing2003:
New Release:

Sep 19, 2023 v5.8.0.0 release

Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.

Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.

For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.

Added a button to reboot to userspace fastboot (fastbootd).

Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)

When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.

On Linux, display a message when terminal app is not set and open shell feature is used.

For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.

Miscellaneous fixes and improvements.
[Google Pixel 6] longbottle:
Hello! I'm having an issue with PixelFlasher and the factory image for my Pixel 6. I am on a Mac using Mac OS 10.13.6. I have triple-checked that I was getting the right factory image for the version on the device, and I freshly downloaded the latest platform tools. I have Android 13 installed on the device and fully updated, and this is the numbers-matching image. Both version 5.8.0.0 and 5.7.2.0 of PixelFlasher throw this following error when I try to process the factory image:

==============================================================================

Detected Pixel firmware

7-Zip (z) 21.07 (x64) : Copyright (c) 1999-2021 Igor Pavlov : 2021-12-26

64-bit locale=en_US.UTF-8 Threads:8

Scanning the drive for archives:

1 file, 2467969845 bytes (2354 MiB)

Extracting archive: /Users/longbottle/Downloads/oriole-tq3a.230805.001-factory-18133fe9.zip

dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin

Referenced from: /var/folders/dv/n8b1ff2s0kj66ccczk6nct0w0000gn/T/_MEIq8dIWO/bin/7zz (which was built for Mac OS X 11.3)

Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: ____chkstk_darwin

Referenced from: /var/folders/dv/n8b1ff2s0kj66ccczk6nct0w0000gn/T/_MEIq8dIWO/bin/7zz (which was built for Mac OS X 11.3)

Expected in: /usr/lib/libSystem.B.dylib

2023-09-20 05:48:30 ERROR: The firmware file did not have the expected structure / contents.

Please check /Users/longbottle/Downloads/oriole-tq3a.230805.001-factory-18133fe9.zip to make sure it is a valid factory image file.

Aborting ...
[Google Pixel 6] badabing2003:
Please generate a support file in PixelFlasher and provide that.
[Google Pixel 6] longbottle:
You got it! Thank you!
[Google Pixel 6] daveybfilms:
Will this flash Magisk into the original factory image, or is that something that I would have to do seperate? I have my OEM Unlocked, so wondering if this will make it easier.

thanks.
[Google Pixel 6] badabing2003:
I'm not sure if I understand your question.

You have OEM unlocked

Do you have Magisk already installed? rooted? or you're just starting?

See this table, depending on your current state, the tool will either do everything for you automatically, or guide you through it.
[Google Pixel 6] daveybfilms:
Just OEM unlocked, no Magisk or root.
[Google Pixel 6] badabing2003:
Make sure the bootloader is unlocked (check guides linked in op)

Install magisk canary on your phone, set the channel to canary.

run PixelFlasher

choose, firmware, platform tools, phone

select patch boot.img, and prepare package. (the tool will launch Magisk and guide you through it) and will do the rest to prepare a package.

choose Keep Data or Wipe Data (your choice) (you can first test with dry run)

Flash

The phone should be rooted at this point, proceed to install magisk modules of your choice.
[Google Pixel 6] daveybfilms:
thanks for the info, i'm in fastboot mode but it's saying my device state is locked. any reason why?
[Google Pixel 6] daveybfilms:
Also for some reason it's saying the factory image is invalid, but i managed to get it off the Google Site. should I download the flash or OTA version? if that makes a difference.
[Google Pixel 6] badabing2003:
You have to download from here for your appropriate device and click on the part that says LINK which is the factory image.

Sounds like you have not unlocked your bootloader.

Have you followed either of these two excellent guides?

https://xdaforums.com/t/guide-root-pixel-6-android-12-with-magisk.4388733/

Part II - INSTRUCTIONS / Unlock Bootloader/Return Phone to Stock/Lock Bootloader

or

https://xdaforums.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/

Unlock Bootloader
[Google Pixel 6] daveybfilms:
The OEM Bootloader has been unlocked by T-Mobile, but i cannot flash any of the patched img's. which of the following would you consider to be the easiest to do? i haven't rooted a phone in years.
[Google Pixel 6] badabing2003:
While in fastboot mode please issue the following command and see what it responds with.

fastboot getvar unlocked
[Google Pixel 6] badabing2003:
T-Mobile probably just enabled flag OEM unlock so that you can unlock.

Have you unlocked the bootloader? (it will wipe your phone)

The two links I gave you explains how to unlock the bootloader.
[Google Pixel 6] daveybfilms:
sorry, both of the commands come back with < waiting for any devices> and this is after i made sure that the device was being recognized.
[Google Pixel 6] badabing2003:
Are you using latest platform tools?

unplug / replug, if that does not work, Google is your friend , there are a lot of guides online how to fix the drivers in Device Manager.

All this is unrelated to the PixelFlasher, which expects a proper connection of an unlocked device.
[Google Pixel 6] phaino00:
Do you have oem unlocking enabled in developer options? And USB debugging? See screenshot.
[Google Pixel 6] daveybfilms:
thank you everyone. i had to download the google adb drivers in order to fully unlock my bootloader. Does anyone have a preferred custom ROM/walkthru on how to do this with the program?
[Google Pixel 6] revhellyoN:
Spoiler content hidden.

I'm stuck at boot loop
[Google Pixel 6] badabing2003:
I noticed that your Android platform tools is quite old, you're at 30.0.4-6686687

and current is 33.0.1, it's important that you always use the latest SDK.

Aside from that, what's the history of this phone?

You're updating from what version?

What version of Magisk you had installed?

What Magisk modules were installed?
[Google Pixel 6] revhellyoN:
Updated from SQ1D.220205.004, Feb 2022

Magisk 24.3

I was using https://github.com/AndroPlus-org/magisk-module-pixel6/releases to disable camera sound

Systemless hosts
[Google Pixel 6] badabing2003:
Yeah, but there are different Magisk versions,

Stable, beta, canary, alpha and even for version 24.3 there is 24301, 24302 - 24305

It really makes a difference which one you were using.

Over at Magisk general thread, you can see reported issues with the various versions,

Also some modules, specially ones related to audio have been reported to cause issues with some of the magisk versions which only got resolved (if I'm not mistaken) with 24305

I don't know the implications of `disable camera sound` module, and how it changes your system.

Lastly, did you have any custom ROM/Kernel applied at any point? Did you first attempt to accept OTA?

Here's one suggested way to disable magisk modules (to see if that is the cause) while in bootloop

run this command

adb wait-for-device shell magisk --remove-modules

If the phone gets in brief adb mode while it is looping, it will remove the magisk modules.

You can also try to flash to both slots to see if that helps.

If everything fails, try flashing unpatched (don't select the patch option) factory (keep data), you will lose root but most likely will get out of bootloop.

Good luck and report back please.
[Google Pixel 6] revhellyoN:
I'm not sure, but I think I was using canary channel. No custom rom or kernel and I didn't try to update from ota.

I already wiped everything and rooted again, maybe next update I'll try the tool again. Next time should I disable all magisk modules before trying to update?