yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] Lughnasadh:
Yep, you should be all set. What I also like to do is grant root access to adb. Will help if you need to remove Magisk mods or the like:

adb shell
su

Accept superuser request in Magisk

Type "exit" twice to exit

Yep.

fastboot flash init_boot <nameofpatchedinit_bootimage>

Is this what you are talking about? If so, recommended but not required.

If you are talking about flashing the factory image to both slots instead, also recommended since with new phones the inactive slot may be empty, but also not required.

👍

EDIT: You probably already know this, but just in case...

If you are on Windows, Platform Tools 34.0.4 should work fine for flashing stuff, but it won't wipe if you flash the factory image with the -w still intact. If you want to wipe while flashing a factory image it's best to use 33.0.3.

If on a Mac, you should use 34.0.4 as Macs have trouble with 33.0.3 (fastbootd troubles) . 34.0.4 doesn't use fastbootd when flashing a factory image so that's why it avoids the fastbootd problems of 33.0.3.
[Google Pixel 8 Pro] Az Biker:
Thanks very much for the quick reply! I started re-reading the thread and saw the SDK/windows question was already answered by you started your reply before I erased that question.

For clarification, did you flash to both slots?

Thanks again!
[Google Pixel 8 Pro] bsg411:
I'm kinda curious if ppl are flashing 1 or both slots as well
[Google Pixel 8 Pro] Lughnasadh:
When I first got the phone I did flash to both slots, via flashing the factory images.

I don't do the "Sideload OTA Twice" method because the OTAs contain updated system apps and I'm using ReVanced YouTube & Music Magisk mods so I need to make sure those ReVanced app versions are equal to or higher than the system app versions or I'll have to downgrade, etc., and it's just more work, lol. I actually had this happen once after sideloading the Full OTA, but have never had that happen after flashing a factory image.

But if it wasn't for that I would sideload the Full OTAs twice every monthly update. Puts you in a safer place, in my opinion, in case something goes wrong. Plus sideloading the Full OTA is probably the safest method since it puts the new firmware on your inactive slot and if something goes wrong during the update process and you can't boot it will revert to your current slot, which is already known to be bootable.
[Google Pixel 8 Pro] Pixel86:
I don't and never have as I usually root my phones, and as such, disable AUTOMATIC UPDATES.
[Google Pixel 8 Pro] simplepinoi177:
Just a reminder to you @Az Biker and all other members,

if you edit a post and mention/ping in that edit (after the initial reply/post), the mentions/pings do not alert those you are trying to grab attention (I just so happen to be subscribed to this thread and was checking out the new posts).

As it seems @Lughnasadh answered all your questions, I will refrain from answering as well. But there is supplemental info I'd like to include (which I will input below)...

From what I've learned from @badabing2003, after some extensive research/figuring, he figured that flashing Full OTA to both slots doesn't employ the "system_other" in quite the same way and mark the slot inactive (like it does with Full Factory Images) (source), so by flashing the Full OTA to both slots, you'll effectively have two bootable slots. With Full Factory flashing, even to both slots, as one is flashed, it causes the other slot to become unbootable; whereas flashing Full OTA to both "...is mainly for having both slots bootable in case something goes wrong and you want to have functional system without having to flash something immediately."(source)

But if you do not care to have both slots bootable, alternating between slots when flashing Full Factory images has its benefits (source) (supplemental source)

Normally when a Pixel is rooted (I'd say all other devices as it's probably an AndroidOS thing, but I'm not 100% sure), whether you disable automatic updates or not, you wouldn't (or at least shouldn't, there have been some rare cases where it sometimes happens) be capable/able to update through the stock system's System Updater in either case. If anything, that might keep one from getting an update notification; but if one was to try, the update process would fail in the end.

I'm unsure if this is true for the Pixel 8/Pixel 8 Pro, but if it is that much similar with Pixel 7's, you all should be sure to flash to BOTH slots at least once (unless you took an OTA at least once)!!!

Unless you flashed it to your other, inactive slot or have taken an OTA, the 2nd slot ships w/o an installed system, and if your active ever becomes corrupted for some reason and you try to switch slots, it's not set up to work....
[Google Pixel 8 Pro] Pfeffernuss:
It sure does :love:
[Google Pixel 8 Pro] Az Biker:
@simplepinoi177

Thanks for the thorough response. Prior to getting your reply, I flashed to factory image to both slots ( have never flashed an OTA before, only factory images ). Unless you recommend I do something different, I'll leave it as is 😁
[Google Pixel 8 Pro] bsg411:
Shi the nac bar goes away?? That image looks edited. Looks like an iPhone with no camera...
[Google Pixel 8 Pro] Pfeffernuss:
Yes...

Or, in a frame again:
[Google Pixel 8 Pro] jhjhjhjhjhjh:
Anyone know if the firmware that's the very last one in the downloads section with build number UD1A.230803.041, is the global unlocked version???

Edit just got it yep unlocked version..
[Google Pixel 8 Pro] Lughnasadh:
A correction has been posted... 😔

https://twitter.com/i/web/status/1714687979233427816
[Google Pixel 8 Pro] A.Priori:
Someone should do a clear, non-rehashed, post about updating OTA and retaining root and settings etc. It would help!
[Google Pixel 8 Pro] Gilg@mesh:
yeah haha
[Google Pixel 8 Pro] ApeironTsuka:
I was just coming to ask about this lol

Is the current version of Magisk aware of init_boot and to patch that instead of boot itself, when installing via the app?

I remember older Android/phone method (thinking back to Pixel 3a XL, Android 10 era) was...

1. Use Magisk app to restore original boot image (or manually flash it via PC if required)

2. Install OTA via Android's own updater. Should pass sanity checks because of the previous step

3. Do NOT reboot at the end

4. Disable any Magisk modules you think might cause issues

5. Install via Magisk app to OTA slot

6. Reboot after that, via Magisk's prompt

7. Update/re-enable what you may have disabled during step 4

If the app knows to install to init_boot (or can be told to), then I would expect these steps to still work with the Pixel 8/Pro.
[Google Pixel 8 Pro] Pain-N-Panic:
I love XDA so much. Just got my P8 Pro and there's already a ridiculously detailed how-to guide on the process of unlocking and rooting the phone. Even though I consider myself a veteran in bootloader unlocking, rooting, modding etc, I always visit the forums to see if anything has changed. XDA has never failed. As with the P7 Pro, Edor, thanks for the awesome write up, literally is going to save hundreds of users from bricking their phones lol.
[Google Pixel 8 Pro] simplepinoi177:
As it was with the Pixel 7 Pro, there is no way to update with OTA and retain root. That's most likely why there's no "clear, non rehashed, post" with directions for it.

The above method only works (on Pixels) to the up to the Pixel 6. It has something to do with the change to init_boot and topjohnwu either not having the time or willingness to make the necessary changes for Magisk to accomplish the "Install to Inactive Slot" option like before -- even if it seems he either updated it so it saves the original init_boot and/or his protocol still applies & works the same as patching the boot.img, just Magisk now has an issue with unpatching and directing the "Install to Inactive Slot". In the early days of Pixel 7, there was some success with the "Install to Inactive Slot" process, but many/most of the times it would cause a soft-brick bootloop that most simply stopped -- to the point that even Homeboy76 established How-To Guide strikesout the steps/directions to do it.

The closest (at least from the Pixel 7 onward) we have for retaining root after updating is using PixelFlasher to immediately re-root which automates it before the OS even loads so that it's very seamless (both in user experience and making sure you don't go unrooted for a temporary time being).
[Google Pixel 8 Pro] aHcVolle:
Hey guys,

I'm cross posting from the magisk general support thread (https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2868) since this thread might be the better place to get help / find a solution for my problem.

What i might have to add: after the first boot with magisk and running the app magisk ask me to reboot since it has to do some changes. This reboot (zygisk still disabled) works fine.
[Google Pixel 8 Pro] move_some:
I would want to know that too.

Anyone who knows this?
[Google Pixel 8 Pro] Gilg@mesh:
you got to give it to Samsung, without root and stuff but still able to do so much more with the UI, Google needs to step up big time and at least offer something similar like Good Lock. :)
[Google Pixel 8 Pro] move_some:
I have read that this is possible with Samsung phones using good lock.

As a Pixel is no Samsung (as far as I understood) good lock is not working.

Is it possible to get vertical recent apps using root and quick switch and another launcher?

Getting vertical recent apps would be the main point for me to root my Pixel.
[Google Pixel 8 Pro] ThatOneGuyOverThere:
Does anyone know what modules/settings are needed to pass all checks in AppList Detector? I cant seem to hide magisk and xposed modules, all other checks pass though.
[Google Pixel 8 Pro] simplepinoi177:
Have you tried completely uninstall Magisk (to the point of removing relevant folders in /data/adb) and reinstalling? And/or make sure you're not running other instances of Magisk (you'd be surprised how many times this is overlooked) -- as I understand it, you can find them in TB Checker.

Just a couple of ideas...sorry if they are obvious to you and/or you have done them

I'm able to this by doing the Hide Magisk (where it renames the package name), then you gotta make sure in HideMyApp the template includes both Magisk and each and every xposed module -- on top of choosing AppList Detector under "enable module" in the app's LSPosed settings (this is for LSPosed, I don't know how Xposed does this) -- and then also apply it to AppList Detector as well.

Hope you're just as successful with this as I am and good luck to you!
[Google Pixel 8 Pro] aHcVolle:
yes, unfortunately I've tried this and it didn't work. I'm not quite sure if anyone running grapheneos has zygisk running already... maybe this is a "common" problem for a totally uncommon setup....
[Google Pixel 8 Pro] ApeironTsuka:
Ahhh, I see. Thank you. I had suspected that maybe Magisk hadn't been updated to handle init_boot entirely (yet?). I'm not as up-to-date with hardware/Android releases enough anymore to know if the switch to init_boot is a device-shipped-with Android 13+ sort of thing, or a weird choice with Pixels specifically, so wasn't sure if there was any upstream interest in supporting it.

If only I knew more Java... maybe I'll try to find the time to look at how the process works.
[Google Pixel 8 Pro] snovvman:
Is anyone running rooted on QPR1b2? Is it the same procedure? Thanks.
[Google Pixel 8 Pro] Lughnasadh:
I am and yes it is.
[Google Pixel 8 Pro] snovvman:
Thank you! Any noticeable difference between the Oct release and QPR1?

I am seeing some Bluetooth issues with the Oct release and my Garmin watch, as well as with Pixel Buds Pro, which is why I am considering QPR. I saw nothing in the release notes, but here is to hoping.

Edit: it looks like they are on QPRb2.1 now, released on 10/19
[Google Pixel 8 Pro] Lughnasadh:
Haven't really noticed much difference but I didn't stay on stable for long. Flashed the QPR1 beta as soon as it was released.

By the way, A14 QPR1 Beta 2.1 hasn't been released for the Pixel 8 series yet. Will be released at a later date, according to Google.
[Google Pixel 8 Pro] dying4004:
whats the benefit of rooting pixel 8 pro? thnx
[Google Pixel 8 Pro] snovvman:
Uhhh.... really? You've been around for some time and have plenty of posts so your question is a head scratcher. Maybe start by reading this thread found in this forum. That thread is probably a better place to ask this question anyway.
[Google Pixel 8 Pro] Jose.pH:
Heyla! before making a mess, I have this update, but I have root and magisk with different modules activated, can you help me to update safely and apply everything again? (I use Pixelflasher)
[Google Pixel 8 Pro] dying4004:
Haha.

I mean before we used to root to flash modified rooms to debloat htc softwares, or more customized roms, roms with more performance or aosp roms or even installing custom icons. But these days pixel roms are fast and have performance and don't have much stuffs that need to be debloated.

That's why I was wondering exactly what people root pixel devices for.
[Google Pixel 8 Pro] Gilg@mesh:
is it possible to lock some of the recent apps so they don't get removed when I choose delete all?
[Google Pixel 8 Pro] LLStarks:
I went back to Magisk alpha and Shamiko. Other solutions stopped working for Hyundai Digital Key.
[Google Pixel 8 Pro] stu5797:
What was the Hyundai Digital key saying when it wasnt working?
[Google Pixel 8 Pro] LLStarks:
It wouldn't allow rooted devices. Really not sure what it was detecting when my banking apps didn't care.
[Google Pixel 8 Pro] Gilg@mesh:
so there is no way to remove the Google search on the home screen and put the apps down there instead? I did try third party launchers but losing the swipe smoothness sucks, wtf Google how can they not offer simple customization for the home screen? learn from Samsung ffs.

I got hiding apps,hiding at glance working at least...and I can hide the search box but can't put the apps there, so it does not look very good but what can you do.

GitHub - KieronQuinn/PixelLauncherMods: A root app that enables you to add a number of features to the stock Pixel Launcher, without needing Xposed

A root app that enables you to add a number of features to the stock Pixel Launcher, without needing Xposed - KieronQuinn/PixelLauncherMods

github.com
[Google Pixel 8 Pro] snovvman:
Pixel is the poster child for root lol. Have a look at the Pixel 7 and 6 forums and look for root-related threads. That should give you an idea. To me, root was never just about performance, it was about having your way with your phone :)
[Google Pixel 8 Pro] stu5797:
If I use Magisk Delta do I need to also install "universal safety net fix" ?
[Google Pixel 8 Pro] simplepinoi177:
if you are rooted and/or employ different modules, even if you were to go ahead with the "installation", it might download, but in the end it would just fail -- because you're rooted; have a modified init_boot partition.

As you use PixeFlasher, you can easily use that to "update safely and apply everything again"; it's how many many Pixel users update monthly to start with.

If, for some reason (it has happened in rare cases), the stock system System Updater OTA updates, you will lose root, but you can easily use PixeFlasher to re-root right after -- in the all the cases I've seen it brought up and discussed, nothing much comes from it (no loss or data or settings) other than just no longer having root access; which once flashing the patched image is applied is corrected.

Hope this helps!
[Google Pixel 8 Pro] Jose.pH:
so if I disable all modules and try to download the beta it fails?
[Google Pixel 8 Pro] simplepinoi177:
Yes. It's not having or employing modules that is stopping OTA's, it's being rooted. Supposedly, if you unroot, you would be able to download it and install it that way.

But wait...."beta"....? You state before

an OTA update is different than a QPR beta, I had assumed you were speaking on an OTA update because you shouldn't be alerted for QPR beta updates....

In any case, whether OTA or QPR beta updates, as you have used PixelFlasher previously, using that program will help you update it in either case -- and just as long as you do not select "wipe" or "clear data" (I'm unsure what iteration badabing2003 uses in the program; I flash manually), no files or settings will be effected.

*I've never installed a QPR beta version, so if I am incorrect in any of my assumptions (not getting alerts for QPR beta newer versions, can't install it if rooted, etc.), I hope other members feel free to correct me...
[Google Pixel 8 Pro] Lughnasadh:
You do get OTA updates when on QPR betas, assuming you enrolled in the beta program and didn't just flash the QPR beta build. No different than OTA updates when on stable builds.
[Google Pixel 8 Pro] simplepinoi177:
Hmmmm good to know....I forget normal locked bootloader users are enrolled into it -- makes sense that you would be able to get update notifications -- it's such a rather advanced (at least more advanced than the average user would be interested in) thing that in my head I mistakenly think one must have to manually flash to work it....Thanks for the clarification...

But towards what I was responding to, if it is "no different than OTA updates when on stable builds", then it can be assumed that the update (even for betas) would

not

work when rooted, correct?
[Google Pixel 8 Pro] Lughnasadh:
Well, it is true that way back when OTA updates would fail if rooted due to the pre-OTA block verifications. However, It is true now that Magisk does not modify most read-only partitions so in many cases it may not be flagged by the pre-OTA block verification checks.

I've seen several examples in the recent past where people have been rooted and got an OTA update which was successfully installed. Of course, they lost root afterward.

There are modifications that would prevent having a successfully OTA update, such as using a custom kernel.
[Google Pixel 8 Pro] Az Biker:
Does your Hyundai app work? Have you added the Hyundai app to Magisk's deny list and hidden Magisk?

The Hyundai app (remote start, unlock, etc.) detected root and wouldn't open until I added it to the deny list in Magisk and hid Magisk. Then it worked perfectly although I never tried to configure my digital key.
[Google Pixel 8 Pro] stu5797:
I wonder if the digital key detected root. My BMW app works fine if I want to lock or unlock the car but my BMW digital key will not pair with my pixel 8 pro. I've tried a million times but it keeps saying "can't pair"
[Google Pixel 8 Pro] LLStarks:
It only needed to be in the deny list. But I want to reevaluate my whole setup because now I'm losing GPay, which usually just works.
[Google Pixel 8 Pro] Jose.pH:
so basically I could try to update to a QPR without risk and obviously I would lose the root, then when a stable version comes out can I use PixelFlasher again to put it back? or I'm waiting for a stable OTA to flash with Pixelflasher... more than anything I wanted to understand how they solved the slowness of fingerprint authentication, but maybe I'd better wait...
[Google Pixel 8 Pro] Gordietm:
I just noticed at SDK Platform Tools has been upgraded to 34.0.5.

It still shows as 34.0.4 on the release notes, but 34.0.5 when downloaded. I haven't tried it yet.
[Google Pixel 8 Pro] Lughnasadh:
If you update to a QPR beta build and then want to go back to stable you'll likely have to wipe for things to run correctly, unless you wait for the stable QPR1 build in December.

The safest way to update is to sideload the Full OTA, either through Pixel Flasher or adb commands. Updating through a normal delta OTA while rooted could produce positive results but that's not the recommended way to update.
[Google Pixel 8 Pro] Jose.pH:
yes I wait for stable... thx
[Google Pixel 8 Pro] THEONEV12:
iPhone 11 64gb is worth $440 😂
[Google Pixel 8 Pro] LLStarks:
This was at my local AT&T store. I'm surprised they had it. Wasn't even on display yet. Obviously couldn't buy it.
[Google Pixel 8 Pro] rester555:
Did you have to ask if they had any units to look at?

I went to my local Verizon and they don't have it out yet. They stated they would have a display unit tomorrow. I am heading to AT&t right now
[Google Pixel 8 Pro] LLStarks:
I called ahead. I thought they had a display unit but they just pulled it out of the back and unboxed it.

For T-Mobile, I wouldn't expect any display units until Friday at the very earliest. Best Buy could vary wildly by location.
[Google Pixel 8 Pro] rester555:
Seriously, the pixel phones are not worth anything compared to the Almighty Apple.

I haven't been so lucky. The manager at the store I went to said they could not bring out a unit for display because they had no direction to do it yet.

Update: anyone that actually has units in the back room is not coughing them up in my local area, unfortunately. Verizon is the only one that gave a day to put out display units and that is tomorrow.
[Google Pixel 8 Pro] Utini:
I am desperate. So I pre-ordered.

And I am even more desperate. So I am refreshing @Freak07 's github every few minutes to see if anything new comes up that might promise his magically doings on the P8P.
[Google Pixel 8 Pro] rester555:
You mean a kernel build with @Freak07 on the P8P?
[Google Pixel 8 Pro] Utini:
Exactly :)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Note: I ordered the Pixel 8 Pro for my wife and I.
[Google Pixel 8 Pro] rester555:
I am going to see the phone at Verizon today.
[Google Pixel 8 Pro] simplepinoi177:
And the Pixel 5 would've been 2 models behind the P7P! And there was no "Pro" version of the Pixel 5 (or I would've gotten it)....and that comes up to just $20 less than a P7P for a P8P?!?!?!?!? For Google and all their Silicon Valley tech capital; that math doesn't make sense....
[Google Pixel 8 Pro] AmyClaraRose:
ive just now its shown on my network (Three UK) pre ordered my pixel 8 pro
[Google Pixel 8 Pro] Morgrain:
It's quite obvious at this point, I think, that Google doesn't really care about previous high-end Pixel owners. Google believes those customers to already be "stuck" inside the Google-verse and that those will not need high incentives to buy the latest and greatest.

Google wants to convince Samsung and Apple customers to switch, and that's why those incentives are much higher. Google seemingly doesn't care about Pixel owners at all (not the cleverest of choices, you don't want to insult your own fanbase too much, before becoming a giant).

Personally, seeing those offered prices is a bit of an insult. Google demanded €1000 for the P7 Pro 256 GB, but now offered €345 12 months after launch (EU Google Store), for pristine and perfect condition. That means that Google itself de-values its own product by more than 65% in the span of just one year. That's insane. The fact that there are sites in Europe offering more than €500 for a P7 Pro 256 GB is just increasing the feeling of being insulted.

No wonder that the re-sale value is terrible. This is definitely one of the problems that Google has to fix: re-sale prices. And it starts with valuing your own product high. There are many Apple customers I know, unwilling to switch to Pixel, simply because they are used to re-selling their IPhone high, so a new one will not cost as much. They are not willing to lose so much money on a Pixel.

Before Google fixes that problem, well, the majority of Apple customers willing to switch, will either not switch, or go to Samsung.