yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to/adjusted Post #3 - Other, most important resources:

Find problem apps, Magisk, and LSposed Modules by (three different methods)

:

Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can re-enable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

You can also follow @Jon8RFC's advice:

Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does.

(May only be for mis-behaving LSposed modules):

Thanks @siavash79!
[Google Pixel 7 Pro] xdrc45:
Glad it worked for you! So you ended up flashing patched init_boot to slot "a" and "b"?
[Google Pixel 7 Pro] State.of.mind:
Yup!
[Google Pixel 7 Pro] Schroeder09:
Anyone running lsposed with xprivacy Lua and/or AOSP mods (saw some reports that this is half working on the December update) are they working without issue?
[Google Pixel 7 Pro] xdrc45:
On Dec update and running AOSP mods. Some of it is working fine and some is not I guess. So far the status bar mods are working fine. Like clock and battery customizations which are the main ones for me. (Mostly use it to hide battery icon and use energy ring and to add am/pm to the clock. On theming most of the icon shapes and signal icons work fine. Some don't change anything at all. Don't really use much more than that. Will look more into xprivacy and test it out.
[Google Pixel 7 Pro] Schroeder09:
Have you used xprivacy before? Developer just dropped it, and the people over there are bummed. I joined the party late. I'm using it, and I too really like it. You should check it out, install, and get the pro app. Worth it and very cool.
[Google Pixel 7 Pro] xdrc45:
No I haven't. I will definitely check it out
[Google Pixel 7 Pro] pp085ster:
Wondering if anyone else is experiencing the same issue, but on my Pixel 7, when I connect via bluetooth to my high fidelity headphones, for the first minute or two, I get this awful stuttering and glitchy sound which eventually normalizes, but it drives me mental while it's happening.

Only solution I have found so far is to switch the "HD audio" option off in bluetooth device settings (which reverts to SBC codec), but considering I am just playing 320kbps mp3's, it seems ridiculous that a modern device can't handle that and that I need to revert to an outdated codec with sketchy quality to get a smooth listening experience.

I have also tried switching from aptX HD to aptX codec in Developer Settings (which fixes the issue), but the change doesn't stick once I disconnect and reconnect. I have tried altering other settings, but nothing seems to make much of a difference.

Any suggestions/solutions are highly appreciated. I'd like to go back to being a sane person 😅
[Google Pixel 7 Pro] dantevn:
If I understand this correctly, rooting my phone disables OTA?
[Google Pixel 7 Pro] simplepinoi177:
Correct; You are unable to take OTA's using the System Update in the OS -- but if taking OTA's specifically are essential/necessary to you (versus updating using the Full Factory image), you can still apply them by "sideloading" the OTA's...

In all cases, you will lose root and have to re-root after each update...

*no longer can you do Magisk's "Install to inactive slot (after OTA)"...
[Google Pixel 7 Pro] cyr4n0:
I have a brand new unlocked Pixel 7 Pro with version TQ1A.221205.011 that I updated with eh android flash tool. I unlocked my bootloader. And now when I try to flash the magisk patched init_boot.img it bootloops. I have tried flashing it from fastbootd and bootloader modes. I've tried flashing it to both a and b init_boot partitions. I can only get it to stop bootlooping if flash the unpatched ini_boot image. Can anyone help me?
[Google Pixel 7 Pro] madmuthertrucker:
So you can still get into the bootloader, and it's unlocked? Re-flash TQ1A.221 205.011 make sure it boots up and try again.
[Google Pixel 7 Pro] simplepinoi177:
I hope to not come off as insulting your intelligence and/or put up such an obvious blunder -- but you'd be surprised how many people (even the number of people specifically on this thread) have made such errors...

I have a feeling & it feels like you may be flashing the init_boot.img to the boot partition. Your "symptoms" sound a lot like in the beginning when most people coming from previous pixels were patching the boot partition still and it would bootloop, but once the stock boot.img or init_boot.img was flashed back, it would stop bootlooping.

If that's not the case, I imagine either re-patching the .img through Magisk again -- it might be akin to the same blunder and you might accidentally be patching the boot.img and not the init_boot.img -- or re-downloading the Full Factory image, confirm the checksums are the same, and re-extracting the stock init_boot.img again.

If you are doing all the right steps and getting the right files from all the right sources, it should be working for you the same as it is for 99% of the people here...

Good luck and hope it works out and this helps...
[Google Pixel 7 Pro] Fishawy:
I had the same exact problem on my 7 Pro, same build, and found out that when I flash the patched init_boot.img, Magisk (both Stable and Canary) automatically installs the Magisk Bootloop Protector module, which makes the device reboot after 20-30 seconds of booting up, and repeats indefinitely.

This happened both with fastboot commands and Pixel Flasher by the way, weirdly enough.

Removing that module stopped that from happening. Hope this helps.
[Google Pixel 7 Pro] LLStarks:
Something is happening
[Google Pixel 7 Pro] Lughnasadh:
Factory Images for QPR2 Beta 1 are up.
[Google Pixel 7 Pro] LLStarks:
The first curiosity:

radio-panther-g5300n-221110-221114-b-9288193

From g to n.

Edit: 3CA is here! Thanks, Milan.
[Google Pixel 7 Pro] cyr4n0:
How are you removing the module? I can't get adb shell from the bootloader. So I am not able to run the command

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

I'v tried using all of the following commands

fastboot flash init_boot magisk_patched-25205_tEsoY.img
fastboot flash init_boot_a magisk_patched-25205_tEsoY.img
fastboot flash init_boot_b magisk_patched-25205_tEsoY.img

I've reflashed with the factory image a couple times and rebuilt the magisk init_boot.img with both canary and stable Magisk. WIth the same results every time.
[Google Pixel 7 Pro] NepoRood:
I read that after I posted, was kinda just giving crap as well, lol
[Google Pixel 7 Pro] mko000:
Nandroid backups are nice, but is there any other reason to use TWRP now? I guess if you don't want to use a PC to flash...
[Google Pixel 7 Pro] emrexcem:
How is wanting control over my device and expecting services that I pay for work with my device my fault?

Ps I also didn't know apps such as play store had such high privileges to check if my bootloader was unlocked. That bummed me out.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@NepoRood Please don't respond to that. No arguing in my thread.
[Google Pixel 7 Pro] roirraW "edor" ehT:
All:

When a situation is just fine already, there is no use for anyone to add any non-constructive comments. The + Quote and Insert Quotes buttons are made for this situation. Click the button, then continue reading and see what the result was, and then if the situation is resolved, don't bother adding unneeded criticism.
[Google Pixel 7 Pro] xChickens:
So we're unable to pull the ROM off our phones to get the boot.img? Should I do the OTA update?
[Google Pixel 7 Pro] ScottIsMyName:
You can pull the boot.img off your phone once you have root ;)

In all seriousness, if you want to root/unlock the bootloader, I suggest the following:

1) Go through the initial setup, skipping everything possible

2) Take the system update

3) Reboot

4) Enable developer options (tap on build number 7 times)

5) In developer options, enable oem unlocking, adb debugging

6) adb reboot bootloader

7) fastboot flashing unlock

8) fastboot reboot

9) Repeat steps 1,4,5 (for adb debugging)

10) Sideload magisk (adb install magisk.apk from your pc)

At this point this is all I'm doing with the phone. Once factory images are available (hopefully tomorrow, the next steps I will take are):

1) Patch boot.img with Magisk and download to PC.

2) Apply factory image, allowing my phone to be wiped again, but adding the --skip-reboot option to the flash file

3) Apply magisk boot img

4) Go through phone setup process as usual

5) Reinstall magisk
[Google Pixel 7 Pro] jlokos:
When the factory images are available, why not simply patch boot.img with Magisk, fastboot flash boot --slot=all [patched boot.img] and reboot ?
[Google Pixel 7 Pro] ScottIsMyName:
Because I don't want to go through all the setup if root is not going to work. I'll stick with my current pixel 5 while it gets worked out
[Google Pixel 7 Pro] jlokos:
Understood. If you go into a boot loop, you can always re-flash the the factory boot.img. Or you can simply wait until someone else tries to root 😊
[Google Pixel 7 Pro] EtherealRemnant:
Just take the patched image, fastboot boot boot.img, run Magisk, direct install?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Once we have a boot.img to patch with Magisk, yes. This is the method I outline in post 2.
[Google Pixel 7 Pro] ScottIsMyName:
Last year the pixel 6 didn't have working root for a few weeks of I remember correctly, so I'm going to wait to migrate until after I have root. Right now my phone is simply ready to go whenever that might be
[Google Pixel 7 Pro] roirraW "edor" ehT:
The reason for that was because Magisk Canary needed more work in order to be Android 12 compatible. Android 12 had only come out 23 days before the Pixel 6's release date.

This time, the changes between 12 and 13 didn't require a new version of Magisk in order to work, and Android 13 has been out for ~58 days, give or take (since August 15th).

It's still possibly Magisk might need modifications because of some Pixel 7-specific changes, but it's less likely than with the 6.

Hopefully, we can tell you tomorrow if root with Magisk Stable (or Beta, or Canary) is working.
[Google Pixel 7 Pro] simplepinoi177:
Thanks for this list of steps/breakdown....it seems sensible.

I just had one question on one of the steps though, if you (or anyone) could clarify...

for doing step #2

before

#5, just wondering why one would, or should, push off ticking the "oem unlocking" until after doing the system update?

I was under the impression that ticking of the "oem unlocking" stays unticked through updates; would make little sense if one would have to do it after each update....

I know it's not really consequential to do it before or after, I was just wondering if there was a particular reason going over my head....Thanks!
[Google Pixel 7 Pro] Annie the Eagle:
My phone has arrived! Now I will unlock the bootloader and await the firmware image for the boot.img
[Google Pixel 7 Pro] Ghisy:
(NOT VERIFIED)

I read on Telegram that the Pixel 7 series uses an init_boot.img instead of a regular boot.img. Apparently, it's this new init_boot.img that needs to be patched for root.

I guess we'll find out later today!
[Google Pixel 7 Pro] edcsxz:
root success
[Google Pixel 7 Pro] KHANrad_SIN:
How did you get the boot.img? I don't see it yet on google's website.
[Google Pixel 7 Pro] Paz9:
What's taking them so long to release the fw
[Google Pixel 7 Pro] EtherealRemnant:
3CA NR?
[Google Pixel 7 Pro] LLStarks:
Yes it is.
[Google Pixel 7 Pro] EtherealRemnant:
Flashing lol
[Google Pixel 7 Pro] Fishawy:
I have about 20-30 seconds after the phone starts before it automatically reboots, so I quickly went into Magisk, removed the module and rebooted.

Is your issue also related to that module?
[Google Pixel 7 Pro] cyr4n0:
My phone doesn't get past the Google logo before it reboots. And I've never installed any magisk modules myself.
[Google Pixel 7 Pro] EtherealRemnant:
Strange that you guys are experiencing that module being installed automatically because it's never happened to me yet.
[Google Pixel 7 Pro] madmuthertrucker:
I don't get what is going on with you guys. I unlocked the bootloader then installed the latest update. I downloaded magisk stable from the TJW official github and and patched the init_boot.img no problem, no extra modules. I'm one of the less knowledgeable guys but I will tell you what I would try. Here we go. Completely uninstall magisk. Completely. Re-flash the latest factory image. Complete wipe with

-w still in. Then download magisk patched stable from official site. Patch init_boot.img again. And flash it. Be careful. Double check everything. Use only everything from your latest attempt.
[Google Pixel 7 Pro] simplepinoi177:
Your issue is really confounding....

I'm just going to "spit" some ideas out here just to eliminate even the most basic and apparent, even if they are fairly obvious and/or might be dumb me mentioning...

One thing that popped into my head is to ask where are you downloading Magisk? Hopefully from Github...if not, maybe the copy you're using is not genuine and is modified somehow; even if it's just a little bit, it might've changed the code just enough...you know?

In your initial post, you state that you were updating using the Android Flash tool, but have since "reflashed with the factory image a couple times" -- are you still "flashing" it using the Android Flash Tool or manually?

If you were using the Android Flash Tool, maybe you are downloading the Full Factory image that's different than the one used/chosen with the Android Flash Tool -- hence different init_boot's that are required... If this is the case, I would suggest making sure you have the most up-to-date platform-tools (you would be surprised how many obscure issues arise from not having the most up to date versions) and manually update using the Full Factory images you downloaded; i.e. run flash-all. It might be a good idea to keep the "chain of evidence" together from applying a certain Full Factory image to extracting the image file from that image and patching it -- one sequence directly to the next.

If you weren't using the Android Flash Tool and flashing manually, I hope you did as I suggested and, when re-downloading the Full Factory image, confirmed the checksums -- even the slightest difference or miniscule corruption might make the update/flash work for the most part, but be just different enough to be a corrupted image file and hence corrupted patched image file...Also, as I've said before, you want to be sure to have the most up-to-date platform-tools...

I prefer to manage things manually on my own as it helps me understand things thoroughly, but if all of this doesn't lead anywhere successful, you might want to consider using PixelFlasher to root; maybe the GUI might succeed for whatever reason (it employs various checks against incompatibilities or misfires) where however you are going about is mis-stepping.

That's all the ideas I have for now...hopefully you get it working and figured out and this helps in some way...

BTW, I think you're able to run adb commands in recovery mode; but I could be wrong in terms of which adb commands or anything outside of sideloading....but it doesn't really matter as it seems you don't have any modules installed to be causing these issues to begin with...
[Google Pixel 7 Pro] Ghisy:
What's 3CA NR?
[Google Pixel 7 Pro] sensation4gking:
Obviously wasn't expecting anything but installing the android beta doesn't remove the unlock restriction on Verizon. I was thinking it would completely replace the Verizon software but no.
[Google Pixel 7 Pro] cyr4n0:
I used the Android flash tool once, to upgrade to the latest firmware. Since then I've been using the factory image to reflash with the accompanying batch file.

I have not checked the checksums as of yet. I'll do that later today and report back.

I've been downloading Magisk exclusively from GitHub.

I had thought it was the version of adb/fastboot that I had but I've since downloaded the latest version and forced it to use that version in my command a la ./adb.exe and ./fastboot.exe

I'll retry downloading the factory image checking the checksums and fully install the latest adb/fastboot. If that doesn't work I'll try the gui you mentioned.
[Google Pixel 7 Pro] cyr4n0:
I deleted all the existing files I had; magisk, factory image, etc. Upgraded adb and fastboot that was installed in the system path. Reimaged and wiped data with PixelFlasher. Verified the checksums matched. And then used PixelFlasher to flash the magisk patched init_boot.img and it works now. Not sure which portion of it was the snag but it's working now. Thanks for all the help!
[Google Pixel 7 Pro] pp085ster:
Read this
[Google Pixel 7 Pro] simplepinoi177:
Good ol' PixelFlasher...! What a great tool of @badabing2003's has ended up being! It is assisting seemingly countless people! I had a feeling it might succeed wherever misstep or snag might have been tripping things up...

I am very happy that you got it working in the end and very welcome my suggestion ended up helping...!
[Google Pixel 7 Pro] Dark_Eyes_:
Still no joy here for the Unified Security & Privacy menu. Tried updating everything, FC Settings, reboot, nothing works. Should I start to worry?
[Google Pixel 7 Pro] JakeDHS07:
Mine should showed up yesterday after checking and installing a play system update
[Google Pixel 7 Pro] Ghisy:
Same here, updated my P7P on Monday. I don't really mind though, it'll show up when it shows up!
[Google Pixel 7 Pro] dnewell:
I'm trying to unlockl the bootloader. When I first connect the phone, I can do 'adb devices' on my pc and it returns:

List of devices attached

1818FDH.... device

I then boot into fastboot mode, and type 'fastboot devices' but nothing is returned. If I type 'fastboot flashing unload', it just returns

waiting for any device

Any help would be appreciated.
[Google Pixel 7 Pro] simplepinoi177:
Sounds like a driver issue....

It looks like you're using Windows, but it would be good to confirm that you are...

If it is a driver issue, open up your Device Manager, what does it say under "Android Device" -- it should say "Android Bootloader Interface"? If it doesn't show that, is there any device that has a question mark or exclamation mark? If so, you most likely need to update or replace that driver specifically with the Google Windows USB drivers (you can get find a link to in the OP)... If nothing is showing, you may need to "Show hidden devices" and either uninstall (and delete, if possible) the existing devices/drivers under Android Device and attempt for Windows to detect them when in the bootloader/fastboot mode or attempt to update those drivers manually by directing them to where you extract the Google Windows USB drivers .zip file. You will find detailed steps to do just that under the "Unlocking Bootloader" section in the OP...

UPDATE: Glad you figured it out in the other thread you created....albeit being resolved with the same advice I gave in this post...😕

but putting this update here just in case someone else peruses the thread here having the same issues and needing to resolve the same problem...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I just now finally updated my P7P to December. I've been busy, plus I had been waiting for the compatibility of AOSP Mods.

I switched slots and rebooted to bootloader, as I did last month, and then used the modified flash-all.bat. I did exactly the same steps the first time I flashed to the other slot than what I had most recently been running and didn't encounter any issues. I thought this was the case at the time, but I wasn't 100% certain until I ran through the steps again, so I'll wait to see if anyone else ever confirms having an issue the first time switching slots and rebooting to the bootloader.
[Google Pixel 7 Pro] Lughnasadh:
Sounds good 👍

Just to be clear, if you are manually setting your active slot to the other slot to flash the factory image via flash-all to that opposite/inactive slot, there's no need to reboot into the bootloader after switching slots. You can just switch slots and flash. At least this has been my experience.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Okay, I don't know why I thought I had to reboot into the bootloader after switching slots, but since it definitely does indicate the new slot immediately after performing the command, I completely believe you! :) I'll change the instructions.

Thanks!
[Google Pixel 7 Pro] badabing2003:
Another thing to keep in mind with dirty flashing is that, even if you flash to inactive slot, you can only successfully boot (to system) to the latest slot that you just flashed to for two reasons.

system_other image gets written to the previous system partition which includes the optimized dex files for copy after successfully booting to system, effectively making that partition unbootable to system (similar to how factory shipped phones are unbootable to the inactive slot).

Because of AVB on phones that shipped with Android 10 or newer.

With older phones, if you remove the system_other image from the factory file and then flash, you can boot to both partitions, I verified this by booting Pixel XL to patched system on one slot and unpatched one on the other. Too bad we can't do the same with the newer phones.

Credit goes to @capntrips for providing valuable guidance.
[Google Pixel 7 Pro] Lughnasadh:
This is a good point. I remember with my Pixel 2 XL I could switch slots and just boot up into that new slot without having to flash anything. Also very convenient if you wanted to test a custom rom or just test out a new update to make sure there are no bugs. If there were bugs you could just switch to the old slot with the previous month's build on it without having to flash anything.
[Google Pixel 7 Pro] Schroeder09:
Is it normal that Google services framework unchecks itself from the denial list? After following this method? The OP mentions that Google Play services might do this, but it doesn't mention Google services. I'm just double checking.
[Google Pixel 7 Pro] JakeDHS07:
Yeah the safety net fix denies them in the background and unchecks them. No worries
[Google Pixel 7 Pro] Nekromantik:
If I flash QPR2 Beta, do I need to wipe to go back to December stable version?
[Google Pixel 7 Pro] Aerosilver:
Does this happen to anyone else with the player? Im on beta
[Google Pixel 7 Pro] budmannxx:
I waited about 15 minutes at the fastbootd screen (on device) and "waiting for device" in Windows before finding this trick--unplugging and reconnecting the device caused the flash-all.bat to continue for me. I was nervous to even do this--wasn't sure how long to wait.

EDIT: fastbootd screen (not fastboot)
[Google Pixel 7 Pro] badabing2003:
I'm seeing more and more reports of flash-all script getting stuck waiting to detect fastbootd mode, specially so on Mac.

In your case unplugging / plugging it probably reloaded the driver and the fastboot.exe which was waiting for fastbootd, detected it and continued.

Make sure there were no errors.

Unfortunately this trick does not seem to be working on Macs.
[Google Pixel 7 Pro] aorifan:
Hi guys, I have rooted my phone with mgisk. Now the system tells me there is an OTA update. How can I install this update? Direct install failed.

Thanks in advance.
[Google Pixel 7 Pro] badabing2003:
Post #2
[Google Pixel 7 Pro] aorifan:
thanks will check it out