yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Contacts rolling out 'Organize’ tab to replace ‘Fix & manage’

After removing the navigation drawer, the next Google Contacts for Android update replaces "Fix & manage" with "Organize."

9to5google.com

Google Calendar for Android just made it way easier to scroll through months

A new update to the Google Calendar app on Android makes it much easier to scroll through months using little shortcut buttons.

9to5google.com
[Google Pixel 7 Pro] 10cheesecakes:
Im not sure what Im doing wrong at this point. I already had my Pixel 7 Pro rooted but my homie updated the phone and I lost root. SO I got everything ready and patched on magisk but now no matter what I do to after adb reboot sideload then fastboot flash init_boot "my patched magisk file" it just says waiting for device. I have all drivers installed and can detect with adb devices just fine but getting the patched magisk file is being a headache at this point and Im honestly lost as to why.
[Google Pixel 7 Pro] Lughnasadh:
You need to be in fastboot mode, not in sideload mode or recovery.

adb reboot bootloader
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm checking, just in case. Are you in bootloader mode before you try to flash it?

adb reboot bootloader

The only other thing I can suggest is rebooting the computer, using different USB ports and cables, but if adb devices works when you're in bootloader mode, then I don't know why it wouldn't work to flash.

Edit: Ninja'd by @Lughnasadh, as usual. :D At least it sounds like we're thinking the same thing.
[Google Pixel 7 Pro] 10cheesecakes:
Oddly enough, I tried in fastboot first cuz thats what I usually do and it wasn't detecting after going into fastboot mode, so I fixed the driver issues and was going into sideload for some reason. I went into fastboot mode and it worked =D. Am dumb. Thanks comrades.

PS - whats the best app for full backups now? I wanna reenable 32 bit support and that requires a wipe. Titanium Backup is no longer good T_T
[Google Pixel 7 Pro] roirraW "edor" ehT:
Things happen, it's easy to make mistakes. In some ways, especially when you do things frequently, it's too easy to forget something. Glad you solved it.

I've been using Swift Backup for app/app data backups the past 2 1/2 years. I'm very happy with it. See here for some other things that I recommend:

Post #3 - Other, most important resources:

A list of other important apps
[Google Pixel 7 Pro] hxxmor:
I'm going to root my Pixel 7, the procedure is the same as mentioned in the original post of this thread or i need to know something
[Google Pixel 7 Pro] roirraW "edor" ehT:
I keep things as up to date as I can. You can see the last edit date at the bottom right of each post. You can use Post #2, yes. :)

Let us know if you have any questions, and welcome to XDA.
[Google Pixel 7 Pro] hxxmor:
Thanks etor for the info but I can't get to post #2, it's confusing getting used to this forum
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! You can just scroll down from the top of the first page, or click on this link: Post #2

It will say "#2" in the top right corner of the second post.

You may also find helpful information here:

[Index] How to Navigate the XDA Forum

[INDEX] How to Navigate the XDA Forum Welcome, this thread has been created to encompass everything you may need to navigate the XDA Forum. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you"...

xdaforums.com
[Google Pixel 7 Pro] hxxmor:
Alright, now I'm going to get my stuff together, also can you tell me someways to backup my pixel?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android Security Bulletin—May 2024 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
May 7, 2024

:

See this document for the description/application of .005 / .B1 / .004 / .A1:

Google Pixel Update - May 2024 - Google Pixel Community

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

developers.google.com

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

developers.google.com

Android Flash Tool

flash.android.com

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] badabing2003:
What would be the difference between these two?

And what does KDDI and MVNO stand for?
[Google Pixel 7 Pro] Lughnasadh:
I think KDDI is a Japanese telecommunications company. MVNO=Mobile Virtual Network Operator, e.g. Tracfone, Mint Mobile, etc..
[Google Pixel 7 Pro] roirraW "edor" ehT:
Covered in:

Google Pixel Update - May 2024 - Google Pixel Community

:D

Edit: (The .005 is Global, the .004 is "T-Mobile, C Spire, US Cellular & Cellcom") - ("and MVNOs of those carriers" is always implied)
[Google Pixel 7 Pro] Lughnasadh:
Looks like they forgot to label the .004 as T-Mobile, etc.. on the download page. I think people on T-Mobile, etc., won't know to use the .004 unless they read the "blog" first.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I was just now able to fit T-Mobile in the thread title beside the .004, so hopefully it helps some. I couldn't reasonably fit all the other carriers. Thanks!
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, I've seen a couple of reports from people who are on T-Mobile and previously sideloaded the mid-April .B1 build had to sideload the .005 May build (Global). When they tried to sideload the .004 May build for T-Mobile, it failed.

Apparently the .004 May build is older than the mid-April .B1 build, so that's why.
[Google Pixel 7 Pro] Lughnasadh:
@badabing2003 tagging you so you are aware of this for Pixel Flasher users. See the post above (#3,839).
[Google Pixel 7 Pro] justDave:
Seriously? They can't make one build that works everywhere? So if I'm dual SIM with Verizon and T-Mobile, I flip a coin and then switch if I have problems.

(And if I have even more problems after switching, switch back?)

And maybe switch to global when I'm traveling?

Yes, I know the differences are probably small edge cases but you have to wonder how bad those edge cases must be if they're pushing this many variants.
[Google Pixel 7 Pro] badabing2003:
I think Google messed up.

Look at the version date.

OTA metadata: # android.ota.OtaPackageMetadata$OtaMetadata@b65952f6
...
postcondition {
build_incremental: "11583682"
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_name: "product"
version: "1710527182"
}
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "generic"
partition_name: "system"
version: "1710527182"
}
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_name: "system_dlkm"
version: "1710527182"
}
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_name: "system_ext"
version: "1710527182"
}
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_name: "vendor"
version: "1710527182"
}
partition_state {
build: "google/cheetah/cheetah:14/AP1A.240505.004/11583682:user/release-keys"
device: "cheetah"
partition_name: "vendor_dlkm"
version: "1710527182"
}
sdk_level: "34"
security_patch_level: "2024-05-05"
timestamp: 1710527182
}
...
[Google Pixel 7 Pro] roirraW "edor" ehT:
It should still work on any build almost anywhere. The Global one would likely work fine for you in all those cases, although only trying will tell.

The particular builds are just optimized towards particular carriers. It's possible the only difference is the radio.img, so you could just keep those handy if you wanted to.
[Google Pixel 7 Pro] justDave:
I get it, but... isn't that their job?
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you're not rooted, you would automatically receive the OTA likely based on whatever your primary SIM card is at the time. If you change which SIM card is your Primary, then eventually you'd likely get an OTA to the build optimized for that carrier.
[Google Pixel 7 Pro] mattburga1984:
Is it possible to go from February firmware back to November firmware?

I have an unlocked bootloader, I am rooted and I use Pixel Flasher to update.

If this isn't possible, does anyone know how I can hide three button navigation?

I'd like it active, but hidden, much like AOSP Mods did for me back in November. :/

Thanks.
[Google Pixel 7 Pro] badabing2003:
With wipe and without bootloader rollback protection in place, you can always downgrade using factory image.

I'm not aware of any bootloader rollback blocks between November and February.

If you do not want to wipe, there is an experimental downgrade path without requiring a patch, but it's experimental and the wider the gap between the releases, the higher the chances that even if you manage to downgrade, you might run into runtime issues.

You can read all about here.
[Google Pixel 7 Pro] schmeggy929:
Come again? Whose job to do what? Lol
[Google Pixel 7 Pro] mattburga1984:
Anyone have ONLY screen unlock haptics despite haptics being turned off?

This annoys me a great deal. I'm on the April firmware.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I just tested on the May firmware, and the very first time I unlocked the phone after a reboot, I didn't get any haptics, but after locking it, using the fingerprint to unlock again did cause a very small haptic feedback.

I don't use haptics for anything, otherwise.
[Google Pixel 7 Pro] weriwd:
Hi guys, will it cause any issues if I flash the latest May update over the December one?

Spoiler content hidden.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Short answer: no

Longer answer: I can't speak as to the specific issue you're having on the December firmware.

Even longer answer: Unless you happen to be extremely unlucky, as long as you follow the directions to update (Full OTA Zip method always recommended by me for the last year), you'll have zero issues. None of this is related to the six-month gap between updates, however. There's no increased chance of anything going wrong by waiting longer between updates.

Note that on Monday, the June firmware might come out (there are unannounced exceptions, so don't count 100% on it). Also, the June firmware should be Android 14 QPR3 Stable.

Make sure all your root-related apps are fully updated and any Magisk Modules are disabled in case you do have issues. There's advice for solving issues in one of the OPs of this thread, if you do enable your Magisk Modules and the phone won't finish booting.
[Google Pixel 7 Pro] weriwd:
Thank you for being helpful as always! I will wait for next week's monthly update, and hopefully, that will resolve the annoying call drops.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! I hope so, too, for your sake. Good luck!

Another note: Especially with QPR updates, such as June's should be, there is a greater chance that any app you've been using which requires root might not function correctly - similar to new major Android versions, so just be aware. Even Magisk itself sometimes needs updating or using its Beta, Canary, or Debug channel Magisk, but other users will report back what doesn't work within a few days after the firmware update, usually.
[Google Pixel 7 Pro] Lughnasadh:
What to expect with June's Feature Drop:

Android's latest feature drop makes your devices work better together

Google is rolling out 8 new exciting Android features to "elevate your everyday." Here's what they are.

www.androidfaithful.com
[Google Pixel 7 Pro] showstopper1:
Just bought a Japan variant gfe4j is the unlock bootloader steps and flashing custom roms are the same as global variant?
[Google Pixel 7 Pro] roirraW "edor" ehT:
The steps are the same, yes. Welcome to the Pixel 8 Pro!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #2 (quote from my Pixel 8 Pro thread):

Spectrum:
[Google Pixel 7 Pro] roirraW "edor" ehT:
June 2024 security bulletin is listed, but linked to the May 2024 one.

Here's the correct link:

Android Security Bulletin—June 2024 | Android Open Source Project

source.android.com

Edit: The main page:

Android Security Bulletins | Android Open Source Project

source.android.com

says June is still security patch level:

2024-05-01

2024-05-05

So obviously, they have some corrections to do on this page. :)
[Google Pixel 7 Pro] Lughnasadh:
Google can keep a phone if you send for repair with non-OEM parts (Update: Changing policy)

In its terms and conditions, Google said it could keep devices sent in for repair if they have a non-OEM part. This will be changed now.

www.androidauthority.com
[Google Pixel 7 Pro] Lughnasadh:
And in a turn around...

Google says it will not keep Pixel devices sent in for repair with 'unauthorized parts'

Google is updating its policy around Pixel repairs, no longer keeping devices that were sent in for repair with unauthorized aftermarket parts

9to5google.com
[Google Pixel 7 Pro] Ghisy:
Did someone at Google forget (again) to click the upload button for the June QPR update images/OTAs? 🤔
[Google Pixel 7 Pro] Sib64:
Well, we'll just have to wait and see, maybe tomorrow

;)

husky version is already available for download...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm not seeing the June firmware for Husky.
[Google Pixel 7 Pro] Sib64:
My bad, I got confused with the Beta version

Sorry :rolleyes:
[Google Pixel 7 Pro] roirraW "edor" ehT:
No sweat, just checking! I try to limit myself to getting confused about which firmware I'm talking about to twice a month.
[Google Pixel 7 Pro] hxxmor:
what is husky version

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
"Husky" is the codename for the Pixel 8 Pro, just as "Cheetah" is the Pixel 7 Pro.
[Google Pixel 7 Pro] hxxmor:
I'm not seeing the June firmware for panther

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
It hasn't come out for any device yet. It's common enough that QPR Stable releases come out on a different day than expected, although Google doesn't promise any day even for the normal monthly updates, but the first Monday of each month is so far still the most common day overall.

Could be today, could be next week, could even be longer. It's happened before.
[Google Pixel 7 Pro] Ghisy:
Basically, whenever Homer finds the upload button. 😜
[Google Pixel 7 Pro] hxxmor:
How do I update when I'm rooted, I was even looking forward to flash a custom kernel but I saw that the procedure to update is different than the click and wait method I had before root

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
The update instructions are in:

For over a year, now, I recommend the Full OTA Zip method (I do it twice to flash both slots).

Edit: Some or possibly most or all custom kernels require Verity and Verification to be disabled, and if you don't already have them disabled, then doing so will require you to wipe your phone after. I haven't played with custom kernels in almost a couple of years, so I can't advise further than that.
[Google Pixel 7 Pro] hxxmor:
What do you mean by flashing both slots

Oh and I forgot to add that the mot recent kernels can be flashed without the Verify and Verification disabled

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
The Full OTA Zip method instructions include how to do so - which is all you really need.

Here is more information than you likely want to know about the two slots:

A/B (seamless) system updates | Android Open Source Project

source.android.com

TL;DR / short or medium version - there are two system partitions. There are not two data partitions, so all system and user app data are shared between the two slots. If one system partition fails to boot enough times, the phone will attempt to boot the other slot.

If you've never taken or manually flashed an OTA since you received the phone, and you never manually changed slots and flashed it with the factory image, then I even more strongly recommend following the Full OTA Zip method.

It was found previously that Google doesn't always ship the Pixels with anything at all on the currently inactive slot - not even a bootloader, which is dangerous. We don't know if this is still the case, but it was within the last few years. If a phone tried to switch boot to a completely blank second slot, the phone would be hard bricked, and in the case of the Pixel, you'd have to RMA it because only Google could fix it.

Edit: I definitely abbreviated the explanation, so it's not 100% word accurate, but I don't want to overload you with information.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@hxxmor

It appears I skipped the most important part of flashing the Full OTA Zip. I'll have to put that in there. Thank you!

Download the usually most recent Full OTA Zip file (link is in the first post):

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

developers.google.com

In last month's case, there were four firmware versions all for May, but you most likely want this one on that page:

14.0.0 (AP1A.240505.005, May 2024)
[Google Pixel 7 Pro] hxxmor:
And after grabbing the full OTA zip file what should I do?

But before I wanted to ask more few questions:

•What does OTA mean?

•What is an image?

•What it means to flash something

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
You should follow the directions in the Full OTA Zip method section, as you were. In your case, continue with the now step 9 adb sideload cheetah-ota-AB#a.YYMMDD.##-blah.zip, but I may be making some further adjustments, so the step # might change, but the text of the step directions won't.

Over The Air update. Obviously, if you manually download it, it isn't actually over the air, but that's what it stands for.

An actual over the air update would be one you receive on your phone through Wi-Fi or mobile data. It used to be that OTAs only contained what was changed since the previous firmware (this is again a simplistic explanation, but basically true). You used to be able to manually download those smaller OTA zip files from Google as well, but at some point they started only offering the Full OTA Zip.

The "Full OTA Zip" is just as much "everything" as the factory image contains.

In the context of flashing, it's a single file that represents one partition on the phone. Like boot.img is the kernel, and is flashed to the boot partition.

In the contexxt of when someone refers to the factory image, they're talking about a zip file which contains all of the individual partition.img files within it.

The system partitions are normally read-only. Flashing something means writing the contents of a file to a partition, overwriting the partition's previous contents.

You can compare it to "burning" a CD / DVD / Blu-ray. There's a whole history of the terms used, but I won't go into that here. You can go down that rabbit hole if you choose to. :)

fastboot flash init_boot Magisk'd_init_boot.img

flashes the Magisk-rooted init_boot.img to the init_boot partition.

Thanks again for pointing out the obvious (to me) mistake I made, not linking to the Full OTA Zip page in the directions for flashing it. :D I sincerely appreciate it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
FYI, I'm done fiddling with the directions in Post #2 for the moment, so the step numbers should currently be safe (if you refresh the browser page again, first).

I really need to / want to split the directions for different processes out into their own posts for this Pixel 7 Pro thread, like I did in my Pixel 8 Pro thread.
[Google Pixel 7 Pro] hxxmor:
if i do this "adb sideload cheetah-ota-AB#a.YYMMDD.##-blah.zip", will it wipe data from my phone or it just overwrites files on my phone?
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you do that, but replacing cheetah-ota-AB#a.YYMMDD.##-blah.zip with the filename of the Full OTA Zip you downloaded, then you will be overwriting the contents of all the system partitions with those that are contained within that zip file.

cheetah-ota-AB#a.YYMMDD.##-blah.zip is just an example/template - change that to the correct filename, which will change slightly for every month's update.

Edit: OTAs

never

wipe user data.
[Google Pixel 7 Pro] hxxmor:
is panther-ap1a.240505.005-factory-06b4c466.zip good? System partitions doesn't mean like app data right? It just overwrites the system files right?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No! Don't use panther files. That's not the Pixel 7 Pro. Cheetah files are for the Pixel 7 Pro. Do you have the non-Pro Pixel 7 (which is indeed Panther), or the Pixel 7 Pro (Cheetah)? If you have the non-Pro Pixel 7, then yes, Panther files are what you need and that one is good. :)

Correct, system files don't include app data.
[Google Pixel 7 Pro] hxxmor:
I have a non-pro Pixel 7, i know that i'm dumb but not that dumb lol. I remember that when i texted from the ReLabs app it showed that i was writing from a non-pro Pixel 7
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hehehe, I just wanted to make sure in case it was an honest mistake. Whew! In that case, yes, panther-ap1a.240505.005-factory-06b4c466.zip is good.
[Google Pixel 7 Pro] hxxmor:
do i need to open the cmd in a file where i have all the required files like the Full OTA zip and the init_boot.img? i chose the platform tools folder bc idk i saw it somewhere that it was better to use that folder
[Google Pixel 7 Pro] roirraW "edor" ehT:
Personally, I keep everything in the same folder. The extracted platform-tools contents, the Full OTA Zip, the Magisk'd init_boot.img, then I open a command prompt in that folder.

Note that PowerShell acts differently than Command Prompt, so it's simpler just to go with the latter, although technically, PowerShell can be used as well, you would just have to type some additional characters before each line, but I don't specialize in using PowerShell, so I don't bother remembering the details.
[Google Pixel 7 Pro] hxxmor:
So i was using the cmd and i tried to type in fastboot devices to see actually if my device was connected but it didn't show me nothing, but when i typed in adb devices it showed my device
[Google Pixel 7 Pro] roirraW "edor" ehT:
Sideload mode is for ADB. Bootloader mode is for fastboot.
[Google Pixel 7 Pro] hxxmor:
what is bootloader mode

unknown partition 'init_boot Magisk'd_init_boot.imgmagisk_patched-27000_rpT6W.img'

fastboot: error: cannot determine image filename for 'init_boot Magisk'd_init_boot.imgmagisk_patched-27000_rpT6W.img'

it says this after i tried to flash the image

oh wait i'm dumb
[Google Pixel 7 Pro] roirraW "edor" ehT:
For now, my explanation is circular, as I don't have much time before I have to do some things - not on the computer, so I won't be available for quite a while after this.

Bootloader mode is the mode you can use fastboot in.

Sideload mode is the mode where you sideload the Full OTA Zip using ADB.
[Google Pixel 7 Pro] hxxmor:
Last thing that i'll appreciate if you do it for me it's to explain what does this mean (point 15 on the full OTA zip method)

NOTE that it it NOT necessary to tell the phone to change slots. Each time you flash the OTA, the phone changes slots already.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Every time you flash (sideload) the Full OTA Zip (or take an actual over the air update), it switches slots before it flashes it.
[Google Pixel 7 Pro] hxxmor:
I just completed flashing the OTA, now I'm going to flash the custom kernel, is it possible to flash it through pixel flasher? I heard it's a handy dumb-proof tool

Sent from Pixel 7 using ReLabs