yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi! Each person's method has their advantages and disadvantages. I prefer to simply extract the Platform Tools (use 33.0.3, not 34.0.0 or 34.0.1 because 34.x has serious bugs). I try to keep the path names short, so I extract it to the top level of my S:\ drive. Obviously or not, you'd have to choose among drive letters that are available to you - could be C:\ or something else.

So I end up with S:\platform-tools, with all of the files like ADB and Fastboot in the folder.

Each month when an update comes out, I keep the old platform-tools folder around and just name it appropriately, like platform-tools <firmware release number>. I then extract the Platform Tools fresh.

I also extract the contents of the new firmware zip to that same S:\platform-tools folder. I edit the flash-all.bat, of course, and for my Pixel 7 Pro, I extract the init_boot.img from the zip that's now inside the platform-tools folder and put it directly in that folder. If you have the Pixel 6 Pro, you'll use the boot.img file instead of init_boot.img.

My steps are also reflected in the "How to update each month (and also how to root) [requires an unlocked bootloader for updating via this factory image method]" section, starting at step 4. Unzip the Platform Tools.

If I had more than one phone (well, I do have some old phones), I'd create a different platform-tools folder for each one. You could, for example, name one folder platform-toolsP6, for Pixel 6, or whatever makes the most sense to you.

I hope all that answers your question.

Yes, use 33.0.3, at least until they come out with a version higher than 34.0.1.
[Google Pixel 7 Pro] Ghisy:
Roger that! 👍

I'm not even gonna try 34.0.1 at this point, too risky!

Edit: update successful! I can confirm 33.0.3 works fine with the April security patch! Magisk updated to v26.1 as well. It's all good! :)
[Google Pixel 7 Pro] Schroeder09:
Do you use LS posed? Is version 1.8.7 still working with your combination of installs?
[Google Pixel 7 Pro] Ghisy:
I do use LSposed, I'm on v1.8.6 (which I think is the latest stable?). I didn't touch anything related to it and everything works fine (I'm using AOSPMods).
[Google Pixel 7 Pro] roirraW "edor" ehT:
There it is!

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Says 26.1 for both Stable and Beta now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Oh yeah, I meant to tell you. I used it for the first time the other day, both from my Pixel 1 and Pixel 7 Pro to Windows. Worked great! Going to use it to send init_boot.img and Magisk'd_init_boot.img back and forth here in a minute while I update.

Edit: One caveat/bug I notice is that if I have Nearby Share on Windows set to save files that are received to the X:\sample\ location, and next time I want to change the location to somewhere else, but X:\sample is no longer available (I don't have the X: drive mounted), then it wouldn't let me change the location until I made X:\sample available again, temporarily.

Edit 2: Second slight caveat. It can't share an "empty" file, i.e. a text file with nothing in it, but that's easily solved.
[Google Pixel 7 Pro] Born<ICs:
Thank you much for the explanation, I think I can manage better now.
[Google Pixel 7 Pro] UberNorse:
Has anyone on T-Mobile tried flashing yet? I'm holding off until I hear further on this.
[Google Pixel 7 Pro] Lughnasadh:
I'm on T-Mobile through Mint Mobile and haven't noticed any problems.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
No issue with April firmware on 7Pro Global, using Platform tool 33.0.3, Magisk 26101 for patching init_boot, root ok, no bug with Zygisk, Lsposed, Themer and Aosp. All work as a charm 👍👍
[Google Pixel 7 Pro] Fishawy:
I didn't know you could use Themer and AOPS Mods together!

Any particular setting I should be aware of before testing Themer? I don't need a nasty bootloop surprise.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
For me, there are complementary. I use Themer for theming and changing disposition and Aosp is used for modify only navbar, lock screen, status bar and some miscellanous. I just don't use same items on both app.

It's smooth and stable
[Google Pixel 7 Pro] dr_rick13:
hey! is Google Wallet working for you yet?

I was able to update without issue and went through the safetynet steup and hid all the Google apps and cleared data as well but it tells me my device doesnt meet the requirements to use Google Wallet.

Any help is greatly appreciated!

EDIT: It decided to work after I made this post :)
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Sorry, i don't use Wallet 😉
[Google Pixel 7 Pro] justDave:
Maybe you do now that you've made that post.
[Google Pixel 7 Pro] Schroeder09:
Device integrity isn't passing on April update. Magisk 26.1 stable. Lsposed 1.8.7. universal safety net fix v2. 4.0. Am I supposed to be using another version of this magisk module?
[Google Pixel 7 Pro] xunholyx:
It's probably not Magisk, but that's just an opinion, not a fact that I can confirm
[Google Pixel 7 Pro] Lughnasadh:
Try this one.
[Google Pixel 7 Pro] justDave:
Which device integrity are we talking about? Are you on universal safety net fix v2.4.0 mod 1.2?
[Google Pixel 7 Pro] takahashi_gunma:
I'm using a Pixel 7 pro device which is on Android 13 (TQ2A.230405.003E1) but the device is in "device state: locker". Is there any way to unlock it so I can root my device?

We hope to help/
[Google Pixel 7 Pro] mariusnoor:
I do however have good news for those who got a free Pixel Watch:

You can link your card to your Pixel Watch and it'll work without any problems, even though GPay isn't working on your phone.

Just successfully did a test transaction:
[Google Pixel 7 Pro] roirraW "edor" ehT:
That is interesting indeed, and good!
[Google Pixel 7 Pro] Annie the Eagle:
Just to confirm, that was with Zygisk and DenyList enabled with the various Google Play stuff added to DenyList?
[Google Pixel 7 Pro] mariusnoor:
Yup.
[Google Pixel 7 Pro] mariusnoor:
Very strange behavior though.

Everything is loading for eternities, especially the field where you're supposed to enter the confirmation number you get via SMS. The message arrived, but the field was still a loading circle. Also, adding the card to the watch took a minute, very weird. But at least it works, added 3 cards as of now.
[Google Pixel 7 Pro] Ghisy:
Have you guys seen that? (found in a different thread here)

https://twitter.com/i/web/status/1580580220913954817

Apparently, the Pixel 7 build of Android 13 is dropping support for 32 bit-apps! That's crazy...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I know there's been news of them planning on doing that, previously, so it doesn't surprise me.

I don't really consider it crazy to drop 32-bit support. 32-bit has been around since the late 1980s or early 1990s. It's time is quite past.
[Google Pixel 7 Pro] mariusnoor:
Hahahahha, this is too funny

Despite CTS Profile Match failing, Google Pay (on the Pixel 7 Pro) works no problem.
[Google Pixel 7 Pro] Ghisy:
I know 32 bits is quite old but does that mean death for legacy apps that haven't been updated? Man, I'm gonna need to find a bunch of new apps to replace perfectly working ones :(
[Google Pixel 7 Pro] Annie the Eagle:
Hahahaha, I wonder if maybe it actually *is* working (the SafetyNet fix) but maybe the checker is not parsing the Android 13/P7P response correctly.

I doubt it, but it would be funny if that's true.

Try clearing your cache/data on Google Play Store, and checking if Google Play Certification is "Certified" (not sure if it should be certified but would be interesting to see).
[Google Pixel 7 Pro] mariusnoor:
It doesn't show me if it's certified or not, but it's not complaining about anything either. Green checkmark.
[Google Pixel 7 Pro] simplepinoi177:
I know a lot is going on with all the news on the issues with passing safetynet so it's probably long forgotten and doesn't need an update, but I just wanted to thank you on the response and add that I'm of the same opinion; to untick the "oem unlocking" and unlocking the bootloader off the bat. I was one of the few who was able to unlock their Verizon Pixel 2 XL's bootloader, and for it to have worked, one had to do those things first-thing or else you would lose the ability. So I also have that peculiar superstition to do it right away, lest you might lose the ability (especially for those, like me, who plan on loading up their device on Verizon's network).
[Google Pixel 7 Pro] Annie the Eagle:
If you tap your account icon top right of Play Store then go "Settings" -> "About" it should say your play protect certification.

Funny enough, even mine is showing "Not certified" -- without any root, so I wonder if it's just to do with an unlocked bootloader. Anyone else know?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Indeed, you and other Verizon users with an unlocked Pixel definitely have even more reason to be pro-active.

I was a Verizon user with a Verizon Pixel 1 and was able to unlock while the phone was still on Android 7.1.0 or 7.1.1, so I'm glad I was able to take advantage of that before 7.1.1 or 7.1.2 - been too long, I don't remember which version was the cutoff now.
[Google Pixel 7 Pro] bosox284:
What are the odds Google drops new platform-tools with the factory images later? Debating whether to unlock now or just wait a half hour
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'd unlock now, but maybe you meant wait to root. I'm waiting for the official factory image zip. I wouldn't worry about platform tools. Several users have rooted using the fastboot and adb we have already.

I'm not a betting person either way on whether there'll be a new platform tools version, but I would guess there won't be today.
[Google Pixel 7 Pro] ScottIsMyName:
Can someone with a clean, locked bootloader pixel 7 pro see if the play integrity is passing right now? It's possible that it might be broken until the phone is officially "released"
[Google Pixel 7 Pro] 96carboard:
It means only for older NATIVE applications. Anything written in pure java/kotlin will be just fine.
[Google Pixel 7 Pro] Ghisy:
Well, I wouldn't know if my installed 32 bit-apps are pure Java/Kotlin... 😅
[Google Pixel 7 Pro] hendusoone:
Yup. I just set mine up. Still locked. Play store says "Device is certified". YASNAC passes both basic integrity and CTS profile match. Play Integrity API Checker is all green.
[Google Pixel 7 Pro] Dr.Pepper:
Did you try to read 1 page with instructions?)

Unlocking isnt only switching on OEM unlock in developer setting, you also need run fastboot flashing unlock command in cmd on PC to unlock bootloader which will wipe data on your device
[Google Pixel 7 Pro] Schroeder09:
No. I said which one I'm using. It's 2. 4.0.
[Google Pixel 7 Pro] Schroeder09:
That's the one in on.
[Google Pixel 7 Pro] Lughnasadh:
You said you were on 2.4.0. The one I linked is 2.4.0-MOD_1.2.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Edit: Ninja'd by @Lughnasadh :D

I think you're accidentally contradicting yourself. The one @Lughnasadh linked to (and you replied that's the one you're on) is 2.4.0 Mod 1.2, which is what you should be using, as regular 2.4.0 has been improved upon with @Displax' 2.4.0 Mod 1.2. I pass Basic Integrity, CTS profile match, and Device Integrity.

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

SafetyNet
[Google Pixel 7 Pro] roirraW "edor" ehT:
See Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

How to Root the first time / aka How to unlock the Bootloader

Unlocking Bootloader

(required in order to root)
[Google Pixel 7 Pro] Schroeder09:
Ok I didn't see that in the notation. It just said 2.4.0 I thought. I went back to 2.3.1 mod 3 and everything is now passing. On April update, have lsposed 1.8.6, and magisk 26.1 stable.
[Google Pixel 7 Pro] HipKat:
Good looking out. I was just coming here with the same issue!
[Google Pixel 7 Pro] Schroeder09:
This is definitely v2. 4.0. What is it supposed to be? V2. 3.1 mod 3 passes safety net but seems to have broken my assistant V2 voice typing and weather at a glance widget
[Google Pixel 7 Pro] Lughnasadh:
Again, the link I provided you is 2.4.0-MOD_1.2. Are you looking at the releases?
[Google Pixel 7 Pro] justDave:
It's confusing. Since it's a clone of the kdrag0n repo, the download link points back there. Don't click that link. Just scroll down to the releases and you'll see the mods.
[Google Pixel 7 Pro] simplepinoi177:
Yeah your v.2.3.1 mod 3 works because it's still a Displax branch -- which works best with the Pixel 6 & 7's (which I believe is what Displax was originally was catering to when creating it) -- so updating to Displax's most recent v2.4.0-MOD_1.2. (like Lughnasadh states in the quote below this) will work best! Old versions might/should still work, but latest version will probably have better "things" under the hood that should/might prevent issues down the road...

Yeah...it can get confusing as some members go straight to kdrag0n's looking for Displax's. They should be sure to go to Displax's Github, but that link should be pointing to Releases, not "tree/integrity" part in the URL...
[Google Pixel 7 Pro] HipKat:
Direct link
[Google Pixel 7 Pro] roirraW "edor" ehT:
Also note that Displax has their own XDA thread for their mod versions of Universal SafetyNet Fix Mod on XDA, and which contains the latest mod version as an attachment, besides linking to the mod's GitHub page, and separately linking to the GitHub Releases.

I had no idea until now that "Download latest version" on the GitHub page directs to kdragon's, which is indeed odd. I always look and go straight to the Releases listed on the right. Edit: I've let Displax know, in case they decide to change that link on GitHub, but it's up to them.

In Post #2's SafetyNet section, I got tired of specifying exactly which one to use at any one time, since it swapped back and forth for a short while, but I list both and say to use whichever is newer. When/if kdrag0n updates theirs and might be preferred over Displax', I might choose to at least reverse the order I list the two in so that the newer one remains listed first.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I made Displax aware of the confusion, and they've changed the text and link at their GitHub. It now says Download latest [MOD] version and correctly links to it.
[Google Pixel 7 Pro] badabing2003:
Word of caution, the update link in the module points to kdarag0n's repo, this could be intentional so that when kdrag0n releases a new version it gets updated to it, however people could get caught off guard.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! I think I noticed that a long time ago, but I forgot. I'll ask Displax.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I did ask, but I ended up answering my own question with the following from the first page of his OP, where Displax responded to another user:

Every once in a while, I still get to feel like a newbie. :)
[Google Pixel 7 Pro] badabing2003:
Yep I suspected it was for that reason.
[Google Pixel 7 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1646974195467681792
[Google Pixel 7 Pro] halfbytecode:
I am thinking of an idea to install OTA updates on a Magisk rooted device, without requiring a PC/Laptop and full factory images.

Would it be possible to restore the unrooted init_boot by using the flash image option of Kernel Flasher, and without rebooting, proceeding to install the OTA update, followed by using Magisk app to install it to the inactive slot, and then rebooting into the rooted and updated system?

Backing up the unrooted init_boot using Kernel Flasher at the right time for using later, could be done too, if possible.
[Google Pixel 7 Pro] badabing2003:
If you're rooted, Magisk already has made backups, you can use that try to dd the init_boot backup image to the partition.
[Google Pixel 7 Pro] halfbytecode:
I guess my idea should work then?

DD or even Kernel Flasher could work to restore the unrooted init_boot image, in that case.

I wonder if it is necessary to uninstall Magisk and/or its modules, unhide Magisk app and stuff, or just restoring the unrooted init_boot should be sufficient, to successfully install the OTA update?
[Google Pixel 7 Pro] badabing2003:
Not necessarily, specially with Samsung.

Please read this.

I was merely responding on how it could be done, not necessarily endorsing it.

Perhaps it might work for some devices like Pixel, but that is an uncharted territory.
[Google Pixel 7 Pro] albsat:
How comes that after December 22 ota, I have never received another ota update? Well next to the manual monthly firmware update via fastboot... It's a bit annoying.
[Google Pixel 7 Pro] badabing2003:
Are you rooted?
[Google Pixel 7 Pro] albsat:
Yes, but no update notification was ever offered since December.
[Google Pixel 7 Pro] badabing2003:
I never get update notification, but would prefer it that way too.

It's not always that you would get notified if you're rooted.
[Google Pixel 7 Pro] halfbytecode:
I actually read that a while ago when Magisk v26.1 came out. However, I feel it may be related to Samsung only, due to the presence of all sorts of strange partitions/files on their phones. It is also specifically listed under the Samsung category. Even while installing Magisk on Samsung phones, it suggested to flash like 3 additional files along with to make it work.

I have a feeling that for Pixel 7 Pro it may work if we flash unrooted init_boot. I have successfully flashed boot.img on a running system while flashing a kernel, directly from Kernel Flasher, when the AK3 zip for a kernel was not flashing it.

Is soft brick the worst that can happen if I flash unrooted init_boot as suggested earlier? If so, it would be fixable by flashing full factory image.

I may not be able to try all this out though as I am not able to remain on stock for long, due to its significantly inferior battery life and sound performance of external speakers, when compared to custom ROMs.
[Google Pixel 7 Pro] reaper000:
I thought that there was a thread somewhere on XDA that was dedicated to posting Magisk-rooted init_boot.img (originally boot.img) with every monthly update, for convenience sakes.

Anyway, for anyone desiring root on the Apr 2023 monthly update, here's the Magisk 26.1-patched version of init_boot.img...
[Google Pixel 7 Pro] supermansaga:
So the April update is now called .E1. I have been thinking it's gonna be .C1 again. So I tried to pull up the cheat sheet you have given me. I am gonna flash!
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's unpredictable every time. The numbers after the date in the firmware # (230405 - April 5, 2023 in our current TQ2A.230405.003.E1) are meaningful, but only to Google. See Post #4 - Build ID definitions, and thank @Namelesswonder.

Also see:

Codenames, tags, and build numbers | Android Open Source Project

source.android.com

I did a very fast analysis of the firmware numbers for the Pixel 7 Pro so far, using Google Sheets and some quick formulas to automatically list statistics/summaries.

For the Pixel 7 Pro:

For the Pixel 6 Pro:
[Google Pixel 7 Pro] hpower1:
Thanks again to all for all the up to date info in this thread. Another successful update to April for me.

Using platform tools v33.0.3 and magisk 26101
[Google Pixel 7 Pro] UberNorse:
My April update failed on me multiple times no matter what I did. Using platform tools 33.0.3 and magisk 26101. Gave the sparse failed error at least 8 different ways I tried flashing. Had to use the google flash tool to get out of bootloop. I am on April update for now but I cant root. Every time I tried to extract init.boot it told me that it was corrupt and couldn't mount. I downloaded the update several times but each time said the same thing.

Edit - I have been updating and rooting successfully since November.
[Google Pixel 7 Pro] badabing2003:
How are you doing this? on your PC? Using which tool?

Have you checked the checksum of the downloaded firmware against the published one?
[Google Pixel 7 Pro] UberNorse:
Yes, I am using my pc. I have tried it with both 7zip and peazip. I will install winzip and try it for now, but the factory images are now gone and I can't download again as I believe mine is corrupted and I can't see the md5 sum anymore.

EDIT - I found the factory images again I'm not sure why but I had to click acknowledge on the page to see them again.
[Google Pixel 7 Pro] badabing2003:
7zip should be fine.

I know you are seeing the factory images now, but sometimes people have problems seeing the new ones unless they change the language to English, keep that in mind.

And it's sha256 that has to match, not md5

if they match, then you should be able to extract the init_boot.img without problems.

If you can't you might want to look for malware first and the disable AV temporarily and see if it makes a difference.
[Google Pixel 7 Pro] UberNorse:
Thanks, I tried my laptop versus my pc and it worked just fine. Now rooted again on April. Not sure what the problem is on my desktop. The sha256 did match on desktop but kept failing. Doesn't matter anymore. Thanks again.
[Google Pixel 7 Pro] badabing2003:
Probably AV getting in the way, happy to learn that it's all good now.
[Google Pixel 7 Pro] G-ThGraf:
Hi eveyrone.

Need a bit of help.

Dispite phone rooted, it managed to update itself to TQ2A.230405.003.E1

(normally, I have to do it manually).

So now phone is updated with TQ2A.230405.003.E1 and April sec patch.

So I went to my PC,

- downloaded the TQ2A.230405.003.E1

- updated to Magisk 26.1 (forgot to disable activated module, does it matter ?)

- extracted init_boot to phone

- patched it with Magisk 26.1

- copied back to PC

- flashed the patched version to phone WITH success, no fail.

Then reboot... And NO Root.

Tried 3 times, still the same.

What could be wrong ?
[Google Pixel 7 Pro] badabing2003:
Probably you have multiple Magisks on your phone (perhaps one hidden and one not)

If you upgraded Magisk while it was hidden, it is possible that it didn't manage to uninstall the hidden one.

Make sure there is a single Magisk, reboot and you should be fine.
[Google Pixel 7 Pro] G-ThGraf:
Oh woaw.

That was easy and fast.

Not exactly sure how it happened but a copy of the hidden Magisk was also installed as a Worker Profile app.

Removed it. Fixed

Thank you 🙏
[Google Pixel 7 Pro] zrzhu:
I never had a pixel phone before. Can I follow the steps to root my pixel 7? Thanks.
[Google Pixel 7 Pro] justDave:
Pretty much. The regular Pixel 7 is called Panther so use that firmware instead of Cheetah. Otherwise the steps are the same.
[Google Pixel 7 Pro] roirraW "edor" ehT:
The update at the usual place(s). Can't update the thread with the details right this second.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Community

Pixel Update Bulletins | Android Open Source Project

source.android.com

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

developers.google.com
[Google Pixel 7 Pro] Ghisy:
May update is now available: https://dl.google.com/dl/android/aosp/cheetah-tq2a.230505.002-factory-fe44ced0.zip
[Google Pixel 7 Pro] justDave:
I have to ask before I update... Did they disable dual active eSIM again?

Edit: Looks like it's still working!
[Google Pixel 7 Pro] Schroeder09:
Anyone running lsposed, James dsp audio, and/or skavalex call recorder on the new may update?
[Google Pixel 7 Pro] LLStarks:
Per Josh from the Shannon modem Telegram:

Guess this won't be fixed until next month's stable QPR3. Bad news for T-Mobile users.
[Google Pixel 7 Pro] Paz9:
Is smart lock fixed?
[Google Pixel 7 Pro] amders:
also wait for this information....
[Google Pixel 7 Pro] Schroeder09:
Wonderful people that are not in any way (sarcasm) in part responsible for the migration away from XDA to other platforms like reddit and telegram told me off for asking this question. No monthly update has ever broken lsposed!!! ::rolls eyes::
[Google Pixel 7 Pro] reaper000:
Again, for flashing convenience, here's the Magisk 26.1-patched init_boot.img for May 2023 to obtain root...