yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
I wish I had known what to suggest, but I honestly didn't. I know that manually flashing a Full OTA ZIp automatically flashes it to your (currently) inactive slot, and makes that slot active, but I haven't kept straight whether taking normal OTA updates does the same thing. I'm very sure that @Lughnasadh and @badabing2003 have been able to keep that straight, so I hope they have time to chime in here.

So, I can't say for certain if you didn't have anything in the other slot or not. There was also one user's experience that both slots contained a bootloader on their brand new, never updated P8P, but there might have been a detail revealed later that I just don't remember for sure - it's all running together.

Apologies that I'm not giving much helpful information, but I'm glad that you got your phone replaced fine. That's good!

I followed my own directions to root all my recent Pixels (6P, 7P, 8P), including my P8P. I don't recall if I had an OTA update available immediately, or if so, if I actually took it. Probably not, though, because it's a duplicate effort since you're flashing the firmware.

The only difference is for the last six months, I've been using the Full OTA Zip method (the next section below the Factory Image method), and that's how I flashed both my slots and rooted my P8P. I know of no reason at all that the Factory Image instructions would specifically fail to work, however. I used the Factory Image instructions every single month for the first ~20 months out of the last 25-26 (until I changed to the Full OTA Zip method).

Edit: It's possible that you got unlucky (before being able to replace the phone), as, although it is frustrating to not know why these things happen, there are definitely things that are out of our control and sometimes don't behave as expected.

PixelXpert doesn't contain all the modification abilities for QS Tiles as Iconify / Themer do, and PixelXpert removed all the theming modifications, probably since QPR1 Beta was showing them that trying to keep them compatible with QPR1 was going to be an uphill battle.
[Google Pixel 8 Pro] Ghisy:
I work in cyber security now and I was wondering about this a few days ago. QR codes have almost become universal but it doesn't seem like people are worried about scanning something malicious?

It would be nice if Google implemented some kind of scan of the URL before opening it.
[Google Pixel 8 Pro] Lughnasadh:
Since when you first got your phone you let it update via OTA, and since the OTA installs the firmware on the inactive slot, neither of your slots were "empty", so I don't think that was the problem.

When you get your new phone it's probably best if you sideload the latest Full OTA firmware twice so the latest firmware is on both slots. Then you can root by patching the init_boot image and flashing that patched image via fastboot as directed in the OP.
[Google Pixel 8 Pro] fil3s:
Since the bootloader's unlocked you can use flashtool

Android Flash Tool

flash.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
December Verizon-specific firmware (if you use your phone on Verizon or a Verizon MVNO, not if you have a Verizon variant of the phone, unless you're actually using it on Verizon, too):

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
As has been pointed out to me by @Homeboy76 (thank you!), the new Verizon images are missing now. Here is the proof they were there:

Here's the link, which still works:

14.0.0 (UQ1A.231205.015.A1, Dec 2023, Verizon)	Flash	Link	4f2b101993eaf5169a3a85f683bc82b7a0108b8697fcdcc8518caf6b05af50c7
[Google Pixel 8 Pro] roirraW "edor" ehT:
Off-topic, but I'm having a heck of a time spending my Google Opinion Rewards before they expire. I have over $50, and some portion of it expires in three days. They don't tell you how much - they used to, but they stopped. It's probably only less than a dollar, however, the next day or the day after that, some more will likely expire, as all the points expire a year after you gained them.

I had accumulated a little over $250 in the last eight years I've been using it (there's a history section), and I always spend it on Play Store apps that I used - it's very, very rare for me to spend my own money on apps, but I'm running out of things to pay for that I actually use. I've already donated to the Developer of X-Plore FIle Manager four times through the app's About menu, and I'll donate again if I have to - at least they have different levels of donation depending on how much I want to give.

I'm looking for suggestions for high-quality useful apps that have a paid version either in the Play Store, or can be bought/donated through the Play Store from the app itself, as those are the only way you can use these Rewards.

If I can't find something I'd actually use to donate for, I'd consider just suggestions for high-quality developers who make Play Store apps and take Play Store payments, whether I use the apps or not.

I'm not looking for any apps that require subscriptions (monthly or yearly), although I'd consider them as a last resort if there's nothing else worth buying.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Verizon images are back with the same hash as before.

@Homeboy76
[Google Pixel 8 Pro] Morgrain:
Google seems to have released the December Update for the Pixel Watch 2, I was able to manually force it (click on the text/icon repeatedly on the Watch System Update screen).
[Google Pixel 8 Pro] Morgrain:
Some suggestions to take a look at

Swift Backup

Shortcutter

Button Mapper
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! I'll take a look. Swift Backup, I already own, but I'll look to see if there's a "donate additional" through the Play Store option. Shortcutter, I'm sure I've had it installed sometimes over the years, but I can't recall if I've bought it yet. I'll take a look at that and Button Mapper.

Cheers!
[Google Pixel 8 Pro] fil3s:
If you have cloud storage, or an openssh server i would definitely recommend this app. Makes file syncing a breeze. There's in app payments. Check it out

Autosync - File Sync & Backup - Apps on Google Play

Universal file sync and backup tool for cloud storages and NAS devices

play.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you very much! Noted.
[Google Pixel 8 Pro] Normandroid:
Hello everybody. I hope someone can give me a little help/guidance. I got my P8P today, an upgrade from my P6P. Well, I didn't see this thread until I realized that I might have made a mistake while trying to root. I unlocked my bootloader, and flashed the December Verizon factory image. Here's where I went wrong. I patched and flashed the boot.img NOT the init_boot.img. I'm not rooted, and the phone is operational, but I know I screwed up. Can anyone offer me some advice on fixing this so I don't brick my phone? Thank you.
[Google Pixel 8 Pro] simplepinoi177:
I imagine if you're able to load up the OS, you're rather safe from bricking (either soft or hard) your phone -- or it would've happened already.

Be that as it may, if you really want to make sure things are settled properly, then flash the Full Factory image flash-all.bat and that should do it. Be sure to edit out the "-w" in the bat file or your device will be wiped.

Also, on Pixels, since it comes out of the factory with the other slot unbootable, it's best to switch slots and run flash-all on the other (inactive) slot to set it up right. That or take an OTA.
[Google Pixel 8 Pro] Normandroid:
Thanks. I rebooted after it flashed "sending 'boot_b' "writing 'boot_b' and was confused why Magisk didn't show me rooted. So I restarted the phone and then started digging into this forum a bit deeper.
[Google Pixel 8 Pro] wangdaning:
You can just use the original boot.img and use "fastboot flash --slot all boot boot.img" and you will be back to where you started.
[Google Pixel 8 Pro] badabing2003:
I wouldn't recommend anyone flashing factory firmware unless for whatever reasons they can't flash full OTA , or are downgrading or fixing some corner case issue that can't be fixed by full OTA.

Time and again I see botched factory flashing bricking devices.

Why chance it?
[Google Pixel 8 Pro] roirraW "edor" ehT:
@Normandroid, what @badabing2003 said above. I recommend the Full OTA Zip instructions in Post #2 instead of the factory image, especially on a brand-new phone, to help prevent bricking under specific circumstances. The Full OTA Zip method, especially if you do it twice, will also correct your accidental flash just as well as the factory image.

Good luck, either way!
[Google Pixel 8 Pro] rester555:
I have yet to do a full OTA install. I have always used the flash-all.bat factory image method. So essentially with the full OTA it does not wipe the phone correct? If I wanted to wipe the phone, can you still use the full OTA method?
[Google Pixel 8 Pro] simplepinoi177:
The best advantage of full OTA install (which is why WrT and the rest [knowledge brought to the masses by the reknown badabing2003] employ the method now) is by sideloading it twice, you have both slots bootable (in case anything happens and you want to switch slots and don't want to do work to activate the "inactive" slot) and no longer have an "inactive" slot....

Full OTA (or any OTA) does not wipe the phone.

As far as I know, there's no argument you can include with the OTA sideloading command that will also wipe (like flash-all does when "w" is included), but if you use PixelFlasher, it can do the wipe with the OTA sideloading for you (it just automates the process of wiping before/after applying the OTA)...
[Google Pixel 8 Pro] roirraW "edor" ehT:
As @simplepinoi177 said, plus in contrast (just to spell out), you cannot achieve two bootable slots by using the factory image, as for some weird reason, Google has the factory image utilize part of the alternative slot; i.e. each time you flash the factory image, then only the slot you most recently flashed it to will be useable.

As far as wiping, if you wanted to use the Full OTA Zip method, and you wanted to wipe, you could either wipe before "adb reboot sideload", or you could choose the recovery menu option "reboot to bootloader" and wipe using "fastboot erase userdata". I'm sure there are even more ways to achieve the same thing.
[Google Pixel 8 Pro] leveleyed:
How did you figure it out??? I have the same issue. What made it show up in device manager?

I see no "Android Devices" section in device manager. I can only get my Pixel 8 Pro to show up under "Portable Devices". I'm on Windows 10 home edition.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You followed the directions in Post #2 to install the drivers?

Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

Unlocking Bootloader

(required in order to root)

Starts step 8 in that section.
[Google Pixel 8 Pro] leveleyed:
If by step 8 you mean: "8. Download the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers."

then yes, I did download and unzip both of those.

However, there is a problem with the instructions here. There is no installer for the USB Driver in the zip file for it.

There is also no instruction to download and install Android Studio, which is how I learned I was able to actually install the USB driver (via the SDK manager, which I also used it to verify that the USB driver is actually installed).

From https://developer.android.com/tools/releases/platform-tools:

However, despite all of this, there is still no "Android Devices" section in Device Manager. It only shows up under Portable Devices:

To ensure I don't do anything wrong and potentially brick my brand new OOTB Pixel 8 Pro, I am following instructions here to the letter. And since there is no "Android Devices" section in the Device Manager, I am hesitant to continue until resolving this, or ensuring that the instructions should be revised to state "Android Devices" or "Portable Devices" in Device Manager.
[Google Pixel 8 Pro] simplepinoi177:
I think he meant more on the part

@roirraW "edor" ehT said

[*]The Windows USB Drivers may have to be installed twice:

The first time while your phone is running and unlocked as normal.

In Windows, right-click on the Start Button and choose Device Manager.

Plug your phone into the computer and look for the new hardware entry in Device Manager. Near the top of Device Manager should be Android Device. Click the drop-down arrow to the left of it.

Below Android Device, it should now show Android Composite ADB Interface

Right-click the Android Composite ADB Interface and choose Update driver

Choose Browse my computer for drivers

Click Browse and navigate to where you unzipped the Windows USB drivers to.

Follow the prompts to install the driver.

Keep Device Manager itself open - you'll need it again in a minute, but you can close any other Device Manager windows after you have installed the driver.

Open a Command Prompt and navigate to the platform-tools folder.

Run command:

adb devices

On your Android device, you'll get an ADB prompt. Check the box to always give ADB permission and click OK.

Confirm that the command results in a list of Android devices. When doing these producedures, you should only have the one device you want to work on connected, to keep things simple.

The second time to install the driver is while the phone is in Bootloader (fastboot mode),

not

FastbootD (fastbootd) mode. I know it's confusing.

Run command:

adb reboot bootloader

Repeat the instructions above starting with "Right-click the Android Composite ADB Interface".

This second time installing the drivers while in Bootloader (fastboot mode), it will show up as "Android Bootloader Interface". Thanks @simplepinoi177 for the suggestion to add this detail.

[/QUOTE]​
[Google Pixel 8 Pro] leveleyed:
​

The problem is, I don't see Android Device listed in Device Manager, nor do I see Android Composite ADB Interface. I only see it as shown in the screenshot in my post, under Portable Devices. I can still right click on Pixel 8 Pro and see Update driver, however. But I want to be sure this isn't going to be a problem before proceeding. Trying to follow instructions to the letter, and there is no "Android Devices" section or "Android Composite ADB Interface". Therein lies my dilemma.
[Google Pixel 8 Pro] EricAzure:
I believe it was simply that I had not enabled "Developer Mode" properly by tapping the build number.
[Google Pixel 8 Pro] roirraW "edor" ehT:
As @simplepinoi177 quoted, step 8 was just the beginning of the instructions.

I don't choose to install the driver that way, as it's overkill to do so just for Android Studio, but that's just my personal opinion, so that method may work better for you.

I understand your hesitation, but when installing drivers, you will definitely not cause any issues wherever you find the phone listed in Device Manager. In your case, I see that you have a Pixel 5 listed, too, so if you already had the drivers installed for the Pixel 5, they were already available for the Pixel 8 Pro to install as well - although it's possible the driver just needs updating, which you can still do by following the rest of the instructions, and just ignoring where I say in the instructions to look for the phone to be listed.

Rest assured that nothing you're describing will result in bricking your phone. It solely has to do with getting ADB and Fastboot commands to work with your phone, and if they don't work, then they won't work at all, and that's all that will happen - they won't work at all, leaving your phone exactly as it already is.

At this time (prematurely perhaps) I'd also like to advocate for the Full OTA Zip method instead of the Factory Image method once you get this all sorted out. Maybe I'll re-arrange those to put Full OTA Zip method first sometime. I'll give it some thought.

After making sure the existing driver is updated with the latest driver download (although the drivers aren't updated frequently, but I think was at least once in the last year or so), using the rest of my instructions, try a simple:

adb devices

in a command prompt, open to the same folder, as outlined in the instructions. If you get a list of attached Android devices, then you know it's working. Again, refer to the complete instructions, which @simplepinoi177 quoted, and is in Post #2 at the parts we indicated.

Hopefully the remaining steps go just fine for you.

The only thing I can think of is maybe you need to change your USB mode on your phone (I have it set to default to transfer mode in Developer Options, although I think MTP mode also works for ADB). What is your USB setting currently set to on your Pixel 8 Pro when you have it plugged into your computer?

Enabling Developer Mode, alone, should not have anything to do with getting the phone to show up in Device Manager - but as I mentioned above, it's possible it's dependent on what USB mode you have the phone set to when you have it plugged into the computer.

🤷‍♂️
[Google Pixel 8 Pro] leveleyed:
I have Developer Mode enabled, unlocked bootloader, etc, but still don't see Android Device(s) or in Android Composite ADB Interface in Device Manager - only Portable Devices and Pixel 8 Pro underneath it.
[Google Pixel 8 Pro] leveleyed:
It has USB debugging on, but I have to tap the notification to manually set it to File Transfer/Android Auto (other options are as shown in the image below).

And yes, I planned to do the full OTA zip rooting.

I've rooted 2 or 3 Pixel phones before, and just wanted to be sure that it wouldn't be a problem not seeing Android Device(s) section in Device Manager.

adb devices in cmd prompt shows:

List of devices attached
<serial number> device

Thank you for your prompt responses in this matter! I'm now confident to proceed with the rest of the rooting instructions.
[Google Pixel 8 Pro] Lughnasadh:
Do you have USB Debugging enabled in Developer Options? If not, enable that and Android Devices "should" show up if everything else is correct.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You can change that to default to whichever you like in Developer Options. You have to have it plugged into the computer while you're changing what the default is. This is optional, of course, just a convenience for me.

You should delete that code from your post above, as I think that might be your device serial number.

Everything's good, then. You just *might* have to install the drivers one more time if you ever go into Fastboot mode (such as when using Fastboot to flash the rooted init_boot.img after using the Full OTA Zip method, if you are rooting).

But again, if the Fastboot commands work for you, such as with the "Fastboot devices" command, when in Fastboot mode, then you should be fine.

You're welcome! Glad we could assist you. I hope the rest goes smoother for you.
[Google Pixel 8 Pro] leveleyed:
Yes, USB Debugging is enabled. No, Android Devices still doesn't show up.

Just ran adb reboot bootloader, and clicked the power button to start in fastboot mode. Still only seeing "Pixel 8 Pro" under "Portable Devices" in Device Manager. Just going to continue as if it were listed properly (as stated in step 12 of the "Unlocking Bootloader" section, it should be listed as "Android Bootloader Interface", but it isn't).

Thanks again!

I just tried this, but not seeing any output from the command. Am I supposed to not click the power button when it is showing fastboot screen and do the rest from there?

EDIT: I figured it out. ran adb reboot bootloader again and reopened Device Manager. First, only saw the device as shown:

Then, right-clicked, and updated drivers using usb_driver folder location.

Now, I'm seeing this:

Looks like it should be okay to proceed from here now. fastboot devices returns the following:

<serial number> fastboot

Okay. Now I've unlocked the bootloader, and am trying to proceed with the Full OTA zip root method. However, yet again, there was a missing step somewhere, since step 1 of these instructions are:

Problem is, there was no step prior to this, either in the bootloader unlock instructions, or before it, that tells me how or when to install Magisk on the phone!

So how and when is this supposed to be done? I have the Magisk-v26.4.apk file in the platform-tools folder.
[Google Pixel 8 Pro] simplepinoi177:
You can/should do it on Step 6 before "Launch Magisk"....
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good point! Instructions adjusted:

[ONLY if you already had your phone rooted before] UN-hide Magisk on the phone.

[ONLY if you already had your phone rooted before] Disable all Magisk Modules just in case they're not compatible with and cause a bootloop on the new firmware

Thanks for making me aware that I needed to adjust that.

Thank you!
[Google Pixel 8 Pro] leveleyed:
@simplepinoi177 @roirraW "edor" ehT - Actually, I'm still not sure how or when to get the

Magisk app

(apk file) installed on the phone. Does it need to be done before or after unlocking the bootloader? Do I flash the apk to the phone somehow?

I just unlocked the bootloader, but I don't have the Magisk app installed on the device. I didn't see any steps explaining how or when to install the app on the device prior to the first step of the

Full OTA Zip method

root instructions, which instructs me to unhide the app. But how can I unhide it when it hasn't been hidden or even installed yet? 🤔🤷‍♂️
[Google Pixel 8 Pro] simplepinoi177:
He hasn't updated the OP yet. If you look at his signature, he doesn't have too much time for XDA.

But I can try and assist. Unlock the bootloader first (this will wipe your phone). Then simply install the Magisk app via the .apk like any other app/apk. If anything, installing the app/apk doesn't actually root your or anything -- that's why the app is called/named Magisk Manager. It simply/directly helps you manage root (modules, permissions, DenyList, etc.).

Like he said,

so, "only if you already had your phone rooted before"...which it is apparent you haven't.

Please have/show some patience, you'll get there, and we'll get to handling/dealing with updating things and assisting you.
[Google Pixel 8 Pro] leveleyed:
Oh I'm sorry if it seemed as if I was being impatient! I just thought my previous post was unclear the problem I was having, since it was still unclear when or how to install Magisk.

Thank you for clarifying that it is to be installed after unlocking the bootloader! I guess I can probably figure out how to copy the apk file to the phone's storage to install it from there (downloaded it from github on my PC), unless that won't work and I need to install it via adb somehow? Either way, I'll try figuring it out first. Got Magisk installed now!

Now I am just wondering: will there be another point in the root process where the phone gets wiped?

I'm trying to determine if I should do the full setup now (after unlocking the bootloader), migrating all of my data from my Pixel 5, or if I should wait until after I finish rooting, and then maybe do a factory reset and migrate everything at that point?

Thanks again for the help!