yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes.

No, no reset as long as you continue to disable Verity and Verification (Verity doesn't require a wipe, but Verification does) every time you flash vbmeta.img - whether through the monthly flash-all.bat or any other method including the online Official Android Flash Tool. If you don't disable those once, then if you disable them again later, you'll have to wipe again.

This is all until/if they solve the AK3 on Pixel 7/Pro method so that Verity and Verification don't have to be disabled anymore.

If you mean the monthly security updates - my instructions in post 2 apply for both first-time root and for updating. If you follow the instructions, you have root again at the end.

OTAs generally don't work when rooted. OTAs require the system be 100% stock, so with a rooted init_boot.img, OTAs fail. You need to follow the instructions in Post #2 to update once you're rooted.

Cool, good luck! I hope everything works well for you. Once the online Android Flash Tool finishes, you can re-follow the instructions to root, this time skipping anything I tag at the beginning with * FAB (Flash-All.Bat).

That's always a very subjective question/answer. In general, yes, most any custom kernel is worth it. Note the instructions in the Despair kernel thread - if you haven't already disabled Verity and Verification before you set your phone up, when you do so (required for the custom kernel, currently), you'll have to factory reset, and keep disabling those every time you flash vbmeta.img including when using the monthly flash-all.bat or the online Official Android Flash Tool.

For changes, read the Despair Kernel thread and the changes listed at his GitHub link.
[Google Pixel 7 Pro] jucin:
I only disabled verity and flashed latest Kernel from Despair and then rebooted and did a Reset after that it worked Well but i didnt disabled verification
[Google Pixel 7 Pro] roirraW "edor" ehT:
You should let @DespairFactor know that whatever version you flashed only required Verity to be disabled, not Verification. Of course, since I haven't flashed it myself, even though I read all the posts in the Despair Kernel thread, I feel I can't keep up with what's necessary.

At one point, I thought I understood that only Verity needs to be disabled, but normally only disabling Verity doesn't require a factory reset. Then I thought I understood that only Verity needs disabled, but for use with the kernel, a factory reset is still needed after it's disabled. The instructions still say to disable both Verity and Verification - I can only guess that it's more a "just in case", as any user is far less likely to receive any corruption errors with both disabled, but if you disable both Verity and Verification now, you'll have to factory reset again.
[Google Pixel 7 Pro] meinlet:
Unfortunately android tool also stuck exactly the same point as flash_all, so i tried to change the cable and used a USB 2.0 cable and that worked perfectly. I don't know what exactly was wrong with the original cable p7p came with.

I already rooted my device and everything works as supposed.

Thank you for your time, you saved me from resetup my phone (few hours of my life for sure).

:)
[Google Pixel 7 Pro] badabing2003:
I don't know the answer to this, however it is a possibility, seeing many people getting stuck in fastbootd state.

Do you know if fastbootd needs different drivers than bootloader ? is it possible that when the phone reboots to fastbootd to flash the images that need to be flashed in fastbootd, the phone is no longer detected and is staying in that state until the user is noticing it and rebooting it, which obviously is incomplete and causing issues.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Glad that advice helped.

There's not necessarily anything technically wrong with the USB 3.x cable or USB 3.x port. Flashing on all devices has been typically finicky - with the details of the finicky-ness changing from OEM to OEM, and over the course of time.

I find there is less and less finickiness with more recent computer hardware, but it might again just depend on the brands/chipsets in the computer hardware. There were times on my pre-Pixel 1 devices when I definitely had to use particular USB ports on my personal or work computers.

In the last six years, I've often flashed several of my devices (Google Pixels, HTC 10, maybe a Sony Xperia XA2 Ultra, and my Samsung Galaxy Tab S8 Ultra) from any USB port on my PC, including through a powered (and battery backed up) USB 3.2 Gen 2 USB hub that's connected to my self-built desktop with MSI motherboard to a USB-C USB 3.2 Gen 2 port, but that won't work for everyone.

You're welcome! Yeah, it's a pain to set back up from scratch, even if you have everything backed up using Swift Backup.
[Google Pixel 7 Pro] badabing2003:
Sounds like fastbootd is more sensitive to cable / USB port than bootloader is.
[Google Pixel 7 Pro] roirraW "edor" ehT:
They solved the problem, see the post above yours. Changing to a USB 2.0 cable and USB 2.0 port fixed the issue. Since I already wrote this before you wrote another reply. :D I don't think fastbootd requires a different driver - I only know that after you install the Google Driver to a Windows PC with an Android device running so you can use ADB commands, when you reboot into the bootloader (regular fastboot mode), it needs the driver installed again.
[Google Pixel 7 Pro] jucin:
I followed your instruction in the section of installing custom Kernel from begining to end, the one Thing what i did different is i only disabled the verity from the vbma and flashed it. After that i downloaded Kernel flasher apk and flashed the 1.09 (it Not more aviable) then i rebooted my device and did a factory Reset in the settings and it started normally without bootloop or Problems and its runing great for me better then the Stock Kernel
[Google Pixel 7 Pro] ram4ufriends:
Are you trying this on Mac or Windows? I got this issue on my two Macs, but on Windows it worked fine.
[Google Pixel 7 Pro] roirraW "edor" ehT:
They already got it working. Good to hear reports (even they're not good ones) about Macs. I may consider letting users know they may have troubles on Macs.
[Google Pixel 7 Pro] meinlet:
I'm using a Windows PC (Win 11).
[Google Pixel 7 Pro] BIGWORM:
In addition to that, always be sure to connect to your computer directly via USB, i.e. don't use a USB hub. Plug into the front I/O of your computer at the most.

Question re: the beta. Would like to keep root/bootloader unlocked, but flash this. Phone is ready to take the OTA. Should it be as easy as disabling Magisk modules, flashing the OTA, pulling the init_boot.img from the full OTA, patching that with Magisk, then fastboot flashing that img?
[Google Pixel 7 Pro] roirraW "edor" ehT:
See @Lughnasadh's quote below from the page before this one. What you're suggesting doing sounds like the other OTA method, though. You'd have to restore the stock init_boot.img (the one not Magisk patched) from your currently running firmware version before an OTA method could possibly work.

Note that I only include factory image zip install/update instructions in Post #2 because that's the way I prefer, so I don't ever bother trying any OTA methods. You have to pull the init_boot.img from inner zip that's in the factory image zip, yes. The instructions should be good for any specifics you need regarding the factory image or flashing the patched init_boot.img.

I just think it's easier using the factory image zip with a modified flash-all.bat (to not wipe the phone) since you need the zip for the init_boot.img inside it anyway, but what you're suggesting, with the addition of restoring the stock init_boot.img first, sounds like it should work.
[Google Pixel 7 Pro] Ghisy:
Speaking of cables, I always flash the factory image with the stock USB 2.0 cable from Google. I have a USB type C connector on my Windows 7 PC. All the flashing done there has worked fine so far!

My platform tools are always up-to-date and I copy things I need to flash to the same folder and delete them once I'm done. This way, you can keep your platform tools folder clean.

I also have another PC on Window 10 but haven't installed Android stuff on it yet so I can't comment on that.
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, I'm using the same drivers while using my Pixel 7 Pro as I was using when I first got my Pixel 6 Pro a year ago and am having no problems with fastbootd. I will say, however, that with the Pixel 7 Pro, the "waiting for device" time frame does seem to be a bit longer than it was on the Pixel 6 Pro.
[Google Pixel 7 Pro] jucin:
I wanted to add the Google Framework to the Magisk hide list but everytime i try to activate it it disable it from hisself. I think this is why i can not buy anything in Google Play Store even with saftynet newest installed.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm not sure when "usb_driver_r13-windows.zip" was first released, but I apparently downloaded the copy that I'm using on 10/27/2021. I know another user was using r12 just fine, too, but I'll still tell everyone to always use the latest. 😜😂
[Google Pixel 7 Pro] roirraW "edor" ehT:
Excerpt from the SafetyNet portion of Post #2:

You might want to look all of those steps over in case you missed anything or aren't using the latest "stuff", as well. :)

Also, don't forget to wipe some app's cache and/or data that you add to the DenyList, and also reboot after adding anything. Then check the status in YASNAC and Play Integrity API Checker, as mentioned in the instructions.
[Google Pixel 7 Pro] Lughnasadh:
I downloaded and am still using r13 on 07-16-2021
[Google Pixel 7 Pro] roirraW "edor" ehT:
Then you're on the latest! :D

I see the files inside the zip are from July 2020. Sounds right - from when I was still fiddling with my OG Pixels.
[Google Pixel 7 Pro] Lughnasadh:
Yep! 😀
[Google Pixel 7 Pro] jucin:
Yes i checked them they are how they should be but still i can Not pay in the Playstore. It say me Check the Security of your Account to complete the payment
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hopefully, it'll fix itself for you before too long. Sometimes just waiting changes the situation - unless you've already been waiting days without luck.
[Google Pixel 7 Pro] capntrips:
I just wanted to mention that I've had to unplug and replug my Pixel 7 several times after the transition to fastbootd before it registers while it's <waiting for any device>.

The issue is with only verity disabled, if you flash back to stock (e.g. during an upgrade) then flash a custom kernel again, you'll have to wipe your data again.
[Google Pixel 7 Pro] jucin:
Well this i didnt knew and didnt tested it. So that means the verity must be disabled with the newest build but does it then not need again to make a factory Reset?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting, and good to know. Thanks! I had no trouble here, but have only flashed once. :)
[Google Pixel 7 Pro] badabing2003:
That's a good approach, as at that point, the computer is waiting to detect the phone, and unplugging / re-plugging is not going to break anything.

It shows that there seems to be a pattern of issues with fastbootd on these phones.

Did you ever had similar issues with other PIxels? on the same PC?
[Google Pixel 7 Pro] capntrips:
If I'm not mistaken, until we figure out what exactly is triggering the wipe, the only way to avoid it in the future is to keep verification disabled.
[Google Pixel 7 Pro] capntrips:
No, I never had this issue with the previous Pixels. I have had it happen both from linux on a laptop with USB-C (I don't have any USB-A ports) and from another phone.
[Google Pixel 7 Pro] Boodzilla:
Thank you for this excellent and detailed thread. I've been reading all comments since day 1 and thought I understood everything until someone had an issue and mentioned fastbootd as opposed to fastboot. Now I'm back to square one. Is there something we need to pay attention to not to face the same problem as reported by @PurppleMonkey?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

From what I remember, @PurppleMonkey mistakenly thought the flash-all.bat was done flashing since the screen was on fastbootd for longer than they anticipated. Hence the warning in my instructions:

So don't pull the plug on the phone and PC or do anything else to disturb the flashing process until it's booted into Android.
[Google Pixel 7 Pro] PurppleMonkey:
True story ! He was here !
[Google Pixel 7 Pro] exocetdj:
sorry as this has been no doubt discussed but, has anyone had any issues with the seamless update with root method? I know this was a bit iffy on P6P

not a huge thing as im happy updating using factory images as per usual
[Google Pixel 7 Pro] Lughnasadh:
If you're talking about the Magisk option to "Install to inactive slot", it likely won't work because Magisk is not restoring the stock init_boot.img, so essentially you stay rooted after using the "Restore images" function and thus the OTA will fail.
[Google Pixel 7 Pro] tatico28:
Hey guys, this question might have been answered but it`s been a long time since I have not been here in the forums and a lot has changed, I`ve tried to use the search option but nothing relevant came up, question is: can you use still use Crypto trading apps after root?

Thanks in advance.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome and thank you for the kind words.

I'm glad things went smoothly for you.

Ah yes, you're right. I think when I wrote that part of the guide, I meant to later go back and check what exactly it says but I forgot.

I've now added:

This second time installing the drivers while in Bootloader (fastboot mode), it will show up as "Android Bootloader Interface".

and I thanked you for suggesting this detail.

I considered adding that originally, and I may still, but I'm going to hold off for now. Mostly because I don't have the time to add that in the detail I want to, but I will likely add it eventually when I can sit down and focus on it.

Yes, that's fair.

It now says (The Mac thing is separate, but something I was recently considering adding):

Thanks for taking the time to let me know, and you're welcome again.

Good question. I've read every post and you're right, I don't recall anyone mentioning either way. Hopefully, someone who knows will answer.
[Google Pixel 7 Pro] simplepinoi177:
I can't remember which post I saw it on this thread (I believe it might be this thread, or it might've been another in regards to custom kernels), but I remember someone asking if/when a certain custom kernel might be supported because he was trying to get this trading app working and the only way to have gotten it to work was using this particular custom kernel. I remember being intrigued because I had no clue what the app he was talking about did, and found out it was a crypto trading app! I'll see if I can't find the name of the app and/or kernel, but if he was correct, you might need to install a custom kernel and/or the custom kernel he used on his old device; even after achieving root...

UPDATE #1: the search function here on XDA isn't too great....if it's not searching through all random forums, it's not too great at plain words (which all I can remember from the post only had)... even using the technique "site:" to this thread's url didn't bear much fruit. still on the hunt....

All I can really remember is the person was asking if a certain kernel might work or was in development of working because he that's what he "uses/used" to get a certain app to work. i can't for the life of me remember the name of the app, but it stuck out to me wondering what he was asking for, so i googled it and found it was a crypto trading app. So the only keywords i can think of is "kernel", "used", and maybe the word "app" (i.e. I "use" it for bybit/etoro; I "used" to use said kernel to get bybit/etoro to work...)

UPDATE #2: Okay, I just can't find it haha 😅! It's like an "earworm" to me and I've been obsessing finding it, but no go. I've used forum search function, google "site:" technique, even resorted to going through every page and searching the word "kernel" on each page and reading what context the post was about on this and 3 other threads it might be in with no success. At this point, I'm even doubting if I read it here and ends up I read it on some random discussion elsewhere like reddit or github -- but that doesn't quite make sense because I'm mostly on here and it makes most sense someone would randomly ask that kind of question here...

It's too bad...it's gonna bother me for the near future since I really randomly wanted to find it. Seems just there, but out of reach. In any case, there only seems to be one working custom kernel (Despair's) up and running right now, and I'm not sure if it can specifically help you with your issue. You might want to ask him if it's possible to implement it or some kind of capability in his kernel to make it work -- I remember back in my Pixel 2 days, custom kernels were needed from allowing tap-touching because it would break in certain root instances, Pokemon GO root playing, or it helped get my safetynet to pass and I could finally get GPay to work rooted (which was a happy accident as that's not why I applied the kernel in the first place). In the end, I wish good luck to you!
[Google Pixel 7 Pro] slubgob:
I resemble that remark! :p
[Google Pixel 7 Pro] simplepinoi177:
that's why it's the same 3 things that needs to be re-iterated on

every

guide or troubleshooting help (including this one; as you can tell by it being re-iterated/reminded multiple times in the same guide 😜)

make sure

everything

unzipped from the factory image is moved to the platform tools folder

make sure your platform tools is up to date! and/or

not

from a bundle or the weird "minimal" platform tools

make sure your command prompt/powershell is directed to the right platform tools folder or adb.exe/fastboot.exe; usually it's an issue of many different platform tools folders around the computer (desktop, C root drive, Documents folder, Downloads folder, etc.)

It was like that on the Pixel 2 XL forums, on the Pixel 5 forums, and it's here on P7P, and probably all the other Pixel phones in between...😝
[Google Pixel 7 Pro] pndwal:
... Further, I recall being stumped until I moved ADB folder to root of C: (working) drive... (Possibly might work elsewhere, but wouldn't from desktop on my machine.)

Nb. This message is original and I never resent it... Hope no-one resembles it either! 😝 PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
I like to keep things like this close to the root of a drive, also. I keep mine in S:\platform-tools\. Eliminating long pathnames and paths with spaces in them doesn't hurt.
[Google Pixel 7 Pro] badabing2003:
If it is helpful to anyone,

I always keep platform-tools in the path (ie I install it somewhere like C:\android\platform-tools) and add it to system path. Platform tools does not change that often, and I update that folder anytime there is a new platform-tools version.

This has the added advantage that no matter where my command prompt is opened from, I can always execute adb / fastboot commands.

I would strongly discourage the use of Powershell for flashing, mainly because Powershell loads various modules at startup (see Powershell profiles), anything wrong in any of those could play havoc (speaking of experience).

When I used to flash manually, all I had to do is get the firmware, unzip it in some temporary directory (no spaces) example:

C:\temp\cheetah-td1a.220804.031 and open command prompt there and run things from that directory.
[Google Pixel 7 Pro] Lughnasadh:
I keep/download/extract my Platform Tools folder right to my desktop (C:/ drive). My monthly builds and other files each have their own folder within a larger Android folder I keep on a separate and larger D:/ drive to save space on my C:/ drive. When there is a new monthly build I copy the 4 needed files over to my Platform Tools folder and open up a command prompt there. When flashing is done, I delete those 4 files so afterwards there is nothing in the Platform Tools Folder except its native files. Same goes for flashing other stuff. Copy to Platform Tools folder, open up command prompt there, flash and delete afterwards. In all these years, this has never failed me.
[Google Pixel 7 Pro] hodula1:
Did you end up getting Marriott app to work? Having the same issue.
[Google Pixel 7 Pro] collegencmc:
Sadly no and haven't found much about why it still detects root when other apps don't. For now I'm just using the website.
[Google Pixel 7 Pro] pndwal:
Are you folk using @Displax modded USNF fork linked in OP w/ fix for new Play Integrity API deviceIntegrity verdict?...

Nb. SafetyNet is now deprecated...

Use Play Integrity API Checker to confirm working... Don't worry about strongIntegrity fail; you cannot pass but banks don't use yet... PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
As far as I know, and from what I remember some more knowledgeable users saying in the last year, there is nothing that keeps any app from being able to tell that the bootloader is unlocked, so they don't even have to care whether you actually have root, but could merely be detecting that. From what I remember, there's no way to hide the bootloader unlocked status, as well.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm pretty sure that was the puzzle, that even with hiding root from the app plus using MOD 2.0 that the Mariott app still refused to work.

@hodula1 and @collegencmc perhaps the next time you update your phone, before re-rooting it, wipe cache and data for the Mariott app and see if you can sign into it. If it won't let you sign into it while being unrooted, then it's likely the bootloader being unlocked that causes the trouble with it.
[Google Pixel 7 Pro] HipKat:
Man, 45 pages??

Tomorrow mine will be here and I haven't rooted a phone since the Nexus 6...

Should I be nervous?
[Google Pixel 7 Pro] capntrips:
It really isn't bad, especially if you're comfortable with the command line. It's difficult to permanently brick the device. Just read the instructions and try to understand why you're doing something before actually doing it, and you'll be fine.

This thread is very active, given the phone is new, so you should be able to get answers to questions quickly, though I'll bet you can find the answers to most almost immediately with the thread search.
[Google Pixel 7 Pro] HipKat:
Oh yeah. I have to probably reinstall the Android SDK today (Since I just installed a new Arch OS).
[Google Pixel 7 Pro] pndwal:
Hope you've managed to get S/N passing as that's imperative; if not, try disabling ALL modules other than @Displax USNF mod 2, reboot and see of it passes in YASNAC... If so you should also have PI deviceIntegrity in Play Integrity API Checker...

If you have all this and app still detects 'root' (assuming you've also taken the Hide the Magisk app option in Magisk App settings, have app in denylist, Zygisk = Yes on home screen, and you cleared bank app data; do this for every test), try installing Shamiko Magisk module and disable 'Enforce denylist' (Shamiko will use list as a hidelist) and check again...

Next, try uninstalling Magisk App (only) and check app again... (Nb. You won't lose any Magisk data or configuration as it's stored in /data/adb, not in app data) If this works, next step is to reinstall Magisk App and obfuscate it more fully; Hide My Applist LSPosed module should do the trick... See here for method:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87608273

Even if not detecting Magisk hidden (stub) app, HMA module may still help as some apps detect other root apps etc as mentioned in my link... PW