yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] mohamed10620:
Can you be more specific, I don't know which section am supposed to look at.
[Google Pixel 6] tom1807:
First make sure you granted "[sharedUID] Shell" Superuser rights in Magiosk to make sure it shows up as rooted.

Second, just select the patched image, select Keep Data(!) and you are good to go.

However, I always use the complete Image, never use the OTA.

Edit: btw. the January update is out

Cheers

Tom
[Google Pixel 6] badabing2003:
New Release:

Jan 07, 2024 v6.6.0.0 change log:

New Feature: Download any Google device firmware or full OTA directly in PixelFlasher.

Automatic detection and notification if an update is available for the selected device.

New feature: Cancel / reset OTA update pushed by Google (need to be used prior to a reboot). Binary graciously provided by @capntrips.

Removed outdated links from help menu.

kdrag0n's safetynet-fix

Displax's safetynet-fix

Added new links to the help menu

osm0sis's PlayIntegrityFork

chiteroman's PlayIntegrityFix

TheFreeman193's Play Integrity Fix Props Collection

Full OTA Images for Pixel Phones / Tablets

Factory Images for Pixel Phones / Tablets

Full OTA Images for Pixel Watches

Factory Images for Pixel Watches

Full OTA Images for Pixel Beta 14

Factory Images for Pixel Beta 14

Enable Magisk Kitsune patch creation using Magisk core component (previously disabled due to incompatibility and patches were only created using the manager).

Miscellaneous improvements, bug fixes and code refactoring
[Google Pixel 6] badabing2003:
Bugfix Release:

Jan08, 2024 v6.6.0.1 change log:

Bug Fix: Toolbar menus were interfering with the download menus and triggering a download when toolbar was modified.
[Google Pixel 6] badabing2003:
New Release:

Jan 10, 2024 v6.6.1.0 change log:

Changed PixelFlasher icons to dark icon (artwork provided by @T-Ryder).

Potential fix for #144, when getting firmware / ota download links, fallback to ignore ssl errors, if ssl errors are encountered.

Add ssl verify ignore fallback to any download (also display warning).

Add button in Pif Manager to convert key=value format (similar to env or older .prop format) to json format.

Device Info now gets props as root if the device is rooted.

Miscellaneous minor fixes and improvements.
[Google Pixel 6] badabing2003:
New Release:

Jan 20, 2024 v6.7.0.0 change log:

Added history to device image selection (Max 16)

#133 Fix for Get Xiaomi.eu print when version_class is missing.

Improved device state detection with retry attempts.

Updated 7zip binaries to v23.01

Added line numbers to Active Pif window and Output Console window, along with an option to sort FP keys for easy visual comparison.

Pixel watches require user intervention after flashing OTA, added popup messages to guide the user for the next steps.

You can now easily save the Active Pif content into a pif json file (filename automatically build from print information, however user can change before saving)

Keep splash screen visible until the main window shows up.

Under the hood improvements and bug fixes, improved logging and refactoring code.
[Google Pixel 6] guniens:
Hi @badabing2003

I'm in the process of selling my P6 and jump on the P8. My P6 is running full stock A14 + root (Magisk).

What's the recommended process to revert root and erase everything? Can be done via PixelFlasher?

Thanks in advance!
[Google Pixel 6] badabing2003:
Yes,

- Enable Advanced options in settings.

- Get the latest factory image, Process and select the stock boot in the list

- Set the following options

View attachment 6061511

- Flash Pixel Phone
[Google Pixel 6] guniens:
Awesome!

I just need to lock bootloader via developer options once did the process above right?
[Google Pixel 6] badabing2003:
Actually, you lock with fastboot or PF

What you need to do is do a basic setup after the steps above so that you get into developer options and enable developer options

Enable USB Debugging (don't just yet disable OEM Unlocking)

Authorize your PC to access over adb

Lock bootloader.

This will lock the bootloader and wipe again.

I don't think you need to worry about disabling OEM unlocking afterwards, that should be harmless.

but if you really want to, you can
[Google Pixel 6] guniens:
This is done in Pixel Flasher right? Can you point this out too? :cry:
[Google Pixel 6] badabing2003:
It should be on the toolbar (unless you have it hidden from the toolbar)

And also in Menu | Device

View attachment 6061560
[Google Pixel 6] badabing2003:
New Release:

Jan 29, 2024 v6.7.1.0 change log:

Added an checkbox in Pif Manager. Keep All Keys which allows any unrecognized key to be kept in the json file when using smart paste. This allows support for future keys that could be added but are unrecognized today. (Example: KERNEL)

Added Cleanup DG but in Pif Manager to clean up Droidguard cached files. Helps in some situations.

Miscellaneous small improvements.
[Google Pixel 6] guniens:
Thank you so much! For your help and your incredible work ;)
[Google Pixel 6] badabing2003:
New Release:

Feb 16, 2024 v6.8.0.3 change log:

Added untested support for patching with KernelSU for Pixel phones. Patching with APatch is in the works.

Detect known blacklisted kernel names, and notify the user. (list is current as of this release date).

Rename the SOS button to reflect that the modules would be removed instead of being disabled.

Removed bulk install APK feature which installed all APKs in a directory, instead reworked the Install APK feature to allow user choice multi-select, and added another option Bypass low target SDK block.

Report device Kernel and KMI.

Added Android Platform Tools 34.0.4 to known problematic versions list, which when detected warns the user.

Improved Pixel Watch flashing dialog messages.

New feature: #152 Show System Apps and Show 3rd Party Apps in Package Manager.

Bug Fix: #157 'PifManager' object has no attribute 'first_api' in some situations.

Bug Fix: scrcpy download link was not working.

Support for upcoming PlayIntegrity Fork v8 changes by @osm0sis.

Added Special Magisk 27001 install option when selecting Magisk install. (This is similar to Special Magisk 26401, just a version difference).

Support for SSL error fallback for all https requests (previously was only for PIF downloads).

Improved factory / image downloading with lower memory footprint.

Miscellaneous minor bug fixes and enhancements.
[Google Pixel 6] badabing2003:
Update Release:

Feb 17, 2024 v6.8.0.4 change log:

Use MacOS 13 to build with Github actions instead of MacOS 11, sorry to folks who use older MacOS, unless I get it to build it successfully on Github, MacOS 13 will have to do.

#158 Fix the App version.

Note: The following versions have identical code 6.8.0.0, 6.8.0.1, 6.8.0.2, 6.8.0.3, 6.8.0.4, the differences are in Github actions.
[Google Pixel 6] coendeurloo:
First of all: Awesome tool, I've been using it for quite a while now, always used it without problems.

Now for my problem: I wanted to update my version from the december build to the one from february, so I downloaded the latest pixelflasher again, connected it with my phone, downloaded te latest image (factory) and patched it. I selected the patched file and I tried to flash it onto my phone but the phone reboots, and gets stuck in the 'Fastboot Mode' screen with a red triangle and an exclamation mark. It doesn't do anything unless I press 'Start' on the phone, after which pixelflasher fails because it can not find the device anymore:

2024-02-20 14:09:50 Getting device: 21041FDF6006UQ state ...
Rebooting device: 21041FDF6006UQ to bootloader ...
Fastboot waiting for device: 21041FDF6006UQ for bootloader ...
Timeout: [60] Fastboot could not detect device: 21041FDF6006UQ in bootloader mode

2024-02-20 14:10:51 ERROR: Encountered an error while rebooting to bootloader
Aborting ...

and later:

2024-02-20 14:11:11 INFO: Flashing was aborted.
This could be user initiated or a problem encountered during flashing.
You might need to manually reboot your device.

Updating connected devices ...

I then tried the latest OTA, to see if that works. The OTA seems to work, but after putting it on my phone and rebooting, I'm stuck in the same 'Fastboot Mode' screen where I can only press Start. SO now my phone is updated, but I seem to have lost root.

What should I do?
[Google Pixel 6] badabing2003:
Provide a support file.
[Google Pixel 6] coendeurloo:
Thank you, I attached the support file
[Google Pixel 6] badabing2003:
It looks like you have USB driver issue when your device is in bootloader mode.

Fastboot waiting for REDACTED: REDACTED for bootloader ...
Timeout: [60] Fastboot could not detect device: REDACTED in bootloader mode

2024-02-20 13:22:49 ERROR: Encountered an error while rebooting to bootloader
Aborting ...

2024-02-20 13:22:49 INFO: Flashing was aborted.
This could be user initiated or a problem encountered during flashing.
You might need to manually reboot your device.

Updating connected devices ...

==============================================================================
2024-02-20 13:23:51 User initiated Scan
==============================================================================

2024-02-20 13:23:51 Scanning for Devices ...
No Devices found.

Which is why you couldn't flash the factory image, but were able to sideload OTA.

However getting root would require the the use of fastboot (bootloader mode)

Install the official Google USB drivers (link in PF's help menu) in both adb and bootloader modes and then you should be fine.

If not, try different cable / usb port, but USB drivers should do the trick.
[Google Pixel 6] coendeurloo:
Thank you! That was it. There were no driver issues when it was booted up and connected, BUT in the fastboot mode it did not have the correct drivers installed apparently, I had an exclamation mark in the device manager of windows 11.

It is now in the process of flashing but I'm sure it'll be fine. Thanks again man, you made my day, I was worried there for a second!
[Google Pixel 6] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version.

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

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

Mar 03, 2024 v6.8.2.1 change log:

Bundle in the executable the missing files android_version.json and android_devices.json otherwise patching with KernelSU won't detect your Pixel as Pixel device.

Add back Magisk Alpha install option, thanks to pull request from @hldr4

Make Magisk install window resizable.

Add right click option on the selected Magisk to download in case you just want it downloaded and not installed.

Update all old forum.xda-developers.com links to xdaforums.com

Make Pif Manager work without a device being connected (obviously for props / pifs management and not for updating / testing pifs).

Typo fixes and other minor improvements.
[Google Pixel 6] mohamed10620:
I have Google pixel 6 rooted and I want update OTA in safe way and use pixel flasher,I tried use pixel flasher twice but it was brick, and want to know if this is right?
[Google Pixel 6] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel 6] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel 6] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel 6] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel 6] badabing2003:
Update Release:

Apr 09, 2024 v6.9.1.3 change log:

Fix regression introduced when refactoring code in KernelSU Patching.

#187 On MacOS, move the exit menu into PixelFlasher's file menu from the OS's native Exit menu.
[Google Pixel 6] badabing2003:
New Release:

Apr 14, 2024 v6.9.2.0 change log:

Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).

Credit to @tbalden for the discovery and @capntrips for the details of the process.

Select any img file and get additional image info.

#190 fix, scrcpy launch improvement.

Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).

If KernelSU or APatch is installed, report their version as part of device details.

Improved logging.

Improved santization.

Other minor improvements and added stability.
[Google Pixel 6] badabing2003:
Update Release:

Apr 16, 2024 v6.9.2.5 change log:

Roll up MacOS related changes. #187 and #190

Logging improvements

When Magisk delta is installed, automatically set the package to: io.github.huskydg.magisk
[Google Pixel 6] badabing2003:
Update Release:

Apr 19, 2024 v6.9.3.0 change log:

Update AVBTool to use RSA library instead of depending on an external openssl.

English typo corrections.

When flashing OTA, give the option to continue, even if it is a downgrade.

Github action: Fix MacOS build deployment issue.
[Google Pixel 6] allday5850:
So I am curious about that first point made about the experimental feature to downgrade without a wipe. I tried finding out a bit more info about this but I came up empty. Would you be willing to elaborate? With me understanding that you're not in any way responsible nor providing support for an "experimental" feature if something goes wrong on my end.
[Google Pixel 6] allday5850:
Reason I'm asking is I'm on Android 14 AP1A.240405.002 Pixel 6. Id like to go back one month without wiping if possible ..how doable is this regarding my first question?
[Google Pixel 6] badabing2003:
See this, basically PF is implementing that and making it easy for you without needing to use AVBTool and command line.

The way it works is that the SPL entry in the boot.img is checked when you try to downgrade, and if the one you're updating to is older, then the downgrade will fail unless you wipe.

What this does is creates boot.img with updated SPL that matches what you're trying to downgrade to

You first create this boot.img, flash that and then do the downgrade.

Theoretically and based on what's been posted it works.

Select the image that you want to downgrade to

Process

Select the boot stock

Enable Advanced Settings

Dev Tools | AVB Prepare Downgrade Patch

You get this

View attachment 6100387

If your device is connected, it will get the device's boot.img, (option 1) otherwise you have to supply the boot.img of what's on your device (option 2)

This should create a downgrade patch of boot.img

You flash that to your device first.

You can use the Custom Flash option in PF

Select Boot, and choose the newly created file and Flash Pixel Phone

View attachment 6100390
[Google Pixel 6] allday5850:
That was exactly what I was looking for. I appreciate you giving me the info. I am pretty sold on giving this a shot now. So I will look how goes.
[Google Pixel 6] badabing2003:
Thanks, please keep us updated so that it can be moved from experimental stage if it works.
[Google Pixel 6] badabing2003:
Update Release:

May 08, 2024 v6.9.4.0 change log:

Added encryption to support.zip for extra privacy / security.

Regression bug fix: When a Magisk module was disabled in Magisk, it was not reflected in PixelFlasher.

Added Refresh button to refresh Magisk module list at will.

When Apply Custom ROM checkbox is checked, make sure that a ROM file is also selected, otherwise ignore the selection.

After rebooting to bootloader, if the device is not detected, sleep 5 seconds and try again.

Update Readme to include a link to proper USB driver setup on Linux systems.
[Google Pixel 6] miss:
pixelflasher no detecta el teléfono

Abro una ventana cmd en la carpeta platform-tools y con el comando adb devices detecta el teléfono, pero pixel flasher no

Intento descargar un archivo de soporte y aparece el error "no se pueden actualizar los datos en el archivo"

Que pasa, la computadora detecta perfectamente mi teléfono y volví a instalar el controlador r13?
[Google Pixel 6] Snnorlaxx:
I'm having a problem with my pixel 6a and PixelFlasher doesn't detect it any more. Was working great before , but I had to re-set my phone and reflash Lineage Os. Flashed fine with regular ADB commands from recovery and fastboot. Just wondering what I did wrong that it is not detected now ?

I'll attach the sanitized support file, just not sure if its complete. Let me know if there is anything else I should look at.

Cheers
[Google Pixel 6] badabing2003:
The last time your device was detected by PF was on May 9th

=======================================
Selected Device on 2024-05-08 11:42:56:
=======================================
Device ID: REDACTED
Device Model: bluejay
Device Active Slot: b
Device Mode: adb
Device Name: Pixel 6a
Device First API Level: 32
Device Version End Date: June 2025
Device Security Update End Date: June 2026
Has init_boot partition: False
Device Bootloader Version: bluejay-1.3-11403664
Device is Rooted: False
Device Build: AP1A.240405.002.A1
Device API Level: 34
Android Version: 14
Android Name: Android 14
Android Codename: Upside Down Cake
Android Release Date: Q3 2023
Android Latest Update: Present
Device Architecture: arm64-v8a
Device Kernel: Linux localhost 5.10.189-android13-4-00012-g1217bb583cc5-ab11174560 #1 SMP PREEMPT Mon Dec 4 18:59:42 UTC 2023 aarch64 Toybox
Device Kernel Version: 5.10
Device KMI: 5.10.189-android13
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state:
ro.product.first_api_level: 32
ro.boot.veritymode:
ro.boot.verifiedbootstate: orange
ro.secure: 1
ro.zygote: zygote64_32
ro.vendor.product.cpu.abilist: arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32: armeabi-v7a,armeabi
Magisk Manager Version: :
Checked for Package: io.github.huskydg.magisk
KernelSU App Version: :
APatch App Version: :

After which there is no operation in PF that would have changed the state of your device.

As you stated you attempted to perform manual updates outside of PF, effectively no PF logs can tell me exactly what steps you took. and what were their outcome and at what point things started going bad.

Without knowing all of that, it is impossible to provide recovery advice.

What I can offer is general one time guidance in this thread considerind that it is OT to this thread.

If you would like me to continue answering specific questions, please kindly mention me in a thread / post that you discuss the issue, which probably is more relevant in a lineageos specific thread (or start one).

If your device is not detected by adb or fastboot from command line, PF has no chance of detecting it either, as it uses those commands.

Try the various published key combination commands to put your device into recovery or bootloader mode, and get it detected by adb / fastboot commands

adb devices , fastboot devices

If you're on Windows, check device manager, make sure you install the latest Google's USB drivers (link in PF)

Try another PC, another cable, another USB port

Drain battery fully and then try again by plugging / charging.
[Google Pixel 6] Snnorlaxx:
Thanks for the reply, I guess I didn't make myself very clear. I had some play store issues with my Pixel 6a. To fix it, I did a factory reset, and reflashed Lineage OS , then reflashed Magisk. I was/am able to enter recovery mode, fastboot mode, everything works as it should manually. The only thing that dose not work , is the device detection in PixelFlasher. Alson tried my old Moto G7 Play (channel) and it is properly detected, which led me to believe that my setup, cables etc, are in working order.
[Google Pixel 6] badabing2003:
if adb /fastboot commands detect the device but not PF, then it is something I need to know.

Please provide the outputs of those commands that your get from command line

After which start PF , enable debug and do a scan, provide support.zip file and I can compare the outputs.

If the Android Platform tools that you have set in PF is different than the one you're using from command line, that could explain it, it's not a good idea to use different ones, spceially if one opens a port and causes the other not to be able to listen on the port.

Killing all instances of adb / fastboot

Removing it from system path and the scanning again should show the device.
[Google Pixel 6] Snnorlaxx:
Thanks again for taking the time. I've attached a new debug support file as well as the Android

Platform Tools version+(command line responses). I only use the one listed Android Tools shown in PF as well as command line.
[Google Pixel 6] badabing2003:
In command line (while in default user directory), please type

where adb
where fastboot
adb --version
fastboot --version

Then go and download the latest Android platform tools please.

unpack it and point PF to it, and try again.

I don't like

C:\Program Files (x86)\Minimal ADB and Fastboot.
SDK Version: 34.0.5-10900879
Adb SHA256: 58765259a349cce392fbb2f15dab75fed3b7c0b40cc68a7653278b9850602a2f
Fastboot SHA256: 43703d6e235a72837c6385a440091dc5da6f522d86cf7735ed53c2a508e2b06b
[Google Pixel 6] Snnorlaxx:
here you go, hope I didn't screw this up.
[Google Pixel 6] badabing2003:
Why is it in a path that says minimal ADB and Fastboot

And you shouldn't be running it from C:\Program Files (x86)\Minimal ADB and Fastboot

So that I could see what it is that's being picked up

Please do the following.

Delete C:\Windows\adb.exe[

Delete C:\Program Files (x86)\Minimal ADB and Fastboot folder

Hunt for any adb.exe and fastboot.exe anywhere on your system, and delete them

unpack the official one I linked into a path without space (even though PF handles spaces, I want to eliminate possibilities) Example: C:\Android\Platform-Tools

Reboot your system, yes reboot so that anything that is currently loaded is no longer loaded

Point PF to where the unpacked Platform-Tools is, and scan

There is absolutely no reason for it not to work.

One last possibility if it still doesn't

Redirect the output of the

adb devices

fastboot devices into a file and share the files, in case there are some funky formatting that PF is not expecting.

Thanks
[Google Pixel 6] Snnorlaxx:
Thanks for all the help and sorry for taking so long to reply

1) deleted, 2) deleted, 3) searched for any other instances, none found, 4) done, 5) rebooted system,

6) done.

Still no joy, let me know if there's anything else I can try.
[Google Pixel 6] badabing2003:
Thank you for all the testing.

This is so weird, it just doesn't make sense.

Please issue the following and redirect it to a file (don't copy and paste from console)

I want to inspect the output

cd c:\
where adb
adb --version
adb devices
cd C:\Android\Platform-Tools
adb --version
adb devices
echo end

If this doesn't reveal anything, I'll have a version with additional debug messages.