yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] Zaxx32:
Prolly not a really difficult q but I'm beyond tired.

P6a on latest stock dec 5 th flashed by PF keeping data....I then exit and flash the magisc patched boot.img cuz I duuno how to add that to my stock dec.5 A13 DL...I keep getting bootlooped cz I'm not shure if my stock flash n patch leaves me with factory kernel or not cuz I previosly tried mvk's latest and didn't seem to take fore some reason.

Please teach me how to flash Dec.5 stock fw AND fash my ready made patched magisc boot.img AND put me back to stock kernel too! So flash fw, flash patched boot.img and ensure my kernel is back to bone. Show me how to use ur wizardry (PF) to make short work of these 3 tasks combined maybe? And I'll in turn try n help another try

accomplish the same with this most excellent baldest ass Pixel Flash Tool ...ever! That I really must learn how to use in all scenarios!

😍😅😎 Thx guys...gotta sleeep...ttys!
[Google Pixel 6a] badabing2003:
If you check the main PF thread's OP or GitHub page (both links are also found in my signature), there is a step by step instructions.

You literally follow the numbers in basic usage and you should be ok.

If for whatever reasons you still fail, just post a support.zip file, you can generate one from the help menu.
[Google Pixel 6a] badabing2003:
New Release:

Feb 05, 2023 v4.7.0 release

Added Magisk Backup Manager:

List all Magisk backups currently on the device.

Highlight the one that is backup of the current installed version.

Delete backups.

Manually add backup from PC.

Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.

Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk

Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.

Magisk installer improvements:

When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.

Magisk installer window displays the package name.

You can now copy to clipboard, the download URL and package ID.

Magisk Manager columns are now wider for better readability.

Package Manager improvements:

Added Search / Filter option.

Show count of filtered packages.

Application Name (label column).

"Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.

Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).

Other under the hood improvements.

When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.

More verbose logging that helps with troubleshooting.

Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.

Moved existing links under Help Menu | Links, and added few more handy links.

Added timestamp to support.zip filename.

On request, spinning cursor with text "Please be patient ..." is now displayed in red.

Flashing to inactive slot is now in basic configuration instead of advanced configuration.

Preparation work for version 5.0 DB improvements.
[Google Pixel 6a] juv3nal:
Hi, is anyone having this error?

Active code page: 850

Sending 'bootloader_b' (11574 KB) OKAY [ 0.261s]

Writing 'bootloader_b' (bootloader) Flashing pack version bluejay-1.2-9288097

(bootloader) flashing platform gs101

(bootloader) Validating partition ufs

(bootloader) Validating partition ufs

(bootloader) Validating partition partition:0

(bootloader) Validating partition partition:1

(bootloader) Validating partition partition:2

(bootloader) Validating partition partition:3

(bootloader) Validating partition bl1_b

(bootloader) Validating partition pbl_b

(bootloader) Validating partition bl2_b

(bootloader) Validating partition abl_b

(bootloader) Validating partition bl31_b

(bootloader) Validating partition tzsw_b

(bootloader) Validating partition gsa_b

(bootloader) Validating partition ldfw_b

FAILED (Status read failed (Too many links))

Finished. Total time: 2.662s
[Google Pixel 6a] badabing2003:
No one has ever mentioned this error, besides you're not providing much context.

You can check this
[Google Pixel 6a] badabing2003:
New Release:

Feb 12, 2023 v4.8.0 release

#50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro

#48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.

Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues

Disable Magisk Backup Manager button if root access to adb shell is not granted.

Button to Open adb shell connected to the selected device.

Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
[Google Pixel 6a] badabing2003:
New Release:

Mar 14, 2023 v4.8.1 release

#47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.

Added more visual troubleshooting event flows.

Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.

Improved support.zip redactions.

Added Support.Zip generator button on the Main screen.

APK Install option can now set the ownership to Play Store Market (useful for Android Auto)

Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.

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

Apr 10, 2023 v4.8.2 release

Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.

Display USNF related flag values when selecting a device.

Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.

Link to download Google USB Driver is added in the help menu.

Added more visual troubleshooting event flows.

Install APK now defaults to Non Market.

Added Install APK cancel option.

You can now select an app in package manager and right click to launch it on the phone.

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

Apr 27, 2023 v4.9.0 release

Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).

Support for recognizing Lineage firmware and extracting / patching boot.

Display 32 bit capabilities of the device.

Utilize New Magisk 26.x flags as needed (patch support for more devices).

Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.

Partition Manager can now list the partitions even if the devices is not rooted.

Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).

Added Open Folder button to open a file browser to the directory of the selected boot image.

Added Reboot to Download button (Odin mode).

Added Reboot to Safe Mode button.

Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.

Various additional validation checks.

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

Apr 30, 2023 v4.10.0 release

Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.

Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)

Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.

Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.

Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
[Google Pixel 6a] franco985:
i am trying to update my pixel 6a with tool. everytime i try to patch the boot.img i receive the following message:

Extracting short SHA1 from magisk_patched_26100_40100d6b_b36f6d13.img ...

Traceback (most recent call last):

File "Main.py", line 2067, in _on_patch_boot

File "modules.py", line 1893, in patch_boot_img

File "modules.py", line 1057, in extract_sha1

UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 1: invalid start byte

I have tried on two PC but same error. Has anyone encountered this error?

Thanks
[Google Pixel 6a] badabing2003:
Yes I'm aware of it, please see this and this
[Google Pixel 6a] franco985:
so for now no fix...
[Google Pixel 6a] badabing2003:
why you say that, see what the other guys did to get around it.

use an older PF 4.8.x
[Google Pixel 6a] franco985:
ah sorry
[Google Pixel 6a] franco985:
nothing to do with 4.8.2.0 and 4.7...same error
[Google Pixel 6a] badabing2003:
Interesting, I was wondering why it would work with 4.8, as that part of the code is the same.

But two people already reported that it worked for them.

In any case, you can still use PF, it just that it will be a two step process

Create the patch with 4.10.0.0, let it fail, the patched file will still found in %APPDATA%\PixelFlasher\tmp\magisk_patched_26100_40100d6b_* (if your Magisk version is different, then it would have that version number

select the stock image, and select no reboot option, and of course keep data

Flash Pixel Phone

After flashing is completed, your phone will remain in bootloader mode (which is what we want)

Change flash options to custom flash (if you don't see this option, enable advanced options in settings configuration), choose init_boot, and browse to select the patch identified above.

scan for devices to detect your device in bootloader mode, and select it.

uncheck the no reboot option

Flash pixel phone

You should be fine
[Google Pixel 6a] franco985:
i have followed your instructions, but when i ty to flash patched boot i have:

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

2023-05-02 23:43:12 PixelFlasher 4.10.0.0 Flashing Phone

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

Android Platform Tools Version: 33.0.3-8952118

2023-05-02 23:43:12 Flashing device 27161JEGR08421 ...

C:\Users\Fero\AppData\Roaming\PixelFlasher\tmp>chcp 850

Tabella codici attiva: 850

fastboot: verbose: Do flash init_boot C:\Users\Fero\Desktop\magisk_patched_26100_40100d6b_f0e7f525.img

fastboot: verbose: target reported max-download-size of 261095424 bytes

Warning: skip copying init_boot image avb footer (init_boot partition size: 0, init_boot image size: 67108864).

Sending 'init_boot' (65536 KB) OKAY [ 1.550s]

Writing 'init_boot' FAILED (remote: 'partition (init_boot) not found')

fastboot: error: Command failed

2023-05-02 23:43:14 Done!

Flashing elapsed time: 2 seconds
[Google Pixel 6a] franco985:
maybe is boot and not init_boot
[Google Pixel 6a] badabing2003:
I'm sorry, you're right it is boot not init_boot

init_boot is only for p7 and p7p devices
[Google Pixel 6a] franco985:
already done...thank you for your support!!!!!!!!!!!
[Google Pixel 6a] UberFiend:
Thanks to you both! I had that exact issue and now all seems well. 😊

I used PF in January to unlock & root, but I lost root a month ago after a forced update. Is there a way to circumvent that or make it easier to reflash in the future?
[Google Pixel 6a] badabing2003:
Yes, you won't run into the same issue on next PF release, you can read the Github issue to see how it will be circumvented.
[Google Pixel 6a] zamarax:
I followed this to a T and my device soft bricks, get's to the google logo and then distorts the screen and reboots to fast mode, my only option is to restore from the web, which works but then leaves me unrooted.

Pixel 6 Pro
[Google Pixel 6a] badabing2003:
support file please
[Google Pixel 6a] zamarax:
Attached.
[Google Pixel 6a] zamarax:
As a side note, I did it the traditional way of extracting the boot.img - sending to phone, patching with magisk on the phone, bring that patched image back to the PC, fastboot, boot the img, launch magisk and direct install.

That worked so I don't think it's a change with the latest release.

Either way, looking forward to a fix in PixelFlasher because your utility is just far easier to use.
[Google Pixel 6a] badabing2003:
Your problem is totally unrelated to the above listed problem, which is specific to 6a boot image.

here's why

SHA1 of magisk_patched_26100_91668d4a_390ac219.img file: 390ac21939fa716368e4f4e436558842524db812

Getting SHA1 of source boot.img ...
Source boot.img's SHA1 is: 91668d4a63e51d0f419225ca3b722a58dbb63499

Extracting short SHA1 from magisk_patched_26100_91668d4a_390ac219.img ...
Short SHA1 embedded in C:\Users\REDACTED\AppData\Roaming\PixelFlasher\tmp\magisk_patched_26100_91668d4a_390ac219.img is: 91668d4a
Comparing short source boot.img SHA1 with short SHA1 embedded in 91668d4a (they should match) ...
Good: Both SHA1s: 91668d4a match.

As you can see, you were able to create a proper patch, which is different from above issues where the patch was giving an error.

Furthermore, your first flash was the stock boot, so patch was not even involved.

Please select a boot image!
Selected Boot:
File: boot.img
Path: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\91668d4a63e51d0f419225ca3b722a58dbb63499\boot.img
SHA1: 91668d4a63e51d0f419225ca3b722a58dbb63499
Patched: False
Date: 2023-05-12 11:49:17
Firmware Fingerprint: raven-tq2a.230505.002
Firmware: C:\Temp\raven-tq2a.230505.002-factory-953c94d1.zip
Type: firmware

...

:: This is a generated file by PixelFlasher v4.10.0.0
:: cd C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\raven-tq2a.230505.002
:: pf_boot.img: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\91668d4a63e51d0f419225ca3b722a58dbb63499\boot.img

That is the hash of stock boot, not the patched one.

And you ran into flashing issue

extracting product.img (2620 MB) to disk...ziparchive W 05-12 11:53:26 30184 32468] Zip: unable to truncate file to 2747408384: Invalid argument
fastboot: error:
failed to extract 'product.img': I/O error

This could be anything, and nothing PF can do about.

It could be low disk space on PC or on the phone, bad cable , bad usb port ...

Product.img as not properly extracted and flashed, on both slots

Then you selected the patch file and tried Flash Boot (just the patch)

Which was a bad idea, you had practically dirty flashed the factory image (that is exactly the options you had chosen) which had failed (product.img was not flashed) and tried to flash a patch on that.

Sorry to disappoint you, you should look into the issue, the fix that PF has will not fix your issue.
[Google Pixel 6a] zamarax:
Well at first I did it the traditional way of using the patched file, but same result, and regardless of which way I do it this error always came up

'product.img': I/O error

But I can use that same Factory image an do it the traditional way with ADB + Magisk and it goes without error.
[Google Pixel 6a] badabing2003:
Maybe you got lucky with one write.

That error is a flash time error, nothing to do with patching.

With PF you chose both slots, the flash_all script only flashes the current slot.

Other than that there is really no difference in the scripts, you can compare the two if you want to see the differences.
[Google Pixel 6a] 3122230:
Thank you. I already wanted to flash back to the April version. Has worked directly and without error.
[Google Pixel 6a] zamarax:
yeah I don't know what to say - I went the old school route and it worked so hard to confirm anything, I'll try again with next months factory image release.
[Google Pixel 6a] badabing2003:
If it fails with next month's then try not to select "Flash both slots" option and see if it works, perhaps there is an issue with your alternate slot.
[Google Pixel 6a] badabing2003:
New Release:

May 19, 2023 v5.0.0.1 release

#75 Bug fix, when device is in bootloader, type error.

#74 Added Support for Pixel 7a (lynx)

Configuration option to define the file manager to use on Linux (default: Nautilus)

Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).

Support for additional types of Factory / ROM files.

Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)

New advanced option, ability to choose the patching method (with recommendations).

Added Recovery Image patching option.

Advanced option to enable the use of busybox shell (default off).

Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.

Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.

Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)

Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.

#66, when checking the patched files internal SHA1, provide a confidence rating.

Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.

Added fastbootd testing to Dry Run.

Added Github actions to build all the targets on Github.

Code refactoring, bug fixes and improvements
[Google Pixel 6a] Moscha:
@badabing2003

Tested the new 5.0.0 Version with my Pixel 6a to Update from April to May Image (latest Magisk stable, Original Google Factory ROM).

- New Version sucessfully processed the Magisk Patch to the Bootloader *yeah*

- If i want to flash and the script executes: After first reboot the Device won't be recognized in the Bootloader:

adb.exe: device '2A281JEGR00440' not found

Atacched support.zip, hope it helps!
[Google Pixel 6a] badabing2003:
Sorry about the silly mistake, fixed and links updated.
[Google Pixel 6a] Moscha:
Now everything runs fine with Release v5.0.0.1 👍👍👍

And thanks for the good work!
[Google Pixel 6a] lalo_a13:
Hi, I just update to latest version. Still doesn´t recognice my device while on bootloader :(

Update: nevermind. It seems that my problem was actually driver related. I installed the driver and now it´s flashing properly may update.

Thanks
[Google Pixel 6a] badabing2003:
New Release:

May 25, 2023 v5.1.0.0 release

Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3

Temp workaround to avoid selecting root method patching when Magisk Delta is detected.

Nicer looking / clearer manual patching dialog.

When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.

Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.

Boot image list box now displays the applied PixelFlasher patch method.

Auto-resize boot image list box columns for better readability.

Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.

#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).

Bug fixes and improvements.

Update:

Patch Release:

v5.1.0.1 release

Exception handling when device is not in the listed Pixel devices.

v5.1.0.2 release

Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
[Google Pixel 6a] masterdex:
One question can this be used to reset my pixel 6a to factory state being on Los?
[Google Pixel 6a] badabing2003:
Yes

To reset to factory state, I would advise to flash to both slots a factory image

and after confirming that it works, locking the bootloader.
[Google Pixel 6a] badabing2003:
New Release:

June 01, 2023 v5.2.0.0 release

Update build workflows

Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.

Added rules engine code to better / easier management of the UI widgets enabling / disabling.

Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.

Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
[Google Pixel 6a] badabing2003:
Bug Fix Release:

June 01, 2023 v5.2.0.1 release

Bug fix #78 Error when opening a shell console on Linux / Mac
[Google Pixel 6a] badabing2003:
Update:

June 03, 2003 v5.2.0.2 release

#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
[Google Pixel 6a] penpex:
Hello,

I am trying to update my Pixel 6a from the March update to the May update (this is fine right, you don't need to to do each one incrementally like I'd have to to do the April one first?)

I am using Android Platform Tools 33.0.3-8952118

I am still under Magisk 25.2 (is this a problem?).

I am using the newest PF 5.2.0.2.

When doing that I get :

"

Comparing source boot.img SHA1 with SHA1 embedded in 4r!~!d6b9512f6dffbb6f6b67c1b878f3bd82d18 (they should match) ...

NOTICE: The two SHA1s did not match.

magisk_patched_25200_40100d6b_8e174e53.img extracted sha1: 4r!~!d6b9512f6dffbb6f6b67c1b878f3bd82d18

boot.img sha1: 40100d6b9512f6dffbb6f6b67c1b878f3bd82d18

This could be normal due to compression

Checking match confidence level.

The confidence level is: 90.0%

Acceptable!

Magisk Version: 25.2:25200

Patch time: 17 seconds

"

I am feeling antsy about this, and did not proceed yet.

Is there anything I can do about that to have a good match ? (Update Magisk?)

What do I risk if I continue the process ?

Thank you in advance!
[Google Pixel 6a] badabing2003:
Yes you can jump from March update to May update.

Magisk 25.2 is good too.

And it is ok to have confidence level of 90%

Anything above 50% is good, the reason it doesn't match 100% because of compression.

You're safe.

At the point where the question is asked, it is only creating a patch, it's not even flashing anything, if you answer no, you won't get the patch, if you answer yes, you would and it would show up as an option to select when flashing.

Even if the patch is not good, and you choose to flash it, the worst that will happen is a bootloop, and then you can flash the stock boot and and be good again.
[Google Pixel 6a] penpex:
Thanks a lot, it did work ! :)

Should I update Magisk to 26100 as it suggests me to do ? (for the future)
[Google Pixel 6a] badabing2003:
If it ain't broken don't fix it.
[Google Pixel 6a] badabing2003:
New Release:

June 06, 2003 v5.3.0.0 release

Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.

PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's 😀), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.

When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.

If there was a way to pre-load odin with the extracted files, flashing could also be automated.

I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.