yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] pndwal:
Well we can still spoof AVB green state if hardware key based attestation is properly bypassed; this means apps need to detect traces of root / compromised operating environment, and some are actually detecting Zygisk hooking and other signs... Nb. We cannot hide Zygisk from vvb2060/Rikka's Momo detector on many devices even with Shamiko module currently; old Riruhide was more effective than Shamiko is for Zygisk... Some are resorting to using unofficial Magisk forks w/ old hidelist restored and Riru-USNF mod with Canyie's MomoHider module, or old Magisk 23.0 with the same to fool such banks...

However, most detections can be bypassed more easily... Of course once Banks accept the collateral damage (ie. customers using devices launched with Android 7 and earlier, even if running latest Android, as well as most OnePlus users and users of other devices with broken keymaster implementations) and start calling PI strongIntegrity, it's necessarily Game Over for all of us (except perhaps Asus ROG Phone 3 users) as bootloader locked / AVB green state cannot be spoofed using HKA... PW
[Google Pixel 7 Pro] xike456:
I just got my 7 pro. It is imported from Japan so I cannot turn off the camera shutter sound (I live in Vietnam and there is no law about that). I found a thread about converting pixel 6 pro JP to global SKU.

https://xdaforums.com/t/converting-japanese-pixel-6-to-global-version.4365275

Can I do that with my 7 pro?
[Google Pixel 7 Pro] Lughnasadh:
On a side note, I have one app that detects if USB debugging is enabled and won't work if it is. :)>
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL, yeah, it's been crazy busy, especially for the week after the earliest folks started getting their phones.

No, nothing to be nervous about.

Interesting. No one else has reported anything about doing so. Technically you should be able to do the same thing with similar information. See Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version. See what @Lughnasadh says that I quoted in that post for how to get your model #. I'd be very curious if it's different from the two I already have listed in that post, and if it is, what it is so I can add it to the list and/or research it just for information's sake in that post.

Then you'd likely want to change it to one of those model numbers I already have in that post. Probably whichever corresponds more closely to your hardware's capabilities (5G mmWave or not).

Be very careful. Typically, pulling partition images using adb, and writing images back using "dd" isn't as reliable as officially supported flashing methods, but there is likely no other choice.

@TotallyAnxious had made some root mods for the Pixel 6 Pro (and are in the P6P section) which I believe had included the ability to disable the camera sound, or possibly replace it with empty audio. I have no idea if those mods would work on the P7P or not, but might be worth trying if you're going to root anyway. It would certainly be much safer than manually pulling a partition image, hex editing, and then writing that image back.

I haven't been able to keep up with all the threads in the P7P section, so I don't know if anyone else has tried it on the P7P, or if they've created mods specifically for the P7P, if they have one.

Oh, good point! Yep, that's another trigger for some.

For what it's worth, the updated module that came out after the last officially released version (I found after the officially released version gave me an infinite boot logo) hasn't helped me with putting my fingerprint in my bank's app. I'm not too worried since it's easily done while the phone is temporarily unrooted when I update next month if I remember to.

Here's the link to the not officially released newer version: https://github.com/Dr-TSNG/Hide-My-Applist/actions/runs/2912867245

Hopefully, the root app/Lsposed module gives better luck to @hodula1 and @collegencmc.
[Google Pixel 7 Pro] rmiles7721:
Crypto.com, coinbase, webull working. I always add them to the denylist prior to ever opening them. As far as other financial apps, Bank of America, Stash, Chase Bank, Paypal, Venmo, Cash App all working as well.
[Google Pixel 7 Pro] Beefheart:
I don't want to disable verity and verification to get Despair working. So before I root, on the current stock kernel, is there any scope to change the governor and voltages or is it fixed like most stock kernels?
[Google Pixel 7 Pro] TotallyAnxious:
This silences camera/screenshot sound.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you!

I haven't tried, because I usually leave those things alone these days, but I wouldn't expect it to be any different on the P7P stock kernel. Hopefully and eventually the custom kernels will be able to be used without disabling those.

Thank you! I will add a link to your post in the OP just as soon as I can. Thanks much!

@xike456 see their post above this one for a Magisk Module to do what you want, if you prefer.
[Google Pixel 7 Pro] Beefheart:
Thanks. Hopefully someone can check.
[Google Pixel 7 Pro] tatico28:
Thank you!
[Google Pixel 7 Pro] tatico28:
To say that the thread search isn`t too great is an understatement, this search function is crap, I remember a few years ago I used to search a thread and you were able to find the cancer cure lol, but not anymore, I missed those days, thanks for the effort anyway. I also search Google but was not able to find anything solid.
[Google Pixel 7 Pro] xike456:
Here is my 7 pro model number: GFE4J

I found some info about this here.

If understood correctly, will modifying the model number permanently affect it even if I unroot the device? I would like to keep it unroot.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks very much for the information. I'll add it to Post #6.

The instructions at the XDA thread you linked to say "This should be permanent, you can also revert root if you want."
[Google Pixel 7 Pro] xike456:
Thank you. I may give it a try and report back :D
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good luck! Be very careful. If something goes catastrophically wrong, consider 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 if you have to, enable the Wipe and Force Flash All Partitions (which would also wipe) options.
[Google Pixel 7 Pro] xike456:
I successfully changed the model number to GE2AE. after flashing the stock image, Regulatory Labels show the model number with the USA region. The camera sound option appeared, and I can turn off the sound. I also unrooted and re-lock bootloader
[Google Pixel 7 Pro] wr3cckl3ss1:
Idk how this happens or who's running things at VZW and Google. But i "carrier unlocked" this VZW P7P with no carrier help.....now OEM toggle gives me a new error of "connect to Internet" . I can elaborate more on what i did but if anyone has an idea on what to do next. Let me know.
[Google Pixel 7 Pro] rage302:
Okay this is great to hear.

So do you think it is possible to change the model from GP4BC to GE2AE and activate mmWave by this way?

Thanks

greetings rage
[Google Pixel 7 Pro] xike456:
I don't think it works that way. It depends on the HW capability.

In my case because my model is similar to GE2AE model, I only need to bypass camera sound turn off restriction in Japan model
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thanks for reporting.

I have no ideas, but I'm sure you mean "carrier unlocked" instead of "sim unlocked", which are two different things. Also, Verizon phones all become carrier unlocked after 60 days, if I understand how they work these days. Carrier unlocking a Verizon phone doesn't let you toggle OEM Unlocking.

Naturally, I'm still quite curious, and I hope you find a way to toggle it. I haven't bought a Verizon phone in six years.

As @xike456 said, these model numbers are "hardware model numbers", so the internal hardware is supposed to be different between your GP4BC and the GE2AE, and it's unlikely to help.
[Google Pixel 7 Pro] pndwal:
Well that's a test build of 24 Aug... Not sure why you need CI builds, but thanks for alerting me to possible issues with latest stable and P7 devices... Could it be issue mentioned below* though?

We've had 5 Beta releases with further fixes from 25 Aug...

Please can you say if V3.0.5 Beta works ok on P7 Pro?... (Betas are working fine on my older Xiaomi device...)

Tip for all:

Please take time to read notes on Releases page where available for apps like on GitHub... Devs often post pertinent information here and often only once...

*Nb. Issues may be related to this (for last Stable 2.3.2 final) note:

And for later builds (incl. CI?) see V3.0.0 Beta notes:

(... This makes me suspicious.)

Nb. 2) 3.x series HMA has a simpler/ cleaner feel (interface has changed a lot)...

👀 PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
I was led to that August 24 version from a link in a thread discussing the Stable version not working with Android 13/stuck on boot logo. I didn't realize there were newer Betas.

I didn't have any version of Hide My Apps List installed before I tried the Stable v2.3.2 from January. I've never used it before.

The app appears to work, although it doesn't help with setting up the fingerprint reader with my bank's app. That's the only app I have trouble with, and it's easily worked around by setting up the fingerprint in its app while temporarily unrooted - which I'll plan on doing when the next firmware update comes out.

Thank you!
[Google Pixel 7 Pro] pndwal:
HMA helps only with hiding suspicious Apps when banks use tricks to bypass proper Google restrictions to see apps on your device traditionally, although we now have

• Support disable /data/data detection for Android 11 and above (Settings-Experimental)

in addition...

Many need it simply to more properly hide the Magisk App because it's inbuilt stub obfuscation is basic/limited and easy to circumvent... Other banks detect a range of root Apps and utilities to make the assumption that you rooted...

I suspect some process your bank uses for biometric security (possibly in a separate app) is detecting traces of root... Doubt that this will include App detection, but I can't know for sure! 😜

May be able to research/identify security engine (Promon etc) bank uses and thereby find proper means to bypass... might be worth mentioning which bank... 🙂 PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks. That's okay, like I said, that's the only app I have trouble with, and only the fingerprint portion and they apparently don't care enough to detect after the fingerprint is set up while unrooted, so it's easy enough to deal with. :)

Some of the other users I mentioned in my earlier posts would likely be better candidates for testing, if they still haven't found a solution.
[Google Pixel 7 Pro] pndwal:
Good to know bootloop can be avoided... PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
Generalized my instructions for

Optional steps when updating - flashing custom kernels

since now we have two custom kernels. Still requires Verity and Verification to be disabled, therefore requiring a wipe if you didn't already have them disabled.

https://xdaforums.com/t/kernel-24-1...ura-1-0-0-for-pixel-7-pro-aka-pantah.4509795/

Whoohooo!
[Google Pixel 7 Pro] selfassembled:
Does this method wipe data on the phone?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You'll have to be more specific. Which method? Unlocking (or re-locking) the bootloader always wipes your phone. As long as you follow the instructions in Post #2 (where it says to remove the "-w" from the flash-all.bat or flash-all.sh), updating your firmware won't wipe your phone.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Oh, three kernels now (makes sense since Kirisakura is based on CleanSlate):

https://xdaforums.com/t/kernel-cleanslate-t1-4-0-s2s-adblock-vib-batterysvr-oct-24.4509793/

Yeeeha!
[Google Pixel 7 Pro] wr3cckl3ss1:
This was short lived. As a factory reset reverted what i originally did to carrier unlock the Pixel 7 Pro. But before I did reset. I did attempt a few AT commands in hopes of finding another way in but didn't work. If your familiar with Samsung devices and Device Services. I believe this pixel and many others carry a certain package that acts the same. I removed (com.google.android.apps.work.oobconfig) .I got the phone Thursday....activated and installed....set it up like normal. Last night I ran into a guide from P7P that talked about carrier unlocking it, so i did the steps and to my surprise, my non Verizon sim (T-Mo MVNO) worked and picked up 5G UC.

Here is the guide I followed to achieve this.....I will add....that this guide is specifically tendered for T-Mobile P7P. So those that are looking for that carrier unlock for T-Mobile. I would suggest looking here. *Warning* Following this guide....WILL WIPE YOUR PHONE.

https://www.getdroidtips.com/unlock-sim-google-pixel-7-pro/

And of course also changed the error on OEM toggle to "connect to internet". There has to be something more to it that i haven't found yet. And i believe it's just a matter of tricking the OS into believimg that it's carrier unlocked. Was also thinking about looking into that package specifically and seeing what it's triggers are. Sounds kind of far fetched but at the moment I'm also dealing with S908U S22 Ultra, the mother of no BL unlock. And to be blunt. I've came a long way as part of that phone has been breached. (See pics attached). If that phone can be breached....it should be a little easier on the Pixel 7 Pro.

@roirraW "edor" ehT , your more than welcome to use my pics and testimonial.

Edited 10-24-22
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's very interesting. Been a long time since I've thought about AT commands. Since the OEM unlocking isn't, or at least isn't only tied to being carrier unlocked, though, I'll hope for the best...

Thanks for sharing what you have, and of course, there will be tons of people who will be interested in what else you uncover.
[Google Pixel 7 Pro] wr3cckl3ss1:
If youre okay with it. I can link the guide (non-XDA) or edit my response from earlier to add in the whole package name. But yes AT became dead on A10 and up. But you'll be surprised at what you find and how relaxed companies tend to be. Where one thing dies or disappears one year, it'll reappear years later, as if the method was forgotten. Case in point, S22 Ultra. I ran a very old script on it and to my surprise it put me in a very Qualcomm spot, which shouldn't of happened. Other factors are involved that i won't disclose yet but it's amazing how companies think that stuff can easily be forgotten. I barely started messing with all this months ago and didn't know squat besides simple adb commands but now I'm all in and slowly making progress. I'll keep watch on this thread and update as needed, if there's something that i find. But for now...I'll sit a day or two and see if i can replicate what i did. See if i can remove said package. Wish me luck lol
[Google Pixel 7 Pro] klark1kent:
Apologies, first time Pixel owner here, coming from Samsung and LG so this is a bit foreign.

But - Is anyone familiar with the Internal SD Card being displayed twice when device is connected to computer? I had already successfully unlocked bootloader, rooted, etc. ... using the Factory Image TD1A.220804.009.A2, but today I updated using the Factory Image to TD1A.220804.031 and ever since my PC has shown two Internal SD Cards in File Explorer with identical storage / files. Specifically, this occured after performing the instructions for:

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

I did notice that on separate thread with instructions for monthly updates, there were several additions to the flash-all.bat that were not present in the method described in this thread. Most notably: fastboot --set-active=other

I am assuming this has something to do with the dual slots of this device, but not entirely sure what I did wrong, how to correct, if it changes things causes issues with the device storage.

Any guidance would be appreciated

(Sidenote, The update seems to have worked fine, I'm updated with root and data appears all there)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Whatever you want to do is fine with me.

I was thinking more like I haven't thought about AT commands in 20+ years. :D

Indeed! I do wish you luck. I look forward to hearing your results.

Hello! No apologies are necessary. I have been familiar with both of those in the past - still with Samsung since I have a tablet.

I've seen that before, but not predictably. It may have even happened on my HTC 10, I don't recall for sure. I just know it's happened to me. I don't know why it happened. A reboot of either the phone, the PC, or both, would likely solve it, although it shouldn't actually cause any problem.

I'm 101% certain you didn't do anything that affects how the internal storage is presented, and I'm not a betting man, so I'm very certain of that. :)

Yes, you can change slots and flash the other slot. I'm not against it - and I might eventually add that to my instructions, I just haven't gotten around to it. It's just different ways of thinking about things - neither way is the one correct way, and my own instructions actually mention yet a third method which is to use the Android Flash Tool, although in that case, changing slots manually might make sense as well.

Thanks for reminding me about changing slots - I'll try to consider that again and decide if I'm going to add it to my instructions soon, but you're not technically missing out on anything. Google's instructions for updating don't mention that, as it's really just a secondary consideration when updating, not a requirement.

I hope that helps, and I can go into more detail if you have more questions, although one reason that, believe it or not, I try to limit the scope of my instructions is to keep things as simple as possible. I don't want too many branches in the instructions of "if this, do that", or such.

There is already so much information and I'd like to prevent "information overload". When you become comfortable enough with the process as it is already, you can decide if you want to do things slightly differently.

I'm glad everything worked well for you!
[Google Pixel 7 Pro] Jon.StatiK:
What adblocker is everyone using these days? Is AdBlock still good and do we need to enable the systemless hosts in Magisk?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, you need to enable systemless hosts for the SafetyNet instructions in Post #2. I haven't installed AdBlock yet on this phone, but I was using it on my Pixel 6 Pro before I sent it in for trade-in.
[Google Pixel 7 Pro] dd805bb:
FYI to anyone wanting know, TMO T Mobile version can be unocked, sim and bootloader. once sim is unlocked oem unlock is not greyed out anymore. not paid off either.
[Google Pixel 7 Pro] Jon.StatiK:
Got it running with Adaway. Thanks for the help and info!
[Google Pixel 7 Pro] bigknowz:
Try to add bank app fingerprint after flashing November update and before re-rooting. That's how fingerprint add works with Chase app.
[Google Pixel 7 Pro] badabing2003:
I wouldn't worry about it, I have seen this happen with other pixels as well, it only happens briefly during startup.
[Google Pixel 7 Pro] blackspp:
Using adguard on all my devices (linux, windows, android) and afaik it is the only blocker that blocks everything.
[Google Pixel 7 Pro] kornball:
I use AdAway installed from F-Droid. Works well with systemless hosts.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Cool, you're welcome!

Yep, thank you. That's exactly what I plan on doing. I'm too lazy to purposefully unroot before then to use the workaround. I just figured I'd test if that Hide Apps List Xposed Module would do the trick. Oh well! :)
[Google Pixel 7 Pro] kornball:
This may not be the best place to ask, but I am hoping someone who understands Displax's USNF mod may be able to confirm.

When my Pixel 7 backs up using Google One, Google sees my phone as a Pixel 3. I am assuming this is something USNF spoofs in order to help pass safetynet?
[Google Pixel 7 Pro] Lughnasadh:
Yes, that mod changes your fingerprint and applies it to the GMS SafetyNet process.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google's Backup still sees my phone as a Pixel 7 Pro, and I'm using USNF 2.3.1 MOD 2.0. Is there somewhere else I should check to see if it's possibly showing as a different Pixel?
[Google Pixel 7 Pro] kornball:
Check within the Google One app. If I check under "Backup" in settings, it says Pixel 7. If I go into the Google One app (or one.google.com), it says Pixel 3
[Google Pixel 7 Pro] roirraW "edor" ehT:
I completely believe you, but for some reason both other places still say Pixel 7 Pro for me. Weird:
[Google Pixel 7 Pro] badabing2003:
By any chance have you applied any build.prop changes aside from the safetynet mod ?
[Google Pixel 7 Pro] xstefen:
Spoiler content hidden.

Google LLC Device Database

device.report
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, I'll add I've added to the post.
[Google Pixel 7 Pro] thenewdroid:
First of all, thank you so much for the detailed instructions. I have not rooted my phone in about 5 years, your tutorials made it so much easy!

One question thought - my Pixel 7 Pro appears as 'Huawei Nexus 6P' in my goole account. Based on this post looks like it is due to the safety-net fix? Is there a way remain rooted with safety net and appear as Pixel 7 Pro?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi! You're welcome, glad to help!

Coincidentally, we were just talking about that. See my replies to another user who Google sees as having a Pixel 3 up a few posts from yours starting here:

https://xdaforums.com/t/unlock-boot...gain-all-relevant-links.4502805/post-87629375

Maybe it's some kind of randomization since my phone shows up as a Pixel 7 Pro everywhere, still. In either case, I don't have any ideas, but hopefully someone else does.

Edit: Maybe @Displax has some ideas?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Maybe @Displax has some ideas?
[Google Pixel 7 Pro] kornball:
Nope. Only thing I have installed is Displax's USNF mod 2.0 and systemless hosts
[Google Pixel 7 Pro] roirraW "edor" ehT:
@pndwal, thank you very much for that information. Does it make sense that with MOD 2.0, my phone still shows up as a Pixel 7 Pro, another user the Pixel 3, and yet another one, Nexus 6P?

Edit: See @kornball's post below this one. Maybe after some time, it's reflected correctly.
[Google Pixel 7 Pro] kornball:
I just checked "Google One" (both app and browser), and my phone is now labeled correctly as Pixel 7.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thank you for sharing that.

@thenewdroid

@Lughnasadh
[Google Pixel 7 Pro] pndwal:
Not making total sense to me ATM either... 🤔

Seems largely Pixel 6 and 7 user's get phone showing in Google accounts as Huawei Nexus 6P ... I assumed this was consistent but seems it isn't...

I just installed @Displax mod 2 (I've been on official USNF till now as mods are not needed on my Xiaomi RN8T w/ A10 MIUI for deviceIntegrity)... My device shows properly as RN8T w/ Google!...

Could the affected users be setting up new accounts and existing ones simply don't check for GMS fingerprint changes?...

I see @Displax seemed baffled by this too:

https://xdaforums.com/t/rooted-pass...ntactless-on-a13-stable.4480819/post-87385703

... Other users also chipped in w/ same issue but @Displax didn't comment further...

Anyway, whether this affects new accounts only or maybe various prop combinations are used to determine device model or possibly there's completely different factors at play, users are still getting the purposely set fingerprint value...

In the case of @kornball w/ 'Pixel 3', it makes less sense... I'm suspecting either MHPC may still be active w/ some spoofing set, or again, Google Account may have initially been set up while such 'device simulation' was set in MHPC or other module... Or something completely different! 🙃🤔 PW

www.youtube.com/watch?v=lPQptu5CYi4

Edit... Seems it was, in fact, something completely different... (See post above.) 🤪
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! It remains to be seen, or not seen.

Spoiler content hidden.