yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
Please, don't insult my intelligence.

That is totally not true.

Even if the application crashes or you have to kill it, you can still generate a support file by launching it again and hitting the support button.

Besides I had asked for support file before you had even mentioned a freeze.

And didn't you say that 6.9.1.3 was not crashing for you, why didn't you create support file with it.

What's your excuse there?

Move on, no sympathy points for you.

This is my last response to you, I don't have time for your nonsense.
[Google Pixel 8 Pro] HipKat:
Not to interrupt, but I Have a folder called Old. Whenever something new for my phone gets downloaded, like a Kernel, firmware version, or PF, I drop the older version into the Old folder.

I just looked, and I have every version of PF going back to 5.7.0.0 lol
[Google Pixel 8 Pro] ko3st:
- I downloaded the latest Pixelflasher.exe

- Google Chrome does not like to download *.exe files, so I manually overruled that.

- As soon as the exe file was downloaded in my Downloads folder, it immediately got deleted.

Please see picture.

View attachment 6092878This has not happened on this same Windows 11 dell laptop, when I downloaded any previous pixelflasher.exe file.

Can you suggest a solution?
[Google Pixel 8 Pro] ko3st:
Tried to download the same file with Firefox and I downloaded it to another folder (See picture).

View attachment 6092883

- On the same as always Windows 11 Dell laptop, I right-clicked the downloaded pixelflasher.exe

- As I inspected the properties of the downloaded pixelflasher.exe file, it got deleted automatically again... Very strange!

So now I have no PixelFlasher.exe file anymore :-(

Where can I download an older version of pixelflasher ?
[Google Pixel 8 Pro] ko3st:
I solved it by creating an exception rule in Windows firewall.

View attachment 6092896

All seems well now. :)
[Google Pixel 8 Pro] RYZONN:
I'm sorry if you took this all wrong, I had no idea I could remove the file even after the crash, I can do it again if it helps you and the community too, far from me wanting to cause problems, quite the opposite.
[Google Pixel 8 Pro] HipKat:
You didn't get a Warning MEssage in your Download window where you could choose to keep it?

I never get that on my Linuix Drive but the few times I d/'d it with Edge in Windows, Defender blocked it but I could choose to keep it
[Google Pixel 8 Pro] ko3st:
That's right, I did not get any Warning Message, after Chrome or Firefox finished downloading the temp file that represents the pixelflasher.exe.

- After the download is fully finished, in the final stage, when the temp file is parity checked and being renamed to the original filename, for a brief moment the exe is created in the Downloads folder on my Windows 11 Downloads folder...

- Almost immediately, Defender(?) intervenes, and classifies that exe file, and as a result, deletes it!

- I found a way to overcome This Behaviour.

- I could bypass that behavior by manually creating an exception rule, that defines a folder that must be trusted.

- In my case I created an exception for the root-folder "c:\platform-tools" and by definition, that specific folder, and subsequently all subfolders in it, need to to be trusted.

- Now, if I download an exe file into a sub folder called "pixelflasher" as in "c:\platform-tools\pixelflasher", it will not be deleted by Defender anymore.
[Google Pixel 8 Pro] zakizafri:
Hi. I’ve just got my 8 pro. I’ve read the op. Just one question which i think will be a stupid question. Do i just click the unlock button in pixelflasher to unlock my bootloader or i need to do something else? Sorry again for the noob question 🙏🏾
[Google Pixel 8 Pro] BABYFACE10:
Yes, it will wipe your data
[Google Pixel 8 Pro] zakizafri:
After that my bootloader will be unlocked right? No need to do anything else?
[Google Pixel 8 Pro] BABYFACE10:
Yes, you need to unlock the OEM BOOTLOADER IN SETTINGS TO. READ THE GUDIES YOU HAVE MANY OF THEM
[Google Pixel 8 Pro] zakizafri:
Okay thank you. I’ve read them, but not sure enough.
[Google Pixel 8 Pro] badabing2003:
Which part you're not sure enough?
[Google Pixel 8 Pro] Tulsadiver:
My windows 10 Dell started doing this as well a few PixelFlasher versions ago. I did an exclusion for the the entire paixelflasherwindows_2019.exe file in downloads folder. I have to delete the old one before I download the next update or it will rename it """"-2019 (2).exe and delete that.
[Google Pixel 8 Pro] zakizafri:
The part before i press the unlock button in pixelflasher. I’ve just need to turn on oem unlock in developer setting, connect to my computer then press the unlock button. Correct?
[Google Pixel 8 Pro] badabing2003:
Yes, and your device will get wiped.
[Google Pixel 8 Pro] zakizafri:
And the bootloader will be unlocked?

Thank you so much. You’re the best!
[Google Pixel 8 Pro] badabing2003:
If your bootloader is unlockable, Verizon for example is not.
[Google Pixel 8 Pro] zakizafri:
Thank you again 😁
[Google Pixel 8 Pro] 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 8 Pro] matmat07:
Hi, here are my logs. I seem to be having problems reading the OTA files :

Prop: com.android.build.init_boot.security_patch -> '2024-04-05'

Error: 'com.android.build.boot.security_patch'

❌ 2024-04-29 19:40:01 ERROR: Encountered an error while selecting boot.
Traceback (most recent call last):
File "Main.py", line 4006, in _on_boot_selected
KeyError: 'com.android.build.boot.security_patch'

This is with the current 6.9.3.0 version. Latest version of the platform-tool too.
[Google Pixel 8 Pro] badabing2003:
That particular error you can ignore.

I added extra reporting about the selected boot file, and it looks like I have missed a check if it is init_boot.

I'll have a fix shortly.

In any case that is harmless, you're just not getting the extra reporting, but it has no impact on the rest of the process.

You can ignore that error, or use 6.9.2.6 if it bothers you, or wait for next version.

However I do have a question for you.

What exactly are you trying to do, I see that you're trying to do a custom patch.

Why do you need a custom patch?

And you're choosing an already patched file to patch again?
[Google Pixel 8 Pro] matmat07:
With the last update, my phone got the OTA and I lost root. My goal was to get it back.

I restarted the app a couple time to try and diagnose something myself, I seemed to have other issues, maybe I just didn't know how to do it.

In any case, from what I understood, after browsing for the OTA file from google, I pressed on process to "extract" the init_boot file. After that, my only "patch" option was "patch with custom magick". At that point I got lost thinking it would be the img file destination. I just now see the message that asks for that img file.

I guess my question now would be how to get that file. I know how to do it manually, but I would have expected that part to be done on its own.

I ended up using magisk itself and flash with fastboot, that's what happened and got me confused.

Thanks for the app by the way, I know I got it to work back in december, I just forgot how since haha.
[Google Pixel 8 Pro] badabing2003:
v6.9.3.1 is on Github.

After processing the OTA image, you get boot file in the list (actually in your case init_boot)

To patch, you have to select the file, then you'd have all the patching enabled (Magisk, KernelSU, APatch) assuming that you have a device connected, and the device is in adb mode.

By selecting the stock entry in the boot list, PixelFlasher knows what you want to patch.

Custom Patch is if you want to patch a file that you want to provide, but you'd have to provide a proper stock file.

You can find where PF extracts the files by clicking on the explorer looking like button on the right.

But you shouldn't need to do that, that custom flash is for very rare special cases.
[Google Pixel 8 Pro] matmat07:
I can confirm those options are available to me now. I also couldn't delete entries in the past. Thanks again for the software
[Google Pixel 8 Pro] Galaxea:
I am trying to flash the latest software onto my wife's P6 but I get an error when I try to patch the file.

I have tried the OTA and Factory files - same error. I have the latest version of PF and ADB tools.

Please advise.

2024-05-04 12:27:16 ERROR: Could not push /storage/emulated/0/Download/boot_e7319b2b.img

Return Code: 1.

Stdout: adb: error: failed to read copy response

C:\Users\abc\AppData\Roaming\PixelFlasher\boot_images4\e7319b2b2d5db73149541ab0c9e68c812397a8fd\boot.img: 1 file pushed, 0 skipped. 333.2 MB/s (67108864 bytes in 0.192s)

adb: error: failed to read copy response

Stderr:

Aborting ...
[Google Pixel 8 Pro] badabing2003:
Can't tell, support file is incomplete.
[Google Pixel 8 Pro] Galaxea:
Please try this one. It is bigger than the other one.
[Google Pixel 8 Pro] badabing2003:
please try enabling the debug option and try again and generate support file.

it looks like file cannot be written to your device so that Magisk can patch it.
[Google Pixel 8 Pro] Galaxea:
This one is with DEBUG on. Thanks.
[Google Pixel 8 Pro] badabing2003:
Please don't modify the support file, I don't see any debug messages nor do I see other troubleshooting data that usually should be there.
[Google Pixel 8 Pro] Galaxea:
I never even opened it - sent it exactly as I found it. I will try again.
[Google Pixel 8 Pro] Galaxea:
Here is another one - unopened or edited.
[Google Pixel 8 Pro] Galaxea:
I tried to copy a file manually to the phone with ADB but that also failed, so I fiddled with USB ports and now it is working.

Sorry for the runaround.
[Google Pixel 8 Pro] roirraW "edor" ehT:
PixelFlasher v6.9.3.1 (latest at this moment).

It doesn't see any of the May firmwares as available to download through the tool. Support file attached, if necessary. Same happens with my Pixel 7 Pro. Tried quitting PixelFlasher, re-launching, un-plugging/re-plugging...

View attachment 6100568
[Google Pixel 8 Pro] badabing2003:
I have to add a refresh option.

Not to burden the system, it only refreshes once a day and only at startup.

If you look at PixelFlasher.json file, you'd see something similar to this.

{
"google_images_update_frequency": 1,
"google_images_last_checked": 1714847786,
}

google_images_update_frequency: is in days

google_images_last_checked: is when it was last checked (epoch)

You can find the json file by selecting Help menu | Open Configuration Folder

View attachment 6100578

If you want it to update now, you can do the following

Open PixelFlasher Working Directory

Exit PF

Delete google_images.json

Start PF

It should be updated.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Ah, I see, thank you! I'm glad to hear it's operating as expected, at least. Thanks for the workaround!
[Google Pixel 8 Pro] nikola1970:
Hello,

I want to flash latest firmware but I am wondering should I flash it to both slots? I never flashed to both slots, and I think other slot have very first pixel 8 pro firmware.

Thanks in advance 🙂
[Google Pixel 8 Pro] roirraW "edor" ehT:
It's a personal choice and also depends on if you're flashing the factory image or Full OTA Zip. I used to use the factory image, but the short version is that if you flash the factory image to both slots, only the most recently flashed slot will actually be useable.

So I started flashing the Full OTA Zip to both slots (it automatically switches slots when you flash the OTA, so just flash it twice, without any manual switching). This way, both slots are actually fully useable.

One thing I am wondering is if flashing the OTA to both slots for the 7+ years I might keep my phone might degrade the storage too quickly, so I'm considering going back to only flashing one slot, although I'll keep using the OTA.

Edit: As @badabing2003 pointed out below, the data partition gets a lot more wear and tear than the system partitions, so flashing the Full OTA Zip twice shouldn't really affect the storage life.
[Google Pixel 8 Pro] badabing2003:
What @roirraW "edor" ehT says, just flash OTA twice.

Data partition is the most used partition, which is common, and that's the only R/W

All other partitions are RO, so the wear shouldn't be signifcant (if any).

But if you're really worried, why not flash OTA 3 times (or once) once every 6 months or so and go back to flashing twice the rest of the times.

That should take care of the wear balancing.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! I'm not really worried, as I also had the same thought about the data partition having much more wear and tear than the static for a month system partitions.
[Google Pixel 8 Pro] nikola1970:
But my phone is rooted, I only flashed full images, never OTA.
[Google Pixel 8 Pro] badabing2003:
I'm not sure I follow the point.

Being rooted or not, is orthogonal to whether you want both slots flashed or not.
[Google Pixel 8 Pro] HipKat:
Ummm... what's up with this??

14.0.0 (AP1A.240505.004, May 2024)	Link	2465576160b9199d9356b22526366e423006bc3ce0d352b710562a873d9da7e5
14.0.0 (AP1A.240505.005, May 2024)	Link	6fd4a237bc7071482d5a28aa96c867fb2e8f133302ae853b25000b61cf82e190
[Google Pixel 8 Pro] Lughnasadh:
.004 is for T-Mobile, C Spire, US Cellular & Cellcom. .005 is global.

Google Pixel Update - May 2024 - Google Pixel Community
[Google Pixel 8 Pro] badabing2003:
To add to what @Lughnasadh provided, if you're on T-Mobile April release, and try to flash the OTA 14.0.0 (AP1A.240505.004, May 2024), it would fail, Google has set the date to March 15 in the OTA metadata, which would be a downgrade and fail.

There are ways around it, but be aware.
[Google Pixel 8 Pro] 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 8 Pro] HipKat:
I am on T-Mobile, but I don't think the April OTA I used was a T-mobile variant. There's just one April d/l and I never flashed the patch that came out on 4/15

14.0.0 (AP1A.240405.002, Apr 2024)
[Google Pixel 8 Pro] badabing2003:
If you flashed the first April patch you'e be at 0405

Unfortunately google embedded March 15 in the metadata of the May T-Mobile OTA.

There are few ways you can tackle this.

Flash the May factory image instead of OTA

Modify the date in metadata in the May OTA and see if that works, I have no idea if it does or does not, but it's harmless to try as it cannot mess up your device.

The way you do it is download the OTA and open it in 7-zip

Navigate to META-INF\com\android\

Edit metadata file, you'd see something like this:

View attachment 6101033

As you can see 1710527066 is March 15, and it will be seen as a downgrade and fail.

1712337936 would be a good value to replace with.

If The method in #2 does not work, you can create a downgrade patch of your boot.img, flash that first and then install the OTA.

See details here.

You can unpack T-Mobile OTA and the global OTA with payload-dumper-go, and compare the different images, the ones that are different (probably radio), just flash those after flashing global OTA, you can do this with custom flash in PF.
[Google Pixel 8 Pro] bsg411:
As I read this again... How is it that the characters 1710527066 equal a date of March 15 2024?

Edit: nevermind I googled it and found a timestamp converter. Thanks.
[Google Pixel 8 Pro] HipKat:
Yikes

If I flash the Factory Image for May and let it ride, do you think I'd be OK to wait til June to go back to OTA's or should I do all this above??
[Google Pixel 8 Pro] HipKat:
I was gonna ask the same thing lol
[Google Pixel 8 Pro] badabing2003:
I say try the OTA, I know for a fact that it's borked for Pixel 7 Pro (Cheetah) but I'm not sure if it is for Pixel 8 Pro

The metadata.pb file looks right even though metadata is not.

No harm done if you try.

Factory image should be fine, we used to do factory for ages before we moved to OTA :)

The only downside of factory is if anything goes wrong, it's a bit more hassle to fix, compared to OTA when it goes wrong, the active slot remains functional.

Flashing 2nd Apirl update on top of the 1st April update works, but it won't make a difference for flashing May update, afterwards, as the problem is in the May update.
[Google Pixel 8 Pro] HipKat:
I realized that after I posted and removed that line but you replied too soon lol
[Google Pixel 8 Pro] Pfeffernuss:
So flash once, reboot, flash again is something completely different than the "flash both slots" option (checkmarked by default)?

I assumed that checkmark made sure both slots would be populated by the same firmware :)
[Google Pixel 8 Pro] badabing2003:
That checkmark only applies to factory image flashing, and is actually disabled when flashing OTA, so is the checkmark to flash to the inactive slot, OTA by design always flashes to inactive slot and only switches slots if the flashing + boot was successful. (a good robust system, which is why it now recommended over factory flashing).
[Google Pixel 8 Pro] nibera:
Hi, I would like to root my pixel 8 pro (currently installed May patch, Italian version) via pixelflasher, then install magisk and create the list of the app in the denylist, and then install the module via magisk for automatically recording phone calls without any registration notice, can anyone show me a guide to avoid having problems? Thank you
[Google Pixel 8 Pro] badabing2003:
To use PixelFlasher follow the guide in the main thread or GitHub (both linked in my signature and OP)

To learn about manual steps using command line tools any of the guides linked in PixelFlasher's help menu.
[Google Pixel 8 Pro] HipKat:
The OTA flashed fine. No problem!
[Google Pixel 8 Pro] HipKat:
Uh oh.

Houston, we might have a problem.

What would cause this after the newest update?
[Google Pixel 8 Pro] badabing2003:
Thankfully Houston, the problem is not in the rocket, it's at the control center :)

Play Integrity Fork disabled v8
[Google Pixel 8 Pro] HipKat:
Doh!

How the heck? …weird
[Google Pixel 8 Pro] badabing2003:
Update Release:

May 17, 2024 v6.9.5.0 change log:

Added Pixel 8a (akita) support.

Updated Pixel device end of life dates based on Google's published data.

Added an option to refresh Google Images download links, useful on release days when you want an immediate refresh.

Memory improvements when building Google Images list.

Added additional troubleshooting debug messages when a device is not detected.

Minor bug fixes and improvements.
[Google Pixel 8 Pro] nibera:
Hi, I wanted to ask if there is any user also available for a fee, via remote or with a complete step by step guide via pixelflasher, I don't know English except via Google Translate, who can:

1) unlock the pixel 8 pro

2) root the pixel 8 pro

3) install the module to record incoming and outgoing phone calls automatically.

at the moment the pixel 8 pro European model with May patches.

Thank you
[Google Pixel 8 Pro] badabing2003:
Translate the guide and follow it, you should be fine, no need to pay anybody.

All questions about things you're not sure about.
[Google Pixel 8 Pro] nibera:
but I can't find the guide with pixelflasher, can you post it to me? Thank you
[Google Pixel 8 Pro] badabing2003:
Read the first post of the thread, or check my signature.
[Google Pixel 8 Pro] rester555:
Are the instructions for installing Apatch in your documentation? Or is it as simple as loading the apk file in the root app option of your tool? Does your tool inject kernelpatch?

Also being unfamiliar with Apatch, there is talk about setting a Superkey for automatic patching. Is this a function separate of PF? I misread, this is built into the app manager.

EDIT: after reading the documentation for Apatch it seems the app does like magisk and patches the boot.img (not init_boot.img) and then the user has to flash the patched boot image. I am guessing you just allow the apk to be installed and then patch the modified boot.img in your tool?
[Google Pixel 8 Pro] badabing2003:
The app's support of APatch or KernelSU is no different than what is supported for Magisk, you can do as little as you want or as much as you want for the end to end process.
[Google Pixel 8 Pro] nibera:
Hi, I had a problem, I was with Android 15 beta 2.1 with bootloader unlocking and root, everything worked fine, then I received a. Android update and the root went away, I reinstalled magisk, and now I don't know how to make the root work again, any suggestions?
[Google Pixel 8 Pro] badabing2003:
How did you root the first time?

Just repeat the process.

Follow the guide, nothing is different.
[Google Pixel 8 Pro] nibera:
but do I lose all the data?
[Google Pixel 8 Pro] badabing2003:
Did you read the guide?
[Google Pixel 8 Pro] nibera:
yes yes, I just wanted to understand if by just patching the OTA with magisk inside and then flashing, will I lose the data or not? already having the phone unlocked.
[Google Pixel 8 Pro] badabing2003:
I'm afraid of you can not detect the phone in one of those modes, then you'd have to RMA

Sorry about your troubles.
[Google Pixel 8 Pro] gigaboss:
No worries it's probably my fault for rebooting while in fastboot
[Google Pixel 8 Pro] badabing2003:
Sadly modding has it's risks.
[Google Pixel 8 Pro] gigaboss:
I was able to return it, fingers crossed for the next one haha, will receive in two days :)
[Google Pixel 8 Pro] supermansaga:
It is safe to flash from 14.0.0 (UD1A.230803.022.A4, Sep 2023, US-Emerging/G-store,CA,TW,AU,Fi) to 14.0.0 (UD1A.230803.041, Oct 2023). Phew. The eSim transfer doesn't seem to work for all the carriers.
[Google Pixel 8 Pro] almahix:
I'm eager to learn to use your app. I've tried it, but everything gis grayed out and I won't do anything. What imperative first step am I missing?
[Google Pixel 8 Pro] badabing2003:
Check the main thread or GitHub for usage, if it is still not clear, ask.
[Google Pixel 8 Pro] stu5797:
Thank you! This made rooting my phone so easy! This was really cool and fun to use! I was looking for a video on how to use pixel flasher to easily install monthly updates and keep root, etc? Any one know of any or have directions to do this?
[Google Pixel 8 Pro] badabing2003:
Now that you've gone through it and know how it works and how easy it is, you can make a video, why would you still need to look for one?
[Google Pixel 8 Pro] stu5797:
Is it the exact same process to update?
[Google Pixel 8 Pro] badabing2003:
Yes
[Google Pixel 8 Pro] minhgi:
I have used this app to root my p6p, p-tablet, p8p, and p2xl....

It's a must have app for rooting, especially on pixel devices. Make life so much easier.
[Google Pixel 8 Pro] Ultimoose:
Just make sure you uncheck the Wipe box ;)

And thank you for about the 4th time/phone for this app. I can ADB but I'm lazy and this fits right in with my lazy.
[Google Pixel 8 Pro] Jose.pH:
I have to try it from my home PC because in the one I use at work I can't change the USB drivers because it requires the administrator, in fact when first restart PixelFlasher doesn't detect the phone
[Google Pixel 8 Pro] byproxy:
worked great for me!!
[Google Pixel 8 Pro] Jose.pH:
yeah perfect for me
[Google Pixel 8 Pro] aaronc_98:
Delete d
[Google Pixel 8 Pro] badabing2003:
Read OP
[Google Pixel 8 Pro] HipKat:
You've been a member here for 13 years. Surely you know how to start at the beginning and read the first posts that always explain everything
[Google Pixel 8 Pro] aaronc_98:
Okay okay I got it. That's enough. Thank you 🙂
[Google Pixel 8 Pro] badabing2003:
As a courtesy one time only, I'll answer you, I will not answer queries that are clearly stated in the OP.

View attachment 6110134
[Google Pixel 8 Pro] nibera:
OK thank you