yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Pbsipher1:
hey homeboy76 I have the spectrum variant of the 7 pro on the Verizon network. the phone is not paid off and ive only been on their network less than 30 days came from metro PCs of 16 years. this is my first pixel. I've rooted almost all my phones since 2017 and up until recently have never had to network unlock in order to oem unlock. actually only phones that I needed to do that on ever was one+ devices but had a work around to bypass with a adb shell command. I'm sure there has to be a cmd line shell that can be called just no luck in finding it ..........yet. I did come across a dialer code. *#*#0702#*#* which brings up a menu for ims sim1 sim2 provisioning and policy, esim provisioning and more all of which are editable. kinda like a build.prop editor ui. could there possibly be something in this menu that would allow us to change the ability to unlock oem without carrier unlock. I have attached some screen shots but it's not even close...... to all the options available I can take more screenshots if somehow I found something no one can access but doubt it. I only consider myself a noob, is self taught and only reason I have the knowledge I do have has all been picked from geniuses such as yourself here on XDA. Let me know pls if there could be hope in this device after all . my window to return is coming quick only 7 days thanks buddy
[Google Pixel 7 Pro] psymsi:
I had a security update required before taking the Feb 2023 OTA update so YMMV, but this did not work for me.

I selected "restore images" from Magisk, then once the update had downloaded, I had to select "Restart" to start the install - no other option. Once installed, it rebooted so couldn't install to inactive slot and lost root.
[Google Pixel 7 Pro] Enddo:
any word on rooting Android 14 with on this phone yet?
[Google Pixel 7 Pro] simplepinoi177:
I know I wasn't the one you called out to ask advice from, but I would suggest you return it. If it is a Verizon variant -- even a MVNO -- there is a highly unlikely chance you will be able to unlock the bootloader; even if you pay it off and/or can get it SIM unlocked. Verizon variants are notorious for not allowing to unlock their bootloader. I might suggest taking more time to research it properly to see if your device is or isn't bootloader unlockable, but since you said you have 7 days only to return, and I'm speaking to you 3 days after you asked your question, if unlocking the bootloader and rooting is a priority for you, I would just directly return it within the return period and obtain a P7P that is unlocked (either from Google store or 3rd party[Swappa]). You might have better luck on an AT&T or T-Mobile variant; but both of those have various other (difficult) requirements to be able to unlock the bootloader as well -- just not as impossible as Verizon.

Good luck to you!
[Google Pixel 7 Pro] Lughnasadh:
Root works fine. May have to use Canary 25206 for Zygisk to work, not sure. There's a whole thread for A14 DPs here.
[Google Pixel 7 Pro] rester555:
Does the newest platform tools work now? Still bugged?
[Google Pixel 7 Pro] Homeboy76:
<Removed>
[Google Pixel 7 Pro] Pbsipher1:
thanks for the reply. I was just on the phone with spectrum who is my carrier and cable co. and they use Verizon lines. they explained as soon as it's paid off, that option will be opened but damn man that's pretty much the whole reason I got it was official beta firmware from Google. i thought as long as official from Google no need for oem unlock to flash but I was misinformed
[Google Pixel 7 Pro] simplepinoi177:
Wait...some clarification requested -- although, it seems you'd be past the 7 day return period anyways...

The " i thought as long as official from Google no need for..." is confusing me a bit; Did you get it from Google Store? Did you get a Verizon variant from the Google Store (because you can still get that, although that is quite foolish as getting a carrier unlocked version is just as viable and available, I never saw the reason to get a carrier variant from the Google Store -- the whole reason ordering from the Google Store is usually to

not

get it carrier variant)? I've never heard of the "if you pay it off fully, you'll SIM & bootloader unlock" off any

Verizon

device -- unlike T-Mobile or AT&T... Are you certain this is the set up for your device? I mean, it could be that they employ and have your device is set up as a T-Mo or AT&T or some kind of restricted device from Google Store, but I wouldn't be able to understand why Spectrum would go that route versus merely using Verizon variant devices (which they are a MVNO of)....

In the end, I hope the person you spoke with is certain and you don't run into any issue after, however long it takes to pay off, you find that they aren't able to allow OEM unlock in any case...:eek:
[Google Pixel 7 Pro] Pbsipher1:
no unfortunately I did not get it from google. I bought it from spectrum but I was under the assumption that as long as beta firmware was official from Google you were able to flash without oem unlock. kinda like an ota release. not sure how I came to that assumption. yes it's a 24 month loan and by then I'll already have traded in for something else. so I guess I'm SOL or if somehow I can get someone who knows a little about the carrier config setup menu I found in my device I posted yesterday to look into it. I've posted about it in a couple different threads but I can't get any responses. almost like it's invisible or something. idk......
[Google Pixel 7 Pro] simplepinoi177:
You should be able to get on the QPR beta firmware without an unlocked bootloader. You have to "enroll" in the program, then I believe they push the update to your device (I guess kinda like a OTA; sorry, I've never participated in the QPR program).

Just be aware

that if you choose to leave the beta program before it is updated to the official stable Android 14 release, it

WILL

wipe your data -- from what I've read in some random articles, updating into the QPR should retain your data as well as when it leaves and updates the beta program to the official release.

I'm sure there are other far more knowledgeable and qualified users here that would be able to guide you better, but on a cursory Google search, you can sign up for the beta program HERE and I imagine you can merely/simply follow the instructions from there; and/or ask or follow instructions from users on this forum.

Hope this helps...
[Google Pixel 7 Pro] Lughnasadh:
With the A13 QPR betas there is a window which begins just after the stable QPR is released where you can unenroll without having to wipe. For example, those enrolled can unenroll after they install the stable March QPR2 build without having to wipe, as long as they do it before the next QPR beta is released. This is unrelated to the A14 Developer Previews or the official stable A14 release which will happen in Aug/Sept.
[Google Pixel 7 Pro] Homeboy76:
Update Magisk Canary

app-release_7dbfba76-25207.apk

Note: Tap 3 dots (...) across from 10.7 MB, Tap Download
[Google Pixel 7 Pro] Lughnasadh:
This version has a bug in it where it won't allow you to open up the app. It's been fixed so hopefully a new version will be released shortly. Suggest people wait for the new release or use the debug app.

Magisk app crashing on appstart (25207) · Issue #6637 · topjohnwu/Magisk

Context: The canary build has been installed and the app would immediate crash when clicked. Uninstalled and reinstalled to make sure it wasnt related to the app being hidden before, same thing hap...

github.com

Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk

Fix #6637

github.com
[Google Pixel 7 Pro] Homeboy76:
<Deleted>
[Google Pixel 7 Pro] Homeboy76:
Thanks for the update.
[Google Pixel 7 Pro] Paz9:
Kdrag0n or Displax's safetyNet Fix for the p7pro? What's the difference
[Google Pixel 7 Pro] simplepinoi177:
Others should be able to elaborate (better), but as I understand it, Kdrag0n is the original maker of the Universal SafetyNet Fix. Displax is a "branch" off of Kdrag0ns; I believe the story goes that, USNF at one point wasn't working properly for the Pixel 6 (and later the Pixel 7's), so Displax made a modification (MOD; which is why you will see the word "MOD" in the filename of his module) that made it work properly with the P6 (P7, as well as some others I imagine). But Displax has always maintained and stated that his was meant as a "temporary solution", and once the original had all things addressed and working perfectly with the P6 & P7's, he would probably no longer develop his mod and we should all refer to the original at that point (he states it HERE). It went well after January's firmware update, but Kdrag0n's has again stopped working perfectly after February's firmware (and/or Feb's Play System update) -- Google had done a number of changes in terms of root detection and different security checks.

But I just saw in roirraW "edor" ehT's guide/thread that roirraW "edor" ehT stated that Displax had started his own "independent OP" for his mod, so there's that to consider now....
[Google Pixel 7 Pro] Paz9:
Explains why my play store looks different on displax I suspect some spoofing happening? Some apps don't appear when I search and it looks slightly different, but play store remains certified only in displax, I think wallet still works with both?
[Google Pixel 7 Pro] simplepinoi177:
Play store looks different...? I haven't noticed any difference in mine, but then again I'm not super well versed in how Play store looks...

Yes, I believe there's some specific spoofing that happens in his mod that helped specifically the Pixel 6 and Pixel 7...

I know that some apps won't appear if you don't pass "INTEGRITY" checks and/or play store is "certified", but I haven't gotten that with Displax's mod. Maybe you'll need to clear cache & data of Play Protect Services, Services Framework, Play Store, and maybe even Play Services -- this will reset a lot of Google settings and/or your cards in Wallet. Then, you'll also need to restart; I just found this out yesterday where I wasn't passing and root was being detected, even after resetting all of those, but after restarting, everything passed. Also, it's important to pass in the apps Play Integrity API Checker and YASNAC (other than "MEETS_STRONG_INTEGRITY")...If you're not passing those, it's very much unlikely to be passing Wallet, banking apps, video streaming apps, and/or seeing certain apps in Play Store.

Kdrag0n's USNF didn't fully pass the "INTEGRITY" checks, so for many people, they weren't able to get Wallet or other services to work. But Displax's seems to have gotten everything back on track -- at least for Wallet; or at least it has for 2 of my Pixel 7 Pro's...
[Google Pixel 7 Pro] supermansaga:
25208 Canary can now open, though it lacks the usual reminder that it needs to reboot to finish setup and grant itself superuser right. So where do we go from here? Flash the init_boot one more time with this new Canary? I first did the problematic 25207 version over the hidden 25206. So there is that.....Thanks
[Google Pixel 7 Pro] Homeboy76:
Update Magisk Canary

app-release_e5641d5b-25208.apk

Notes:

Tap 3 dots (...) across from 10.8 MB, Tap Download

Will not hide Magisk
[Google Pixel 7 Pro] supermansaga:
I tried it, but as i mentioned in #259, it doesn't know to reboot itself to grant super user rights and enable the rest. Should we patch init_boot.img again and re-flash? I submit to you that I forgot to unhide the previous 25206 first, before I tried 25207 which crashed. Many thanks.
[Google Pixel 7 Pro] Homeboy76:
Updating to Magisk Canary 25208 should be done via the Direct Install method.
[Google Pixel 7 Pro] gpvecchi:
Can't hide Magisk with 25208...

Does anyone have a link for Canary 25206 please?
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary 25206

app-release_831a398b-25206.apk
[Google Pixel 7 Pro] supermansaga:
direct install meaning via the 25206 internal method? But I already ran into the 25207 issue. Now 25208 appears to be no longer crashing but with its capability castrated since it has bo super user right anymore. not to mention I forgot to unhide magisk first. So right now the hidden one keeps crashing as I open its shortcut. Thanks
[Google Pixel 7 Pro] supermansaga:
I agree with this. I had to re-wipe my phone after this 25206>25207>25208 canary disaster. With a brand new Feb 2023 release, 25208 just can't hide itself. Is topjohnwu aware of this? Hard to find the issues page. Debug doesn't work either. Also need to go back to 25206
[Google Pixel 7 Pro] Homeboy76:
do know why you had to wipe your phone because of issues with magisk.

Yes topjohnwu is aware of the issue(s) with Magisk 25208: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88223503

I suggest you use Magisk 25206 (link at post #264 above) until Magisk 25208 is fixed.
[Google Pixel 7 Pro] supermansaga:
Essentially I can't boot with either partition a or b. So I had to wipe it. No way to boot into recovery or rescue mode either. What could have been the trick to resolve this?

I just spent 6 hours to restore the majority of apps which still refused to be grouped in the same way on the home screen. Wished TWRP could have supported Android 13 by now. Thanks.
[Google Pixel 7 Pro] gpvecchi:
I managed to downgrade to 25206, hide app, then upgrade to 25208. This works.
[Google Pixel 7 Pro] Guivre:
I recently noticed that my P7P is failing the "CTS profile match" check in YASNAC. Basic integrity passes but device integrity fails. This is on the December security patch and it was working fine at the time I installed it. I updated to Magisk Canary 25208 (with no improvement) before coming into this thread and seeing others having problems as well. Do you think this is related to my safetynet issue? For what it's worth, magisk hide seems to be working fine for me on 25208.

EDIT: I fixed it by installing the newest displax 1.2 safetynet MOD over my "original" kdragon version. I wasn't sure if it would cause issues but it looks like it was a seamless upgrade.
[Google Pixel 7 Pro] Homeboy76:
Glad you got it working, sorry you had to wipe your phone.

When you wrote" just spent 6 hours to restore the

majority of apps which still refused to be grouped in the same way on the home screen

."

I don't understand why you can not place an app any where you want it on the Home Screen.

Unless, the grid was changed back to the default

App grid

setting when you wiped your phone.

When I have a problem with a installed Magisk manager App that is

bad

, I do the following:

Unroot by flashing the

unpatched

init_boot.img to both slots:

fastboot flash init_boot --slot all init_boot.ing

Remove all Magisk Manager App(s):

Settings ==> Apps ==> Show all apps

Find the Magisk Manager App(s) and delete.

If the Magisk App is hidden look for a settings app, this is normally the (default)

name given to a hidden Magisk Manager App.

NOTES:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88230843

If the hidden name of the Magisk App is settings be extremely careful removing it, you do not want to delete your Settings app.

Install the Magisk Manager app I want installed.

Patch the init_boot.img with the newly installed Magisk Manager app.

Flash the newly patched init_boot.img to reroot.
[Google Pixel 7 Pro] chuck4100:
Is there a way to clear Google Play Services without disconnecting a android watch i.e. Galaxy Watch5?
[Google Pixel 7 Pro] supermansaga:
May I ask why root checker keeps saying my device isn't rooted, despite it seems it is? Though currently network signal guru app says I am also not rooted, the rest work. I swear I have flashed the 25206 patched img to both partitions/slot a and b. I have no appetite to wipe my phone. Thanks!
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release_2717feac-25209.apk

Notes:

Tap 3 dots (...) across from 10.x MB, Tap Download
[Google Pixel 7 Pro] simplepinoi177:
Serious non-sarcastic inquiry...

What are the good reasons for you to be on beta/canary? Especially considering that it being an "experimental" version (meaning there are already inherent risks incorporated), it potentially wrecked your device where it takes you something like 6 hours to set things back to normal (I, too, also wish TWRP was available; it really was so much easier and complete to implement a nandroid backup). I mean, I understand the need to apply a Beta or Canary version to a phone or OS or ROM where root isn't being achieved successfully or normally, but AFAIK, Pixel 7 Pro Android 13 (non-QPR beta), the stable release works well enough. And I would think employing an app like Swift Backup in tandem with the Google Backup should restore most of the apps and settings lost where it wouldn't take 6 hours...?

*after some consideration, all this is invalidated if you are running a custom ROM (but I have my doubts because you complain about not being "grouped in the same way on the home screen" which you would have the expectation to for stock and not a custom ROM[because it might be the way the custom ROMs written]) or on QPR beta...

I appreciate the clarification!
[Google Pixel 7 Pro] supermansaga:
As a newbie, when I read an article at https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/ that says, "While the current stable version of Magisk can patch the Pixel 7's init_boot image, you might want to opt for the bleeding edge Canary build of Magisk for additional fixes," that was good enough reason for me. Never had I imagined it to have so many issues.

Not smart enough to try any other custom ROMs. Back to default Feb 5 QPR 1 stable, what's interesting is my mum's Google backup could restore the grouped icons on home screen but not mine. Why is that? Not restoring the groups is my biggest pet peeve, in addition to adding back email accounts. Btw, Is it safe to try 25209 now? I want to give that a shot only because my 25206 was again told to be incomplete by Fox's MMM. Thanks

To fix the said issues, I disable the existing modules and reboot. Then i think the several apps start asking for superuser rights again, so I am good on that. And after some roller coaster rides on 25209 incl. hidden "settings" app were having issues restoring and thus requiring installing the original, etc etc, I am now at 25209 without wiping my phone. Phew. My only remaining problem now is the 5G can't be enabled even with Network Signal Guru app's trick, probably because I have another eSim on the phone. China Telecom agent said that could be the cause of P7P only working in LTE (after foobar66's module) (for now).

Wallet and SEP Mobile are fine with Displax Safety Net fix and Shamiko. I did delete my work profile first before I tinkered with upgrading 25206 to 25209. But Company Portal is still screwed.
[Google Pixel 7 Pro] myi500:
Is the LSPosed addon the only option to get MicroG installed on Pixel 7? Is that safe because all of the devs are in China/HK.
[Google Pixel 7 Pro] supermansaga:
They just ignored a bug. https://hub.fgit.ml/LSPosed/LSPosed/issues/2417. Geo Setter module seems to be quite capable.
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary

app-release_2717feac-25209.apk

Note: Not fixed!

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88237343

https://xdaforums.com/t/pixelflasher-for-google-pixel-7-pro-support-thread.4505287/post-88240637
[Google Pixel 7 Pro] supermansaga:
I guess I was lucky with 25209 then. Company Portal still fails to work by saying I am not in an Android Enterprise country, despite it previously worked with 25206
[Google Pixel 7 Pro] Gygun:
Hello guys. New Pixel user here. I just bought a Japanese Pixel 7 and want it to root it. In the first post it says I need to download a factory image (global) to use it. Will it remplace my Japanese versión of Android? I think there are differences (like payment methods support) and stuff, and I want to keep my Japanese Rom (but rooted). Is it posible? Will that factory Image remplace my current one? Thank you and sorry for the noob question!

Edit: the phone has this hardware chip (https://en.m.wikipedia.org/wiki/FeliCa) that I want to continue using it.
[Google Pixel 7 Pro] Homeboy76:
¯\_( ͡❛ ͜ʖ ͡❛)_/¯

Here is the limited information I found about Pixel 7 Pro / Pixel 7 Japanese Models:

Question Pixel 7 Pro US vs Japan variant by: vanthatou

Google Models:

Google Pixel 7 Pro (GFE4J 128GB)MODEL 4

Countries or regions available: Japan

Google Pixel 7 Pro (GFE4J 256GB)MODEL 5

Countries or regions available: Japan

Google Pixel 7 (GO3Z5 128GB)MODEL 1

Countries or regions available: Japan

Google Pixel 7 (GO3Z5 256GB)MODEL 2

Countries or regions available: Japan

Google is your friend!
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release_981ccabb-25210.apk

Notes:

Tap 3 dots (...) across from 10.x MB, Tap Download
[Google Pixel 7 Pro] askylitangel:
So my P7P passes SafetyNet but I cant seem to be able to use my Barclays Banking anymore. Can anyone help? (Am UK based if asking)
[Google Pixel 7 Pro] Homeboy76:
Not another broken Magisk Canary release

Magisk Canary - app-release_981ccabb-25210.apk

breaks

all modules

:

25210 breaks module loading · Issue #6688 · topjohnwu/Magisk

Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...

github.com
[Google Pixel 7 Pro] HipKat:
Did you configure that app in the Deny List?
[Google Pixel 7 Pro] Slim2none4u:
I updated:mad:
[Google Pixel 7 Pro] supermansaga:
February 2023 Google Play system update rolls out to Pixel in March, do we have to install 25209 to inactive slot to avoid rerooting? Thx
[Google Pixel 7 Pro] askylitangel:
Yea I did that. Keeps coming up with an 06 and then AND error
[Google Pixel 7 Pro] supermansaga:
Have you tried the Shamiko module? https://hub.fgit.ml/LSPosed/LSPosed.github.io/releases

After installation, you need to create a file called "whitelist" at data/adb/shamiko/. Works on my Barclays US app. I presume the UK app should work as well.
[Google Pixel 7 Pro] askylitangel:
Just installed it and still getting nothing =/
[Google Pixel 7 Pro] Phoebus89:
How does one fix this then?
[Google Pixel 7 Pro] Homeboy76:
Post# 271, When I have a problem...
[Google Pixel 7 Pro] supermansaga:
Have you also done "force stop, clear cache, clear storage?" With the Displax mod on safety net, it should work by now
[Google Pixel 7 Pro] askylitangel:
Yea did those too and nothing
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Fixed

Magisk Canary - app-release_981ccabb-25210.apk

https://github.com/topjohnwu/Magisk/issues/6688

https://github.com/topjohnwu/Magisk/pull/6690
[Google Pixel 7 Pro] rester555:
Still can't use that away after this fix. Adaway says you need to add the systemless host module and I did that. Still get an error
[Google Pixel 7 Pro] nordilf:
Nice Guid, thx.

One thing at 2) Prerequisites .... A Computer with SDK Platformtools r33.0.0 , the link gets you to r34.0. Maybe you could change the link to r33.0.3 or to the thread Platform-Tools v34.0.0 HAS ISSUES, that provide the r33.0.3 links
[Google Pixel 7 Pro] simplepinoi177:
to add on to this suggestion, if OP does not wish to direct to another Guide/Thread, you can get the URL links from THIS POST ; just be sure to credit @Namelesswonder for providing/pointing out the URL links (he, himself, may not actually be personally sharing/hosting the files, but still...)...
[Google Pixel 7 Pro] Homeboy76:
@nordilf

Thank you.

I believe the latest SDK Platform-tools is rev. 34.0.0 (RC2).

It was released yesterday (March 08,2023).

The OP has been updated.

<Edit> The SDK Platform-tools download links are still downloading SDK Platform-tools R 34.0.0 and not SDK Platform-tools R 34.0.0 (RC2).
[Google Pixel 7 Pro] bird333:
Question: What are the two slots you refer to?
[Google Pixel 7 Pro] Homeboy76:
The two slots I am referring to are the A and B partitions: Help understanding A/B partitions
[Google Pixel 7 Pro] bird333:
Thanks for the link.
[Google Pixel 7 Pro] Homeboy76:
SDK Platform-tools Update

SDK Platform-tools r34.0.0 and r34.0.1 are not working.