yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] 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 Pro] Ultimoose:
November firmware flashed, no drama, no problem.
[Google Pixel 8 Pro] 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 Pro] 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 Pro] cmh714:
Hoping I can get you to fix what I believe would be considered a small bug as it probably effects very few......like me! :)

I havent switched to using PixelFlasher due to this but havent reported it either, as old school works fine for me but would like to use your app.

In Windows, my user name has a space which causes the Open Folder and Open Working Directory to fail

So its like this: "C:\Users\First Last"

If you have another workaround thats fine too!

TIA!!
[Google Pixel 8 Pro] badabing2003:
Handling space in paths have been addressed long time ago, try and report if there are issues, with support files.
[Google Pixel 8 Pro] jcp2:
@badabing2003 Question.... I got my new P8 Pro yesterday and unlocked the BL and updated the OS to Nov build and Rooted with Pixel Flasher. I saw somewhere that there is a risk of bricking the phone if both slots don't have a bootloader installed. My question is: do I only just need to flash the init_boot.img with Pixel Flasher to the inactive slot to avoid the possibility of hard bricking the phone, or is more required?
[Google Pixel 8 Pro] badabing2003:
No don't do that

First question, did you do you use full OTA or firmware?

If you used full OTA, it already flashed it to the other slot, so your device should now have both slots at least bootable to bootloader.

If your did firmware method, then I suggest you do the full OTA to minimize the risk.

And if you want both slots fully bootable, just do the full OTA a second time.
[Google Pixel 8 Pro] jcp2:
Thanks for the quick response. I unlocked the BL, installed Magisk, then I used pixel Flasher to pacha & flash the full (not Ota) firmware file that I downloaded. That is how I've been doing it on my P6 Pro. I spent hours setting everything up. So I guess my next step should be to download the OTA file and sideload flash it twice in ADB Platform Tools? This will unroot me, but not erase my data/settings correct? Then I just have to re-root again? Sorry for all the questions. Thanks for your help.
[Google Pixel 8 Pro] badabing2003:
Just check OP of the main thread, you can do it all in PF, the same way you do firmware, just load OTA file.
[Google Pixel 8 Pro] jcp2:
Awesome. Thank You for your time and hrlp.
[Google Pixel 8 Pro] badabing2003:
New Release:

Nov 26, 2023 v6.2.1.0 release

New feature: Added Bulk apk install capability. Point to a directory where the apk files are and all of those would be installed.

New feature: Extract current device's Pif print.

New feature: Push a file to /data/local/tmp

New feature: Push a file to /sdcard/Download

New feature: Kill Google GMS (for testing different pif.json files without needing a reboot)

Updated pip.prop editing to pif.json (with syntax coloring).

Option to create pif.json if one is missing.

Miscellaneous improvements.
[Google Pixel 8 Pro] cmh714:
Support file attached. Having issue with space in file paths (so I believe)....TIA Badabing!!
[Google Pixel 8 Pro] badabing2003:
I don't see any issues in the logs, what makes you think that there is a space in file parts issue?

What is the problem?

What are you doing? What are you expecting? What are you getting instead?
[Google Pixel 8 Pro] cmh714:
If you look at the screenshot I previously posted, you will see the error. But basically it seems everything loads correctly, but if I click on Open folder or Open Working Directory I get the error. I was just concerned that something might get goofed if I try and flash.....didnt want to hose myself up by accident.

TY Again!!
[Google Pixel 8 Pro] badabing2003:
I only see the support file, no screenshot.
[Google Pixel 8 Pro] cmh714:
This post Sir! https://xdaforums.com/t/pixelflasher-for-google-pixel-8-pro-support-thread.4635555/post-89177766
[Google Pixel 8 Pro] badabing2003:
I'm sorry, I totally missed that screenshot.

I'll get it fixed, it's when opening the folder or working directory in explorer, it shouldn't impact other areas of PF, you can safely use it to create patch / flash
[Google Pixel 8 Pro] cmh714:
No worries! and again, TY for all your efforts here!!
[Google Pixel 8 Pro] badabing2003:
Fixed:

Release Release v6.2.1.1 · badabing2005/PixelFlasher

Show Magisk application / root versions in the Magisk UI. Disable Push file menu when a device is not selected Disable Bulk Install menu when a device is not selected Bug Fix: When opening a window...

github.com
[Google Pixel 8 Pro] HipKat:
It won't unroot you, like @badabing2003 said, just use the OTA going forward
[Google Pixel 8 Pro] jcp2:
The reason why I used the full firmware first, is because I always had to use the full firmware with my P6 pro because I was running a custom kernel and OTA's won't install while runng custom kernels. So when I got my P8 Pro, it was a habit. Has the "no Ota updates while using a custom kernel " rule changed with the P8's?
[Google Pixel 8 Pro] badabing2003:
No,

OTA on the phone is typically incremental, meaning that it has to match exactly what it expects so that it can patch the diff.

That is why it doesn't work.

OTA when sideloading is a full OTA, so no need to match anything, just overwrites.
[Google Pixel 8] badabing2003:
View attachment 6019961

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel 8 devices, generic issues that are device agnostic should be discussed in the main thread.

For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 8] badabing2003:
Update Release:

Oct 11, 2023 v5.8.1.0 release

Added data for Pixel 8, Pixel 8 Pro

Build workflow update, sha256 checksums are now published along the binaries.
[Google Pixel 8] swords90:
Thanks alot!!!
[Google Pixel 8] sean222:
Thanks!!!!!! Made rooting this device super easy :)
[Google Pixel 8] t-ryder:
Unlocked bootloader with Pixel Flasher, installed magisk, downloaded latest full OTA. Processed it, patched it and flashed it in full OTA mode. Device does not boot anymore. Getting the error message in the screenshot.
[Google Pixel 8] t-ryder:
Repeated the whole thing but with factory image to only inactive slot. Worked.
[Google Pixel 8] badabing2003:
@t-ryder

If you create a support file, I'll take a look to see what happened.
[Google Pixel 8] badabing2003:
Thanks for the support file.

For the benefit of others, I looked into the support file and this is what happened.

You went from stock to flashing full OTA patched with disabled verity and verification and rooted init_boot.

The first time you patch vbmeta, the phone needs a wipe, that is why you get that message, and the second option would do that.

However when you select a wipe, all the data will be wiped, which also includes the OTA data as by design it gets written to userdata,

Because of that the system would revert the OTA and boot back to the original slot.

It's possible that if you attempted adb reboot, it would have switched to the original slot without a wipe.

The proper procedure for first time patching vbmeta would be

do that first including the wipe and then do the OTA update / patch

It is also recommended that when patching vbmeta, you patch both slots so that you don't get caught with one slot having it enabled, in case you boot to it and boot to the other, it would require a wipe again.

Here's the manual way to perform disabling verity / verification for the first time.

adb reboot bootloader
fastboot --slot all --verbose --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot

This will patch vbmeta on both slots, and do the wipe and reboot, after that do whatever you want.

I'll add a button in PF for first time vbmeta patching to make this option seamless, and put out a warning that it will wipe userdata.
[Google Pixel 8] t-ryder:
So you mean for the next update in Nov. I should go for the full OTA file update, patched/rooted flashing to inactive slot? Or both? What's recommended again? Sorry, sometimes I forget stuff. Must be me getting old.
[Google Pixel 8] badabing2003:
When you flashed factory, did you flash to both slots?

Edit:

I checked the logs, you're good you flashed both slots, so you have vbmeta patched on both slots.

Next update (possibly sooner than November, seeing that Google has only published August images for your device)

Download full ota

process

patch

there is no option to select inactive slot, because OTA is always inactive slot, there is also no option to keep data because it is also always keep data.

make sure you select verity and verification disabling (seeing that you had them already disabled)

Flash pixel phone

When Android finishes the optimization, for good measure, I'd click on Flash Pixel phone button again, to flash to the second slot (you can choose to keep one rooted and one not, it is up to you)
[Google Pixel 8] Raz0Rfail:
I want to inform you that Google messed up with their own naming convention for the initial P8 build.The zip file and the files in it says it's containing the august security update on Android 14.

Indeed it's already on the October build, I was positive surprised after I flashed it and that it was already on October security patch.
[Google Pixel 8] vandyman:
I tried using this tool, but for some reason it would not let me select the patch option.

So I tried to manually install magisk using fastboot. It seemed to flash ,but magisk did not install

I am not sure what is going on.
[Google Pixel 8] badabing2003:
Patch option is a enabled in advanced settings.

Without support file I have no idea what is happening.
[Google Pixel 8] vaibhav palande:
Hi @badabing2003,

This is my first time using PixelFlasher. I want to use it to first time unlock the bootloader and root my new Pixel 8.

I read the procedure on PixelFlasher main thread and also read multiple posts in the forums for P8 and P8P just to get an idea of what people were saying. Based on this reading, I think I need to perform following steps to unlock bootloader and root my P8.

Can you please let me know if these are correct and answer questions ?

I have already downloaded latest PixelFlasher 5.8.1.0, platform-tools, USB drivers and factory image from "shiba" for Pixel 8 (shiba-UD1A.230803.041 because that is the version on my phone).

Enable USB deebugging. Do I need to enable OEM unlocking ?

Open pixel flasher, (platform-tools are automatically recognized by the tool because I have PATH set)

Select phone from the list of ADB connected devices.

Device -> Unlock bootloader and follow prompts on the phone.

I am aware that this will wipe all data.

Anything else I should be aware of ?

After the bootloader unlock process, reselect phone in ADB connected devices list on PixelFlasher.

Select factory image and process it.

Select init_boot.img from the list and patch it with Magisk using Patch button on PixelFlasher.

Select flash mode of WIPE all data (since I am not using this phone yet. I think I would rather select wipe to start fresh).

Click on Flash Pixel Phone and see the magic happen.

Additional questions:

I see in this comment, you mentioned to select [advanced mode options] both slots and select disable verity but the post also mentions that this is for OTA. Does this also apply for factory image ? Do I need to do this ?

Also in the same post, you mentioned "When Android finishes the optimization, for good measure, I'd click on Flash Pixel phone button again, to flash to the second slot"

Did I miss anything ?

Any gotchas to look out for ?

I appreciate the help.

Thanks
[Google Pixel 8] badabing2003:
I prefer to do it with full OTA images, and I have given the reasoning of my preference in many posts, but you could do it with factory as well, the issue with factory is if anything goes wrong, you bootloop, which is ok, but with brand new device where the inactive slot could be empty, it could be worse, like a brick.

1- check

2- check

3- check

4- check

4.1 go through phone setup as it will be wiped

4.2 enable developer options again, and enable USB debugging and authorize your PC

4.3 Install Magisk

4.4 settings | enabled advanced options.

5- check

6- Check, or select full OTA image

7- check

8- No need to wipe, you just wiped in step 4 anyways, besides you will make it more difficult as you need to install Magisk again to be rooted, if you use factory image, select flash both slots.

9- check

10- if you you used full OTA image, do step 9 one more time to flash the other slot. (OTA images can only be flashed one slot at a time, that is why you repeat the step 9)

you don't need to disable verity / verification unless you plan to flash rom / kernel that needs it.

If you need to, then disabling verity / verification should be done step 4 as that will involve yet another wipe.
[Google Pixel 8] vaibhav palande:
Thanks. I will use full OTA image.

4.3 Instructions say when I click patch, magisk will automatically be installed.

Do I download and install latest apk of magisk from here ? OR just install magisk using PixelFlasher witn Install Magisk button ?

4.4 Is this enabling advanced option in PixelFlasher ?
[Google Pixel 8] badabing2003:
4.3, right if you try to patch and PF does not find Magisk on your system it will open the Magisk installation window for you to select the variant.

Or you could do open that dialog before clicking the patch, the end effect is the same.

4.4 yes
[Google Pixel 8] vaibhav palande:
@badabing2003

This worked like a charm. Thank you very much for this awesome tool. Rooting a phone has never been easier.

App is even more useful because of additional features of ADB Shell, Scrpy and Magisk Module manager.
[Google Pixel 8] trox5361:
I had the same problem. Figured out that I was patching and flashing the wrong file.

Need to patch and flash the init_boot.img
[Google Pixel 8] badabing2003:
I don't know how you can manage to patch the wrong file with this tool, it actually knows what to patch and patches the right file for you.

Curious to find out.
[Google Pixel 8] Koeties:
Same here. This tool is the bee's knees!
[Google Pixel 8] badabing2003:
New Release:

Feb 16, 2024 v6.8.0.3 change log:

Added untested support for patching with KernelSU for Pixel phones. Patching with APatch is in the works.

Detect known blacklisted kernel names, and notify the user. (list is current as of this release date).

Rename the SOS button to reflect that the modules would be removed instead of being disabled.

Removed bulk install APK feature which installed all APKs in a directory, instead reworked the Install APK feature to allow user choice multi-select, and added another option Bypass low target SDK block.

Report device Kernel and KMI.

Added Android Platform Tools 34.0.4 to known problematic versions list, which when detected warns the user.

Improved Pixel Watch flashing dialog messages.

New feature: #152 Show System Apps and Show 3rd Party Apps in Package Manager.

Bug Fix: #157 'PifManager' object has no attribute 'first_api' in some situations.

Bug Fix: scrcpy download link was not working.

Support for upcoming PlayIntegrity Fork v8 changes by @osm0sis.

Added Special Magisk 27001 install option when selecting Magisk install. (This is similar to Special Magisk 26401, just a version difference).

Support for SSL error fallback for all https requests (previously was only for PIF downloads).

Improved factory / image downloading with lower memory footprint.

Miscellaneous minor bug fixes and enhancements.
[Google Pixel 8] badabing2003:
Update Release:

Feb 17, 2024 v6.8.0.4 change log:

Use MacOS 13 to build with Github actions instead of MacOS 11, sorry to folks who use older MacOS, unless I get it to build it successfully on Github, MacOS 13 will have to do.

#158 Fix the App version.

Note: The following versions have identical code 6.8.0.0, 6.8.0.1, 6.8.0.2, 6.8.0.3, 6.8.0.4, the differences are in Github actions.
[Google Pixel 8] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version.

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

Misc. bug fixes and improvements.
[Google Pixel 8] badabing2003:
New Release:

Mar 03, 2024 v6.8.2.1 change log:

Bundle in the executable the missing files android_version.json and android_devices.json otherwise patching with KernelSU won't detect your Pixel as Pixel device.

Add back Magisk Alpha install option, thanks to pull request from @hldr4

Make Magisk install window resizable.

Add right click option on the selected Magisk to download in case you just want it downloaded and not installed.

Update all old forum.xda-developers.com links to xdaforums.com

Make Pif Manager work without a device being connected (obviously for props / pifs management and not for updating / testing pifs).

Typo fixes and other minor improvements.
[Google Pixel 8] m4j0r4:
Can anyone who's in the mood for some researching perhaps have a look at what I'm doing wrong? I flashed my pixel 8 through pixelflasher to the new android update. And now the device won't boot or get recognized even. It won't boot beyond the first bootscreen and I can't get it off or do anything with the hardware buttons. All ideas are welcome!
[Google Pixel 8] badabing2003:
I suspect it's not happy with one of the modules you kept enabled.

Flash stock init_boot and if it boots normally then it confirms that the problem is with modules.
[Google Pixel 8] m4j0r4:
Thanks Bada! the stock boot trick worked (via regular fastboot) Now, I remember having issues with updates earlier because of modules not working correctly. Is there any guide here or rule of thumb that I should be looking for when installing modules? Because I am trying to keep the modules to a minimum already but also fear that without Lposed. playcurl, integretifix and so on I'll won't be able to use wallet apps anymore. I always think that if it's from XDA acknowledged sources nothing could go wrong, am I the problem or is the internet just evil? :P
[Google Pixel 8] badabing2003:
If you cannot disable the bad modules because as soon as you root again, it bootloops, you can follow this

GitHub - badabing2005/Magisk at versionCode_27001

Special Magisk with modules loading disabled. Contribute to badabing2005/Magisk development by creating an account on GitHub.

github.com

But first check the FAQ, if you manage to boot to safe mode, it's easier.

As for bad modules, the ones you mentioned aren't the problem, one if these is

Pixel Xpert enabled canary-338
Pixelify enabled v3.0
Pixelify uninstaller services enabled 1
[Google Pixel 8] m4j0r4:
Pixel Xpert seemed to even block Lposed from functioning. I will do some homework to prevent this in the future, did you pull this out of the support file from pixelflasher or is there also a way I can see or check if modules are causing errors? I would love to be able to fix these sort of issues by myself in the future! I thank you again for being a GOAT as always, very much appreciated that you always guide a way home for lost phonepirates <3
[Google Pixel 8] badabing2003:
There is no direct way of telling (even from the logs) is a specific module is giving you issues.

Perhaps you get that from logcat, but not PF's logs.

What I see in PF's logs is everything PF checks and PF executes.

So I saw what modules you had installed, excluded the ones that I know don't cause any issues and gave you a list of the rest.

This is a common issue with modules, OS gets updated and some modules are compatible, that's way all the guides (including PF's) suggests disabling modules before update and then enabling them once you confirm that the system is operating correctly.

After enabling if it bootloops, you know it's the modules.