yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] Cpm0813:
Help, something went wrong and phone won't boot properly now. I thought using OTA method is supposed to prevent this. Support file attached. Thanks.
[Google Pixel 7] badabing2003:
What is the issue?

You were on slot a November release, and your phone booted to slot b December release.

Selected Device on 2023-12-30 13:11:29:
Device ID: REDACTED
Device Model: panther
Device Active Slot: b
Device Mode: adb
Has init_boot partition: True
Device Bootloader Version: cloudripper-14.0-10825040
Device is Rooted: True
Device Build: UQ1A.231205.015
Device API Level: 34
Device Architecture: arm64-v8a
Device Kernel Version: 5.10
sys_oem_unlock_allowed:
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state: unlocked
ro.product.first_api_level: 33
ro.boot.veritymode: enforcing
ro.boot.verifiedbootstate: orange
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
vbmeta type: ab
Slot A Verity: Enabled
Slot A Verification: Enabled
Slot B Verity: Enabled
Slot B Verification: Enabled
Magisk Manager Version:
Magisk Version: a468fd94:25205
Magisk Config SHA1: bd65f0ef723b2a3ddeba2cb245d213db5aae5a21
Magisk Modules:
DisableFlagSecure enabled v7.0
Tethering Enabler enabled 11.0.0
Systemless Hosts enabled 1.0
Universal SafetyNet Fix enabled v2.3.1-MOD_3.0 [Update Available]

Couple of things that I don't like about your options.

You kept modules enabled, specially DisableFlagSecure and Tethering Enabler, you should always disable such risky modules prior to update.

You're still using USNF?

You're using Magisk 25205, it has compatibility issues with A14
[Google Pixel 7] Cpm0813:
Whenever I try to boot phone now, I get message saying corrupt and then it gets stuck on Google screen, never actually fully booting phone.

I just installed DisableFlagSecure yesterday.

What should I use instead of USNF? Is it this Pif thing I now see mentioned in the release notes?

Which Magisk version do you recommend?

Thanks.
[Google Pixel 7] badabing2003:
Check this.

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

This should allow you to disable module (try the safe mode suggestion first)

I suggest you install the latest Magisk.

As for USNF, right you need to switch to PlayIntegrityFix (I recommend @osm0sis fork), PixelFlasher will give you the option of installing either.
[Google Pixel 7] Cpm0813:
Not sure about Safe Mode. I know how to boot to get to Fastboot Mode, which gives me choices about other modes I can go into.

I never get the animation, so not sure how to get Safe Mode to actually go.
[Google Pixel 7] badabing2003:
Check the guide in the Magisk link I gave you, it has a link to Magisk document explaining how to get into safe mode.
[Google Pixel 7] Cpm0813:
It says reboot into Safe Mode. This is what I found for Safe Boot for Pixel: https://support.google.com/pixelphone/answer/2852139?hl=en. However, I never get the animation to show up.

Is there a way to force it to boot into the other slot with the November release?
[Google Pixel 7] Cpm0813:
I did tell it to switch slots in PixelFlasher, which did get me to the animation screen, where I held down Vol Down, so I did get it to boot info Safe Mode.
[Google Pixel 7] badabing2003:
If your modules are correctly disabled, you should be in system and PixelFlasher should indicate that.
[Google Pixel 7] Cpm0813:
Yes, I was able to boot normally now and the modules are disabled. Do I just re-enable them one at a time now?

In Magisk, it is showing Magisk is 25205, but the App is 26404. Not sure what that means, or what to do to change it to a different version now. I used Canary when I first got this phone because it worked and the Stable release did not. Do you recommend I switch to Stable now?

Everytime I see the lock screen or reboot my phone there are a lot of horizontal lines appearing. Not sure why or how to fix this.
[Google Pixel 7] badabing2003:
That's good, but don't enable without first checking if they are compatible with the latest December release.

you'd have to check each module in their release notes or if others have reported it.

I already pointed out which ones I fear might break your system.

Not sure what you mean exactly, I suppose the app is at 26404 but the core (rooted part) is still at 25205 for sure.

Click on install and choose the recommended Direct Install (assuming that you actually have the app at 26404)

Canary is fine, that is what I use, although at times it gets broken, but it also has the latest fixes.

If you don't feel comfortable with that then go for stable.

That I know nothing about, I don't think it has anything to do with rooting.
[Google Pixel 7] badabing2003:
Latest Release:

Dec 30, 2023 v6.5.3.0 change log:

Added Smart Paste Up to simplify getting operational for beginners.

It automatically sets the First API to 25 if it is not set, otherwise keeps the value.

It automatically reprocesses the output window content, to meet module / version requirements.

It automatically pastes the processed data into Active Pif window

If Auto Update pif.json is checked.

Updates the correct pif.json on the device.

Kills the unstable GMS.

Runs Play Integrity Check if Auto Check Play Integrity is selected.

Updated screenshot for the guide.

Pif guide in OP is updated as well.
[Google Pixel 7] badabing2003:
New Release:

Jan 07, 2024 v6.6.0.0 change log:

New Feature: Download any Google device firmware or full OTA directly in PixelFlasher.

Automatic detection and notification if an update is available for the selected device.

New feature: Cancel / reset OTA update pushed by Google (need to be used prior to a reboot). Binary graciously provided by @capntrips.

Removed outdated links from help menu.

kdrag0n's safetynet-fix

Displax's safetynet-fix

Added new links to the help menu

osm0sis's PlayIntegrityFork

chiteroman's PlayIntegrityFix

TheFreeman193's Play Integrity Fix Props Collection

Full OTA Images for Pixel Phones / Tablets

Factory Images for Pixel Phones / Tablets

Full OTA Images for Pixel Watches

Factory Images for Pixel Watches

Full OTA Images for Pixel Beta 14

Factory Images for Pixel Beta 14

Enable Magisk Kitsune patch creation using Magisk core component (previously disabled due to incompatibility and patches were only created using the manager).

Miscellaneous improvements, bug fixes and code refactoring
[Google Pixel 7] badabing2003:
Bugfix Release:

Jan08, 2024 v6.6.0.1 change log:

Bug Fix: Toolbar menus were interfering with the download menus and triggering a download when toolbar was modified.
[Google Pixel 7] badabing2003:
New Release:

Jan 10, 2024 v6.6.1.0 change log:

Changed PixelFlasher icons to dark icon (artwork provided by @T-Ryder).

Potential fix for #144, when getting firmware / ota download links, fallback to ignore ssl errors, if ssl errors are encountered.

Add ssl verify ignore fallback to any download (also display warning).

Add button in Pif Manager to convert key=value format (similar to env or older .prop format) to json format.

Device Info now gets props as root if the device is rooted.

Miscellaneous minor fixes and improvements.
[Google Pixel 7] krugm0f0:
Friendly reminder to let you know the year is now 2024. :D
[Google Pixel 7] badabing2003:
It is clearly stated in the guide.

If you keep modules enabled you risk a bootloop due to bad module(s) or incompatibility, hence it is strongly advised that you first disable modules (not all modules are created equally), and of course when you run stock boot, modules are not loaded and there is no bootloop.

With Factory image flashing you cannot have two slots bootable, you need OTA for that, and flashed the same version on both slots.

@simplepinoi177 asked you to submit a support file here, and yet you posted here without support file, screenshots and some console captures are not support file, not only I don't get enough troubleshooting details, you're exposing personal data, a support file redacts sensitive data.

Too bad you had to spend a day hopefully it was a educational experience, but be aware that the probelms you experienced including the corrupt message (which by the way is harmless and there are documented ways to get rid of it) has absolutley nothing to do with PixelFlasher, and categorizing as such is a disservice to others who might believe you.

You would have ran into the same issues with or without PixelFlasher, just Google it or search it here at XDA and you'll see.
[Google Pixel 7] badabing2003:
New Release:

Jan 20, 2024 v6.7.0.0 change log:

Added history to device image selection (Max 16)

#133 Fix for Get Xiaomi.eu print when version_class is missing.

Improved device state detection with retry attempts.

Updated 7zip binaries to v23.01

Added line numbers to Active Pif window and Output Console window, along with an option to sort FP keys for easy visual comparison.

Pixel watches require user intervention after flashing OTA, added popup messages to guide the user for the next steps.

You can now easily save the Active Pif content into a pif json file (filename automatically build from print information, however user can change before saving)

Keep splash screen visible until the main window shows up.

Under the hood improvements and bug fixes, improved logging and refactoring code.
[Google Pixel 7] badabing2003:
New Release:

Jan 29, 2024 v6.7.1.0 change log:

Added an checkbox in Pif Manager. Keep All Keys which allows any unrecognized key to be kept in the json file when using smart paste. This allows support for future keys that could be added but are unrecognized today. (Example: KERNEL)

Added Cleanup DG but in Pif Manager to clean up Droidguard cached files. Helps in some situations.

Miscellaneous small improvements.
[Google Pixel 7] surya467:
Hello, im trying to install magik and getting this error while patching

ERROR: Could not get file content: /data/local/tmp/pf_patch.log

Aborting ...
[Google Pixel 7] badabing2003:
Support file please
[Google Pixel 7] surya467:
HI, thank you for response, I solved it.
[Google Pixel 7] badabing2003:
New Release:

Feb 16, 2024 v6.8.0.3 change log:

Added untested support for patching with KernelSU for Pixel phones. Patching with APatch is in the works.

Detect known blacklisted kernel names, and notify the user. (list is current as of this release date).

Rename the SOS button to reflect that the modules would be removed instead of being disabled.

Removed bulk install APK feature which installed all APKs in a directory, instead reworked the Install APK feature to allow user choice multi-select, and added another option Bypass low target SDK block.

Report device Kernel and KMI.

Added Android Platform Tools 34.0.4 to known problematic versions list, which when detected warns the user.

Improved Pixel Watch flashing dialog messages.

New feature: #152 Show System Apps and Show 3rd Party Apps in Package Manager.

Bug Fix: #157 'PifManager' object has no attribute 'first_api' in some situations.

Bug Fix: scrcpy download link was not working.

Support for upcoming PlayIntegrity Fork v8 changes by @osm0sis.

Added Special Magisk 27001 install option when selecting Magisk install. (This is similar to Special Magisk 26401, just a version difference).

Support for SSL error fallback for all https requests (previously was only for PIF downloads).

Improved factory / image downloading with lower memory footprint.

Miscellaneous minor bug fixes and enhancements.
[Google Pixel 7] badabing2003:
Update Release:

Feb 17, 2024 v6.8.0.4 change log:

Use MacOS 13 to build with Github actions instead of MacOS 11, sorry to folks who use older MacOS, unless I get it to build it successfully on Github, MacOS 13 will have to do.

#158 Fix the App version.

Note: The following versions have identical code 6.8.0.0, 6.8.0.1, 6.8.0.2, 6.8.0.3, 6.8.0.4, the differences are in Github actions.
[Google Pixel 7] vlc_marcos:
Hello, can I ask you one thing. Do you have videos explaining how to use your tool to install modules to make GPAY to work on Lineage 21? Thank you a lot.
[Google Pixel 7] badabing2003:
I don't, but I've seen others make some.

My guide is on the first page of the main thread.
[Google Pixel 7] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version.

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

Misc. bug fixes and improvements.
[Google Pixel 7] badabing2003:
New Release:

Mar 03, 2024 v6.8.2.1 change log:

Bundle in the executable the missing files android_version.json and android_devices.json otherwise patching with KernelSU won't detect your Pixel as Pixel device.

Add back Magisk Alpha install option, thanks to pull request from @hldr4

Make Magisk install window resizable.

Add right click option on the selected Magisk to download in case you just want it downloaded and not installed.

Update all old forum.xda-developers.com links to xdaforums.com

Make Pif Manager work without a device being connected (obviously for props / pifs management and not for updating / testing pifs).

Typo fixes and other minor improvements.
[Google Pixel 7] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel 7] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel 7] ldeveraux:
Maybe not the place to ask this, but why is there only 1 variety of image for the March update? I'm on VZ so typically flash that version, but it doesn't exist this month.
[Google Pixel 7] badabing2003:
I don't know, maybe when there is one variety, it's generic to apply to VZ and non-VZ

Just a guess.
[Google Pixel 7] ldeveraux:
OK thanks, you're the guy so if you don't know.... I was contemplating flashing this but wasn't sure they were going to drop the VZ version later, or it was pulled for reasons.
[Google Pixel 7] Cpm0813:
I use Verizon but I never use their version. My understanding is their version has all the Verizon bloatware included also.
[Google Pixel 7] Dr Grato:
I used PixelFlasher to update. However after I update, i lose the root. Im a bit confuse which part I did it wrong. Can anyone help?
[Google Pixel 7] badabing2003:
View attachment 6084396
[Google Pixel 7] ldeveraux:
Did you follow the steps closely in the main thread?

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com

It sounds like you might not have actually patched the image, or you didn't flash the patched image.
[Google Pixel 7] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel 7] ldeveraux:
What's the story with Magisk these days? I know Topjohnwu said he'd stopped developing it, but there are still updates for some reason? Is KernelSU the spiritual successor, should I be rooting with this from now on?
[Google Pixel 7] badabing2003:
He hasn't stopped, in fact he's very active.

View attachment 6084894
[Google Pixel 7] ldeveraux:
No I know, but he said he was stopping the development with like version 26 or so. I don't remember the specifics.

But apart from that, what's the benefit/drawback to KernelSU vs Magisk? I only ask because you've included it in the latest PixelFlasher
[Google Pixel 7] badabing2003:
People asked for it, hence I included.

I personally don't use neither APatch nor KernelSU, my test devices don't support it.

This should tell you about their similarities and differences.
[Google Pixel 7] The_real_Narutoxik:
Whaoooo!!! it's an fantastic app . Work very fine on win 10 / pixel 7. upgrade and root last version of A14 without problem . many many thx :cool:
[Google Pixel 7] Tirofog:
Having recently moved to Linux Mint, I'm using the Ubuntu package. The April update seemed to be going fine but then stalled at 'fastboot could not detect device'. The device boots, the update was installed, but apparently not with the patched image as Magisk/root is not present.
[Google Pixel 7] badabing2003:
You're device is not detected in bootloader mode, which is required to flash the patch.

Reboot to bootloader and run this command and tell me what you get.

fastboot devices
[Google Pixel 7] Tirofog:
Okay, back in business! Firstly, in the built-in terminal I tried adb devices, got 'adb not found but can be installed with sudo apt install adb', which I did. After this step the flash was successful.

Still getting my head around linux, does this mean another platform tools was installed in addition to my previous download from within PF?
[Google Pixel 7] badabing2003:
You shouldn't install package manager's version using apt, those are typically behind, and they add themselves into the path.

The best is to uninstall that

Download the latest from Google (link in PF)

Unpack it somewhere and point PF to it.

Quit PF

kill all instances of adb and fastboot

start PF

this way PF will only pick up the ones defined in PF.
[Google Pixel 7] Tirofog:
I'm a bit puzzled as to why it happened, as I had downloaded through PF, then unpacked and pointed PF to it in the first place. Anyway, really appreciate the tool and your helpfulness (y)
[Google Pixel 7] badabing2003:
Not sure, perhaps there was an old one running

Repeat the steps I mentioned, but this time by first removing the package manager version kill and only have PFs

The reboot to bootloader in PF, and see if it reports errors or it detects it.

Perhaps there is a bug in the version: 35.0.1-11580240

I'm curious what version the package manager is at.
[Google Pixel 7] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel 7] Tirofog:
Appears to be a bug in the works.. I uninstalled the package (v1:10.0.0+r36-9), and removed all traces of adb. Then pointed PF to the downloaded one, booted to bootloader successfully, even though PF could not detect device. From there PF died, with the force quit/wait dialogue.

Opening PF again gives about ten seconds of the splash then just closes. Support file to follow hopefully after a reboot🤞
[Google Pixel 7] badabing2003:
I'll wait for the support file.

Can you also try this version of Platform tools please

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
[Google Pixel 7] Tirofog:
After reboot still just get the brief splash screen. I've just grabbed the latest release but on opening asks to choose a program?
[Google Pixel 7] badabing2003:
It's a zip file, you have to unzip it to a folder and point PF to it.

You can run PF with the argument --console

To see the errors

You can also try:

Kill PF

Rename this file:

/home/REDACTED/.local/share/PixelFlasher/PixelFlasher.json

Change REDACTED to your username

and start again,

If it works, I want a copy of the renamed file.
[Google Pixel 7] Tirofog:
Sorry, I was referring to opening PF not platform tools..

Appreciate if you would spell it out a bit for me. The --console, how to run exactly. Is kill PF a command? Also the json file code, I get command not found.

Bear in mind that I can't open PF (and I'm old 😊)..
[Google Pixel 7] badabing2003:
Please see this post, if you're still having an issue, let me know.
[Google Pixel 7] Tirofog:
PF is up and running but still have an issue booting into bootloader. It does boot but PF freezes, 'could not detect device'. Tried latest platform tools also 33.0.3.
[Google Pixel 7] badabing2003:
Kill all adb and fastboot process

quit PF

put your phone into bootloader mode

issue from terminal

fastboot devices

then start PF

scan for devices

give both fastboot output from terminal and PF logs
[Google Pixel 7] badabing2003:
There's your prblem seen in fastboot command.

no permissions (missing udev rules? user is in the plugdev group); see [http://developer.android.com/tools/device.html] fastboot

See what the link is telling you

sudo usermod -aG plugdev $LOGNAME
[Google Pixel 7] Tirofog:
Sorted now, a fair bit tweaking required on Mint to do anything, e.g. make PF executable.. Thanks for making life easier for everyone on here (y)
[Google Pixel 7] Mississip:
I would appreciate input to help me understand what I may be doing wrong in updating with Pixelflasher.

My rooted Pixel 7 showed build number UQ1A.240105.004 (the January build) before and after the April update, in which Pixelflasher again appeared to perform the update properly without any error messages, though perhaps I don’t know what to look for. I don't believe I changed my process since last August, but I must have started doing something wrong in February. Please suggest what my error may have been in the following procedure.

Download Pixel 7 Factory Image

Verify SHA-256 checksum

Disable/remove Magisk modules and restart

Enable USB debugging

Connect Phone

Open pixelflasher.exe

Allow debugging

Right of android platform tools box browse to platform tools 33.0.3

Right of ADB connected devices box scan and select the phone under ADB Connected Devices

Delete autopopulated old update

Right of Device Image browse to the location of the newly downloaded build image and open

Process the update by pressing the rocket button

Select the update that appears in the SHA space

Click the patch button (and patch with Magisk)

Select the patched image

Click “Flash Pixel Phone” button

Verify magisk is up to date
[Google Pixel 7] badabing2003:
Your steps look right, but I can't tell you what's going on without seeing support file.
[Google Pixel 7] badabing2003:
Update Release:

Apr 09, 2024 v6.9.1.3 change log:

Fix regression introduced when refactoring code in KernelSU Patching.

#187 On MacOS, move the exit menu into PixelFlasher's file menu from the OS's native Exit menu.
[Google Pixel 7] Mississip:
Apologies. I slept on it and tried to recall what I might have done differently up to three months ago. I use the Skvalex call recorder module. To be on the safe side, in addition to removing the module, I used to delete the call recorder app it installs and the unlocker, but quit that extra step without realizing it made a difference. I repeated my process but deleted these apps after removing Magisk modules and am now on the April build. Thanks so much for you time and attention.