yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] AggresiveSoldier:
Thx for the reply, its appriciated, been a long long time i been doing this rooting and such.

Currently my device is back to where it was this morning after a lot of trial and error.

Both slots wouldnt boot, tried to switch slots from fastbootmode.

After that i tried to flash stock factory image from April version, this resulted in the same corrupted message and not booting device.

I ended up trying a couple of version of PF and couldnt get it to work so i ended up reflashing March factory image with whipe of device.

This got my device booting again but just on 1 slot, i then proceeded to flash the same March factory image to the other slot with full whipe, this resulted in both slots booting again for me with the factory image.

After this i used March OTA file with KSU again and have that flashed, so basicly im back at the point before i started this morning (besides all app logged in).

Had to do this as my work SIM i in this device too as E-SIM and need to be reachable for work during office hours.

From what you state i need to grant ROOT access to PF, this might actually be the problem then.

KSU works the other way arround compared to Magisk, instead of everything having root with Magisk, nothing has root with KSU unless i tell in KSU manager something can have/use root priveledges.

Im quite sure i havent granted root to anything as i wouldnt even know what i would need to allow root for PF to have root access.

KSU manager just shows apps installed on the device, PF isnt a app on the device so thats a big questionmark for me personally.

You mention shell, would i need to give root to com.android.shell before trying to install the update?

Modules i have installed within KSU are only 3 modules.

1. Playintegrityfix from Chiteroman

2. ZygiskNext from Dr-TSNG

3. Pixelify submodule for unlimited Gphoto storage V2
[Google Pixel 8] badabing2003:
Hmm,

You can't get both slots bootable by flashing factory alone, if you search the thread you'd understand exactly why that happens.

Perhaps after flashing OTA , which would be right.

See basic usage step 3 part 1

There's even a screen of the option (though that is for Magisk) indeed it its com.android.shell

It's always a good idea to disable modules first, update and when it reboots to system you know that it's functional, and then enable modules, this way after enabling modules it does not boot, you know it is one of the modules and you can use the elimination process to narrow it down.
[Google Pixel 8] AggresiveSoldier:
Ok trying again now.

On phone i granted root to the shell proccess and disabled the 3 modules.

Deleted the entire APPDATA folder for PF on my laptop.

Downloaded the latest version of PF.

Selected my ADB path, then searched for devices, i see my device and it has the green checkmark for the device.

Selected the April OTA file, enabled debug in PF, then pressed process, patched the April OTA file with GKI and started the flash.

Now its back in rebooting again, did this multiple times and is now presenting me again with the "your device is corrupt" message.

Cant get into safemode trying the methods stated here: https://support.google.com/pixelphone/answer/2852139?hl=en#zippy=

Forced device to Fastboot mode and tried to flash the stock OTA image that isnt patched from within PF.

The device reboots and gets the "your device is corrupted" message screen right away so that wont work either.

EG im back to where i was this morning.

Then forced back to bootloader again and tried the "flash boot" button, this also reboots the device into the "your device is corrupted" message.

Booted to rescue mode, cant flash boot with that.

Went back to fastboot and choose to flash boot with the "no reboot" option enabled.

system is now rebooting straight to fastbootmode and not even showing Google splash anymore.

Im not sure what to do now.

Only way i know to get it back working now is using the Factory image instead of OTA file and flash that to both slots with a full whipe
[Google Pixel 8] badabing2003:
I want to be clear about the corrupt message.

It is harmless, but it requires a user interaction, when you see that message you have to press the power button for it to continue, it won't continue by itself.

So your tests can only be relevant if you click on it as soon as you see it to avoid any timeouts in PF.

On the other hand, looking at the detailed logs (thanks)

I see that PF has downloaded this file instead of this.

I'm investigating to determine why.
[Google Pixel 8] AggresiveSoldier:
Yes, i have to manually press to start when i see that message.

I dont see that message though before startting this upgrade proccess.

Also my phone is now in a state it wont even show that anymore.

Its now just booting straight too Fastboot mode, enter reason: boot failure.

As for the corruption message, i have tried to toggle that so it continues to boot, its waiting for ADB as you can see in the logs but it nevers comes to a state where ADB actually responds as it reboots before that to eventually end up in fastboot mode again.
[Google Pixel 8] badabing2003:
Ok found the issue with using the old Kernel.

It was good in v6.8.4.0 and v6.9.0.0 introduced a regression when I refactored code.

I'll have a proper fix released sometime today.

In the meantime, if you want you can flash stock factory,

then create a patch with 6.8.4.0

and flash the patch

When your device only gets to bootloader mode, you'd have to use factory image to fix it.

You don't have to wipe.
[Google Pixel 8] AggresiveSoldier:
I already wiped again using the March image.

System is booting again and going to set it up now with rooted March how i know to do it.

When the new version is released i will try to do the update to April rooted with the new released version.

To be clear, no rush, if you dont manage today thats fine for me.

Really appriciate you taking the time to assist and look whats going wrong
[Google Pixel 8] badabing2003:
Update Release:

Apr 09, 2024 v6.9.1.3 change log:

Fix regression introduced when refactoring code in KernelSU Patching.

#187 On MacOS, move the exit menu into PixelFlasher's file menu from the OS's native Exit menu.
[Google Pixel 8] AggresiveSoldier:
Thank you verry much, with this version i could update to April version and use KSU GKI mode.

Steps i done.

1. Granted Root to shell.

2. Disabled the active modules on my phone.

3. Patched the April OTA in PF.

4. Installed April patched OTA.

5. Success
[Google Pixel 8] badabing2003:
Thanks for your confirmation.
[Google Pixel 8] badabing2003:
New Release:

Apr 14, 2024 v6.9.2.0 change log:

Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).

Credit to @tbalden for the discovery and @capntrips for the details of the process.

Select any img file and get additional image info.

#190 fix, scrcpy launch improvement.

Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).

If KernelSU or APatch is installed, report their version as part of device details.

Improved logging.

Improved santization.

Other minor improvements and added stability.
[Google Pixel 8] badabing2003:
Update Release:

Apr 16, 2024 v6.9.2.5 change log:

Roll up MacOS related changes. #187 and #190

Logging improvements

When Magisk delta is installed, automatically set the package to: io.github.huskydg.magisk
[Google Pixel 8] AggresiveSoldier:
Used the 6.9.2.6 version to update to the B April release version with KSU in GKI mode.

Worked like a champ, thx for the tool Badabing.

Your continues effort to improve the tool and support to the members who need support is appriciated(y)
[Google Pixel 8] fluid46:
Posted a query about this software here:

https://xdaforums.com/t/flashing-kernel.4669408/#post-89482181
[Google Pixel 8] badabing2003:
That's for ROMs, not kernels, and it doesn't apply to all ROMs. In either case, you'd have to follow the ROM / Kernel guides from their authors as each is different.
[Google Pixel 8] 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] m4j0r4:
I keep getting this message in pixelflasher:

WARNING! WARNING! WARNING! Slot a verity / verification does not match slot b verity / verification 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.

I don't know for sure if this might have something to do with my Pixel 8 being stolen a month ago, but the keen thief tried to pawn it to a mobile shop, where they checked the IMEI number. This resulted in the thief being swiftly taken into custody and me getting my Pixel back :D ( hooray for petty thief) the person had done a factory reset, thus attempting to erase all data. Is pixelflasher informing me about this? Cause when I got it back I did flash it successfully with my already previous made patched boot.img. Is there anything I could do to make both slots match again? flash my original Vbmeta perhaps? Or is it not a problem for the device? Thanks in advance!
[Google Pixel 8] badabing2003:
Good for you you got it back.

I don't know the exact state of your phone without seeing a support file, but what the messages is telling your that slot a and slot be verity / verification states don't match.

Do you disable verity / verification?, people usually do that when they want to flash custom kernel (not all need it)

But if you disable verification, then the phone requires a wipe, otherwise you won't be able to boot to system, and it won't tell you that you need a wipe.

You have check each slot's verity / verification state, PF usually tells you.

It's ok to go from disabled to enabled, that does not require a wipe, but if you go from enabled to disabled, you'd have to wipe.

Let's say your current slot is enabled, and the other is not, if you switch slots, you'd be going from enabled to disabled and won't be able to boot unless you enable it or wipe.
[Google Pixel 8] m4j0r4:
Sorry I completely forgot the support file!
[Google Pixel 8] badabing2003:
Your device is currently on slot a.

Which has vbmeta enabled, but slot b has then disabled.

Slot A Verity: Enabled
Slot A Verification: Enabled
Slot B Verity: Disabled
Slot B Verification: Disabled

Perhaps the thief flashed custom kernel on slot b and disabled vbmeta.

Do the OTA flashing again, just like you did the first time and the device should switch to slot b and both slots would have them enabled.
[Google Pixel 8] 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] Raz0Rfail:
Hi @badabing2003 I think i need your help.

My Pixel 8 was on Evolution X ROM 8.3

Today the author updated it to Evolution 9.0 and stated that on Pixel 8 it has to be wiped and the May update to be installed.

[ROM][14.0_r53][OFFICIAL] Evolution XYZ 9.2[07/07/2024]

Google Pixel 8, 8 Pro & 8a [Shiba][Husky][Akita] Pixel UI, customization and more, we are Evolution X! Joey Huab - Founder/Lead Developer Anierin Bliss - Co-Founder/Co-Developer Akito Mizukito - Co-Founder/Project Manager Reach us on...

xdaforums.com

So I downloaded the Google Factory Image for May for the Pixel 8 "shiba-ap1a.240505.005-factory-d0adedea.zip" and wanted it to flash with your Pixel Flasher.

I made all the settings including wipe all Data in Pixel Flasher. Then I started the Flashing Process.

The flashing was sucessfully and the phone rebooted and showed the Google Logo and some time later an progress bar.

But after an Minute it rebooted automatically, and then I saw again the google logo and the progress bar again and I let the device do it's things. But it rebooted again in the boot process and I thought I made an mistake somewhere.

So I hold the power button + Volume - button to kill the phone and reflash the ROM again.

Then immediatly afterwards I got an message in Windows that it wants to install an Pixel ROM Recovery driver which I let it install.

The phone goes off, but afterwards I'm unable to start the phone. No button mechanisms work. When I plug it into my PC i hear that an device is recognized, but I can't see the device in device manager.

With USBLogView I found out that the Pixel 8 shows now this information in the device manager:

View attachment 6101994

I don't know what failed this flashing process. I don't know if the adb plattform files in version 33 where the issue which leads to the point that my phone won't boot / react any more.

Attached is the support file, I hope you have an idea what happened and if I can recover the phone or that I have to ask google for an warranty.

Regards
[Google Pixel 8] badabing2003:
I'm afraid seeing a serial device is not a good sign. (Usually is a sign of hard brick)

What I see in the PixelFlasher logs is the following.

❌ 2024-05-12 09:22:48 ERROR: The selected path C:\adbLink\adbfiles\scrcpy does not have adb and or fastboot

ℹ️ 2024-05-12 09:22:53 Selected Platform Tools Path:
C:\adbLink\adbfiles.

❌ 2024-05-12 09:22:53 ERROR: Detected old or problematic Android Platform Tools version 34.0.4-10411341
2024-05-12 09:22:56 User accepted the bad version 34.0.4-10411341 of Android platform tools.
SDK Version: 34.0.4-10411341
Adb SHA256: 705ddc21f33ac52105d1b075b019962ad0e44fb3d560bde69ce8cb3a36bca183
Fastboot SHA256: 377ff87ec40a2a9b947e00b487f4f4a42b03e195612bdcd8a526b70a1b0a918a

I'm not sure why you decided to proceed even though the app warned you that the platform tools version you're using is known to have issues.

I don't know if it played any role or not, however what I see is that after the flash your device was in bootloader mode.

After which you decided to switch to 35.0..1

❌ 2024-05-12 09:22:48 ERROR: The selected path C:\adbLink\adbfiles\scrcpy does not have adb and or fastboot

ℹ️ 2024-05-12 09:22:53 Selected Platform Tools Path:
C:\adbLink\adbfiles.

❌ 2024-05-12 09:22:53 ERROR: Detected old or problematic Android Platform Tools version 34.0.4-10411341
2024-05-12 09:22:56 User accepted the bad version 34.0.4-10411341 of Android platform tools.
SDK Version: 34.0.4-10411341
Adb SHA256: 705ddc21f33ac52105d1b075b019962ad0e44fb3d560bde69ce8cb3a36bca183
Fastboot SHA256: 377ff87ec40a2a9b947e00b487f4f4a42b03e195612bdcd8a526b70a1b0a918a

but that's the end of Pixelflasher logs / involvement, not sure what else you did and using what tools?

I don't see this in the logs,

and that ROM Recovery driver message, I have never seen that and have no idea where you got that from? definitely not something PF pops.

If you can manage to put your device into bootloader or recovery mode, there is hope to revive, but if it gets stuck in serial mode, it needs to go for repairs or RMA.

Hope you can recover.
[Google Pixel 8] Raz0Rfail:
I used only the Pixelflasher to execute the flash operation.

After I couldn't boot the phone anymore I tried to use the 35. plattform tools to see if it could help.

I used in the past the 34. plattform tools which worked fine. But I had only flashed it in the past for the february update and it worked without issues.

The device description in windows device manager returns that is in Pixel ROM recovery. After what I have read, when the phone is in this state it's bricked and can only be recovered when the entire motherboard got replaced.

Guide: Unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven"

Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU This means that there is Exynos boot recovery in the CPU You can repair the bootloader using the Samsung Exynos Tool Nothing could be flashed from the mode, however it...

xdaforums.com

As I have the warranty for the Pixel 8 I chatted with the google Support and asked for an RMA.

Regarding:

This notification I got from Windows 10 notification center.
[Google Pixel 8] badabing2003:
Glad, to hear that you can RMA, it would suck to have such a device become a wasted door stopper.

If you did everything in PF, the logs should show, unless you captured the support file before doing everything there is no reason for it not to be in the logs.
[Google Pixel 8] Raz0Rfail:
I created the support file after the phone didn't boot anymore and hoped that you can see something.
[Google Pixel 8] 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] mebetree:
Hello im getting the pixel 8 tomorrow and i badly want to root and although i rooted all my old phones until 1 click became impossible. Is this a non pc method? Also judging from glancing through the thread this looks too complicated for my dumb self. I dont know what 95% of the terminology means. Being that the most difficult method of rooting ive used is odin, and i dont have access to a pc. How difficult is this method and again do i need a pc? Thanks.
[Google Pixel 8] bdr127:
Technically, PixelFlasher itself isn't doing the rooting... When you initiate the rooting process in PixelFlasher, it just uses underlying commands and programs to root your device. Easier to get those underlying programs from one place in PixelFlasher and issue all the correct commands automatically, rather than doing everything manually (mostly in a command-line terminal window).

Regardless, PixelFlasher does require a computer. It runs on Windows, MacOS, and Linux.
[Google Pixel 8] mebetree:
I see thank you for the reply. Is there any method you know of that would enable me to root my pixel 8 using my galaxy s14 5g using that adb app to sideload commands possibly or without a pc? Thanks again.
[Google Pixel 8] bdr127:
There might be a way using osm0sis' adb ndk Magisk module..... but that assumes your other phone is already rooted with Magisk and also supports USB OTG. I don't know anything about that method and have never used it. Regardless, it is definitely off-topic for this thread.

(EDIT: The adb ndk module won't help you unlock the bootloader because that's done via fastboot..... So I guess the answer is "no", or at least "I won't know of a way.")

BTW, I assume your other phone is either an A14 or S24? (Because I've never heard of an S14, and a web search didn't show anything.)
[Google Pixel 8] 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] cswithxda:
Appreciate the great tool. I have been successfully using it to upgrade my pixel 7 by flashing factory images without wipe. And I have never bothered about the inactive slot, i.e. I was probably always using one slot and never switched slot on Pixel 7.

This week I got a new Pixel 8. I unlocked the BL, and was trying to (in the following order):

1. Start Pixel 8, skipping any unnecessary setups, in order to get into the OS, and enable ADB;

2. Connect Pixel to the computer, on PF process the latest factory image, patch;

3a. With wipe option enabled, select patched boot and flash to both slots ( for this step I also tried select original boot and flash to both slots);

3a. With wipe option disabled, select elect patched boot and flash to both slots ( for this step I also tried select original boot and flash to both slots);

3c. Flash patched boot to slot a, and then manually switch to slot b to flash patched boot again, wipe option enabled;

3d. Flash patched boot to slot a, and then manually switch to slot b to flash patched boot again, wipe option disabled;

Outcome: 3a - 3d all result in one of the slots getting a boot loop. For example, after testing slot a and being able to see the setup wizard, I would reboot to bootloader, switch to slot b and start, but this always leads to a boot loop.

I'm scratching my head because in the past I mostly used command line to flash just one slot, for monthly updates.

I do remember when initially setting up my Pixel 7, I manually flashed factory image to both slot, but never bothered to check if both slots boot OK.

Could you please help me understand what's going on? I'd hate to leave one slot crippled and set the new device up just to find out later down the road that I'd have to do a wipe flash.

Much appreciated.
[Google Pixel 8] badabing2003:
With factory flashing you can never get both slots bootable.

What you are experiencing is expected.

We've discussed in PF threads the exact reasons why that is the case, and it has nothing to do with PF.

Use full OTA image instead of factory and you'd get both slots bootable.

And it's safer than factory.
[Google Pixel 8] cswithxda:
Thanks for the quick reply. I did a more detailed read in this thread and found some relevant posts below (the last one I found it in Pixel 7 forum). I now understand that OTA is safer especially for a new phone, but I still do not understand why flashing factory image to both slots will render one of them unusable. Would you be so kind in guiding me to the correct post of explanation (for my own education further down the road)?

For now, I guess I will first get this device set up so I could start using it.

So would the following proposition be correct and the most time efficient way:

1) Flash the already patched factory image to slot a, in order to get one working slot with root;

2) Flash the corresponding full OTA (in my case, 240505.005) to slot b, making it "identical" with slot a, except for init_boot (I intend to keep slot b with no root);

3) Test if both slots boot fine, and eventually pick slot a to start a data transfer from P7 and setting it up.

The reason for "1) flashing factory image to slot a" has part to do with my OCD, in that I'd like a totally clean start after so many careless test flashings in the past two days.

Or I suppose I could also do:

1) Flash the already patched full OTA to slot a, in order to get one working slot with root;

2) Flash the corresponding full OTA (in my case, 240505.005) to slot b, making it "identical" with slot a, except for init_boot (I intend to keep slot b with no root);

3) Test if both slots boot fine, and eventually pick slot a to start a data transfer from P7 and setting it up.

But I'm not sure if the second procedure would be as clean of a start as the first procedure.

Again, thanks for a great tool, and your help is much appreciated!

***Relevant posts I found:
[Google Pixel 8] Lughnasadh:
This should explain it...

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com