yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] badabing2003:
yes, and you have to make sure that the patched magisk init_boot is from the init_boot.img of that firmware's version, you can't use the one you made last month on the new firmware.

That's fine.

Yes, all files, otherwise when you run flash_all it will miss files that it needs.
[Google Pixel 7 Pro] halfbytecode:
I was wondering before buying a Pixel 7 Pro, is it possible for us to restore hard bricked units, as for a lot of the phones but with Qualcomm processors?

Since people with Pixel 6 (Pro) have had issues while upgrading to Android 13 and the anti-rollback mechanism, with the phones bricking if the upgrade process is not followed correctly.
[Google Pixel 7 Pro] EtherealRemnant:
The Tensor chip seems to have a low level mechanism like that but there has never been any leak or even any evidence that Google themselves have access to such tools from Samsung. It seems like the chance of someone figuring it out are pretty slim.

https://xdaforums.com/t/guide-unbrick-pixel-6-oriele-or-pixel-6-pro-raven.4441245/post-87764133
[Google Pixel 7 Pro] halfbytecode:
Thanks for the reply. I wonder if I should get a Pixel 7 Pro or another phone but with a Qualcomm processor that allows users to recover from hard bricks.

Recent OnePlus phones have been notorious for being locked down for users in this regard. Limited progress seems to have been made for OnePlus 10 Pro, but OnePlus 11 seems even further locked down.
[Google Pixel 7 Pro] EtherealRemnant:
Bricks of Pixel devices are quite rare. Bricks of OnePlus devices? Dime a dozen. Now that OnePlus has switched to requiring VIP signatures to use the MSM Tool on the 9RT and after, they're no longer an option for me.

I had to use the MSM Tool on my OnePlus 9 more than 5 times because of how easy it was to brick the thing (and I am not a newbie, I've been unlocking and rooting my phones going back to the HTC Hero in 2009 and before that, I was modding Windows Mobile devices going back to 2006). It was the first phone I've ever managed to brick to the point of needing a restore tool - the worst I ever had before that was a boot loop.
[Google Pixel 7 Pro] pndwal:
In case this hasn't been resolved for some (nb. I follow here only spasmodically), and some have

Google One app and Google website account showing device as Huawei Nexus 6P,

in response to this:

I posted this response a short time ago:

Happily it seems my supposition was largely correct and the user was able to restore P7 Pro as device showing in Google One app and Google website account this way:

... Hope it helps some here. 🤠 PW
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, @pndwal!
[Google Pixel 7 Pro] halfbytecode:
I wonder if Pixel 7 Pro will have the same issues that some Pixel 6 (Pro) users with the anti-rollback feature, in the future when a new Android version comes out.

It would have been great if we had access to the necessary tools to recover from hard bricks.

I have also been flashing ROMs and stuff, for more than a decade now. Personally, I never had any of my devices hard bricked. Thankfully, all I had to face were bootloops at times, while flashing a ROM/kernel/some other zip file.

TWRP has always helped me in worst case scenarios, even for backing up all my data to a USB drive when my earlier phone developed a hardware issue, began overheating, and rebooting over and over while trying to boot into Android.

I think I even made a Nandroid backup from within TWRP, and used Titanium Backup to extract and restore all the app data on my new phone through that.

Here's hoping TWRP is able to add support for Pixel 6/7 series soon.
[Google Pixel 7 Pro] Lughnasadh:
The Pixel 6 series was a specific case where a security vulnerability was found in the A12 bootloader, therefore leading to the anti-rollback measures in the A13 bootloader. They didn't want people using that A12 bootloader with the security vulnerability.

Unless a similar vulnerability is found in future A13 bootloaders, it's not likely that we would have to worry about it.
[Google Pixel 7 Pro] Nyu_Tux:
Hello everyone, I'm not sure where to post this, please tell me if there's another place for this but it concerns the updating process.

I just woke up to my P7Pro completely bugged. The alarm was ringing but the screen was staying black and totally unresponsive. Eventually it stopped ringing, I managed to reboot it and now it's stuck on the Enter PIN screen. When I type my PIN the screen goes black but nothing actually happens and if I wake it up I'm still stuck on PIN keyboard.

So I though I might try to do the January update (I'm on last month's one still), but the problem is I can't do this:

Made sure all Magisk Modules have been updated.

Disable all Magisk Modules.

UNhide

Magisk!

because I don't have access to the OS. I'm kinda lost RN and honestly very nervous. If you guys can point me in the right direction there that would be much appreciated. I wrote this in a rush so I might have forgotten to provide basic information, please let me know if you need anything else.

Thanks in advance.

Edit: Oh and btw, the "adb devices" command returns: "[random numbers and letters] unauthorized"

I don't remember how it was before but I'm pretty sure it didn't say "unauthorized" :(

Edit 2: I don't care about factory resetting the phone if that's the way to go, I just need it functional asap.
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
@pndwal I got this resolved by a process of elimination and found out that having play store in the deny list caused my phone to show up as a Nexus 6 in the security tab of Google account under devices using Displax's mod. Once removed, I was able to use everything else BAU with Shamiko. Banking accounts, wallets, play store certified, company portal intune all worked fine and my phone shows up as Pixel 7 pro.
[Google Pixel 7 Pro] HipKat:
You may have to reboot to recovery and do a factory reset from there or try to boot to safe mode and see if you can get into your OS
[Google Pixel 7 Pro] Nyu_Tux:
Thanks for the quick reply! I just tried taking the SIM card out, it allows me to get into the OS and use the phone so that's cool, I just can't get phone calls/SMS for now but I'm already relieved. As soon as I put the SIM card back in I'm back to where I was before.

Ok I just tried safe mode and it's weird because it's actually worse:

with SIM in: same as before, typing the PIN doesn't do anything and I'm stuck with the numpad

without SIM: exactly the same but with the device PIN that you have to type after reboot

So I can get to use the phone normally without the SIM but not in safe mode. wtf...

Edit: Looks like safe mode actually fked me up, now I can't get back to normal, the "Back" soft key that had appeared on the bottom left of the disply in safe mode is still here after normal reboot, and I can't get past that "device PIN after reboot" screen even with the SIM card out, just like in safe mode before. :(
[Google Pixel 7 Pro] Nyu_Tux:
Ok nvm, I was just waiting after inputting the PIN because I was used to the auto unlock feature, pressing the arrow key let me in. But the weird thing now is I'm stuck on safe mode, even when I just reboot normally it stays in safe mode. I don't get it lol I think I'm just gonna factory reset it, but I have one noob question: Will it completely put it back to normal, as in, will it re-lock the bootloader if I do a factory reset or will it still be a rogue bootloader-unlocked phone? How should I proceed?

Thanks in advance to anyone for taking the time to help me, I'm reasonably savvy but usually everything goes well so I'm not used to having serious issues like this... Probably not a big deal but it does make me a bit nervous =s
[Google Pixel 7 Pro] schmeggy929:
factory reset will not relock the bootloader. Proceed with factory reset
[Google Pixel 7 Pro] m3ath:
hi

After the December update my phone freezes and does not respond to touch

After rebooting, it works for about an hour, then the problem returns again

It has been formatted more than 10 times

The system was installed via Android Flash Tool and the same problem

But strangely, if you go to the beta version, the problem goes away completely

And when installing a custom ROM also the problem goes away

May I know the cause of the problem?
[Google Pixel 7 Pro] HipKat:
Well, I don’t know what the problem is but I know the first thing that I would do is update to the January firmware since it’s obvious your problem started after the December update
[Google Pixel 7 Pro] m3ath:
Same problem even in the January update
[Google Pixel 7 Pro] HipKat:
I'd guess it's the device, not software. Try to back up everything, flash again with a full wipe and see how that goes
[Google Pixel 7 Pro] m3ath:
Tried this more than once same problem

And what do you mean by full fermat?
[Google Pixel 7 Pro] HipKat:
I didn't say that anywhere. You mean wipe? I mean a factory reset
[Google Pixel 7 Pro] m3ath:
sory full wipe
[Google Pixel 7 Pro] roirraW "edor" ehT:
What!? No one corrected me about having "January 3,

2022

" in the thread title? :D
[Google Pixel 7 Pro] Ghisy:
Wait, that wasn't correct? :D
[Google Pixel 7 Pro] yycDAAN:
I tried Graphene OS for the past week and decided to go back to original.

- bootloader is unlocked

- am using Android Flash TOOL from here https://flash.android.com/

- Removed non-stock key prior to proceeding with Flashing

- i got to FastBoot screen during the Flash and the browser provided the following warning : '' Your device is being used by another program'' and then the Flasing process stopped.

- Am now back at the main Google screen.

- I believe Graphene OS already removed from device.

- Trying to initialize Android Flash TOOL once again, i accept ADB / Grant access to ADB keys - device does not show up in the tool anymore to flash stock OS. (see attached screenshot)

When I'm stuck at the main Google screen, I decided to factory reset.

Turned device off > Pressed Volume down > highlight “Recovery mode.” > “Wipe data/factory reset” > After reset completed, pressed the Power button to select “Reboot system now.”

View attachment 5826707

I can get to recovery, tried to update via ADB command with the latest 2 image Pixel 7 pro found here https://developers.google.com/android/ota

13.0.0 (TQ1A.230105.002, Jan 2023)	Link	0c8fdd0d42af8477338bf841524327f3aa253cf4a562eadc6a6198c3da88ed19
13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra)	Link	c1f202817b5a56ca67d2165605ed0938d118646b22bd46be67f136a5ccc5d6b0

, yet am getting this error.

Verifying update package ...

Error Recovery : footer is wrong

Signature verification failed

error:21

Ideas ?

Thank you
[Google Pixel 7 Pro] schmeggy929:
Don't know why you are trying from recovery, have you tried putting the phone in Bootloader mode(fastboot) and see if phone is recognized?
[Google Pixel 7 Pro] yycDAAN:
Thank you for replying.

got into Fastboot mode. Android Flash TOOL recognized device and was able to install the original OS . When i restart phone, get the warning page :

''Your device is corrupt. It can't be trusted and may not work properly'' . I click CONTINUE and everything loads normally.

Is there anything I can do to ensure that ''Your device is corrupt.'' page stop showing up on Boot ?

EDIT : appears once bootloader is Locked, screen disappears
[Google Pixel 7 Pro] badabing2003:
Flash factory to both slots
[Google Pixel 7 Pro] Lughnasadh:
Looks like an update to Platform Tools may be coming soon...

platform-tools-34.0.0 - platform/frameworks/base - Git at Google
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good time to mentally prepare for "Why can't I successfully flash the latest firmware" questions. :) Thank you!
[Google Pixel 7 Pro] roirraW "edor" ehT:
You likely only had to factory wipe the device (which locking the bootloader also does). If you ever want to re-unlock the bootloader, it'll wipe the phone again.
[Google Pixel 7 Pro] roirraW "edor" ehT:
404 errors on new links for now, hopefully they'll work soon.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ1A.230205.001.A2, Feb 2023, Telstra)	Flash	Link	f81c82a2687ee092b675e8329628a00dfc5ce722e47d0603c000a3dd8ddfb68d
13.0.0 (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs)	Flash	Link	f2c2d91a753f96c45cb7d31c79929eeac408ba4abff9603cf2c786e36aa87042
13.0.0 (TQ1A.230205.002, Feb 2023)	Flash	Link	4439927e14a29c71499ed7796756b7197e76096c197c7f43634638ccea89e237
[Google Pixel 7 Pro] Lughnasadh:
Links aren't working just yet.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're right! :(
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - February 2023 - Google Pixel Community

https://support.google.com/profile/79501506
[Google Pixel 7 Pro] roirraW "edor" ehT:
Pixel Update Bulletin—February 2023 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've got Aignes Website-Watcher checking the link for the February 2023 Global Pixel 7 Pro download to be available, so I'll post again when it starts working.
[Google Pixel 7 Pro] SchmilK:
If I have a rooted Google Factory unlocked device using T-Mobile e-sim, should I install the T-Mobile version?
[Google Pixel 7 Pro] Lughnasadh:
I would.
[Google Pixel 7 Pro] Paz9:
What?; How?!
[Google Pixel 7 Pro] Ghisy:
Like the monthly updates, I believe it will be released today around 1 PM PT so 4 PM ET and in the evening for Europe.
[Google Pixel 7 Pro] Paz9:
Look at a few posts prior, someone's rooted the p7p

When are the images expected to drop?

I may unlock BL and wait for factory image to drop to root.
[Google Pixel 7 Pro] Larakali:
There wasnt any release of the Firmware lmao.

How? telegram????
[Google Pixel 7 Pro] Ghisy:
I've seen that but I don't know how this is possible given we don't have the factory images to extract the boot.img (or init_boot.img apparently).
[Google Pixel 7 Pro] Larakali:
Prob chinese firmware was given out early, as the screen suggest its a chinese phone
[Google Pixel 7 Pro] Ghisy:
Maybe? I'd rather wait for the official files directly from Google.
[Google Pixel 7 Pro] Lughnasadh:
We may have to patch init_boot.img for rooting. 🤔

Was doing some digging and found this:

"For devices launching with Android 13, the generic ramdisk is removed from the boot image and placed in a separate init_boot image. This change leaves the boot image with only the GKI kernel."

@Freak07 Would you have any insight to this?

EDIT: Have been informed that the Magisk Alpha developer has said this is indeed the new way to do it, but I would like confirmation.

Generic boot partition | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] Fentadroid:
Well, let's see what will be the answer.....
[Google Pixel 7 Pro] Larakali:
Prob none or fake. If not then we will see soon...
[Google Pixel 7 Pro] Paz9:
When are we expecting them to drop the images?
[Google Pixel 7 Pro] Ghisy:
Probably today as it's release day. I forgot to type "today" in my previous post...
[Google Pixel 7 Pro] Annie the Eagle:
I guess once firmware images are out, all we'll need is Magisk to patch that image, then we can boot into that image, use Magisk to flash on the device, and then hopefully we only need USNF and DenyList to get working Google Pay, root, etc.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm sure there's no particular reason. Personally, I unlock the phone's bootloader just as soon as I can "just in case". :)

I also have the steps I take in Post #2 - Unlocking Bootloader / Rooting / Updating | Passing SafetyNet - Device Integrity and Basic Integrity | ADB/Fastboot & Windows USB Drivers.

See @Ghisy's answer below.

Interesting, thank you! I'll update the OP with the "maybe" just as soon as I can. Rather busy this morning.
[Google Pixel 7 Pro] edcsxz:
That's right, need init_boot.img

Here is my init_boot.img and my version

init_boot

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[Google Pixel 7 Pro] AndyYan:
Can confirm it's init_boot - just worked with @anirudhgupta109 and successfully rooted his unit. He'll have the images uploaded later.

The images can be extracted with DSU Sideloader and a prerooted/userdebug GSI. There aren't many such A13 GSIs yet though, so for convenience we did it on a private build of mine.
[Google Pixel 7 Pro] Lughnasadh:
Thanks for the confirmation!
[Google Pixel 7 Pro] Paz9:
So we just patch init_boot? Or is it both boot and init?
[Google Pixel 7 Pro] AndyYan:
Just init_boot. Not even vbmeta is needed (also as evident by @edcsxz only uploading a single image).
[Google Pixel 7 Pro] Paz9:
Nice!

Can't wait!
[Google Pixel 7 Pro] Ghisy:
1.5 hours later and still not working. That's weird!
[Google Pixel 7 Pro] Lughnasadh:
It happened several months ago as well. They're actually available on Android Flash Tool, so hopefully we get them soon.
[Google Pixel 7 Pro] Ghisy:
I'm not in hurry as I won't update today. I was just noticing how weird it is. I didn't remember that this happened a few months ago. Oh well.
[Google Pixel 7 Pro] jaseman:
Mine is updating OTA....albeit very slowly as is common with these Pixel devices.

I did try the links of the OTA's and they were not working but a few minutes later the OTA came through the settings on the phone.
[Google Pixel 7 Pro] Josh:
I also have unlocked phone and T Mobile e-sim (Croatia)on beta T2B3.230109.002 . What to flash,also T Mobile or normal beta ? What is the difference between builds?
[Google Pixel 7 Pro] krkhaha:
There is error whe I tried open link to download. Everyone have same problems?
[Google Pixel 7 Pro] roirraW "edor" ehT:
The URLs are working now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, all the new links were giving a 404 error up until about 15 minutes ago. All working now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you're using T-Mobile, then use the T-Mobile firmware. Usually the difference is just optimization to work on that carrier. It's likely the others would work, too, but since the T-Mobile is made to work for those using T-Mobile, there's no reason not to use it unless for some reason it didn't work well for you.

Oh! You're on the QPR2 Beta 3? Did you opt into the beta or only manually flashed it? If you flash the Stable firmware over top the Beta, you must factory reset your device, and yes, you'd want to flash the T-Mobile version.

If you opted into the Beta, you should opt out first.

Sorry about the multiple posts in a row. :D
[Google Pixel 7 Pro] Lughnasadh:
You shouldn't have to factory reset if flashing today's stable over QPR2 Beta 3.
[Google Pixel 7 Pro] Josh:
Thanks for your quick response, I manually flashed beta. I just thinking is it builds made for T mobile for locked phones and as I see from your post it was not . I can try to flash it and see what happens.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Heed @Lughnasadh's post above your response:

But things do happen, so be prepared for the worst just in case.
[Google Pixel 7 Pro] herrman0:
Anyone else have any luck getting the chase app to work properly with root. Its the only banking app giving me grief, you can sign in with password only and wont let you turn on fingerprint and wont go into the security settings in the app.
[Google Pixel 7 Pro] schmeggy929:
I see a lot of people with the same complaint on that Chase Banking app. No solution the last time I looked.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It worked fine for me once I signed in (and enabled biometrics, but that's optional) while not rooted - before re-rooting. I had been trying to remember to do it after a new firmware update when I first got my P7P, but didn't remember until December to do it before I re-rooted. It's at least mostly been fine since then. The only possible side effect I have is that even though the app lets me sign in/use my fingerprint, and it does sign in, it gives me a quick pop-up as if I just signed in for the first time, with some newbie advice.
[Google Pixel 7 Pro] NippleSauce:
I installed the Global version (using T-Mo PSim) and everything is working except for Google Pay =/. Phone service is fine and seems normal - but I also have an esim that isn't from T-Mo....but I might try flashing the T-Mo factory image to see if GPay works.
[Google Pixel 7 Pro] otonieru:
Flashed in 152s. Lucky me i forgot that we are on February already, and only check this thread just now, just when the link was fixed. Lol.

Thank You again
[Google Pixel 7 Pro] Wmateria:
Battery is eating up even with the latest KiriSakura kernel installed, and Wallet does not work, but January Patch it did work woth SafetyNet. Can i flash both slots back to January firmware?
[Google Pixel 7 Pro] amders:
have you try using shamiko magisk module? combine with enforce deny list unchecked?
[Google Pixel 7 Pro] Josh:
Flashed latest build T-mobile on unlocked phone and wipe data,5G not working so must root and install Network guru to enable it. Google wallet not pass not working but bank app work.

Google wallet and google play was on deny list,play was certificed. I noticed bad quality when speaking with someone. No volte . Maybe must turn back to flash global build and see .
[Google Pixel 7 Pro] NippleSauce:
GPay/Wallet doesn't work on the Global build either. I guess I'll save myself the hassle of re-imaging my phone to the T-Mo build and will go back to using my debit card for now.
[Google Pixel 7 Pro] Josh:
Successfully call the bank and activated Google wallet and seems that fine now but will see in market today is it work. What bother me is bad quality call when I speaking with someone and no Volte . My provider support 5G and activated e-sim but seems not work without root and enable it without application. Will see
[Google Pixel 7 Pro] roirraW "edor" ehT:
No, I haven't had any reason to. The normal USNF and deny list, plus setting up the app while unrooted and then re-rooting, works well enough. All my other apps including banking apps work fine solely with USNF and deny list.
[Google Pixel 7 Pro] LeshaRB:
Why can't I see new updates?
[Google Pixel 7 Pro] EtherealRemnant:
Staged rollout. Download the full OTA image and flash it yourself with adb sideload.

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 7 Pro] Schroeder09:
so wallet and safety net (integrity check or whatever it's called now) is broken on february update? I saw one comment on the previous page that battery drain is awful. Any other comments? Novemeber battery was soooooo good. I wish we could just have that back. Others have said the same thing, so it seems there is something behind this observation.
[Google Pixel 7 Pro] Wmateria:
Seems like the most recent update of Google Wallet flags as rooted phone. I downloaded the January 13 version of Google Pay and i can use my bank card normally with Magisk
[Google Pixel 7 Pro] swieder711:
Safetynet passes on my phone with Feb update and Magisk 25.2.

Google Wallet, my banking and corp apps also run fine and dont detect root.

I have Magisk hidden, Shamiko .6 installed and USFN 2.4 installed.
[Google Pixel 7 Pro] Ghisy:
Same here with Magisk hide, USFN 2.40 and deny list.
[Google Pixel 7 Pro] LeshaRB:
The question was

Why is there no notification that there is an update!?

That the phone can be reflashed manually and so it is clear
[Google Pixel 7 Pro] EtherealRemnant:
I just told you why. It's a staged rollout. Not everyone gets it at the same time. It puts less strain on the servers and giving the update to a small amount of people at each interval makes it easier to deal with if the update is broken and has to be pulled.
[Google Pixel 7 Pro] Schroeder09:
When you say "denylist" you just mean you're enforcing denylist, right? So some people need to use shamiko and extra stuff while others don't?

Is the wallet detecting root a wallet all update or part of the February update?
[Google Pixel 7 Pro] schmeggy929:
GPay and Wallet both open with no problem and GPay worked fine at 7-11 this evening.