yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you!

More things I really should add to my OPs.

It first made me think of (boot flo), and I didn't even know this was a thing:
[Google Pixel 8 Pro] badabing2003:
If prior to flashing Softbank, you had verification enabled, and when you flashed Softbank you accidentally or intentionally disabled verification, you would get that Cannot load Android system. Your data may be corrupt message and would require a wipe if you want to have verification disabled,

However if you flash back vbmeta with verification enabled, the system would boot properly.

It probably had nothing to do with Softbank, just verification flag.
[Google Pixel 8 Pro] Chickenkillla81:
Ok. Really weird thing happened today. When I got up at 530 my battery was at 100. At 1130 my phone dinged in my pocket with 20 percent battery left!! It was ad away!! It had never done that before. I've been using it since warrior recommended it. It was even paused because I was reading the news this morning and a site balked at it and I forgot to resume it. Could that have caused it to run in the Background more?

Edit. I'm running without root
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good question. That would be my guess. I think sometimes things just get "stuck". I've had the same thing happen with my non-rooted (and no ad-away) Pixel Watch 2.

If no one here has any idea, you could check the app's thread:

[APP][ROOT/NONROOT][OFFICIAL] AdAway v6.1.3

AdAway AdAway is an open source ad blocker for Android using the hosts file. Google Play Store notice According the Google Play Developer Policy, especially the "Device and Network Abuse" section, ad blocker like AdAway violates the "Apps that...

xdaforums.com

You could use the "Search this thread" option with the keyword battery and see if something similar has been reported before. It also wouldn't surprise me if the non-root method of ad-away uses more battery than the root method.
[Google Pixel 8 Pro] Chickenkillla81:
I'll check it out tonight. Thanks
[Google Pixel 8 Pro] radionerd:
Updated Safteynet (never tried to mess with PF) and UQ1A.240205.004, no problems. Opened magisk after updating, it prompted to update to version 26404, Weird, had just updated Magisk prior to flash.

No prob noticed until I opened Magisk today and got a notice:

Requires Additional Setup

your device needs reflash Magisk to work properly. Please reinstall Magisk within app. recovery mode cannot get correct device info.

Everything seams to be working fine, and finally it passes safety check, CTS profile match, was able to add CC to Wallet.

I'm hesitant to try anything yet.

Thanks,

radionerd
[Google Pixel 8 Pro] roirraW "edor" ehT:
Did you by chance have Magisk hidden (so you might have two copies now)?
[Google Pixel 8 Pro] Chickenkillla81:
New beta out if anyone is on it. It changed to AP21. If you are on AP11 and want to opt out without phone wipe, now is the time. After taking AP21 out will require a wipe

Edit. Woops, didn't mean to quote you there. Force of habit I guess. Lol

Double edit: finally I have the power of circle!!!!!!!!! 😂
[Google Pixel 8 Pro] roirraW "edor" ehT:
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] radionerd:
Nope,

not hidden.

All fixed.

I clicked on Magisk's normal Install "Direct Install (Recommended)" it installed, rebooted, and it cleared the error popup. All good

Thanks ;-)
[Google Pixel 8 Pro] Chickenkillla81:
Warrior, I did something you talked about awhile back and it's amazing. I made a folder and set up gestures. I love it. Thank you. I don't know how I lived without it.

And the battery thing seems to be a fluke. I charged up to 46 when I got home and am at 31 now. And that's with all my heavy usage time. News, video games, etc. I think it was ad away just wondering why I never resumed it. It was having FOMO🤣
[Google Pixel 8 Pro] roirraW "edor" ehT:
With Nova? Cool, glad you like it.

Glad it's more normal now. :)
[Google Pixel 8 Pro] Agenesis:
I'm having issues with the January update where I can no longer install old apps. It's saying this app was made for an older version of Android.

Yet on my S24 also running Android 14 I can install it without any issues.

Any idea how I can get around this?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Can you give an example of a particular app?

I know Google has modified how old an app can be installed - at least on the Pixel, or maybe the apps you're trying to install are 32-bit? I can't recall if everything requires 64-bit apps now, but it's possible that Samsung kept the compatibility for the old apps.
[Google Pixel 8 Pro] Agenesis:
Naked Browser Pro and Termux both isn't downloadable from the play store. It was downloadable a month before but not anymore. Google is imposing these arbitrary rules on old apps.
[Google Pixel 8 Pro] Lughnasadh:
You can try sideloading them with this command:

adb install --bypass-low-target-sdk-block apk_name.apk
[Google Pixel 8 Pro] Ghisy:
It's odd: Termux is 64 bit-compatible as I have it installed on my P7P that can only run 64 bit-apps. At least, this app shouldn't be a problem. In the worst case, sideload it from APKMirror or something,
[Google Pixel 8 Pro] Morgrain:
Gemini seems to be out. Anyone found a way to enable it on non US models yet and combine it with Google Assistant?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel Phones Will Soon Adapt the Touch Sensitivty On Your Phone Based On Your Activities and Environment

Google is apparently adding a new feature to Pixel phones that will let your device have adaptive touch screen sensitivity

wccftech.com
[Google Pixel 8 Pro] Lughnasadh:
Google System Release Notes (January & February (partial))​

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com
[Google Pixel 8 Pro] Chickenkillla81:
Supposedly play store updates is fixed and released again. I just updated mine and all seems good. I don't have multiple users though so I don't know if that was the real issue with last release or not. But it is going good for me

Also, Gemini app is live now. It even replaced my assistant. I haven't really used it but definitely looking forward to it. It even synced all my bard stuff from the old bard website. So I have my last conversations already in the app. Anyone else try this yet? What do you think?
[Google Pixel 8 Pro] Keiuran:
So I'm in the process of doing my update to the February update and I'm a little concerned about unhiding Magisk (what do you mean exactly by unhiding Magisk btw) and turning off the modules. The moment I do that won't I fail to pass integrity and my credit cards will be removed from my wallet? I'll be unable to be added for at least a couple days if that happens and it's very annoying (Thanks Chase). How do I update without losing basic and device integrity?
[Google Pixel 8 Pro] BillGoss:
You should not use Termux from the Play Store - it's an old, unsupported version. You should always get it from https://f-droid.org/en/packages/com.termux/
[Google Pixel 8 Pro] roirraW "edor" ehT:
I read yesterday that Gemini doesn't really fully replace your assistant, and that it only passes voices assistant phrases on to the assistant.

I don't plan on trying Gemini any time soon, or possibly until it actually replaces assistant.

In Magisk's settings, there's an option to "hide" Magisk, which creates a copy of the Magisk app that you rename to whatever you want, and this replaces the unhidden version. From time to time, Magisk has had problems during updates when Magisk is hidden, so I recommend unhiding it in case that issue comes back.

You can try without unhiding. It'll most likely work, but there's always a chance something will go wrong. It's up to you.

I can't speak as to "the moment you turn off the modules", except I didn't think it was that instantaneous. However, you can try updating without turning off the modules - just make sure they're all up to date. There's a chance that if a module is incompatible with the new update, that the phone will boot loop. If it does, there are options listed in the first page OPs for getting out of that, and there are other options as well that I may not have added to the OP yet.
[Google Pixel 8 Pro] roirraW "edor" ehT:
FYI for future considerations, once QPR3 is closer to going stable (around June 2024):
[Google Pixel 8 Pro] snovvman:
I've been flashing for over a decade, so this is not new. I've been updating monthly since P8P came out, so that's not new either. I flash manually--patch the init_boot, download the image, flash, the flash the patched init_boot. It has ticked like a clock with no issues.

I was on QPR2 and decided to flash the Feb factory. The flash went fine, but the restart goes back into fastboot with "boot failure". I tried to re-flash with 33.03, 04, and 05, it made no difference. I re-downloaded the image, no difference. I might try Pixel Flasher later but I have never used it.

Any idea on what might be going on and how to resolve it? Thanks!
[Google Pixel 8 Pro] Lughnasadh:
Might be that you needed to wipe, if you didn't, since the last QPR2 beta is ahead of the QPR1 stable, which the February image is.
[Google Pixel 8 Pro] roirraW "edor" ehT:
QPR2 hasn't gone Stable yet (or at least the Stable QPR2 hasn't been publically released), so flashing the February firmware was technically a "downgrade", which requires a factory reset in order to behave correctly. So the issues are from having QPR2 Beta app data trying to be used by QPR1 February firmware, and things just aren't going to mesh.

I can't think of any other solution at this point but for a factory reset. You could try flashing the same QPR2 Beta that you were most recently on, and it might work, but it's possible that app data has been modified even further by trying to boot the February firmware. Worth a try, I suppose.

Then you'd have to either opt out immediately (if you were opted into the Beta program) and refuse any OTA until QPR2 goes Stable, or wait and opt out when you hear QPR2 Stable has been released.

Ninja'd by @Lughnasadh. :D
[Google Pixel 8 Pro] snovvman:
That must be it. I'm going to QPR3 in that case. I wanted to get off of the QPR train for a while, but I am not going to wipe. It's too much work right now. Thanks for clarifying. I guess I should have done my research on the order of things. Thanks again!

Thanks for the information. Can I go to QPR3? That would be an upgrade to QPR2. I guess the wild card is how the app might have been modified by the Feb release.

I have always directly flashed the images, including QPR, so I never opted in and always have OTA turned off.

So before I shoot my other foot, what's the prognostication on going to QPR3, now that boot has failed because I flashed the Feb stable on top of QPR2?

Thanks!

Edit: I have been running QPR2 since early December (I recall seeing a date of Dec 5). If QPR2 is a better option of saving a wipe, where might I find the image? Found QPR2b2. Link here in case someone needs it. Just to get my ducts lined up--does anyone have a canary patched QPR2b2 init_boot.img they can post?

Lesson learned here is to keep the last flash and all the resource files.
[Google Pixel 8 Pro] roirraW "edor" ehT:
There's the same chance the QPR3 Beta 1 would work or not work as flashing whatever QPR2 Beta you were on previously, with the potential benefit of flashing QPR2 Beta being that assuming it does actually behave more normally after you go "back" to it, then you'll be able to get back to Stable sooner (when QPR2 Stable is released probably next month).

QPR3 won't go stable until ~June, so that would be far longer to wait to get back to Stable releases.

I did a Google search and found the following article:

Android 14 QPR2 Beta 3.1 rolling out with many Pixel bug fixes

Google is rolling out Android 14 QPR2 Beta 3.1 with a slew of bug fixes today. It follows the last...

9to5google.com

which has all the links for the various device including:

It is very common that the links to these files are still good after they've been superseded, or even in the rare occurrence that Google "pulls" an update (like they did on one or more previous Pixels with some December's stable update IIRC).

Even if this Beta is newer than what you were on previously, it should have just as much a chance of working, as this would be an "upgrade".

If it doesn't work, sure, you could try QPR3 Beta 1 if you want to do everything possible to avoid a factory reset, but I think if QPR2 Beta doesn't make your phone workable again, then neither will QPR3 Beta.

Good luck! Let us know how it goes.

Edit: And indeed, I try to keep the previous two firmware updates I've downloaded, just in case, although I stay on Stable in recent years.
[Google Pixel 8 Pro] snovvman:
@roirraW "edor" ehT thank you for taking the time to provide all that info. I've said this before, but it needs to be said again. What a breath of fresh air--thanks for being such a helpful mod. Instead of "search for it", you actually help, a lot. Same to @Lughnasadh too. I will report back with what happened.

Attached are two ini_boots from QPR2. Will someone please patch with canary and re-post? It will help a lot. Thanks!
[Google Pixel 8 Pro] badabing2003:
These were patched on Pixel 5 Redfin

Although it's preferable that you create a patch on a device that you would use, most likely they will work for you.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you! No sweat. I agree with you about @Lughnasadh, too. And @badabing2003. You're welcome!
[Google Pixel 8 Pro] snovvman:
Thank you very much @badabing2003! I'll give them a try.
[Google Pixel 8 Pro] snovvman:
So the phone is breathing, but can't restore root.

I flashed QPRb2 and the phone booted fine. Flashing the patched boot from @badabing2003 caused the phone to reboot to fastboot with either "boot failure" or "BL1 requested". I re-flashed QPR2b2 and the phone booted fine once again. This time I used Magisk to patch init_boot and then flashed the result. Same problem--phone reboots to fastboot with "boot failure". Any ideas? I am flashing the patched boot to both slots. Could that be the problem?
[Google Pixel 8 Pro] BillGoss:
I've seen some users have booting problems after patching with Magisk 27. The problem disappeared when using Magisk 26.4.
[Google Pixel 8 Pro] badabing2003:
What @BillGoss says.

Also try with modules disabled.
[Google Pixel 8 Pro] snovvman:
Ah, that again. Is there a way to back-rev from 27 to 26.4 without losing the Magisk settings, modules, etc.? Thank you, Bill!
[Google Pixel 8 Pro] badabing2003:
Uninstall Magisk application Flash Magisk 26.4 patched init_boot, Install Magisk 26.4

If you cannot boot to system, no need to uninstall Magisk
[Google Pixel 8 Pro] snovvman:
Uinstall Magisk application--I presume this will cause the loss of grant root to apps, modules, and hide settings?

Flash Magisk 26.4 patched init_boot--how would I do this if I didn't have the app installed?

Any way around losing the Magisk application settings--grant root, modules, and hide settings?

Thank you.
[Google Pixel 8 Pro] snovvman:
I uninstalled Magisk 27 and installed 26.4. I used 26.4 to patch QPR2b31. Still getting "boot failure" from bootloader with patched init_boot. The phone boots fine on a fresh factory flash.

Any other ideas?
[Google Pixel 8 Pro] badabing2003:
Did you disable modules?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Argh. I just lost my draft post. :)

If I were you, I'd try the Official Google Android Flash Tool. Make sure the following options are UNchecked: Re-lock bootloader, factory reset, force flash all partitions (this would also factory reset), and the option for disabling Verity and Verification.

On the Pixel 7 Pro and Pixel 6 Pro, I've both personally experienced and also seen a large handful of other users who were able to solve strange issues with that site.

None of the experiences I noticed, however, were like your unique circumstance, but it shouldn't hurt to try.
[Google Pixel 8 Pro] badabing2003:
Don't you hate that? it's sooooooo irritating. :(
[Google Pixel 8 Pro] roirraW "edor" ehT:
I have a browser extension made for that sort of situation, but I only just definitively recognized earlier this morning that it's not working with either of the two main sites that were the reason I installed it for. Either there's a privacy lock-down for extensions in place now that cause it not to work, or something's going on.

I'll have to research further and find out what's going on.

I am normally in the habit of Control-A and Control-C before I refresh the browser or have some other issue. In this case it wouldn't let me post or switch to BB-Code mode, and I manually chose XDA's save draft option, but it obviously didn't work this time - and probably for the same reasons everything else wasn't working. I should've Control-A'd Control-C'd before I refreshed, but my 'bot brain glitched.

Edit: At least it wasn't the very longest draft post I lost. :)
[Google Pixel 8 Pro] snovvman:
Well, here we go: I made a front-page, facepalm worthy error and continued to not see it until late last night. In fact, the patched .img that @badabing2003 made from me from P5 would have worked the first time I flashed back to QPR2, but I was too distracted with other things to realize my mistake. Worse, I was making the same error over and over until the light bulb went on.

The phone booted fine with the factory flash but not when flashed with patch. I went as far as uninstalling Magisk, installing 263, 264, 270 stable and patching the .img with each. None worked--the phone would go back to the bootloader every time with "BL1 requested" or "boot failure". I had to go back to factory every time. I was tired of it, so I decided to just try to "boot" with the various patched img hoping to find a solution and save some time. That was when I saw it. WTAF?!!! I have been flashing to BOOT rather than init_boot. WTAF?!!!

Btw, I did try to disable the modules, but ADB kept returning with magisk not found (maybe because Magisk was hidden?).

After unsuccessfully kicking myself in the a$$, I flashed the patched img to init_boot and it booted just fine with 27001. Next issue was that Magisk was hidden, so I had to delete the "other" "settings" and then I was able to install the 27001 apk. To my delight, all the config was still there. The deny list, root grants, and modules were all there.

I only have two modules: Fullscreen/Immersive Gestures (which I can see is working) and USNF v2.4.0 MOD_1.3 (Displax fork). As expected Play Store was not certified. So as always, I hid Magisk and cleared the storage/data for Play Store. To my surprise, Play Store was still not certified after a few tries. I've never run into this problem before, so I am curious if I need to uninstall/reinstall USNF? I mentioned that the other module was working, so I would assume that the USNF is also working, but something is not. Any ideas?

Many thanks to @roirraW "edor" ehT, @badabing2003, @Lughnasadh, and @BillGoss for all the help and sticking with me. It is much appreciated!

Lessons:

1) Keep previous versions until the next version is flashed and running. I used to do this but got complacent. It might save you one day.

2) Make sure you are flashing to init_boot. WTAF!!!

Feel free to add lol.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome, and glad you found the issue. USNF 2.4.0 Mod 1.3 is extremely out of date. See the SafetyNet section in Post #3 for the current recommendations. Even then, it can take just waiting hours, or even a day, some cache clearing, and/or an extra reboot before you're certified again.
[Google Pixel 8 Pro] snovvman:
Thanks--I did not know about the waiting period, but I was just thinking that I should RTFM [the first few posts]. I see that there are three options in post #2 and I only need one. Do you have a preference out of the three?
[Google Pixel 8 Pro] badabing2003:
The best method is for you to find your own print, this way the chances of that lasting is much higher, actually my first one is still working fine.

You can go the easy route and use a public print, but be prepared to go down weekly or so.

Here's UI way of getting setup and hunting for a print.

My recommendation would be to use @osm0sis fork, which is very solid and reliable.
[Google Pixel 8 Pro] roirraW "edor" ehT:
daboynb's PlayIntegrityNEXT (fork of @chiteroman's) actually says not to use his fork of @chiteroman's module, and to instead use @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix) directly, but to install the PlayIntegrityNEXT fingerprint module (curl?), which you can use to grab new fingerprints.

That's what I've been doing, but I've been planning on going down the road @badabing2003 explained, and may do that soon.

I haven't tried @osm0sis PlayIntegrityFork (fork of @chiteroman's) just yet.
[Google Pixel 8 Pro] Chickenkillla81:
I have been doing what warrior has been as well. The PIF and additional NEXT (playcurl) module. It's been working great for me personally on my pixel 5. I had to change it once, but all I had to do was press the"fingerprint"app icon and it automatically updated itself and has been good since.

On different note. I know this isn't general forum but anyone try the Gemini yet? I find it to be as I've read online, very hit or miss. I tried using it for navigation one time and it started a 2 minute speech and didn't even open maps. I still had to click on the screen to actually start the nav. WTH is up with that.
[Google Pixel 8 Pro] fil3s:
I got Gemini from apkmirror as it's not officially available in Australia. I use a lot of AI, ChatGPT plus for helping with my business listing on Google maps, blog posts, etc, and others.

I use voice ai primarily. I don't particularly like the Gemini voice, I would rather a female, however, my Google nest speaker has Gemini in charge of it now, with the original assistant voice.

Sent from Pixel 8 Pro using ReLabs
[Google Pixel 8 Pro] snovvman:
Thank you, @badabing2003, @roirraW "edor" ehT, @Chickenkillla81. I've got up and running using

PlayIntegrityFix with Playcurl alongside. It was a quick fix. The @osm0sis fork and getting my own print seem like a better long term solution so like @roirraW "edor" ehT I will probably go that router later. From the looks of it, it will require some set up and learning on my part.

What a journey. I got root back and now once again certified without wiping, which was so important. Very grateful for this sub-forum and all those who helped!
[Google Pixel 8 Pro] Chickenkillla81:
Thanks definitely goes to the other two. I'm just a noob. Those two are awesome and extremely helpful. Glad it's working for you though. I would hate a wipe too. It sucks to have to do setup again 😃
[Google Pixel 8 Pro] roirraW "edor" ehT:
Awesome! Thanks for letting us know everything's all fixed.

Thank you!

Spoiler content hidden.