yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Schroeder09:
I see a handful of people- myself included- noting worse battery life on the December update. I am starting to wonder if it could be all version customers. There wasn't a specific Verizon update image in December, but in previous months- at least in November- Verizon had its own update files.

Personally I have a lot of Google play services wakelocks related to location checks and wakes. Could it be possibly be they're related to not having strong radio signals and the phone is now waking up and working more for signal checks? If this is not possible someone lmk and shut me down. I'm just brainstorming though. It seems no one has really been able to determine why the battery life has gone down. They just note that it has.
[Google Pixel 7 Pro] budmannxx:
I don't believe there were any errors after disconnecting/reconnecting, but I'm not sure how to be sure. And, I'm reconfirming I'm on Windows--bad news about this not working on Mac.
[Google Pixel 7 Pro] plemen:
Hi - I'm trying to return back to stock for testing the new beta. I've read and reread the instructions. Can I install the stock ROM without wipe? Is that all there is to it?

Thanks

Edit: Not possible - installing OTA, locking bootloader and returning to stock causes all data to be wiped.
[Google Pixel 7 Pro] spdwiz18:
Alright guys... Its been a really long time since i'v done any of this. So please bear with me a I try to reteach me self this stuff.

So hear it goes....

I rooted, it worked..

Got Dec system update, obviously it fail to install. Downloaded Dec factory image. repacked the init_boot.img with Magisk. Flashed the using pixel flasher with repacked IMG without wiping date. Reboots with boot loop. Yeah... I screwed something up.. Not a big deal, you live and learn. Finally got it back to bootloader mode and flashed the full factory image after editing the batch file to retain data. Reboots great. Runs fine, unfortunately, no root as expected.

i pull the factory init_boot.img, put in storage, open magisk, repack img, reflash img via cmd. flashes fine... reboot... BOOTLOOP.

so i reflash OG init_boot.img and boots just fine. So great, what did i do wrong??

after rereading the steps.. there is the whole thing about unhiding magisk, moduls ect..... I obviously missed that,, My fault, ill own it.

so to my question...

Do i Need to do a data wipe? or is there a work around?

tried the adb.exe wait-for-device shell magisk --remove-modules

cmd line returned /system/bin/sh: magisk: inaccessible or not found

And can i repack the factory img with the modded init file to do a fresh flash without installing Magisk first. i use to make my own flashable files but so mush has changed just want to be somewhat sure and not Brick my toy...

I know this post is long, But sometimes the devil is in the details.

And yes, i have reread all the post from Dec 5 till now to see how others tried to fix.
[Google Pixel 7 Pro] Tasneem khan:
Hi sorry to hear that... yes everyone messed up at some point for now here is two things to do without wiping..

1 flash the original boot _init image without magisk after flashing boot up your phone then try to get it into safe mode there is chance it will disable all modules which are causing bootloop.

If this didn't work then try second option

2 look for magisk app in Pixel flasher which patch the boot image with module disable code. After patching boot image with that magisk flash it

Hope this will work for you...
[Google Pixel 7 Pro] badabing2003:
1- safe mode with stock init_boot cannot disable Magisk modules., you need root to be able to access /data/adb/magisk so that you disable the modules. Yes catch 22

2- with patched init_boot if you manage to get to safe mode then it should disable Magisk modules, most often it does, but there has been cases where this has not worked.

3- with patched init_boot, if the phone temporarily manages to get to adb, even briefly then this command would work adb.exe wait-for-device shell magisk --remove-modules (which by the way what the sos button does in PF)

4- if all else fails, you can flash as special Magisk version that provides root access but does not load Magisk modules (all credit goes to @gecowa6967) You can also install it from within PF.

@spdwiz18 Of course all of this assuming that the problem is due to incompatible modules.
[Google Pixel 7 Pro] spdwiz18:
I'll give these all a try and report back, but one other question....

I assume if I make it into safe mode, I uninstall the modules and then try to reboot normal correct?

Thank you guys for the prompt reply...

ill let you know how it goes....
[Google Pixel 7 Pro] Fishawy:
Adding to the two above posts with suggestions, I initially had a similar behavior.

In my case, after hours of trying, I found out that Magisk (both stable and Canary, not Delta, downloaded from the original Github website), were - for some very weird reason - automatically installing the Magisk Bootloop Protector module, immediately after flashing the patched image, which caused my bootloops (funny enough it was the only Magisk module installed). That was using both adb/fastboot commands and the great PF tool here.

I suspected that I was doing something wrong. Factory reset, deleted and re-downloaded everything, especially Magisk. Setup went fine. Patched the init_boot, flashed, fine. Reboot, again bootloop (because of the same module). I couldn't figure out why, and the people I asked for assistance couldn't replicate or explain it.

I managed to remove it, and finished setting up everything, apps settings modules and all. Two days later, tried to flash that module again, bootloop.

Right now I'm living with a rooted P7P using Magisk Canary and without this bootloop protector, which is an acceptable price. I'm only mentioning this because it sounds similar to your issue, so hopefully this helps.
[Google Pixel 7 Pro] spdwiz18:
Thank you guys. Got it going. It finally managed to run the adb.exe wait-for-device shell magisk --remove-modules command. Then booted just fine.

Lesson learned for the next update.
[Google Pixel 7 Pro] Bxperiaz3:
Hi could you elaborate on what isn't working anymore? I used Aosp mods a lot and don't want to lose a lot of its functionality if I update. Thanks
[Google Pixel 7 Pro] cmh714:
More things are working with Magisk Canary and the AOSPmods canary version.....YMMV
[Google Pixel 7 Pro] Bxperiaz3:
I must check that out thank you
[Google Pixel 7 Pro] Bxperiaz3:
I'm rooted and looking to update from the October firmware. Do I need to flash November first or can I skip straight to December?

Also the December 02 UK firmware, is this for all UK based phones or does it mean O2 as in the network provider? Thanks
[Google Pixel 7 Pro] Bxperiaz3:
Thanks, I'm gonna try it this evening. Can I just go from October straight to December build?
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Once again a big resounding earth shattering YES. Happy Holidays!
[Google Pixel 7 Pro] Bxperiaz3:
Legend. Same to you!
[Google Pixel 7 Pro] schmeggy929:
You do not need to relock the bootloader. I would also advise to never relock the bootloader again( unless to plan on selling or open a RMA to get it repaired.
[Google Pixel 7 Pro] justDave:
Aren't there applications that detect that the bootloader is unlocked?
[Google Pixel 7 Pro] schmeggy929:
There are a few apps, no matter what are smart enough to detect root and or Bootloader unlocked. If you absolutely need that app to work, say goodbye for now to root and relock the bootloader. Exception number 3, haha. I was referring to the OP relocking the bootloader to switch to beta.
[Google Pixel 7 Pro] alfrqan:
You mentioned "

How to update each month (and also how to root)

" I can not find the root steps! it is missing.
[Google Pixel 7 Pro] EtherealRemnant:
I don't know where you're looking because it's clearly there in Post 2.
[Google Pixel 7 Pro] UltimateGamer83:
its easy to do this once you figure out the whole init_boot thing because the past pixel phones like 5 and below didn't have that.
[Google Pixel 7 Pro] Chris123NT:
Thanks for the well written guide, got unlocked and rooted without any trouble at all and pass safetynet :D
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes.

When I flashed the December update, mine too got to a point in fastbootd where the flash-all.bat errored out trying to flash something. In my case, I switched USB-C cables and I started from scratch with the flash-all.bat and it worked perfectly.

It's very strange because I have 3 USB-C cables, and I've used all three successfully to flash my phone, including the one I was initially using, which I had flashed with in November. Every once in a while no matter which of these three I'm using, I have to switch to another of them in order to flash successfully. I'm more of a whatever works person, so I haven't bothered trying to diagnose anything. I haven't changed the cables themselves at all, I just go from whichever of the three is not working currently to one of the others.

You're welcome!
[Google Pixel 7 Pro] roirraW "edor" ehT:
If anyone hasn't seen this, there's a newer USNF mod by @Displax at XDA link or on GitHub.
[Google Pixel 7 Pro] budmannxx:
I did want to clarify that in my case there was no error in the script. Then PC was just sitting there with the "waiting for device" prompt. Based on the note in the OP about the fastbootd portion taking a few minutes, I just let it sit for a while before disconnecting and reconnecting the OEM cable from Google
[Google Pixel 7 Pro] roirraW "edor" ehT:
@kdrag0n has some interesting work going on for the official Universal SafetyNet Fix (USNF) v2.4.0, that's now in testing.
[Google Pixel 7 Pro] Lughnasadh:
He's released it to his Patreon members. Hopefully it will be released to the general public in a week or two.

Highlights​

Play Integrity bypass without breaking device checks or causing other issues

Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)

Other changes​

Updated instructions for newer Android and Magisk versions

Better debugging for future development

It's taken a while to find way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
[Google Pixel 7 Pro] simplepinoi177:
So for those who are more knowledgeable in such matters, do you experts think/predict that we would go back to using this standard official Universal SafetyNet Fix? Or need to continue to use Displax's mod branched off of kdrag0n's? Or is kdrag0n's incorporating Displax's modifications (from the small changelog Lughnasadh posted and I understand it, kdrag0n is attempting to spoof only when necessary whereas Displax's may spoof it continuously[?]) and using it is essentially the same as using the one with Displax's mod? Or am I just totally off the mark and kdrag0n's official USNF is slated for other devices outside of Pixels? -- When USNF and MagiskHide Props Config stopped working for getting Google Pay to work properly for a window of time there (about 6 weeks), for a small period of time I stepped away from updating my firmware and proper root hiding. When I came back, I found that, while USNF may have continued to work for other devices, Displax's mod was necessary to work for Pixels(?).

Sorry if I may be rather out of touch and/or misunderstanding of the situation; hence the request for some clarification in the pursuit of understanding things better...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I would expect that once 2.4.0 is released publicly, we should probably go back to using the official release, but conversely, as long as something works for you, there's also not necessarily a need to fix what isn't broken. Personally, I plan on switching once it's made completely public.

Note that @Displax wasn't trying to replace the official version - they always kept it the same version as the most recent official along with "Mod", "Mod 2", or "Mod 2.1", so that suggests to me they were merely making temporary workarounds until/if the official was updated.

The methods used in 2.4.0 sound superior to the implementation used in the Mod versions. Some users had previously reported a Mod version making their device at least temporarily reported as a wrong (old) device, and 2.4.0 should prevent that.
[Google Pixel 7 Pro] Displax:
Indeed. My MOD is a temporary solution until kdrag0n release accurate fix.

I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems.
[Google Pixel 7 Pro] Lughnasadh:
Google rolling out Pixel January 2023 update on Tuesday

Per Verizon, the next Google Pixel (4a to 7 Pro) update with the January security patch is rolling out tomorrow...

9to5google.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ1A.230105.002, Jan 2023)	Flash	Link	34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db8793
13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra)	Flash	Link	6632344c9647b04bfce622b0decf3733dfb3bc5c3b2c068ea118f8631c1b39b8

Android Security Bulletin—January 2023 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] dimm0k:
no issues with magisk?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I haven't flashed it yet. I wouldn't expect any problems, but of course, who knows. I'll wait until I hear reports that AOSP Mods works with it without it needing any updating. Anyone else flash it and root yet?
[Google Pixel 7 Pro] 01046:
just had flashed

works fine with magisk, AOSP MODS too
[Google Pixel 7 Pro] LLStarks:
I'll wait for the QPR beta tomorrow.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Hello

I'll probably try flashing tomorrow. With Aosp mods, i have'nt any issue with the december rom before updating app, so i hope it will work too.

My other priority is testing USFN 2.40 because i'have issue to use my bank app since some days.
[Google Pixel 7 Pro] justDave:
Yup. Same here. SN looks ok too.

Dual eSIM is still disabled 😞
[Google Pixel 7 Pro] Lughnasadh:
"Again, we are waiting for official word from Google because there could be additional notes to make here. Verizon’s list is at least giving us a start."

Pixel's January Update Fixes 7 Bugs and Adds Spatial Audio

The January Android update is rolling out now to Google Pixel phones and it brings a bit more than just security patches. Google is addressing several bugs, but as was promised, Spatial Audio is here for devices like the Pixel 6 and Pixel 7. We are still waiting for Google to post... #Bugs #Google

www.droid-life.com
[Google Pixel 7 Pro] justDave:
So... nothing for Pixel 7? 😐
[Google Pixel 7 Pro] Lughnasadh:
Huh?
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Finally, flashing and it works. No issues with Aosp mods and Themer. All my modules seem to work fine. I just have to reimport my settings on Aosp mods.
[Google Pixel 7 Pro] justDave:
You cheated... you changed the link while I was posting. :LOL:

The official announcement you posted first only mentioned Pixel 6 series and earlier. I assume that'll get updated shortly but it's Google so maybe not.
[Google Pixel 7 Pro] cmh714:
you must be looking in the wrong place....its there
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - January 2023 - Google Pixel Community
[Google Pixel 7 Pro] swieder711:
January update works fine. Did the following:

Unhide magisk

Patch init_boot with Magisk

Edit "Flash-all.bat" to "Flash-nowipe" and removed -w and included "fastboot --disable-verity --disable-verification update image-cheetah-tq1a.230105.002.zip"

Flash no_wipe

Fastboot flash init_boot m_init_boot.img

Using the December 1.2.1 Kiri kernel.
[Google Pixel 7 Pro] charlessxavier:
Why is this method preferred over google 's online tool to flash the new update?
[Google Pixel 7 Pro] swieder711:
The steps that I listed are needed for Root and Custom kernel. You can get similar results with the Google online flash tool.
[Google Pixel 7 Pro] rebj2007:
Not sure if this is new but to anyone manually flashing factory images then installing magisk. You can replace the init_boot.img inside the image zip file with patched init_boot from magisk and save an extra step.
[Google Pixel 7 Pro] Schroeder09:
So extract the init_boot.img prior to flashing, send it to the phone, patch it with magisk, put that modified init_boot.img back on the PC REPLACING the Google stock init_boot.img, and run the flash-all.bat file?
[Google Pixel 7 Pro] rebj2007:
Yes
[Google Pixel 7 Pro] Schroeder09:
What's the flash-all no wipe stuff about? That's just you re-naming the batch file so you can keep track of it having been modified? This isn't required. Just trying to be clear.
[Google Pixel 7 Pro] swieder711:
Correct. Just me renaming the file.
[Google Pixel 7 Pro] PurppleMonkey:
So, you have to :

1) DL the update

2) Unhide Magisk

3) Patch the init-boot

4) replace the init-boot

5) use the online google tool

6) ???

Héhé, not sure what to do
[Google Pixel 7 Pro] chabuje99:
I would use PixelFlasher, it will make your life much easier for updates
[Google Pixel 7 Pro] Sh0X31:
yes I downloaded P6 image xD
[Google Pixel 7 Pro] Schroeder09:
Okay, I'm going to update today, and I have some questions about your method.

1.) To unhide magisk are you just unchecking the "enforce denial list "option in majisk?

2.) After you patch the init_ boot.img with magisk, are you sending it back to the computer? You dirty flash (no wipe) and disable verity and verification and then fast boot flash the patched image just like the first time you root?

3.) At any point, did you disable your magisk modules?
[Google Pixel 7 Pro] Tracker31:
1. just click unhide magisk in magisk settings.

2. yes you flash patched init_boot to init_boot partition. Yes you have it in platformtools folder to ensure flashing.

3. you can do it whenever you want but before flash-all.bat file
[Google Pixel 7 Pro] justDave:
This right here ☝️

I used PixelFlasher for the initial setup and rooting and for 3 monthlies now. So easy.
[Google Pixel 7 Pro] whitewallman:
"fastboot --disable-verity --disable-verification update image-cheetah-tq1a.230105.002.zip" will adding this wipe the device? I've never added this before.
[Google Pixel 7 Pro] Tracker31:
yes if you disable verity for the first time the device will be wiped same as unlocking bootloader
[Google Pixel 7 Pro] bradhoschar:
Not sure what I did wrong....

Disabled all modules

unhid Magisk

flashed Jan. thru Pixel flash tool

patched boot_init in Magisk

copied to adb/folder

renamed to just magisk

ran in bootloader: fastboot flash boot_init magisk.img

got following errror
[Google Pixel 7 Pro] cmh714:
possibly old version of the Tools...

****EDIT -- its init_boot NOT boot_init
[Google Pixel 7 Pro] bradhoschar:
Thanks, I mistyped my comment. I did use init_boot in my cmd.

It WAS an older version of platform tools. Update worked! Thanks!
[Google Pixel 7 Pro] Schroeder09:
This worked for me. I should not in addition to this after unhiding magisk I disabled all the modules I have. Then I proceeded with these steps which are also outlined in the OP of this thread. I too flashed the kiri kernel. all is well as of now.
[Google Pixel 7 Pro] hpower1:
what is everyone seeing so far for Jan update, I'm still running on Nov.
[Google Pixel 7 Pro] Schroeder09:
I don't notice anything different. Been on January for like an hour but December was a downgrade from November. All kinds of wakelocks once I went to December. November battery life was absolutely insane. Still good, but man November build was great.
[Google Pixel 7 Pro] hpower1:
good to know, thanks. Biggest issue I have with Nov is when in car using android auto (wireless) screen will unlock but stay off, so if I need to use the phone, i'll have to press the power button. Not all the time, but most of the time.
[Google Pixel 7 Pro] whitewallman:
It's fastboot flash init_boot, not boot_init
[Google Pixel 7 Pro] otonieru:
Am on 2.4.0 along with January Updates. So far working fine, although i didn't notice difference compared to Displax's modded version. But am just happy to support the project and being on the bleeding edge of the release, lol
[Google Pixel 7 Pro] Paz9:
Can I flash this ontop of beta?
[Google Pixel 7 Pro] LLStarks:
Can be risky or force a wipe.
[Google Pixel 7 Pro] Lughnasadh:
If you are talking about the January update, then yes. You can use flash-all and Android Flash Tool (Pixel Flasher as well I would imagine) to return to a public build.
[Google Pixel 7 Pro] Paz9:
Without a wipe?
[Google Pixel 7 Pro] Freddzen:
Hi guys, first of all: thanks to all of you for your work and tutorials, this helps a lot of people!

I have a question regarding unroot:

I would like to unlock my bootloader, root my pixel 7 pro, then unroot it and relock the bootloader, so no one can see that it was ever rooted. Is that possible or is it still possible to see that it was rooted?

Background: I need root access because I accidentally did a factory reset (please do not ask, stupid like ...). Now I want to restore some data and therefore need root.

Thanks in advance for your help.
[Google Pixel 7 Pro] Lughnasadh:
If using flash-all, you can without wiping by removing the "-w" from the flash-all.bat script. If using Android Flash Tool, you'll have to wipe.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Hello

Relock bootloader will wipe your data, so it's not the solution to restore your backup.

Wich method did you use to backup data?
[Google Pixel 7 Pro] Freddzen:
That would be no problem because I just need root to access the "deeper" storage. (hope any tool like DroidKit, Dr. Fone etc works).

I would backup all relevant data (photos etc) - after that it is completely irrelvant for me if I have to wipe the phone again when unroot/relock bootloader.