yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have links to all of them in the SafetyNet section of Post #2.

My understanding of PlayIntegrityNext (which I'm using) is not to use the actual PINext module, but to use @chiteroman's alongside the other PINext module which installs a FP Downloader app you can use whenever you become decertified again, instead of necessarily installing a new version of a module each time.

Edit: I'll have to check my links later when I'm not on mobile.
[Google Pixel 7 Pro] B00mB00mBang:
Thanks. I meant to say about the pixel 7 pro guide link posted by @Homeboy76

Thread '[Guide] [January 3, 2024] Root Pixel 7 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More' https://xdaforums.com/t/guide-janua...s-safetynet-both-slots-bootable-more.4505353/
[Google Pixel 7 Pro] roirraW "edor" ehT:
Ah! Thanks for the clarification. I'm happy to hear I don't have to troubleshoot any of my OPs after all. :D

I hope my information helps.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Whoohoo! Updated for Android 14, v1.7.2: @Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+
[Google Pixel 7 Pro] roirraW "edor" ehT:
Got this so far.

Android Security Bulletin—January 2024 | Android Open Source Project

source.android.com

Disregard. The February 2024 link goes to January. :D

Edit 2: Here's the right link.

Android Security Bulletin—February 2024 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Feburary 5, 2024

:

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 Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] dimm0k:
anyone confirm Magisk still working good?
[Google Pixel 7 Pro] schmeggy929:
Can confirm with updated Magisk 27.0(27000). Used Pixel Flasher to patch init_boot.img and flash. 276 seconds

with:

Iconify 6.7.0 enabled

VIPER4Android RE 6.1 enabled

AML 5.1 enabled

Font Manager enabled

Systemless Hosts enabled

Play Intergrity Fix 15.5 enabled

Zygisk - LSPosed 1.9.2 enabled
[Google Pixel 7 Pro] bird333:
Hello. I need some current process help. I'm on Magisk 26.4, Iconify 6.6, Pixel Expert 3.1 and I'm on the November build of Android. I want to update to February. First can you backup your Iconify and Pixel Expert settings? If so, how? Second, should I update to Magisk 27 and Iconify 6.7 before I update my system? In particular does Iconify 6.7 work fine with the November build? I do have modified qs panels. I'm guessing I need restore all Iconify settings to default and disable any Magisk modules before I update? Thanks for any guidence.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I use Swift Backup to backup everything, and you definitely want to upgrade Iconify to 6.7 before the firmware, otherwise you may have bootloops. Magisk v27 is Beta. I can't speak personally whether there's a reason to update it anyway. I wait for Stable.

I don't know about backing up Iconify since I don't have it installed at the moment, but yes, you definitely want to update PixelXpert as well. You can click the 3-dot menu in the upper right corner of PixelXpert, choose Import/Export (by Art Vandelay), then choose Export settings to file. I backup to a Google Drive location so that if my phone gets wiped, my settings are still safe, although as I said, I use Swift Backup as well.

I don't know, but if you backup the settings you can just uninstall Iconify until you update the firmware.

It's always wise to disable Magisk Modules before updating, but if you update all Magisk Modules first, you'll likely be okay, depending on what other modules you have installed. I don't have that many.

Good luck!
[Google Pixel 7 Pro] bird333:
Thanks for the response. I don't use Swift Backup because I'm not comfortable with them wanting my info to use it. I've seen somebody mention backing up Iconify but I can't see how unless they do mean through SB. Oh, it looks like Magisk 27.0 might be stable now. Can you just hit the 'update' button safely?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Sorry that I can't give more helpful information regarding Iconify. I'm sure I'll reinstall the new version soon, and then re-figure out if I have a direct backup somehow, or just use Swift Backup.

v27.0 shows as Beta:

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

Normally, yes, you want to update the app first, then you can let it update/direct install the new Magisk to the running init_boot.img.

In the Releases section, Betas look just like Stable ones, so you have to look at the main page to be able to tell which a release is.

I don't even have Magisk set to look for Betas.
[Google Pixel 7 Pro] Fishawy:
Funny you should say that, this happened to me yesterday!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Very strange! I see it offers the update when I manually look in the app, too. I see I didn't have it set to Stable since I got my P8P, I just had it set to the default of nothing selected. I changed it to Stable now. No idea if that'll make a difference in the future.
[Google Pixel 7 Pro] Fishawy:
Yeah, mine is set to stable but still shows the update. Dunno if it's a glitch.

A member suggested it might have something to do with the Magical Overlays module, as it gave them similar problems. I'll try without it when I get home.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't use a Magical Overlays module. I'll have to look that one up.

Edit: Oh, this one?

GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)

Make system partition become read-write (it is also possible without Magisk) - HuskyDG/magic_overlayfs

github.com
[Google Pixel 7 Pro] Fishawy:
@roirraW "edor" ehT All good after removing the Overlayfs module, updated to 27.0 stable and the February release without issues.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks!

@Fishawy and @bird333, now that I think of it, I think maybe at least once before a Magisk version was pushed to Stable and the indicator on the front page at GitHub just wasn't updated, so maybe that's what happened again.
[Google Pixel 7 Pro] Ghisy:
FYI, Magisk v27 went stable yesterday after only 2 days on beta. John Wu tweeted about it.

https://twitter.com/i/web/status/1754438078171869246
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, @Ghisy!

Edit: Got the update prompt in my notifications, updated app fine from there, then updated the init_boot.img through direct install, rebooted after, and all is good. I haven't updated to February yet.
[Google Pixel 7 Pro] otonieru:
It only took 228 seconds to update to February release using Pixel Flasher, with all data, root, magisk & lsposed modules intact and perfectly working.

Also. Kirisakura works with this release as well. Fantastic
[Google Pixel 7 Pro] JoshuaUB78:
Are others still in google play system November?
[Google Pixel 7 Pro] schmeggy929:
No January 1
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've paid no attention except when someone asks. I was on November the last time I checked in the last couple of weeks, but it must've updated to January sometime since. :)
[Google Pixel 7 Pro] TotallyAnxious:
He really needs to leave twitter. At least use a service that lets you see things without having an account.
[Google Pixel 7 Pro] eriks0n:
I've successfully updated to the Feb 2024 security updates.

Root working.

I have installed the Play Integrity Fork v7 by osm0sis and followed instructions but I am passing Basic Integrity but failing CTS Profile match and 'MEETS_DEVICE_INTEGRITY'.

Only modules I have in my latest Canary build of Magisk are systemless hosts and Play Integrity Fork v7. Anything I'm missing? Would love some help. I really want to get my wallet working again and I'm assuming I need CTS profile match to pass for this?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Do you mean not being able to see the comments, anymore? I agree.

You can try:

daboynb's PlayIntegrityNEXT (fork of @chiteroman's)

which, as far as I understand, now instructs you to use the following:

@chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)

but then only install the PlanIntegrityNext FP Downloader module/app (not that actual PINext module).
[Google Pixel 7 Pro] TotallyAnxious:
Among many things but yes it includes this.
[Google Pixel 7 Pro] Fishawy:
Is Kirisakura still including the powerhint module within the kernel?

I'm currently using different powerhint tweaks, and they previously conflicted with Kirisakura's, that's why I'm checking.
[Google Pixel 7 Pro] eriks0n:
Actually, simply switching back to using the original "PlayIntegrityFix_v15.5.zip" solved it!

CTS and device integrity all working now!
[Google Pixel 7 Pro] Ghisy:
Updated to February with root and current Kirisakura! All seems well! 👍
[Google Pixel 7 Pro] otonieru:
Am not sure about the powerhint, but there is definitely an AK3 Helper Module built in into the Kernel Zip.

Are you using the powerhint mod that need a MagiskOverlayFS ? I forgot the dev name, but i recall seeing the thread.

Is it actually better than latest Kiri ? Because i feel that Kiri actually work much better now compared to older iteration, my phone almost never got overheated again, and battery is finally can survive a day.

I do.

But i rather have november than a january with all those ridiculous storage issues. LoL
[Google Pixel 7 Pro] Fishawy:
Yes, the Purgatory one. I've had similar results with both, but recently the MagiskOverlayFS module gave me hell while updating Magisk, so I removed it.

I actually went ahead and flashed Kiri (with the AK3 Helper), all is well.
[Google Pixel 7 Pro] Schroeder09:
Are there any platform tools issues? What version should I use to update to February? I'm on November now.
[Google Pixel 7 Pro] Lughnasadh:
34.0.5 has been working fine for me.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Same here. 34.0.5 has worked fine for me ever since it came out.
[Google Pixel 7 Pro] dcarvil:
I've had problems with fastboot on versions 34.x. Version 33.0.3 still works for me.
[Google Pixel 7 Pro] roirraW "edor" ehT:
34.0.4 and below had issues, including the Fastboot issues - it just took them something like 6-8 months to come out with 34.0.5, and I haven't noticed anyone reporting any issues with it. If a monthly firmware comes out that requires a new version of Fastboot, as they do sometimes, then you should be fine to upgrade.
[Google Pixel 7 Pro] Ghisy:
I can also vouch for v34.0.5. I've been using it for the past few updates without any problem.
[Google Pixel 7 Pro] dcarvil:
I tried 34.0.5 a month ago, and still had "fastboot flash" failure. It worked fine after dropping back to 33.0.3. I'll try it on a different computer when I have time.

Thanks for the info.
[Google Pixel 7 Pro] Lughnasadh:
Google System Release Notes (January & February (partial))​

Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
FYI for future considerations, once QPR3 is closer to going stable (around June 2024):
[Google Pixel 7 Pro] bird333:
Help! I tried to flash February OTA from November with PF. It said it went to 94%. But it got hosed somehow The recovery screen came up with the option to factory reset (this was the February recovery) I tried again to reboot a couple of times which didn't work. So I went to factory reset but I canceled out of it (can't remember why now). When I canceled out the recovery said it was the November one WTF? At that point I think I chose 'try again' and the phone came up and said the phone was corrupt and couldn't be trusted (I think this was the bootloader). Then it just seemed to get stuck with 'GOOGLE' on the screen. I finally got it to turn off by holding the power button. I can't seem to get recovery or rescue mode to work. What now?
[Google Pixel 7 Pro] badabing2003:
See my answer in PF thread here.
[Google Pixel 7 Pro] Schroeder09:
I just disabled all my magisk modules and rebooted. im stuck in a bootloop at the google logo. It will sometimes reboot to the "your device is insecure" message. Then it will hang at the google logo again. I have seen the "your device is corrupt, do you want to try rebooting again or wipe your device?" message a couple times. I've rebooted of course. I have kiri kenel and powerhint module, iconify, lsposed, pixel expert, systemless hosts, and maybe a magisk module or two that I'm forgetting. Is there anyway to re-enable these magisk modules? a "adb devices" command will see the phone. I can't issue commands like "adb reboot loader" though because I can't get in the phone to authorize this PC.

edit: I can go to rescue mode. then in a command prompt when I type "adb devices" the powershell returns the device name with "rescue" by it. I hope there's something I can do here.
[Google Pixel 7 Pro] BunnyPig1:
Try to boot the phone in safe mode. This will disable all Magisk modules and the phone will start in a state where only the basic functions will work.

Power off your device, then boot it normally.

As soon as you see any animation starts, press and hold the volume down button. Keep holding it until the phone boots into safe mode.

The phone will make a different vibration pattern during boot to let you know it's being done properly.

If the phone boots, then it's something installed on the phone making this issue (might be a module causing this like Iconify (some features are still a bit hit and miss)).

Reboot it normally and see if it's working.

This will reset all your modules as well so you have to reconfigure Iconify, pixel xpert etc.
[Google Pixel 7 Pro] Schroeder09:
Thanks for the reply. I've been trying to get it into safemode. I've started holding the volume down button right when the "your bootloader is unlocked and the device can not be trusted" message appears. I have tried not pressing the volume down button until that message passes and the Google logo shows up. The Google logo stays on the screen and doesn't progress past that. It just stays there. It'll stay there for quite a long time (5-10 minutes??), reboot to the "your device has an unlocked bootloader and can't be trusted message," will show the "your device may be corrupted. do you want to reboot again or factory reset" message, and then will go back to the Google logo after I select "try again." What else can I try before wiping the phone. I am terrified of doing that.

@badabing2003 , is this something pixel flasher can help with? The behavior of my p7p seems to be the exact same as what was happening above in post 3641 where you were replying to another user. I am on the november security patch. All I did was disable all modules and reboot. I wonder if disabling the kiri powerhint module has caused this issue??
[Google Pixel 7 Pro] BunnyPig1:
Hm, I'm no expert but it seems something big has happened.

Can you get into fastboot mode?

Either through ADB commands or simply by holding volume up + power button while booting?

If you can, maybe use pixel flasher (or some other way, I find that tool to be the easiest) to push an OTA update to see if it something with your partition that's gone bad.
[Google Pixel 7 Pro] Schroeder09:
yes. I can get into fastboot. I'm looking into pixel flasher now. I just tagged the pixel flasher developer above, and I'm hoping he has some insight.

EDIT: I am trying this pixel flasher thing and here's the message i see in its command prompt so far when starting in fastboot mode via the hard keys on the side of the phone:

Selected Device on 2024-02-11 21:06:04:

Device ID: XXXXXXXXXXXXXX (my personal device number is displayed here)

Device Model: cheetah

Device Active Slot: a

Device Mode: f.b

Has init_boot partition: True

Device Bootloader Version: cloudripper-14.0-10529422

Device Unlocked: True

slot-retry-count:a:

slot-unbootable:a:

slot-successful:a:

slot-retry-count:b:

slot-unbootable:b:

slot-successful:b:

Here's another effort where I tried rebooting to system from the pixel flasher "System" button.

2024-02-11 21:08:41 User initiated Reboot System

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

2024-02-11 21:08:41 Getting device: XXXXXXXXX state ...

Rebooting device: XXXXXXXXX to system ...

ADB waiting for device: XXXXXXXXXXX for device ...

2024-02-11 21:09:41 ERROR: Command "filepath for platorm tools XXXXXXXX wait-for-device timed out after 60 seconds

2024-02-11 21:09:41 Getting device: XXXXXXXXXX state ...

Device is now in ERROR mode.

Updating connected devices ...

Getting package com.topjohnwu.magisk path on the device ...

2024-02-11 21:09:44 ERROR: Could not get package com.topjohnwu.magisk path.

Selected Device on 2024-02-11 21:09:44:

Device ID: XXXXXXXXXXXXXXXX

Device Model:

Device Active Slot:

Device Mode: recovery

Has init_boot partition: False

Device Bootloader Version:

Device is Rooted: False

Device Build:

Device API Level:

Device Architecture:

Device Kernel Version:

sys_oem_unlock_allowed:

ro.boot.flash.locked:

ro.boot.vbmeta.device_state:

ro.product.first_api_level:

ro.boot.veritymode:

ro.boot.verifiedbootstate:

ro.secure:

ro.zygote:

ro.vendor.product.cpu.abilist:

ro.vendor.product.cpu.abilist32:

Magisk Manager Version: :

Magisk Path: None

Checked for Package: com.topjohnwu.magisk

Opening Magisk Modules Manager ...

2024-02-11 21:10:21 User Pressed Cancel.

Aborting Magisk Modules Management ...

Launching Package Manager ...

2024-02-11 21:10:26 ERROR: Could not get package list of all+uninstalled.

Return Code: 134.

Stdout: .

Stderr: adbd F 02-12 02:10:26 491 491 shell_service.cpp:380] Could not set SELinux context for subprocess

libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 491 (adbd), pid 491 (adbd)

.

Refreshing the packages ...

2024-02-11 21:10:32 User Pressed Close.

2024-02-11 21:10:32 Closing Package Manager ...

Opening Magisk Modules Manager ...

2024-02-11 21:10:37 User Pressed Cancel.

Aborting Magisk Modules Management ...
[Google Pixel 7 Pro] badabing2003:
Do you know if you had verity / verification disabled?

It's important to know prior to the next step.
[Google Pixel 7 Pro] Schroeder09:
both were disabled. I've always disabled them every time I update because the kiri kernel used to require it. Also, while you replied I edit my previous post. I added some info obtained from the pixel flasher.
[Google Pixel 7 Pro] badabing2003:
Flash stock factory, with both verity and verification disabled.

Get the phone working again before moving to rooting again.

If you want to use PF to flash.

Load factory

Process

Select the stock boot from the list.

Choose boot options

Flash Pixel Phone
[Google Pixel 7 Pro] Schroeder09:
I've actually never used pixel flasher prior to now. so if I do this the "old way" do I just go into the fastboot screen (that's what shows up when I press "bootloader" from pixel flasher) and press the flash-all.bat file like usual?
[Google Pixel 7 Pro] badabing2003:
Yes you can do old school.

You have to make sure you disable verity / verification in the script.
[Google Pixel 7 Pro] Schroeder09:
I'm in. wow. that was gut-wrenching. This harrowing experience has reminded me it's time to do a backup!!! Thank you for the help.
[Google Pixel 7 Pro] Fishawy:
Glad you sorted it out.

Just FYI, to reboot into Safe Mode (and disable all modules), you don't press volume down on as soon as you see the booting screen, you press it once you start seeing the Google logo/word.
[Google Pixel 7 Pro] Schroeder09:
Thanks for the clarification. I tried both ways. It wouldn't boot into safe mode.

It seems the issue is something to do with substratum. I just updated all my apps, created the overlays, and I get a crash, shutdown, and bootloop after trying to enable the overlays. Today I

can

boot into safe mode, and that's how I'll have to get by until I get home from work. I figured it was iconify since that app and mod seems

so

unstable. It's good ole' substratum though. It looks like magisk modules can be disabled from pixel flasher? So my plan is just to hook up to it, disable substratum, boot into the system normally, and disable the overlays. I wonder if I have to disable systemless hosts. Isn't that part of gettign substratum to work
[Google Pixel 7 Pro] roirraW "edor" ehT:
I think systemless hosts is very important for some (not the most obvious) root features we take for granted, so I'd avoid disabling that unless you absolutely have to.
[Google Pixel 7 Pro] Schroeder09:
I was just going to disable it to be able to boot normally. I think substratum installs its own magisk module too though. I can try disabling that first I guess. Is it possible to just disable (not uninstall) a magisk module from pixel flasher?

Updating the p7p has been uneventful and easy until now. Coming from november, 2023 has been awful! Thank God for the support on this site.
[Google Pixel 7 Pro] roirraW "edor" ehT:
TL;DR - I interpret the following as that you can only uninstall the modules, but it may be just the way things are written in Magisk's FAQ, and I'm misunderstanding.

The SOS button in PixelFlasher says:

But I haven't used this option directly in PixelFlasher, and if I've used that ADB command in the past, which I may have, I don't remember if it actually uninstalls the Magisk Modules or just disables them.

I just found the following in a Google search, which makes it sound like it uninstalls them:

Frequently Asked Questions

The Magic Mask for Android

topjohnwu.github.io
[Google Pixel 7 Pro] JakeDHS07:
If that's the case sounds like @badabing2003 may want to alter that wording to remove instead of disable to mitigate confusion
[Google Pixel 7 Pro] avid_droid:
I'm reading the constant post and envy having root problems with my phone. It's so boring being locked haha. Thinking of paying this off and jumping on another unlocked one
[Google Pixel 7 Pro] UberNorse:
Hi everyone, forgive me for the question as I have tried to read and catch up on the thread because I haven't been able to be on regularly as of late.

I'm on QPR2 Beta 3.1 I believe, the latest beta I'm sure, but when is the time to go back to stable? Was it with the release (UQ1A.240205.002, Feb 2024?

Apologies if it had been answered and I used to know this information but it has slipped my old noggin!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hello @UberNorse. QPR2 hasn't been made available as a Stable release yet - my best guess is it will next month.

There is no stable release you can flash while keeping your data, because all stable releases are QPR1 so would be considered a downgrade, which requires a factory reset coming from beta in order to work.

In the meantime, QPR3 Beta 1 has come out, but if you want to go back to stable, then don't flash it because QPR3 won't become stable until around June.

If you officially opted into the beta program, you could opt out, but make sure and not take any OTA, but if it were me, I wouldn't opt out until it's confirmed that stable QPR2 has come out and users are verifying that they're receiving the QPR2 stable OTA after they opt out.

If you've only manually flashed the beta without officially opting in, just wait until QPR2 goes stable - I'll have announcements in this thread and in the OP of the thread, and probably the thread title, too.
[Google Pixel 7 Pro] UberNorse:
Thank you bro You're a lifesaver
[Google Pixel 7 Pro] simplepinoi177:
I'm sorry I'm too late to this, but I don't believe I saw it brought up in the last few pages.....

If it's to be believed that it might be a module issue, and if running it in safe-mode is an issue, you could also run the adb command (the one with "wait-for-device" in the OP).

Back when Iconify and modifying QS was causing a corrupt issue as well, only running the adb command would get me back in....