yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] badabing2003:
Thanks to @Lughnasadh for finding the correct post you should have your answers.

As for what to do, I prefer your second method over first, less risks.

I'm fact if you have fully functional one slot now at the firmware level that you want, all you have to do is flash ota once and you're done
[Google Pixel 8] cswithxda:
Moment of enlightenment!! Thank you so much. I tried many keywords to search for with little gain, but this single link leads me to so many pieces of knowledge I have been missing for the past couple of years.

To be honest I was getting tired of unlocked BL and root, until I discovered PF.

I have learned to leave most of the root-required modules or apps. For me, there's only two modules I have to have root to use: one for an NFC simulator and another to enable VoLTE since I live in an unsupported country for 80% of my time. I don't even know why I'm still sticking with Pixels, may be the power of habit.

But I'm currently in the states and am discovering just how great to use this phone can be, sans the part of broken Safetynet/Google Pay I'd never bothered to solve previously.

Thank you badabing2003. On my way to downloading OTA XD
[Google Pixel 8] cswithxda:
Just a quick thought while doing the preparation. Since OTA can't be flashed to both slots at once, and flashing factory image to both slots corrupt one of them, does that mean the option of flashing to both slots is pretty limited in its use. I suppose for now the option is only useful when doing flash boot?
[Google Pixel 8] badabing2003:
It is still useful for people who prefer flashing factory instead of OTA (mostly due to habit), it would flash the bootloader on both slots (asking with radio and other partitions) but the bootloader is of importance, specially for brand new devices, or a bootloader is updated with anti rollback protection and is crucial that both slots get updated to avoid potential hard brick.
[Google Pixel 8] cswithxda:
I see, thanks.

I forgot to ask about this in my procedures:

Do I set up the system first with the working slot, and then flash OTA (to the other slot)? I've never flashed an OTA at all, so I'm not sure if it must be initiated from ADB commands or it can be done in fastboot. If former, I'm going to set everything up and then flash OTA. If the latter, I won't go through setting up the device, but rather just finish flashing both slots and then pick the one with root to start setting up.
[Google Pixel 8] badabing2003:
You can do either way,

It gets flashed in sideload mode.

PF takes care of all that.
[Google Pixel 8] cswithxda:
Reporting back. Finally flashed OTA to slot b, after setting up in slot a. Now slot b with no root is booting up fine, so I switched back to slot a. It caught me off the guard to see "your device is corrupt" message.

I remember reading somewhere that it is harmless, so I hit the power button to proceed. But it's stuck at the Google logo, won't even bootloop. Should I switch back to slot b and flash a patched OTA to slot a?

Nope, looks like booting from slot a shows corrupt as well. My first instinct is to try dirty flash factory image to slot a and start all over again, but in PF the flash mode is limited to Full OTA and Custom Flash. I'm baffled :cry:
[Google Pixel 8] badabing2003:
Ignore the corrupt message, it is harmless, other than you having to press the power button when you see it.

Flash OTA again.

The PF flashing options are limited to the type of image you select, but I wouldn't flash factory, unless nothing else works.

If you want me to provide pertinent feedback, your have to generate support file and provide that.
[Google Pixel 8] cswithxda:
Both slots were unbootable. After pressing the power button, using either slot would get stuck at Google logo and never booted successfully. I had to wipe flash both slots to get one slot to boot successfully. Now I'm in the process of setting up the phone, get into the system to enable ADB, and flash OTA.

Could you please advice me on what to do next? It'd be devastating to start all over if this time it fails again.

The phone's current state is: slot a flashed with non-patched factory image, so slot b is likely unbootable at the moment.

My goal is to root in slot a and keep b non-root.

I plan to:

Under the current slot a environment, install Magisk app first, patch the latest OTA. Then, flash original OTA to slot b, and boot under slot b. Finally, flash patched OTA to slot a.

Would this be correct?

Thank you Badabing
[Google Pixel 8] badabing2003:
Please create a support file and provide that.

I don't want to speculate without fully understanding what went wrong in the first place.

That's the only way to avoid further problems.
[Google Pixel 8] cswithxda:
Thanks, I was too eager and went ahead last night to flash OTA to both slots consecutively and all is good now =D

I also removed everything in the PF working folder (under roaming), with intention of a fresh start, since there had been this INFO I wasn't sure about: multiple package_boot records found for *SHA1 of the init_boot".
[Google Pixel 8] dmitriibugayov:
Hello, please help me, I'm a newbie. Here is a brief description of the problem:

After updating to beta version, phone gets stuck at Google logo. fastboot mode and recovery mode work. I tried updating the firmware via adb sideload. The update reaches 100% but the firmware is not installed. Bootloader locked.
[Google Pixel 8] badabing2003:
With bootloader locked, the only option you have is sideloading the OTA.

Try sideloading the OTA you had before flashing beta.
[Google Pixel 8] AggresiveSoldier:
I probably did something wrong again.

Tried to flash JUNE OTA build with KSU and my system got corrupted again.

I really dont understand why i get this so often, i disabled the 3 modules i have.

Shell has SU permission and it showed Checkmark in PF.

Fresh installed system(windows side), fresh ADB download and all.

Edit: flashed the full factory image with "keep data", that booted the system, then tried the patched OTA image again and now it booted without a problem and KSU is active
[Google Pixel 8] badabing2003:
Corrupt message is harmless, the only drawback is that upon reboot it waits for you to press start, and PF times out if you don't press in time.

Aside from that it has zero impact on functionality, and it gets cleared out if you flash OTA again or flash old boot / init_boot and reflash the current one.

It also gets cleared out with the next month's update.
[Google Pixel 8] AggresiveSoldier:
Well in my case it is harmless as my device wont boot when i press start.

This behavior has happened multiple times for me and always leads to non-booting device.

It just stays on the Google image for like 30 seconds and then reboots itself again, after 2 or 3 attempts its full corrupt and can only boot into Fastboot mode.
[Google Pixel 8] badabing2003:
I think the two are unrelated, you probably are having bad boot / init_boot or misbehaving modules.

The fact that when you flash stock boot, it works suggests that.
[Google Pixel 8] dmitriibugayov:
Does not work. I tried to install OTA, but the installation always reaches 100%, but nothing changes. Then I noticed. When I do wipe:

"

Wiping data

error: logwrapper: Cannot log to file /dev/fscklogs/log

error: recovery: open failed: /metadata/ota: No such file or directory"

These errors always pop up at the beginning.

I wanted to use pixelrepair.withgoogle.com but there is no pixel 8
[Google Pixel 8] badabing2003:
Update Release:

June 24, 2024 v6.9.8.0 change log:

Improve Check keybox.xml to report if the certificate is software signed, also report about all included certificates.

Added settings option Keep temporary support files in case one needs to inspect the support files.

Add Github action to build on MacOS 12, MacOS 11 runner has been deprecated.

Update Pixel beta links from A14 to A15.

Minor bug fixes and improvements.
[Google Pixel 8] aap7:
Hi.

I'm confused with compilation numbers.

I rooted my device using a guide from XDA Pixel 8 Pro forum and I'm planning to update my phone without loosing root using PixelFlasher.

My current Pixel 8 compilation number is AP1A.240305.019.A1.

However, when looking for the latest OTA version I see many files:

14.0.0 (AP1A.240505.004, mayo de 2024)

14.0.0 (AP1A.240505.005, mayo de 2024)

14.0.0 (AP1A.240505.005.A1, mayo de 2024, Verizon y MVNO de Verizon)

14.0.0 (AP1A.240505.005.B1, mayo de 2024, MVNO de KDDI y KDDI)

14.0.0 (AP2A.240605.024, junio de 2024)

14.0.0 (AP2A.240605.024.A1, junio de 2024, Telus)

I think options 3, 4 and 6 might relate to other carriers.

I don't know if option 5 (starting with AP2A) is compatible with my current build (starting with AP1A).

Should I use option 2 (AP1A.240505.005), which starts with AP1A and does not mention other carriers or strange acronyms after the version number?

Thank you very much!
[Google Pixel 8] badabing2003:
Based on what you have, you should go with option 5

14.0.0 (AP2A.240605.024, junio de 2024)

That's the June (latest) release of what you have.
[Google Pixel 8] aap7:
Thanks.

Out of curiosity, should I always ignore de first code (e.g.: AP1A, AP2A)? Or are some of these codes related to non-compatible versions?
[Google Pixel 8] badabing2003:
See this.

Codenames, tags, and build numbers | Android Open Source Project

source.android.com
[Google Pixel 8] aap7:
Thanks for sharing this.

Based on this page, AP1A and AP2A are based on different branches. I don't see any explanation that confirms that we can update a phone from version AP1A to AP2A (but likewise, there is nothing that indicates the opposite!).

I asked ChatGPT about this and it replied that I should not update from AP1A to AP2A but I know that AIs make up many responses :)
[Google Pixel 8] badabing2003:
Take a look at other devices (even yours)

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

They change letters and numbers.

I have cheetah and i flashed the latest without concern even though it changed numbers.

Do what makes you feel safe.
[Google Pixel 8] aap7:
Hi @badabing2003

Thanks for your help so far.

I followed the steps in your guide and attempted updating from AP1A.240305.019.A1 to AP2A.240605.024 using PixelFlasher 6.9.8.0.

I patched init_boot with Magisk (my phone is already rooted and I want to keep root after updating) and clicked on Flash (using Full OTA flash mode). I also deactivated my magisk modules (LSPosed, Youtube Vanced and Zygisk detach).

When the process finished, I went to Settings to check the phone version and found that my phone was still on the old version (AP1A.240305.019.A1). I can see these messages in the log:

Do you have any idea about what might have caused this? Should I try again or flash a different version?
[Google Pixel 8] badabing2003:
I need to see a support.zip file generated by PF to troubleshoot.
[Google Pixel 8] aap7:
Thanks, I've attached the support zip file.
[Google Pixel 8] badabing2003:
The issue is because the flashing of OTA did not go 100% (actually 94% reported by sideload tool) instead it went 50% (reported 47% by sideload, blame Google for the wrong progress)

In any case try the following.

Device Menu | Cancel OTA update

View attachment 6117916

Then repeat the flashing.
[Google Pixel 8] aap7:
Thanks, doing this again worked!

I had a small issue.

After the first boot Magisk said that my device was no longer rooted, although PixelFlasher still displayed the tick icon next to the version number. After rebooting 1 time, Magisk started working and I was able to re-enable Magisk modules to get everything working again.

I only have one doubt, do you recommend flashing both partitions? Should I run it again after successfully flashing one time?

(When I rooted my phone for the first time I followed a guide in this forum that recommended flashing both partitions)
[Google Pixel 8] badabing2003:
Considering that you are doing OTA flashing, which is the safer and recommended flashing over factory image flashing, you just flash one more time, and you end up with both slots identical and bootable.

That's because each time you flash OTA, it automatically switches slot, so doing it twice covers both slots.

I recommend it.
[Google Pixel 8] wetwilly5519:
Hello Friends,

My OTA flash of magisk patched image is aborting at 47%. I've tried with the image downloaded from the Google Dev site as well as through the PixelFlasher app. I've attached my support file. What's going on here?
[Google Pixel 8] badabing2003:
Read 3 posts back
[Google Pixel 8] wetwilly5519:
Thank you!
[Google Pixel 8] pixel8kid:
I am having the same problem of the june update failing at 47%. I have tried flashing twice now and the pixel is not bootable. However I do not have a cancel OTA update option in the device menu. I have attached a support.zip.

Edit: actually the pixel is bootable but still on the april update.
[Google Pixel 8] badabing2003:
Dude, pay attention to the console messages.

PixelFlasher 6.4.1.0 started on :2024-06-29 11:48:45
...
A newer PixelFlasher v6.9.8.0 can be downloaded from:
https://github.com/badabing2005/PixelFlasher/releases/latest
[Google Pixel 8] pixel8kid:
Ah I see, thank you sir. I really appreciate your help with the dumb question.
[Google Pixel 8] eric_4321:
I failed to update from ap1a.240505.005 to ap2a.240605, 47% too! I have to manually reboot, the system is still May 2024. But I can't Cancle OTA update. I tried version 6.9.8.0 and 6.9.4.0 and got the same. Previous monthly updates have been successful. Attached my support file, waiting for your help.

View attachment 6118679
[Google Pixel 8] badabing2003:
That option is only available if:

- The device is in adb mode

- The device is rooted and you have granted shell process su permissions.

- And obviously the device is connected and PF is reported ADB mode + rooted.

Please make sure of that and it should be enabled.
[Google Pixel 8] guniens:
Hi @badabing2003

I'm still on May 2024, tried updating to June 2024 but got flash aborted as many others.

Can I jump straight to July 2024 from May 2024?

Thanks!
[Google Pixel 8] badabing2003:
Yes, just make sure you do Cancel OTA update from device menu in PF first.
[Google Pixel 8] McFlypants:
OTA Update rooted with Kitsune from june to july worked fine! (y)(y)
[Google Pixel 8] guniens:
Yeah, actually it happened a couple of days ago, I hadn't read yet here so I just started my P8 from booloader menu.

Thanks again!
[Google Pixel 8] Snow_ball:
OTA update rooted with Magisk from June to July worked as expected - @badabing2003 thank you for all the work you put into this tool.
[Google Pixel 8] johnsmallberries:
April update rooted with Pixelflasher and Magisk.... Normally when new updates come along I get a message saying "couldn't apply update" or something like that, whenever a new OTA comes out.

For the July update I didn't get a failed to apply message. Instead it says "Your Pixel is getting even better..." and prompts to restart now. Is this new behavior? I thought if the pixel was rooted that the udpates just fail to apply?

Should I reboot (and maybe it will fail or lose root) or go into pixelflasher and cancel the OTA and manually patch and flash the OTA?
[Google Pixel 8] badabing2003:
Google can force update at will, and usually do with quarterly updates or important updates

You should have lost root
[Google Pixel 8] johnsmallberries:
I appear to still have root. Previously it would just reject updates if the device was rooted. This is the first update (that I've noticed) that went through while rooted.

shiba:/data/misc/update_engine/prefs # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:magisk:s0
shiba:/data/misc/update_engine/prefs # ls -lgt |head -3
total 248
-rw------- 1 root 10 2024-06-27 20:16 total-bytes-downloaded
-rw------- 1 root 4 2024-06-27 20:16 post-install-succeeded
shiba:/data/misc/update_engine/prefs # cat total-bytes-downloaded
2710660152shiba:/data/misc/update_engine/prefs #
shiba:/data/misc/update_engine/prefs # uptime
15:56:33 up 52 days, 17:38, 0 users, load average: 0.54, 0.69, 0.90
shiba:/data/misc/update_engine/prefs # getprop ro.boot.slot_suffix
_b

I haven't rebooted yet, but assuming I do I think I'll lose root, so was just wondering what the proper way to cancel the update was. I guess after this I'll try to disable factoryota app and stop it from checking automatically.
[Google Pixel 8] badabing2003:
Do the Canceling of OTA mentioned here

You can't disable factory OTA updates, Google can still push at will
[Google Pixel 8] johnsmallberries:
Thanks I may cancel it but as you say it may come back anyway. The question is what is the procedure if it already downloaded the update and is ready to boot into it, without losing root.

Can I just download the OTA myself now, patch it, and flash it to the slot while the google updated OTA is pending? ro.boot.slot_suffix showing 'b', I guess I would try to apply it to 'a'.
[Google Pixel 8] badabing2003:
That potentially would work assuming that the update was successful, but I'd do it differently.

I'd Cancel OTA Update in PixelFlasher's Device menu, and then sideload the OTA with the patched boot selected.

Longer, but safer.
[Google Pixel 8] badabing2003:
New Release:

July 4, 2024 v7.0.0.0 change log:

When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).

Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).

Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).

When reading device details, report the sys.oem_unlock_supported prop value.

Miscellaneous minor improvements.
[Google Pixel 8] badabing2003:
Latest Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.
[Google Pixel 8] badabing2003:
Update Release:

July 14, 2024 v7.1.1.1 change log:

Bugfix: #222 Customize My Tools menu is duplicatede when no tools are added.

July 14, 2024 v7.1.1.0 change log:

Windows versions of PixelFlasher are now signed (self-signed).

Hopefully this would cut down on false positive virus / trojan alerts, but it should also get rid of Unrecognized app warnings.

PixelFlasher.crt is the certificate, and ca_badabing2005.crt is the root CA.

Bugfix: #221 handle a corner case exception.
[Google Pixel 8] Clems92:
hi here !

first of all thanks a lot for the job done!

I get stuck on the "now send the package you want to apply ...." on the device when I try to flash wiht OTA patched.

Here is the support log.

thanks !
[Google Pixel 8] badabing2003:
I see multitude of issues, but let's focus on the main one.

adb: failed to stat file C:\Users\REDACTED\Downloads\shiba-ota-ap2a.240705.005-3376b945.zip: No such file or directory
Error: The sideload command encountered an error, aborting ...

The sideload operation is not able to find / read this file

C:\Users\REDACTED\Downloads\shiba-ota-ap2a.240705.005-3376b945.zip

(replace REDACTED with your username)

Make sure you don't download or run PF as administrator

Start PF

Use this button to download OTA image for your device

View attachment 6125282

Save it somewhere simple: (example: c:\Android\...)

Process it.

If patched init_boot automatically shows up, select it, otherwise select the stock one and create a patch.

Flash Device

If you get errors, provide a new support file.
[Google Pixel 8] Clems92:
Thanks! Probably because I have "é" in my user name, so I moved all to C:\platform-tools

I think it ok now, I have Magisk 27.0 installed :)
[Google Pixel 8] Clems92:
Thanks for this reading! Very interesting.

Do you wan me to share other ogs with you ?

Do you think I should restart the process ?
[Google Pixel 8] badabing2003:
I suggest you should do one more Full OTA to make sure the other slot is good too.

What I'm suspect (though cannot be sure) you had received OTA from Google, and because you weren't rooted, it installed properly and was just waiting for the reboot, and when you did the sideload, even though that part stopped half way, it checked the other slot and determined that it was applied properly so switched to it.

PF detected the switch and applied the path. (just a guess).

Flash full OTA to make sure you're good on both slots, and the give me one last support file.

Thanks
[Google Pixel 8] Clems92:
Hi ! Hi think you got it, this true that the phone did just run an OTA before, and probably it was waiting to reboot!

Hi flashed again, here is the log.

thanks for your support!
[Google Pixel 8] badabing2003:
The flashing worked well.

You ahven't granted su permissions to shell process, hence PF does not detect that you're rooted,

You should do that before next month's update, otherwise PF will not try to cancel a partial OTA before sideloading, which might cause sideload to fail if there is partial OTA.

Furthermore, you get other benefits like not having to unhide Magisk and use root to create a patch.
[Google Pixel 8] Clems92:
Well received, thanks.

But I struggle to understand how can I do this ?

At this point I'm still not sure I'll stay rooted, as my UBS Bank app is detecting the root, anyhow :(

thanks for your support!
[Google Pixel 8] badabing2003:
It's in the guide in the OP.

View attachment 6126125
[Google Pixel 8] Clems92:
Thanks a lot!

I think this time is all fine :)
[Google Pixel 8] badabing2003:
Latest Release:

July 27, 2024 v7.2.0.0 change log:

In Magisk Manager, added the option to install Tricky Store module. (You now have 3 PIF related modules to choose from, Playintegrity Fix, Playintegrity fork, Tricky Store).

Updates to PIF Manager:

Option to convert from Json to prop (Env) format and vice versa (Tricky Store uses prop format) .

Compatible with Tricky Store (latest CI), you can now edit / update / test using Trick Store module.

Note: Tricky Store module does not yet support automatic updates, hence PixelFlasher is currently setup to point to the latest release in Github, this still uses Json file to spoof prints, use the latest CI.

If you have multiple PIF modules, for example if you use Trick Store and PiFork together, you can select which module's print you want to edit / update by selecting from the combo box. (Only enabled PIF modules are listed).

When loading prints from favorites, or console output, or using Smart Paste, PixelFlasher automatically converts the print to the format (json / prop) that the module requires.

Added option to push keybox.xml file to Tricky Store's predefine path.

Added a button to generate FrameworkPatcher compatible code for use in Android.java, just select the print, generate code and paste it in the proper section of Android.java to use your custom print with FrameworkPatcher.

Note: the generated code by default is commented out, as you can select multiple prints, just uncomment the ones you want to apply.

Added option to backup / restore /data/adb directory, please be aware that this only backs up / restores /data/adb/*, any modules that installs files outside this path will not be backed up, as it's impossible to know what all modules do.

New features in My Tools Manger:

Different methods to launch application.

Option to enable / disable launching detached process.

Option to insert separator.

Note: Start with the defaults and experiment if default behavior is unacceptable.

Miscellaneous fixes and improvements.
[Google Pixel 8] badabing2003:
Update Release:

July 28, 2024 v7.2.0.1 change log:

Set a default PIF format to json to allow displaying the print when Processing Image in PIF Manager.

When PIF Manager is used with an unrooted device or one without granting su permissions to shell, display a message to inform the user about the reduced PIF Manager functionality.