yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] speakeasy2:
what version would you suggest?
[Google Pixel 8 Pro] Lughnasadh:
33.0.3

EDIT: Unless you are on a Mac, as badabing just reminded me. Think you need to use 34.0.4 in that case to avoid the fastbootd problems Macs have with 33.0.3.
[Google Pixel 8 Pro] badabing2003:
Are you Mac by any chance?
[Google Pixel 8 Pro] A.Priori:
That's what she said! Going to try this out to unlock and root.
[Google Pixel 8 Pro] speakeasy2:
On windows. Thank you it worked.
[Google Pixel 8 Pro] gigaboss:
I somehow froze my phone. I unlocked the bootloader, restarted, configured everything, installed Magisk App, used the pixel flasher to patch boot.img and flashed, then the phone got stuck in fastboot, I restarted it and now it won't start. It won't do anything. Screen is black, I tried pressing power + volume up for over 30s and nothing happens...

I would love help to just get it to boot -_-
[Google Pixel 8 Pro] gigaboss:
I think I did not realize the phone was doing fine and I was supposed to wait (because on Mac pixelflasher freezes completely and it's hard to see if it's still working) and i stopped in the middle of the process, not sure what to do now :(
[Google Pixel 8 Pro] badabing2003:
Please generate support file in pf and I'll take a look
[Google Pixel 8 Pro] gigaboss:
Pf was frozen so I force quit it :/
[Google Pixel 8 Pro] badabing2003:
you can still generate a support file.

Just launch it and click on support button, no need to do anything else.
[Google Pixel 8 Pro] gigaboss:
That would be it!
[Google Pixel 8 Pro] badabing2003:
actually not,

the zip includes more troubleshooting information than just the logs, and all the sensitive data is redacted.

In any case I was able to see what went wrong.

unlocking bootloader - pass

installing Magisk - pass

creating a patch - pass

flashing - fail

Sending sparse 'product_a' 1/12 (262112 KB) ERROR: usb_write failed with status e00002ed
FAILED (Error reading sparse file)

The issue is a known issue on a MacOS

Android platform tools 33.0.3 runs into issues on MacOS, hence why it is recommended that on MacOS you use 34.0.4

Although 34.0.4 has its set of issues, and is only the recommended for MacOS

Now that we know what went wrong, how do we recover from it.

You need to be able to get into one of the two modes

bootloader

recovery

your phone should not be totally unresponsive, unless the inactive slot from factory is blank and the phone is not getting into bootloop.

Can you explain what you observe?

Have you tried key combinations to force the phone into different modes?

Keep it plugged to your Mac (if your Mac makes a noise when a USB is connected, like windows does, I don't know) that would be a cue that the phone got into some mode.

This is one of the reasons why I advocate for flashing OTA over factory, because with OTA, if anything goes wrong, your active slot remains intact and your'e able to boot back to it.

If you can get your phone into bootloader or recovery mode, this is easily recoverable.
[Google Pixel 8 Pro] gigaboss:
Sorry I was trying to limit the useless data!

So I ran home to use my desktop computer which uses windows.

When I plug it in it says Pixel ROM recovery device detected. The phone is completely unresponsive, I cannot get to bootloader or recovery :( I tried every combination of buttons (power, power + up volume, power + down volume, power + both) for 30s and it doesn't do anything. The windows does make a noise but nothing changes
[Google Pixel 8 Pro] badabing2003:
Recovery is good.

On Windows use 33.0.3, make sure you install the USB drivers.

Download the OTA image, you can download the latest, you don't need to stay on August.

Process

Patch

Select patch

Flash Pixel phone.

When the phone goes to system and finishes the Android setup.

For your measure, hit the Flash pixel phone button to flash the inactive slot too.

Good luck.
[Google Pixel 8 Pro] gigaboss:
The phone doesn't appear in adb devices! "Pixel ROM recovery" is just the name windows is giving it :(

I cannot use adb right now

View attachment 6020594
[Google Pixel 8 Pro] gigaboss:
I think I might have to try and return it...
[Google Pixel 8 Pro] badabing2003:
What happens when you scan in PF
[Google Pixel 8 Pro] gigaboss:
View attachment 6020595

No device found
[Google Pixel 8 Pro] Aphex13:
@badabing2003

Having just received my P8P, I'm using Pixel Flasher to update to the latest firmware, root, install Magisk, etc... This is the first time that I've used the software to wipe my phone. I just wanted to say thank you for the "Are you sure?" pop-ups. I'm sure that this will save some people some heartache in the future. Also, thank you for having the wipe selection reset to keep my data after you use it once. This is a really thoughtfully designed piece of software!
[Google Pixel 8 Pro] badabing2003:
Whether they are known to you or not is irrelevant, when your device is stuck, the key combinations are the only way to force (and hopefully succeed) in getting your phone into bootloader or recovery mode.
[Google Pixel 8 Pro] ko3st:
Yes I have installed the official latest Google USB drivers.

Picture now shows no trace of the Pixel Phone since it remains unresponsive.

However some USB device is detected. I think the PC can not figure out what device it is (since it is soft/hard bricked)...

I can make a or picture...
[Google Pixel 8 Pro] ko3st:
Not trying to be un-polite, because I am happy you are thinking with me, but...

What do you think I have been doing all night long ?

Not dancing that is for sure :)

I might have lost 1300 euro... :-(
[Google Pixel 8 Pro] ko3st:
Looking at the Windows 11 Device Manager:

- I also have a (still working) Google Pixel 5, which shows up in a normal fashion:

Portable Devices

Pixel 5

- When I plug in on the same USB cable the Pixel 8 Pro, then it shows up as

Ports (COM & LPT)

Serieel USB apparaat (COM6)
[Google Pixel 8 Pro] totonavarro12:
work for install custom rom on pixel 8 pro?
[Google Pixel 8 Pro] badabing2003:
It depends on the ROM, you'd have to check the instructions of the ROM.
[Google Pixel 8 Pro] ko3st:
I even tried to force Windows to "believe" the driver for the Serieel USB apparaat (COM6) is wrong by forcing the Google USB device driver to load in its place. See picture:

View attachment 6069775

Unfortunately, it did not work.

Windows still sees my bricked Pixel 8 Pro just as a COM Port, rather than a Pixel 8 Pro that it used to be.
[Google Pixel 8 Pro] ko3st:
I even tried to force Windows to "believe" it it is a Google USB device, but it did not work. Windows still sees my brick as a COM Port. See picture:

View attachment 6069776
[Google Pixel 8 Pro] badabing2003:
I feel for you, this is not looking good.n

Not very hopeful, but you could try draining the battery all the way down, the charging and powering up.

If it is under warranty, you might have an option to rma.

Good luck.
[Google Pixel 8 Pro] Pietro69:
Hi,

I have a problem flashing.

I have a new Pixel 8 Pro direct from Google, did the fist OTA update and then unlocked the bootloader. Back in it again, I did the first setup, reenabled the usb-debugging option, disabled auto-update and now I want to root. (I did the unlocking in Arch Linux but PixelFlasher didn't want load the Platform Tools so now I switched to Windows 11.)

Here I downloaded PixelFlasher.exe the Platform Tools 35 and the Google USB Driver. I also added the Platform Tools to the PATH.

The first quirk I found was that I can't install the usb-driver. Dev.manager already found a "Pixel 8 Pro" and in the manual driver update process, it said that the newest driver is already installed. Additionaly I choose the "ADB-Device" driver from the "available driver" list (instead of the WinUsb-Device). The outcome in the console was the same, but I made an additional Support File (so the fist File was with the standard settings, and the latter with the ADB-Device driver, if that has made a difference). I don't know if all this is a problem or if Win.11 really has the right driver OotB (even the Google download page only have sections till Win.10)!?

At this point I'm going throgh your tutorial on how to flash.

- Load Platform Tools

- Scan Dev. and choose the one I connected

- Load the OTA 14.0.0 Image I downloaded and Process it

- Patch the init_boot with Magisk and let it install Magisk to the phone (yes, first time, no Magisk before)

- choose the patched file and Full OTA

- Hit Flash Pixel Phone and I get the following Error:

ERROR: Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 4022, in _on_flash

File "modules.py", line 3070, in flash_phone

TypeError: argument of type 'NoneType' is not iterable

Did you know what went wrong?
[Google Pixel 8 Pro] badabing2003:
What is this?

Pixel8Pro OTA 14.0.0 Image (UQ1A.240205.004, Feb.2024).zip

Please do not rename the file, PixelFlasher does validation and you renaming it messes that up.

View attachment 6071027
[Google Pixel 8 Pro] Pietro69:
THX for the info :)!

I had it downloaded manally and I normaly rename all files so that I can understand what it was ;).

I try it with the original name again!
[Google Pixel 8 Pro] Pietro69:
Thanks again! Yes, now it works!

Maybe you could catch the python error and write out a message, that the app can't recognice the image file name? Then I had get my error by my self :).
[Google Pixel 8 Pro] Pietro69:
Hi again,

It don't worked fully. This time the flashing runs and in the reboot phase it get's a timeout and said it didn't finished the job. At this time the Phone sits in a bootloader screen with "start"-sign at the powerbutton with i have to press to restart. It restarts in the flashed Slot A (it was in B at the beginning), no problem or bootloop, but it's not rooted. I tried it a 2nd time, this time Slot B get's flashed, but with the same result.

Did i do another thing wrong?
[Google Pixel 8 Pro] badabing2003:
Not recognizing image file name is a valid scenario, and PF actually reports it.

PF can process other image file for other device.

The issue is that the way you renamed caused an exception, and although I can catch exceptions and provide a generic message, there is no certaintly that the message would be relevant, specially if it's dealing with a firmware for another device.

Leaving it as such allowed me to quickly get back to you with the specifics of the issue.

You have the same issue as this one.

Install USB drivers for fastboot.
[Google Pixel 8 Pro] Pietro69:
You are quick :)!

Thank you, that worked!

Just one last question please:

We shouldn't install Magisk 2 times, I know that, but when I open Magisk, which was installed by PF, in the Tiles "Magisk" and "App" there are Install buttons, but besides Installed it is written 27.0, so shouldn the be eg. "installed"-fields or someting? Should I hit install from there, and what is the difference between Magisk and App?

Sorry if it should be obvious. I rooted all my phones since it was a thing, but not the last one with I had the last 4 years (O+7Pro), so I'm rusty ;).
[Google Pixel 8 Pro] badabing2003:
Even if you flash two slots, there is a single data slot,

So for the Magisk App, you only need to install it once, as that gets installed in the data partition.

There are two parts to Magisk,

The app, which is what you use to manage the permissions / modules / denylist ...

The root component, which is what grants root, the root component is the one that gets flashed to either boot partition or the init_boot partition depending on the phone model.

This is how Magisk is displayed when it is properly installed.

The top part is the root component, the bottom one as the name suggests is the app.

View attachment 6071067
[Google Pixel 8 Pro] 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 Pro] 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 Pro] Morgrain:
March update is out, someone tried flashing with PixelFlasher yet?
[Google Pixel 8 Pro] badabing2003:
works for me :giggle:
[Google Pixel 8 Pro] viper8u2:
*Edit* Disregard, I was downloading with Chrome but missed that it had flagged it and I had to tell it to download anyways.

I just downloaded the latest which I thought was Release v6.8.2.1, Is it still pointing to an old link? It says it is version 6.7.1.0 when I launch it

Thank you
[Google Pixel 8 Pro] mko000:
I just did the same and everything is correct on GitHub. You probably started the old executable.
[Google Pixel 8 Pro] dDoctar:
Mac version is missing on this build
[Google Pixel 8 Pro] badabing2003:
Yeah I know, Apple is always special, the build breaks again.

It's a recurring song, no other build ever breaks, except MacOS, almost every time I need to build :(
[Google Pixel 8 Pro] HipKat:
Edge does the same thing. In Arch Linux and Windows so it's not Defender
[Google Pixel 8 Pro] HipKat:
Success, as usual, although it took a bunch of times to find a working FP - I had to go back to Xiaomi instead of Freeman, but all good now!
[Google Pixel 8 Pro] banshee28:
Flashed March OTA, rooted, latest PF, no issues! :cowboy:
[Google Pixel 8 Pro] nikola1970:
Everything worked great with latest update, rooted, but now my magisk app saying zigisk iz not enabled, but its enabled in setting, i tried turning it on and off in app, and rebooting but its same...
[Google Pixel 8 Pro] badabing2003:
You probably have multiple Magisk apps, hidden and none.

This is a known issue with Magisk, use TB checker from play store, it finds Magisk, even hidden ones and identifies the package name,

Uninstall all that it finds, reboot, and then install Magisk.

You won't lose root, this is just the Magisk App.
[Google Pixel 8 Pro] nikola1970:
I have magisk alpha, installed TB checker but I cant find option to find Magisk apps.

It just says Magisk specific checks: Fail

edit:

i reinstalled it, and now everything is ok
[Google Pixel 8 Pro] JazonX:
Hey @badabing2003

Just a suggestion; Remind disable-verity option before flashing a rooted Phone?

I forgot to enable expert mode, and totally forgot to tick disable-verity.

Flashed March firmware as is, and while flashing the kernel (and failing) - realized that enabled verity again.

Entirely my mistake for not paying attention, But A reminder would be a nice touch somewhere.
[Google Pixel 8 Pro] badabing2003:
Just above the fail, it tells you the package name (I'm assuming that you ran the tests, specially the xposed one)

Please provide support file, there is a built in check already.
[Google Pixel 8 Pro] kscjx:
Same here, could someone please provide a guide? Should I uninstall and reinstall TB checker?
[Google Pixel 8 Pro] kscjx:
In TB checker, what does it mean when it says pass or fail, does the fail mean the file is not installed?
[Google Pixel 8 Pro] fma388:
Always with platform-tools 33.0.3 or updated platform-tools 35 ?

I tested with 35 as mentioned in another topic, but now Play Store and other Google apps stuck at startup.

I tried to used the "switch slot" button in PF to restart my phone on other slot but it's won't work.. On restart, the phone indicate "You're device is corrupt" :cry:

I can restart my phone, but only on the slot of the last OTA.
[Google Pixel 8 Pro] badabing2003:
support file please, sorry, to many posts / messages / threads, hard to keep up.

Best is provide fresh support file so that I can troubleshoot.
[Google Pixel 8 Pro] fma388:
Thanks !

Here's the support file you want.

I did the March update today.
[Google Pixel 8 Pro] fma388:
Thank you very much for all the explanations !!

I thought it was possible to use the 2nd slot as a backup, I didn't know it had to be on the same OTA.

I'll check it out tomorrow !

PS : I haven't updated Shamiko otherwise it no longer works correctly for my banking application. For PIF I don't test latest update
[Google Pixel 8 Pro] badabing2003:
See this

Latest GitHub release missing macOS build · Issue #171 · badabing2005/PixelFlasher

Title ^

github.com
[Google Pixel 8 Pro] knopie:
I compiled 6.8.2.1 on my own MacBook with osx 14.4, first impression of a dry run is ok.
[Google Pixel 8 Pro] Galaxea:
I just flashed the latest factory image with disable-verity and verification, and flash-to-both-slots enabled, and I am now in Android recovery mode. Says I need to Factory Data Reset.

Do I have any other options before I go that route please?

EDIT: I have attached the log in case you can advise what went wrong so that I can avoid it next time. Thanks.
[Google Pixel 8 Pro] badabing2003:
Why did you disable verity / verification?

Did you need it for a custom rom / kernel? or you just thought it was a good idea to disable?

If you need them disabled, you have to wipe data, there is no other way around.

Each time you transition verification state from enabled to disabled, you have to manually wipe data.

If you didn't need to disable them, then you can re-enable them and have your system boot properly.

The way to do it is:

Put your device into bootloader mode

Select boot image in PixelFlasher

Select Custom Flash

Select vbmeta from the dropdown

Click on Paste (it should fill the textbox next to it, with the proper path to vbmeta.img

Click on Flash Pixel Phone.

View attachment 6078489
[Google Pixel 8 Pro] Galaxea:
From reading previous posts I thought is was dangerous to flash WITHOUT doing this, but I had no reason to do it, so it was my mistake.

Appreciate your suggestion - I will try it soon.
[Google Pixel 8 Pro] Galaxea:
@badabing2003 : Worked perfectly - thank you. How do I buy you a coffee?
[Google Pixel 8 Pro] badabing2003:
:) https://xdaforums.com/t/pixelflashe...dating-rooting-managing-pixel-phones.4415453/
[Google Pixel 8 Pro] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel 8 Pro] vegetaleb:
I am seriously thinking to go back to stock unroot, I tried both Evox and Sigma but they don't have all the customisation I want, and the integrity thingy to use secured apps could be killed by Google anytime soon.

@badabing2003 So what are the proper steps to go back to unroot stock using Pixel Flasher and relock the bootloader?

Would it wipe also the esim partition ?
[Google Pixel 8 Pro] badabing2003:
Load the latest factory (not OTA) firmware.

Process

Select the stock boot from the list (don't select a patched boot)

Select the below options

And Flash Pixel Phone

When all is done and working fine, lock the bootloader.

View attachment 6079320
[Google Pixel 8 Pro] HipKat:
Why would you want to relock the bootloader??

Granted, this is referring to beta versions, but to quote @roirraW "edor" ehT
[Google Pixel 8 Pro] roirraW "edor" ehT:
If you merely unroot and don't re-lock the bootloader, I believe you won't pass the integrity checks (without the benefit of the root-based workarounds). Anyone correct me if I'm mistaken, though.
[Google Pixel 8 Pro] HipKat:
I'm sure you're right about that. I was following the Chiteroman thread recently and saw that
[Google Pixel 8 Pro] badabing2003:
That's correct
[Google Pixel 8 Pro] 22Ti:
Tried to flash the March update, with platform tools r35 on Windows. It gave me a message saying something like " Phone is now corrupt, may not work as expected". Phone is now unresponsive black screen, I hear the windows usb sounds tho.

Tried to get into recovery but screen remains black so I'm not sure if i'm doing it right.
[Google Pixel 8 Pro] vegetaleb:
So I simply install latest official full build with Pixel Flasher then relock the bootloader from developer menu or from adb or fastboot?

The custom rom I am using now is pretty battery hungry
[Google Pixel 8 Pro] vegetaleb:
T=

Thanks mate
[Google Pixel 8 Pro] A.Priori:
Got magisk errors after using the latest stuff. "module suspended because zygisk is not enabled" any ideas?
[Google Pixel 8 Pro] badabing2003:
I don't have a crystall ball ;)

Without support file, I have not idea what errors you got and why.
[Google Pixel 8 Pro] A.Priori:
I am trying to fix errors myself but which log would be helpful? I got the error using platform tools 33.0.3 because of a popup when starting PF. Then I updated magisk and repatched OTA and flashed again. Then updated modules. Now I am going to try redoing everything with latest platform tools. I am getting slow phone and apps not repsonding.
[Google Pixel 8 Pro] badabing2003:
Click on Support button (lower right) or toolbar rightmost, or from help menu in PF
[Google Pixel 8 Pro] A.Priori:
Yep I wanted to try a few things. Not sure what's going on maybe conflicts with modules. Here is the zip if you have a chance to peek
[Google Pixel 8 Pro] A.Priori:
Seems mostly to be system apps not responding (i.e. play store, camera, messages etc.)
[Google Pixel 8 Pro] badabing2003:
That could be due to PIF, if you played with it.
[Google Pixel 8 Pro] A.Priori:
Thanks for looking! Yes sorry I was playing with it so logs are jungle-like. It looks like the problem module is LSPosed; there hasn't been an update and disabling it fixes some things.
[Google Pixel 8 Pro] badabing2003:
check this fork

GitHub - pumPCin/LSPosed: LSPosed Framework

LSPosed Framework. Contribute to pumPCin/LSPosed development by creating an account on GitHub.

github.com