yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! Nice.

LOL!!

Just for reference (but I recommend still sticking to @badabing2003's advice), on Windows, you:

Right-click the start button

Choose System from the pop-up menu

Over on the FAR right, choose "Advanced system settings". Instead of steps 1 & 2, you can also click (left) on the start button and start typing Advanced system settings, and eventually you'll see "View advanced system settings", and click on that.

Click on "Environment Variables" at the bottom on the default Advanced tab at the top.

Under the bottom "System variables" section, click "New".

For Variable name, put in:

ANDROID_PRODUCT_OUT

For Variable value, put in the full path to your platform-tools folder. For example:

S:\platform-tools\

I always run platform-tools while actually having a command line open in the platform-tools folder, and I haven't tested this version yet, so as was remarked previously, I don't know if that would necessarily prevent requiring these steps.
[Google Pixel 7 Pro] Lughnasadh:
I always open the command line directly from the Platform Tools folder as well. Because of this, I've never had to define/add a system/user environment variable. I haven't tested this version either but I don't see how anything would change if opening up the command line directly from the Platform Tools folder itself.
[Google Pixel 7 Pro] LLStarks:
Raised a bug.

Google Issue Tracker

issuetracker.google.com
[Google Pixel 7 Pro] LLStarks:
Also looks like the new version flashes everything as part of the Super partition.

A good deal faster tbh.
[Google Pixel 7 Pro] Lughnasadh:
Okay, I was wrong. Just tried to update my Pixel 6 Pro to A14 Beta 2.1 using Platform Tools 34.0.3. Opened up command line from the Platform Tools folder and ran flash-all.bat and got the ANDROID_PRODUCT_OUT error. Grrrr...

33.0.3 worked fine, btw.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, and +1'd it. Interesting about being noticeably faster.

Thanks for the report.

In other, albeit unimportant, news - on the following page:

Android Beta Program

Android Beta Program allows you to enroll your Android device for beta releases.

www.google.com

Aignes Website-Watcher has been noticing a fight for wording for the past week or so, such as in this one FAQ item:

Sometimes it says Android Devices, sometimes Android Phones, and sometimes, like in that example above, "Android Android Devices". It makes the same exact changes for that and another FAQ entry on that page. Occasionally, there's a 12 or 24-hour lull in changes, and then suddenly they change back and forth between the various available wording options multiple times in an hour or so.

I have to wonder what is going on behind the scenes when this happens. I'm sure two Google employees aren't actually trying to exert their preference over each other. Weird!
[Google Pixel 7 Pro] ScottHW:
I just got a factory unlocked Pixel 7 Pro. I unlocked the Bootloader, used Magisk to patch init_boot.img but had problems with flash-all.bat script.

Here is the output when it went off the rails

...
extracting product.img (2857 MB) to disk... took 12.380s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/12 (262112 KB) OKAY [ 6.721s]
Writing 'product_b' OKAY [ 0.402s]
Sending sparse 'product_b' 2/12 (262124 KB) OKAY [ 6.758s]
Writing 'product_b' OKAY [ 0.404s]
Sending sparse 'product_b' 3/12 (262128 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...

And now it's in a boot loop.

I am able to get back to Fastboot Mode (and to Recovery Mode)

1) Can anyone help me recover from this boot loop?

2) Anyone recognize what might have gone wrong?
[Google Pixel 7 Pro] roirraW "edor" ehT:
What version of Platform-Tools are you using? If on any 34.x version, then the easiest solution is to go back to v33.0.3:

Technically, 3

4

.0.3 also works (whereas 34.0.0 and 34.0.1 are very broken), but 34.0.3 may require you to jump through some hoops to work correctly, whereas 33.0.3 will just work as is.

Just be back in bootloader (fastboot) mode and start the flash-all.bat back from scratch.

Cheers and good luck! Let us know how things go.

Edit: Otherwise, if that doesn't solve it, then different USB cable and different USB port, or even rebooting the computer is worth trying.
[Google Pixel 7 Pro] badabing2003:
Yes you can get out of it, it failed in the middle of flashing, all you have to do is flash again to a successful end.

Why did it fail you might ask,

Make sure the downloaded firmware's checksum matches what is published.

It could be communication issue

Try another cable

Try another USB port, preferably USB2

Makes sure the drivers are up to date.
[Google Pixel 7 Pro] aer0zer0:
I ended up buying a faster cable. The c -> c cable provided by Google just stopped working for these newer 14 builds. I got a the USB 4 cable from Spigen, and these new images bats started flashing properly again.

That's my best guess.
[Google Pixel 7 Pro] ScottHW:
Yes, you're correct; I previously did have that problem, but have since corrected it. It was not the culprit here.

Since I could easily get into fastboot (bootloader), I was able to just try it again.

I did use a different cable (Anker this time, my "good")

It did work. For both slot-a, and then slot-b.

Whether the previous cable/usb port was to blame, I'll never know.

Thanks as always for your help, y'all!
[Google Pixel 7 Pro] ScottHW:
It's just incredible to me that

our phones shoot 10's of GBs of HDR+ 10-bit 4kp60 video

and still... a very common and accurate troubleshooting tip is

"try a different cord"
[Google Pixel 7 Pro] gpvecchi:
Were you using the black or the white Google cable?
[Google Pixel 7 Pro] aer0zer0:
The white c -> c that Google provided. Bought the black USB 4 c -> c from Spigen.
[Google Pixel 7 Pro] Displax:
Another issue with PT 24.x.x found by me... 🤦‍♂️

"fastboot cannot work when %username% in Windows OS contains non latin characters"

Already created issue: https://issuetracker.google.com/issues/284450364

But do not be surprised at such a large number of errors, since Google massively rewrites fastboot
[Google Pixel 7 Pro] Displax:
And another one... :ROFLMAO:

Google Issue Tracker

issuetracker.google.com

fastboot failed to format partitions or running "fastboot -w" on some devices
[Google Pixel 7 Pro] Displax:
Love to reporting fastboot issues...😆
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for sharing! That issue tracker page https://issuetracker.google.com/issues/284450364 shows up blank (but perpetually "loading", while saying "Access denied" at the bottom. Your other link for the other issue works for me fine, and I've +1'd it.
[Google Pixel 7 Pro] Displax:
Looks like broken link. Fixed.
[Google Pixel 7 Pro] roirraW "edor" ehT:
For what it's worth, the first link https://issuetracker.google.com/issues/284450364 still doesn't work, even if I try it through a VPN without a Google account. Still says "Access denied". 🤷‍♂️

Second link https://issuetracker.google.com/issues/284335462 works fine.
[Google Pixel 7 Pro] Displax:
Strange things... Now even i can't access my own issue. Maybe time to report issue about Google issue tracker 😆
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1662323594427531265
[Google Pixel 7 Pro] namitutonka:
I think it is scandalous for Google not to incorporate open source TWRP in their stock OS. I believe TWRP is the #1 reason for users wanting to root their devices.
[Google Pixel 7 Pro] Displax:
A new try: https://issuetracker.google.com/issues/284616650
[Google Pixel 7 Pro] xunholyx:
That link worked
[Google Pixel 7 Pro] xunholyx:
You are literally the first person ever in my memory that I've come across that has said TWRP is the main reason they want to root.
[Google Pixel 7 Pro] wangdaning:
You don't need root to have twrp.
[Google Pixel 7 Pro] xunholyx:
Yep, just an unlocked bootloader.
[Google Pixel 7 Pro] namitutonka:
Didn't know that. Thanks. Going to request an unlock from Cingular.
[Google Pixel 7 Pro] xunholyx:
Keep in mind that there is no TWRP for the Pixel 7 series. There hasn't been one for a couple of Android OS versions now, well before the 7/Pro came out
[Google Pixel 7 Pro] Displax:
Fixed in upstream.

https://android-review.googlesource.com/c/platform/system/core/+/2609188

https://android-review.googlesource.com/c/platform/system/core/+/2606013
[Google Pixel 7 Pro] Ghisy:
What? Someone at Google is ACTUALLY paying attention? *shocked *

Good news though! 👍
[Google Pixel 7 Pro] JakeDHS07:
How long until a fixed build actually gets published tho is the question
[Google Pixel 7 Pro] Displax:
Pending to merge: https://android-review.googlesource.com/c/platform/system/core/+/2613189
[Google Pixel 7 Pro] roirraW "edor" ehT:
No update yet, but at least:

Android Security Bulletin—June 2023 | Android Open Source Project

source.android.com

Edit: And looks like two different security patch levels, unless a typo:
[Google Pixel 7 Pro] TotallyAnxious:
This article talks about the differences between the two. https://www.xda-developers.com/how-android-security-patch-updates-work/
[Google Pixel 7 Pro] Ghisy:
So I guess the feature drop is postponed to next Monday at least?
[Google Pixel 7 Pro] wangdaning:
Something must have been really broke for them to not push.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Just a guess of mine, but I think maybe they thought it was more important for them to get the new Android 14 Beta 3 out as soon as possible, to give them as much time as they could to debug it the rest of the way. Who knows, though.
[Google Pixel 7 Pro] wangdaning:
I think so, too. That means it is really broke though. Maybe we are just crazy people
[Google Pixel 7 Pro] Jawzper:
I am trying to update my Pixel 7. I have already unlocked the bootloader and rooted previously, now trying to update I have gotten as far as copying the new init_boot file onto my phone but have hit a wall.

Magisk does not give an option to install, it only gives an option to update, or to install the app. So I cannot "select and patch a file". How can I patch?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Can you share a screenshot?

These are what I see:

Spoiler content hidden.

Did you hide Magisk previously, and now you might have a still hidden Magisk and a second Magisk that you installed?
[Google Pixel 7 Pro] Filsafat00:
Please help me if there is a notice of unlock bootloader oem pixel 3a verizon, I hope there is a teacher who gives a complete explanation and tutorial. thank you.
[Google Pixel 7 Pro] Homeboy76:
AFAIK, Verizon phones are bootloader locked. No one has developed a (safe) way to unlock the bootloader yet.
[Google Pixel 7 Pro] Jawzper:
Thanks for the reply. This is what I see...

Having said that, I tried pressing update again and now it works and shows the "select and patch a file" screen. I don't know what has changed since my last post but I think I'm good now? o_O
[Google Pixel 7 Pro] roirraW "edor" ehT:
Glad it's worked out. Since that screenshot is from the latest Stable release of Magisk (v26.1), but it wanted you to update the app, I would suspect that you have it set to look for Beta or Canary versions, and to prompt for updates to them.

Unless you discover a particular need to be on a Beta or Canary version, I would suggest you go into Magisk's settings, and change it back to look only for new Stable releases - but on the other hand, if everything is working fine now, maybe it's best to leave it alone. 🤷‍♂️
[Google Pixel 7 Pro] Jawzper:
That might be the case actually, I did notice I was on canary build earlier and switched to standard. So maybe that was the reason. Anyway, I've successfully updated. Thanks!
[Google Pixel 7 Pro] Ghisy:
Hey Google, ya know we're supposed to get a feature drop this month? Right? Right? 😅
[Google Pixel 7 Pro] Schroeder09:
Yeah. Crap hardware. Now the fast updates thing doesn't happen anymore. Why are we buying these again? Is the only reason the cameras now? Seems like it.
[Google Pixel 7 Pro] Ghisy:
The hardware is fine. Sure, I wish Tensor G2 ran cooler and the battery was better but these are more first world problems. They're not a deal breaker for me.

I like being able to root my phone rather easily and do whatever I want with it. It's not the case with Samsung for example. YMMV.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Very soon?
[Google Pixel 7 Pro] Lughnasadh:
Seems like it...

Of course yesterday the official Made By Google Twitter account said that it was rolling out yesterday and gave a link to a Google Blog that was dated 2 years ago 🤣

https://twitter.com/i/web/status/1668664796118495237
[Google Pixel 7 Pro] Lughnasadh:
Hands-free photos, SpO2 and more for the Pixel family

The June Feature Drop for Pixel phone, Pixel Watch and Fitbit is here.

blog.google
[Google Pixel 7 Pro] roirraW "edor" ehT:
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

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] Ghisy:
Who's gonna be a Guinea pig and flash this with the 33.0.3 version of the platform tools? 🤔
[Google Pixel 7 Pro] UberNorse:
Just updated and everything is fine.
[Google Pixel 7 Pro] kornball:
Are you using Magisk 26.1? That looks to be the most recent stable release (I'm still on March 2023 factory image and Magisk 25.2). Thanks!
[Google Pixel 7 Pro] UberNorse:
Yes, magisk 26.1 and platform tools 33.0.3.
[Google Pixel 7 Pro] WingedCow:
Anyone got the new wallpaper AI and emoji working? Mine seems to be missing those options lol. On both my Pixel 6 Pro and 7 Pro.

Video Macro mode is a no go too.

Update: So I checked, the apps are there, Cinematic Wallpaper and Emoji Wallpaper.

Stuffed I tried: Clearing storage and cache on all the wallpaper apps and reflashing update. When SETTING a wallpaper, the cinematic option pops up during midway of the setting process, but then disappears.
[Google Pixel 7 Pro] schmeggy929:
Same here 26.1 Magisk Stable and 33.0.3 Platform-tools using PixelFlasher. All went well. I did have to re-add the internet tile to my Quick Settings. Now when you click on it both cellular and Wifi come up as toggles
[Google Pixel 7 Pro] amders:
damn.. gonna ask the same question.. haha
[Google Pixel 7 Pro] synesthete:
😂 I flashed it with 33.0.3 while on a work meeting and had no problems.

I got emoji wallpaper working, but cinematic wallpaper isn't working for me. Maybe it needs a clean flash.
[Google Pixel 7 Pro] Namelesswonder:
This has been my experience on and off with Pay since 2016, either being able to make payments because it's cached tokens and nonces, make payments even though my device fails and shouldn't even have them (that was back in the day), or not being able to make a payment even though the device passes.

The best check I have is the aforementioned clearing data, rebooting, checking the Pay security requirements, tapping on a card and waiting about 5 seconds for the tap-to-pay icon to appear, and if it doesn't animate with a cross-out then everything is good.

Networks have no control over the carrier or bootloader unlocking of unlocked devices, as when the phone contacts Google to request to unlock the bootloader it only does so based on IMEI/serial/whatever is unique to the device. Carriers only matter because the ones that are connected to Google's backend (T-Mobile and AT&T) are able to clear authorization to allow bootloader unlocking on their carrier models. Although supposedly they might not perform both a network unlock and bootloader unlock at the same time, so mileage may vary.

That is tied directly into Play Integrity however it doesn't check for StrongBox, so it's still doing the "old SafetyNet check" that doesn't care about hardware backed security modules but does care about CTS profile and bootloader unlock. It's also the slowest to update to any situation as I think the status is cached for something like up to 3 days.

You shouldn't need to care, they would release the new platform-tools well before launch.

The new partition is already supported right now by the latest platform-tools release.

fastboot/fastboot.cpp - platform/system/core - Git at Google

In fact this was the specific commit over 10 months ago that added it.

dd1eb8733dbae94958a9327e9247d9400815a5ba - platform/system/core - Git at Google

I'll have to dig up a shell script from 6 years ago that I used to output the architecture that all apps on the phone are built for.
[Google Pixel 7 Pro] 96carboard:
If they're java/kotlin then this DOES NOT APPLY. They're fully compatible.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That would be interesting. Thanks!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I think they're saying the wouldn't know if they were.
[Google Pixel 7 Pro] Ghisy:
If you do find it, could you share it here please?
[Google Pixel 7 Pro] Annie the Eagle:
So my phone is bootloader unlocked, but *not rooted*, but I still get "Play Protect Certification" as "Not Certified". Does this mean something is wrong? Or is it just because of unlocked bootloader and nothing to worry about
[Google Pixel 7 Pro] ScottIsMyName:
It's because of your unlocked bootloader. You will not be able to use Google Pay, or install certain apps in the play store (i believe Netflix is one example)
[Google Pixel 7 Pro] Annie the Eagle:
Ah okay, and once SafetyNet fixes work on this device (seems right now they don't), then I should be able to get back to certified + GPay working?
[Google Pixel 7 Pro] DiGiTaT:
Firmeware is out: https://developers.google.com/android/images
[Google Pixel 7 Pro] Gordietm:
The factory images were just posted for the 7 and 7 pro.

There are two links for October, assuming,

TD1A.220804.031, Oct 2022 is the latest.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Figures, I got busy at work. :)

Version	Flash	Download	SHA-256 Checksum
13.0.0 (TD1A.220804.009.A2, Oct 2022)	Flash	Link	8e7393e1bd7f86d76d75cdea988d5e4ebfded3a50fac26d774b9eb07152c1ed5
13.0.0 (TD1A.220804.009.A5, Oct 2022, JP carriers)	Flash	Link	c68659bdd1d2b0b9a1740daa1502acbbf1b535be5b7e5bada157c82ef5fbf5c5
13.0.0 (TD1A.220804.031, Oct 2022)	Flash	Link	6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f
[Google Pixel 7 Pro] Ghisy:
Factory images for Cheetah (P7P): https://developers.google.com/android/images#cheetah

I guess 031 is the most recent one.
[Google Pixel 7 Pro] bosox284:
TD1A.220804.009.A2 was the build my phone had stock out of the box and I'm running the update now. I'll edit this post once the update completes with the build. I'm assuming .031 is the latest as well.

Edit: TD1A.220804.031 is the new build number now that I've completed the update.
[Google Pixel 7 Pro] Gordietm:
.031 is apparently for the US unlocked version according to Droid Life.
[Google Pixel 7 Pro] hendusoone:
I just finished running the update. I'm on .031 now. US Unlocked.
[Google Pixel 7 Pro] bosox284:
That's what I have and I can confirm that .031 is the post-update build.
[Google Pixel 7 Pro] Gordietm:
My 7 pro is only arriving later this afternoon, so Im looking forward to hear from others that have now rooted. 🙂
[Google Pixel 7 Pro] rhodry999:
I'm from Europe and have the same built as US. I guess there is no difference.
[Google Pixel 7 Pro] ScottIsMyName:
I'll be holding out on setting the phone up until SafetyNet passes!
[Google Pixel 7 Pro] Lughnasadh:
It's not 33.0.3 you have to worry about. It's 34+ where we need Guinea Pigs, but that still has a couple of bugs.
[Google Pixel 7 Pro] amders:
root? magisk version? really hate when there is an update
[Google Pixel 7 Pro] roirraW "edor" ehT:
Magisk Stable 26.1 is still working perfectly for me. I updated about 15 hours ago.
[Google Pixel 7 Pro] synesthete:
As

Root with Magisk 26.1
[Google Pixel 7 Pro] Ghisy:
I updated to the June feature drop a few hours ago but several things are missing like the cinematic wallpaper or the adaptive alert vibration.

Are these rolling out as a server-side update? It's odd, I thought they were included in the June update itself.
[Google Pixel 7 Pro] Lughnasadh:
You need some app updates and/or some server side updates, depending on the feature.
[Google Pixel 7 Pro] Ghisy:
All my Google apps are up-to-date... I guess I'll just see in a few days. 🤷‍♂️
[Google Pixel 7 Pro] Lughnasadh:
But are the ones you need to update updated? For instance, did you get Google Camera 8.9 yet? Did you get the Emoji Workshop Wallpaper app yet?
[Google Pixel 7 Pro] Ghisy:
I just installed Google Camera 8.9 manually from apkmirror. No Emoji Workshop Wallpaper yet. Oh well.
[Google Pixel 7 Pro] Lughnasadh:
I think you need Google Camera 8.9 for the self-timed photos when raising palm and for Macro Focus on videos. Are those two things working for you now?

You should get the Emoji Workshop Wallpaper app soon.
[Google Pixel 7 Pro] Ghisy:
@Lughnasadh, yeah, I got the self-timed photos in the camera app now.

I checked apkmirror for Google apps updates and there's been a ton of them since yesterday. Some of these are probably still rolling out.
[Google Pixel 7 Pro] Sasaiber:
UU I have everything but a new smart home panel and cinematic wallpaper...
[Google Pixel 7 Pro] amders:
camera 8.9 work well? i tried install 8.9 downloaded from apkmirror, but its always crash.. dont know what happen

edited... after i tried the apk bundle version, now it can work normally

for anyone whose already on june update, but no emoji wallpaper, maybe you can clear data dan cache the wallpaper apps.. but before that install the emoji workshop apps first..
[Google Pixel 7 Pro] weriwd:
Just a quick question, as I'm still using the December update, I'm wondering if I should update. How do you all find the battery performance so far is it getting any better recently?
[Google Pixel 7 Pro] reaper000:
For the sake of rooting convenience, here's the flashable Magisk 26.1-rooted init_boot.img for the monthly June release.

If you don't already know what to do with this file, I suggest you ignore this post, or read the pinned posts at the beginning of this thread on how to obtain root.

Good luck!
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
In other news, I am really frustrated at the cat and mouse play going on with Google monthly updates and USB DAC playback with UAPP. Everyother month, USB DAC playback with UAPP gets fixed only to break the next month. April and May was awesome with USB DAC playing great through UAPP dedicated mode even when screen is off (previous months of Feb and March saw it work by changing the default USB mode to No Data transfer). This month, crap has landed again, one can play through a USB DAC using Qobuz but the max it will play is 24 bit 96 kHz (i know that cos I use a Chord Mojo which has light indicators to show the bit rate and frequency). Moment you switch to UAPP, dedicated mode (theres a pop up which allows you to do that once you accept it), within 15 seconds from screen off, music stops while the DAC tries to reconnect through that pop up. Every month its a mystery for me, "what gonna happen this month". Sorry for the rant, feels like every month some one from Google forgets to update the USB hand off code or something. I have emailed UAPP support at length and they ask me to email google. I am not sure what to tell Google, since they know what fixes it for sure (else how does it get fixed).

I can imagine some people reading this post go "Aww muffin, can you really hear the difference!!". I almost am saying that to myself while am typing this post. Meh! for what its worth, hope they fix it the next month.
[Google Pixel 7 Pro] synesthete:
When I opened up the google camera a few minutes ago, I got a little in-app message saying there was an update available. I tapped it to install and now I have access to the macro video feature.

I am also now able to use the cinematic wallpaper now. Before I was trying to use it through longpressing the desktop, but I got it working by ggoing to Settings > Wallpaper & Style > Chnge Wapaper > My Photos > Select your photo you want > tap the little magic stars icon. It isn't very obvious hiding behind all of those menus.