yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] Ultimoose:
This is so helpful to everyone OP. I remember finding this for my last pixel when I needed to push an update and giving it a shot and was just amazed and thought this is going to save so many people new to rooting so many problems and questions. Far less "I think I bricked it, can someone help" posts for sure with tools like this.
[Google Pixel 8 Pro] speakeasy2:
My p8p was able to be rooted by pixel flasher, but when going to the beta software i selected wipe all data and when after selecting yes to the prompt. it went through the process for flashing the beta, but nothing was erased. did this happen to any one?
[Google Pixel 8 Pro] Lughnasadh:
What version of Platform Tools were you using? There may be a bug in the current 34.0.4 where it doesn't wipe. Seen a few similar reports as well.
[Google Pixel 8 Pro] jcp2:
OK. I think Ive got it now. Last question, if I flashed Nov. OTA to both slots and they both boot fine, next month I need only flash The full OTA to 1 slot, or both? Would it not be easier to just flash the full firmware to active slot every month going forward, leaving an older working OS on the inactive slot?
[Google Pixel 8 Pro] badabing2003:
The minute you flash firmware, the other slot becomes unbootable (not brick).

Next month if you only flash OTA once, only one slot will be bootable, the other won't because for both to be bootable, they have to be on the same version .
[Google Pixel 8 Pro] jcp2:
Ok, I'll have to get used to flashing the OTA file to both slots every month then. Thanks
[Google Pixel 8 Pro] badabing2003:
New Release:

Nov 29, 2023 v6.3.0.0 release

New feature: Process build.prop, browse for the build.prop and it will extract PIF relevant fields, no fancy checking of dates or anything, if it is in there it will extract the values.

Added Magisk module uninstall / restore functionality.

Added PlayIntegrity API checking, can use one (or more) of the three apps from Playstore (user has to install the app)

Play Integrity API Checker (less reliable than the other two).

Simple Play Integrity Checker

TB Checker.

pif.json editing automatically kills the com.google.android.gms.unstable process, no need to reboot.

Magisk Management UI improvements

Bug fixes and improvements
[Google Pixel 8 Pro] badabing2003:
Latest Release Changelog:

Dec 02, 2023 v6.3.1.0 release

When processing build.prop extract values from ro.system.* and ro.product.product.* if ro.product.* values are not found, just like @osm0sis script does.

Bug Fix: On Linux, set permissions to readable before attempting pull.

Dec 02, 2023 v6.3.0.4 release

Support for @osm0sis Play Integrity Fork which uses a different path for the print file: /data/adb/modules/playintegrityfix/custom.pif.json

Dec 02, 2023 v6.3.0.3 release

Make Magisk dialog resizable

Add support for PlayIntegrityFix-resetprop

Dec 01, 2023 v6.3.0.2 release

Add debug message for module troubleshooting.

Handle unpdateJson entry for modules on Linux / Mac

Nov 30, 2023 v6.3.0.1 release

Update pif.json editing to use the one in /data/adb/pif.json, Playintegrityfix changed the location in version 14.0 beta

Bug Fix: #125, handle exception when a module's update link is broken.

Other silly oversight bug fixes.
[Google Pixel 8 Pro] cmh714:
You Sir, are an animal!!! TY for your contributions!
[Google Pixel 8 Pro] Aphex13:
Anyone tried flashing the Dec OTA yet? I'm about to be the guineapig if not...
[Google Pixel 8 Pro] bjevers:
Yes, worked fine.
[Google Pixel 8 Pro] HipKat:
Always does
[Google Pixel 8 Pro] saluzzo997:
Hi everyone, I'm on November stable and I'd like to upgrade to the new December version, I'm using a custom kernel and I have root permissions. What should I do to update with Pixel flasher without problems? Could I keep root permissions? Thanks in advance for your help
[Google Pixel 8 Pro] HipKat:
READ.THE.OP

Sorry, but man, really, come on. ALL this is explained in the OP
[Google Pixel 8 Pro] saluzzo997:
You're right, I'm so sorry
[Google Pixel 8 Pro] HipKat:
It's OK, it just happens often where someone will come in and ask a question that's in the first posts
[Google Pixel 8 Pro] jlokos:
I'm not sure this is the issue, but you are using Android Platform Tools Version: 33.0.3; try updating to 34.0.5 and see if that works. I had to do that on the November update.
[Google Pixel 8 Pro] HipKat:
Actually, I checked the version and it says December?? But I never saw any files get installed. Something isn't right. I'll see what Badabing says

That's a good idea though
[Google Pixel 8 Pro] banshee28:
Yea I had the exact same issue a while back where v 33.0.3 does not actually flash. I installed 33.0.5 and its been fine since. Sounds like the issue!
[Google Pixel 8 Pro] banshee28:
Just updated using latest versions to Dec and all is good!

Diggin the new slot# and rooted icons :LOL:
[Google Pixel 8 Pro] HipKat:
But when I check the version it says December update....

Anyway I'm back on Arch. I'll switch back to Windows later and update platform tools
[Google Pixel 8 Pro] banshee28:
Nice, I used to run Arch, but now on Mint. Have used this setup for the last 6 months or so.

** I see you were using Windows, cool.
[Google Pixel 8 Pro] supermansaga:
I used Pixel Flasher 6.3.1.0 with platform tools 34.0.5 and upon finishing the process, the following lines appear and I am stuck in the starting menu. But then I choose to restart and it seems to work after all....Not sure what to make of it. Thanks

2023-12-06 23:50:04 Getting device: 38201FDJG001ZK state ...

Currently the device is in ERROR mode.

2023-12-06 23:50:05 Getting device: 38201FDJG001ZK state ...

Rebooting device: 38201FDJG001ZK to bootloader ...

Updating connected devices ...

2023-12-06 23:50:07 ERROR: Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 3527, in _on_flash

File "modules.py", line 3291, in flash_phone

AttributeError: 'NoneType' object has no attribute 'get_current_slot'
[Google Pixel 8 Pro] Morgrain:
Are you sure that you are actually on December now?

Maybe your device fell back on the other slot
[Google Pixel 8 Pro] HipKat:
I use Arch primarily, but have Win11 on a separate drive - so not a true Dual-Boot, that I use for some things, work programs, games, etc and PixelFlasher just seems to work better on Windows for me
[Google Pixel 8 Pro] HipKat:
Similar to mine, but I didn't get stuck, it just rebooted
[Google Pixel 8 Pro] Aphex13:
Everything worked well for me on PixelFlasher 6.3.1.0 and Platform Tools 34.0.5. I flashed the OTA with no errors. I do like the more verbose output after flashing is finished...
[Google Pixel 8 Pro] Morgrain:
I also used the latest Pixel Flasher and Platform Tools (34.0.5), used the latest OTA files and my phone updated without errors (make sure you guys are using cables that work on ADB and a good PC slot, those can often bug. Once you find a cable and USB slot that work, never change it again).

Thanks again for this great tool. Makes the process easy and fast.

Btw my flashing took 580 seconds long, curious to know if other people have faster/the same/longer loading/flashing times
[Google Pixel 8 Pro] badabing2003:
No issue there, your device is fine.

As you can see up to that point everything went fine, the last step is to reboot to system.

PF waited 90 seconds to see if your device was booted properly to system, and then it timed out.

It either took longer than 90 seconds for the phone to be back up after flashing (it could happen) or it was unplugged.

Either way if the phone booted to system, then you're good to go.

That is not an issue, I still use 33.0.3 and have not run into any issues.

You mean 34.0.5, but again, there is no issue with 33.0.3, either is fine.

This is a totally different issue.

The phone rebooted to bootloader so that it could be flashed, but was no longer detected.

In the next version there will be a clear message about what happened and how possibly it could be mitigated

ERROR: Your device is not found in bootloader mode.
If your device is actually in bootloader mode,
hit the scan button and see if PixelFlasher finds it.
If it does, you can hit the Flash button again,
otherwise there seems to be a connection issue (USB drivers, cable, PC port ...)
[Google Pixel 8 Pro] HipKat:
no, the system is fine. The process was just way different than I’ve ever seen before. That unpacking or whatever it is where it was going one percentage at a time, I’ve never seen that, and the reason it timed out is because after it rebooted, you know, the screen turns off, and I was waiting to see if it was gonna do anything else and when it didn’t, I turned the screen on and it was waiting for me to toggle permissions for USB debugging and access. Which is why it timed out.

But you can see that instead of the regular 280 seconds or so, it took almost 620 seconds, I think it said
[Google Pixel 8 Pro] badabing2003:
That percentage thing is what you get when you flash OTA, which is streaming the update as opposed to firmware flashing where it flashes each partition separately.

And strangely enough it goes to 94% and completes, I have never seen it 100% displayed, but that is probably a bug in the percentage reporting code (Google's)

OTA flashing is slower than firmware, but safer and better, 500 - 600 seconds is normal, that includes waiting for the device to be detected in system (in your case that was 90 seconds, so it actually took 530 seconds)
[Google Pixel 8 Pro] HipKat:
That’s what it is. I’ve always flashed the image instead of the OTA. It was something you had posted that got me to switch to the OTA.

Good to know, man!
[Google Pixel 8 Pro] supermansaga:
I have Android webcam now so I hope it was successful. But as Badabing noted, they would update PF in the next version to address some of the issues. I am just curious if I should re-flash once the new version is out.
[Google Pixel 8 Pro] jlokos:
Thanks. Worked like a charm; updated to December using OTA, patched image and all is well.
[Google Pixel 8 Pro] badabing2003:
New Release:

Dec 08, 2023 v6.3.2.0 release

Added Dump Screen XML (uiautomator).

With SPIC and Play Integrity Api Checker apps, when they hit quota limits, detect and report.

Added Playintegrity testing using Play Store (Developer options need to be enabled. First run takes longer as PixelFlasher tries to find the coordinates of the elements).

Added a setting to disable Firmware / OTA image hash validation, useful for firmware images that are for Pixel devices (example CalyxOS) but don't follow Google's naming convention.

Detect and report cases where a device rebooted into bootloader mode is not detected by the PC, provide suggestion on how to fix / continue.

Make the Magisk management window resizable and remember and load last size on startup.

Support for older Pif modules PROPS-v2.1 and PROPS-v2.0 as they store pif.json in a different location.

Improve pif.json extraction by detecting and using (if need be) ro.product.vendor.name ro.product.vendor.device ro.product.vendor.manufacturer ro.product.vendor.brand ro.product.vendor.model ro.vendor.build.fingerprint ro.vendor.build.security_patch

add pif print BUILD_ID extraction.

Other minor improvements.
[Google Pixel 8 Pro] lbtaylor198401:
I don't know what i'm doing wrong i'm getting this error.

2023-12-09 15:22:13 ERROR: Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 3549, in _on_flash

File "modules.py", line 2857, in flash_phone

TypeError: argument of type 'NoneType' is not iterable
[Google Pixel 8 Pro] badabing2003:
New Release:

Dec 09, 2023 v6.3.3.0 release

When selecting build.prop to generate pif.json, you can now do multi-select, PixelFlasher will process them in a priority order based on the filename. build.prop being the highest priority.

Added Auto Copy to Clipboard which automatically copies the generated pif.json content to clipboard.

Added Auto Push pif.json which automatically pushes the file to the device and kills GMS process (after generated build.props processing).

Added Auto Check Play Integrity which automatically triggers the selected Play Integrity checker after editing or auto-pushing pif.json.
[Google Pixel 8 Pro] supermansaga:
Just used 6.3.3.0 and platform tools 34.0.5 and ran into the following errors. Even when the % seems to not have reached 100%, but just 94%, it appears it also says, "Done script flashing." Back on the phone, it again got stuck at the boot menu, so I manually pressed the power button to reboot. Upon reboot finish, it seems the update was successful. Not sure what to make of this. Thanks.

serving: 'D:\My software\@Android\Android 14 P8P (UD1A.231205.015, Dec 2023) (OTA Image)\husky-ota-uq1a.231205.015-c52b44d3.zip' (~93%)

serving: 'D:\My software\@Android\Android 14 P8P (UD1A.231205.015, Dec 2023) (OTA Image)\husky-ota-uq1a.231205.015-c52b44d3.zip' (~94%)

Total xfer: 2.00x

2023-12-11 11:14:42 Done script flashing!

Sleeping 10 seconds ...

2023-12-11 11:14:52 Getting device: 38071FDJG009M6 state ...

Currently the device is in ERROR mode.

2023-12-11 11:14:54 Getting device: 38071FDJG009M6 state ...

Rebooting device: 38071FDJG009M6 to bootloader ...

Updating connected devices ...

2023-12-11 11:14:56 ERROR: Your device is not found in bootloader mode.

If your device is actually in bootloader mode,

hit the scan button and see if PixelFlasher finds it.

If it does, you can hit the Flash button again,

otherwise there seems to be a connection issue (USB drivers, cable, PC port ...)

Aborting ...

2023-12-11 11:14:56 INFO: Flashing was aborted.

This could be user initiated or a problem encountered during flashing.

2023-12-11 11:14:56 ERROR: Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 3554, in _on_flash

AttributeError: 'NoneType' object has no attribute 'get_device_state'
[Google Pixel 8 Pro] badabing2003:
Your device is not detectable in bootloader mode, you probably are no longer rooted.

Could be USB driver , cable, port ...
[Google Pixel 8 Pro] supermansaga:
That's fine. Don't plan to root anytime soon. It's a brand new P8P. But the fact that the update % never got to show 100%, despite saying, "done script flashing".... Is that ok? Thanks
[Google Pixel 8 Pro] badabing2003:
Yes, I always see up to 94 % never 100,

I suppose it's a bug in the progress calculation in Google code.
[Google Pixel 8 Pro] iestynapmwg:
I'm new to pixel flasher, manually flashed and rooted when i first got my P8P last week, but figured i'd check it out...

When i start pixel flasher (6;3;3;0) there are a few error messages in the console window:

023-12-11 19:55:37 ERROR: /bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq

2023-12-11 19:55:37 ERROR: Android Platform Tools version is not available or is too old.

For your protection, disabling device selection.

Please select valid Android SDK.

I'm on arch, using the latest android tools package available there. Which has been flagged as out of date, but only by a month or so. Is 34.0.4 really too old?

The message seems to imply i can continue using this old version as long as i "select valid Android SDK." Where do i go to do this?

Any clues about the first error message, or can i safely ignore it?

Thanks!
[Google Pixel 8 Pro] badabing2003:
Take a look at this ticket.

The issue is addressed, you'd have to add an exclusion.

As for Platform tools, use PF's links to download from Google 34.0.5 (the latest) 34.0.4 has issues.
[Google Pixel 8 Pro] HipKat:
Your SDK version is fine.

I use Arch, also but I haven't had success with PF so I reboot to a Win11 Drive and use it there without issues.

Not sure why I can't get it to work with Arch -actually Garuda, other than my build has been glitchy lately and I need to reinstall the OS.

I might try pure Arch w/KDE
[Google Pixel 8 Pro] iestynapmwg:
Ok, it seems i need to add "libreadline*" in the settings to not use that library. Which brings me to the next question: in the settings dialog box there's no "save" button or anyhting of that sort. How do i make any changes to the settings "take"? Simply closing the window throws out any settings i've altered, as re-opening the settings shows everything is back to the original defaults.
[Google Pixel 8 Pro] badabing2003:
How are you closing the window? there's OK and Cancel buttons,

OK saves it, cancel just cancels the changes.

PixelFlasher/images/advanced-options.png at main · badabing2005/PixelFlasher

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com
[Google Pixel 8 Pro] iestynapmwg:
As i mentioned in my last post, i don't see a "save" button. There's no "cancel" button either. The only opton i have is to use the window manager's close button. See the first screenshot attached.

Your screenshot shows a lot more below the bottom of my window. If i drag the window up, there's no more off the edge of my screen. No scrollbar, either. See the second screenshot.
[Google Pixel 8 Pro] badabing2003:
What is your screen resolution?
[Google Pixel 8 Pro] iestynapmwg:
1600x900

Just been playing around with the settings window and there are no resize handles either. It's a fixed 736x874. The main app window is resizable without issue, even if i make it taller than my display resolution. No scroll bar if i make it smaller, though.
[Google Pixel 8 Pro] badabing2003:
I see,

With wx.python it is really PITA to have the pane scrollable with the widgets in it.

It's been asked before and I couldn't get it working nicely.

Even if I place scroll bars, it clips as soon as you resize.

I'll take another stab at it,

In the meantime you can edit it directly in the PixelFlasher.json file

In help menu, select Open Configuration Folder

Quit PixelFlasher

Edit PixelFlasher.json file, find and modify the line

"delete_bundled_libs": "libreadline.so.8",

Save

Start PixelFlasher
[Google Pixel 8 Pro] iestynapmwg:
That option in the help menu didn't do anything, presumably because the default entry in the settings screen for "Linux File Explorer"is blank. But the console output in the main window does tell me where that file is located, so i was able to edit it and change at least the libreadline part.

It seems to be working now! At least, it finds my phone, etc., i haven't tried flashing yet. I can probably figure out how to manually change other settings in the json file until the settings window is fixed. Thanks for your help!
[Google Pixel 8 Pro] jdkruzr:
This is also what just happened to me. If you look in the dropdown it doesn't see it although the phone is in fastboot. Hitting Scan again doesn't help.

ETA: the problem is that I didn't have the Android USB drivers installed for Windows. All I did was download platform tools and give it to PixelFlasher.

ETA2: since I already had a patched init_boot, I just flashed that and it came up fine. Was able to enable Zygisk. What I'm not clear on yet is whether or not as a normal part of the flashing process it already made sure e.g. Google Pay and such are still working (I don't know what that's called, "Play Integrity" sounds like it might have something to do with it but I can't tell from context)
[Google Pixel 8 Pro] badabing2003:
I'm sorry without a support file i can't tell you if it is or it isn't the same issue nor i can suggest a resolution.
[Google Pixel 8 Pro] jdkruzr:
Thanks, I updated the post to reflect that I didn't have the fastboot Windows driver installed. Is SafetyNet etc. good to go after a normal Magisk patch install?
[Google Pixel 8 Pro] badabing2003:
You need the PlayIntegrity Fix, safeynet is no longer good.

See the excellent thread by @V0latyle here.
[Google Pixel 8 Pro] cmh714:
Wait a second....didnt we "all" have to switch back to SafetyNet Fix v4 from Chiteroman a week or two ago??? or is PIF working again? Fun with Google!

TIA!
[Google Pixel 8 Pro] supermansaga:
When I use remote assistance program Team Viewer, the resolution of pixel flasher could be wonky and sometimes one can't find the console window to see progress.
[Google Pixel 8 Pro] badabing2003:
You've got it reversed.

Sorry can't do much there, its the libraries.
[Google Pixel 8 Pro] A.Priori:
Would pixelflasher allow me to update easily if I initially used it to root etc?
[Google Pixel 8 Pro] badabing2003:
Yes

see the main guide and I suggest you upgrade using full OTA
[Google Pixel 8 Pro] DRatJr:
Just as a refresher for my P8Pro... to update I can just download factory image. Patch it. Then flash and keep data. Then I'd have all my stuff still except an updated firmware right? Wouldn't have to worry about anything else?
[Google Pixel 8 Pro] simplepinoi177:
Yes....just make sure you have "Keep Data" checked....

badabing2003 and PF truly keeps it simple that you "wouldn't have to worry about anything else"...
[Google Pixel 8 Pro] badabing2003:
I'd go with full OTA instead, much safer.
[Google Pixel 8 Pro] DRatJr:
I figured I just don't use it just long enough to forget some of the better aspects about it and need a lil refresher lol. Thank you.
[Google Pixel 8 Pro] illyrande:
Hello,

I flashed my Pixel 8 pro with PixelFlasher as I did in October, the flash went well until the end but now it is in bootloop.

View attachment 6044600

View attachment 6044602

it reaches this stage but then restarts, and has been doing so for over thirty minutes.

Am I missing something? And above all, what can I do to get it working again, please?
[Google Pixel 8 Pro] Homeboy76:
Please, attach the support file!
[Google Pixel 8 Pro] simplepinoi177:
@illyrande , from the OP...
[Google Pixel 8 Pro] iestynapmwg:
I just tried flashing the December OTA, and after flashing and rebooting, Pixelflasher couldn't see my phone. This is reported in the console:

-----------

2023-12-16 09:46:35 Getting device: 38230DLJG0022T state ...
Currently the device is in recovery mode.

2023-12-16 09:46:35 Getting device: 38230DLJG0022T state ...
Rebooting device: 38230DLJG0022T to bootloader ...
Fastboot waiting device: 38230DLJG0022T for bootloader ...
device: 38230DLJG0022T is now in bootloader mode.
Updating connected devices ...

2023-12-16 09:46:47 ERROR: Your device is not found in bootloader mode.
If your device is actually in bootloader mode,
hit the scan button and see if PixelFlasher finds it.
If it does, you can hit the Flash button again,
otherwise there seems to be a connection issue (USB drivers, cable, PC port ...)

Aborting ...

2023-12-16 09:46:47 INFO: Flashing was aborted.
This could be user initiated or a problem encountered during flashing.

2023-12-16 09:46:47 ERROR: Encountered an error while flashing
Traceback (most recent call last):
File "Main.py", line 3554, in _on_flash
AttributeError: 'NoneType' object has no attribute 'get_device_state'

2023-12-16 09:47:40 User initiated Scan

2023-12-16 09:47:40 Scanning for Devices ...
No Devices found.

2023-12-16 09:51:15 Creating support.zip file ...
Saved support file to: /home/conrad/Downloads/support_2023-12-16_09-51-03.zip

--------------------

So it looks like it found my device in bootloader mode at 2023-12-16 09:46:35, then updated connected devices and at 2023-12-16 09:46:47 threw the error. I hit the scan button as suggested, but still no luck.

At a command prompt i typed "fastboot devices" and my phone is definitely there and connected:

$ fastboot devices
38230DLJG0022T HP Truevision HD

(though why it always shows up as "HP Truevision HD" i have no idea).

I've attached the support file in case it helps any...

Thanks!