yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
I strongly discourage running Pixelify on Google Pixels....!

Pixelify is there to install certain features (most of these features natively exist on Pixels) on non-Pixel devices. Because of this, installing Pixelify on Pixels have been known to cause all sorts of issues with native features (call screening, hold for me, direct my call, Monet theming, Assistant Quick Phrases, Live Transcribe, as well as others I can't recall). And, even if the module is uninstalled, I know and have helped members deal with issues that remained, even after. The main original branch of Pixelify still modified other things on the Pixel that even if they didn't install any other option from the module other than unlimited storage spoofing, all the problems still remained and a full factory reset was the only thing to set things back to normal with none of the features glitching or having errors. I guess it has something to do with Pixelify sort of enabling certain AndroidOS things that already are enabled on Google Pixels that it makes it redundant and/or stacks commands on top of already existing protocols and causes incompatibilities/issues....

If you are looking for unlimited storage spoofing, there are other modules that only address that spoofing without installing & modifying other aspects of the OS like the main branch of Pixelify does....
[Google Pixel 7 Pro] Homeboy76:
Magisk Beta/Stable Update

Magisk-v26.4

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Magisk Canary Update

app-release (aa6c7c15) (26401)

Sync with public release

Diffs to v26.4

N/A

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] V0latyle:
As a whole, maybe.

I'm using the Google Photos Unlimited Storage mod on my Pixel 5 with great success and zero problems.
[Google Pixel 7 Pro] simplepinoi177:
From Pixelify Magisk module main branch? Or one of the multiple other forks? I've spoken with numerous other Pixel owners who have run into issues just installing that option of the mod...
[Google Pixel 7 Pro] V0latyle:
Now that you mention it...I'm not sure.
[Google Pixel 7 Pro] simplepinoi177:
Hmmmm....so I know the original main branch is developed/created by Kingsman, but that is not exactly how I recall it looking like. If anything, maybe kingsman made a whole other module based off of what he does in Pixelify but separated it for those of us who just one the single feature....

Like I said, this has got to be the 3rd or 4th fork I know of it (I never really checked what the 3rd one is, so for all I know, this is the .zip module the member had attached to his post....I never wanted to go through the trouble of installing an unknown module; especially if the one I have works perfectly as it is and I don't want to mess it up.

In any case, that's my case in point, it might mean one thing (reassuring against what I was warning) if you were running Pixelify main branch without seeing any issues because of it, but as that doesn't look exactly like Pixelify, it might not secure the confidence as it might've if it was the former situation I outlined.
[Google Pixel 7 Pro] V0latyle:
I'm only running the Google Photos mod.
[Google Pixel 7 Pro] arubamon:
@Homeboy76, before I read the entirety of at least your initial post here, I just want to make sure there is no requirement to upgrade to Android 14 in order to root a Pixel 7 (GVU6C) | Panther. I'm currently on 13.0.0 (TQ3A.230901.001.C2, Sep 2023, Verizon, Verizon MVNOs). After ignoring the Android 14 OTA update nag screen for maybe a week or two, it finally gave up. It actually doesn't even let me update to Android 14 in the ROM anymore and says I'm up to date

Including my SGH-i747, the first phone I rooted, along with every device since, I've never had a single one that thermal throttles, at least not noticeably or that I can recall. This device, which does have an unlockable bootloader, lags horribly, even at under 90°F, and it actually got up to 117°F at least once already in the past two months since I've had it, which I believe is very not good. This is the first Google mobile device I've owned, and the first device I've had in about 11 years, since my Galaxy S3, that I didn't buy outright and wasn't able to root and get away from the stock ROM immediately upon receiving it. I think I'm a little off topic; I guess I just wanted to preface this missive with this somewhat relevant information

Again, my question is simply do I have to upgrade from A13 to A14 in order to root my Pixel 7 (GVU6C) | Panther, because I really would really rather. Not because of all the seemingly pretty major issues that I've just seen recently with the first, I think, "stable" update of Android 14, but mainly since there's always functionality that is important to me that no longer is attainable after upgrading to a higher Android version, namely compatibility with Magisk and LSposed modules, and, etc. I wish I would have stayed on Pie on my OnePlus 6T McLaren (A6013). If you, or anyone, got to the end of this, thank you, and if anyone has an answer to my single question in this entire letter, I'd appreciate the information. Thank you in advance

EDIT: Attached screens which are most likely irrelevant to this thread
[Google Pixel 7 Pro] V0latyle:
There is no requirement to update and never has been. Rooting Android 14 is no different from Android 13, 12, even 11 and 10. The 7 series launched with Android 13. The only requirement is that you use a version of Magisk newer than 24.0 for Android 13, and 26.1 for Android 14.
[Google Pixel 7 Pro] arubamon:
Thank you for the prompt reply. You actually read all that already? Sorry about that, I overexplain far too much, I know

As this is my first Pixel, and at least upon first glance, I didn't see any mention of Android 13 in @Homeboy76's very thorough, and I'm sure, extremely helpful instructions, I just wanted to make sure that there isn't a step or two different between these Android versions and I'll end up bricking or otherwise messing up this device, which could very well happen anyway. Similar, I guess, to the apparent fact, according to @roirra"edor"ehT, in his thread November 2, 2023 Update to the October 29 storage issue - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet, that "On the Pixel 7/Pro, we use Magisk to patch init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition."

Again, I appreciate your prompt response
[Google Pixel 7 Pro] V0latyle:
Correct, the Pixel 7 and 8 use init_boot, not boot for the Magisk patch. But, that's been the same from Android 13.
[Google Pixel 7 Pro] supermansaga:
Shouldn't the Canary be something like 26303 or 26401? Just thinking out loud. Thanks
[Google Pixel 7 Pro] Lughnasadh:
Latest Canary is 26401.
[Google Pixel 7 Pro] Homeboy76:
Typo corrected, link was correct Magisk Canary 26401.
[Google Pixel 7 Pro] pritchfest:
Um, is OP missing something here?

"Navigate to the Google OTA.zip file"

Did he mean to say that I need to extract the OTA file AND THEN "Navigate to the init_boot.img file" (instead of saying "Navigate to the Google OTA.zip file"), or is he talking about patching something other than the init_boot.img file here? Pretty sure I'm supposed to be patching the init_boot.img file here, correct?

Can anyone please advise whether I am misunderstanding OP, or whether OP made some typo's in the post?

Thanks.

*Edit: I've rooted my Pixel 3 XL with Magisk several times before but that was years ago. Trying to make sure I don't mess something up on my 7 pro as I am trying to remember how to do all this again.
[Google Pixel 7 Pro] Homeboy76:
No, he did not "mean to say that I need to extract the OTA file AND THEN "Navigate to the init_boot.img file" (instead of saying "Navigate to the Google OTA.zip file"), "

Magisk will extract the init_boot.img from the OTA.zip file and patch it.

No he "is not talking about patching something other than the init_boot.img file here? :-)
[Google Pixel 7 Pro] pritchfest:
Roger that. Just verified I am now rooted. Thanks!

Regarding the safetyNet fix guide section, I am not getting an option to set the update channel to Canary (I can only choose Stabe, Beta, or Custom).

Any idea what I missed? :unsure:
[Google Pixel 7 Pro] Homeboy76:
What version of Magisk are you using?
[Google Pixel 7 Pro] Dragon1212:
I used the canary manual download the was kindly linked above to get on canary, but i have it working on stable using the 1.3 version of safetyfix 2.4.0 mod.
[Google Pixel 7 Pro] simplepinoi177:
If you update to Android 14, be sure not to employ multiple profiles -- at least for the time being. There is a weird, and somewhat serious bug (serious because it causes a full wipe irretrievably) about updating it and finding bootloop/soft-brick due to it; I know it started being reported on Pixel 6, but has since spread to other Pixels. That is the only caveat for updating to Android 14 that I know to be aware for.

On the bright side, many/most users say updating has improved their battery life -- I don't know about that myself, but I did notice that on Android 13 the screen hz remained at peak (whether 60hz or 120hz depending on my setting), but now on Android 14 it rests at 10hz and sometimes pops up to 30hz for a split second before going back down to 10hz. So I imagine if Google worked on things like that, it is indicative of why battery life has improved.

There was an issue with LSPosed and Android 14 initially, but all is well now and Magisk and LSPosed now work properly with Android 14 and I think many/most modules do as well.

You speaking on thermal issues, if you do plan on employing a custom kernel -- which should help and improve things like that (cpu frequency, max/min thermal limit, etc.), be sure to disable verity & verification if/as you unlock the bootloader -- it will save you another wipe. Then, you will have to be sure to disable verity & verification every time you update or flash the firmware or you will lose it and have to wipe the device when disabling them again.

*Note, I've heard news that many/most custom kernels no longer have this requirement, but I'm not up to date with custom kernel development (because I don't employ it; I know I'd forget every month) so I just put this in just in case it is not outdated or wrong as it could possibly be....
[Google Pixel 7 Pro] arubamon:
Thank you for your detailed reply; I appreciate that. I did read notice articles involving the multiple profile issue; no idea why Google doesn't resolve issues such as this prior to releasing supposedly stable releases. I also noticed multiple articles regarding issues of high battery drain and increased battery temperatures, which leads me to believe that my current issues will not be improved, as again, I've never had a phone in my life that increased to over 110°F when not doing anything CPU intensive nor have I ever had a phone that throttled the battery based on temperature and won't eve charge it depending on the current battery temperature. I just know that every time I update to a new version of Android, there are multiple modules, either Magisk or LSposed that I find very useful that no longer are compatible with the newer versions, and I wish I had just remained with a previous version of Android for this reason alone. I stayed on Pie on my OnePlus 16 McLaren (A6013) for like two years because of this before upgrading to Android 12 and wish I would have just remained on Pie. Oh well, thank you again for your reply
[Google Pixel 7 Pro] Homeboy76:
SafetyNet Fix

Google has made some changes that caused a SafetyNet Fix problem: Displax's SafetyNet Fix 2.4.0-MOD_1.3 is not passing Device Integrity.

Use chiteroman's

Play Integrity Fix - Latest version
[Google Pixel 7 Pro] re_endymion:
Strange, after latest November update, Displax's SafetyNet Fix 2.4.0-MOD_1.3 works for me. YASNAC show Basic Integrity
[Google Pixel 7 Pro] Homeboy76:
Great! You have one of the, exception, Pixel 8 Pro phone. :-) Just kidding. Several XDA Members have posted, on several different threads, they are not passing SafetyNet - Device Integrity with Displax's SafetyNet Fix 2.4.0-MOD_1.3.
[Google Pixel 7 Pro] re_endymion:
You're right Homeboy76. I've done a second check but with the PlayIntegrityAPI Check App in place of YASNAC, and I've the same result that you.

So how is right ? YASNAC or PlayIntegrityAPI Check ?

In Playstore, my device still appear to be certified!
[Google Pixel 7 Pro] straumli:
Do you install this in Magisk or SuperSU? I tried magisk and it slows down my phone to a crawl, unable to open any apps
[Google Pixel 7 Pro] Homeboy76:
Please read the OP in the Play Integrity Fix thread. If you do not find an answer post your question in that thread.
[Google Pixel 7 Pro] Homeboy76:
I think PlayIntegrityAPI Check is right. You can confirm my assumption or refute it by using Google pay.

If it works YASNAC is right, I am wrong.

Sorry for the late response.
[Google Pixel 7 Pro] TheRomRooster:
Did safetynet get updated? Since today in the morning India Time im getting a safetynet error in Google Wallet however, all safetynet checkers say my status is passed
[Google Pixel 7 Pro] Homeboy76:
See post #753
[Google Pixel 7 Pro] TheRomRooster:
thx bro, looks like it work
[Google Pixel 7 Pro] en11gma:
i have an s21 ultra on tmobile that has been paid off for about 8 months. i been waiting for a good phone to get released. probably be the s24 ultra or the next iphone (to use as my main phone with cellular service).

i been thinking about grabbing a pixel 7 just so i can have root and not use with cellular networks (only on wifi).

do i have to worry about anything like being caught rooted with a google play account?

i would really just like to install a full linux OS on it and not even use it like a phone but more like a kickass raspberry pi or something.

can anyone add some input on this?

thanks for any help you can add.

ive never owned a pixel device. long time samsung owner. think i had a Nexus 5X one time but that was many years ago.
[Google Pixel 7 Pro] HippoMan:
I'm wanting my Pixel 7 Pro to run Android 13 instead of Android 14. If I replace "14" with "13" in all of your instructions in the OP, will all those instructions still be valid?

Or are there differences between A13 and A14 that I would need to take into account?

Thank you very much.

PS: This cheetah device is currently running the crDroid 9.8 ROM (A13) and Magisk Delta 26301, in case any that info makes any difference.
[Google Pixel 7 Pro] Homeboy76:
The only way to run Android 13 on the Pixel 7 Pro, with the latest security patches, is with a Custom ROM. If you choose to install a Custom ROM follow the instructions of the Custom ROM you choose to install.

There are differences between Android 13 and Android 14. The most significant difference to me are the updated security patches.
[Google Pixel 7 Pro] HippoMan:
The Android Flash Tool offers both Android 13 and Android 14 for the Pixel 7 Pro. And when I originally purchased my Pixel 7 Pro a couple months ago, it came with Android 13.

Are you perhaps thinking of a different Pixel?

PS: And I have been able to download an A13 factory ROM image and an A13 factory OTA image for cheetah.
[Google Pixel 7 Pro] Lughnasadh:
Yes, you can run stock A13 on this device. You'll want to clean flash though. You can use Android Flash Tool, Pixel Flasher, flash the factory image via flash-all or sideload the Full OTA. Not sure what build or OS you have on your inactive slot so may be best to flash it to both slots.
[Google Pixel 7 Pro] Homeboy76:
@HippoMan @Lughnasadh

Opps, I left this out:

The only way to run Android 13 on the Pixel 7 Pro,

with the latest security patches

, is with a Custom ROM. If you choose to install a Custom ROM follow the instructions of the Custom ROM you choose to install.

True, the Android Flash Tool will flash Android 13 and Android 14.

Yes, you can download Android 13 factory and OTA images, abd flash them.

However, If you want the latest security patches for Android 13 you will have to install an Android 13 (not stock) Custom ROM.
[Google Pixel 7 Pro] HippoMan:
Oh, I see. Thank you for explaining.

Well, I don't want the latest security patches. I have another A13 phone (a Nothing 2), and I'm happy with its level of security. And with my current cheetah phone on which I installed the A13 crDroid version that I mentioned above, I'm also happy with the level of security.

I've been managing my own security on rooted Android devices for more than 12 years, and I can do it in manners that are much better suited to the ways I want to use my device than what Google offers. Whenever Google has released a newer Android version lately (since maybe A11), the behavior of the device gets more annoying to deal with ... at least by my standards.

So ... if I follow your extensive and complete instructions in the OP of this thread, but if I do so with an A13 factory ROM instead of A14, would any of the steps in your installation instructions have to be different?

Thank you very much.
[Google Pixel 7 Pro] Homeboy76:
@HippoMan

AFAIK, no, thanks for asking.
[Google Pixel 7 Pro] HippoMan:
Thank you! That's good news!
[Google Pixel 7 Pro] krkhaha:
Hi. Which version of Magisk is recommended for Pixel 7 pro stock ROM?

A14 stable release.
[Google Pixel 7 Pro] Homeboy76:
Magisk 26.4 Stable
[Google Pixel 7 Pro] meili_33:
Has anyone got the older Zygote-x64_32 to work with Android 14 on the Pixel 7? I have a 32bit app that I really need to be able to use but I keep getting stuck in a boot loop after trying to flash the older custom init_boot to each slot and both slots.
[Google Pixel 7 Pro] Homeboy76:
¯\_(ツ)_/¯

Google seems to have disabled support for 32-bit apps on the Pixel 7

General [Magisk] Magisk Zygote64_32: Enabling 32-bit Support For Apps

The support matrix is as follows:

Phone + SoC, Build​

SoC AArch32 Support​

Zygote Property​

Multilib​

32-bit Support?​

Pixel 6 with Tensor​

Yes​

Zygote64_32​

Yes​

Native​

Pixel 6 with Tensor, 64-bit Only Build​

Yes​

Zygote64​

No​

Not Possible*​

Pixel 7 with Tensor G2​

Yes​

Zygote64​

Yes​

With Modification​

Pixel 7 with Tensor G2, 64-bit Only Build**​

Yes​

Zygote64​

No​

Not Possible*​

Phone with AArch64-only ARMv9-A​

No​

Zygote64​

No​

Not Possible***​

* If no multilib build is also available. It may be possible with extensive work to use Treble to bring 32-bit libraries forward, assuming Android 14+ doesn't remove AArch32 and Zygote32. Emulation could be a possibility but has not been done yet.​

** Build does not exist yet. It may be realized with a QPR build or it may be done with Android 14 instead.​

*** Emulation could be a possibility but has not been done yet. Currently just the Pixel 6 and 7 have KVM built-in, but the Pixel 7 is the only one with it on by default.​

This means that with the right changes 32-bit support can be enabled and used if 32-bit libraries are on the device and the SoC supports AArch32.
[Google Pixel 7 Pro] wangdaning:
I am guessing the only way this will work going forward is if someone gets an emulator going to run the apps. Depending on the app in question, it might be useful.
[Google Pixel 7 Pro] Homeboy76:
Just to be clear, are you referring to getting Zygote-x64_32 to work with Android 14 on the Pixel 7?
[Google Pixel 7 Pro] wangdaning:
Just getting x32 apps to work. I am pretty sure google will shut it down, so my guess is an app will be needed to emulate it.
[Google Pixel 7 Pro] Navalon:
Hello friends

I was flashing the last OTA with pixelflasher like always, but when the process has finished and the "G" with the bar appears the phone restart...

The version of pixelflasher is 5.8.0.0

I have patch the OTA with magisk and after that I have selected the image and "flash pixel phone"

Any idea?
[Google Pixel 7 Pro] badabing2003:
Sounds like you have kept modules enabled and some are not playing nice.

You can follow this to fix a bad modules issue.

GitHub - badabing2005/Magisk: Special Magisk with modules loading disabled.

Special Magisk with modules loading disabled. Contribute to badabing2005/Magisk development by creating an account on GitHub.

github.com

After that if you still have issues, please submit support file so that I can take a look, but do so in PF thread to keep this thread PF noise free.
[Google Pixel 7 Pro] Homeboy76:
Yes, it is alright if you use the stable version of the Magisk app.

Usually, when people write about changing their Magisk app version. They explain why they are changing it. If the explanation they provide is not something you

need

to do.

"If it ain't broke don't fix it"

The instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 6. Set Magisk App Update Channel/Update Magisk, •

Set Magisk App Update Channel

is the easiest way to change versions of the Magisk app.

If you lose root after changing the Magisk app version: Patch the init_boot.img with the new magisk app and flash it.

fastboot flash init_boot magisk_patched...img
[Google Pixel 7 Pro] Elastep:
Guys, I've reset my phone to stock and relocked the bootloader. Now getting this.. How do I reset everything back? Or am I fully bricked now?
[Google Pixel 7 Pro] jejemc:
hi no i don't think flash it via google flasher and its should be fine

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

developers.google.com
[Google Pixel 7 Pro] Elastep:
My bootloader is locked…

Device Unlock Disabled​

For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

That's what the Google Flasher tells me...
[Google Pixel 7 Pro] Lughnasadh:
Try sideloading the full OTA image.
[Google Pixel 7 Pro] Elastep:
FAILED (remote: 'flashing unlock is not allowed')

fastboot: error: Command failed

When I try to unloack the bootloader :(
[Google Pixel 7 Pro] Elastep:
I can't boot into recovery :(
[Google Pixel 7 Pro] Lughnasadh:
Then you are probably out of luck. Try to RMA if you can.
[Google Pixel 7 Pro] jejemc:
not possible to have access to fastboot mode to re unlock the bootloader?
[Google Pixel 7 Pro] Elastep:
FAILED (remote: 'flashing unlock is not allowed')

fastboot: error: Command failed
[Google Pixel 7 Pro] Elastep:
How do I switch to another system image? We have 2, right? I've flashed only the first one.. Thanks
[Google Pixel 7 Pro] EtherealRemnant:
fastboot getvar current-slot

fastboot --set-active=a or b (whichever isn't currently active)

It is unlikely to work though. You clearly had something modified that shouldn't have been.
[Google Pixel 7 Pro] Elastep:
FAILED (remote: 'command (set_active:) is not allowed when locked')

No luck :)

Google said that the fix is going to be free.. Will try some local Asurion guys first, but I doubt. Then probably will have to send it to google...
[Google Pixel 7 Pro] Lughnasadh:
You can't switch slots with a locked bootloader.

EDIT: Ah, see you found that out. Glad you can RMA it.
[Google Pixel 7 Pro] EtherealRemnant:
Well it's good that Google is going to take care of you. You must have bought it directly from the Google Store. I've heard nothing but problems for people trying to get warranty service that bought it anywhere else (which means it's a good thing that I only keep my phone for a year as I bought it from Best Buy).
[Google Pixel 7 Pro] Elastep:
Yes, bought it from Google Store directly...

Never had a phone before (and I had a lot of phones) that I could not somehow reset to factory. settings...

This is clearly some underthought.