yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
@knopie , please give the latest release a try and see if it works.

But before doing so, can you please try 6.6.0.1 again, I'm wondering if you installing modules on your system is now making 6.6.0.1 work?

If not try the 6.6.1.0 please.

Thanks
[Google Pixel 8 Pro] thefinger:
This one works OK @badabing2003 ! I had the same problem as @knopie with 6.6.0.1 on OSx
[Google Pixel 8 Pro] knopie:
Badabing, 6.6.0.1 is also working, probably by the installed Python modules. 6.6.1.0 is also working.

Thanks for your great support.

Jos
[Google Pixel 8 Pro] Morgrain:
Did everything as normal (used your new OTA download button however), and it seems that there was a problem after flashing the OTA, device remained in fastboot mode and I got an error message, effectively stating that the device could not be found in fastboot. The program effectively stopped at flashing the magisk patched init_boot file.

I've been rooting my P3, 4, 6, 7 and 8 every month, I can definitely confirm that I had Google USB drivers installed. It seems that for some reason, my Windows doesnt have the Google USB Drivers any longer, I had to re-install those (after checking device manager, it stated that no drivers for my p8 pro were installed). Not sure what happened, if it was a windows update, your program, a bug, or something else.

It's not a big deal, I merely have to re-install magisk manually, but something seems to have gone wrong. It will probably be impossible to troubleshoot, considering that I have no idea how the Google USB drivers just "disappeared".

The only thing that changed on my end was the fact that I bought a Quest 3 recently and - obviously - installed the Oculus tool / drivers, maybe Facebook messed up the Google USB drivers?
[Google Pixel 8 Pro] badabing2003:
Yeah, USB drivers missing would explain that, basically when PF rebooted to bootloader, it no longer could detect your device, hence couldn't flash the patch.

PF definitely does not mock around with drivers.

And seeing that you installed Quest 3 too / drivers, which is Android based, I bet you they removed Google's drivers and installed theirs.

That's the only logical explanation.

You just have to flash the patch, Magisk should already be on your phone.
[Google Pixel 8 Pro] maverixz:
Hello our Pixel hero! @badabing2003, I have been unable to process the latest beta release (husky_beta-ota-ap11.231215.007-40f903ad.zip.) When I choose the download OTA file and click process, it goes through the motion but doesn't separate the boot ini file for me to patch. Any ideas? Btw, I am using the PixelFlasher version 6.6.1.0
[Google Pixel 8 Pro] badabing2003:
Support file please.

Seeing that you posted in Pixel 8 Pro support channel, I downloaded and processed the latest beta for Husky.

No issues here.

2024-01-12 12:08:17 User initiated Process firmware

==============================================================================
2024-01-12 12:08:17 PixelFlasher 6.6.1.0 Processing firmware file ...
==============================================================================
Low memory option: False
Available Free Memory: 76.32 GB / 127.92 GB
Factory File: C:\Android\Images\husky_beta-ota-ap11.231215.007-40f903ad.zip
Detected OTA file
Extracting payload.bin from C:\Android\Images\husky_beta-ota-ap11.231215.007-40f903ad.zip ...
Extracting files from payload.bin ...
Processing boot partition................................Done
Processing vbmeta partition.Done
Processing init_boot partition....Done
sha1 of init_boot.img: d5d3370a88a538ea3078f10b05e8153768fe39a6
Checking for cached copy of init_boot.img
Cached copy of init_boot.img with sha1: d5d3370a88a538ea3078f10b05e8153768fe39a6 is not found.
Copying E:\pf-data\tmp\init_boot.img to E:\pf-data\boot_images4\d5d3370a88a538ea3078f10b05e8153768fe39a6
Checking DB entry for PACKAGE: C:\Android\Images\husky_beta-ota-ap11.231215.007-40f903ad.zip
Creating DB entry for PACKAGE: C:\Android\Images\husky_beta-ota-ap11.231215.007-40f903ad.zip
Package ID: 97
Checking DB entry for BOOT: d5d3370a88a538ea3078f10b05e8153768fe39a6
Creating DB entry for BOOT: d5d3370a88a538ea3078f10b05e8153768fe39a6
Boot ID: 170
Checking DB entry for PACKAGE_BOOT: package_id = '97' AND boot_id = '170
Creating PACKAGE_BOOT record, package_id: 97 boot_id: 170
Package_Boot row id: 191

Please select a boot image!
Process firmware time: 4 seconds
------------------------------------------------------------------------------
[Google Pixel 8 Pro] maverixz:
Thanks for your prompt response. Please find below the sanitized support zip file.
[Google Pixel 8 Pro] maverixz:
You are amazing. I updated the magisk and everything went smoothly!
[Google Pixel 8 Pro] HipKat:
That's not the most recent. That's the December update, fyi
[Google Pixel 8 Pro] fabiodifa:
@badabing2003 First of all, thanks for your work and sorry for my noob question. I own a P8P, with stock Rom and no root. I'd like to test a custom Rom, but I want to be sure that Ican come back to stock with no issues.Is the PixelFlasher tool intended fot this use? Is there a detailed guide I can use if necessary? Thanks in advance!
[Google Pixel 8 Pro] simplepinoi177:
I know you directed your inquiry to badabing2003, but I'd like to attempt to assist...

As long as you can get into bootloader/fastboot mode, you should be able to return "back to stock with no issues" using PF tool -- so be careful if/when updating/removing/modifying the bootloader; which I don't believe you would ever do when "test[ing] a custom Rom"....

I wonder if a detailed guide could/would be created for such a circumstance, but most of PF is pretty intuitive and I'm sure can be figured out with relative ease without a pure detailed guide...

But if not, as much as I wouldn't want to direct traffic away from this great tool, there is the official tools that should take care of getting you back completely stock for you such as Android Flash Tool or the Google Pixel Update and Software Repair Tool
[Google Pixel 8 Pro] iestynapmwg:
I just tried flashig the January update to my P8P using PixelFlasher 6.6.1.0, and ran into the same problem I did a month ago: after the flash finishes and the phone reboots into the bootloader again, PF can't see it. It suggests hitting the scan button, which i did, but it returns "No Devices found." Yet i can use fastboot from the command line, and it's there:

$ fastboot devices

38230#@#@#@#@# HP Truevision HD (mod edit; removed serial number -- probably not the best thing to publicly publish your serial number)

Maybe PF thinks it's not there because of the weird "HP Truevision" string?

I'm attaching the support.zip file, in case it helps.
[Google Pixel 8 Pro] badabing2003:
What kind of drivers are you using?

What mode is HP Truevision HD ?

PF is definitely not expecting that.

When you reboot to bootloader and run fastboot devices

And you're on a buggy version of Android Platform Tools Version: 34.0.4-android-tools
[Google Pixel 8 Pro] iestynapmwg:
Nothing special, bog-standard usb kernel modules

$ fastboot devices

38230#@#@#@#@# HP Truevision HD (mod edit; removed serial number -- probably not the best thing to publicly publish your serial number)

This is while the phone is in fastboot mode. After booting the system, adb shows:

$ adb devices

List of devices attached

38230#@#@#@#@# device (mod edit; removed serial number -- probably not the best thing to publicly publish your serial number)

Yeah, Arch still haven't updated the android-tools package. Is that what's causing this? I found out what that HP Truevision thing is:

$ lsusb

...

Bus 001 Device 005: ID 04f2:b2f8 Chicony Electronics Co., Ltd HP Truevision HD

....

Bus 003 Device 022: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)

So the buggy fastboot is reporting the wrong device string, despite showing the correct device ID/serial number?
[Google Pixel 8 Pro] iestynapmwg:
I just downloaded 34.0.5, and now:

$ ./fastboot devices

38230#@#@#@#@# fastboot (mod edit; removed serial number -- probably not the best thing to publicly publish your serial number)

So, yeah, that would appear to be the problem.
[Google Pixel 8 Pro] HipKat:
What OS are you using?

If in Windows, open a Command Prompt and (if not in your command line) cd to C:\Android\platform-tools\ and run

adb start-server

adb devices

and see if your device shows up, then rescan with PF

EDIT: Just saw t he posts following yours.

I run Arch and have a drive with WIn11 on it almost specifically just to run PF and some work apps
[Google Pixel 8 Pro] Galaxea:
I don't remember getting this warning the last time I downloaded PixelFlasher.

Is this normal?

View attachment 6055861
[Google Pixel 8 Pro] badabing2003:
Please check OP
[Google Pixel 8 Pro] Galaxea:
Got it. Thanks.
[Google Pixel 8 Pro] DougMG:
Bitdefender has been doing this off and on for a couple of months now. A day or two from now after a couple of definition updates and it will stop for awhile.
[Google Pixel 8 Pro] Morgrain:
just fji, today Windows Defender also started to "indentify" your program also as malware and blocked it, which probably means that every other Windows user will also encounter this issue. Which will probably lead to a lot of people either not noticing that the program disappeared, or they will not use it.

View attachment 6057428
[Google Pixel 8 Pro] Morgrain:
I am aware of the false positives and read the OP, I merely wanted to note that not only some third-party anti virus programs give out a false warning, but Windows itself seems to have started doing that. Which is a tad more problematic, overall.

Anyway, thanks for the program.
[Google Pixel 8 Pro] simplepinoi177:
But that's why @badabing2003 stated to "Check the OP", and if you truly did, you'd see from the quote below (taken from the last bullet "If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post." from "the OP") in which I highlighted in orange for you........

note: Microsoft Security is a "Lazy AV companies".

So, in fact, Windows has not "...seems to have [just] started doing that" (or he wouldnt've put it in the OP already; which you supposedly have read), in actuality, it's been a long while that I have had to click "more info" and "run anyway" on my Windows 10 running every new version of PF for a long while now....
[Google Pixel 8 Pro] mac796:
Ok. I finally got around getting this pif deal figured out. I gotta say the pif tab in your app is awesome. Took me about 5 tries with get the freeman. I had to use that button to change the API to 25 to pass both.

Thank you very much for this.
[Google Pixel 8 Pro] HipKat:
Correct!! Once I set it to use 25, I started passing most FP's right away.

I have about 15 stored now
[Google Pixel 8 Pro] mac796:
The props that we keep for ourselves, obviously the ones we find that work off that Freeman deal. Do they get put in some kind of folder where they can't be picked again? I was just curious.
[Google Pixel 8 Pro] badabing2003:
Assuming that you're taoking about the favorites.

They get saved in one file favorites.json (in PixelFlasher working directory), which PixelFlasher loads when you open Pif Manager, and you can select any of them from the dropdown combo box.
[Google Pixel 8 Pro] mac796:
Yeah I mean the favorites. I was just wondering if they can be picked again, by someone else. Or do they get pulled out of the get the freeman pool?
[Google Pixel 8 Pro] badabing2003:
If I understand you correctly, what you select has no bearing on what others select, there is no cental management of pif assignments, from a set or large enough pool you're selecting a random print, others might land on the same print or not are totally a fuction of probability, which depends on the pool size as well as user size.
[Google Pixel 8 Pro] HipKat:
Fact, it's like saved Bookmarks for websites. Click the drop-down next to the heart and you'll see the ones you've saved
[Google Pixel 8 Pro] simplepinoi177:
You know....this brings to mind something for me....

if one felt so inclined to assist and/or share, could one be able to send someone this favorites.json of their own with multiple working FPs and have that other person be implementing & using it? Then could that favorites.json be passed around and such? Might create a whole sharing precedent/network -- but also create a whole level of spoonfed where it might just lead to (run PF, download this favorites.json, load up one of the FPs in there, profit).

Also, in cases like that of @HipKat where using your tool have found multiple working FPs and have their own private repository, maybe you should make an option to also output the favorites to their own individual pif.json so if a fp gets banana'd, one wouldn't need to wait to connect their phone to a computer and run PF to implement another pif.json from their favorites and could manually do it in the root explorer (of course they'd need to figure out placing the file in the right folder and restarting gms and/or simply rebooting, but yeah....). You're constantly updating and implementing features to PF, so apologies in advance if you have something like this available already....
[Google Pixel 8 Pro] badabing2003:
I'm strongly against the idea of sharing working prints or spoonfeeding.

I expect people to put the minimal effort to read up and understand what it takes to get a working print, and all it takes is few clicks.

If one can root, one can easily find a working print.

If they are not willing to put that minimal effort, I don't want to encourage and support that free loding behavior.
[Google Pixel 8 Pro] 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 8 Pro] simplepinoi177:
Oh absolutely agree 100%!

It was more just on understanding your program better and its capability (if one could pass around their own favorites.json -- does your program work that way?)....

That and my inquiry on making the prints found in favorites.json available without a PC (if can be output in a series of pif.jsons that can be manually copy/pasted just on the phone root explorer)...
[Google Pixel 8 Pro] 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 8 Pro] LeonHart23:
After Cleanup DG every check show NO INTEGRITY (I was using a working fp). What to do?

EDIT: wallet works even if Play Integrity show no label
[Google Pixel 8 Pro] badabing2003:
After Cleanup DG, run YASNAC once, or reboot.
[Google Pixel 8 Pro] LeonHart23:
I did it before posting, my bad. I just wanted to say everything back working couple hours after running spic/TB/play integrity check and rebooting/shutting off the device
[Google Pixel 8 Pro] guniens:
Hi @badabing2003

I've successfully unlocked my P8's bootloader with PF but I cannon't patch the init_boot img, I keep gettings this error:

2024-02-01 22:37:07 ERROR: Could not get file content: /data/local/tmp/pf_patch.log
Aborting ...

Aborting ...

I'm using latest PF version and latest OTA image, followed your steps on GitHub's page.

Here's the support file.

Thanks in advance!
[Google Pixel 8 Pro] V0latyle:
Doesn't look like you have Magisk installed on your device. It is necessary to patch the boot image. Install it using this icon

View attachment 6062826

And try again.
[Google Pixel 8 Pro] guniens:
Worked!

My bad I tought PF would do on it's own as per GitHub's page guide... it's late :sleep:

Thanks @V0latyle and @badabing2003
[Google Pixel 8 Pro] V0latyle:
IIRC Pixel Flasher is supposed to warn you if Magisk isn't installed, you must have ignored the warning!

A little detail on how this works;

The Magisk app not only acts as a "manager" for root, Zygisk, and Magisk modules; it also functions as a "patcher" to provide the initial root patch.

Pixel Flasher extracts the boot image (or in this case, init_boot) from the factory firmware and pushes it to your phone, then attempts to use ADB to command Magisk to patch the image.

Once Magisk produces a patched image, PF then pulls it back to your PC, and it becomes available in the boot images list.

You could do this all manually - unzip the firmware, extract the init_boot image, transfer to phone, patch with Magisk, copy patched image to PC, so on and so forth.
[Google Pixel 8 Pro] badabing2003:
Yeah, it's supposed to warn you and prompt you to install it, giving your the choice of Magisk to download / install.

But in this case it didn't.

I'd look at the code and see if I missed a check somewhere, it could be a regression introduced from recent changes.
[Google Pixel 8 Pro] guniens:
Hi again @V0latyle @badabing2003

I can confirm I didn't get the warn, 100% sure about that.

I got the warning on my P6 when I first rooted, that's why I didn't understand what was happening yersterday night
[Google Pixel 8 Pro] vegetaleb:
Hello

So I just updated the FW for the 1st time using Pixelflasher, though magisk root (not the app) is still on 26.4 instead of 27, how can update it without breaking something?
[Google Pixel 8 Pro] badabing2003:
Support file please.

I don't understand what exactky you are asking.
[Google Pixel 8 Pro] vegetaleb:
This
[Google Pixel 8 Pro] badabing2003:
I can't tell what you've done without seeing the support file.

If your rooted Magisk was on 26.4 and you used that to create a patch, why do you expect the created patch to be v27?
[Google Pixel 8 Pro] HipKat:
Jeez man, you see that big blue UPDATE thing? What do you think happens if you click on it?
[Google Pixel 8 Pro] vegetaleb:
That's why I am asking, back with my last rooted phone aka oneplus 7 pro , we shouldn't update magisk from the app itself because of the patch boot thingy. So now we can simply update in the app?
[Google Pixel 8 Pro] badabing2003:
Yes you can, or you could have chosen to create the patch with the Magisk app instead of rooted magisk as PF would have recommended.
[Google Pixel 8 Pro] guniens:
Hi @badabing2003, sorry for late reply.

After having manually installed Magisk via PF I solved the issue, however I'm sure I didn't get the prompt from PF to instal Magisk when needed.

Here's the support file.

Thanks!
[Google Pixel 8 Pro] badabing2003:
OK Thanks,

I'll look into it.
[Google Pixel 8 Pro] 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 8 Pro] ko3st:
- I have an unbranded pixel 8 pro.

- I did NOT use OTA but the factory image firmware from february 2024

14.0.0 (UQ1A.240205.004, Feb 2024 (Pixel 8 Pro)

Package Fingerprint: husky-uq1a.240105.004

Date: 2024-02-17 10:33:49

Firmware Fingerprint: husky-uq1a.240105.004

Firmware: C:\TEMP\husky-uq1a.240105.004-factory-498499a8.zip

Type: firmware

- Please understand that due to the fact that my (soft)bricked Pixel 8 Pro is unresponsive, most checkboxes are not available for me in Pixel Flasher v6.8.0.2

- By the way nobody is able to upgrade to Pixel Flasher v6.8.0.3by way of clicking the provides link in het About Pixel Flasher Window, since the link to the newest version seems to points to the "old" executable (which is the current version v6.8.0.2).

Attention:

I now remember, that when all was working fine, and I had the bootloader unlocked, all drivers were OK and so on..., that on the phone I always needed to manually click on the radiobutton at the top, before I could "see" the Pixel 8 Pro device in the Explorer Window on the PC.

Questions:

- Is this what is now the same thing what is preventing the phone from showing up?

- Or is this not relevant at this point?

- Is there anything I CAN do at this point?
[Google Pixel 8 Pro] badabing2003:
If you can put your device in bootloader or recovery mode (try the key combination) then it can be recovered.

If you can't, then it's not a soft brick, it would be a hard brick.

What do you see on the phone?

Perhaps it's not detected because you don't have the proper Google USB drivers installed (link in the PF's Help menu) or perhaps you have a bad cable / port.

As for PF saying that there is an update, but still not getting 6.8.0.3 it's because I forgot to increment the version in the application, you can ignore that,

Versions 6.8.0.0 -> 6.8.0.3 are identical as far as the code / app, the'yre just different builds to try and address MacOS not building on Github.

I'll work on that next.
[Google Pixel 8 Pro] ko3st:
What is that promising "the key combination"?

I see mothing on the phone it does absolutely nothing except when you plug it in the USB cblke you CAN hear Plon Pling (low high). So to me it seems not completely dead yet...
[Google Pixel 8 Pro] 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 8 Pro] badabing2003:
Fastboot key combinations | Android Open Source Project

source.android.com

How to use Android Recovery Mode to Fix Your Phone or Tablet | Digital Trends

Recovery mode is often indispensable for solving phone problems. This guide explains what it is and precisely how to access it on most major Android phones.

www.digitaltrends.com

What does Windows show as device in Device Manager when you connect your phone?

Have you installed the official latest Google USB drivers?
[Google Pixel 8 Pro] ko3st:
Press and hold Volume Up, then press and hold Power

and

Press and hold Volume Down, then press and hold Power

are known to me.

FYI: You can shut down some phones, by pressing all three (!) buttons at once and keep pressing them until it is switched off.

This is NOT an advisable method, but none the less :) .
[Google Pixel 8 Pro] speakeasy2:
I just used that one. I will try and older version and report back.