yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] HipKat:
Dude, "a lot of information" is understating it lol

It reminds me of the Evo 4G Guide I wrote - highly detailed, step-by-step walkthroughj
[Google Pixel 7 Pro] EtherealRemnant:
Slots primarily serve two functions:

1) Allow the system to be updated in the background

2) Provide a small safety net if the phone boot loops after an update as after so many fails it will switch slots
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL!

Good summary!
[Google Pixel 7 Pro] mad4some:
Ok back to trying to unlock bootloader.....and still at a dead end trying to install google driver. Main problem being that manual driver update ("Have Disc") method always fails with a popup that says: "the file you have selected does not contain a compatible driver for your device blah, blah, blah" :rolleyes: That is the same whether I point it at the extracted "usb_driver_r13-windows" folder or at "usb_driver_r13-windows\usb_driver" or right to the "android_winusb.inf" folder containing the driver. I have downloaded the driver folder more than once, have tried on my main PC (windows 11) and my laptop (windows 10) same results. If I put the device in fastboot (adb reboot bootloader), then it no longer shows up in Device Manager under devices, but I see the "Android Bootloader Interface" under LeMobile Android Device and if I try to update the driver there, I get the same "no driver found...." popup. Damn, where did the easy days go!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I hope you understand that due to us helping so many people recently, I don't remember if we were already through this part:

Not just uninstall the old drivers, but delete them. I don't want to mention anything else yet since I want to get that cleared up first. I remember someone couldn't find the option to delete the driver, but can't recall if that was you. Was it? :)

Edit: And you might have to delete the driver with both Android running, and then also in the bootloader (fastboot mode), separately.
[Google Pixel 7 Pro] mad4some:
Yes that was me, sorry. I only get the option in the dialog box to "uninstall device", there is no delete driver option box and clicking uninstall device doesn't generate a driver delete option either. Under properties > driver > details, I was able to see the complete path to the different current drivers and deleted them manually and that created yellow flags at "Pixel 7 Pro" in Device Manager but when trying to update manually (Have Disc) it still fails with popup per my first post.....
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for confirming! And the install driver dialog options that you choose are:

Browse my computer for drivers

then copy and paste the path to the extracted latest official Google drivers

and have the "Include subfolders' checkbox checked

?

And if so and that doesn't help, you also tried:

Browse my computer for drivers

Let me pick from a list of available drivers on my computer

Click "Have Disk"

then copy and paste the path to the extracted latest official Google drivers, and click "OK"

From there, you may have to play around with the "Show compatible hardware" checkbox - which I believe is by default, checked.

?

Besides all this, do you happen to have another computer you could attempt to do this on? Is this on Windows 10? How old is the computer and how long has the version of Windows that's running on it been installed (if different from how old the computer is)?

Try different USB ports, especially USB 2.0 ports if they are available.

Try different USB cables, including the USB 2.0 USB-C cable that comes with the phone.

Edit: Try rebooting after having deleted those Windows-supplied driver files.
[Google Pixel 7 Pro] mad4some:
@roirraW edor ehT , So I just successfully unlocked using Pixel Flasher even though it had a warning about not having correct drivers will cause it to fail.....go figure! Anyway, thanks for the help......on to root!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Glad you got that part solved.

The online Official Android Flash Tool also has the capability to unlock the bootloader as long as OEM Unlocking is enabled. I wonder if it, too, would have both acknowledged and ignored the driver situation.

I'm on the verge of suggesting that, just like another user has too do very recently, you should reinstall Windows.
[Google Pixel 7 Pro] bleez99:
I'm inclined to sneak in something that may be considered off topic.

"I don't use Windows, and neither should you"

-- Jamie Zawinsky

You can look up this man's impressive credentials.

If you do see me posting a screenshot from a Windows system, it means I'm at work and I have to make a living.

From day one, I've used FreeBSD, Mac, or Linux for flashing and never once did I have an issue with USB.

Sorry, back on topic.
[Google Pixel 7 Pro] mad4some:
@roirraW edor ehT, One more thing please, I have patched the init_boot.img with Magisk and have it back on my PC. To root I just put it in the "Platform Tools" folder and run "fastboot flash init_boot magisk_patched-25200_1a2B3c.img" (using the name of mine instead) and then reboot, is that correct?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No problem! I recognize that not everyone uses Windows. If GPSoftware's Directory Opus, which version 1 of came out over 30 years ago, was made available for Linux, I would consider a more serious attempt to use a version of Linux. Same with some other software, without having you depend on emulation.

I also love the speed of Window's Hyper-V for virtual PCs for things I like to keep sandboxed in their own Windows 10 installations.

I also don't want to dual boot on a regular basis.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Correct.

Edit: Well, after you have the phone in bootloader (fastboot mode) with adb reboot bootloader, of course.
[Google Pixel 7 Pro] bleez99:
I keep a dual boot for those providers that refuse to port their stuff over to other OSs.

I basically dropped from the Windows scene for personal use after Windows 3.1 was released.

To give some more background, I've been programming professionally since the late 80s.

I'm old and tired and didn't really gain much interest in mobile stuff but I do keep Android Studio installed to satisfy my curiosity and to keep the SDKs and Platform Tools up to date with little effort.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Ironically, I was very anti-Microsoft until my Commodore Amigas just couldn't go anymore. Hence my love of Directory Opus, which v1 through v5.8 of was made for the Amiga, then v6 through now v12 is for Windows starting in about 2001 or 2002.

And I'm not a great defender of Microsoft still - all software has its pros and cons.

I possibly should've gotten professionally involved in programming. I only pursued it very casually and didn't put any further effort into it after about 1993 or so.

Edit: Oh, I have some software running 24/7, so that's one of the reasons I don't want to dual boot normally.
[Google Pixel 7 Pro] Ghisy:
Does anyone know if it's possible to theme the recent apps screen? I'd like to have the background transparent instead of a solid color which, honestly, doesn't look that good.
[Google Pixel 7 Pro] simplepinoi177:
I don't know if this app will modify the recent apps screen -- I tried researching it myself but the descriptions and screenshots on it is limited -- but this app seems to have a good chance of working (it's all about theming "transparent"ly); although it might theme the whole phone on top of things so I don't know if this will be good for you. But you should check out the post below pointing to the app...

*Of course requires root; that's why this post belongs to this thread vs. me just pm-ing it to you...

https://xdaforums.com/t/post-of-root-mods-that-are-working-in-android-13.4509383/post-87682129
[Google Pixel 7 Pro] Dewaynelives:
Will i be able to install modded apks after root
[Google Pixel 7 Pro] capntrips:
You don't strictly need root to install modded APKs. There are some scenarios where it's nice (YT mods, for example).
[Google Pixel 7 Pro] Dewaynelives:
I cant use my download version of Spotify or beetv so on. None works i download
[Google Pixel 7 Pro] capntrips:
This is a bit off topic for this thread, and you might want to watch for rule 6 before you post a new thread about it.
[Google Pixel 7 Pro] Dewaynelives:
Yeah bud i looked at all the threads same thing its got to be 64bit or wont work.. Thats not what i was asking mainly. I thought i was on the kernal thread.

Also wanted to update that the reason for spotify mod isnt warez but gives more options such as rotation and artwork saves... not a warez for it doesnt make it free... i havnt been on here in a while but ive been a member since 2012 im guessing you cant even mention a modified apk even if it doesnt make iot "Free" but adds functionability... sorry either way tho just got mixed up.
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you can't install it while not rooted, you won't be able to install it while rooted. I haven't seen any mod available yet to re-enable the ability to install 32-bit APKs yet. The developer of the modded APK needs to update their mod to be 64-bit.
[Google Pixel 7 Pro] roirraW "edor" ehT:
‘Google Wi-Fi Provisioner’ update rolling out via Play Store with new explanation of app

Google this morning rolled out an update to the “Google Wi-Fi Provisioner” app and made it available via the Play Store in the process...

9to5google.com
[Google Pixel 7 Pro] wr3cckl3ss1:
@roirraW "edor" ehT any of this ring a bell? I'm still on the hunt for VZW....
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hmmmm, interesting, but no, not familiar to me except you might have mentioned some aspects of this previously, but not both those images that I recall.
[Google Pixel 7 Pro] wr3cckl3ss1:
So the issue here for VZW Pixel 7 Pro owners....is getting that toggle to come to life (error of "connect to internet")....even after carrier unlocking....the framework has a lot of good info. As I just discovered and screenshot the pics up above. I insanely cut them down to prevent any curious lookers and well, it would be nice to claim that trophy as mine. Lol. But aside from that. Having to dig thru apks and jars...is a headache. But luckily....I was on day two of my expedition. So this is where I stop and let's say "call" those services.
[Google Pixel 7 Pro] wr3cckl3ss1:
And btw....AT is dead on it. No matter what I did....not a single thing would connect to serial port. But maybe you might have an idea?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You have a lot more patience than me. I've only done relatively minor following "by-the-book" instructions for doing anything with APKs years ago, such as implementing the 3MinitBatteryMod in stock ROMs on 2-3 old phones.

Good luck again, I hope your calls don't reach 911! :D
[Google Pixel 7 Pro] djcsurf:
I've ran into a little problem trying to root. I patched the IMG file but when I try to transfer (copy over) the patched boot IMG to my laptop (Win 11) I get an access denied error.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Try unplugging the phone, and plugging it back in. You're choosing MTP on the phone, correct? Try rebooting the phone and the computer. Any access denied error you get on your computer is definitely a Windows problem.

Where did you extract your platform-tools to? If you extracted it to a protected place such as in C:\Program Files, then you can't copy directly from an MTP access to a protected location in Windows. Copy it temporarily to elsewhere on Windows like your Desktop, then move it to the protected folder. It'll give you an Admin access prompt if you're moving files into a protected location.
[Google Pixel 7 Pro] djcsurf:
Life saver, I was trying to copy to C:\ so just copied to desktop then moved it. Thank you. It's been years since I've done this. Last root was my old Nexus 6. I was just gonna use ADB pull when the phone pinged with your response.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome, glad that was the solution for you. :)
[Google Pixel 7 Pro] wr3cckl3ss1:
Well looks like I'm going to have to expose my secrets here in hopes of bringing some light to the VZW Pixel situation. But also at the same time. I will sort of disclose some new info. But first I can start here. For anyone that's familiar with isemtelephony... oemrilhook... transactions and functions....this was used and put a stop on in Android 10 by Samsung. Now you're probably wondering why I would be talking about Samsung when this is a Pixel thread. Well before Samsung put a stop to it, using certain functions and transactions....was a way to "bypass" security which in turn...meant you could sim unlock and sort of get that OEM toggle to come on and ultimately get BL unlock. That was killed by Samsung on Android 10. Here we are Android 13...fresh new VZW Pixel 7 Pro.....got thru one loop with the "carrier unlock" out of the picture....now I get "connect to internet"...the phone is on and running with plenty of data and wifi. Plenty of factory resets...even half attempts at hard bricks....could not bring that toggle to life. I dig around and come to find something that I thought wasn't right. "com.samsung.slsi.telephony.oemril" it's an APK installed on the Pixel 7 Pro. Cracking open the APK gives me certain transactions and functions. To my surprise and plenty of help from my friend....it carries the same transactions and functions from before...maybe a little updated...that was in place before Samsung cut it off. Now I've been told and I, myself have proven that just because a company gets rid of it one year... doesn't mean it won't show up a few years later down the line and more importantly on another phone, like the Pixel 7 Pro. It's all speculation at this point but if there's a way to analyze the whole APK and gather all of its functions and transactions....I think there may be a shot at bringing that toggle to life....there's a specific "service" that I won't mention here yet, that carries several specific key words.....

TRANSACTION_getOemUnlockEnabled

TRANSACTION_setDemUnlockEnabled

TRANSACTION_isDeviceOemUnlocked

TRANSACTION_isOemUnlockAllowed

TRANSACTION_isOemUnlockAllowedByCarrier

TRANSACTION_isOemUnlockAllowedByUser

TRANSACTION_setOemUnlockAllowedByCarrier

TRANSACTION_setOemUnlockAllowedByUser

I'm only a one man band with a life...family and job...I kind of dove into a brick wall here with VZW but if there's one thing..I don't do is give up without a clean fight. And with that said...if this goes somewhere and makes it to where a bypass is achieved....looks like Samsung is once again exposed. As that APK from the Pixel 7 Pro....I extracted...and got it installed on my S22 Ultra S908U.....and everyone knows US Samsung devices are Kings of no BL unlock. So....if anyone can help the good cause here. Shoot me a DM and let's get to work. Lol
[Google Pixel 7 Pro] roirraW "edor" ehT:
@wr3cckl3ss1 Intriguing and very cool. I do have sympathy with the plight of users on Verizon devices because I started out on them, and the HTC 10 and Pixel 1 were my first experiences with being allowed to unlock the bootloader.

I hope some developers notice and respond.
[Google Pixel 7 Pro] wr3cckl3ss1:
It's

It's truly been a roller coaster. I stepped away from Samsung for years. Rode the Nexus and Pixel train but Samsung surprised me with the quality this year and since pixel 4xl...I feel like the scale is tipping a bit. Don't wanna bash Google but if I can call a phone an embarrassment it would be the Pixel 6 and 6 Pro. I was just overall disappointed. So believe me...at first chance...I hopped on the Pixel 7 Pro bandwagon and waves of people did as well. This 7 Pro is definitely back on track...battery for me....absolutely kills it over s22 ultra. But currently after two days of hard testing....I glitched my battery icon and my time seems to jump or stay in place. See pic attached.

Actual time is 7:03....not 6:43 (currently stuck)...battery is at 0%.....but it's actually 83%...... i got one more good round of hard testing today before I go to wipe her clean and start new. I hope more people become interested. The two guys I hack/"tinker" with are pretty good. One has worked on DirtyPipe (issue s22) and the other was the one who discovered the breach that's affecting S22 Ultra....but as well as other Samsung devices new and past.... it's even still valid and on official Android 13 One UI 5....but besides all that...I'll focus my next few days efforts on Pixel 7 Pro....
[Google Pixel 7 Pro] Ghisy:
November update is live!

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

developers.google.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Monday, November 7, 2022

: Pixel 7 Pro Factory Images available:

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

developers.google.com

13.0.0 (TD1A.221105.001, Nov 2022)	Flash	Link	f2793a62a48bc840b892e74dd515739b657d2727c25edd074064e3ab019e73bf
13.0.0 (TD1A.221105.003, Nov 2022, Verizon, Verizon MVNOs)	Flash	Link	021be73c7c602de0fdefcd3a4c43d0d745188b7847880a0d4a2ccb6aa64c47a6
[Google Pixel 7 Pro] Annie the Eagle:
Of course you'll pass SafetyNet on an unmodified device 😂
[Google Pixel 7 Pro] Larakali:
It was more of a ,,Proof,, i have it ^^

Im working on it tho. give me an hour or smth this update is taking ages.

EDIT:

No firmware yet i keep monitoring tho
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome. Start following the steps in Post #2 - Unlocking Bootloader / Rooting / Updating | Passing SafetyNet - Device Integrity and Basic Integrity | ADB/Fastboot & Windows USB Drivers. You can at least get the bootloader unlocked, and might as well do that first thing since that forces a factory reset.

At least, I'm assuming you're asking what can be done while we're waiting for the factory images to post. Should be tomorrow - normally it's the day of the official release. I don't remember, but I would guess that they might not appear until after 12 or 1 PM ET, as the monthly updates do.

It'll be a toss-up as to whether I'll have received my P7P before the firmware images are available.

When they do I'll also post about it here and change the thread title to reflect the news.
[Google Pixel 7 Pro] Larakali:
I can monitor traffic. it is not shipped with latest update. Im working on it to get the url of the download of the image
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good luck! I hope you share if you find it. :)
[Google Pixel 7 Pro] Larakali:
If i can find a way to wireshark my android traffic to my pc then sure :D

No WiFi Gang....
[Google Pixel 7 Pro] Annie the Eagle:
Were you able to unlock the bootloader just fine using the usual fastboot commands
[Google Pixel 7 Pro] Larakali:
yes
[Google Pixel 7 Pro] mariusnoor:
Got as far as fetching the host, but I am unable to sniff the OTA package, since the download client won't accept a modified TLS certificate.

However, the host is as following: https://ota.googlezip.net/
[Google Pixel 7 Pro] mariusnoor:
Got the URL:

Pixel 7 Pro (Europe)

https://ota.googlezip.net/packages/ota-api/package/674427f7501c86422e9b502666af8a47cbd3cff7.zip

Edit: If you want to sniff it yourself, reset your phone completely, start it, enable USB debugging, log everything using logcat and then you'll find the URL.

here we go ;)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome, thank you! I quoted your post in the OP.

Edit: I have the SHA-256 hash of the 674427f7501c86422e9b502666af8a47cbd3cff7.zip as:

280187417316DAEDD18D69027EC101DF6916030A0BB4BF1C2AFCB033257AD9AB

(for double-checking the OTA zip is intact)
[Google Pixel 7 Pro] wildlime:
Is this the 0 day update? Can I apply it to my pixel 7 pro?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, and yes, you should be able to. If your Pixel 7 Pro is somehow already on the latest update, then the OTA should just fail, but there's no harm.
[Google Pixel 7 Pro] Larakali:
https://dl.google.com/dl/android/aosp/cheetah-tp1a.220804.009-factory-*sha*

Should be the full one when it release am i right? *note this is the august one its yet downloading this update for me... its so slow.*

If someone has this already can you try to add the string found in Build Number into https://dl.google.com/dl/android/aosp/cheetah- with the sha above just as try.

or is there perhaps a dumper that can use OTA Updates. bc mine *payload-dumper-go* cant.
[Google Pixel 7 Pro] Annie the Eagle:
Have you been able to root?

I'm guessing once people get the latest boot.img's from the OTA (I guess that's what the ZIP is?) then is it just as simple as installing latest update on your Pixel 7 Pro and then using that boot.img in magisk to get a patched version?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, with only the first eight characters of the SHA-256 hash, such as for the Pixel 6 Pro:

where the SHA-256 hash is:
[Google Pixel 7 Pro] roirraW "edor" ehT:
The OTA zip is not the factory image zip. It's typically smaller than the factory image zip, as it only contains what's needed to bring your phone up to the latest update, whereas the factory image zip contains everything. The boot.img file in the OTA zip is not the full boot.img file that'll be present in the factory image zip.

Theoretically, with an unlocked bootloader, you can use commands to rip the boot.img from the phone, but it's risky re-flashing such a boot.img, and not worth the trouble. Just wait for the firmware zip, likely tomorrow ~1PM ET.
[Google Pixel 7 Pro] mariusnoor:
No, unfortunately, this is only a security update, meaning the boot.img is 0 bytes large. You can't root your phone with that file..
[Google Pixel 7 Pro] Larakali:
im trying to bruteforce the download server for the full one.

ill be able to maybe
[Google Pixel 7 Pro] Annie the Eagle:
Ah okay! I guess we wait for the firmware.zip :D
[Google Pixel 7 Pro] roirraW "edor" ehT:
Pixel Update Bulletin—November 2022 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] Tracker31:
Simplest way to update phone with magisk and root remain running?
[Google Pixel 7 Pro] vurtomatic:
Oof. I just flashed Oct over the weekend and am still setting up my phone :LOL:

Question: I'm guessing whatever magisk / lsposed modules will need to be reapplied? Is there a process that people do?

Or do they automatically get re-applied after a dirty flash?

Asking ahead, I'm catching up on flashing and first time using a Pixel.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hello!

Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

How to update each month (and also how to root)

[requires an unlocked bootloader for updating via this factory image method]
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi!

Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

How to update each month (and also how to root)

[requires an unlocked bootloader for updating via this factory image method]
[Google Pixel 7 Pro] Tracker31:
what about verity and verification? on Android flash tool these options like lock bootloader and disable verifications are already deselected. I am not sure and want ask. Dont need to set up phone again :D thanks for help