yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for the report!

I'm secretly glad the November firmware hasn't (so far) happened at the same time as the Magisk 26.4 update, so it'll be easier to keep any potential problems by either separate. Could still be today, though.
[Google Pixel 7 Pro] Ghisy:
Sure thing! It could have been a real mess!

I always wait a few days for Freak07 to update his kernel before updating the OS though.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - November 2023 - Google Pixel Community
[Google Pixel 7 Pro] Ghisy:
P7P image is available:

UP1A.231105.003

https://dl.google.com/dl/android/aosp/cheetah-up1a.231105.003-factory-c7f94298.zip
[Google Pixel 7 Pro] Ghisy:
Now, who's gonna be brave enough to update with platform tools v34.0.5?! 🤔
[Google Pixel 7 Pro] swour:
Where does this myth to always do the unhide-hide game for every update originate from? I can remember there being a few glitches in earlier versions but those have been fixed.

Unless heavy modifications via mods or modules are in place I'd simply update without those steps. I can happily report that there were no issues on my P7P updating to Magisk 26.4.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It has been my experience that yes in the past there has been an issue updating if you don't unhide, and also that up until today on the P7P, I never had issues unhiding or re-hiding Magisk (or PixelXpert cloning all on its own, for that matter). I'd rather not gamble that there isn't going to be another issue with Magisk updates while hidden, so it's never hurt to unhide.

It's not a myth, it's caution because of a past bug. Normally, it takes two seconds each way.

Whatever preference works for you is fine.
[Google Pixel 7 Pro] Ghisy:
Heads up from the P6P thread: the newest platform tools v34.0.5 might be required for the November update!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Okay, here's the Ninja! :D
[Google Pixel 7 Pro] swour:
I just sideloaded the November OTA with the 33.03 Platform Tools (using PixelFlasher). All went well.
[Google Pixel 7 Pro] savaytse66:
Used 34.0.5 here, and all went well with PixelFlasher and the November OTA.
[Google Pixel 7 Pro] Fishawy:
Wow, I guess I was lucky. Updated Magisk without unhiding the app, and all went well.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Now that I have a spare phone, I don't mind upgrading immediately as much. Updated to November on the P8P & P7P without any hitches using the Full OTA Zip method using Platform-Tools v34.0.5.
[Google Pixel 7 Pro] Fishawy:
Flashing November update now.

Does anyone know if the bug of failing to install Play System Security Update has been fixed? It's not mentioned on the changelog. Have you to tried to update to October?

Edit: Not fixed, and now device doesn't meet security requirements 🤦‍♂️
[Google Pixel 7 Pro] simplepinoi177:
Uh oh.... and you're employing the pre-requisites Displax MOD or PIF?

if so, and there's more reports of those not bypassing root detection, that's a problem because a lot (too many) use it to hide root detection...! I use Google Wallet too much that I'd hate this...
[Google Pixel 7 Pro] Fishawy:
I fixed it, Google Wallet that is.

Apparently I've done a couple of reboots after updating without re-enabling my Magisk modules, and GMS/Wallet sniffed that the device is rooted, so they got angry. Wiping data & cache of GMS and Wallet resolved it (painful to re-add all your cards though).

The thing that is not yet fixed is Google Play System Update (download a 71MB update, install it, reboot, turns out to be a double reboot, and back to square one). Was hoping the November update takes care of it, apparently not.
[Google Pixel 7 Pro] amders:
wait until the problem is coming to you...

once i forgot to unhidenand disable module, after update android auto not working even bluetooth say connected... so i flash fresh and untouched factory image again then the problem solved...

but it wasting time for backup and restore
[Google Pixel 7 Pro] Fishawy:
I forgot to un-hide and got lucky.

Fresh and untouched every month is a bit too much for me. Pixel Flasher helps doing a smooth upgrade and retaining root, and of course scheduling backup is a safe practice.
[Google Pixel 7 Pro] justDave:
Did app clone go away with the Nov update? I still have the clones I made last month but don't see a way to do it anymore.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Platform-Tools v34.0.5 release notes:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] scorpio76r:
Can you share the steps that you took? I'm rooted with latest magisk and running the Kiri kernel. Last month when I updated via pixel flasher I lost all my data and, had to start from scratch after updating. I want to avoid that. This is for the 7pro BTW.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
November update flashed with Platform 33.0.3, Magisk Canary 26401 and Zygisk LsPosed and it's working like a charm.

No issue on PixelXpert and Iconify.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Nope, they don't go away 😤
[Google Pixel 7 Pro] justDave:
Well that's just crazy. I'm glad I took screenshots this time.

12:05pm:

3:54pm:

🤯
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Same here, that's crazy :confused:
[Google Pixel 7 Pro] Fishawy:
If I can take one guess - you forgot to tick "keep data".

Been using Pixel Flasher since last year, never lost my data. In fact, it actually saved me from doing a full wipe twice.

@badabing2003 explains it best in the attached screenshot (numbered steps), and you can find all the details in the main thread.
[Google Pixel 7 Pro] scorpio76r:
I think that I did tick that. Would the kernel be the reason? Or could it had the fact that I went from android 13 stable to 14 stable? I'm lost never had this issue the whole time I was monthly updating on Android 13.
[Google Pixel 7 Pro] Fishawy:
Can't say for sure, but I went from A13 - with a custom kernel as well - to A14 using PixelFlasher, and all went well.

I would suggest reading through the detailed guide and verifying each step before flashing. Otherwise, if you feel more comfortable using the commands, by all means do that.
[Google Pixel 7 Pro] scorpio76r:
Thanks for

I will try again. Thanks for getting back to me.
[Google Pixel 7 Pro] Ghisy:
Updated as usual to November and running the latest Kirisakura kernel, all good here! 👍

(unlike my P6P)
[Google Pixel 7 Pro] stroke55:
FYI - today on all family's Pixels (7Pro, 6Pro & 4a5G) the device integrity was broken. Play Integrity Fix v.12 fixed it for all 3 Pixels :)
[Google Pixel 7 Pro] mavrovelos:
When you say GMS which programs do you mean exactly? I'm asking because after update of the magisk I no longer have Google wallet working...
[Google Pixel 7 Pro] Fishawy:
GMS = Google Play Services.

FYI, my issue was a user problem, completely separate from a more generic issue that started happening yesterday night and today morning (Basically SafetyNet failures, device doesn't meet security requirements, Google Wallet failing to pay, etc).

@chiteroman managed to fix it with the latest release of his Play Integrity Fix module. I suggest you read the last few pages as well.
[Google Pixel 7 Pro] re_endymion:
Hi everyone,

I hope that someone will be able to help me. I've used PF to update to latest november full image. But i've not checked my empty space on my hard drive, and during the installation "extracting product.img" I've had an error "unable to truncate file to 3127772532 : File Too Large".

Since that moment, I'm in boot loop.

I've seach on the forum and google how to be able to restore my phone. Ideally, I would prefer to be able to keep my data, but if necessary, I can wipe all my data.

Thanks in advance
[Google Pixel 7 Pro] swieder711:
Sounds like a corrupt source file. If you are bootloader unlocked than try downloading the Zip file again. Check the checksum before flashing.
[Google Pixel 7 Pro] re_endymion:
As said, on another thread, its strange because I've updated to the latest November update, and Displax's SafetyNet Fix 2.4.0-MOD_1.3 works for me. YASNAC show Basic Integrity
[Google Pixel 7 Pro] re_endymion:
Thanks swieder711. I always verify the checksum, but I've not check my empty disk space size before launching the flashing operation, and it fails because of the lack of hard drive disk space.

I finally succeed in booting under fastboot and successfully reflash the november image after doing some cleanup!
[Google Pixel 7 Pro] simplepinoi177:
add me to the pile that needed to move to PIF to pass Play Integrity API Checker properly....until I did, Wallet wouldn't even let me launch it....

I just uninstalled Displax MOD and installed PIF (without even restarting in between the uninstall and install). I'm just glad I didn't have to clear all the services/apps Play Protect Services, Framework, Play Services, Play Store, Wallet, GPay and have to re-enter all the cards and digital IDs.......
[Google Pixel 7 Pro] phoinix_gr:
I can confirm. Device integrity was broken with today's update.

Remedy:

1. Remove SafetyNet Fix Displax MOD

2. Install Play Integrity Fix v.12

All working again.
[Google Pixel 7 Pro] swieder711:
Removed SafetyNet Fix Displax MOD. Installed Play Integrity Fix v12.1

Now passing Play Integrity Check for Device and Basic.
[Google Pixel 7 Pro] DoJo_Mast3r:
Someone please please help me, been trying to undo the stupid mistake of having my phone update itself via settings ota. Way to many hours trying to fix this here. I had full magisk installed with modules and root access, updated phone of course lost this.

Ive tried so many things here, Ive flashed a magisked patched init_boot.img of UP1A.231105.003 and also tried just tried the larger boot.img file too. Ive also tried flashing slot b, uninstalling all magisk from my phone, reinstalling it, redownloading firmware, reflashing the firmware via pixelflasher etc etc.

Please help, I feel like my only other choice here is todo a full system restore and I really dont want todo that, the bootloader is unlocked so I dont see why that would even help anyways. Please help :(
[Google Pixel 7 Pro] Homeboy76:
If you flashed your phone via PixelFlasher, get the support file and post your questions and the support file on the PixelFlasher Thread. @badabing2003 will help you.
[Google Pixel 7 Pro] humb13:
Guys, I need your help. Something strange is going on.

I flashed the November image on my Pixel 7 Pro as usual, no issues. As always I copied init_boot.img to the phone and tried to flash with Magisk. This after updating to version26.4. Magisk wouldn't search for the init_boot.img file as it normally does and crashed after a few seconds. I tried installing Magisk to my Nox emulator and patch from there. It patched - but now my phone wouldn't boot and I had to re-flash the November release. I tried uninstalling Magisk and using version 26.1 - same result. It's almost as if Magisk won't work with this release. Phone works but I can't root. I run some root-only programs and I'm going bonkers.

Can anyone help?
[Google Pixel 7 Pro] simplepinoi177:
Take heart...there are many members who have lost root, and simply flashing the patched init_boot hadn't returned root....it gets figured out without the need of doing a full factory reset....

But as @Homeboy76 suggested, badabing2003 is one the best devs here at responding to personal inquiries as long as you include a support file....I'm sure you'll get it figured out if you do that...
[Google Pixel 7 Pro] mattburga1984:
Regarding the Play Integrity Fix v.12

I was able get my card working again with this fix, however, my Wallet QS tile says unavailable.

Is there a way to fix this? I'm on stock rom / kernel.

I followed these instructions from a previous thread but it did not work.

Manually remove your Google account

Force stop and clear data for Google Play Services, GPay, Play Store, and Wallet

Reboot

Add your Google account

Open GPay, Play Store, and Wallet, and set everything back up

Reboot again

Any help would be appreciated.
[Google Pixel 7 Pro] mattburga1984:
Is your Wallet QS tile working as well? Mine is not.
[Google Pixel 7 Pro] simplepinoi177:
Probably because you're running it off that Nox emulator (just a guess)....

I was going to say you probably had to re-install the Magisk Manager app as maybe that's struggling patching, but you said you uninstalled it, so....

I might think that you're accidentally running a second Magisk and there's a remnant (hidden renamed Magisk most likely)....you should double check with TB Checker.

But if not, I suggest PixelFlasher and you can either have PF install Magisk proper and/or run it "Manual" and have Magisk patch it external of your device (I only know this in theory from reading about it, I've never experienced or done this myself to confirm/verify if this is actually how it works)
[Google Pixel 7 Pro] phoinix_gr:
Yes. It is working as expected.

Try and clear Google Wallet cache + data, and retry.
[Google Pixel 7 Pro] d4m4s74:
After the play integrity fix my wallet kept saying that nfc wouldnt work for but it still worked. 24 hours later the message was gone too.

Ubiqu Authenticator still detects root somehow. But I can just use a text message for two factor to log into my work stuff.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #2:

As of November 11, 2023, this is the only one that will work @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)

Spoiler content hidden.
[Google Pixel 7 Pro] mattburga1984:
That didn't seem to work, unfortunately.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
You can change your title : PIF updated to v12.3 😉
[Google Pixel 7 Pro] humb13:
You're right. I tried it again only this time with my lady's unrooted Pixel 6 and it worked. I should also mention I used the new platform tools (3.4.09). Maybe that had something to do with it. In any event I've got root back :). Magisk appears to be working OK except for the fact that it continues to crash when it's supposed to bring up a file manager to locate the file you want to patch. It works on other phones. I have no idea why.

Please enlighten me. I downloaded TB Checker but I'm new to it and don't know how to use it. There are several menu items on there but I'm not sure which to pick or what to look for. Even it I find something odd, is there a way to fix it?

I had no clue this thing even existed, so acting on your advice I googled myself a copy. This is the next best thing to sliced bread! You can do all kinds of things! I was surprised by the fact that not only can you patch the init_boot.img file, but you can also flash it together with the image file. I ran a test and it successfully patched the init_boot file that Magisk was unable to locate. I checked and the file wasn't identical to the one I flashed, but then again PixelFlasher seems to use different methods.

So let me ask all you guys before I go full tilt with this. Is it really as good as it appears to be? What's been your experience? Anything to be careful with? And finally, when flashing anything do you always check "Keep Data"?
[Google Pixel 7 Pro] simplepinoi177:
Mine works -- I had the same issues as everyone and had to migrate to PIF from Displax MOD and everything works as intended.

I know there are many that have had QS Wallet tile issues even before this fiasco...I'm sure you can search it and see how they resolved it -- even if it's not the same cause, the solution might still apply to both...
[Google Pixel 7 Pro] badabing2003:
@simplepinoi177

Wow, thanks for collating all that, always happy to be able to contribute.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've been slacking, so I might've missed when this became available, but now besides the Global UP1A.231105.003 November firmware, there is now a UP1A.231105.003.A1 release for Japanese carriers.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

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

developers.google.com
[Google Pixel 7 Pro] simplepinoi177:
It wasn't too hard...it shows how greatly loved & adored you are on this site -- and proves your contributions (both the tool, and the support & engagement you give/make here) go a very long way and are well established/documented....
[Google Pixel 7 Pro] humb13:
I tried all that and it didn't work. What's even weirder is that when installing a module from storage it DOES work. It even prompts me for what file manager I prefer. Everything is OK except when trying to flash init_boot - no file manager appears then Magisk closes.

AFAIK when you take any Android app and clear storage and cache, it also wipes out the settings. That's not happening here. After finally succeeding in rooting the phone, all settings and module were there, untouched.

I ran "Run Xposed Check". At the very bottom it says "Magisk Random Package Name:" and nothing after the colon - no strange text or anything else. However, under "Result Check Xposed" every instance of "com.topjohnwu.magisk" is listed as "Fail". Lucky Patcher is also listed as "Fail" and yet Lucky Patcher works. What does this mean?

Come next month I'll use it to update and let's see what happens. If it crashes I can always reflash with the platform tools assuming I can get the phone into the fastboot mode.

If this is the case then I fail to see why the emulator didn't work. Nox is just an operating system running as a virtual machine. Magisk runs on top of it. It is Magisk that does the flashing. Maybe it was the fact that I used the old platform tools to flash that one and the new tools to flash the other one. I was hesitant to use the new tools at first because a few months ago the new platform tools literally destroyed a Pixel 7 I had. I sent it to Google, believe it or not they fixed it under warranty.

I'm not too clear as to how to approach babading with this. PixelFlasher successfully created a patched ini_boot file which has yet to be tested. All I know is that according to Total Commander's file compare, the init_boot file from the Pixel6 (the one that worked) is not identical to the one that PixelFlasher spit out, except for the byte count.

I'm thinking the issue I have should be asked to topjohnwu. I don't think he'll answer, he's probably a very busy man.

In a nutshell: always enable Keep Data unless wiping. Not too sure what to do with Verity and Verification. And of course make sure to uncheck anything that smells of wiping. I hope this is more or less correct.

BTW thanks for your help.
[Google Pixel 7 Pro] badJester:
I had the same problem with Magisk not working after patching the November 2023 update. (I accidentality rebooted my phone while a update was pending, so no root after that)

Opening Magisk told me to unhide it, which i did.

After extracting init_boot, patching it with the unhidden Magisk Manager and flashing it did not work (Magisk Manager showed no installed Magisk).

I then discovered, the hidden Magisk Manager is still there (searched in my launcher for the name i gave the while hiding Magisk).

Opening it, said, Magisk is installed and another reboot is required.

After rebooting, the unhidden Magisk Manager disappeared and everything worked.

I should have used root checker or something like that to check in first place...
[Google Pixel 7 Pro] Fishawy:
Just a quick update - This is not required anymore for most A14 kernels.

I don't have verity or verification disabled, and I'm shuffling between Kirisakura, Sultan, and Radioactive kernels.

Edit: I believe CleanSlate and Despair still require it though.
[Google Pixel 7 Pro] simplepinoi177:
Thank you for confirming! I had heard news on this, but then got conflicting reports/posts where members were still urging/pushing it (I believe @roirraW "edor" ehT is still currently suggesting/urging for it). But I'm glad you mention this so I know what to tell other people now....

And maybe I will employ a custom kernel now....I wasn't interested in wiping my device and running one wasn't a priority....
[Google Pixel 7 Pro] Fishawy:
True, I was in the same boat, but when Sultan started this thing, I honestly couldn't resist the temptation lol.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I wouldn't characterize it as suggesting or urging others to do so. :D

I choose not to disable mine, because way back on the Pixel 6 Pro, I once forgot to re-disable it, and I don't want to have one more thing I have to remember each month, so I never disable them anymore.

But I do have in my OPs the instructions disabling them if someone needs to.
[Google Pixel 7 Pro] humb13:
I assume you mean uninstall Magisk from within, i.e., using the Uninstall Magisk option inside it as opposed to using the standard Android uninstall method. Would doing this unroot the phone and force you to re-flash the patched init_boot.ing file, or would a basic reinstall alone do the trick? Also, in Magisk settings you can select Stable, Beta, and Custom. Would selecting beta and updating be essentially the same thing?

So if Magisk and Lucky Patcher fail, they're OK and working. If they pass, they're not. I'm starting to think the developer's logic is in reverse. Either that or I didn't understand what you said.

That's good do know. I'll run my first test come December. As I understand it, you can patch the init_boot file from within PixelFlasher, flash first the update followed by patched init_boot in one shot. If PixelFlasher can pull that off, then kudos to badabing2003

You might want to check out Nox emulator in your spare time go to https://www.bignox.com. Grab a copy and screw around with it. It's basically and Android phone on your Windows desktop. It runs most (but not all) Android programs. It even includes a copy of Google Play so you can just download directly from Google. Great for testing. Just be sure that on Control Panel -> Programs and Features -> Turn Windows features on and off -> Virtual Machine Platform is unchecked. Windows Subsystem for Linux and for Android need this, but it conflicts with Nox.

When I tried patching on the emulator, it didn't work. Then I tried on the Pixel6 and used the new platform tools. That DID work. I have no idea why since ideally it should be on the same phone and you explained that init_boot.img files patched on different phones aren't exactly the same. Let's see what happens next month when PixelFlasher patches init_boot.img with my phone's Magisk.

:)
[Google Pixel 7 Pro] roirraW "edor" ehT:
It sure looks like the next Google Pixel phone will support Qi2 as certification arrives

Qi2 certification has arrived, and with it, the likely support of the magnetic charging standard on Google Pixel devices.

9to5google.com
[Google Pixel 7 Pro] simplepinoi177:
As of around 5:30 AM (PST), it looks like Google blocked the PIF circumvention...
[Google Pixel 7 Pro] Schroeder09:
Is there any noticable difference with the November update? I went to A14 October and there definitely is an increase in battery life. Anything new or noticable with this one?
[Google Pixel 7 Pro] i42o:
It has been fixed for now. Take a look at his last post. Can confirm Gpay is working
[Google Pixel 7 Pro] synesthete:
I think it is mainly just security patches.