yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] simplepinoi177:
I was starting to feel confident with r34.0.5, but with 2 members having incidents in the last couple of days of what seems to be hard-bricks after the flashing in FastbootD, I'm worried now.....

It's been a couple of days since you made this post, so there's a good chance you already attempted the updating and/or rooting....but if you haven't and are still interested in flashing/applying-the-firmware-image/update to the other slot automatically (particularly if you didn't want to load the OS and wanted to immediately go to the other slot and update), if you use PixelFlasher, there is an option/capability (among all the myriad others) to apply to both slots (either using the slot-all parameter [i imagine] or by manually switching slots and applying the firmware image again) and/or not reboot after applying update and/or to even apply the patched image without loading the OS (if you were interested in that)....
[Google Pixel 8 Pro] roirraW "edor" ehT:
Now I'm even more glad that I already switched to using the Full OTA Zip method each month (both slots), so no FastbootD re-involvement.
[Google Pixel 8 Pro] Lughnasadh:
Flashed the A14 QPR1 Beta 2.2 factory image on both my Pixel 7 Pro & Pixel 8 Pro using Platform Tools 34.0.5 (via flash-all) with no problems, for what it's worth.
[Google Pixel 8 Pro] zellleonhart:
I have been updating to the latest QPR by flashing the factory image and the process works well for my case, where I need to disable verity & verification for flashing custom kernel. If I switch to using Full OTA zip, do I have to disable verity and verification someway? Or this step is not needed anymore?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I would always assume you have to disable Verity and Verification each time, just because 1) it won't hurt, and 2) it's a good habit to have, if you need that sort of thing. That way, if you switch methods, it'll still be part of your process, and you won't accidentally forget and find that you have to factory reset because you didn't disable them and now your user data is corrupt. :)

But if I remember correctly, @Lughnasadh has answered that question before. @Lughnasadh?
[Google Pixel 8 Pro] Lughnasadh:
Yeah, you would still need to disable verity and verification when sideloading the Full OTA because it will replace your modified vbmeta image with the stock vbmeta image, thus enabling the flags.

After sideloading, but before booting, you can just go into bootloader/fastboot mode and flash the vbmeta image with the disabling flags. Should work...
[Google Pixel 8 Pro] zellleonhart:
I see, I don't mind disabling Verity & Verification each time, but just not sure what is the right process with Full OTA zip, since I will use adb sideload instead of flash-all.bat.

Is this correct?

1. adb reboot sideload

2. adb sideload husky-ota-AB#a.YYMMDD.##-blah.zip

3. Choose recovery menu option reboot to bootloader

4. Disable verity & verification fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Google Pixel 8 Pro] Lughnasadh:
Yeah, that should work.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Check Post #2 where I detail all the steps for the Full OTA Zip method, including the optional flashing the Full OTA to the second slot, where you can leave one slot unrooted if you want, or just root both slots like I do. I will add the (optional) disabling Verity and Verification command into the steps ASAP at the right place.

Edit: Done edited.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I guess I have to actually add the instructions to extract the vbmeta.img from the Full OTA Zip, now. Whoops!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Added to Post #2 Full OTA Zip method instructions:
[Google Pixel 8 Pro] tomer82:
Hi and thanks for your excellent tutorial on the Pixel 8 and others,

coming from a S22 i'm a little confused about the steps needed to disable Verity and Verification in order to flash a custom kernel,

do i need to wipe my device every single time if i choose to use the Full OTA method?
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome and thank you! Good question, it's fair to ask, and it's very commonly asked. No. As long as you disable Verity and Verification each and every time you flash anything that flashes vbmeta.img (such as the factory image, the Full OTA zip, or using the Official Android Flash Tool site), then you will not have to wipe again.

If you do happen to not disable them, and you start booting the phone, then you won't have to wipe right then (IIRC), but when you re-disable them, you will have to wipe again.

If you don't disable them and realize it before you boot the phone, then simply disable them, and you'll be golden.
[Google Pixel 8 Pro] simplepinoi177:
It seems add another one to the list ("Somewhere in the middle it failed" sure sounds like FastbootD flashing, but the wording doesn't say exactly) and is reminiscent of the other two instances I previously mentioned :eek: ; quoted below....
[Google Pixel 8 Pro] roirraW "edor" ehT:
Magisk Stable v26.4 released:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 8 Pro] Jose.pH:
After the update I can't install the apk anymore
[Google Pixel 8 Pro] roirraW "edor" ehT:
You'll have to be more specific, please.

I'm assuming you mean the Magisk update. If you updated already, how do you mean that you can't install the APK?

Also, do/did you have Magisk hidden? You should unhide it before updating, otherwise you might end up with one hidden Magisk installation and one unhidden. What method did you use to update Magisk?
[Google Pixel 8 Pro] Jose.pH:
I updated from the app, first magisk and then the app, when I restarted the phone the app disappeared, even if I try to install the apk manually it doesn't work
[Google Pixel 8 Pro] Voklav:
I can't root my phone (patched image with Magisk Stable v26.4)

History:

adb reboot bootloader

fastboot flash init_boot magisk_patched-26400_W7tS5.img

fastboot reboot

EDIT:

tried with Magisk Stable v26.3 and all work normally!!

pfff... p.s. was afraid that I was doing something wrong - I hadn't done these things since the htc m8

Should I report a bug on github?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Did you have the Magisk app hidden to start with?

From memory, you should update the Magisk app itself first (after unhiding it), then direct install Magisk. After all, if you do the direct install first, you're just direct installing the same v26.3 (I assume) you already had, since the app isn't updated yet.

It would probably be better if they had the App section above the Magisk section.

Try re-flashing your device and start from scratch. Probably some simple error. It's impossible to tell what happened just from this information.
[Google Pixel 8 Pro] Jose.pH:
Magisk wasn't hidden, but yes I was wrong and I updated Magisk first and then the app... now what should I do? repatch everything with pixelflasher?
[Google Pixel 8 Pro] Voklav:
I tried many times. Only works with Magisk v26.3

After successfully rooting the phone. Updated v26.3 to v26.4 normally.

What i'm saying is i failed to root the phone directly via v26.4
[Google Pixel 8 Pro] Jose.pH:
I try to repatch with pixelflasher but nothing, I would like to avoid doing manual things....
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm sorry to hear it's not solved yet. I would do a full re-flash of the full stock ROM first (no wipe necessary), then re-root. I don't use PixelFlasher, I do things manually, so it's possible you might get better advice in @badabing2003's PixelFlasher threads.

Edit: From your screenshot, it appears to me, you only have to get the Magisk-patched init_boot.img re-flashed to the device, and then you should be good to go. (and re-configure Zygisk and any other Magisk options)

Ah, I see. That's interesting. We'll see if we get more reports of the same. Thanks for letting us know.
[Google Pixel 8 Pro] Lughnasadh:
So it fails to root with 26.4 via fastboot flash? What about direct install?
[Google Pixel 8 Pro] badabing2003:
How can you even create a proper patch for 26.4 if you don't have it installed?

I just tested it on Pixel 5, no issues.

I had Magisk 0352ea2c:26302

Installed Magisk aa6c7c15:26401 with PF

Created a patch

Flashed the patch

Perhaps Pixel 8 related, which I don't have to test.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I think he already solved it. I believe they clicked Install besides Magisk first before Update on the App, but they've straightened it all out now.
[Google Pixel 8 Pro] badabing2003:
Happy to hear that they already solved it, but I still fail to understand how they get the Install option if the app is not updated.

The app needs to be updated first to offer the update to Magisk.

My understand is that.

The app checks for app updates only.

Once installed it checks if Magisk matches the app version, and if not offers an update.

I have never seen any other behavior, I could be wrong, but that is my experience.
[Google Pixel 8 Pro] roirraW "edor" ehT:
The Install option is always available, whether there's an update or not. It turns into "Update" after the app itself is updated. It was just confusion, but it's understandable in my opinion.
[Google Pixel 8 Pro] Lughnasadh:
I'm guessing when they were on 26.3 there was no "Update" button for 26.4 since they didn't update the app to 26.4 (as you alluded to), but only the "Install" button. I think they then installed but of course since they didn't update the app they were installing the same version they were already on (26.3). Even without updating the app, the install button will still show the 3 options available, if rooted (Inactive Slot, Direct, Patch Image).

EDIT: And Ninja'd by The Rode Warrior 😅
[Google Pixel 8 Pro] badabing2003:
It still does not make sense.

1- Hit the install option before updating the app. It installs the same patch that you already have, nothing changes

2- Install the app, it shows an update option for Magisk, but it should still be rooted with the previous step 1

No reason to lose root either way.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm not going to look back and check, but I don't recall if he mentioned the method he used to update the Magisk-patched init_boot.img. Some people choose not to Direct Install. Case in point, another user in my P7P thread (it's all running together now, though, so I might have lost track which thread).

Edit: Nevermind. It's REALLY all running together now. LOL!

Whether it makes sense or not, I have no reason to doubt them. In the end, all that matters is they fixed it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android Security Bulletin—November 2023 | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] Lughnasadh:
Direct Installing Magisk Stable 26.4 went fine for me (A14 QPR1 Beta 2.2; yes, I know this isn't the Beta thread🙃).
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Pixel Update - November 2023 - Google Pixel Community
[Google Pixel 8 Pro] Lughnasadh:
November Images are up.
[Google Pixel 8 Pro] roirraW "edor" ehT:
:D

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 Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] rester555:
No mention of radio improvements.. Anyone know if the radio has a new image?
[Google Pixel 8 Pro] Pixel86:
It does not. Same radio from October build.
[Google Pixel 8 Pro] rester555:
Here's to December build
[Google Pixel 8 Pro] Morgrain:
Well, that changelog is a bit of a disappointment. I was expecting more bug fixes.
[Google Pixel 8 Pro] Gilg@mesh:
ok, I was trying to update using PixelFlasher with factory image, but now in a bootloop, I did not patch the init_boot.img as I thought as I already have Magisk installed it would not be needed, anyway, how can I get back into Android now? Thanks
[Google Pixel 8 Pro] roirraW "edor" ehT:
@Lughnasadh (and @Ghisy FYI even though this is the P8P thread), I didn't have any of the root trouble that I had unhiding, and updating (while still on October firmware) as I did on the P7P.

EXCEPT that Magisk got a clone, and it was easily deleted, after which the non-cloned Magisk worked fully as expected, and was able to re-hide although as previously noted by (you? someone?) and myself, it took much longer than usual to re-hide it, and it got another clone of the hidden Magisk, which I was able to again delete without trouble.

So still got Magisk clone troubles, but root fully worked the whole time despite that.
[Google Pixel 8 Pro] Lughnasadh:
I would suggest going over to the Pixel Flasher thread and submit support file so he can look at it and see what went wrong.
[Google Pixel 8 Pro] roirraW "edor" ehT:
First, do you want to use PixelFlasher to fix things, or you want to fix things manually?

If you want to use PixelFlasher, you'll likely get quicker help in the PixelFlasher thread. Just say the word if you'd like the manual way(s) to fix.

Ninja'd by @Lughnasadh again! 😜
[Google Pixel 8 Pro] Gilg@mesh:
I have no problem fix it manually as I used manual mode first time haha :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, next question, although it may not apply if you don't have a rooted/patched init_boot.img: Before updating the firmware, did you deactivate all Magisk Modules?
[Google Pixel 8 Pro] Gilg@mesh:
no, should have done that I see now :D
[Google Pixel 8 Pro] Ghisy:
For what it's worth, I usually don't disable my Magisk modules before updating. I know I should but I don't have anything critical in there.
[Google Pixel 8 Pro] Gilg@mesh:
OK, I'M BACK! I think the problem was I did not see PixelFlasher status window when it flashed, anyway I'm inside Android now, but I think I'm not rooted. :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, then either way, next you should just follow the directions in Post #2. I would use the Full OTA Zip methods - whether you choose only to flash one slot or both, it's up to you. See what that gets you.

I quite often don't, either. But I also normally wait days for other users to report their experience, but at least once - maybe twice, I was caught in a situation where I should've and had bootloops until I used one of the methods in the OP to get to a bootable state again.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, so just use the directions in Post #2 to Magisk-patch the init_boot.img (you can do so using either the factory image zip, or the Full OTA Zip - directions for doing so in each method's steps).
[Google Pixel 8 Pro] Ghisy:
Same here. What years of working in IT have taught me: don't jump on an update right away. It's always best to wait it out for a few days.

On a completely different topic, seems like everyone got a P8P but me. Boohoo. :(
[Google Pixel 8 Pro] gettinwicked:
I pretty much always forget too lol.. However, I haven't had an issue yet, and I've been doing this since pixel 2xl. #knocksonwood
[Google Pixel 8 Pro] rester555:
Updated with no issues.
[Google Pixel 8 Pro] roirraW "edor" ehT:
At least some of us, I included, kept our P7P due to low Google trade-in values, and personally for me, I decided not to sell on Swappa or trade elsewhere, so that I have a modern spare phone.
[Google Pixel 8 Pro] Gilg@mesh:
can I just flash the patched magisk.img or do I need to flash everything? :)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Correction, @Lughnasadh. PixelXpert cloned again at some point on the P8P, too (still haven't updated firmware, only Magisk and PixelXpert sometime today).
[Google Pixel 8 Pro] Ghisy:
Yeah, Google trade-in values for their own phones are ridiculously low. They sure don't entice users supporting the brand to upgrade. Although I never resell my phones for some reason. I still have a P6P that I barely used but I'm gonna be using it for emulation purposes with a Gamesir controller.

Anyway, I'm way off topic now. Oops. 😅
[Google Pixel 8 Pro] roirraW "edor" ehT:
If the phone boots up fine, but you just don't have root, then flash the Magisk-patched init_boot.img, and if you don't have the Magisk app installed when you boot up (and it's not hidden), then reinstall that, too.
[Google Pixel 8 Pro] roirraW "edor" ehT:
That's okay, I don't mind some reasonable amount of off-topic, and happy to see you in this thread, even if you don't have a P8P.
[Google Pixel 8 Pro] Gilg@mesh:
Yes, thank you, everything is back to normal. :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
LOL, I wonder if anyone was confused by my Full OTA Zip method instruction saying to put the Magisk app back in the Root tab. This note was just for me since I use Nova Launcher and I put root capable apps on their own app tab. ROFL! Fixed now.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Great to hear!
[Google Pixel 8 Pro] Ghisy:
Thanks dude! I appreciate it.

Back on topic, I really do want to get a P8P in bay blue, love the color. I would have traded my P6P actually if Google didn't give me a meager 263 euros for it (around $270). It's ridiculous, the thing is like new. *sigh*

Not to mention, prices have gone up 160 euros (around $170) in Europe for the 256 GB model. Can't really justify the upgrade until there's a significant price drop. And that's gonna be around the P9P release and the cycle will start again!

Anyway, I hope you guys are enjoying your P8P. 🥺
[Google Pixel 8 Pro] roirraW "edor" ehT:
I definitely hear you. The $600 trade-in for the P6P when I got my P7P last year was definitely much better, and at least reasonably competitive. I could've potentially gotten a little more through Swappa, but not enough to be worth the trouble versus the (three times lucky in a row for me, easy trade-in process).

I don't know if you had seen, but I actually bought two iPhone 11's from Swappa to trade-in when I got our two P8Ps. Got ~$190 difference (they gave $440 each, whereas they cost about $250 each). I had looked up almost each and every phone model they were taking trade-ins on, and the iPhone 11's were about the best deal.

Really off-topic now, but it's funny how you can tell the difference when buying a used phone, between a user who loved their phone, and a mass re-etailer. The one iPhone 11 came in the original box, had not only the charging cable, which wasn't required (and I have one lightning cable anyway), and lightning headphones. The other iPhone 11 came in a very minimal, small bubble protected "envelope", and that's it. :)

Thanks! I really am very tempted to use this phone for the seven years of support it's supposed to get. Other users are of the opinion I'll keep upgrading, and they could be right, but time will tell. :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
Now that I have a spare phone, I don't mind upgrading immediately as much. Updated to November on the P8P & P7P without any hitches using the Full OTA Zip method using Platform-Tools v34.0.5.
[Google Pixel 8 Pro] Aphex13:
Same here. I updated using OTA and 34.0.5. No problems at all.

Here's the change bulletin if anyone is interested. There's not much to it this time around.

Google Pixel Update - November 2023 - Google Pixel Community
[Google Pixel 8 Pro] DanielF50:
Updated to Nov 2023 (UD1A.231105.004), flashed patched init_boot.img (Magisk Delta 26301) & all running smoothly with:

Pixel Xpert (canary-294).

Play Integrity FIx v9.9

V4A RE v0.5.0

YouTube Revanced (v18.38.44 by j-hc)

Lsposed (v1.9.2)

Pixel Mods (v1.4.0-beta)

Hide My Applist (v3.2)

No noticable issues with any of the above, or the phone as a whole over the past ~4 hours other than the pre-exisiting WhatsApp notifications issue (opening one chat dismisses all other WhatsApp chat notifications) & my Samsung Galaxy Watch5 disconnecting my Pixel Buds (WearOS4 issue?).
[Google Pixel 8 Pro] Zilla0617:
So Im stuck with bootloop on P8P. I flashed Nov ota using pixel flasher back to-back assuming that both slots were flashed. I then flashed magisk patched init_boot using pixel flasher and rebooted. When I rebooted making sure i attained root I flashed a custom kernel, when it rebooted I entered into a bootloop. I tried restoring stock kernel, restoring boot image, sideloading the ota again. All failed. Not sure what i can do to restore without losing data. My phone is bootloader unlocked. Thanks

P.S. i tried switching to "a" slot since my active is "b" but there was no os installed ( android on its back). Out of ideas...
[Google Pixel 8 Pro] roirraW "edor" ehT:
Did you disable Verity and Verification after flashing the OTA (OTAs)? As far as I know, all the custom kernels for the P8P so far require them to be disabled, although I would expect you to get a corruption message instead of a boot loop, if that's what happened.

I would flash the OTA again - follow the Full OTA Zip method steps in Post #2.
[Google Pixel 8 Pro] Zilla0617:
When i initially installed the OTA I selected disable verity and verification. Before installing the Nov ota verity and verification was already disabled. Never saw the corruption message

I tried intalling the OTA zip via pixel flasher but the phone constantly reboots itself once it reaches google.

Will flashing factory -w using flash tool help in this situation?

Edit: Using the Android flash tool worked, but lost data in the process.
[Google Pixel 8 Pro] roirraW "edor" ehT:
It's possible it will, but I have no way of telling for certain. If it doesn't help, I would try the Official Google Android Flash Tool (including checking the boxes to wipe and to disable Verity and Verification).
[Google Pixel 8 Pro] Raz0Rfail:
On my Pixel 8 (not pro) I had verity disabled in october Update and used the Despair Kernel.

After installing the november Update with the full package it enabled verity again. After trying to install the Depair Kernel the phone boot loops (fixed it by reflashing the full OTA package again).

Now I'm unsure when I disable verity again, if it will wipe my phone and I have to restore my backups, my settings etc.
[Google Pixel 8 Pro] Lughnasadh:
When you update the firmware you need to also keep verity and verification disabled, meaning during the flashing process of the new firmware you need to disable those flags before you boot into the new firmware. If you don't, the stock vbmeta image will be installed and verity and verification will be enabled. If you follow this procedure when updating you won't have to wipe.

However, since you didn't disable verity and verification when updating, you will have to wipe if you want to disable those flags again.
[Google Pixel 8 Pro] Raz0Rfail:
Crap, then I have to redo all the tasks again :D.
[Google Pixel 8 Pro] Ashray_Vk:
Folks, do you see an issue with Lightroom and the stable/stock firmware?

Im on QPR beta, and Im seeing flashing colors when editing with Lightroom mobile; and wanted to check if its the same in the stable builds too.
[Google Pixel 8 Pro] zellleonhart:
Since the November patch is released after the QPR1 beta 2.3, is it safe to assume most (if not all) the changes and fixes on QPR 2.3 are also included in November patch? Or they don't work this way?
[Google Pixel 8 Pro] roirraW "edor" ehT:
They typically don't work that way. The QPR1 Betas are in preparation for the final QPR1 that should be released next month (sorry for stating the more or less obvious), so any changes in the Betas wouldn't normally be seen until then. There should also be a QPR1 Beta 3 this month, and that Beta might likely include November's Stable fixes, so it's pretty much the opposite way around.