yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Agenesis:
Wow, wtf this works. Thank you so much.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! You're welcome!
[Google Pixel 7 Pro] jlokos:
Thanks for all the great information and to all those who contributed. I got my wife's phone unlocked using the Android flash tool, updated to the latest factory images and rooted, passing all safety net checks. She is happy, so I am happy!
[Google Pixel 7 Pro] Bad Bimr:
I'm going to say the issue was fastboot flash init_boot magiskpatchedinitboot.img. I'm pretty sure I did not run that command that way. My USB drivers were Rev 12 so not old. Regardless all seems well now. A huge thank you. The Good News is, since I was not rooted I logged into my banking apps and enabled bio-metrics (almost impossible with root) and it seemed to keep after root.

Thanks Again!
[Google Pixel 7 Pro] i5lee8bit:
Just wanted to give a progress update. Managed to get the kiddo in bed at a reasonable time tonight, so here I am on my laptop, [double] wiping my phone again, lol.

Took @NepoRood's advice and first "fastboot --set-active=other", then combining with @roirraW "edor" ehT advice ran the Online Android Flash Tool with wipe data and force flash all partitions checked. Successfully flashed Slot B with .031 and booted into Android fine from that slot. Reboot back into bootloader, "fastboot --set-active=other" again and currently Online Flash Tooling .031 onto slot A with the wipe data and force flash all partitions checked yet again. Just finished while typing this post and booted fine on slot A, now going through setup. Going to set up without restoring any data again. Goodbye 100+ saved networks... (I'm a network and systems admin which is why I have so many, so it's gonna be fun entering all the networks back in manually, lol)

I didn't opt to lock the bootloader this time, just so that if everything seems fine after 2 days or so, I don't have to wipe all my data again and I can just flash the patched boot image (which I'll redo Magisk patching again, and use adb push / pull to move the files - going super overkill cautious with everything this time, yo!!), finish setting up my root stuff and reassess from there.

It seems that the issues I was having always started back up within 6-12 hours after setting the phone back up, so 2 days should be plenty to see if being unrooted (but bootloader unlocked still) stays working. If the problem DOES come back, even after all this and not having an actually rooted system... I'll cry. Lol. Wish me luck, and thanks guys!
[Google Pixel 7 Pro] kornball:
With the MOD 2.0, I was initially passing safety net, but now YASNAC says I fail CTS profile match. Integrity checker says I fail "MEETS_DEVICE_INTEGRITY" and "MEETS_STRONG_INTEGRITY." Play Store still says my device is certified, though. Anyone else experiencing this with Displax's USNF MOD 2.0?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Cheers, you're welcome!

Cool. Ah, thanks for the reminder. My main bank's app is the same way so I'll have to temporarily unroot or at least when the next update comes out, set up my fingerprint in it, and then re-root.

Thanks for the update. The best of luck to you. Let us know.

Interesting. I just checked and I'm still passing CTS profile match (and Play Store certified). Did you get the most recent MOD 2.0? It's named the same, but there was a typo that kept it from working initially, but the replacement has been perfect for me so far.
[Google Pixel 7 Pro] kornball:
Good to know it's still working for you. Will grab from GitHub and try again later today. Do you add Google Play Services to the DenyList? If so, all entries or just gms?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I was already passing CTS profile without denying Google Play Services. The USNF Magisk Module takes care of that, and because of its fix, they automatically get re-undenied in Magisk anyway. I tried @wpswpatester's method of only denying com.google.android.gms, and initially that seemed to stay denied (exiting the DenyList and going back in), but a reboot must have re-undenied it, so I'm removing that guidance from my instructions.

Edit: See Post #2 in the "SafetyNet working again" section for what I do deny.
[Google Pixel 7 Pro] Lughnasadh:
Yep, rebooting undenies it because, as you alluded to, the mod won't work properly if it is denied in the list so the mod "denies" it in the background.
[Google Pixel 7 Pro] PurppleMonkey:
Following the "brick" of my pixel 7, I made a request for warranty support to my seller.

When I receive the new phone, I will root it, but a question comes to me: Once rooted, how to update it via ADB?

To be more precise :

1) I unlock the bootloader,

2) I root it by patching the init_boot.img (or something like that, don't remember),

3) If I want to upgrade to a newer firmware, do I have to remove root first or can I directly flash an entire firmware with ADB, especially using the "Flash-all.sh" file? Or is it better to use pixel-flasher?

I ask because on my Mac I had to face some errors, in particular an error, which I just remembered, telling me "fastboot too old; please download the latest version at https://developer.android.com /studio/releases/platform-tools.html" while I'm on version 33.0.3... Maybe it's better to use pixel-flasher ?

I don't want to brick a new Pixel! haha
[Google Pixel 7 Pro] roirraW "edor" ehT:
My update instructions in Post #2 of this thread apply whether rooting for the first time or for updating every month. Also, if you follow my instructions, you'll be updating before you root it. Not to confuse rooting with unlocking the bootloader. I unlock the bootloader immediately, but there's no reason to root the phone before updating, because you'd just have to root the new update, too.

For the first time rooting a device, I update it, so you can move #3 to be step # 1.5.

No need to remove root first. Running the flash-all (with the -w removed) will overwrite your root anyway, while not wiping your data.

I prefer using the factory image zip. I've done so since my first Pixel 1 in 2016. It's a personal preference and if you prefer to use a front-end for the process is completely up to you. There is no "better". Some users 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), so there's a third option. Then there are those who prefer one of the two OTA methods. I won't get into the OTA methods because I do believe the factory image zip method is better, and you ultimately still need the factory image to re-root anyway. That also applies to the Official Google Android Flash Tool - you still need the factory image zip.

The second OTA method technically wouldn't require the factory image zip if it worked consistently, but Magisk is constantly needing further development to keep working with that method. It's hit and miss and from what I saw on the Pixel 6 Pro with other users, mostly miss, so IMHO, it's not even worth pursuing.

To be clear, ADB is only used to reboot into the bootloader (fastboot mode). Fastboot is what flashes things. :)

I know nothing about doing this process on Macs, so I don't know what other users experience or if it's common to have trouble.

I really don't know anything specific about Pixel Flasher either. If it works on Macs, you can try it. I prefer to be completely in control of the process myself. Plus this way I stay completely in the know about any changes to how things are done.

Understood! I hope that doesn't happen to you. Is there no Windows PC handy to use just for this process?
[Google Pixel 7 Pro] PurppleMonkey:
You are so patient! Thank you so much !

Yes, I was wrong, I meant flashing the firmware with fastboot, not ADB!

So, if I understand correctly, once the bootloader is unlocked and the smartphone is rooted, if I want to update the firmware, I can follow your tutorial in post #2 and flash via fastboot with the command "flash-all.sh "without it causing a problem?

The process with the official google flash tool is detailed somewhere? Any precautions to take with unlocking the bootloader?

Once again, thank you for your advice!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Correct, as long as you also remove the -w from the flash-all-.sh so that:

fastboot -w update image-cheetah-td1a.220804.031.zip

becomes

fastboot update image-cheetah-td1a.220804.031.zip

The -w wipes your phone.

I don't have it in the instructions, but if you use Official Google Android Flash Tool instead of flash-all, maybe you'll have better luck. It's generally considered the more user-friendly way. You'll still need the factory image zip, so that you can pull the init_boot.img out of the inner zip file - plus it's good to have all the files handy for if anything does go wrong.

If you use the Official Google Android Flash Tool you should have the following items not selected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

For first-time rooting, it matters less if you let either tool wipe your phone. Feel free to wipe them if you wish to go through the first setup process - which will let you access the Google cloud restore steps, so you can restore the apps and a lot of the app data if you had your previous phone set to do Google cloud backups.

At Official Google Android Flash Tool. If you use it, just substitute it for almost half the steps in my

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

section of Post #2. Edit: There are only two particular steps to skip when using the Android Flash Tool. I've now updated my instructions to indicate which steps to skip in that case.

Nothing I can think of. That's typically the safest part of the process (and actually gives you more options to recover from catastrophe in most circumstances).

You're welcome!
[Google Pixel 7 Pro] kornball:
Once I undenied gms again, everything is passing again!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thanks for letting us know.

Ignore what I said before about skipping steps 1 through 8. There are only two particular steps to skip when using the Android Flash Tool. I've now updated my instructions to indicate which steps to skip in that case.
[Google Pixel 7 Pro] badabing2003:
Did you get prompted to update to the latest SDK even though you were on latest SDK?

if so, please provide details in PF thread (support.zip would be best), this should not happen and I have not seen this happen with anyone.

PF checks your current Platform tools against the latest (currently set in the app to 33.0.3) and if it sees it to be older, it is only then that it warns you.

On the other hand you are saying "Maybe it's better to use pixel-flasher" are you suggesting that, because PF caught you using an older version, you prefer using PF, as it catches certain user oversights?

In any case, this is what I tell everyone.

There is nothing PF does that you can't do it manually, it's a UI shell over adb / fastboot commands.

It is build from knowledge gathered through excellent guides in these forums like this one.

What PF offers is the automation and simplicity of the multiple commands through UI selections / checkbox-es and options, and it also tries to validate every step of the way if it is detecting expected responses / files are properly placed, versions are up to date, if you're already rooted or not, if you are flashing the right firmware to the matching devices and so on and on ...

It offers the choice to retain root (actually the default) without having to first boot to an unrooted state and then root, you can choose to flash factory to the inactive slot (recommended), this way you can keep your current active slot intact, which comes handy if anything goes wrong, and many other such convenient choices.

But all of this comes with some risk, any added layer has the potential of having bugs, it's a trade-off between user error or a program error.

I recommend everyone to follow excellent guides as this thread to learn and understand the exact processes involved in modding and rooting a device (that is how I started many moons ago and still read these guides and follow the threads to learn about new tricks and methods of modding, my bread an butter), after several monthly updates, when doing it becomes a routine, and you know what it takes to do it, then you could consider looking into tools like PF that speed and automate your work.

This is my suggest way, and in time you would be so good at it that you'd be able to help newcomers.

On the other hand if one finds following the manual steps so overwhelming, or they have zero interest in learning the process and all they want to do is get their phones modded, PF makes it easy, but I would say to those people, modding comes with risks and warnings, and the less you know the higher they are, perhaps they should stay away from modding.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@badabing2003 I don't think @PurppleMonkey has used Pixel Flasher yet. Also, currently, their phone appears to be hard-bricked, so they won't be able to do anything further until they get their replacement. @PurppleMonkey please correct me if I misunderstood. :)

And well said.
[Google Pixel 7 Pro] badabing2003:
Thanks,

This comment threw me off
[Google Pixel 7 Pro] i5lee8bit:
Quick update, even though it's only been like 12-16 hours (8 of those spent sleeping, lol). Everything seems fine so far. By my best guess, it likely would have happened again by now. Literally no issues at all as of yet.

Like I said, I used online flash tool to flash both slots, wipe all, force flash all partitions. Cmdline fastboot to change slots in-between. Running non-root for current testing.

Here are my caveats:

- I kept bootloader unlocked, so after testing I can easily just root and continue / finalize setting up.

- I "cheated" with the root aspect to be honest! I temporarily rooted so I could restore my 10 years of texts (I have an unhealthy obsession with keeping all my texts so I can easily search stuff that happened over the last 10 years... It actually comes super handy way more than one might think!). Immediately after restoring my Textra data, I full uninstalled Magisk and restored stock init_boot. That was about 12 hours ago and everything still seems fine. Btw, my old and new Magisk patched images hashes were identical so it wasn't that.

- I installed a huge majority of my standard apps, even my "root" tools like AdAdaway, TeMeFI, Fox's MMM, etc... At this point, it might be good to eliminate the possibility of a misbehaving app, i.e. if my problem doesn't come back until after I re-root, at least I know it's not (strictly) an app causing it. Besides, I install all these identical APK's on my wife's devices, which are not misbehaving in any way.

There are other very random issues I was having that also went away, but I won't make this post longer than it already is, lol. One involved both my Pixel Buds 2 and Pro settings, in case anyone is having issues I can share more.

So yeah, so far looking good. No root yet, but I *did* temporarily root to restore some data very early on (and honestly this caveat makes me even more hopeful, that I cheated and it still hasn't broken). I think @roirraW "edor" ehT and @NepoRood were definitely onto something, and I'm very hopeful their advices were correct! Gonna give it another day before I root again and finish setting up... 🤞!!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have to admit, I don't understand it exactly either, and I failed to ask where that message came from. Hopefully, @PurppleMonkey will clarify.

@i5lee8bit sounds good, thanks for the update!
[Google Pixel 7 Pro] Jiggs82:
Hey guys I just got the 7pro , after unlocking the bootloader , I factory wipe the phone with -w, then factory reset again. Rebooted the phone, set up everything, install latest magisk canary 25205 , patch init.boot.img , rebooted to bootloader fastboot verity img thing then fastboot magisk patch but now the phone just reboots to bootloader and it says boot failure. Could anyone tell me what went wrong? Thanks
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi. When you say Fastboot verity img thing, do you mean you disabled Verity? Did you also disable Verification or just Verity? If you disabled Verification too, then you have to factory reset after.

I'm also not sure why you would wipe with -w and then factory reset again. Did you update to the latest factory image as well, or was your Pixel 7 Pro already updated? The initial firmware release ended in .009 and the zero-day update which is the latest is .031. I don't know if you could've possibly mixed and matched the two (running .009 but used the .031 factory firmware zip...).

When you say fastboot magisk patch, did you flash the init_boot.img to the init_boot partition, or accidentally flash it to the boot partition?

Edit: I suggest using 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) and starting over from scratch. You can use my instructions in Post #2 if you like.
[Google Pixel 7 Pro] Jiggs82:
I mean this command fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification, and ok i didnt factory reset after that.

My phone came with .009 image but i downloaded and extracted zero day update .031,

Hmm idk, i just installed/patched the init,boot.img to latest magisk canary, then rebooted to fastboot but i entered this command first fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification , before fastbooting flashing magisk but thats where i get boot failure. So i think my issue was i should have wipe after the vbmeta command .....
[Google Pixel 7 Pro] NepoRood:
I think you're going to be good to go, when modding an A/B device, slot corruption (IDK what else to call it) is pretty easy to accomplish and it takes very little effort, lol

The A/B slot system was implemented for both seamless OTA updates and a fail safe backup of the currently running OS (in case an OTA was interrupted, corrupted, or what ever) When users start modifying and flashing the device manually, it's pretty easy to forget which slot was active or inactive and what was flashed where.

It's a common problem when people can't get a custom ROM to boot as well, but that's a different rabbit hole...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm still not clear if you actually updated your phone to the .031, versus it sounds like your phone still had .009 but you used the init_boot.img from .031, which could be a part of the problem. Unless you did indeed run the flash-all.bat to update your phone to .031. I'm just trying to cover all angles.

Disabling Verification always requires a factory reset after. Disabling just Verity does not require a factory reset. You should still be able to wipe and have the phone work - unless your phone is still indeed on .009 with only the .031 Magisk'd init_boot.img.
[Google Pixel 7 Pro] Jiggs82:
My phone was shipped with .009 but i thought the .031 was the update build, so i downloaded and exrtracted .031 files , flashed that build and used the init_boot.img from it to patch magisk. You saying i should have patched the init_boot.img from the .009 build? @roirraw-edor-eht
[Google Pixel 7 Pro] roirraW "edor" ehT:
So it sounds like that's another problem. Your phone was still on the .009 firmware, except for the .031 Magisk-patched init_boot.img that you manually flashed. Yep, you should start from scratch and follow my directions in Post #2 starting at

How to update each month (and also how to root

.

Edit: I see you edited your post. Actually, you should've used the flash-all.bat from the factory image to update your entire phone to .031, then use the init_boot.img from .031 to root the phone. .031 probably contains important bug fixes since they released .031 at least on the same day as the phone officially came out. Just follow the instructions at the link I gave for Post #2.

Edit 2: But yes, technically, you could've used the init_boot.img from whichever of the two .009 factory image zips that match your exact build number, but then you'd likely have other bugs that updating to .031 would fix, and then you'd have to re-root again.
[Google Pixel 7 Pro] Jiggs82:
But i did flash bat with -w from .031 factory image over .009 factory image that which i had on my phone currently and it did boot fine , only had the issue after flashing magisk patch
[Google Pixel 7 Pro] i5lee8bit:
Thanks for the explanation, definitely makes sense to me. I don't know what the slots should look like on a brand new, fresh out of the box device, but I definitely 100% hadn't touched slot-b at all, at least not directly and/or intentionally. With that said, the fact that my wife's panther had errors when initially flashing .031 until I used a 2.0 cable (AND come to think of it, final factory flash was done with online tool on hers, lol) definitely makes me suspect something didn't flash right on mine. But it (un)luckily went through *supposedly* without any errors for me 🥴

I'm fairly competent with how slots work (first A/B device was HTC U12+); I'm sure not anywhere nearly as you are but at least for the average modder, but again I'm not sure how they're set up on a factory fresh device. I'm guessing they're both loaded with the shipped firmware.

One last thing to note that I didn't mention before, as a final test before my last factory reset, I online flashed the factory firmware with a 2.0 cable and left unrooted, hoping it would fix my problem and "repair" whatever was corrupt without another reset. Obviously that didn't work; I guess the damage was already done or it was one of the ones that needed force flashing? lol. So it was definitely worth using the online tool to force flash all partitions, plus go fresh on both slots too.

I'm really hopeful too, and either way I owe you guys a huge thanks for your time and advice!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Okay, then that wasn't part of the problem, and you're right, it's probably just the factory reset you need after disabling Verity and Verification, as you had said. In that case, you probably just need to wipe the phone and it should boot fine. If it doesn't, start from scratch.
[Google Pixel 7 Pro] NepoRood:
I was hoping, and you confirmed, that you knew what I meant when I said "both" slots (y)

I don't know for certain if a new device comes with firmware on both slots, but I would think that it would. We pretty much get an OTA out of the box, what if it fails? That's my thinking anyway...

I haven't used Google's flash tool very much as I usually download the zips for my devices to compare changes from the previous release. I never run stock Android very long...
[Google Pixel 7 Pro] Lughnasadh:
As you said, a new phone should come with full firmware on both slots. Interestingly, though, and as originally pointed out by @Namelesswonder , that when I checked the radio version of my inactive and untouched slot using fastboot getvar version-baseband , it came back as unknown. When I got the phone I immediately flashed .031 so the inactive slot was never updated via the 0 day OTA. Whether this was just a glitch, or maybe for some reason fastboot wasn't able to read the version, or there really wasn't a radio, or something else, not sure.

https://xdaforums.com/t/unlock-boot...gain-all-relevant-links.4502805/post-87578287
[Google Pixel 7 Pro] NepoRood:
You know, after reading that and actually thinking on it for a minute. It probably does ship with only one slot flashed, that way the other slot is empty for the first OTA update. Since OTAs flash the inactive slot, it shouldn't matter if it has anything on it or not. If the update fails, it's not going to boot that slot anyway, it will stay on the one it shipped with.

Sometimes I get foggy in the head, and I was trying to watch Rings of Power...

(That's all I got for an excuse, lol)
[Google Pixel 7 Pro] eg1122:
Rings of Power is an excellent excuse. That's all I got. Next reply will be productive.