yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] badabing2003:
Update Release:

June 04, 2024 v6.9.6.0 change log:

#204 Fix Pyinstaller issue, thanks to PR from @cjshearer.

PIF Import favorites can now import recursively including subdirectories.

Added Device | Check otacerts menu option to quickly check if the ROM is signed.

Sync banned kernel list with @osm0sis published list.

Improved exception handling

Improved debug messages for troubleshooting

Fix timing issue for a corner case cleanup before unzipping is completed.

AVBTool improvements.
[Google Pixel 8 Pro] nibera:
Hi, everything was done according to the guide, no problems, everything is ok. I sincerely thank you and apologize if I sometimes break the links.
[Google Pixel 8 Pro] nibera:
I also noticed last time, that after every flash with root, it creates a folder on the device with two files inside called:

magisk_patched_27000_ecc.....img

init_boot_ecc......img

what are they for ?
[Google Pixel 8 Pro] bdr127:
Those are the original boot image and the boot image patched by Magisk.

If you do the process manually (the old fashioned way... Ha!), you have to extract the boot image from the main big image, give it to Magisk, Magisk patches it, and then saves it in the same folder with a name that includes "magisk_patched".

PixelFlasher just utilizes the same tools under the hood but makes it so you don't have to manually do everything.
[Google Pixel 8 Pro] nibera:
Hi, I understand, thanks.

While flashing the OTA image with magisk root, I noticed that the flash procedure with pixel flasher went from slot A active at that moment to slot B, but now that I'm on slot B, what remains on slot A?
[Google Pixel 8 Pro] badabing2003:
Whatever you had before switching, if it was rooted, then it would be rooted.

Keep in mind that there are no two data slots, only one.

If you had root on slot A and you want it unrooted, all you have to do is select the stock init_boot from the list and Flash Boot (not Flash Pixel Phone) while on slot A
[Google Pixel 8 Pro] nibera:
Got it. Thank you
[Google Pixel 8 Pro] nibera:
Hi, I noticed that after the last update of the pixel flasher, that the Microsoft Defender Antivirus program always deletes the flasher program, any solution?

EDIT: I think I solved it by excluding the file from threats to the PC.
[Google Pixel 8 Pro] Galaxea:
I just tried to update from AP1A.240405.002 to AP2A.240605.024 and it failed twice. It got to 47% and ended.

Current slot:

Comparing the current slot with the previous active slot ...

❌ 2024-06-11 20:24:02 ERROR: It appears that OTA flashing did not properly switch slots.

Aborting ...

Aborting ...

I restored the stock kernel and tried again, same error.

Please see attached file and advise.
[Google Pixel 8 Pro] bsg411:
I just flashed the June OTA firmware update using the latest updated pixelflasher and it went thru fine. Only difference is this time I didnt patch the image with magisk.....kept it stock so I could use my RCS message again.

Maybe it was a bad download?? Did you try redownloading the file?
[Google Pixel 8 Pro] Galaxea:
I tried downloading again. Same issue...

I did patch with latest Magisk too.
[Google Pixel 8 Pro] badabing2003:
Try this

Device Menu | Cancel OTA Update

View attachment 6112488

Then try flashing OTA again.

This usually happens if there is an incomplete OTA, or if the partitions layout has changed.
[Google Pixel 8 Pro] roirraW "edor" ehT:
@badabing2003, I'm having an unrelated to PixelFlasher issue with the "Your device is corrupted", but I'm also having two other issues with PixelFlasher 6.9.6.0. Edit: This is on Windows 11 Pro 23H2 22631.3593.

The first is that I can't successfully create a support file. 🤪🤣

Multiple attemps:

Spoiler content hidden.

The support files end up only containing pf.dat and support.pf, which appear to be binary, or encrypted - not human-readable. I haven't tried quitting PixelFlasher yet and re-running, but I get the same issue creating a support file if I copy the .exe to a virtual PC running Windows 10 Pro 22H2 19045.4412, and run PF from there.

The second issue is that I get these errors when I have the Pixel 8 Pro in Fastboot (Bootloader) mode, and click on the Device Image arrow to be able to try to download:

Spoiler content hidden.

The Device Image arrow to download worked fine from the phone will up and running. Edit: Both before and after encountering this error when in Fastboot mode.

As I said, nothing relating to my corruption issue (I ended up using the May factory image for now, which worked fine - I might still be corrupt, but I can at least boot), but I just wanted to mention since it's a variable in the mix.

My post about my attempts so far to fix the corruption in my thread here, for reference. I do have more plans to attempt to fix - I probably just won't get around to them until 12+ hours from now, and I'm in no rush since the phone is working fine, relatively speaking, and I have my backup Pixel 7 Pro if necessary.
[Google Pixel 8 Pro] badabing2003:
Sorry to hear about your troubles. :(

This sounds like there is a process locking that file / folder, probably PF itself or some other process (perhaps Windows explorer or cmd shell in that path), Basically PF needs to clean before creating a new support file. Try this:

Close PF

Open ProcExplorer form sysinternals (by the way, excellent tools the sysinternals suite, I'm sure you know and use already)

Search (filter for) PixelFlasher.db

Kill or quit every process that has a hold of it,

Start PF, and it should work.

Actually this is the correct support.zip file contents with recent releases (few versions back)

Basically pf.dat is an symmetric key (asymetricly encrypted) which I can decrypt with the matching pair.

The support.pf is actually the encrypted (with the key from pf.dat) contents of support files that typically used to be created.

I did this because even though 99.99% of the time redaction worked very well, due to the nature of matching strings to redact, I noticed in few support files device IDs or usernames that didn't follow the normal patterns and were leaked, and I didn't want to risk user privacy being exposed, so I now I encrypt the support file.

In your case it probably contains everything except the db file, becuase that was locked.

This one is going to be tough one to crack.

Mainly because without being able to reproduce, and probably after you restart PF, you won't be able to repro either.

While experiencing the issue can you take screenshot when you are hovering over the item you want to download, or does it happen even without attempting to download?

When you hover over it, the status bar should display the checksum.

I'm curious to know if this is an image (icon) issue or downloaded file list issue.

Have you tried the Refresh images list option?

View attachment 6112519

By the way I tested this: I put my device in bootloader mode and downloaded husky June OTA image without problem

oh, the issue is with the popup next to Device Image rather than the menu item Google Images?

Usually corrupt issue is fixable with the attempts you made, ie either flashing OTA image or actually flashing old boot / init_boot and then flashing the new one (both slots).

I say usually because I experienced once a case where I couldn't fix no matter what I tried, so I let it be, ie lived with the corrupt image (harmelss, just a nuisance), and then next month flashing OTA fixed the issue.

This happened only once with my Cheetah, all other times I managed to fix it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you! At least I'm not worrying too much, or panicky, like I would've been a couple of years ago. :) I know that at worst, I still haven't lost anything, but I'll most likely be able to solve it either this month or next.

I'll try this tomorrow (time for bed for me), but this wouldn't explain me getting the same thing when trying a copy of the exe in a virtual PC:

I see! I wondered if something like that format change of the support file occurred. It's so hard to keep up with all the changes in all my favorite programs and apps, and I didn't remember that, but I might've just forgotten.

It would be interesting if users could see the unencrypted/99.99999% redacted copy of what's in the copies of the support files they generated.

Exactly - the issue is with just clicking on the arrow next to Device Image - no pop-up menu appears, and that error comes up, so no possibility to refresh images list in this case (without restarting PF, or exiting PF, manually deleting, and re-loading).

Thank you!

The very first time I experienced the corruption issue on the Pixel 6 Pro, it was fixed the next month when I flashed the factory image/flash-all.bat, since I wasn't experienced with or using the Full OTA Zip yet, and I don't think the news about temporarily downgrading had gotten around yet. It's good to hear that the OTA can fix it, too, in those cases.

Today, I definitely wasn't as complete in my attempts as I could've been since I was in a slight rush at the time. I'll make sure to downgrade both boot and init_boot to some older stock unpatched firmware next, attempt booting, and then re-upgrade them both (patched, in the case of init_boot). I had no problems fixing it on the various Pixels since that first time with the downgrade method.

I'll update you tomorrow.
[Google Pixel 8 Pro] Galaxea:
I can confirm that this worked. Many thanks!
[Google Pixel 8 Pro] badabing2003:
Oh shoot, I missed that,

Ok I have a theory, more on it below.

Yeah easy peasy, it was always there, but part of the optimization, PF is now deleting temporary files it creates.

If you go to help menu and select open configuration folder, it takes you where the support.zip gets prepared, in there a support directory is created and the redacted files are placed there before zipping / encrypting them.

At the end, PF deletes the support folder, I can add an option to keep that folder in case anyone wants to peruse what's in the support.zip

Back to the theory, I'll inspect the code later when I have some free time, perhaps it is a race condition where PF is trying to delete before the zipping / encrypting is completed,

So what do you visually get when you click on arrow?

Do you see the first level OTA and factory?

Do you see the second level latest files?

Do you get the error when you click on the file to download or does it happen when you actually click on the arrow to see the OTA / Factory / Files?

View attachment 6112717
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm trying to get around to do some more testing / solve my other issues. I'm finally caught up with both work, personal emails, et cetera. Well, off to my paying job for at least a little while again before I can fiddle with my phone and PF.

I get nothing visually in that particular circumstance. The error happens when I click on View attachment 6112718. OTA and Factory are never shown.

(reminder for anyone else: this was only while I was in FastBoot/Bootloader mode, along with the detail that I was also in a "Your device is corrupt" state unrelated to PixelFlasher, whether that detail is related or not.)
[Google Pixel 8 Pro] Morgrain:
Sometimes, Windows updates/Driver updates can mess up the Google/Android drivers (especially the fastboot drivers). Did you check that your machine has them correctly installed?

It's possible for the "base" drivers to still be installed, so PixelFlasher and the Explorer can recognize the phone, but once you go into fastboot, the correct drivers are missing and it won't work properly.

This can often happen if you are enrolled in the beta/insider builds, Microsoft messes a lot up in those builds.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Fastboot is working - I was able to use the factory image (without wiping) with no issue, but I just double-checked in Driver Manager. Good callout!

Device Manager says "SAMSUNG Android phone" as the category (just "Android Composite ADB Interface" for the actual device). I have a rooted Samsung tablet, but I've been finding that the tablet works and is able to be used with Odin just fine using Google's driver at least most of the time, so I don't think I manually installed Samsung's driver, and maybe Windows had loaded it for me. (Thanks, Microsoft 🤪 )

So I'll get rid of Samsung's driver and put Google's back. Depending on the results, I might reboot too, but I can't do so casually as I have a lot of virtual PCs and other things going on. I definitely had Google's driver installed when in FastBoot mode previously.

These days I don't even normally see FastBoot mode since I've been using the Full OTA Zip.

I'm not opted into the Insider builds for Microsoft Windows.

Thank you!
[Google Pixel 8 Pro] badabing2003:
Thanks,

That helped me find the issue.

bootloader mode + not seeing OTA / Factory.

When that button is clicked, the current device model and currently installed firmware date is passed to the function that shows the downloads available for the device.

In bootloader mode, the date is not available hence the error because I wasn't expecting that and hadn'e code for such exception.

Simple fix, it should be in the next versionb.

Thanks for the feedback.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Awesome! Thank you, and you're welcome.

So the difference between your test:

and mine is, in fact, my corrupt state, or something else?
[Google Pixel 8 Pro] badabing2003:
I have a similar setup, my phone is Pixel but my tablet is Samsung, and I only have the Google's drivers installed, and haven't had any issues.

FYI in case you didn't know, I do the update processing of the Samsung tablet in PF (you can load the image and process, patch the boot, and it should create a patched boot.tar), the only part that PF can't do is the flashing with odin, as I have not found APIs or CLI of odin (that I can define what files to flash) to automate that part.
[Google Pixel 8 Pro] badabing2003:
I don't think the corrupt part had any role.

The fact that the device was initially in adb mode and I rebooted to bootloader mode in PF, PF still had info cached about the device, either than or I tested from Google Images menu (I don't remember)
[Google Pixel 8 Pro] Lughnasadh:
Correct me if I'm wrong, but I was under the impression that you had to use the boot.img, not the init_boot.img for this trick, even with devices that have the init_boot.img. I remember when the Pixel 7 Pro came out that people tried with the init_boot.img but it didn't work, but using the boot.img did. At least that's my recollection, but I'm old, so there's that🙃 ....I think people thought that they had to use the init_boot.img because that's what we patch to root, but I believe that's unrelated to the red eio corrupt message. I also "remember" people reporting the same behavior with the Pixel 8 Pro.

From how I understand it, when encountering the red eio corrupt message the bootloader looks for a new OS so that it can switch to restart mode rather than eio mode, thus making that corrupt message disappear. When you downgrade the boot.img, then upgrade the boot.img the bootloader thinks it's a new OS and thus reverts to restart mode, hence the "trick". However, my understanding is that if you downgrade the init_boot.img, then upgrade it, the bootloader doesn't think a new OS was installed.

It's quite possible that I missed any reports where this worked with the init_boot.img. Have you ever gotten this trick to work with the init_boot.img rather than the boot.img on your Pixel 7 Pro?

For what it's worth, here's a success story from a Pixel 8 Pro user using the boot.img rather than the init_boot.img.
[Google Pixel 8 Pro] badabing2003:
Yep,

Your memory is better than mine :)

Boot Flow | Android Open Source Project

source.android.com

It makes sense, Magisk patches the Ramdisk

Devices that have init_boot, the Ramdisk is in init_boot, but the kernel is still in boot.

Only devices that don't have init_boot, both are in the boot, so it makes sense that if eio is looking for the OS change, then we would need to flash boot, not init_boot.
[Google Pixel 8 Pro] HipKat:
Are you using PF to D/L the update and that's where it's giving you your first issues?

Why not d/l it manually and then browse to it after scanning for your device?

Or am I misunderstanding?

EDIT!

And then I read @Lughnasadh's post!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you, I didn't know. I'll try to remember to take a closer look at that the next time the tablet gets an update.

I was in a particular circumstance where I was in Fastboot and PixelFlasher wasn't bringing up the menu to download OTA or factory image. I did end up manually downloading what I needed at the time, but I still thought badabing2003 would be curious about it. It should be fixed in the next version:
[Google Pixel 8 Pro] kingpeppermint:
Unrelated question to above and i hope i'm not asking the same question that has been asked many times but anyway, i have roughly about 50gb in pixelflasher folders, mainly old version that i don't use anymore, can i just delete the folders or do i need to do it within the menu somewhere?(menu of pixelflasher opposed to explorer/windirstat)
[Google Pixel 8 Pro] badabing2003:
The bulk of the space is the images unpacked if you're flashing factory,

The extracted files like boot.img or init_boot.img / vbmeta ... are small files.

If you're flashing full OTA, the image file is where you load it from.

In any case, you can delete the folder, but you will lose your settings, which is not a big deal.

You can also use the delete button in PF, if you delete the extracted patched boot / init_boot and there is no more of them in the boot list, the associated extracted image file are also deleted.

Show all boot files, and delete every one listed,

You can also set the PF working directory (in settings) to be to an alternate drive where you have space.
[Google Pixel 8 Pro] ko3st:
After pixelflasher flased the newest Husky firmware all looked good, However I might experience a problem...

Please see the support file.

What is the best way to resolve this without loosing my data? (I do have backups of the other day).Please see the picture in which you can see I am stuck at "Try Again".

Thanks for any help in advance.
[Google Pixel 8 Pro] ko3st:
I am now in Fastboot Mode and I do not know how to proceed...
[Google Pixel 8 Pro] ko3st:
- Currently I am stuck in a boot loop.

- Using PF, I am also able to access FastboodD

- I still have no clue what I could ty next.

I am almost ready to wipe my P8P, but I have still some hope, that someone can help me through this mess I got myself into...
[Google Pixel 8 Pro] HipKat:
Reflash the May Update, then look up at the issues that @roirraW "edor" ehT had, which seems familiar
[Google Pixel 8 Pro] ko3st:
@HipKat
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes, most likely you were on the .005 firmware, but ultimately, that part doesn't matter for trying to fix your bootloop, although optimally, yes, you should reflash the exact same firmware to fix it.

I can't advise you specifically about what you indicated is in the other screenshot.
[Google Pixel 8 Pro] ko3st:
I guess my problem started when I downloaded the Full June firmware instead of the Full OTA update. After that ended up in Try Again (see my previous picture)

- From FastboodD, I can get a correct reply after running the command adb devices

- From FastboodD, I can invoke a reboot command running the command adb reboot

But then the bootloop starts again.

Now my main concern is to NOT brick my new P8P, because I have bricked my old P8P one time earlier...
[Google Pixel 8 Pro] ko3st:
From Fastboot mode I can run all fastboot commands like

fastboot flash init_boot init_boot.img --slot all
[Google Pixel 8 Pro] roirraW "edor" ehT:
I completely understand about not bricking (even temporarily) your Pixel 8 Pro. I had to factory reset both my phone and watch for the first time since I got them, in the last few days.

I would go so far as suggesting you use:

Android Flash Tool

flash.android.com

Edit: If it lets you choose the May firmware, if not, then stick with the factory image. Not that for normal updates, I use the Full OTA Zip rather than the factory image for more than a year now, as it's a safer alternative.

Just make sure and have

UN

checked:

Wipe/factory reset

Lock bootloader

Force flash all partitions (this includes storage/user data, so effectively wipes everything, too)

and if you're not using a custom kernel, don't have the Verity/Verification checkbox(es) checked, either. Of course, at least some custom kernels don't require that any more (again), so choose wisely.
[Google Pixel 8 Pro] badabing2003:
Here's you're problem.

You selected to disable verity / verification

Flash Mode: keepData

Custom Flash Options: True
Disable Verity: True
Disable Verification: True
Flash Both Slots: False
Force: False
Verbose Fastboot: True
Temporary Root: False
No Reboot: False
Wipe: False
Flash To Inactive Slot: True

And PF warned you about it.

Slot A Verity: Enabled
Slot A Verification: Enabled
Slot B Verity: Enabled
Slot B Verification: Enabled
⚠️ WARNING! WARNING! WARNING! There is a mismatch of currently selected vbmeta verity state and device's verity state
⚠️ WARNING! WARNING! WARNING! There is a mismatch of currently selected vbmeta verification state and device's verification state
This has a device wipe implications, please double check.

You ignored it, which means unless you wipe or re-enable verity/verifaction you will have that issue.

If you really want to disable (for whatever reasons) then you need to wipe.

If that was done unintentionally or without understanding the consequences, all you have to do is flash vbmeta.img with the options not disabled.

Do the following

While your device is connected and detect by PF, and you have selected the same image that you last flashed in PF.

Select Custom Flash option (if it is not enabled, you can enable it in the settings)

From the drop down select vbmeta

And hit the paste button,

if you did it right, then PF will select the vbmeta it had extracted and you would see it pasted.

Flash Pixel Phone.

View attachment 6113741
[Google Pixel 8 Pro] ko3st:
Thank you @badabing2003 , @HipKat and @roirraW "edor" ehT

I 'd better not ignore the warnings anymore :).

Thanks for your help guys, much appreciated!
[Google Pixel 8 Pro] sic0048:
EDIT - I missed the last couple of posts before I replied. I see now that this is already a moot point.....

Installing OTA will not cause you to loose your data, nor will installing root.

The only things that force a wipe are: unlocking your bootloader. disabling Verity, or flashing a full factory image without removing the "wipe all" command/flag.
[Google Pixel 8 Pro] bsg411:
I tried to remove root so I could get my RCS working again so I reflashed the latest OTA and opted not to patch before flashing. Afterwards, the magisk app was still in my app list so I uninstalled without unhiding first by uninstalling the renamed Magisk app. RCS is working and banking apps too but not Google Wallet. However I heard the google wallet and RCS is working while using Apatch. But when I use Apatch to patch and then flash the latest OTA is flashes but does not root the files once completed. Is there anything special I need to do to get this to root using Apatch?

Any help would be appreciated.
[Google Pixel 8 Pro] badabing2003:
After doing all that, did you launch Apatch app and type the same key and followed the steps?
[Google Pixel 8 Pro] bsg411:
Yes after doing all that I typed in my key and then hit install highlighted in blue for the kernel. Then i went to rootchecker and it says "root access not properly installed on this device"
[Google Pixel 8 Pro] badabing2003:
You can post a support.zip generated from PF and I'll check to see if anything didn't go right, otherwise it would be something to bring up in APatch threads / Github.