yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
You should hide your serial number that's listed after the ADB Devices and Fastboot Devices command, too.

The problem may be if you're using PowerShell instead of Command Prompt. In PowerShell, I believe you have to enter a ..\ before commands, or at least before some of them - I could be wrong, though. I keep it simple in Command Prompt.

Edit: Could also be too long of a path/folder structure. Try right off the root of the drive, and without spaces in any folder names, such as C:\platform-tools\....
[Google Pixel 7 Pro] Lughnasadh:
Haha, I just edited my post after I saw the screenshot to suggest command prompt instead of PowerShell.

Ninja=74

Me=0

😆
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! Ninja twins?
[Google Pixel 7 Pro] xstefen:
Correct in regards to partition by partition, as I believe I read somewhere using fastboot update or fastboot flashall will reenable the verity flags this will do basically the same ensuring they remain disabled, I think
[Google Pixel 7 Pro] SOCOM-HERO:
I was able to resolve using ADB and Fastboot ++
[Google Pixel 7 Pro] roirraW "edor" ehT:
Cool, thank you. fastboot update can keep Verity and Verification disabled as such:

fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification

I have no idea how/if that works with custom ROMs, however, so yeah, best stick to what's safe.

Is that some third-party ADB/Fastboot redistribution? Lots of us highly discourage the use of those, but I understand if it somehow resolved the issue - although that would be puzzling as there is nothing wrong or missing with the official distribution. Glad you got it solved.
[Google Pixel 7 Pro] xstefen:
Good deal, wasn't sure, touché
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's always good to have other options. I wouldn't know about that either if it hadn't come up a bunch in the last year on the Pixel 6 Pro.
[Google Pixel 7 Pro] SOCOM-HERO:
yeah I don't like using tools like that but it is an XDA project.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's good, at least. Thanks for sharing that!
[Google Pixel 7 Pro] m3ath:
Can anyone help me what codes are available for the pixel 7pro?
[Google Pixel 7 Pro] SkylinesHD:
Pixel 7, but should be same on pro
[Google Pixel 7 Pro] Lughnasadh:
Pixel 7 Pro
[Google Pixel 7 Pro] SkylinesHD:
are you on beta? might be useful to mention it.

(My screen is from stable)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to thanks and to Post #3 - Other, most important resources:

A list of other important apps

@Chainfire's thread [APP][5.0+][2020.12.22] CF.lumen v3.74 - I used to use this app to enable my phones to go extra dim before Android developed better native capability for that, and the app has been confirmed to work on the Pixel 7 Pro for color control, too
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #3 - Other, most important resources:

How to determine if you already have Verity and Verification disabled

(required for custom kernels for now)

Alternative two more manual ways of checking:

Thanks @capntrips for the Magisk Module to check Verity and Verification status!
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Quick question, while doing monthly updates through flash-all by removing -w is it required to unhide magisk? Disabling modules yes but as long as you are not upgrading magisk in which case one has to unhide is it required to unhide magisk during monthly updates retaining root?
[Google Pixel 7 Pro] bleez99:
Actually, neither. Once you're set up and stable, no need to do anything extra.
[Google Pixel 7 Pro] roirraW "edor" ehT:
As @bleez99 said, no need to unhide Magisk whether doing the monthly update or updating Magisk. If I remember correctly (Magisk Stable updates aren't frequent, and I don't use Canary except when absolutely necessary), at least one time about a year ago when Magisk Stable wasn't yet Android 12 compatible, if you had Magisk Canary hidden and tried to update, there were issues that didn't happen if it wasn't hidden, but I think that was a temporary bug, and that I may have updated since then without unhiding just fine. I can't swear by that, however, but I'm mostly sure.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Arm reportedly changing licensing model to prohibit custom GPUs and TPUs, could impact Google Tensor

A lawsuit has revealed that Arm is apparently changing its licensing terms so that what makes the Pixel's Google Tensor unique...

9to5google.com
[Google Pixel 7 Pro] badabing2003:
Disabling modules is actually recommended, at least some modules, there has been cases (audio related modules come to mind) where keeping the modules enabled while applying the monthly updates caused bootloops..

Unhiding Magisk is not necessary unless you are upgrading Magisk.
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you find the person, we'd love to get clarification from them. 😁

I preferred to boot even my own Magisk'd image and then direct install, previously, too.
[Google Pixel 7 Pro] KyleSEES:
Hello guys

i'm trying root my Pixel 7, but it's stuck in fastbootd.

command shown as below.

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

did I make someing wrong...
[Google Pixel 7 Pro] simplepinoi177:
what does it say in your command prompt or powershell? is it still flashing parsed parts? if it is still flashing, I would leave it. DO NOT do anything or select anything on the phone when in fastbootd mode....

I've seen some people have to unplug and replug the phone at this point sometimes...
[Google Pixel 7 Pro] Ghisy:
Hey,

I finally had time to upgrade to my Pixel 7 Pro from my 4 XL! 🥳

Used Swift Backup and it worked very well.

I'm just seeing something weird with Twitter notifications: everything is ticked in the app and system but I'm not getting any sound or vibration when I have a notification. They don't show up as silent.

Is that something Swift may have screwed up? Should I reinstall Twitter from scratch?

Edit: nevermind, "people you follow" notifications were different from regular ones for some reason. I enabled sound and vibration for them in settings. Let's see.
[Google Pixel 7 Pro] KyleSEES:
I think i put some wrong file inside the platform folder before i flash.

I reflashed the factory image and it's boot normaly.

But I still have a question when install magisk.

After patch the init_boot.img, It said make the Modules updated and disable.

but the Superuser and Modules logo is gary out, is it normal?
[Google Pixel 7 Pro] HipKat:
I'm sure this is covered in here, but it's 5AM...

CTS Profile match failed

MEETS_DEVICE_INTEGRITY red X

What did I miss?
[Google Pixel 7 Pro] roirraW "edor" ehT:
If this is your first time rooting this device, then you have no Magisk Modules to update or disable. That instruction is if you're updating from an already established/in-use firmware to a newer firmware. Basically, I have that instruction in the wrong place, and I'll clarify the instructions to make it clear that part is for updating from one already rooted firmware to another (where a Magisk Module previously working might bootloop on a new firmware).

Thanks for bringing it to my attention. Edit: I've adjusted those instructions now so that they're the first steps, and mentioned that they're only for updating when you're already rooted.

Glad you solved your other problem.

It's hard to say. Did you try:

Sometimes, clearing app cache and/or data for apps like the Google Play Store, GPay, Wallet and others (and then rebooting) after these steps may help pass SafetyNet as well.

Coffee? :)
[Google Pixel 7 Pro] xgerryx:
Not sure i see a section about how to unroot and relock bootloader. I believe I will be sending my unit back for now so I will need to do that.

Flash factory image>reboot to fastboot>fastboot flashing lock?

Can someone correct me?
[Google Pixel 7 Pro] Ghisy:
I thought I'd ask here: is there any way to have the default app picker from Android 11 on 13?

I set Bromite as my default browser but I can't seem to clear defaults as I did on 11. Sometimes I like being able to open a link with Chrome (mostly for websites in a language I don't understand). Did Google remove this option?
[Google Pixel 7 Pro] Lughnasadh:
The easiest way would probably be to use Android Flash Tool. You can select wipe and lock bootloader in there.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hello! I don't have a section on it, but yes, that looks correct to me. You can alternatively use the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own).

Select the options to:

Wipe

Force flash all partitions

Re-lock bootloader

Edit: I figured it was @Lughnasadh who Ninja'd me, so I took my time with the rest. :D

Good question! I'm not finding the right place to clear the default browser, either.

Edit: Try these instructions:

Set or clear default apps - Pixel Phone Help

If you have more than one app that does the same thing, you can pick which app to use by default. For example, if you have multiple photo editing apps, you can choose which one to use to open a

support.google.com
[Google Pixel 7 Pro] HipKat:
Coffee, check!

Clearing cache, I'll give that a shot
[Google Pixel 7 Pro] Ghisy:
:(

I'll look around and post here if there's a workaround!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Don't forget to reboot after. Good luck!

I had made an edit above that you might not have seen:

Try these instructions:

Set or clear default apps - Pixel Phone Help

If you have more than one app that does the same thing, you can pick which app to use by default. For example, if you have multiple photo editing apps, you can choose which one to use to open a

support.google.com
[Google Pixel 7 Pro] Lughnasadh:
If you are rooted, do you have Displax's USNF mod installed?
[Google Pixel 7 Pro] Ghisy:
Yup, found that page. I don't have the "open by default" option for the browser.
[Google Pixel 7 Pro] roirraW "edor" ehT:
And specifically Displax' USNF MOD 2.0, referenced in my instructions, and not their original MOD 2.0 which had a bug?

Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

SafetyNet

Mmmmmm, me neither. Indeed :( I hate it when Google's (or any company's) pages aren't up to date, or at least specifically call out when the instructions might not apply, like with what apps.

Edit: I just submitted feedback to them at the bottom of that page ("Was this helpful?"). I said:
[Google Pixel 7 Pro] Ghisy:
Oh, good! Didn't see the feedback section, will do the same.

I found this app suggested on Reddit: https://play.google.com/store/apps/details?id=de.ub0r.android.choosebrowser&hl=en_US&gl=US

It uses the share picker so you are able to pick the browser you want. It's OK but it takes too many steps, I uninstalled it. I'd rather copy and paste my link in the meantime.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for the information and review of the app. I'll keep my eye out for anything better.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added

How to unroot

to Post #3 - Other, most important resources.
[Google Pixel 7 Pro] Ghisy:
Found another workaround on Reddit but it involves disabling Chrome (which I don't want to do) but here it is: set Chrome as default then disable it. It will bring the browser picker back, Now I need to find a way to do that with a browser I don't use but I guess only system apps can be disabled...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting! Try Disable Application [ROOT]. It looks like I can disable user apps with it. You could install Brave browser in order to pick to set default, if you don't use it.
[Google Pixel 7 Pro] Ghisy:
Found an app that brings back the old picker for web links!

Open Link With... - Apps on Google Play

Open links in native apps when you're stuck in the browser! 🚀

play.google.com

In the app, go to:

- "App Features", "Set As Browser" then "Enabled",

- go to Apps/Default Apps then choose "Open Link With" as your default browser,

- profit! :)

It sucks having to install an app for that but it'll do for now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thanks again for reporting. I will consider adding these two workarounds to post #3, leading with this one since it seems easier.
[Google Pixel 7 Pro] Lughnasadh:
War and Peace has nothing on this OP (in a good way 😀) 😂
[Google Pixel 7 Pro] roirraW "edor" ehT:
Perhaps I should add the answer to life, the universe, and everything?
[Google Pixel 7 Pro] Lughnasadh:
Now your getting into The HItchhiker's Guide to the Galaxy territory 🤪

You will soon become a cult hero 😁

"The Hitchhiker's Guide to the Pixel 7"
[Google Pixel 7 Pro] HipKat:
I do. I just got rooted late last night and didn’t get a chance to really do anything till this morning when I started working on safety net. But didn’t have much time before I had to start getting ready for work so later today I’ll have a lot more time to go through everything else.

I actually have UNSF 2.3.1 From the original thread according to Magisk
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good, that's the issue, then.
[Google Pixel 7 Pro] Bofahad:
THX ALOT
[Google Pixel 7 Pro] HipKat:
Awesome, when I get home from work I will remove that module and flash the correct one.

Speaking of removing modules, LMAO, I got very familiar with rebooting to windows, opening power shell and running ,\ ….shell magisk —remove-modules lol

It seems like everything I learn is through trial and error!
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

If things still don't pass afterwards, you may have to re-wipe cache and/or data for the apps specified, and reboot again. Even then, sometimes users don't pass immediately but do within a few hours.

Heh. :) What's your usual OS (since you have to reboot into Windows)?

Yeah, it sucks a little having to re-install all modules, but less than having to reconfigure some or all of my widgets in Nova Launcher Prime. I recently tried some Magisk Module which kept the phone from finishing booting, so had to remove all modules.
[Google Pixel 7 Pro] xdrc45:
First must say great tutorial @roirraW"edor"ehT Just got my P7P. First pixel device. Have unlocked bootloader and have root. Question. I'm still on the first firmware and want to update. When extracting the init_boot.img from the factory image to the platform tools folder is it okay for the init_boot.img to still be in the factory image or does it need to be removed completely before running the flash-all.bat?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi, and thank you for your kind words.

Keep it in the extracted factory image zip's internal zip as well. You just want a copy of the file handy in order to copy to the phone, run Magisk on it, then copy the Magisk'd init_boot.img back over to the computer.

I hope that helps.
[Google Pixel 7 Pro] xdrc45:
Okay. So run the flash_all.bat with the factory init_boot.img and when that's done then flash the patched init_boot.img afterwards correct
[Google Pixel 7 Pro] roirraW "edor" ehT:
You can patch the init_boot.img at any time, but I just usually choose to successfully boot completely stock (unrooted), and then I patch the init_boot.img with Magisk at that time, copy it back, fastboot boot bootloader again, then fastboot flash init_boot MagiskdInitBoot.img.

But you can copy the init_boot.img over to your phone while you're still on the original firmware if you feel like it, although I would still wait until your phone successfully boots into the updated image before flashing it.
[Google Pixel 7 Pro] xdrc45:
Thank you for the clarification and I appreciate your patience. Still new to flashing pixel device and don't feel like recovering from a soft brick today 😂
[Google Pixel 7 Pro] roirraW "edor" ehT:
No sweat. Continued luck to you.
[Google Pixel 7 Pro] HipKat:
Garuda Linux. I've been running different Arch Distros for about 3 years and I think I'm settled on Garuda as my DD since it comes with Nvidia drivers baked in - which is a pain in the butt otherwise.

Safety net isn't a huge issue, anyway. My bank app still works. Mostly I just want to get it right just to get it right.

Dude, I was freaking out, when it started boot looping and since there's no TWRP Recovery, I was thinking a factory reset was coming til I found the ONE link that said to use Power Shell instead of a CMD Prompt and that cleaned it right up
[Google Pixel 7 Pro] HipKat:
@roirraW "edor" ehT

Flashing the correct mod did fix Safety Net
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting! Thanks.

I understand.

PowerShell instead of Command Prompt? I haven't come across that advice. Do you have a link?

They should, of course, be interchangeable, as long as the user precedes each line with ".. \", as you had said earlier, but I'd be very interested to hear what's said about using PS over CMD. Heck, there's always Microsoft Terminal, too, which from what little I've played with it, is superior to both. 😁

Awesome! Thanks for letting us know.
[Google Pixel 7 Pro] xstefen:
Super props on the Hitchhikers shoutout. Always bring a towel!
[Google Pixel 7 Pro] HipKat:
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)

Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…

www.thecustomdroid.com

Scroll down to the section about using ADB to remove Modules.

The script is actually wrong.

The correct script is

.\adb wait-for-device shell magisk --remove-modules
[Google Pixel 7 Pro] pndwal:
Don't... It's overrated...

If I were you I'd download Magisk from one of the 3300 Magisk forks on GitHub... The challenge of a dirty fork is the only thing that cheers me up... I found one with a python script:

I only do this stuff to keep my mind off things... But it hasn't worked. I have an exceptionally large mind... I guess it beats parking cars...

Don't talk to me about life...

The best conversation I had in 40 million years was with a coffee machine... Helped my analysis of Sirius Cybernetics Corporation's GPP capable personality drives no end, but that didn't really interest me at all despite my being a prototype...

How I hate the night... I get this terrible pain in all the diodes down my left side...

If all this helps someone I shall only be slightly less depressed... but no one ever listens.

😐 Marvin.
[Google Pixel 7 Pro] roirraW "edor" ehT:
😂 👍

I'm still unsure how PowerShell would make a difference. The only difference is that the ".\" would be left off the front of the command on CMD. I did it in CMD. Are you saying you were unsuccessful doing it in CMD but successful on PS?

I did it in CMD when I had to do it recently using:

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

LOL! Nice references. Always look on the bright side of life.

"The first million years were the worst. The second million, they were the worst, too."

"What are you doing in the car park!?"

"Parking cars..."

I think I missed your edit earlier. LOL! Hmmmmm...tempting.
[Google Pixel 7 Pro] HipKat:
When I did it in CMD, (Run as Admin) nothing happened when I booted up. It was only in Powershell that the script ran and cleared the bad Module
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added new reserved Post #8 - Old news from the OP.

Thanks @Oswald Boelcke!
[Google Pixel 7 Pro] djcsurf:
Am finally getting around to sorting out my P7P tomorrow. Have laptop set up with latest Android tools and factory image. Not messed with a phone in 4 years so don't wanna mess it up. Once unlocked is it easier to root then disable Verity, I just wanna do it the easiest and quickest way. I read it's also good to flash factory image to both slots if Installing custom kernel, pixel or android flasher best way to go?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Nice! Have fun with it.

It's neither easier or harder to disable Verity at one point versus another. I suppose it's slightly easier to disable it when you update to the P7P's initial OTA via the factory image zip (don't take the automatic OTA offered, it's slower to take that way).

See Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

Optional steps when updating - flashing custom kernels

At the end of that section is the command you should use to disable Verity and Verification when you update the firmware using the flash-all.bat that comes in the zip.

Starts with:

fastboot update...

For this first time, you can keep the "-w" in the "fastboot update" command line, because after disabling Verity and Verification the first time, you need to factory reset anyway. Every month when you update, you'll have to re-disable them, so use that same command every single month. Otherwise, if you don't disable them, then re-disable them later to use a custom kernel, and you'll have to factory reset again.

Also in that section are the instructions on how to disable them on their own (after you update), if you prefer.

Starts with:

fastboot flash vbmeta...

There is no single best way. It's completely up to the user's preference. I prefer using Google's official tools, driver, and firmware zip directly. Knowing how to do this will make you more comfortable in correcting any accidental mistake you make, if that ever happens.

You can do the flash-all.bat to update the firmware on your existing slot, then fastboot boot bootloader again, switch slots with:

fastboot --set-active=other

and then I believe (correct me if I'm wrong, but it won't hurt anyway) you have to:

fastboot reboot bootloader

after switching slots. Then do the flash-all.bat again the same way you already did on the initial slot.

Good luck!
[Google Pixel 7 Pro] Lughnasadh:
I am enjoying the new "theme" in the OP 😁
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! I may eventually reduce the size of the image, but at least for now since I moved the "old" news, there's not too much distraction from what matters.

And I guess I won't tempt fate with another major HHGTTG reference with the potential title you suggested. 😂

If anyone does think the image is too distracting, though, please let me know.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Pixel Recorder 4.0 rolling out: Playback speed controls and more precise sharing

The Pixel 7 and 7 Pro will launch with Recorder 4.0 with some nice usability tweaks, but a bigger multi-speaker support upgrade is coming...

9to5google.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #3 - Other, most important resources:

Multi Timer StopWatch - this multiple timer app is the bomb. Got widgets, customization like crazy, you name it.

I forget when I finally found this - I believe early to mid-2020. There were many timers I regularly set up and left in Google Clock - which I mostly love, but unlike alarms in Google Clock, the timers weren't backed up and restored using Google's automatic cloud app data when I got a new device.

Beyond that, also, there was no way to re-order or better organize my many timers. Now this is how I have the Multi Timer app and the app's widgets set up:

You may think I'm crazy for being this excited about a timer app, but I could never go back to Google Clock's timer, except for the rare one-off in a hurry, but for my pre-programmed timers, I didn't find anything that beats this app. Its app data was restored by Google automatically when I set up my last two phones, and you can also manually backup and restore its app data from within the app without root if you wanted.

Edit: Quickly double-checked all my pre-programmed timers to make sure I didn't leave anything embarrassing in.
[Google Pixel 7 Pro] Lughnasadh:
Crazy like a fox 😉

Thanks for sharing!
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! You're welcome. See my edit?
[Google Pixel 7 Pro] roirraW "edor" ehT:
One more.

​
[Google Pixel 7 Pro] bigknowz:
Android Flash Tool is the way to go, has gotten me out of many sticky situations. Select the proper options, flashing simplified.
[Google Pixel 7 Pro] djcsurf:
Has anyone had a problem installing usb drivers for this device on a win 11 laptop. In device manager it shows as firmware update!