yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] inpowers:
HI simplepinoi77

I think i might just have to take you up on that offer in regards to the permanent fix.

Would be much apricated merry Christmas

Thank you
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release (65207f96) (26404)

Magisk (65207f96) (26404)

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[Reset Prop] Add new wait for property feature

resetprop -w

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on

devices with small boot partitions

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] rczrider:
Why is Play Integrity Fork recommended over the the SafetyNet Fix 2.4.0 MOD 2.0 from Displax? According to YASNAC, Play Integrity Fork (including the latest 5.0 version) only passes Basic Integrity, but fails CTS Profile Match. The SafetyNet Fix MOD passes both.

Not arguing, just want to better understand the differences.

EDIT: literally just saw this post 2 above mine, but it doesn't really explain why SNF works (despite being deprecated) and Play Integrity Fork doesn't. Or, rather, I missed the explanation.

EDIT 2: Play Integrity Fix 15.1 works where Fork does not. Again not sure why the Fork variant is recommended over alternatives.
[Google Pixel 7 Pro] Fishawy:
SafetyNet Displax MOD and YASNAC are both deprecated (The former fails integrity, and the latter is no longer relevant since Google shifted from SafetyNet to Integrity).

PIF 15.1 has an embedded fingerprint that is still not banned yet. The dev chiteroman will not included an embedded fingerprint anymore after this one gets banned.

PlayIntegrityFork requies you to get and use your own private fingerprint. All releases up until v5 never include a generic one. The reason why the fork is recommended is to stay away from mass use which triggers Google into mass bans, and slow down the ban cycle in the process. Less users, less alarms, less bans.
[Google Pixel 7 Pro] kenzolo:
edit
[Google Pixel 7 Pro] jova33:
Question, sorry if it's been asked before,

Is it possible to be rooted, no TWRP, accept the OTA update, and then root the update before restarting?

I'm new to this device, and know it's been possible to do on some phones, but then the phone I came from the only way to update was to hook it up to a computer, unroot, update, reroot.

Also, OP needs to be updated, as extracting the factory image now involves payload dumper.
[Google Pixel 7 Pro] Slim2none4u:
No and you do not need payload dumper to extract the factory image but you do for the factory ota. Thats the difference. Factory Image = no payload dumper, Full OTA = payload dumper needed.

The easiest and safest way is to use PixelFlash with the factory OTA image. scan, patch, flash twice to make both slots bootable.

You can try to take the OTA. Magisk, uninstall, restore images. Take OTA and let it install. Do not reboot. Go to magisk, install to inactive slot. Reboot.
[Google Pixel 7 Pro] Homeboy76:
@Slim2none4u beat me to the punch. :ROFLMAO:

install Magisk to the inactive slot
[Google Pixel 7 Pro] jova33:
With this method, how would I restore the non-patched init_boot.img?

I know there's an option in magisk to do so, but if magisk doesn't know where the unpatched init_boot.img file is, it won't uninstall.
[Google Pixel 7 Pro] Homeboy76:
Magisk knows where the unpatched init_boot.img is, it remembers the location of the init_boot.img it patched. :)

To unroot open Magisk => tap Uninstall => tap Restore images.
[Google Pixel 7 Pro] jake.99x3:
I am on the August version of CrDroid android 13 and am looking to upgrade with a fresh install of 14. To keep things simple, would it work using the pixel recovery site: https://pixelrepair.withgoogle.com/ and then repeat step 2 to re-root? Not concerned about losing data
[Google Pixel 7 Pro] simplepinoi177:
Yes, I imagine all of that should/would work.

Good idea using the official tools, either that one or Android Flash Tool should do. I'm glad you aren't concerned about losing data, as I imagine all instances of going from custom ROM to stock requires a wipe.....
[Google Pixel 7 Pro] bahriphonewala:
Google pixel 7 root done but how can enable diag port ?

below commends not work:

adb shell

su

resetprop ro.bootmode usbradio

resetprop ro.build.type userdebug

setprop sys.usb.config diag,diag_mdm,adb

diag_mdlog
[Google Pixel 7 Pro] weriwd:
This safety bet pass drives me crazy as I'm traveling and all of a sudden a can nit pay with my device... I'm currently running dec official pixel 7pro software and not passing device integrity with neither play integrity or play integrity fork.
[Google Pixel 7 Pro] simplepinoi177:
It's because none of these Play Integrity Fixes modules work "out of the box".....you are required now to implement your own custom fingerprint.

As you are traveling and you need something immediately & urgently, PM me and I can get you up and working in a matter of minutes....
[Google Pixel 7 Pro] DragonChasm:
Dunno if this has already been mentioned but does Whatsapp stops working on Pixel after root? I'm trying to activate it but it keeps saying that it cant send sms or call on the number. Have hidden magisk and also added whatsapp in deny list but cant seem to make whatsapp work. Is there any workaround?
[Google Pixel 7 Pro] JohnTheFarm3r:
No, it doesn't. Works fine with root. The issue must be something else.
[Google Pixel 7 Pro] simplepinoi177:
Maybe need something more like passing MEETS_DEVICE_INTEGRITY (if you are not achieving that), or something extra like Magisk Delta or Kitsune, using Shamiko or HMA, and the like?
[Google Pixel 7 Pro] BunnyPig1:
WhatsApp doesn't care about root. Been using it for years now with root. Even when I couldn't pass DEVICE integrity.
[Google Pixel 7 Pro] DragonChasm:
So I did the safetynet patch and this is what is showing currently. Is this correct? I see meets_basic_integrity but not the 'device integrity'. I also installed Shamiko but its says it doesn't work cozuse denylist is enabled. I have added whatsapp and all google apps in the denylist but still dont receive the sms or the call.
[Google Pixel 7 Pro] DragonChasm:
This is what it was showing in Whatsapp before hiding it in magisk. After hiding it simply says to try again but the resend sms option is always disabled.
[Google Pixel 7 Pro] simplepinoi177:
based off what these members said below...

...I'm not confident that it's having root that's the problem nor do you need to pass MEET_DEVICE_INTEGRITY.

But just to address what you've said and tried, as you are only showing MEETS_BASIC_INTEGRITY, under normal circumstances (for Wallet, Netflix, Turo, etc.) that would mean what you are doing is not enough. Also, you mentioning SafetyNetFix means you are using the wrong thing -- SafetyNet is depreciated and hardly applicable any longer and, as such, SafetyNetFix is no longer enough/viable. You need Play Integrity Fix.

Shamiko is a good (if not the best) root-hiding module, but it isn't as good as Play Integrity Fix as that assist not only with root-hiding (to a degree), but unlocked-bootloader-hiding.
[Google Pixel 7 Pro] DragonChasm:
ok I got confused and used 'safetynet' as 'playintegrity fix' interchangeably. I'll try redoing play integrity fix again.
[Google Pixel 7 Pro] BunnyPig1:
Odd. WhatsApp could've released an update I'm not aware of recently that actually check for DEVICE integrity. But do you have a custom rom installed or using a different kernel?

It's been popping up weird things about custom kernels lately.
[Google Pixel 7 Pro] simplepinoi177:
Yes, this is true. The established way of "tricking" Google that the phone isn't rooted (and to a degree has a locked bootloader) has hit some issues with Google now identifying some custom ROMs and custom kernels and outright failing/not-passing them.

But, as established previously, it doesn't look like WhatsApp even requires passing such a check (DEVICE)...so it's doubtful, even if getting it to pass, that would resolve the issue...
[Google Pixel 7 Pro] DragonChasm:
Sorry for taking this long to reply. I was not using any custom rom or kernel. This whole thing started with battery drainage spike after the latest "security" update for android. I raised this concern with the google tech support team and they told me my warranty has expired (last week) and that to get the phone repaired even though its not a hardware issue. My battery had started draining like crazy, coneveniently just few days after warranty expired, it used to fell almost 5% in mere few minutes on idle. I then decided to root my phone and put stock android nothing fancy. Came across this thread and rooted the phone. Worked fine except for Whatsapp. No matter what, it just would not receive sms or callback for reactivation. Was surprised to see that error msg I attached earlier.. 'whatsapp wont work on root'. As of now I have un-rooted my phone coz tbh its too much of a hassle and lil to no rewards. Rooting the phone used to be much easier and had many merits but now one has to go through soooo many hoops and half the stuff doesn't work. My battery is working fine now btw.
[Google Pixel 7 Pro] DragonChasm:
I dont exactly know why whatsapp wouldnt work on my phone but even after multiple tries it would not start so I just unrooted my phone. This is too much work for over nothing in return.
[Google Pixel 7 Pro] simplepinoi177:
that's a shame considering there was so many members/users here that said they run it rooted....

but i guess congrats on getting it up and running!
[Google Pixel 7 Pro] BunnyPig1:
I understand.

As long as you got it working and don't feel the need for root it's perfectly fine running am unrooted phone.

In case you find the time and energy to give it another try we'll be here to help. Glad you found a solution at least!
[Google Pixel 7 Pro] missionman:
If anyone can help me here. Please?

I have a Pixel 7 Pro, bootloader unlocked, rooted with magisk and i have LSposed on it too. I have safetynet installed and the device fingerprint is still OEM. I had a denylist going on default google apps (like 4) and a couple of games.

I opened my ADB AppControl on windows and I decided to uninstall my google messages and google phone apps again and replace them with private phone and messaging apps on F-Droid app, however I ALSO stupidly decided to reinstall/enable a couple of Verizon based apps I had previously removed in the past to see if it would now fix my ongoing hotspot issue since leaving Visible for US Mobile last week.

As soon as I did this I rebooted the phone, and it boots up, shows a new G logo color unlike the color i had set, and it crashes after showing the lock screen for 1 second, then goes into recovery mode saying “Cannot load Android System. Your data may be corrupt...” see photo below..

I have all my root progress saved in a backup folder when I first rooted and finished. I used this tutorial here to unlock bootloader and root. I still have my factory init_boot files (the one thats 8mb too) & safetynet file and the 2 different OTA files and other root image files and so forth. I have everything i needed to get bootloader unlocked, rooted and magisk and all that.

Can i save my phone? I was about to sideload the stock OTA image from Google (May 2023 image) to save myself from losing data, but I don't know if this is wrong. What do i do? I came here before I did anything dumb. Can I sideload or restore the image without wiping it?

If so how?

My Pixel 7 Pro is carrier unlocked. It works on Verizon or T-mobile if that helps.

HELP PLEASE!
[Google Pixel 7 Pro] DragonChasm:
Thank you!
[Google Pixel 7 Pro] Slim2none4u:
Just flash stock
[Google Pixel 7 Pro] missionman:
will I lose data flashing stock ota? my only concern is not losing photos, notes and videos.
[Google Pixel 7 Pro] missionman:
How do go about flashing stock? Do I use abd platform tools to side load it by applying update from ADB? or do I use Odin, Android flash tool or droidkit?

Any help appreciated greatly.
[Google Pixel 7 Pro] Slim2none4u:
Honestly your answer is in the OP but......

I would use PF

📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...

xdaforums.com

Read the whole OP first.

Its an awesome tool!

Download the factory image, not the ota.

Personaly I would wipe but may not need to unless you issue persists
[Google Pixel 7 Pro] missionman:
oh yes I remember now. I used pixel flasher in the beginning to root and unlock bootloader I believe, using this tutorial. It was flawless and took minutes to do.

Thank you Slim2none4u. I really appreciate the guidance.

I will grab my factory image and flash after refreshing myself on OP for pixel flasher. If that don't work I'll have to wipe.
[Google Pixel 7 Pro] missionman:
Im kinda stuck on what mode my phone should be in to attempt this factory flash on pixel flasher. My phone wont do anything unless i force it into recovery or fastboot or whatever mode i need to be in. Does anyone know? My issue is im trying to save my data and i had a "cant load android system. Your data may be corrupt" error. Im rooted and bootloader i unlocked but i dont know wht mode i should put the phone into. It requires it, actually since it just sits on "retry" or "wipe factory data reset".
[Google Pixel 7 Pro] missionman:
i selected apply update from adb and i brouse for the factory image, I process it and pixel flasher instanly freezes for like 10 seconds and then finshes with an abort, see below... (am i in the wrong boot mode or do i need another init.boot file?

ALSO, i cant seem to disable modules or acesss anything Magisk wise. I hear this will mess with flashing...

==============================================================================

2024-02-05 02:13:12 User initiated Process firmware

==============================================================================

==============================================================================

2024-02-05 02:13:12 PixelFlasher 6.7.1.0 Processing firmware file ...

==============================================================================

Low memory option: False

Available Free Memory: 1.44 GB / 5.90 GB

Factory File: C:\Users\PWNing YOU softly\Desktop\cheetah-tq2a.230505.002-factory-fe44ced0.zip

Failed to check_zip_contains_file_fast. Reason:

Traceback (most recent call last):

File "runtime.py", line 1330, in check_zip_contains_file_fast

File "zipfile.py", line 941, in read

File "zipfile.py", line 1025, in _read1

File "zipfile.py", line 1055, in _read2

File "zipfile.py", line 775, in read

MemoryError

Failed to check_zip_contains_file_fast. Reason:

Traceback (most recent call last):

File "runtime.py", line 1330, in check_zip_contains_file_fast

File "zipfile.py", line 941, in read

File "zipfile.py", line 1025, in _read1

File "zipfile.py", line 1055, in _read2

File "zipfile.py", line 775, in read

MemoryError

Failed to check_zip_contains_file_fast. Reason:

Traceback (most recent call last):

File "runtime.py", line 1330, in check_zip_contains_file_fast

File "zipfile.py", line 941, in read

File "zipfile.py", line 1025, in _read1

File "zipfile.py", line 1055, in _read2

File "zipfile.py", line 775, in read

MemoryError

Detected Pixel firmware

7-Zip 23.01 (x64) : Copyright (c) 1999-2023 Igor Pavlov : 2023-06-20

Scanning the drive for archives:

1 file, 2750491221 bytes (2624 MiB)

Extracting archive: C:\Users\PWNing YOU softly\Desktop\cheetah-tq2a.230505.002-factory-fe44ced0.zip

--

Path = C:\Users\PWNing YOU softly\Desktop\cheetah-tq2a.230505.002-factory-fe44ced0.zip

Type = zip

Physical Size = 2750491221

Everything is Ok

Folders: 1

Files: 6

Size: 2767090478

Compressed: 2750491221

Nothing to extract from firmware

Aborting ...
[Google Pixel 7 Pro] badabing2003:
What Veriszon based apps you reinstalled / enabled?

What color you had set? how,

Your problem is that you don't have enough memory

Please create a support file in PixelFlasher and provide that.

It might tell us few things about the state of your device, but I'm afraid it won't tell us anything about what you did and how you caused data corruption.

Every little detail of the exact steps and their respective outcomes are crucial to properly diagnose your issue.
[Google Pixel 7 Pro] missionman:
It happened right after I reinstalled a sim toolkit apk, my Verizon services apk, mmsservices apk, com.verizon.llkagent v.13 apk, carrier provisioning service apk and carrier services.

All an attempt to get my hotspot working. I think the carrier services and provisioning service and Verizon apks caused the crash and data corruption.

all I need to know is what state my phone has to be in for flashing the factory image? I have to manually do this as my phone is not able to be controlled by pixel flasher without manual boot mode control. I'm not sure what mode I need to be in to flash factory image. so far I been trying to apply update using ADB but it errors and says nothing to extract from firmware.
[Google Pixel 7 Pro] badabing2003:
I suppose you didn't read the post above yours, directed at you.
[Google Pixel 7 Pro] missionman:
I had been talking to Slim2none4u on this matter. I been here recieving help because I flashed from this OP. prior to this error.

Waiting to see if he can get back to me.
[Google Pixel 7 Pro] Slim2none4u:
badabing2003 knows way more than me and you should do EXACTLY as he asks if you want to fix your phone.​
[Google Pixel 7 Pro] missionman:
Ok sorry I didn't see this post as someone pointed out to me. thank you for the direction.
[Google Pixel 7 Pro] ohap:
instructions need to be updated , use https://github.com/chiteroman/PlayIntegrityFix/releases instead of one in op post , this will pass safetynet
[Google Pixel 7 Pro] Slim2none4u:
osm0sis PIF fork v7 works also! This is false info!​
[Google Pixel 7 Pro] ohap:
it would fail csc for me on mine with PlayIntegrityFork-v7.zip osm0sis , PlayIntegrityFix_v15.9.3.zip passed safetynet for me no issues . guess diffrent strokes for diffrent fokes . "no LIES! lol "
[Google Pixel 7 Pro] badabing2003:
@Slim2none4u is right, if you can pass with chit's 15.9.3 you can pass with @osm0sis fork too.

You haven't followed the instructions and set it up properly.

15.9.3 bundles xiaomi.eu print, which today is passing.

Did you set up the custom print with the fork module?

It intentionally does not bundle any print, you have to supply it.

And the guide tells you what to do.
[Google Pixel 7 Pro] ohap:
i followed all this ""

Download File(s)

Play Integrity Fix - Latest version

Magisk Module repositories:

Androidacy Module Manager

Androidacy Module Manager - Releases

Androidacy Download Center

Install osm0sis PlayIntegrityFork

Open Magisk

Tap Modules icon

Tap Install from storage

Navigate to the osm0sis Play Integrity Fix file you downloaded.

Tap the osm0sis Play Integrity Fix file.

When you see the confirmation screen, tap Ok. installation.

After it installs tap the Disc icon to save the log

Tap Reboot

Settings for Magisk

Open Magisk App

Tap the Setup icon.

Scroll down to App and set the

Update Channel

to Canary.

Scroll down to Check Updates and

enable

it.

Scroll down to Magisk and enable

Zygisk

.

Enable Denylist

Tap

Configure DenyList

=> Tap 3 Dot Menu => Check ✓

Show system apps

=> Check ✓ Google Play Store, Google Pay, Google Wallet etc.

(Optional) Scroll down to Superuser and enable

Enable Biometric Authentication

.

Get Device Certified

Flash the osm0sis PlayIntegrityFork module in Magisk

Turn Airplane mode on

Open Settings

Tap Apps & notifications

Tap see all...

Tap three dot menu

Tap Show system

Scroll to

Google Wallet/Play Store/Play Services

Clear Google Wallet cache (if you have it)

Clear Google Play Store cache and data

Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)

Turn Airplane mode Off

Reboot

Check Device Certification

Note: If after completeting Get Device Certified your device is

not

certifed or your device

is

certified but

certain apps (Google Pay, NetFliks, etc.)

are not working. Do this to verify you are passing Play Integrity.

Open Google Play Store app

Tap your profile icon (top right corner)

Tap Settings.

Open the About menu

Tap the row labeled Play Store version seven times to unlock developer mode.

Tap the back arrow (upper left corner)

Tap your profile icon (top right corner)

Tap Settings.

Open the General menu

Tap Developer options

Tap Check integrity

If you see Basic Integrity and Device Integrity, you're passing Play integrity.""

i dont see anywhere where is says change the device fingerprint
[Google Pixel 7 Pro] badabing2003:
@ohap

It's in the fork's guide, where you managed to figure out where to download from.
[Google Pixel 7 Pro] ohap:
that explains it then lol i didnt read that at all lol , but ya changing fingerprint would fix osm0sis, i will go read it even tho its passing now . theres many ways to pass csc i uses to use MagiskHide Props Config also to pass
[Google Pixel 7 Pro] badabing2003:
CSC is not really relevant anymore, it's Play Integrity that matters now.

And there aren't many ways left to pass that unfortunately.
[Google Pixel 7 Pro] ohap:
i been out of this for a bit , what issues you have if you fail meets strong integrity ? i dont use any google pay or walet , and all my bank apps are working
[Google Pixel 7 Pro] Slim2none4u:
Strong is locking the bootloader which you clearly can't do.
[Google Pixel 7 Pro] ohap:
i seen strong pass with unlocked bootloader

https://www.reddit.com/r/Magisk/comments/15bxqmi
[Google Pixel 7 Pro] BunnyPig1:
In the beginning it used to pass strong integrity, but this was because of a loophole that has been patched. From my understanding Chiteroman has found a way to spoof strong in a weird way, I don't have the knowledge to explain but it has something to do with broken TEE on a specific phone (again, could be way off on this).

But long story short, you will NEVER be able to pass Strong with an unlocked bootloader. If you want more info on this you can head over to PIF FAQ and PIF Thread to learn more.
[Google Pixel 7 Pro] woj.mor.1998:
I have constant problem with Magisk. I've tried installing on stock ROM and aby custom Rom for Pixel 7.

I Simply install any magisk module, everything seems to be fine after reboot but after a few days phone always starts to freeze screen and eventually reboots. After reboot phone works for about 15 seconds and again freeze and reboot... Constantly.

I was able to uninstall magisk and everything works fine but cannot get rid of that crashes. Any suggestions?

Flashed via fastboot init_boot and adb sideload recovery with same results.