yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] trox5361:
vandyman was trying manually. As was I because both my computers were having different issues with your flasher. Coming from pixel 5 for which boot.img was the correct file to patch.
[Google Pixel 8] vandyman:
Exactly.

I have been patching the boot.img since the beginning of the Nexus days.

And thanks for pointing out the init_boot.img.

I just wanted to try this flasher software to save some time in typing and booting...

I will give it a go again on the next os update.
[Google Pixel 8] swords90:
Hello all!!

I just received my pixel 8 and I wanted to root it but I'm a little confused about how to...

Is there a simple guide to do it??

Thanks all!!!
[Google Pixel 8] vandyman:
If follow the steps described in the first post you will be golden.(click on the main link thread for a step by step)
[Google Pixel 8] vandyman:
I now have root and have posted the details in the magisk thread.

In the future, do I need to remove the magisk modules to root with an ota?

Just wanted to make sure if I use PF from here on out.

In the past the modules needed to be removed on my Pixel 6 or magisk would get corrupted.
[Google Pixel 8] badabing2003:
It all depends on the modules, USNF can be kept enabled without ill effects, but other modules are not as safe.

You don't have to remove them, just disable them.
[Google Pixel 8] vandyman:
Safetynet and magisk systemless is all I use.

Thanks.
[Google Pixel 8] badabing2003:
Then you don't have to worry about disabling them.
[Google Pixel 8] badabing2003:
New Release:

Oct 18, 2023 v5.8.2.0 release

Added `Wipe` option (only available in custom flashing), this will wipe userdata after flashing, required for first time vbmeta verification disabling.

Added validation checks to make sure A and B slot vbmeta verity / verification states match.

Added a warning when toggling `Disable Verification` to inform about the the potential wipe implications.

Display both slots verity / verification states when displaying device details.

Extract vbmeta.img if found to easily select it for patching.

Improved paste button which now dynamically selects what to paste based on the custom flash option selection.
[Google Pixel 8] fullmetal509:
Is there a Guide or Video how to root/unlock via Mac? Having hard time figuring it out lol. Tried rooting manually by terminal commands but kept getting stuck at fastboot mode screen.

Luckily Googles Android Flash tool has helped restore it back.

Pixel 8
[Google Pixel 8] badabing2003:
Have you tried the main thread's OP
[Google Pixel 8] fullmetal509:
Ending up using this guide.

Thank you!

Worked
[Google Pixel 8] badabing2003:
Just be aware that, the video is using factory image, and the current recommendation is to use full OTA image, as it is safer if anything goes wrong.
[Google Pixel 8] fullmetal509:
Thank you will take a note of that next time!.

ATM eveything seems to be working as normal.

Couple Majisk Modules flashed
[Google Pixel 8] Lughnasadh:
In case you didn't see, just saw over at the Kernel Flasher thread where someone was having problems using the flasher on their Pixel 8 Pro. Turns out it was because slot B was completely empty. So some confirmation on one slot being empty on new phones.
[Google Pixel 8] badabing2003:
Thanks for keeping me in the loop.

Just to be clear, when yous say

Is that kernel flasher issue or PixelFlasher issue?

I usually keep an eye on that thread but I haven't noticed it.
[Google Pixel 8] Lughnasadh:
Kernel Flasher. Kernel Flasher is working fine on this device, it appears, but this one user never flashed anything to the inactive slot so Kernel Flasher couldn't find a valid kernel from that slot, because it was empty, which in turn produced an error. He has a test build that will ignore a bad slot to solve this issue.
[Google Pixel 8] badabing2003:
ok, got it thanks,

I appreciate you keeping me in the loop.
[Google Pixel 8] TotalChaos71:
Used your utility, very nice. Unlocked Bootloader, downloaded, patched and installed. Gained root OK, but when I boot the phone a message comes up that states "Your device is corrupt. It cant be trusted" If I click the power button past it, I get the normal Bootloader Unlocked screen, and the phone boots fine. Is this something I should be worried about? Or is there a fix? Thanks in advance.
[Google Pixel 8] badabing2003:
The message is harmless, aside from the fact that you have to click the power button to continue.

There is a way to clear that if you really want to, or you can wait till next update flashing and it will clear.

There are two known approaches that have work to some extent.

Flash full OTA firmware again, this has resolved the issue for many.

Or Just an old boot image, don't reboot to it as it won't, and then flash again the current boot image.

If it is not bothering you, just wait for the next update, should be soon anyways.
[Google Pixel 8] Toastking:
Hi,

thanks for creating this tool!

I have just received my Pixel 8. Haven't even opened the box yet but I'm going to use your tool to root the phone. It has been a few years since I've last rooted an Android phone though (long before Magisk was a thing), so I hope you can help clear 2 more things up:

1. You recommended using a full OTA image for the process. On Google's full OTA image download site, there are 5 images for the Pixel 8 available for download. I'm located in Germany, EU - which one am I supposed to use? Intuitively, I would say the bottom one ending with "397c7bc" in the checksum?

2. The concept of "inactive and active slots" is new to me. I suppose these slots both hold a full system image independently and are used by Android in order to be able to rollback in case an OTA update fails? So, to a normal user, the "inactive" image will never be visible and never be booted? If that's the case, why are you recommending to flash the OTA image to both slots?

You also mention that one could only root one of the two slots. Why would anyone do that if they are unable to choose which slot to boot from when turning on the phone?

Thanks again, I'll report back if all went well!

Please let me know if you want me to test something specific, as I've mentioned I haven't even unboxed the phone yet.
[Google Pixel 8] badabing2003:
That's the only October release, and I'd assume it is universal, I'd use that.

I recommend to flash OTA twice (to end up having the same on both slots) because for whatever reasons if something goes wrong with your current slot, you still have the other slot which would be bootable.

PS: There is only one data partitions, of if you mess that up, system wise the other slot would be good, but the data would not be.

you can root, both slots, there is no limitation on that, some people to choose to root only one so that they can boot to it when they want to run application that detect root and refuse to run.

But that's a totally different topic how to bypass root detection, and there are many dedicated threads about it.

If you're rooted, you can choose to switch slots from the phone by using an app, Boot Control written by @capntrips

If you're not rooted, you can do it from the PC.

You can use Switch Slot button in PF or do it from command line.
[Google Pixel 8] johnsmallberries:
Is slot a supposed to be bootable? I patched and flashed twice. Seems the phone is currently rooted and booted into slot b, but if I boot slot a it says device is corrupt and all I get is the google logo. I had to force it back to use slot b.
[Google Pixel 8] pixel8kid:
I am in the same situation, I am currently booted on slot B. How do I ensure I have something on Slot A so I don't get stuck booting to it. Do I simply flash with pixel flasher one more time? Will I lose all my data again?

Before I ever flashed I accidentally hit "Switch Slot" or whatever in pixelflasher and got stuck on the G logo for a very long time. Eventually I was able to get it booted, and flashed, but I'm not sure if I have anything on slot A at all.
[Google Pixel 8] badabing2003:
@johnsmallberries and @pixel8kid support file please
[Google Pixel 8] badabing2003:
I took a look at your logs.

Your slot a is blank (brand new device ships with one slot not having the necessary data), you have not flashed the OTA to slot a, you have just patched init_boot and applied, that is why your slot a is not bootable.
[Google Pixel 8] johnsmallberries:
I'm a little confused why I had to flash boot twice though.

First time after flashing patched boot I did not have root. Had to flash twice.

Maybe first time flashed to A which was useless anyway, and the 2nd time B.

To get A to work, then we should wait for the new OTA to come out and flash?
[Google Pixel 8] badabing2003:
No the first time it was flashed to b as well.

How did you check if you had root?

in PF or in Magisk?

PF will not detect root until you grant adb process root access.

Usage | Basic Mode | Step 3
[Google Pixel 8] johnsmallberries:
After the first flash I went into Magisk.

Ramdisk was NO. Superuser button was greyed out.

I did not use PF to verify su because I couldn't grant it root anyway. Maybe I accidentally flashed the regular boot but I thought I flashed the magisk patched one the first time.

What is the recommended way to populate A with something bootable? Wait for the next OTA and just flash it?
[Google Pixel 8] badabing2003:
Sometime on first launch of Magisk, it needs to perform further actions, did you get that?

To make the other slot button, use OTA image and then:

Use the Flash Pixel Phone button.

See usage in main thread's OP
[Google Pixel 8] pixel8kid:
Just wanted to report that after reading the above replies, I flashed again and can now switch between slot A and B to boot. I have root on both which is great! I have been using the OTA image. For updates do I just download and flash the new OTA image?

Anyways, I wanted to thank you so much for this tool and your help and support. This is my first time rooting android, and I'm already loving the community and the possibilities root provides.
[Google Pixel 8] badabing2003:
Yep
[Google Pixel 8] drilldrill:
Thank you for the software!

I flashed to slot A and rooted successfully. I tried to flash again so that I could get it on slot B, but now slot B is the only slot that works and slot A gives me the message that "Your device is corrupt".

Should I try switching the slot to A and then flashing on it again?
[Google Pixel 8] badabing2003:
First time you only flashed the patched boot to an empty slot.

The second time you flashed a newer full OTA image to slot b, which effectively made slot a unbootable.

Both slots have to match to have them both bootable.

Just flash full OTA which will flash to the inactive slot and make both work.

Notice the Device build differences

Selected Device on 2023-10-24 11:25:20:
Device ID: REDACTED
Device Model: shiba
Device Active Slot: a
Device Mode: adb
Has init_boot partition: True
Device is Rooted: True
Device Build: UD1A.230803.022.A5
...

Selected Device on 2023-10-24 11:46:16:
Device ID: REDACTED
Device Model: shiba
Device Active Slot: b
Device Mode: adb
Has init_boot partition: True
Device is Rooted: True
Device Build: UD1A.230803.041
...
[Google Pixel 8] drilldrill:
Thank you, that worked!
[Google Pixel 8] johnsmallberries:
Was it common to get previous pixel's from the factory with only one slot populated? If not it might be a good idea to add a warning for new Pixel 8 factory phones which seem to be coming with only one slot. If you try to get both slots to work it can temporarily result in a boot problem unless a and b are the same.
[Google Pixel 8] badabing2003:
Yes all Pixel ship with only one slot populated.

if you try to get both slots to work, you would try to flash OTA twice, and if you do, then there should be no problems at all.

The issue is if you flash only one slot. and you choose factory instead of OTA, which will inherently flash into the current slot, which is by the way the only functional one on a brand new device, and something goes wrong during flashing, you could end up with a brick, because you messed up the current slot and the other slot is empty.

That is why the recommendation is to flash OTA.

Twice if you want both slots bootable, (bootable as in bootable all the way to system) if you don't care about both slots, then flashing OTA once should be enough.
[Google Pixel 8] badabing2003:
New Release:

Nov 12, 2023 v6.0.0.0 release

More verbose logging and additional debug messages for troubleshooting.

Renamed the Verbose label to Debug.

Improve UI responsiveness when running background tasks.

Automatically detect vbmeta state for both slots, and warn if the selection would have wipe implications (this is for verity / verification disabling).

Removed Check Verity button, (verity / verification), replaced with vbmeta state reporting for both slots as part of device details.

Show Bootloader version as part of device details.

Show slot related details such as slot-retry-count, slot-unbootable, slot-successful as part of device details.

Added Reboot to Sideload option.

Graphical display of device's slot and root status.

In most cases long background processes are automatically killed with proper timeouts (when possible) and reported to unfreeze PixelFlasher.

Reworked device detection / update / refresh, reboots, PixelFlasher now automatically detects device state changes and waits exactly the time until the device state changes to the expected state. Less dependency on arbitrary timeouts.

Improved support logs sanitization.

Detect free space on the computer and block flashing if less than 5G of storage is available.

Refactor flashing function.

More response console widget log messages.

Detect currently installed OS version and block flashing older OTA (Android by default allows flashing but fails to boot).

Detect, warn and block flashing if bootloader is locked for flashes that require bootloader to be unlocked.

Added wipe option for custom flashing to easily wipe the phone when flashing vbmeta to disable verity / verification.

Report if the device is unlockable.

Bug fixes, lots of changes under the hood and miscellaneous improvements.

Added option to delete specified libraries from the PixelFlasher bundle, to let the system library be loaded instead. Needed for newer OSes that require updated libraries. See Symbol Lookup Error #109, and After a large system update (manjaro), do not work now. #111

Additional support for Scrcpy of non-Windows platforms.

Updated XDA links
[Google Pixel 8] outcubus:
Hi. I'm new to the Pixel scene but I managed to root my P8 with PixelFlasher. Great tool @badabing2003 , congrats.

So...I tried, minutes ago to install the November update with PixelFlasher v6.0.0.0, but it continues on october build and when I go to System Update it tells me that an update is available and that in 2 days my "device will automatically install the update and schedule a restart".

I must be doing something wrong. These were the steps I took:

Unhided magisk and disabled all modules on my P8 and restarted the phone;

Connected my phone to PC and run PF;

Downloaded and selected last OTA image "shiba-ota-ud1a.231105.004-49029a3a.zip", then Patched on PF;

Selected the patched init_boot, and Flashed Mode OTA;

Pressed Flash Boot;

After some seconds phone rebooted and the process was finished but with no updated build.

I just want to update without losing root/magisk and data.

I've read the OP a few times but I'm missing something...

Need some help please.

Thanks
[Google Pixel 8] badabing2003:
You have to hit the Flash Pixel Phone button, not Flash Boot button.

The former applies the OTA / firmware update and the patch, the latter just applies the patch.
[Google Pixel 8] outcubus:
oh god. how can I missed the big button...so dumb.

Of course it solve the problem.

Thanks for your help.
[Google Pixel 8] badabing2003:
New Release:

Nov 13, 2023 v6.0.1.0 release

Added settings option to enable / disable free storage space check.

Improve storage check to follow symlinks and return the partition free space where the data resides instead of where the symbolic links resides.

Added command line support for specifying PixelFlasher config json file, use -c or --config flag followed by full file path of configuration json file.

Added command line --console (only useful on Linux / Mac) to display all PixelFlasher output to console, useful when troubleshooting.

Further improved handling of large file extraction on low memory computers.
[Google Pixel 8] badabing2003:
Update Release:

Nov 14, 2023 v6.0.1.1 release

Bug fix: Make sure Low memory settings are loaded at startup.

After flashing factory or OTA, on last reboot to system, increase the wait from 60 to 90 seconds to make sure the device loads all the way to system and does not timeout PF. Although the error message is benign, it creates unnecessary anxiety seeing an error message in the console and thinking that something is wrong.

Bug fix: Available storage was not computed correctly on Linux platform.

Fix and speed up MacOS platform build.
[Google Pixel 8] me_droid:
Thanks for this utility - I'll be using this to root (hopefully!) a new just out of the box Pixel 8. I have a few questions, one is can I flash the OTA twice in the same session (by checking Flash to both slots) or does the device need a reboot in between? Second question, I am not familiar with verity and vbmeta - I gather from your posts that these do not need to be touched unless I plan to install a modded OS. Just want to verify these items before starting.
[Google Pixel 8] badabing2003:
No you can choose flash both slots with OTA, it's one at time (it's written in OP), besides even if you could would you want to risk it? in case anything goes wrong, you'd be out of both slots.

Your understanding of verity / verification is correct, stay away from touching those unless you plan to flash custom ROM / Kernel, besides many of them don't even need them disabled anymore.
[Google Pixel 8] vaibhav palande:
Hi all,

I have a rooted Pixel 8 with magisk. I rooted with PixelFlasher. I am getting update failed problem.

View attachment 6033331

I searched online and came across a post that said PixelFlasher can be used for this while keeping data and keeping root.

Question:

For the update, am I supposed to use the latest OTA image or factory image ?

Are the following steps correct when using PixelFlasher to do this update ?

Connect phone to PC and select it from the list in PixelFlasher. (Shows a checkmark for already rooted device)

Select image for latest update -> Process.

Select boot image -> Patch

Select patched image, select Keep data option and Flash Pixel Phone

Regards,

Vaibhav
[Google Pixel 8] badabing2003:
Full OTA image is the recommended method.

The OP of the main thread outlines the steps with explanation, it should be clear, but if you have questions on those steps, come back and ask.

Non-device specific questions / support should be posted in the main thread so that others benefit from it.
[Google Pixel 8] me_droid:
So I've gone through all steps to the point where I've patched init_boot with Magisk and am ready to root. My options to flash include only Flash Boot - I don't see a Flash Pixel Phone option. I assume that since I have the same version already installed, I don't need to flash the phone, just boot. Here's what I see:

View attachment 6033393

Before I go further, let me know if Flash Boot is going to produce the desired result.

Thanks!
[Google Pixel 8] badabing2003:
If you have already the same version installed, you're correct you don't need to flash the entire phone, you can just hit the Flash Boot button.

As for why you're not seeing the Flash Pixel Phone button, make the window larger, it's below Flash options,

There is also a handy console below it.

If you are short on vertical real estate, you can hide the Toolbar or move it to the right / left from the Toolbar menu
[Google Pixel 8] me_droid:
LOL, yes, should have figured! Forgive me for being paranoid, but when I clicked Flash Boot, the next window indicates boot.img path, not init_boot:

View attachment 6033398

Can I assume that it's patched init_boot in this case?
[Google Pixel 8] me_droid:
Nevermind, looking through the console history, I see that PixelFlasher used init_boot
[Google Pixel 8] badabing2003:
Update Release:

Nov 15, 2023 v6.0.1.3 release

Cleanup temporary created files when using low memory option.

Don't wait for device to be available in adb when wipe option is selected. (The user would need to setup the phone for the first time, enable developer options and enable debug, which could take a while)

Add more debug messages for troubleshooting.

#117 psutil is not reporting free storage correctly on Linux platform, use shutil module instead.

Print available memory when processing Image.
[Google Pixel 8] badabing2003:
New Release:

Nov 16, 2023 v6.0.2.0 release

Removed Magisk alpha from Install Magisk module (update link is broken).

Added Special Magisk build based on versionCode 26401 that disables loading modules but keeps root, to help getting out of bootloop due to bad modules.

Bug Fix: #117 check for disk flag finally working correctly.

Bug Fix: #118 add wrap boot path in quotation marks.

With dry run selected, don't attempt to flash the patch file.

Block patch flashing if bootloader is locked.

Add settings option to bypass block flashing if bootloader is locked.

Added more debug messages on failures to further ease the troubleshooting efforts.
[Google Pixel 8] badabing2003:
New Release:

Nov 18, 2023 v6.1.0.0 release

Renamed Magisk Modules button to Magisk as it now offers additional settings management.

Add features to manage Magisk settings through PixelFlasher. Needed for Pixel watches, as Magisk Manager app is not watch friendly.

Features available so far:

Enable / disable Magisk modules

Install Magisk module.

Enable / disable Zygisk

Enable / disable Magisk denylist

Add / remove application to Magisk denylist

Grant / deny / SU permissions to an app, with control of: screenshot

Enable / disable notifications

Enable / disable logging

Grant until (Forever, 10 min, 20 min, 30 min, 60 min)

Revoke SU permissions

Added Pixel watches to the devices list to provide additional details when a Pixel watch is selected.

Added icons to the popup menu in App Manager. screenshot

Factory / OTA download link is now a single button with a dropdown list of:

Full OTA Images for Nexus and Pixel Devices

Factory Images for Nexus and Pixel Devices

Full OTA Images for Google Pixel Watch Devices

Factory Images for Google Pixel Watch Devices
[Google Pixel 8] maxmax0:
Wow, this is AWESOME! Cool new features, thank you!
[Google Pixel 8] badabing2003:
New Release:

Nov 22, 2023 v6.2.0.0 release

Added Magisk module update detection and updating.

Add button to install Play Integrity Fix module by @chiteroman

Added gui to pull / edit and push pif.prop file. (If there is interest I will add the ability to pull pif.prop values from system, using @osm0sis script)

Added Systemless Hosts module install button.

Maintain a list of unlocked bootloaders in memory to skip over extra unlock checks.

#121 Removed Delta Magisk from Magisk Install options (update json no longer published).

Removed the functionality that automatically finds and adds platform tools from the system, it is now required to select the desired platform tools.

Bug fixes and improvements.
[Google Pixel 8] c19932:
hey guys im new to Pixel and would like to ask a few questions. I am on pixel 8 rooted with magisk delta, verity and verification disabled.

1) when it's time to update with pixelflasher, do I use the full image or OTA image?

2) with my verity and verification disabled, in order to prevent data wipe when I update, all I have to do is click "disable verity" and "disable verification" when I update via pixelflasher, correct?

3) I am on magisk delta. When I update, how do I retain root with magisk delta? (not regular magisk; I use magisk delta strictly)

thank you very much for your help