yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] EtherealRemnant:
You needed to use the Android Flash Tool. Android Verified Boot 2 will brick if you have made any modifications to system partitions and re-lock the bootloader. This goes for any phone, just some have low level tools like MSM and Odin that will allow you to recover from the brick. AFT would have restored full stock software and re-locked it for you. Your mistake is re-locking the bootloader manually. Nobody should ever be doing this if they don't want to risk a brick.
[Google Pixel 7 Pro] Elastep:
Yes, it’s clear now.. I was under the impression that I can always use some tool like Odin as you’ve mentioned.. I wonder if Google has some secret low level tool as well…
[Google Pixel 7 Pro] EtherealRemnant:
There has never been a leak of one and Google charges for board replacements when people brick and it's not covered by warranty so I doubt it.
[Google Pixel 7 Pro] Elastep:
So they replace a an entire board when it’s software locked? It’s ridiculous… I really doubt that…
[Google Pixel 7 Pro] Homeboy76:
SafetyNet

A Google patch has rendered chiteroman's Play Integrity Fix inoperable.

chiteroman fix, V13.
[Google Pixel 7 Pro] Navalon:
Thank you for your answers. SafetyNet is the only module that I had active. Otherwise, I flashed the non-patch img, I have lost the root but I wasn't using it. My data is still alive...
[Google Pixel 7 Pro] HipKat:
I just noticed this tonight on mine.

I flashed the module but when I run YASNAC or PI API Checker, they both time out with a too many requests error
[Google Pixel 7 Pro] Homeboy76:
Additional Tools and Support

Check the device integrity verdict from any device

If you need to verify what integrity verdict the Play Integrity API returns for your app on a particular device—for example, while debugging or troubleshooting a user-reported issue—you can use the Play Store app to generate a Play Integrity API verdict for that device.

First, enable the Play Store's developer options on the device. Tap your profile icon and then tap Settings. Open the About menu and tap the row labeled Play Store version seven times to unlock developer mode.

Then, to generate a verdict from an Android device, open the Play Store app. Tap your profile icon and then tap Settings. Open the General menu and then tap Developer options. In Play Integrity settings, tap Check integrity to generate a verdict...

If you see Basic Integrity and Device Integrity, you're good.
[Google Pixel 7 Pro] HipKat:
Thanks, I posted in the thread for the fix and got the same info

It passes but Wallet still shows I'm rooted
[Google Pixel 7 Pro] Homeboy76:
Did you clear the cache and data of the wallet after adding it to the Deny list? Then readding the card to Google Wallet?

I also have a Pixel 8 Pro thread. :)

[Guide] [November 6, 2023] Root Pixel 8 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
[Google Pixel 7 Pro] HipKat:
According to the thread, PIF thread, Chiteroman recommends disabling the Deny list. The reply I got in there though was to clear cache on the Wallet and Google Pay, re-add my cards or wait a few days for cached verdicts to clear.

I never use G Wallet anyway but I want to make sure everything is working right
[Google Pixel 7 Pro] Homeboy76:
Try this to test if Google Wallet is working:

Add Google Framework, Pay, Play, and Wallet to the Deny list. Then clear the cache and data of Google Framework, Pay, Play, and Wallet.

disable Enforce deny list

. Then readd the card(s) to Wallet and try it.

If Wallet doesnt work,

enable Enforce deny list

and try it.
[Google Pixel 7 Pro] HipKat:
From what I’ve read that will probably work. I’ll give it a shot when I get home later today.
[Google Pixel 7 Pro] HippoMan:
I recently followed this procedure on my Pixel 7Pro, and I installed stock Android 13. I also rooted it with Magick Alpha 26401. It's working well, which is a testimonial to the completeness and accuracy of all your instructions, and I'm very grateful.

However, there is one small issue that I don't understand how to fix.

When running, I see the time at the upper left in the status bar and the battery status on the upper right in the status bar. However, I don't see any network-related icons in the status bar ... no signal strength, no LTE nor 5G indicator, nor any other related icons.

I've searched numerous times through the settings, and I couldn't find anything which controls this. I'm wondering if this might be due to some sort of error that I might have committed during OS installation, or whether this simply might be a characteristic of stock Pixel 7Pro A13 ... or whether I'm just overlooking some settings somewhere.

I previously was running stock A13 on a different device, and there indeed were settings offered regarding the display of these and other status-bar icons.

And on this Pixel 7Pro, the network is functioning with no problem whatsoever.

Thanks in advance for any thoughts and ideas.
[Google Pixel 7 Pro] HippoMan:
Oh! Never mind ... I found the source of my problem and solved it! It turns out to have nothing to do with the way that I followed the outlined installation procedure, but rather, it's because of something I did soon after that installation.

I use the TeMeFI utilitiy to save restorable backups of my device's settings, including "secure" settings. I would run that on the old OS on the other device, and after I installed the stock A13 on the Pixel 7 Pro, I restored those old device's settings onto the Pixel 7 Pro. Upon examining those settings, I relaized that they contained some items which control the placement of network-related icons in the status bar. After changing those items in that restore script and re-running it on the Pixel 7 Pro, those network-related icons started appearing normally in the status bar.

Problem solved!

I should have realized that copying "secure" and possibly other settings from one type of device to a different type of device might cause issues like this.

Something for me to always keep in mind for the future.
[Google Pixel 7 Pro] LeonHart23:
Hi guys, Idk if im asking in the right place but can't find any specific topic on xda.

My question is: is it possible to reduce or modify tiles on P7P?

They're SO big, I prefer my old Oneplus where I had 6-7 little icon all in a line
[Google Pixel 7 Pro] Slim2none4u:
GitHub - Mahmud0808/Iconify: Iconify lets you customize your Android 12+ device easily. Change icons, colors, shapes, and even the notification panel for a personalized look that suits your style.

Iconify lets you customize your Android 12+ device easily. Change icons, colors, shapes, and even the notification panel for a personalized look that suits your style. - Mahmud0808/Iconify

github.com
[Google Pixel 7 Pro] Homeboy76:
Are you asking about the tiles on the quick settings menu or the notification bar?
[Google Pixel 7 Pro] LeonHart23:
Thanks for the reply, I'm asking about the 4 big button in the setting menu. I'd love to have at least 8 smaller square buttons
[Google Pixel 7 Pro] Homeboy76:
Man you're fast, good looking out. :ROFLMAO::ROFLMAO:
[Google Pixel 7 Pro] Homeboy76:
I don't see any buttons in the Pixel 7 Pro Settings menu. Screen shot please.
[Google Pixel 7 Pro] LeonHart23:
Sorry dude i mean the notification bar
[Google Pixel 7 Pro] Homeboy76:
That is the Quick Settings Menu not the notification bar. Take a look at @Slim2none4u post # 794.
[Google Pixel 7 Pro] LeonHart23:
I tried this app but i can just modify the aspect, not the number or the dimension
[Google Pixel 7 Pro] Homeboy76:
@LeonHart23

First, you can remove icons from the Quick Settings Menu.

Second, you can take a look at the Pixel 7 Pro forum for a app that would modify the Quick Settings Menu button sizes.

If you do not find one, there is no way that I know of to modify it.
[Google Pixel 7 Pro] Fishawy:
Look for "PixelXpert". I use it alongside Iconify.

PixelXpert to modify the number of tiles, and Iconify to adjust the corners roundness.
[Google Pixel 7 Pro] Homeboy76:
@LeonHart23

Pixel Xpert and Iconify Documentation

Iconify Documentation has a link to the app.
[Google Pixel 7 Pro] HipKat:
This worked!
[Google Pixel 7 Pro] Homeboy76:
Which one worked for you?

a.

disabling

Enforce deny list

b.

enabling

Enforce deny list
[Google Pixel 7 Pro] HipKat:
Enabling it. Going into Wallet was no problem, re-added my cards, etc

Weird how I never knew about the Dev options in the Play Store
[Google Pixel 7 Pro] orpamoc:
Hi all. First off thanks to everyone that has contributed and provided valuable information regarding our devices. This community has made our Pixels much more enjoyable :)

I'm running into an issue where my device keeps getting stuck on the "Pixel is starting..." screen and cannot get past it no matter what I try. Never prompts for my PIN. Still on the tq3a.230805.001.a2 image. Did not try to update to Android 14 so not entirely sure why it is happening. I am aware of the issues devices are facing when upgrading Android version but this is not what's happening here (as far as I'm aware).

Things that were done before problem began:

1. On latest Magisk stable version, I downloaded and installed Play Integrity Fix via AMM

2. Hid Magisk app and renamed it something else in an effort to make an app not detect root

3. Cleared Google Play Services Framework cache/data then rebooted

4. After all this then the problem started happening

Things I have done to no avail.

1. Reflashed stock init_boot.img matching current firmware

2. Reflashed several other stock images while retaining data

3. Booting to safe mode but still get stuck on Pixel is starting

Is there anything that can be done to fix this without losing my data? Not sure what else to try at this point. Any help would be appreciated!
[Google Pixel 7 Pro] Slim2none4u:
Things you should try,

Different usb port

Diferent cable

Try using Pixel Flasher with verbose and debug enabled to get an idea of what is going on during the flashing process and maybe submit a support.zip for a further detailed set of logs.

My 2 cents
[Google Pixel 7 Pro] Homeboy76:
a. redownload the Nov 2023 factory image

b. check SHA 256

c. Use platform-tools r.33.0.3 or r.34.0.5

d. download Play Integrity Fix from link in instructions

e. flash factory image

f. flash init_boot.img to root
[Google Pixel 7 Pro] orpamoc:
Thanks. Unfortunately neither of the suggestions worked out. If I flash the Nov 2023 image, it reaches the "G" screen then bootloops. If I flash August 2023 image, I get past the G screen but stuck on "Pixel is starting" screen indefinitely. Happening with both platform-tools r.33.0.3 and r.34.0.5

I'll attach support.zip here in case someone that knows more than me can see what I may be doing wrong
[Google Pixel 7 Pro] mochamoo:
Well I normally manually flash the monthly updates myself. This time I wasn't aware that there was an update and my phone took the ota today and I have lost root. SO my guess is that I need to go ahead and download the update files, extract the init_boot.img file and patch it on my device, copy it over to my pc and then fastboot flash init_boot magisk patched***.img and should be good to go? Or proceed like any other monthly update and flash the full update package over the OTA first? Thought that I had better ask to be sure.

The other question is that I was using a renamed Magisk app version. The renamed and Original apps show up so not sure. Should I delete either of them? Superuser and modules are greyed out
[Google Pixel 7 Pro] Homeboy76:
SO my guess is that I need to go ahead and download the update files, extract the init_boot.img file and patch it on my device, copy it over to my pc and then fastboot flash init_boot magisk patched***.img and should be good to go?

Yes!

The other question is that I was using a renamed Magisk app version. The renamed and Original apps show up so not sure. Should I delete either of them?

Yes, both.
[Google Pixel 7 Pro] Homeboy76:
Go to this thread: Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

Post your question and support file there.
[Google Pixel 7 Pro] mochamoo:
The renamed one would be first to go or both and start with a fresh magisk install? Thanks!
[Google Pixel 7 Pro] Homeboy76:
Both, start fresh.
[Google Pixel 7 Pro] mochamoo:
All working as it should. I was a little gunshy because I ended up having to factory reset when I went from Android 13 to 14. Thanks for all that you do.
[Google Pixel 7 Pro] GuyInDogSuit:
Has there been any news on T-Mobile devices? I really hate that despite being a customer for nearly a decade, I'm told by every employee I talk to, that I must fully pay off the device first. Meanwhile, some apps can't even be installed unless I install Magisk to enable 32-bit, and there are some Magisk add-ons I'd really love to use.
[Google Pixel 7 Pro] madmuthertrucker:
Google gives you 24 months no interest payments and it's unlocked.
[Google Pixel 7 Pro] GuyInDogSuit:
I'm aware of that but that really depends on your credit, and I might as well have no credit at this point.
[Google Pixel 7 Pro] State.of.mind:
G Pay no longer works. Any ideas?

Nevermind, I searched the thread.
[Google Pixel 7 Pro] inpowers:
Anyone else having issues with updating Magisk 26402?
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release (1dcf3255) (26402)

Magisk (1dcf3255) (26402)

[Zygisk] Introduce new code injection mechanism

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] inpowers:
Yer I had to 1st unhide it to make it work. Thanks for the update
[Google Pixel 7 Pro] _bluefox_:
Hi everyone,

if I want to have one slot bootable and rooted and the other slot bootable without root, can I still deactive dm-verity and verification?

For me it did not work, but I don't know if I did something wrong or it does not work in general.

I flashed the factory image with disable verity, disable verification, to both slots, wipe all data. Then after reboot I flashed the patched init_boot to slot a, set slot a active, reboot. Result was a bootloop and after two failed tries it booted into slot b. I tried it a second time, but same result.

Going with the instruction of adb sideload OTA, doing it two times, then flash patched init_boot I got a working phone with one slot root and the other without. Then I installed avbctl and disabled verity and verificaton on slot a, as it seemed like it was not disabled. After that I could not boot into a or b and had to flash the factory again to fix it.

Did I have to disable verity and verification already when I used adb sideload OTA?
[Google Pixel 7 Pro] V0latyle:
This is no longer necessary and hasn't been since Magisk v24...Unless you're using a custom kernel that requires it

To have both slots bootable you must sideload the OTA twice.

You can only do it when directly flashing /boot but as I mentioned above you shouldn't need to at all
[Google Pixel 7 Pro] _bluefox_:
Thank you for your quick response.

I want to use the custom kernel Kirisakura and it is requiring to disable verity and verification.

My idea of having a rooted and non rooted slot was to quickly disable root so I can use banking apps and others. I often have problems hidding root from these apps, making it quit challenging to get arround it or not be able at all.

To get a rooted and non rooted slot I have to use the OTA method, but then I can't disable verity and verification. Is this the case?
[Google Pixel 7 Pro] V0latyle:
The OTA process flashes /boot, so by default, verity and verification are enabled (on the updated slot) after performing an OTA. Since you have to reflash boot anyway, you have to manually turn off verity and verification. But, you have to wipe data at the same time.
[Google Pixel 7 Pro] Lughnasadh:
Whenever you sideload the Full OTA the stock vbmeta image is installed, therefore enabling verity and verification (once you boot). So what you need to do is to sideload the Full OTA, then before booting disable verity and verification, then boot. If you sideload the Full OTA, then boot, then disable verity and verification you'll have to wipe each time since you booted with the stock vbmeta image. Repeat for the other slot.

Of course, if you currently have verity and verification enabled you'll have to wipe anyway after disabling.

Pixel Flasher can automate this for you if you want.
[Google Pixel 7 Pro] Homeboy76:
Welcome to XDA!
[Google Pixel 7 Pro] _bluefox_:
Thank you for the hint, I thought PixelFlasher can only handle Factory Images, but what a powerfull tool it can also do OTAs.

With it I got dual boot to work with disabled verity and verification (y)

I don't understand, yet, why having dual boot is only possible after flashing the OTA seperatly to both slots.

In which way does it differ from when I flash a Factory Image to both slots and then flash a patched init_boot to the other slot? What I am missing in my understanding?

For the record how I did get it to work:

Flashed Factory Image with verity and verification disabled (as I broke my system just before, to have a clean start)

Sideload OTA (unpatched) with verity and verification disabled

PixelFlasher sideloaded OTA and then flashed the vbmeta probably to disable verity and verification

Restarted afterwards automaticly

Sideload OTA (patched) with verity and verification disabled

PixelFlasher sideloaded OTA and then flashed the vbmeta probably to disable verity and verification

PixelFlasher flashed patched init_boot

Restarted afterwards automaticly
[Google Pixel 7 Pro] Lughnasadh:
You are welcome!

In a nutshell, when you flash the factory image it installs the factory image to your current/active slot, but it also installs the system-other image (basically containing odex files) to your inactive slot, effectively making that slot unbootable until you flash an image to that slot. Sideloading a Full OTA doesn't do this.
[Google Pixel 7 Pro] VerticalCobra:
My way is you chat and tell them you are out of the country and need to use another SIM so could you please unlock my phone. They have done it for both my phones over the past 3 years.

Gl!
[Google Pixel 7 Pro] UberNorse:
For anyone using Iconify for QS tile SHAPE modification I suggest disabling that if you are updating to QPR1 as it causes a system crash with a reboot to recovery stating data is corrupt and system can't boot.
[Google Pixel 7 Pro] GuyInDogSuit:
That worked for me before on my last device but not this time. They insist I MUST pay it off first. Been a customer for 13 years, wtf.
[Google Pixel 7 Pro] WhiteAsIce:
I have the osm0sis Fork installed and followed the steps, but I still only get BASIC_INTEGRITY on my device, not DEVICE_INTEGRITY. Am I missing anything?
[Google Pixel 7 Pro] jlokos:
I had the same issue when I updated to December. I went back to play integrity fix v14.2 and I got basic and CTS profile to pass and wallet is working.
[Google Pixel 7 Pro] WhiteAsIce:
Okay it works going back to Fix. I can't help but feel that this is just another temporary thing......
[Google Pixel 7 Pro] jlokos:
Probably...
[Google Pixel 7 Pro] anas sami:
After the dec update, my pixel 7 lost Play Integrity, so I flashed dec firmware with wipe data and again tried installing Play Integrity fix v14.2, thinking it might help but no luck. I was disappointed that I could not find any way to come out of this headache. So I tap on relock bootloader in pixelflasher app thinking that I'll never root my pixel again, as on every update I feel a lack of help from anywhere after updating to the latest OTA. well, things got worse after that. after relocking the bootloader, my pixel got stuck saying it could not be turned on( I'm forgetting the exact wording). By being so nervous I went immediately to the service center and they submitted the phone. the date was 07/Dec. now I'm waiting for my pixel 7 to get repaired/restored. they asked me to wait at least 15 days.
[Google Pixel 7 Pro] HippoMan:
Forgive me if the following question is considered to be OT here. If so, feel free to reply in PM or to redirect me elsewhere ...

Given that there is no TWRP nor OrangeFox for the Pixel 7 Pro which I can use for nandroid backup and restore, does anyone know whether Qualcomm EDL will work on this device? If so, I think I could use it to take full snapshots of my Cheetah device and restore them, as an alternative to nandroid.

Thank you in advance.
[Google Pixel 7 Pro] Nekromantik:
delete
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release (d7750b72) (26403)

Magisk (d7750b72) (26403)

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] rohheat:
I have pixel 7 this method is applicable to pixel 7 as well no ? Bro after unlocking the device , boot into the device and set it up and then can I install evo rom directly .. ??? I have updated to dec update
[Google Pixel 7 Pro] Homeboy76:
Yes this method works on the Pixel 7, just downlosd the Pixel 7 files.

Please post this question on the evo thread: ...then can I install evo rom directly .. ???
[Google Pixel 7 Pro] inpowers:
HI can someone please tell my why google wallet stops working every couple of days or so even thou the last update was back on the 5th of Dec. It starts working once I have update Play Integrity Fix in Magisk Modules.

Will there be a more permanent fix in the near future? Just asking Thanks
[Google Pixel 7 Pro] Homeboy76:
Try Play Integrity Fork: A link to it is in the OP, Part II, 7., Pass Safety Net.
[Google Pixel 7 Pro] simplepinoi177:
Because Google is blocking what he "spoofs" to trick and get wallet working -- within days/hours.

It starts working once you update because chiteroman manually changes "what he 'spoofs'" and includes it in the next update. But that's why "it starts working once [you] have update", and that's why it won't work for long, and that's why he updates it to another/next version so soon after that version.

No. Not in the near future. There is a bit of panic among the experts that this is an early sign of things/change that will completely shut down the way we bypass this completely.

There is a more permanent fix, but it is very involved and is a

challenge

for any who are unfamiliar with the logic/processing/internal-method of it all.

If you are interested in beginning such a challenge, reply here and/or let me know and I can give you the two pre-requisite posts/readings and a place dedicated to assisting in the "challenge"...
[Google Pixel 7 Pro] inpowers:
Yes I am using that one at the moment Oh well will see what the future brings thank you
[Google Pixel 7 Pro] inpowers:
Thanks for the reply at this time might just wait and see what happens finger crossed.
[Google Pixel 7 Pro] Lollo245:
Hello,

I was forced to install an OTA Update on my phone while out of home.

I wanted to investigate when returning home, but the phone shut off due to empty battery, and installed the update when I booted it up again.

Now I have a broken magisk app (because I hid it) and no root access.

The phone was already on android 14, and I had a couple of plugins installed (namely Play-integrity-fix, lsposed, and another one I don't recall)

What can I do to restore root access without messing up?

Thank you in advance
[Google Pixel 7 Pro] badabing2003:
Identify what version of OS is currently installed on your device, and by version I mean the exact release, not just A13 or A14

Download the matching firmware.

Extract init_boot.img

Patch init_boot.img

Flash the patched init_boot.img

Basically it's the same thing that you did the first time your rooted, except that you already have your bootloader unlocked, so you can skip over those pre-requisites.
[Google Pixel 7 Pro] synesthete:
You should still be able to find the hidden Magisk app in settings > apps > see all > [whatever you renamed Magisk to]. Then just uninstall it and reinstall Magisk, patch the img and flash the img