yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
New Gen-AI Features Coming to Your Pixel - Google Pixel Community
[Google Pixel 7 Pro] Ghisy:
Oh awesome. I guess I've missed this thread! I'll take a look, thanks! 👍
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android Security Bulletin—April 2024 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] amders:
really s*cks.. even until today google has not enabled volte as default... really s*cks
[Google Pixel 7 Pro] itschaotic:
Does anyone have any idea why I'm losing root after a while? This has happened twice in the same week
[Google Pixel 7 Pro] fijasko:
does your system update itself? have you ever gotten the notification about it?

lately, even the rooted phones with the update option turned off somehow get the new updates automatically. it happened to me and some others here and in P8P forum and we had to root again
[Google Pixel 7 Pro] itschaotic:
No, it does not automatically update and I keep this option disabled anyway. Just for the sake of information, I'm already in the last beta released in April, and today I opened Magisk Delta and saw that the root is gone again.

Other information: I was able to root for the first time with the official Magisk, but then I couldn't, even though I was patching init_boot as casually. So I only managed to root again with the Magisk Delta
[Google Pixel 7 Pro] justDave:
Yes. This happened to my Pixel 6a the other day. I was still on January and got the notification that the phone was updated and I needed to reboot.

I went into Magisk and did the install to other slot (after ota) and rebooted. When it came back up I was on March and still rooted.

I guess the flash after ota option is still working
[Google Pixel 7 Pro] sawdoctor:
I've had that happen once and I've had the magisk app uninstall itself once. Sometimes you just need a reboot and root comes back
[Google Pixel 7 Pro] itschaotic:
What??? I'm feeling like an idiot now but not so stupid cuz when I used the official Magisk, I even restarted the device several times but the root didn't come back. Thanks ❣️
[Google Pixel 7 Pro] dimm0k:
anyone used this with the April update and root successfully?
[Google Pixel 7 Pro] itschaotic:
Me
[Google Pixel 7 Pro] T.A.R.D.I.S.:
I have same issues than others here : my 7pro auto-updated from February to march. So i've flashed April (PT 34.0.4) and i can't root with patching init-boot with Magisk 27001. I've reflashed rom with new platform tools 35.0.1. and same issue.

Other in the same case here?
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Solution to my issue : flashing patched boot on slot a. Since i have my 7Pro, i always flash on slot b. Auto-update has probably change slot.

So, if you are in the same case, you have to flash your Patched boot on the other slot.
[Google Pixel 7 Pro] Lughnasadh:
Yes, OTAs always install to the inactive slot. Flashing factory images install to the active slot.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
I think it's the first OTA of my life on Android since my Galaxy Note 1 😬😬

So, i didn't think about the inactive slot with OTA, because i flash after OTA. 😉
[Google Pixel 7 Pro] roirraW "edor" ehT:
+1 Me, too, with Magisk Stable v27.0.
[Google Pixel 7 Pro] dimm0k:
add me to the list, just updated too!
[Google Pixel 7 Pro] Ghisy:
I used v35.0.0 to be on the safe side but glad to hear v35.0.1 works as well! 👍
[Google Pixel 7 Pro] darkness4every1:
I lost root after installing with latest version of Pixel Flasher and Platform Tools 35.0.1.

I'm updating every month without issues, this has never happened before.
[Google Pixel 7 Pro] Jwtiyar:
Normally you will lose root after update.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Only if you don't patch the init_boot.img with Magisk in PixelFlasher, and select that patched init_boot.img when you tell PixelFlasher to flash the firmware update.
[Google Pixel 7 Pro] darkness4every1:
Yeah exactly, which I always patch.

Wasn't a big deal tho, just patched the new init_boot and manually flashed it.
[Google Pixel 7 Pro] TotallyAnxious:
Yes
[Google Pixel 7 Pro] Ghisy:
I just got the notification from the Google app about circle to search! It launches a tutorial asking to hold the navigation bar... But it doesn't work. 😅

Go home Google, you're drunk!
[Google Pixel 7 Pro] Ghisy:
Okay, I've figured out why it wasn't working.

I'm in the EU and I recently had to choose my default search engine via a notification. I chose Duckduckgo because that's what I use to search (never really liked Google for this). I thought 'maybe this choice is blocking/breaking circle to search somehow'.

So I temporarily set the Pixel launcher as default (I use Nova) and long-pressed the Duckduckgo search bar and set it to Google instead. And what do you know, I was greeted with the option to use circle to search and it works now!

So basically, if your default is not Google search, you can't use CTS. I kinda understand the idea behind this behavior but it should let you know.
[Google Pixel 7 Pro] bird333:
As a general rule, should you update Iconify and PixelXpert before the firmware update or do it after? Or does it even matter?
[Google Pixel 7 Pro] PurppleMonkey:
Hi !

I can see a huuuuuuuuge difference between the P7P forum and P7 hahahha

Can i follow this tuto for my P7 ? (using "Panther" instead of "Cheetah" ?
[Google Pixel 7 Pro] rlewis312010:
- fastboot flash boot magisk_patched_file.img fails with "error: cannot load 'magisk_patched-25200_1a2BSc.img" so I'm stuck. I made the file using Magisk and copied it to the same folder as platform-tools. Then I ran a command prompt and am getting nowhere.
[Google Pixel 7 Pro] davidgro:
@roirraw-edor-eht (No idea if that will work)

Perhaps remove "Pass SafetyNet" from the thread title and instruction headers until that's actually possible? (besides Basic) - I mean leave the directions that exist, but it's kinda misleading to have headlines in post 1 saying it will pass after we do them.
[Google Pixel 7 Pro] TheLoonyRebel:
Read the main post to this thread.

On that note.... here I am now a Pixel 7 Pro owner.
[Google Pixel 7 Pro] rlewis312010:
Yeah, it doesn't work for me. Even after clicking on the .bat file and that process finished. It keeps giving the same error for the fastboot flash. If it was like Odin I could just pop that updated file into a slot, hit flash and be done. I found the Flash Tool for Pixel and that locked up and wouldn't patch the file it found. Then I couldn't simply pick what I wanted to flash. Everything is in the platform-tools folder and I run a command prompt in there.
[Google Pixel 7 Pro] Namelesswonder:
I want to know where you are at, because you were previously having issues just updating the phone.

Were you able to complete that?

What are you currently trying to do?

If you're trying to flash the Magisk patched init_boot.img over the boot slot, then you're doing it wrong.

You flash it over init_boot, fastboot flash init_boot magisk_init_boot.img
[Google Pixel 7 Pro] rlewis312010:
I'm giving the command and the guide says to use the name our file has right? I do that and it is giving me an error cannot load "name of my patched magisk file." Yeah I updated once I knew it wouldn't do anything bad. Then I was going through the steps but the POS won't do anything other than give the error. I moved platform-tools to the root of C: as I think I did years ago. Then I opened the command prompt and thought I was going line by line of the directions.
[Google Pixel 7 Pro] simplepinoi177:
one possible reason is you state you run the command line "fastboot flash boot" when it's supposed to be "init_boot", (in pretty big bold letters in the OP btw...)

but I would think that your phone would simply bootloop instead of it stating "error: cannot load" -- there have been a few posts here and on another thread where people have made this same mistake and it caused a bootloop -- so there might still be a pressing issue nonetheless, although I can't think of why it would just error out can't load.....
[Google Pixel 7 Pro] rlewis312010:
Open a Command Prompt and navigate to the platform-tools folder.

Run command:

Code:

adb reboot bootloader

After phone has rebooted into Bootloader (Fastboot) mode, run command:

Code:

fastboot flash init_boot magisk_patched-25200_1a2B3c.img

fastboot reboot

I'm literally copying/pasting the command but changing the file name after 25200_ so it makes no sense unless the command is somehow wrong. Odin was much easier lol.
[Google Pixel 7 Pro] Namelesswonder:
Rename the file to something else like magisk.img and try again. If it still doesn't work then copy the fresh init_boot.img back to your phone and patch it again in Magisk.

The "cannot load" error is because the path to the file fastboot is trying to open doesn't exist.

I want to see a screenshot of the command prompt window.
[Google Pixel 7 Pro] llin:
Send a screenshot of the command window so we can see the input and output from the commands.
[Google Pixel 7 Pro] swieder711:
About 1/3 of the apps that I restored with Swiftbackup didnt work. I am having to uninstall/reinstall the app thru the Play store to get them working again. Bit of a bummer.
[Google Pixel 7 Pro] rlewis312010:
Thanks, if I try it manually again I'll see if I run into anything. I used PixelFlasher and had to choose to use file mode and as soon as I turned that on PixelFlasher did it's thing and now I'm rooted. That is a good tool to save some time. If I try again manually I'll try to rename the file to something different and if it still doesn't work I will post a screen shot.
[Google Pixel 7 Pro] Namelesswonder:
I've spent the past 4 hours trying to get fastboot boot to work with modified ramdisks on the Pixel 7, and I can say that it either doesn't work, or I don't know what I'm doing.

First off, the fastboot help output isn't lying, but it is omitting information on how it should be used.

fastboot boot KERNEL [RAMDISK [SECOND]] makes it seem like supplying a boot.img and a ramdisk (image? raw cpio? compression?) should work fine, however when I run it I get fastboot: error: cannot boot a boot.img *and* ramdisk

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

Well after looking at the code, it turns out it is capable of doing two things, passing a supplied boot.img to the device, or creating a boot image from components (kernel, ramdisk, dtb, second stage) to then pass to the device. If there is a second argument and it determines the first argument is a valid boot.img then it fails. It fails because where can it put the ramdisk being supplied, boot.img should already have a ramdisk.

This is the next issue, the Pixel 7 doesn't have a ramdisk in the boot.img, and the boot partition only contains the kernel binary.

The Pixel 7 actually uses four ramdisks, init_boot holding just the init binary, vendor_kernel_boot holding kernel modules, and vendor_boot holding two ramdisks combined with one being a few platform related stuff like configs and firmware and the other being the contents for the recovery. The only thing that matters is init_boot, but I can't find any way to get the phone to boot with the image created by fastboot.

I used the x86_64 libmagiskboot.so from the Magisk-v25.2.apk to unpack the kernel binary from boot.img, the ramdisk from init_boot.img, and from the Magisk patched one, but my phone just boots back into the bootloader after fastboot sends it the created image. Even tried decompressing them, using gzip, xz, or keeping them as lz4.

It might be that I need to use mkbootimg to create my own, as fastboot isn't doing it properly. Potentially incorrect offsets or headers. Need to study the header formats.

include/bootimg/bootimg.h - platform/system/tools/mkbootimg - Git at Google

At this point I think the Pixel 7 is unable to boot a traditional boot.img, and that it is only capable of booting kernel binary images. Which isn't that helpful for us because Magisk needs to modify the ramdisk and insert itself into the init.

Anyone that is a GSI/GKI wizard could help us out. However as it stands right now just flashing the Magisk patched init_boot.img gets us root without issue, so eh, whatever. At least it appears custom kernels on the Pixel 7 will never overwrite Magisk unless they want to modify the init in init_boot.img
[Google Pixel 7 Pro] badabing2003:
Thanks for all the testing.

"Failure is a success in progress"

Albert Einstein.
[Google Pixel 7 Pro] grimz:
Hello 👋, coming from the OnePlus world having never owned a Pixel before. Thank you all for the great thread, awesome to see a strong rooting community for this device.

Just wanted to clarify our options for OTA/updates. On my OnePlus (7 Pro, 😆) phone with an unlocked bootloader and Magisk + modules (stock everything else) the System Update app detects root and downloads a full zip of the new Factory Image version. All I need to do is let that download and install and, rather than rebooting, switch to Magisk and install onto the inactive slot and then reboot. Phone then boots up the new version and everything is carried over.

Is there no similar process for Pixel phones? For updates, do we have to make sure not to install OTAs and always flash and patch the full zips manually as per the OP's post? Also, assuming it were possible, would we need Magisk to update so that it knows to patch the right file (init_boot.img) on the inactive slot?
[Google Pixel 7 Pro] V0latyle:
Pixels have always been A/B devices, so the automatic OTA process is the same - update_engine downloads and extracts the OTA to the inactive slot, which you then have to patch using Magisk (install to inactive slot). There were issues in previous versions with Magisk not doing this properly, and I would assume that Magisk doesn't already "know" how to properly handle the Pixel 7.

Yes. We need to start by making sure the developers are aware, so someone knowledgeable on the issue (such as @Namelesswonder ) should open an issue on the Magisk git if it hasn't been done already. It only needs to be done once so everyone else, DO NOT go over there and spam your own issues. It'll get fixed when it gets fixed.

That being said, the Magisk devs are pretty quick about fixing issues. When we started out on Android 12, Magisk 23001 did not work with the A12 boot image. It wasn't until 23015 IIRC that this was completely fixed; the Pixel 6 received an update a couple months after launch that broke this, so Magisk had to be updated again. OTA patching wasn't completely fixed until somewhere around Magisk 24.
[Google Pixel 7 Pro] Annie the Eagle:
Yeah I was actually thinking about this, I guess Magisk will need to know to patch init_boot partition on the inactive slot. So for now, if we get an OTA, we will lose root until we get the OTA's file from Google Dev Resources webpage and do the patching setup manually?

Is there any risk to this normally (bootloop, etc) or will we just temporarily lose root?

I guess for now the best way to update OTA with root would be:

1) Disable modules and Uninstall Magisk in the app (lose root)

2) Install OTA

3) Reboot

4) Download OTA ZIP from Google Webpage

5) Redo the patching of the init_boot.img as you would normally

6) Fastboot flash

7) Root regained.
[Google Pixel 7 Pro] badabing2003:
If you're going to download a file on your PC (OTA in this case) why even bother with this long and risky process?

Just download the full firmware and do the standard dirty flashing as explained in the thread.

You can do everything in one shot without even losing root.
[Google Pixel 7 Pro] Annie the Eagle:
What method is that? Sorry I haven't really kept up to date with all the different methods.

If I had the full OTA what would I do then to preserve root?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Generally, you want to update everything before a firmware update. I haven't been using Iconify for the last half a year, so I can't speak specifically about it with the current firmware. I'm still on PixelXpert Canary 338, however, with no issues.
[Google Pixel 7 Pro] bird333:
Platform tools 33.0.3 still good to go with April update?
[Google Pixel 7 Pro] T.A.R.D.I.S.:
No issues too with Canary 347 ans Iconify 6.76 on April update 😉
[Google Pixel 7 Pro] simplepinoi177:
yeah, I imagine so, but it seems 35 has been reported to be stable enough and not cause any bricking issues as early 34 did...
[Google Pixel 7 Pro] samdaman91:
Can the mint mobile carrier locked pixel 7 pro be unlocked without having mint mobile unlocking the device?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No. The carrier must carrier-unlock the device - which would allow it to be able to be used on other carriers, although that's no guarantee by itself that this will then allow the device to be bootloader unlocked, but the few carriers that their Pixels don't come bootloader unlockable out of the box which can eventually allow bootloader unlocking require the phone to be paid off and for the carrier to carrier-unlock it before bootloader unlocking is possible.

i.e. they're two separate things that aren't necessarily tied together, but frequently are - just not always. Verizon devices, for example, always eventually become carrier unlocked, but they'll never be bootloader unlockable.

I think Mint uses AT&T's network? So I think it should be similar to AT&T, which from what I remember is like I described in my first paragraph above.

Edit: Just to be clear, I don't know for certain the situation with Mint Mobile regarding bootloader unlocking, but the carrier is definitely the only one who can carrier unlock it.
[Google Pixel 7 Pro] samdaman91:
thats a shame. are you sure i cant unlock the phone without the carrier intervention? in this forum someone found a glitch?

Successfully Bootloader unlocked AT&T Pixel 7 Pro!

Hi guys, I'm a longtime member here and developer for Paranoid Android custom rom. While I haven't been active on XDA these days, I did want to share a bit of information about how I unlocked the bootloader on my AT&T Pixel 7 Pro. To my...

xdaforums.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm sure that there is no "this is how you do it" that will just work all the time. There will always be unpredictable factors on all technology; there always has been. Repeatable hacks to unlock bootloaders no longer occur on Pixels. Anyone might hit the lottery.

Also, discussion of ways to circumvent the carrier's restrictions - especially, but not only when there are already Legal ways to take care of it, such as paying off the device and contacting the carrier in many cases, could get XDA into Legal trouble, and discussions that could get XDA into trouble aren't allowed.
[Google Pixel 7 Pro] Lughnasadh:
Mint Mobile uses T-Mobile network.They were also just recently purchased by T-Mobile.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't know what they are (for particular carriers?) yet, but there is a new April Stable build, AP1A.240405.002.B1, for the P8/P & P7/P/a. The original AP1A.240405.002 still exists.

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 7 Pro] Ghisy:
That's odd... I wonder if it's worth flashing the new 'update' if already on April. 🤔
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'd wait it out. I'm sure eventually it'll be announced or noted on the download pages what the .B1 is. But ya never know! :D
[Google Pixel 7 Pro] samdaman91:
does this impact the ability for mint mobile locked phones to be unlocked?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No.
[Google Pixel 7 Pro] Ghisy:
B1 suggests it might be a regional variant. I'm just gonna wait. I wasn't in a flashing mood today anyway ha!
[Google Pixel 7 Pro] sawdoctor:
interestingly the pixel fold is A2 and the others are B1. Also its only available for the pixel 7 upwards so maybe related to gemini / circle to search or something similar
[Google Pixel 7 Pro] Ghisy:
Hmm, the radio version is higher in this new build:

- OG April update is g5300q-231218-240202-B-11396366

- new April build is g5300q-231218-240404-b-11673025

🤔
[Google Pixel 7 Pro] Fishawy:
Could that be related to the anticipated "satellite connectivity" thing Google announced earlier?
[Google Pixel 7 Pro] Ghisy:
I've seen a few people on Reddit saying they got the OTA for this new update. So it might actually be a new update for the same month.

Hopefully Google will post about it and explain what's new.
[Google Pixel 7 Pro] JakeDHS07:
Same update just a different radio for a different carrier. They just didn't bother to label it this time
[Google Pixel 7 Pro] Ghisy:
How did you find out?

Edit: the previous B1 update was for Japan (Softbank carrier: UQ1A.240205.002.B1, Feb 2024, Softbank). So that would make sense.
[Google Pixel 7 Pro] JakeDHS07:
I had downloaded and compared the included files. But also with that last part being the only difference usually that's a regional thing
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, I've seen a couple of people get the .B1 OTA update and both were in Japan.
[Google Pixel 7 Pro] JakeDHS07:
Yeah think we can comfortably say it was just an unlabeled regional variant
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, this is apparently the response from Google to someone who asked about the 2nd April update:

"We're starting to push an update to Pixel 7 and newer phones. This includes network stability and performance improvements. This update will roll out globally to the regions and carriers impacted over the coming weeks."
[Google Pixel 7 Pro] Ghisy:
It'd be nice if they said which carriers and regions... Talk about being vague!
[Google Pixel 7 Pro] Lughnasadh:
Here's what Verizon says about the B1 update:

"The current software update provides performance improvements for LTE call/data and network issues"

Google Pixel 7 Software Update | Verizon Customer Support

Get instructions on downloading the latest software update for performance improvements to your Pixel 7, including current Android security patches.

www.verizon.com
[Google Pixel 7 Pro] sawdoctor:
Wonder why the pixel fold is a different number, that's A2 rather B
[Google Pixel 7 Pro] roirraW "edor" ehT:
I interpret what they said, and the lack of specific mention of carriers as meaning it's just like any other non-carrier specific "Global" firmware - potential improvements for everyone.

The below, of course, is only a technical explanation in general, and not specific about this example, but still might help or be interesting, anyway. Thanks as always to @Namelesswonder for the original linking, quoting, and explanation.

Post #4 - Build ID definitions
[Google Pixel 7 Pro] Ghisy:
Soooo I ended up flashing that build like an hour ago. We'll see. I'm also using Kirisakura with it, Freak07 said there were no kernel changes apparently.
[Google Pixel 7 Pro] TotallyAnxious:
He said there was no changes to source. It's possible Google didn't release new source for kernel. So not the same as no kernel changes.
[Google Pixel 7 Pro] TonikJDK:
My Google purchased unlocked P7 Pro on Verizon just pulled the B1 update.
[Google Pixel 7 Pro] Ghisy:
Right, he said; "There's no source update as far as I can see." But that was last Thursday and Google usually posts the source earlier than that if I'm not mistaken.

So far, current Kirisakura for April seems fine. 🤞
[Google Pixel 7 Pro] itschaotic:
Anyone updated to a15 (beta released today) and root successfully?
[Google Pixel 7 Pro] Lughnasadh:
Yes and yes (Magisk Canary 27001). The A15 Beta thread is here.
[Google Pixel 7 Pro] itschaotic:
Thank you ☺️
[Google Pixel 7 Pro] roirraW "edor" ehT:
15 Beta thread here :) ->

June 18, 2024 AP31.240517.022 Android 15 Beta 3 "Vanilla Ice Cream" - Pixel 7 Pro [Cheetah]

Android 15 Beta program for the Pixel 7 Pro [Cheetah] ⬇️ This is always true when dealing with Betas ⬇️ ⬆️ This is always true when dealing with Betas ⬆️ June 18, 2024: Android 15 Beta 3...

xdaforums.com
[Google Pixel 7 Pro] itschaotic:
I'm sorry
[Google Pixel 7 Pro] roirraW "edor" ehT:
No need to be sorry, sir. I just thought I'd point you to that thread so that nothing gets confused between Stable and Beta release talk. :)