yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
For anyone who hasn't seen, although as far as I'm aware, no one has rooted their Pixel Watch 2 yet, or reported trying to, ADB access and OEM Unlocking are accessible on it, so unlocking the bootloader and rooting might be too - all through the included charging cradle - just make sure the watch is as securely as possible connected to the charging pins. I'm just glad that the charging cradle carries data, and not just power.

Of course, I don't know if there really is a practical reason to root the Watch 2, and I'm not necessarily going to root mine when I get it in two weeks, but we'll see.

July 1, 2024 TWD9.240705.001.A1 Pixel Watch 2 Wi-Fi (Aurora) and LTE (Eos) firmware updates / + root directions by LLStarks

Pixel Watch 2 Wi-Fi (Aurora) and LTE (Eos) July 1, 2024: For both LTE and Wi-Fi models: https://developers.google.com/android/images-watch https://developers.google.com/android/ota-watch...

xdaforums.com
[Google Pixel 8 Pro] snovvman:
Lol, if it's a device, it will be rooted. If it can't be rooted, it will still be rooted. Even if it doesn't need to be rooted, it will still be rooted. What a crazy bunch we are.
[Google Pixel 8 Pro] Lughnasadh:
Yeah, I don't know what the hell is going on or what Google is doing, lol.

📳🔥PixelFlasher for Google Pixel 8 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

[MODULE] [MOD] Universal SafetyNet Fix

Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...

xdaforums.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
LOL! MUWAHAHAHAHA! Insert evil Jeffrey Combs laugh here.
[Google Pixel 8 Pro] Ultimoose:
I downloaded the singleton that is October, not the 3 called September and used it to root and my phone is reporting it's on October release. That is as of about 8:00 a.m. CST Oct 12th.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, I'm digging a foxhole, fortifying it, jumping in, and watching through my binoculars in all directions until this is straightened out.

No tin foil hat, though. I'm not that crazy.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks for the report! Yeah, I'm withholding judgement until there are more confirmations that the October one somehow isn't actually the October firmware. I mean... Google labeled it in the running Android wrong, too? Doesn't seem likely.

Until then, I'll continue believing that they're labeled correctly, except *maybe* that some or all of the September images are August instead, which is just fine with me, although I still hope it gets fixed sooner than later.
[Google Pixel 8 Pro] A.Priori:
Nice, I'll try this soon. Thanks
[Google Pixel 8 Pro] WorldOfJohnboy:
Ding Ding Ding, we have a winner... flashed Verizon Sept. Boot, then rebooted and flashed October Boot, no more stupid message. Thank you! (Thanks @roirraW "edor" ehT as well)

I guess I'll be the one to take one for the team and say that this method works for the 8p!
[Google Pixel 8 Pro] Lughnasadh:
Awesome! Thanks for reporting. Thought it may not work based on my most recent post about this.
[Google Pixel 8 Pro] roirraW "edor" ehT:
That is truly awesome! Thanks for following through and following up, and thanks @Lughnasadh!
[Google Pixel 8 Pro] Kingcool88:
Rooted and used

https://github.com/chiteroman/PlayIntegrityFix/releases/download/v9.2/PlayIntegrityFix_v9.2.zip

together with Magisk Delta to pass Google Wallet security check. If anybody need to know :)
[Google Pixel 8 Pro] snovvman:
Following up on my plan, given @WorldOfJohnboy's findings and no other mentions of QPR1b2, here are my modified steps. I also switched things around a bit. Please let me know what you think.

0) New phone out of the box

1) Extract Sept Verizon init_boot AND Oct init_boot, patch them with P6P Magisk 26301 and store on computer.

2) Unlock bootloader of P8P. Boot to bootloader. Flash with 33.0.3.

3) Flash Oct image (flash-all, remove -w and add --no restart), reboot from fastbootd to bootloader, fastboot flash init_boot --slot all magisk_patched.img from Sept VZ, let phone. boot, then flash the Oct patched init_boot.

4) Fastboot reboot and start new phone setup. migrate Google phone backup from P6P, install magisk.apk, install safetynet fix, install SwiftBackup.

5) Copy SD contents from P6P.

6) Restore from SwiftBackup.

7) Restore from Nova backup.

Many thanks!
[Google Pixel 8 Pro] reaper000:
And for the sake of convenience, here's the current (as of 10/12/23) Magisk-patched init_boot.img that you can flash to obtain root..

(Disclaimer: if you don't know what to actually do with this file, then you need to learn about root first)
[Google Pixel 8 Pro] Utini:
Let me summarize again for a new P8P out of the box:

0. Pre-requisites in Android Developer Settings

- OEM Unlock in settings

- USB Debugging enabled in settings

1. Unlock Bootloader:

adb reboot-bootloader

fastboot flashing unlock

- Now the phone will be completely wiped

- Now the phone will reboot into Android

2. Root & also update + re-root:

- Download latest factory image and extract it

adb reboot-bootloader

fastboot devices #to check if device is detected

fastboot flash bootloader xxx.img #updating to latest bootloader from downloaded image

fastboot reboot-bootloader

fastboot flash radio xxx.img #updating to latest radio from downloaded image

fastboot reboot-bootloader

fastboot --disable-verity --disable-verification update xxx.zip #updating to latest version and (again) disabling verification.

- Now the phone will reboot into Android without being wiped

- Install latest canary Magisk

- Extract and copy init_boot.img from factory image to phone

- Patch init_boot.img with Magisk

- Copy patched init_boot.img to PC

adb reboot-bootloader

fastboot flash init_boot magisk_patched_boot.img

fastboot reboot

3. Disable automatic OTA updates

- Settings -> Developer Options -> Disable Automatic System Updates

To update with a pc:

- Reboot to fastboot ("adb reboot bootloader")

- sudo fastboot devices

- Flash full factory image but remove -w from the flash script to preserve data

- Alterantive: Run each line from "flash_all.sh" manually with sudo. REMOVE -W !!!

- If flash doesn't load anything, change cable & port

- Now the phone will be on stock kernel and without root

- Install Magisk Manager

- Extract init_boot.img from factory image .zip and move it to the phone

- Patch init_boot.img with Magisk

- Move magisk_patched.img to the PC

- Reboot to fastboot ("adb reboot bootloader")

- Flash patched boot.img ("fastboot flash boot magisk_patched.img")

- Boot android which is rooted now ("fastboot reboot")

- Install the kernel via e.g. FKM

Correct?
[Google Pixel 8 Pro] snovvman:
Just sharing my experience. @roirraW "edor" ehT, @Utini, and many others have done a much better job with instructions. The above was the second iteration of my plan, but this is what happened so far:

0) New phone out of the box

1) Extract Oct init_boot, patch with P6P Magisk 26301 and store on computer.

2) Unlock bootloader.

3) Flash Oct image w/ 33.0.4 (flash-all, remove -w and add --no restart), fastboot flash init_boot --slot all magisk_patched.img.

4) Boot, install magisk.apk, restart, and root!

That was easier than I thought!
[Google Pixel 8 Pro] EricAzure:
There is no "Android Devices" showing in my Device Manager. Any ideas? It says I have the latest google USB drivers already.

Edit: I figured it out
[Google Pixel 8 Pro] beterman:
is there any chance to get 32-bit support for apps?
[Google Pixel 8 Pro] Utini:
Using this method I somehow f***ed up.

I unlocked the bootloader, flashed everything (at the end with -w --disable-veritfy --disable-verification) and after the reboot it says:

Cannot load Android system. Your data may be corrput.

It lets me reboot (which doesn't work) or factory reset.

What to do?

Edit:

I selected "factory reset" and now I am booting fine again. No idea if vbmeta is disabled now though?
[Google Pixel 8 Pro] roirraW "edor" ehT:
After the first line in the quoted part of your instructions below, you would have had to factory reset, because the first time you disable Verity and Verification, you have to factory reset because of the corruption message, so it's normal.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Another hype message for the P8P: The face unlock is amazingly fast on this phone! I'm impressed. Or did I already hype the face unlock? I don't remember. These days are blurs.
[Google Pixel 8 Pro] cmh714:
I for one am having so many issue with Apps not working, I think I need to reflash and start again. PITA! :)

Regular app, rooted stuff, all sorts of oddities
[Google Pixel 8 Pro] snovvman:
Following up on my journey, I have since

5) Setup the phone and migrated files and settings using the Google transfer tool from phone to phone. Many apps, files, and settings moved over just fine.

6) Installed safetynet fix (MOD 1.3) and hid Magisk, cleared data on Play Store so it is certified.

7) Connected OTG with all the SD files from P6P and copied over files that the migration tool did not, including (strangely) some files in Download, Swift Backup, and other backup files.

It's been smooth so far. I did not have to flash the Sep init_boot first. Oct worked the first time.

QUESTION: Are there good replacements for Greenify and/or MyAndroidTools? In the past, I used MyAndroidTools to cut off broadcast receivers to keep apps from starting up, "app mesasurement", and other conditions. It worked well for me. We all know what Greenify did. I am looking for something that will keep infrequently used apps from starting up and/or receiving certain broadcasts such as user present.

QUESTION2: I see some people talking about disabling verity when flashing. Is this for QPR? I didn't have to do that.

Thanks.
[Google Pixel 8 Pro] cmh714:
So I just reflashed QPR over the top of my previously QPR flash. I left the -w in the script because I wanted to start completely fresh. Using the latest flash tools 34.04, it DID NOT wipe me......not sure I trust 34.04!!!!

Just an FYI!

*** just realized I shouldve put this in the QPR thread.....My bad! Sorry!
[Google Pixel 8 Pro] Zilla0617:
How did you get to this is to work? With normal Magisk Google Wallet works fine, but not the digital state ID function (Maryland). I switched over to Delta, hid the app, configured Google Wallet to be unmounted with modules, but it stills detect unlocked bootloader
[Google Pixel 8 Pro] snovvman:
I recall reading in earlier posts in this thread that 33.0.4 does not wipe even with -w, otherwise works fine.
[Google Pixel 8 Pro] almahix:
I may not be the sharpest knife in the drawer but I'm learning. I was unable to unlock my bootloader but it turns out I don't need to if all I want to do is root. I've just read that it is possible to root with magisk even with a locked bootloader. Can someone kindly verify that this is correct please?
[Google Pixel 8 Pro] KingKj52:
I think I've bricked my phone and really need some help. I have a Pixel 8 Pro from Google Store. I think what I did wrong is I updated the phone on arrival (so October update), then flashed it in the first step to root (after following steps up to that point) with the Factory image, not the OTA update, which also says September, but I guess I needed the OTA and not the Factory Image?

Anyways, after the flash-all (I got rid of the -w), it failed to boot, and offered to reset. I tried to boot once or twice more, and now its just a black screen. Holding power does nothing. I'm not sure what to do from here.

I see the earlier message about how factory resetting is normal, but my phone is just a black screen. If I plug it into my PC, the PC makes sound like its trying to connect, but then shows the device I connected malfunctioned and windows can't recognize it.

Holding power + vol down doesn't seem to do anything either.
[Google Pixel 8 Pro] Tomadock:
Nope, you definitely need to unlock the bootloader to root with Magisk.
[Google Pixel 8 Pro] roirraW "edor" ehT:
What @Tomadock said. You absolutely need to unlock the bootloader in order to root. Is the source for the incorrect information saying that you don't need to unlock the bootloader for root, on XDA? If so, do you have a link?

Oh boy. I'm not clear on what exactly you did, besides maybe mixing and matching two different firmware months since you mention both October and September, but it sounds pretty likely you'd need to RMA it to Google ASAP. Or just straight return it and buy another one.

To be clear, you can update and root with either the factory image or the OTA.

As a last ditch effort, you could try the Official Google Android Flash Tool, although I hate to say I don't feel there's much hope in recovering it.
[Google Pixel 8 Pro] almahix:
Unfortunately I have not been able to unlock the bootloader. It is said to be an unlockable phone but "fastboot flashing unlock" seems to be an incorrect instruction. Fastboot just display all commands but flashing isn't one of them.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Are you following the directions in Post #2 exactly?

You went to Developer Options and enabled "OEM unlocking" and "USB Debugging"

Downloaded the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers?

Installed the drivers (up to two times - once while Android is running, and once after you boot into the bootloader)?

Confirmed Fastboot sees your phone with:

fastboot devices

while you have the phone in bootloader mode?

Does:

fastboot reboot bootloader

do anything?

fastboot flashing unlock

is definitely the right command for the Pixel 8 Pro, but check all the above to make sure fastboot works at all for you, first.
[Google Pixel 8 Pro] almahix:
I genuinely appreciate your support. You're a terrific moderator. I sent the phone back and reordered another in case they sent me a locked one. I'll have it next week and will try what you've suggested. Keep up the good work!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you for your kind words! So, you were able to enable "OEM unlocking"? If you weren't, then that's why "fastboot flashing unlock" wouldn't unlock the bootloader, and if you were able to toggle it, then your phone was definitely unlockable.
[Google Pixel 8 Pro] znel52:
You're a legend for this. been trying to figure out what the hell i was doing wrong lol. Installed that version and boom
[Google Pixel 8 Pro] johnha:
Wondering if anyone has an issue with unzipping the October image at: https://developers.google.com/android/ota#husky

I verified the checksum but after unzipping, it's not in a format I'm familiar with. I can't find the init_boot.img file, etc.

edit: I was accidentally on Google’s OTA page, when I ordinarily use the Factory Images page to download the files used to root. Many thanks to @roirraW "edor" ehT
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, all, I got off my lazy butt and at least updated that portion of Post #2:

SafetyNet

:​

You do not need more than one of these:

@Displax Universal SafetyNet Fix Mod on XDA.

DO NOT INSTALL v2.4.0 Mod

2.0

- this one will

NOT

work completely

DO

install v2.4.0 Mod

1.3

- this one will work correctly

Another choice is @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)

@kdrag0n's Official Universal SafetyNet Fix released - this one will NOT work completely
[Google Pixel 8 Pro] roirraW "edor" ehT:
Howdy! I use the OTAs, too. Had no problem unzipping the OTA Zip.

In the OTA zip, the init_boot.img is inside the payload.bin. You can get init_boot.img out of payload.bin with the free "payload-dumper-go" by @ssssut (XDA thread [TOOL] A QUICK Android OTA payload dumper) and directly from GitHub. At GItHub, click the Releases link at the far right, down the screen a bit.

In the command prompt, open to the folder where you hopefully have ADB, FastBoot, the OTA zip, and payload-dumper-go.exe, extract the payload.bin file out of the OTA zip, and run:

payload-dumper-go.exe -p init_boot -o . payload.bin

The period . after -o will cause it to put init_boot.img in the same folder as where you're running the command in (if you have the command in the same folder with all the rest of the files).

Thanks to @badabing2003 for leading me to that tool and educating me about it. Now I no longer download the factory image zip (except for archival purposes, in case of serious accidents).
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, the root instructions and all have been integrated into Post #2. There are still some minimal out of date pieces of information that I need to adjust sometime, and I haven't updated about the latest option (on P7P kernels) not requiring Verity and Verification to be disabled, but we'll see if that will be the case with the first P8P kernels when they start coming out.
[Google Pixel 8 Pro] ThatOneGuyOverThere:
Is there any way to reenable 32 bit app support?
[Google Pixel 8 Pro] Kingcool88:
You used the module I linked also?
[Google Pixel 8 Pro] gpvecchi:
I'm planning to try a custom kernel in future, so I'll have to disable the verify, as this will wipe my data. I'll have to do it every time I'll update the software, as it will be re-enabled by default.

What it's not clear to me is, if I forget to disable it again, will my data be wiped?
[Google Pixel 8 Pro] Morgrain:
Previous Pixels kept the ability for 32 bit hidden deep in the system for compatibility reasons, AFAIK the Pixel 8 does not. It's gone.

It might be possible to get it working with a custom kernel, custom OS and if a person would manage access to the decompiled architecture of Tensor 3.

That's quite unlikely however. Maybe someone will find a way to emulate, but that would be quite taxing on a chipset already struggling with efficiency. The Pixel 8 AFAIK does not support 32 bit natively any longer on a hardware basis.

If there are lazy companies not willing to update their apps to a modern architecture, then you are out of luck on a Pixel 8.
[Google Pixel 8 Pro] gpvecchi:
RIP Pornhub app. 😂
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good question. The deal is that if you forget to disable Verity and Verification, then if you don't actually try to boot the phone, you can disable them and no factory reset will be required.

If you forget to disable them, and you do try to boot the phone, then yes, you'll have to factory reset.

Note that disabling or not disabling them doesn't actually wipe your device, no matter what. It's a small difference, but rather, they corrupt (or report as corrupt) your device until you wipe it manually (although that's not the only cause of corruption messages, and in at least one other case, a different solution is required).

I have chosen to never disable them, but that's my personal preference. I have one or two accidents a year anyway where I forget some step on my phone, without having to worry about disabling them.

I am hoping that the method that has been found recently on the Pixel 7 Pro, to not need to disable them for custom kernels that implement the fix, will apply to the Pixel 8 Pro, too. If not, then I won't be using custom kernels. Nothing against anyone at all, especially the Developers. I'm just too clumsy. :)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Added new section to:

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

IF you forget to disable Verity and Verification
[Google Pixel 8 Pro] bsg411:
If I unlock the bootloader and root ... At what point could I do the built-in Google data transfer from my old phone to the new one?
[Google Pixel 8 Pro] beterman:
I just hope that someone gets 32-bit to work, let's just give things a little time, the device has just come onto the market =)
[Google Pixel 8 Pro] Zilla0617:
Yes, I installed the integrity fix with same result. Somehow Google wallet still detects unlocked bootloader therefore unable to set up digital ID
[Google Pixel 8 Pro] roirraW "edor" ehT:
When you boot the phone the first time after unlocking the bootloader (which causes a factory reset) and the phone goes through the first time setup (OOBE "Out Of Box Experience"). You can do it before you root or after, either way, doesn't matter.
[Google Pixel 8 Pro] Gilg@mesh:
just asking here, when rooted etc , I will be able to remove that ugly search bar on stock launcher? thanks
[Google Pixel 8 Pro] badabing2003:
Verity enabled -> Verity disabled will require a wipe (every single time)

Verity disabled -> Verity enabled does not require a wipe, but if this happened because you forgot to keep it disabled, then you would need to disable it again and it will require a wipe.

Another caveat that you should be careful about, these devices have two slots, you might end up disabling verity on one slot, switch to the other intentionally or unintentionally which has it enabled, you can't switch back without a wipe.

Hence why it is advisable that the very first time you want to disable Verity, you do the following.

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

This will disable verity on both slots, perform the wipe and bring your to OOBE

At this point do what you want, and making sure that each time you keep Verity disabled.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I have no idea if there is any root modification available to remove the search bar on the stock launcher. I've used Nova Launcher for ~11-12 years, so I just don't keep track of that. It won't surprise me if there is just no way to remove it without installing a third-party launcher or at least a modified version of the Pixel Launcher.

Would you mind if I quote/link to your entire post for:

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

IF you forget to disable Verity and Verification

?
[Google Pixel 8 Pro] Gilg@mesh:
ok hopefully there is a way, using third party launcher does it not break the swipe smoothness?
[Google Pixel 8 Pro] badabing2003:
Of course not. (to be clear, I don't mind, if double negative makes it confusing)
[Google Pixel 8 Pro] bsg411:
Got .. and thank you for your work in this forum and platform.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't have any major problem with the swipes. Maybe once in a great while there's a hiccup with Recents, but I just normally have to swipe Home and then swipe Recents again. I know some people recommend disabling Animations in Developer Options, and maybe that takes care of any problem they had.

Any problem I've had wouldn't be worth me switching away from what I achieve in Nova. :) Note that I stick with v7, I haven't tried the v8 Betas they've had over the last year (and a half?) since it was sold.

Cool, thank you!! And done.

You're welcome! Cheers.
[Google Pixel 8 Pro] nujackk:
OK, I bought mine via google store, came with 14.0.0 (UD1A.230803.022.A4, Sep 2023, US-Emerging/G-store,CA,TW,AU,Fi) firmware

Going to use on t-mobile so can i flash the t-mobile version 14.0.0 (UD1A.230803.022.B1, Sep 2023, T-Mobile)

I'm assuming the t-mobile version has a t-mobile specific modem.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You should flash the lone October firmware. It will still work on T-Mobile.
[Google Pixel 8 Pro] roirraW "edor" ehT:
‘Google Camera’ is now ‘Pixel Camera’ on the Play Store

Google Camera has been exclusive to Pixel devices for several years now, and it’s now being renamed on the Play Store to better reflect that.

9to5google.com
[Google Pixel 8 Pro] snovvman:
I recall some time ago when flashing QPR on my P6P for the first time, I had to disable verity. Somehow, though, I found a way to not wipe but I do not recall how. I am already rooted and will want to QPR at some point. Will this once again require disable verity and there for a wipe?
[Google Pixel 8 Pro] nujackk:
I'm sure it would work, But i've read a number of people complain about network issues with t-mobile on previous pixels. And i;m thinking using t-moible specific firmware would help. Just concerned about bootloop