yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] Chickenkillla81:
pixelflasher does look really awesome. it seems like it packs a lot into it. I REALLY hate that I have this stupid locked bootloader. I should have known though that Verizon hasn't changed. they've been doing this forever. that's why when I lived in Phoenix where all providers were pretty much equal I always went with t Mobile\Metro. they have always been good about not locking down their devices. all I have to play with right now is a cheap Sky devices tablet. it's a mediatek soc and I know nothing about the way it works. I already bricked one mediatek tablet about a month ago trying to pull partitions and flash a modified boot for root. luckily it was only 30 bucks so I don't really care. but there is almost no support for most of these devices so it's tough going. I'm basically just winging it going off of other devices running the same soc. but without stock firmware it is really a pain. anyways. I'll shut up now 😁

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
@Chickenkillla81 By the way, after several days of keeping adaptive battery disabled, I can report that my fingerprint issue might happen slightly less with my recently extra-dry hands, but I can't swear to it, and it definitely doesn't take care of the issue to any great degree.

Thank you for the suggestion, anyway, it was worth trying. I'll go ahead and re-enable adaptive battery and see if I notice any difference the other way around, if it seems worse. After re-testing like that for several days, I'll likely just have to spray oil on my hands after I wash my hands a lot.
[Google Pixel 8 Pro] Chickenkillla81:
I have noticed it doesn't help completely. I forgot to tell you that. it SEEMS better but definitely still has issues. the moisture on the hands makes a big difference. when I'm at work with sawdust and dirt it almost never works. or right after I wash my hands. etc...

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] Ghisy:
Did you also have the issue on the P7P? Or is it only on the P8P? Sounds odd as they have the same fingerprint sensor, don't they?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, good to know I'm not having too different of an experience, at least. :)

I never had any problem at all with my fingerprints on the P6P, P7P, or P8P until something (specific that is irrelevant to share details of) happened to my hands a few weeks back that causes them to be much drier than they had been.

The reader does work for me sometimes, and when it does, it's almost always on the first try, but after washing my hands now, it frequently doesn't work all three times in a row, but I noticed last week or the week before, after I used some olive oil spray for cooking and got some on my hands, that the reader worked perfectly, so when I'm having more trouble, I might just spray some olive oil, but I'm going to try to not do that too often or habitually, plus for now that I'm testing re-enabling adaptive battery to see if I notice it being worse, I won't do the oil at all.
[Google Pixel 8 Pro] Chickenkillla81:
someone just posted a new rom for p8p. evolution x rom.

I just enrolled in qpr2 just so I can feel like I'm part of the crowd. Lol. Lucky people with your rooted pixels. Able to test new roms and stuff. 😝😝😝

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] vegetaleb:
Thanks bro

I rooted my phone to both slots, installed magisk 26.4 with pixelflasher, now when I open magisk app it's showing Magisk Installed: N/A

Zygisk: No

Should I install Magisk from the app itself?

I mean what are the steps for magisk for the 1st use?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I only know the steps I outline in Post #2 - in which case the Magisk app is both installed and used before actually applying the Magisk'd init_boot.img to one or both slots. @badabing2003 would have to weigh in on what might be going on. Have you tried rebooting? @badabing2003 might need to see your PixelFlasher logs (uploaded as an attachment in the PixelFlasher thread).

The only other thing I can guess is that you didn't actually install the Magisk'd init_boot.img to one or both slots, but were under the impression you did.
[Google Pixel 8 Pro] badabing2003:
As @roirraW "edor" ehT suggested, best way is to submit a support file in PixelFlasher thread.

Based on your description, the fact that you're saying that you don't see Magisk Installed, it's either patched init_boot is not flashed, or you have multiple Magisk managers.

Perhaps one hidden and one not.

If you were previously hidden and then unhid to create a patch, sometimes Magisk does not do a good job and the stub remains.

If PixelFlasher is saying that you're rooted, it's definitely that.

When I see the support file, we'll know better.
[Google Pixel 8 Pro] Agenesis:
Anyone having issues with the newest firmware? Getting invalid boot.img with Kernelflasher on Jan firmware.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're trying to flash a custom kernel? Which one?

Or are you by chance accidentally trying to flash a file that's not a kernel to the boot.img partition? Otherwise, is there a possibility to check that the hash of the boot.img you're trying to flash matches what it's supposed to be (if provided)?
[Google Pixel 8 Pro] Agenesis:
Kernelflasher shows this, it worked with the Dec update though.
[Google Pixel 8 Pro] roirraW "edor" ehT:
What, exactly, are you trying to flash? A custom kernel? Which one? Have you tried using fastboot flash boot boot.img to flash whatever you're trying to flash, instead?
[Google Pixel 8 Pro] Agenesis:
Yeah I might have to flash via fastboot. I was just curious if anyone else had this issue with the Jan update or if it's solely on my end.
[Google Pixel 8 Pro] roirraW "edor" ehT:
:) It helps for us to know what you're trying to flash, exactly, otherwise it's challenging to know if anyone else has had the same experience.
[Google Pixel 8 Pro] Agenesis:
It happens immediately once I open the app, couldn't even get to the flashing part.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Oh, I see, thanks. That sounds odd and interesting. I haven't actually flashed the January firmware yet, but may tomorrow if I find the time. I'll try launching v1.0.0-alpha19 of the app once I update and see if I have any trouble.

Try swiping it away from Recents and relaunching?
[Google Pixel 8 Pro] simplepinoi177:
Either @badabing2003 was listening in and reading these, or already had it in mind and it's a fun coincidence! As I just came from reading his newest PF version's changelog and it seems he's addressed your guys's concerns & is trying to assist with it...! Image from his post of the changelog of his newest version.

that guy.....always trying to be the most helpful and get his most helpful tool even more helpful!!!
[Google Pixel 8 Pro] HipKat:
Jeezuz! And he does this for Free!

The guy is a hero in this community.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I saw that in the changelog yesterday, and I'm intending on checking it out. Very awesome! :)
[Google Pixel 8 Pro] badabing2003:
By the way if you don't want to go over all devices from the menu, even though your device would be the highlighted one.

You can check this button, which would switch from being green to red.

It would only display the updates and only for your device.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Kernel Flasher v1.0.0-alpha19 launches fine for me on the January update on my P8P. If swiping the app away from Recents didn't help, try wiping the app's cache and data.
[Google Pixel 8 Pro] Az Biker:
This is only my second factory update on the 8 Pro, so forgive my noobness :D

Is it required, or is there any benefit, to install/fastboot the monthly updates to both slots after I initially rooted, and initially flashed Nov factory image to both? Couldn't find an answer to this after searching a bit.

Thanks in advance.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Only if you're using the Full OTA Zip method, since flashing the factory image prevents the "other" slot from working (as far as fully booting into a workable Android image). i.e. If using the Factory Image method, only the most recently flashed slot will work, so the advantage of using the Full OTA Zip method is that you get two completely working slots, so if one slot fails, the other slot can take over.

With the Factory Image method, if you never took an actual (over the air) OTA before you rooted and flashed, and never sideloaded the Full OTA Zip, then your other slot may not even have a bootloader on it.

History has shown that to be the case, at least on the P7P, although at least one P8P user said they tested and the "other" slot did have a bootloader on it, but it's jut not worth taking the chance, to me.

With the other slot not having a bootloader, if anything happens to your working slot, and it tries changing slots, the phone will be hard bricked, and I mean hard - only Google can solve with the device in their hands.

I use the Full OTA Zip instructions in Post #2, where I detail flashing it twice, and flashing the rooted init_boot.img to each slot, so I have two rooted and bootable slots.

Also keep in mind that if you only update one slot each month with the Full OTA Zip method, although both slots will technically be bootable, the slot that has the old firmware on it will likely not work correctly, because it'll still be using the new system and user app data since the data is shared by both slots, therefore again a good idea to have both slots have the same updated firmware on it.

I hope this helps.
[Google Pixel 8 Pro] Az Biker:
Thanks for the usual in depth response!

I'm pretty sure I flashed the factory image and rooted init img to both slots individually on my initial bootloader unlock and first factory image without taking an OTA.

Step 9

On the phone:

Wait for the phone to boot normally.

OPTIONAL: If you want to flash both slots, after this first time, then after do the following

:

Code:

adb reboot bootloader

fastboot --set-active=other

flash-all.bat

So you're doing the flash-all.bat a second time on the second slot.

How do I verify if both slots have a bootlader without bricking myself?

Sorry for the basic questions.
[Google Pixel 8 Pro] roirraW "edor" ehT:
No sweat, you're welcome!

Ah! Good catch. I need to remove the instructions about flashing both slots when using the Factory Image, since the only good that does is make sure there's a bootloader on the other slot.

So it's actually not useful in any way to flash the rooted init_boot.img to the other slot, since only the most recent slot that was flashed with the factory image will even work beyond the bootloader.

I'm sure @badabing2003 has a more direct answer, but I would say simply sideload the Full OTA Zip (and flash the rooted init_boot.img again, since the beginning of the sideloading process automatically switches slots). That will both make sure the slot (was "other", but now is "current") has the bootloader, although it will also make sure it has the current firmware as well. You'd do well to go ahead and do it twice, however, since the initial slot that you flashed the factory image to will no longer work once you overwrite the (was other, now current) slot with the Full OTA Zip, I believe.

I'm vaguely aware of that you can manually flash the bootloader to slot=all, but I never use slot=all, so I'd just do the Full OTA Zip method to be absolutely safe.

Bonus for the Full OTA Zip method - there's no flash-all.bat that needs modifying - it'll never wipe your phone.
[Google Pixel 8 Pro] Az Biker:
Believe it of not, in my 12 years of flashing I've never used the sideload method, always stuck with the factory images. I'll follow your suggestion with the full OTA zip method to be sure both slots are good.

Thanks again.
[Google Pixel 8 Pro] simplepinoi177:
I was about to suggest simply switching slots, and if the other slot doesn't load/boot, it probably doesn't have a bootloader -- but that's only because I imagine it should be easy to go back into bootloader mode and switch slots back.

But you're right, I imagine badabing2003 would have a good idea as PixelFlasher has a lot of checks and such in its code that I imagine he'd know a proper direct way of finding out in a proper output or something...
[Google Pixel 8 Pro] simplepinoi177:
Since I've been on the Pixel (2 XL), I was under the same practice -- I didn't like the logic of incremental OTA updates when compared with Full Factory images/update (have since learned there is a difference between incremental and the Full OTA updates)! Oh yeah...that's when I first met you! But yeah....every month manually flashing, never thought/went-through with the sideload method -- just told lost members with broken devices that that might help....
[Google Pixel 8 Pro] roirraW "edor" ehT:
I always did the factory image, too, until @Lughnasadh and @badabing2003 showed how Pixels sometimes (or for a period, seemed to always) not include anything at all in the alternate slot, which was dangerous to not at least have the bootloader.

And before that, they also showed how flashing the factory image to both slots was different from flashing the OTA to both slots, and what I said about only the most recently flashed factory image slot would work (although at least the bootloader would be on both slots).

The last 6-8 months, I've been only using the Full OTA Zip method (and to both slots), and I won't be going back.

I suppose I'll keep about optionally flashing both slots in the factory image steps, but I should modify that instruction to point out the caveat, even though Post #2 has that information already between the "Unlocking Bootloader" and "How to update each month" sections:

NOTE that as @Lughnasadh has previously found and reported, both the factory image method using Flash-All.Bat, and the Official Google Android Flash Tool (webpage) cause only the most recently flashed slot to boot. If you want both slots to be bootable, you want the Full OTA Zip method a couple of sections down in this post.
[Google Pixel 8 Pro] cmh714:
I noticed that the screenshot @roirraw-edor-eht posted of Kernel Flasher had a "boot hash" that I would assume corresponds to the boot image.....not sure how that would convert over to a version number....
[Google Pixel 8 Pro] roirraW "edor" ehT:
That wouldn't explicitly mean that there's a bootloader on the other slot, only a boot.img or init_boot.img, whatever Kernel Flasher goes by or that indicates.

If you go into "View" in Kernel Flasher for the other slot, it does have a button to check the kernel version on that slot, but again, that's not the bootloader. I know it might be logical to think that as long as there's a kernel on the other slot, that there'd also be a bootloader, but I wouldn't want to assume.
[Google Pixel 8 Pro] Lughnasadh:
https://twitter.com/i/web/status/1744762602990043389
[Google Pixel 8 Pro] Lughnasadh:
https://twitter.com/i/web/status/1744766601814212747
[Google Pixel 8 Pro] Chickenkillla81:
So what does the kernel upgrade mean exactly? Would it add anything to the device? Or is it just security oriented?
[Google Pixel 8 Pro] Gilg@mesh:
don't expect miracles, it's still Exynos.
[Google Pixel 8 Pro] Chickenkillla81:
I was reading that recently. I didn't realize that the G3 tensor is just rebranded exynos chip. those have always been the crappy Samsung chipset.

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
Taken from a Google Search:

and from:

Android common kernels | Android Open Source Project

source.android.com

Et cetera...
[Google Pixel 8 Pro] Chickenkillla81:
the QPR Beta 3 is out if anyone doesn't know yet. it has a really nice change(for me anyway) when you go to system-system update. it had a new option to check for app updates right there instead of having to go to the play store. I frequently forget to check for app updates so I like it being up front.

phone does feel like it is running warmer than usual but maybe I'm just crazy.

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
Interesting! Thank you! I look forward to checking it out when it hits Stable in a couple of months.

QPR3 has gone Stable, see my Stable thread - Android 14 QPR3 Beta - "Upside Down Cake" - Pixel 8 Pro [Husky]

Android 14 QPR3 Beta program for the Pixel 8 Pro [Husky] June 11, 2023: QPR3 has gone Stable. QPR3 Stable discussion starts here...

xdaforums.com
[Google Pixel 8 Pro] Chickenkillla81:
That's right I forgot you don't do the beta. I wouldn't either if I could mod like I want to. Lol. I have been looking at used phones on swappa. There are some really good deals on older pixels. I might try to pick something up so I have a secondary device I can play around with. Although I love this p8p so much that it seems pointless to spend the money just to root and mod a device. 😂 I just don't have many hobbies and am a sad boring old man. 😂😂
[Google Pixel 8 Pro] Lughnasadh:
Hopefully they'll move the Google Play System Updates to back to System>Software Updates section like they had it for a little while in earlier betas. Currently it's still in the Security & Privacy section.

But hey.....beta be beta.
[Google Pixel 8 Pro] Keiuran:
I have no idea where to ask this question so I'll post it here since it's the most relevant.

I got my Pixel 8 Pro all set up and with Play Integrity Fix but some reason I just cannot download and install Netflix or Hulu.

Disney+ (same with Mario run) was giving me similar issues but after I installed and activated the Universal Safety Net Fix that was fixed even though NetFlix or Hulu wouldn't even let me find them on the store.

Doing more digging led me to the Play Integrity Fix and so I installed that one and put the phone in airplane mode and cleared data (which cleared cache) on Google Play, Google Play Services, and Google Play Framework. When I got back in I was finally able allowed to try and download and install Netflix and Hulu but it failed repeatedly. Netflix then went back to being unsupported by my device and unable to be downloaded, while Hulu I can still find on the Play Store but I'm unable to install it as it fails.

Does anyone know what's going on and how I can fix it? These are the last two apps to finish my migration from a Pixel 2 XL and it's driving me mad.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi! What does the following from Post 2 report?

And what version/who's Play Integrity Fix are you using? @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)? Or the fork of that, which I don't have a link to, handy?
[Google Pixel 8 Pro] Keiuran:
Meets basic and meets device integrity. I can use Google Wallet no issues. No other apps are giving me issues besides Netflix and Hulu at the moment.
[Google Pixel 8 Pro] roirraW "edor" ehT:
My other question:
[Google Pixel 8 Pro] Keiuran:
15.1, the most recent. I believe there's going to be a 15.2 soon since the dev is refractoring code at the moment.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! I haven't experimented too much with the fixes lately, as the 14.6 version I'm using has remained good enough for my purposes, but I know there's a fork of that fix, you might want to experiment, and I'm sure has been mentioned somewhere in that thread, and maybe this thread too - just make sure and disable one fix when you try another, before rebooting.

Hopefully that or 15.2 fixes it for you. Just the unlocked bootloader alone might be keeping those apps from installing or working, and I think that either all the time, or sometimes, it's not possible to hide the fact that the bootloader is unlocked. I don't use those apps, though.
[Google Pixel 8 Pro] Keiuran:
I figured it out! Somehow during all of this I missed putting Google Play Services in the denylist of Magisk. I thought I had put it before, but maybe mis-clicked or it got reset when installing Play Integrity Fix. Everything is working fine now it seems. Now I can finally get to setting up more fun modules and revanced manager.
[Google Pixel 8 Pro] roirraW "edor" ehT:
From Post 2:

But it's certainly possible that still initially denying it, even if it becomes undenied, is beneficial. There's more that we don't know than we know. :)

It's also possible that just waiting helped.

Cheers! Glad you solved it.
[Google Pixel 8 Pro] HipKat:
I made that back when Chiteroman's was the go to.

Now I use Osm0sis, but still on v5.

Deny list off

Same FP has been working for a few weeks now

FWIW, I installed Netflix, no problem
[Google Pixel 8 Pro] BillGoss:
You'll find the Play Integrity Fork by osm0sis at https://xdaforums.com/t/tools-zips-...tiple-devices-platforms.2239421/post-89242336
[Google Pixel 8 Pro] Chickenkillla81:
my recent button stopped working. anyone running stock ever run into that problem? it's not the screen. my haptic comes on and it shows the touch on the recent button but it doesn't do anything

Sent from Pixel 8 Pro using ReLabs

edit: rebooted and all is good

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] Keiuran:
I've had this happen a few times already. It's very annoying but reboot does solve it. Are you running nova for your launcher? I thought it might be nova but killing and restarting the app didn't bring back the recent button functionality so I'm unsure what the problem is.
[Google Pixel 8 Pro] Chickenkillla81:
ahh ha! I am running Nova. I didn't try killing it though. just a reboot. but that could be it. I don't mind a reboot occasionally as long as it isn't a constant issue. I am running QPR Beta 3 also. I bugged it and reported it. I hope I didn't just waste their time

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] roirraW "edor" ehT:
I resisted gestures instead of the navigation bar until a month or two after I got my Pixel 6 Pro, and I've been happy with gestures since then. I also appreciate the increased screen real estate.

I use the most recent Nova Launcher v7.x (I believe maybe 7.0.58). I refuse to run the v8 Beta until I don't have any choice.
[Google Pixel 8 Pro] Chickenkillla81:
That's what I am currently using. 7.0.58. I don't really use the gestures with Nova. I did turn on the nav bar though. (before I installed Nova) I had an iPhone for the first time in my life for about 5 weeks before the p8p. My biggest complaint was no nav bar. I don't know why I'm attached to it but I am. 😂😂 sentimentality I guess. Kinda dumb.
[Google Pixel 8 Pro] HipKat:
I'm with you. Gestures are just too easy and now I've had so many that do common tasks for so long, I couldn't go back to buttons