yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] 22Ti:
I really appreciate your time and effort that you put into this reply. For some reason I decided to jump into updating without fully understanding the whole picture of how rooting works, I'm new to this scene. I have backups so it's not the end of the world.

I followed this guide: https://www.xda-developers.com/how-...-root-google-pixel-phone/#optional-gui-method

They say to use the factory image. Maybe I'm interrupting it incorrectly? I also incorrectly assumed that using the factory image allows you to have the option to keep your data. The guide further pushed that assumption since it's about updating but uses factory image.

It's beyond me why you would try to flash patched init_boot (only) from March release over your January firmware.

What is init_boot (only)?, Is the standard way of updating to increment? So I should've updated from January to February and then March?

How can you recover from this?
If you manage to put your device into bootloader or recovery mode, then you can recover, if your device can't be detected, I'm afraid you're looking at an expensive door stopper.
Try the key combinations for various mode to manage to put your device into recovery or bootloader mode.
If your manage to get into bootloader mode, you would flash factory image.
If you manage to get into recovery, you would flash OTA

Yeah looks like there's no recovery for me, the phone is unresponsive, no vibrations, sounds, images. As I understand, I had only been using one slot, slot A. I broke it and since I don't have anything in slot B, I have no hope for recovery, is that right?

Make sure you address the communication issue, install the latest Google USB drivers, use a good cable, and often USB 2 ports are more reliable, never use USB hub.

Not sure why there was a communication issue, I'm using a "known" good setup. My cable works and I do have the drivers, not using a USB hub. Is there a way to further investigate or did I just get unlucky and it just failed.

One other thing, you kept suspect modules active before flashing, they can get you into bootloop even if youd flashing was successfull.
I would never keep these enabled when flashing patched.

So is the procedure to disable all modules and patch bare Magisk? Is there a reason why people leave modules enabled if it's so risky (As I learnt now).

Overall, thank you for your help, it's a great learning experience. I hope I can contribute to idiot proofing the steps to rooting 😅. I hope others can learn from my mistakes here.
[Google Pixel 8 Pro] badabing2003:
Never a good idea, specially when you're new to this.

There are some excellent guides linked in the help menu, as well as in OP

Factory method is outdated, it still works, but it's riskier than OTA method, hence why all the good guides have been updated to suggest OTA sideloading.

And with OTA, you have no other choice, it always keeps data, it doesn't wipe, and as a bonus it flashes to the alternate slot, just like Google's OTA updates work, hence to risk of hosing your current slot.

Follow the OP guide, or better yet, read and follow those linked guides, init_boot is the extracted part from the firmware / OTA, which gets patched to give you root access.

you can't mix and match.

I'm really sorry to hear that, if you can't get the device into recovery or bootloader, I'm afraid there's not much you can do.

It could happen, it could be driver issue, USB port, cable, or even PC,

You can check this: https://developer.android.com/studio/run/device

Not all, but all would be safest, and then you enable them one by one, or in groups to make sure they don't cause conflict, the ones I highlighted are known to break and require an update with almost each OS release.

You're welcome, and sorry for the expensive learning experience.

Hope you take you time and grasp the concepts and the manual steps to get a good understand of the process, that's invaluble to get you out of troubles.
[Google Pixel 8 Pro] sic0048:
If the computer responds by playing the "USB device attached" sounds when you plug the phone in, it probably isn't as dead as you think. The fact that the computer recognizes the phone is a great sign. Try booting the phone into bootloader mode and or recovery mode. It may be a little harder without the screen, but it should still work.
[Google Pixel 8 Pro] badabing2003:
Not necessarily,

If it is detected as serial device, you're toast with Pixels.

You should see any of the following detections in the device manager

View attachment 6080153

View attachment 6080155
[Google Pixel 8 Pro] slimshadyy97:
How do I check if I have it installed already?

How do I remove it if I want ?
[Google Pixel 8 Pro] badabing2003:
Can you be more cryptic?

Installed already what? remove what?
[Google Pixel 8 Pro] slimshadyy97:
Sorry I should've been more specific. Someone had access to my phone and stock os has been overwritten with some mod/mirror versions. I've tried to flash the ROM couple of times. There are lots of shady apps with permission to , idk lot of things. Even my google account was signed in with a different device.

Thanks anyway

View attachment 6080224
[Google Pixel 8 Pro] badabing2003:
The first thing I would do is restore stock on both slots and wipe.

See details here.

📳🔥PixelFlasher for Google Pixel 8 Pro Support Thread.

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...

xdaforums.com

Locking the bootloader is optional, but if you will, first make sure it works properly before locking.
[Google Pixel 8 Pro] slimshadyy97:
Thanks for the help. I'll try it and update you.
[Google Pixel 8 Pro] vegetaleb:
Thank you

Yes I will boot up the rom and check if all went OK then I will relock the bootloader .

Too bad Sigmadroid is hungry in battery, I liked the customisations, though it's also to avoid any risk during my upcoming travel of April, I don't want to face unusable money apps because google decided to up their games again against root.

So in case flashing back stock rom went alright with your instructions but bootloader is still unlocked , I have to:

“fastboot flashing lock” in fastboot mode?

It shouldn't wipe my esim right? Just like when I unlocked bootloader and rooted
[Google Pixel 8 Pro] badabing2003:
I don't know what will happen to your esim when you choose to do the steps I outlined, so please proceed with caution, the steps I outlined is not a soft reset, so the chances are that esim might get wiped.

I honestly don't know the outcome, if anyone here knows, please let @vegetaleb know.
[Google Pixel 8 Pro] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel 8 Pro] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel 8 Pro] wolfsister:
@badabing2003

I was updating from Jan to the March update using full OTA on my rooted with Magisk P8P when my laptop died.

After that PF is unable to recognise the device as husky and shows a random numerical name. When trying to reflash the patch boot it gives the error that the software is only for pixel devices and the disclaimer that I should flash only if I'm sure .

However when trying to flash I get errors after step 1/2

I couldn't take a picture of the error but it happened after verifying update, step 1/2 and then this:

error applying update 7 errorcode kinstall deviceopenerror recovery error failed to sideload....

(Roughly what it said from what I can remember)

My device still boots up and I am able to use my rooted mods.

What can I do to flash the OTA somehow?

Sidenote: after deleting storage of Google play my gps stopped working so I was trying to update as I couldn't figure out the issue after 3 days and hoped this would fix it. Gps works slowly when I'm outside in clear view of satellites but not indoors (like. At all) If you know the cause or solution of this error (or if you know that an OTA update will fix it), please do let me know

Hoping badly that you can help. Cheers.

Edit: the sidenote is an unrelated issue. It was the reason I decided to use PF to update. PF DID NOT cause the issue
[Google Pixel 8 Pro] badabing2003:
Support file please
[Google Pixel 8 Pro] wolfsister:
PMing you the file
[Google Pixel 8 Pro] badabing2003:
Log files are sanitized (sensitive data redacted), you don't need to PM

The good thing about OTA flashing is if something goes wrong mid flashing, your active slot is still good, because OTA is flashed to inactive slot and is only switched if everything is ok.

This is why you are still able to use your phone.

But becuase something messed up your inactive slot, you're not able to sideload OTA to it,.

I suggest you first try to Cancel OTA update from the Device menu

View attachment 6087262

Then flash again the OTA

If that works, you're good

If it is messed up badly, then what you could do is flash factory image instead of OTA.

However flash it to inactive slot, or both slot,

View attachment 6087263

Don't worry you don't have to wipe, choose Keep Data.

Good luck, and if you run into any issues, I'd need a new support file.
[Google Pixel 8 Pro] wolfsister:
This will work even thought I disconnected the device and will be reconnecting it when I'm back to my laptop?

Also are there any things I need to be mindful of when flashing factory image in case the OTA route doesn't work?
[Google Pixel 8 Pro] vlubosh:
Trojan inside Pixel Flasher.exe?

View attachment 6087286
[Google Pixel 8 Pro] HipKat:
No, that's false flagging the file.
[Google Pixel 8 Pro] Pfeffernuss:
After trying to flash the April OTA I receive the error noted in the attached zip. What can be done about this?

Spoiler content hidden.
[Google Pixel 8 Pro] badabing2003:
yes

Just make sure to choose the options I suggested.

1- Please do not rename downloaded OTA / Firmware files nor try to extract them, PF expects intact images and it will take care of things.

2- Your issue sounds like a communication issue / driver / port / cable, start with driver.

See this post.

Note to self: I really really really need to have a FAQ, as I'm fedup answering the same questions.
[Google Pixel 8 Pro] wolfsister:
Thanks, it worked! I cancelled the OTA update and then installed the April OTA. I patched the OTA with Magisk but PF says patch method is app. The zip isn't flashed on my device. I tried the install Magisk from PF option but it didn't do anything. What should I be doing? You're a lifesaver btw
[Google Pixel 8 Pro] badabing2003:
Happy to hear that Canceling OTA fixed the issue.

> What should I be doing

Provide a support file.
[Google Pixel 8 Pro] wolfsister:
www.transfernow.net/dl/20240403Xdj5zUoI

Apologies for not attaching it earlier

My order of steps:

Cancel ota

Flash March OTA which had the patch method as Magisk

Reboot phone to see that it is booting

Flash April OTA which had the patch method as app

Reboot phone

Try to flash patched Magisk img file in Magisk app

Get errors

Flash April OTA in the other slot and reboot

This is my Magisk manager right now
[Google Pixel 8 Pro] badabing2003:
See my answer to Pfeffernuss few posts above.
[Google Pixel 8 Pro] Pfeffernuss:
1. Did not know, have always done it like this.

2. That would be strange because I've flashed numerous times already, same pc, same (original) cable, same everything.

Wouldn't have asked it otherwise. Will rename file to it's original name and try again, thx :)
[Google Pixel 8 Pro] badabing2003:
no you need to install the Google's USB drivers while in bootloader mode as well as adb mode
[Google Pixel 8 Pro] wolfsister:
Got it working, thank you.

What fixed it: Put my phone in bootloader mode by flashing the patched magisk boot image file.

Once in bootloader I updated google USB drivers https://developer.android.com/studio/run/win-usb by going to device manager>portable devices>Pixel 8 pro and rightclicking on update drivers. Then I browsed to the extracted driver folder

After that I rebooted my phone

Used PF to flash patched boot image

Voila

Thanks for being so patient and helping out!

EDIT:

Welp. New issue with Magisk. Like I said, I flashed patch and was trying Magisk mods (with anti bootloader module active). My device automatically changed slots on boot when I flashed lsposed-zygisk (which was my last mod to flash smh).

Now the device cannot seem to get Magisk root no matter what. I even flashed the OTA with patched boot twice. Both slots cannot seem to get rooted.

Support file: https://www.transfernow.net/en/bld?utm_source=20240403f82t0Ual
[Google Pixel 8 Pro] wolfsister:
Fixed and everything working as normal.

The issue was a hidden Magisk and a visible one like you said. Thanks again
[Google Pixel 8 Pro] HipKat:
Never have a problem unhiding Magisk before using PF to update, then rehiding it and if you're flashing the OTA, flash both slots.
[Google Pixel 8 Pro] badabing2003:
Just to be clear for everyone in case it is not (I know it is not obvious)

The default settings of PF is to keep it simple and hide unnecessary dialogs from the user, however you can enable advanced features in the settings which will give you higher control.

One of those is this setting.

View attachment 6087924

When enabled, and you choose to patch with Magisk, you get an additional dialog as the following View attachment 6087926

When it comes to Magisk, PF can automatically (without user intervention) patch using one of two methods.

Method 1 and Method 2 (see screenshot)

It also checks the versions of each and accordingly recommends the best method.

If this option is hidden, it automatically selects the recommended method.

If method 1 is chosen, ie using the rooted Magisk (in /data/adb/magisk), you don't need to unhide, patch / rehide

It doesn't care if your Magisk is hidden or not, it uses the necessary bits from /data/adb/magisk

On the other hand for method 2, needless to say, the app needs to be unhidden, otherwise it doesn't contain the necessary bits to create a patch (it's just a stub), but method 2 never gets chosen if Magisk app version is not read.

The only time one would choose method 2 would be the following scenario.

Let's say you patch with Magisk 27001 and are using it, and then Magisk releases 27002, however you only update the app but not update the installed patch (ie through direct install).

When you try to create a patch with PF, it detects this scenario and it recommends and chooses (if the option is hidden) method 2, on the likely assumption that you probably want to use the latest that you have installed to create a patch, and not the older rooted Magisk, becuase if it uses the older rooted Magisk, it will create a patch with 27001 instead of 27002 (in the above example).

Obviously for PF to detect this scenario, it needs

1- Either an unhidden Magisk app

2- Or the hidden Magisk's package name specified in the settings. (of course if it is hidden you should set the value to the hidden package)

View attachment 6087937
[Google Pixel 8 Pro] Pfeffernuss:
Other cable, latest drivers, original OTA filename, but same issue.

First time this is happening, on all previous OTA's all was fine. Probably a minor thing, but what :)
[Google Pixel 8 Pro] badabing2003:
It's a different problem now.

adb server version (40) doesn't match this client (41); killing...
* daemon started successfully
adb: sideload connection failed: protocol fault (couldn't read status): connection reset
Error: The sideload command encountered an error, aborting ...

You probably have multiple ADB versions running and also possibly in your system path that is being picked up.

Double clicking on this part in PF, will shutdown the adb started by PF

View attachment 6088028

However you should kill all other instances of adb / fastboot and remove them from your system path.

Then scan for devices in PF and try.
[Google Pixel 8 Pro] Pfeffernuss:
Incredible, recently installed an app called Superdisplay. This apparently also installed an adb instance (and path). Checked the Windows paths prior but didn't expect a random app to contain an adb version as well.

Needless to say, removed it, and now PF is flashing the April OTA. Thanks for your patience and help! :)
[Google Pixel 8 Pro] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel 8 Pro] BABYFACE10:
This is the best tool I have found to facilitate the really easy job. Thank you, fully rooted after 4 hours out of the box
[Google Pixel 8 Pro] 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 Pro] 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 Pro] Galaxea:
My Magisk is a bit broken so I am trying to reflash the latest factory image, but I keep getting this error:

2024-04-15 10:52:53 ERROR: Encountered an error while running flash script.

theCmd: "C:\Users\abc\AppData\Roaming\PixelFlasher\factory_images\husky_beta-ap21.240305.005\flash-pf.bat"

Return Code: None.

Stdout: <_io.TextIOWrapper name=5 encoding='ISO-8859-1'>.

Stderr: None.

Aborting ...

Please check log and advise. Thanks.
[Google Pixel 8 Pro] Galaxea:
Edit: The previous version of PF doesn't give the same error.

I was hoping to test the Beta to Stable without wipe feature, but I can't get to that point with the latest version.
[Google Pixel 8 Pro] RYZONN:
I flashed the new update, and I do it as I always did, and this time there was an error, I lost root, can I flash it again or will I have to confirm something to avoid crashing the phone or doing a wipe?
[Google Pixel 8 Pro] badabing2003:
I should be fixed now with v6.9.2.1

I must bring up few points about this.

First an foremost, this is untested, (ie switching from beta to stable without wipe) and assumed that it might do the trick, however be aware that there is an inherent risk that you might require a wipe, or get wiped. If you're not willing to take the chance please do not proceed.

On the other hand if you decide to proceed, please report back as your results will be very valuble.

The way you need to do it, is different than teh default.

- First enable Advanced options (this will enable the menu Dev Tools | Prepare AVB Downgrade Patch

- Select the firmware you want to switch to, process it and select the stock boot file from the list.

- Issue the command Dev Tools | Prepare AVB Downgrade Patch

- Make sure to select the option to patch fingerprint

View attachment 6092188

- Select the option 1 or 2 as it applies to your device

- Once the patch is created, you need to flash that as boot.img first before you try to switch the firmware (or downgrade)

View attachment 6092189

- You might need to select Flash to both slots (am not sure) when flashing the downgrade patch.

Sorry can't guess what error you ran into to provide any valuable feedback.

No support file -> no guessing.
[Google Pixel 8 Pro] RYZONN:
I already have several problems in the last 2 updates, the first time I lost verity in one of the slots, and now I lost root, I wanted to do everything from 0, give wipes, have both slots unlocked root etc.. is there a step by step guide to do this smoothly here using pixelflasher? I can't find it, here on the forum there is a rooting guide etc... but it doesn't mention Pixelflasher
[Google Pixel 8 Pro] badabing2003:
Have you check the OP of the main thread or Github?

By the way both are linked in my signature.
[Google Pixel 8 Pro] RYZONN:
im already seeing, if i use Custom flash, select disable verity and verification,do I solve the problem? Wipe the cell phone and I'll have everything, ok? Do I only need to flash it twice to also have the verity/verification disable in both slots?
[Google Pixel 8 Pro] badabing2003:
View attachment 6092231

Select the correct firmware, hit the paste button, it should select the proper vbmeta.img
[Google Pixel 8 Pro] RYZONN:
Using like this, i will get, root, disable verity and verification in the 2 slots? I dont have yet
[Google Pixel 8 Pro] badabing2003:
You never provided support file, so I have no idea what you have, what you have done and what you're doing.

You asked how you get verity verification disabled on both slots, I have you that.

Don't tell me what you have, provide support file, that tells me alot, and then if I have questions, I'll ask.
[Google Pixel 8 Pro] RYZONN:
I'm going to start from scratch, flash everything from scratch, I'm going to do what you said and I'll give you feedback

EDIT: trying flash again, but the app freezes, why? already download another time, AV off

View attachment 6092442
[Google Pixel 8 Pro] HipKat:
Try a different USB Cable, make sure it's in a USB 2.0 slot and run PixellFlasher as Administrator
[Google Pixel 8 Pro] RYZONN:
I switched to version 6.9.1.3 and I got it, it's no longer crashing,

Well, now I'm going to do a clean install to take advantage of having root, and having verity and verification disable in both slots, these are the commands in the advanced options that I need to activate, right? What does verbose do?

View attachment 6092523
[Google Pixel 8 Pro] HipKat:
I wouldn't ever toggle flash to both slots but I'm sure this is way after the fact
[Google Pixel 8 Pro] badabing2003:
It seems that not only you're not interested in helping yourself, by not providing a support file, you are also doing a disservice to the program and others, if there is any corner case issue with the latest version, I wouldn't know without a support file.

As of this moment, don't expect assistance from me, and I urge others to do the same.
[Google Pixel 8 Pro] 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 Pro] RYZONN:
I'm really sorry but I can't agree, I would provide the file without any problem but the problem is that with the most recent version until yesterday the application crashes, I can't use it after it crashes, only closing it, I can't remove the file, I would be happy and interested in this, to be able to solve it and help everyone, but when the app crashes and becomes "unresponsive" there is no way to change it other than closing