yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
You can use either method as you wish, both to start with, and to continue each month. However, the disadvantages of the factory image method will persist if you use that method - that only the most recently flashed slot that you used the factory image on will be bootable. If something happens to that slot, the other slot won't be bootable, but yes, at least taking or using an OTA once will get make sure a bootloader exists on the other slot, so that you'll have a way to recover if you get switched to the other (unbootable) slot for some reason.
[Google Pixel 8 Pro] in_dmand:
Ok thanks, so I think (if I'm understanding correctly) the best way would be to do the Factory Image Method and flash to both slots (so that way they both work in case something happens to one), correct? Then I can just update each month (or whenever) using the same method?

I got the issues sorted out and am now rooted on slot 'b'... quick question though, can I simply switch from slot b to slot a on the fly using

fastboot --set-active=other

and basically run two different 'systems'? after I flashed the factory image on both slots it only seems to want to allow me to boot into the last active slot which is why I'm wondering.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Incorrect. That's the issue with the factory image. Only the most recently flashed slot with the factory image will be able to boot. If you switch slots after you flash the factory image, you'll find the new slot won't actually work.

That's why the Full OTA Zip method is what I've been using for over six months. It's up to you whether you flash it to both slots, but it makes sense, because both slots use the same user data, so if you're using the latest updated slot and then have to switch to the old slot for some reason, it may not work correctly, or possibly even boot fully, because the system will still be using the user data that the new firmware was using.

That's why it makes sense to do the Full OTA Zip method twice - each time it will switch slots on its own.

Not if you used the factory image instead of the Full OTA Zip, since only the most recently flashed slot (with the factory image) will work. If you use the Full OTA Zip twice, then you can switch slots at will with that command.

And no, not really regarding two different systems, since they'll both be using the exact same user data as each other.

You can have one rooted and one not-rooted, if you choose, although just having an unlocked bootloader will still be enough for some apps to detect and not work correctly, too. But it may help with some apps, if you have any like that.

If you used the Full OTA Zip method twice, then yes, you can switch slots at will at least, but they can't be really different other than you can have one rooted and one not, if it helps.
[Google Pixel 8 Pro] Chickenkillla81:
Ok. I found more on the DSU loader thing I was talking about before. Right here

Dynamic System Updates (DSU) | Platform | Android Developers

Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.

developer.android.com

It says google uses that since Android 10. And it doesn't say it needs unlocked bootloader just that it must be signed by Google. I'm not sure what that means or if there is a way to sign an image?? It says that it carves out some of the memory to boot into the gsi using that method. You can make it sticky so that it can be used for a longer period. If you don't then it will automatically boot back to original OS erasing the temp partition.

I know, I know, I'm grasping at straws here. 😂. And on the other. My battery did really well today. 84% since 515am, but if course that was only an hour and 15 minutes SOT. that is just about what I was getting before turning off adaptive battery. I'm 😊
[Google Pixel 8 Pro] in_dmand:
ok thanks so much for the very helpful advise!!

So basically I flashed the latest verizon factory image (I'm on an unlocked pixel 8 directly from the google store) then patched the boot.img file and rooted that way.

When I go to update to next month's build, can I just do the full OTA zip method then?

Under step 8 where I would run:

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

that husky...ota.zip would just be the latest OTA direct from google correct?

Thanks again for all your help
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm definitely not knowledgeable about DSUs and GSIs, so I rely only on what information I search for.

For what it's worth, you might (temporarily) lose a lot of the advantages of using a Pixel while not running the full Pixel firmware.

My fingerprint reader has still been hit-and-miss today with the adaptive battery disabled, but I've probably been on my phone less, so I might leave it for another day or two and see how it does. I think it still might come down to how often I'm washing my hands, and therefore the dryness or oilyness of my fingers. When it doesn't successfully read my fingerprints, it does so three times in a row, and when it does work, it works the first time.

I'll update you in another day or two.

Be sure to distinguish between the init_boot.img, which is needed to run Magisk on in order to be rooted, and flash that to the init_boot partition, rather than the boot.img to the boot partition - which we only have to fool with while using custom kernels, and also when we accidentally trigger a "corruption" issue, which involves flashing any older boot.img, attempting to boot (which will then fail), and then re-flashing the correct current boot.img.

Yes, exactly, and you can do so at any time (now, next month, ...) - of course, you'd have to reflash the Magisk'd init_boot.img each time you flash the Full OTA Zip (for each slot you want to be rooted).

You're welcome!
[Google Pixel 8 Pro] radionerd:
This fixed my laggy p8p too! Thanks!!!
[Google Pixel 8 Pro] Chickenkillla81:
Your welcome. 😁😁
[Google Pixel 8 Pro] in_dmand:
I got an unlocked pixel 8 directly from google and flashed the factory image for it 14.0.0 (UQ1A.231205.015.A1, Dec 2023, Verizon).

I'm having an issue with RCS texts, should I have went with the non-verizon version? I'm wondering if this may be causing the issue. My phone updated to the latest version (UQ1A.231205.015 which is non-verizon) just prior to me flashing the factory image.

(note I am using a verizon network/sim)
[Google Pixel 8 Pro] Chickenkillla81:
Have you checked to make sure there aren't any updates to Google messages in the play store? I'm assuming that's what you're using?
[Google Pixel 8 Pro] in_dmand:
yeah I tried all the things recommended on google support forums and a reddit thread I found but nothing seems to be working.

yep, using messages and yes I made sure it's updated. I even cancelled my messages beta testing part of the app and went back to the public version.

*edit: I FINALLY figured it out, I had to uninstall the latest update from the play store to the messages app... apparently it caused issues and was messing up RCS
[Google Pixel 8 Pro] Chickenkillla81:
Really? That's weird. Although I was having a problem sending a picture using messages earlier today. The person on iPhone got it just fine but the other on Samsung phone didn't get it. I'm doubting it's related but maybe I'll try that. Ya never know. I'm on the beta at the moment as well. Could be a fly in the soup. Get it....a bug! 😂😂
[Google Pixel 8 Pro] in_dmand:
well the RCS is more than sending a pic, it has to do with sending high quality pics and even files. It also allows you to see when the other person (who has it enabled) is typing and know when messages have been sent vs delivered. :)
[Google Pixel 8 Pro] Chickenkillla81:
Ahh. I did not know that. That's why I see the little dots when they are typing. Supposedly iPhones will be compatible with that this year
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android Security Bulletin—January 2024 | Android Open Source Project

source.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Pixel Update - Jan 2024 - Google Pixel Community
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hot off the press!

Both Global and for those on Verizon or Verizon MVNO carrier firmwares released:

https://developers.google.com/android/images#husky

https://developers.google.com/android/ota#husky

https://support.google.com/pixelphone/community?hl=en

https://source.android.com/docs/security/bulletin/asb-overview
[Google Pixel 8 Pro] roirraW "edor" ehT:
Does anyone think that the seven years of updates for the Pixel 8 Pro (always assumed monthly, but we'll see) will force Google to finally update their firmware and OTA Zip pages to not make it such a chore to accurately get to the most recent update when there'll be more than the usual 24 or 36 update releases, not counting those months with multiple packages for different carriers?

Not to mention if all or most devices from now on end up with seven years of updates after the 8 Pro.

I used to always for my own purposes follow the link to the next device on the list and then scroll up, but I've mistakenly downloaded the wrong device's firmware that way when I forget that I should scroll up instead of down. :)

Of course, be careful what I wish for. Next thing you know, they'll make it more difficult to tell if there's any new firmware releases (such as always collapsing entries of all devices on a page refresh). So it might force them to change things, but won't necessarily mean they'll change things smartly.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Awesome. I guess I lied, I couldn't fall asleep yet. I'll add your post to the OP.

Effectively, just like on the Pixel 7 Pro.

Magisk Stable v26.3? Platform-Tools which version?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Pixel phones are getting a bunch of funky new ringtones

Custom ringtones: still very much around.

www.theverge.com
[Google Pixel 8 Pro] gpvecchi:
Well, there are different factory images on Google website
[Google Pixel 8 Pro] Paz9:
Yes sure effectively the same latest stable 26.3
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes, but only one for October (the latest update).

Thanks! Do you know if you were using Platform-Tools v33.0.3 or 34.0.4?

I just want to make sure I report accurately.
[Google Pixel 8 Pro] Paz9:
I used the flash tool since the platform tools was having issues back in 31xx iirc

Im still on an old version only to fastboot flash init_boot
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks again very much!
[Google Pixel 8 Pro] Paz9:
First thing I noticed is that the camera allows you to shoot in 50mp haven't done much testing but it seems to produce better photos
[Google Pixel 8 Pro] Annie the Eagle:
Mine is arriving in a few hours! I assume 33.0.3 will still work as before then?

λ fastboot --version

fastboot version 33.0.3-8952118

Installed as C:\Utilities\adb\fastboot.exe

Can we use PixelFlasher for this? Or should we do it more manually (extract init_boot.img, patch on device with Magisk 26.3 and then flash using fastboot flash
[Google Pixel 8 Pro] roirraW "edor" ehT:
Unknown, but I think it's likely yes, we can use 33.0.3.

You would have to ask @badabing2003, either here or in one of his PixelFlasher support threads. I don't think he has one for the Pixel 8 Pro yet, since he likely doesn't have the phone yet, or might need other users to help him beta test it for the 8/Pro, or he might have the phone but just hasn't had enough time yet to make sure all works as it should on it when used with PixelFlasher.

Edit: See his reply two posts below this one.

It's your preference. I like doing the steps manually.
[Google Pixel 8 Pro] Annie the Eagle:
Okay, so in summary, when I get the phone, I should:

1) Set up the phone minimally

2) Unlock the bootloader (resets the phone anyway)

3) Fully set up the phone

4) Use Android Flash Tool to update to October 2023 Image

5) Extract init_boot.img from the factory image and patch on device using Magisk 26.3 APK

6) Flash to phone using "fastboot flash init_boot magisk_patched.img"

7) Install Displax Modded SafetyNet Fix 1.3 Module

Does that sound like a sensible list of steps?
[Google Pixel 8 Pro] badabing2003:
Correct, I don't have the phone, but seeing the firmware being available, being able to properly process in PF and manual steps not having changed, I'm confident it will work.

A while back it was coded in a way to detect and properly choose init_boot / boot.

Unless something changes in the manual steps, it should be forward compatible just like the guides.

I added support threads in each of Pixel 8, and Pixel 8 Pro

Thanks for the mention.
[Google Pixel 8 Pro] roirraW "edor" ehT:
That will work.

Thanks, @badabing2003!
[Google Pixel 8 Pro] bsg411:
Let us know how it goes!
[Google Pixel 8 Pro] roirraW "edor" ehT:
He did! :)
[Google Pixel 8 Pro] Paz9:
Should always patch it on the device you are going to flash it on

I remember it was discussed that magisk may use information from the device to patch the image
[Google Pixel 8 Pro] Annie the Eagle:
Yes, I will do that :) Should be arriving very soon!
[Google Pixel 8 Pro] JasDevi:
Still waiting eagerly for @Freak07 kernel to be out!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Disregard. It would happen that I actually quickly adopted the new version for once, and the developer of AOSPMods says that the new LSPosed breaks some things so avoid updating for now.

New LSPosed version at the GitHub link. Mentions a crash with Android 14.

LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module

Developers: LSPosed Developers Homepage: GitHub ✱ Requirements: • Magisk 21+ • Android 8.1-13 • Riru(NOT NEEDED) USE ZYGISK Description: Riru module providing ART interception framework (natively for Android Pie) that provides consistent API...

xdaforums.com
[Google Pixel 8 Pro] bsg411:
I notice the factory images for the P8Pro is up but it doesn't show the full version number. It only shows 14.0.0 (, Oct 2023 ). Maybe a typo?? Nor does it have different carrier versions for the October image like it does for September images. Do you guys think more images are coming later for different carriers? I have T-Mobile.
[Google Pixel 8 Pro] Ghisy:
They should have a drop down menu with all the devices and selecting one takes you to a page with only firmwares or OTAs for this device, sorted by years.

But knowing Google, it'll probably stay the way it is now for a while. 🙃
[Google Pixel 8 Pro] roirraW "edor" ehT:
That makes sense to me. And hopefully have a different URL for each device at the resulting page.
[Google Pixel 8 Pro] Morgrain:
Well that's a bit of a disappointment, was hoping for some fixes improving HDR whites in photos and better battery life/ more on device handling of the new p8 pro features
[Google Pixel 8 Pro] HipKat:
This is the link that goes right to the P8P OTA Images

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

developers.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Right, but the page doesn't only contain P8P OTA images, the link just takes you to the top of the P8P section on the same page as all the other devices. It contains all the other Pixel/Nexus device OTA images as well, and when there approaches 24 or 36 out of the 84+ monthly images the P8P will get, it's a lot of scrolling to go from the P8P label to the actual latest update(s) at the bottom of the section, and if you scroll too fast, it's easy to get into another device's OTAs by accident. It's just inelegant, and I wish they'd at least put them in reverse chronological order, but I like @Ghisy's suggestion, as long as each separate device had its own dedicated page.

I know it's not really that big a deal, but it also wouldn't be hard for them to improve it. They just likely have no interest in doing so. :)
[Google Pixel 8 Pro] HipKat:
Yeah it looks that way.

I'm glad there is a way to at least get to the right section/device with one click/bookmark
[Google Pixel 8 Pro] roirraW "edor" ehT:
Oh, definitely! :)
[Google Pixel 8 Pro] Chickenkillla81:
we're there any cool updates or mainly just the security ones I read about?

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
I know there were supposed to be a couple of camera fixes, but no, as far as I know no big deal things. Probably have to wait until the next QPR Stable in March.
[Google Pixel 8 Pro] vegetaleb:
Unlocking the bootloader will erase my esim? If yes should I delete it before unlocking the bootloader?
[Google Pixel 8 Pro] HipKat:
THis update was just to repair several bugs. None that I've seen anyone post about on here, so its pretty minor
[Google Pixel 8 Pro] Chickenkillla81:
I was just wondering because when I looked at my phone this morning when I got up. the battery said I have 1 day and 4 hours charge left. it normally says like 11pm so like 18 hours. today it said 28!! that's a huge difference. and I have adaptive battery turned off so it isn't learning from my usage anymore. dang Google wanting to know how I use my apps. big brother! 😂 jk

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
No, unlocking the bootloader wipes all user data on the device. It does not affect physical or eSIMs. Always be prepared for the worst case possibilities, however. :)

Edit: It's the same as performing a manual factory reset on the phone, as that's what unlocking (or re-locking) the bootloader does - factory reset.
[Google Pixel 8 Pro] vegetaleb:
So logically it won't throw my esim into the limbs of a parallel universe, but for extreme safety it's better to delete it from the phone's settings and scan it back once the unlocking is done ?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I really can't advise on eSIM personally as I have yet to deal with them. If it were me, I probably wouldn't bother deleting the eSIM, but it's ultimately up to you. Just the usual caveat that sometimes things happen.

It's the same as performing a manual factory reset on the phone, as that's what unlocking (or re-locking) the bootloader does - factory reset.
[Google Pixel 8 Pro] Chickenkillla81:
man. I'm trying that video boost for the first time. it takes forever!

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
I've used it a couple of times. It'll notify you when it's ready. The last time, I forgot I was even waiting for it. :D
[Google Pixel 8 Pro] Chickenkillla81:
exactly! I thought it was my video being ready and it was you answering telling me to wait! damnit! 😂 😂

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] vegetaleb:
Sorry for my noob question but I didn't root a phone for the last 3 years

What are the advantages and negatives of flashing init.boot to both slots instead of 1?
[Google Pixel 8 Pro] roirraW "edor" ehT:
If something happens to the one slot where it won't boot, the other slot is already rooted as well, assuming you mean the Magisk-rooted init_boot.img.
[Google Pixel 8 Pro] vegetaleb:
Yep

I was reading the tutorial in 1st page , so it's better to have both slots rooted right?
[Google Pixel 8 Pro] roirraW "edor" ehT:
To me, it is. Others might have different reasons as to not root the other slot: if there's a particularly finicky app that detects root no matter what and will only work without it - as long as that app doesn't also detect your unlocked bootloader and not work because of that. In some cases, with an unlocked bootloader, more apps that detect root will work as long as root-based solutions are installed to help with that sort of thing, than on a not rooted (but still bootloader unlocked) device, but there are exceptions for everything.
[Google Pixel 8 Pro] BillGoss:
But that's only true if you've also flashed all the inactive a/b partitions with the current software.

You have to go out of your way to have both slots running the same firmware.

The a/b design was implemented to minimize down time when updating by allowing the inactive partitions to be updated while the current partitions are active. It was never designed for running two different firmware versions.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Correct. That's what the Full OTA Zip instructions in post 2 detail, updating both slots fully, and is where I mentioned the possibility of flashing the rooted init_boot.img, so I expected that the person asking about it was already aware about flashing the full firmware to both slots as well.

Edit: "...and is where I mentioned the possibility of flashing the rooted init_boot.img to each slot"
[Google Pixel 8 Pro] vegetaleb:
And in case the Pixel is already updated to latest FW prior rooting , I still have to do this step or it's for future FW updates after rooting?

Pixelflasher has a different way of rooting the P8P?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Which step, exactly?

If you're using the Full OTA Zip method, then the moment you tell it to sideload the OTA, it'll be flashing the "other" slot than what you were previously on - which probably wouldn't be updated, and historically hasn't had anything flashed to it yet - even a bootloader, but that's a tangent to the subject.

Then, since the slot you used to be on was already updated, if you're confident enough, then you can just switch slots (back to it) and flash the rooted init_boot.img if you choose to, then both slots should be updated and rooted.

No, PixelFlasher uses the same methods as far as I'm aware, but that would be a question for @badabing2003.
[Google Pixel 8 Pro] badabing2003:
No, Pixelflasher uses fastboot command to flash a patched boot / init_boot just like in the guides.

It does so prior to rebooting to system to make sure that you don't lose root.

When flashing OTA it also makes sure that the slot switched properly indicating that OTA flashing was successful, to avoid undesired flashing of a patched boot / init_boot (which could be for the newer version) on current slot if slot did not switch.
[Google Pixel 8 Pro] vegetaleb:
So if I don't want to go to the hassle of manual method which is in this thread , I can simply use pixelflasher to root for the 1st time , no?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I can answer that. :D Yes.
[Google Pixel 8 Pro] vegetaleb:
Hahahaha

But it's good to read your tutorial just for info too
[Google Pixel 8 Pro] badabing2003:
Absolutely, the tool is based on information gathered from such great guides, and I always encourage users to learn the manual steps, that is priceless, and when you're comfortable with the steps and what it takes to get from point A to point B, then use tools to ease your life and automate it for you if you so desire.

If you decide to use, turn on debug logging and look at the messages that scroll in the console, it's good learning tool to see what operations and commands it is executing, and you can correlate those to the guide steps.

Understand the steps gets you out of a jam when things go wrong, and they do go wrong at times, it's the nature of modding (manual or automated).
[Google Pixel 8 Pro] Chickenkillla81:
personally I always enjoy the manual steps. it makes it fun. and like badabing said it helps to know what's happening so that you can pull your device out of a loop or some other catastrophe that the automated methods don't or can't help with. not that anyone asked. I'm just bored and thought I'd put in my two cents. 😂

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
Ironically, I used PixelFlasher after I was getting constant SystemUI FC's (Force Closes) to fix my issue (uninstall a new release of a Xposed module). I'm sure I technically could've done it with command line tools, and that's what PixelFlasher was doing under the hood, but it would've taken a bit of research including figuring out what the Xposed module's package was called in order to uninstall it manually, but PixelFlasher made several aspects of my journey back to a useable (while still rooted) phone easy.

To be fair... :) All tools available definitely have their uses, and PixelFlasher does have some really nice features when you need them.

But yeah, I like to do manually quite a lot, too.