I will uninstall the safetynet module and flash the kernel and report back. I'm not at my computer right now but when I get back to it I'll let you know what happens
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Support Thread.
- Thread starter badabing2003
- Start date
So I uninstalled safetynetfix and I think it removed the enforcing flag but I was still unable to use the kernel
[ro.boot.product.hardware.sku]: [GVU6C]
[ro.boot.revision]: [MP1.0]
[ro.boot.secure_boot]: [PRODUCTION]
[ro.boot.slot_suffix]: [_b]
[ro.boot.theme]: [1]
[ro.boot.verifiedbooterror]: [ERROR_VERIFICATION]
[ro.boot.verifiedbootstate]: [orange]
[ro.boot.verifyerrorpart]: [vbmeta]
[ro.boot.warranty.sku]: [UGS]
[ro.bootloader]: [cloudripper-1.0-9074510]
[ro.bootmode]: [unknown]
Have you checked the kernel forums / threads?
I don't know what Kernel it is, what it expects and what problems you're having, and even if I knew, I probably shouldn't give advice on it.
New Release:
Dec 04, 2022 v4.5.0 release
Dec 04, 2022 v4.5.0 release
- New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
- New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
- Use latest Python updated packages.
- Ubuntu 22.04 support.
- Miscellaneous improvements.
New Release:
Dec 05, 2022 v4.6.0 release
Dec 05, 2022 v4.6.0 release
- Added single click button to easily flash just the
boot/init_boot(stock or patched) to the phone. - #39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
- #39 Do the Magisk backup only when rooted.
- Decouple OTA sideload from needing factory image.
- Other minor improvements.
Successfully installed December update. Excellent work! We thank you
Hello,
first of all thank you for the great tool.
My report about the first experiences:
After I received my new Pixel 7 last week, I immediately wanted to root it (like my old OnePlus 7).
The first attempts under Windows 11 and Linux failed and always bricked the Pixel.
This was not due to the PixelFlasher, but to the USB cable I used and its length.
After I tried it with the original cable everything worked
One day later I had magisk so far that Google Wallet with PayPal worked without errors.
I just downloaded the December update and patched and flashed it.
Everything worked right away. YASNAC SaftyNet Check shows everything green
Google Wallet also does not complain, so the next purchase at the checkout should all go well ...
Thanks again for PixelFlasher
Greetings Jerry
first of all thank you for the great tool.
My report about the first experiences:
After I received my new Pixel 7 last week, I immediately wanted to root it (like my old OnePlus 7).
The first attempts under Windows 11 and Linux failed and always bricked the Pixel.
This was not due to the PixelFlasher, but to the USB cable I used and its length.
After I tried it with the original cable everything worked
One day later I had magisk so far that Google Wallet with PayPal worked without errors.
I just downloaded the December update and patched and flashed it.
Everything worked right away. YASNAC SaftyNet Check shows everything green
Google Wallet also does not complain, so the next purchase at the checkout should all go well ...
Thanks again for PixelFlasher
Greetings Jerry
I can't launch 4.5.0 or 4.6.0 versions, I'm under windows 11, there's only the access fence "Pixel flasher is loading" and when it disappears nothing more (the app appears on windows task manager). 4.4.0 version is working fine.
Any idea?
Any idea?
New Release:
Dec 06, 2022 v4.6.1 release
Dec 06, 2022 v4.6.1 release
- #40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.
- Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.
Credit to gecowa6967 at XDA.
Once connected i try to to restar boot loader or do a Dry Run. It says phone doesnt seem to be connected
badabing2003, Hi! Have some problems here...
Pixel 7, current firmware installed on the phone is 220804.031, I'm trying to patch a boot image but always failed. I tried on MacOS and Linux, the same error.
Looks like the model is not recognised. Would appreciate any ideas.
Pixel 7, current firmware installed on the phone is 220804.031, I'm trying to patch a boot image but always failed. I tried on MacOS and Linux, the same error.
2022-12-07 22:35:00 The following firmware is selected:
panther-td1a.220804.031-factory-2f036a47.zip
Please select a boot image!
2022-12-07 22:35:03 Scanning for Devices ...
1 Device(s) are found.
Selected Device on 2022-12-07 22:35:03:
Device ID: 28161FDH2000ZJ
Device Model:
Device Active Slot:
Device Mode: recovery
Device is Rooted: False
Device Build:
Device API Level:
Device Architecture:
Device Bootloader Version:
Magisk Manager Version:
Selected Boot:
File: init_boot.img
Path: /Users/anton/Library/Application Support/PixelFlasher/boot_images4/caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d/init_boot.img
SHA1: caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d
Patched: False
Date: 2022-12-07 21:35:30
Firmware Fingerprint: panther-td1a.220804.031
Firmware: /Users/anton/Downloads/panther-td1a.220804.031-factory-2f036a47.zip
Type: firmware
==============================================================================
2022-12-07 22:35:07 PixelFlasher 4.6.1.0 Patching boot.img
==============================================================================
*** Dialog ***
WARNING: Your phone model is:
The selected init_boot.img is from: panther-td1a.220804.031
Please make sure the init_boot.img file you are trying to patch,
is for the selected device: 28161FDH2000ZJ
Click OK to accept and continue.
or Hit CANCEL to abort.
______________
User pressed ok.
Deleting init_boot.img_caf4d53a.img from phone in /storage/emulated/0/Download ...
2022-12-07 22:35:09 ERROR: Encountered an error.
Return Code: 134.
Stdout: .
Stderr: adbd F 12-07 21:35:08 403 403 shell_service.cpp:380] Could not set SELinux context for subprocess
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 403 (adbd), pid 403 (adbd)
.
Aborting ...
panther-td1a.220804.031-factory-2f036a47.zip
Please select a boot image!
2022-12-07 22:35:03 Scanning for Devices ...
1 Device(s) are found.
Selected Device on 2022-12-07 22:35:03:
Device ID: 28161FDH2000ZJ
Device Model:
Device Active Slot:
Device Mode: recovery
Device is Rooted: False
Device Build:
Device API Level:
Device Architecture:
Device Bootloader Version:
Magisk Manager Version:
Selected Boot:
File: init_boot.img
Path: /Users/anton/Library/Application Support/PixelFlasher/boot_images4/caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d/init_boot.img
SHA1: caf4d53ab8b0d8e1ec65c98cdfbd4ce6611d678d
Patched: False
Date: 2022-12-07 21:35:30
Firmware Fingerprint: panther-td1a.220804.031
Firmware: /Users/anton/Downloads/panther-td1a.220804.031-factory-2f036a47.zip
Type: firmware
==============================================================================
2022-12-07 22:35:07 PixelFlasher 4.6.1.0 Patching boot.img
==============================================================================
*** Dialog ***
WARNING: Your phone model is:
The selected init_boot.img is from: panther-td1a.220804.031
Please make sure the init_boot.img file you are trying to patch,
is for the selected device: 28161FDH2000ZJ
Click OK to accept and continue.
or Hit CANCEL to abort.
______________
User pressed ok.
Deleting init_boot.img_caf4d53a.img from phone in /storage/emulated/0/Download ...
2022-12-07 22:35:09 ERROR: Encountered an error.
Return Code: 134.
Stdout: .
Stderr: adbd F 12-07 21:35:08 403 403 shell_service.cpp:380] Could not set SELinux context for subprocess
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 403 (adbd), pid 403 (adbd)
.
Aborting ...
Looks like the model is not recognised. Would appreciate any ideas.
@fullmetal509
Click on the box between adb connected devices and scan. I think that's what you need.
Click on the box between adb connected devices and scan. I think that's what you need.
Last edited:
As @scuzzo500 said, hit the scan button.
Read the main thread's OP or GitHub for usage.
If after scan and then selecting from the dropdown does not work, please provide support.zip
It was in "bootloader mode" but PixelFlasher requires "adb mode"... I thought recovery is what I need because in recovery mode my phone is available by "adb devices", I was wrong
Now I see, need just to enable USB debugging in developer options and keep the phone in "system running" state. Ok, now I patched desired init_boot with no problems. Thanks for the tool!
When flashing the device can be in any mode, PF will detect the mode and reboot to bootloader (assuming that the device can get into bootloader mode)It was in "bootloader mode" but PixelFlasher requires "adb mode"... I thought recovery is what I need because in recovery mode my phone is available by "adb devices", I was wrong
Now I see, need just to enable USB debugging in developer options and keep the phone in "system running" state. Ok, now I patched desired init_boot with no problems. Thanks for the tool!
However to create a patch, you need to be in adb mode.
I have a question and I hope someone can help me understand something confusing me. I've got my phone updated to the November patch. In the attached screen shot I have updated to the firmware circled in red. I know the December update is out and I'm set up and ready to apply it. However, I'm not sure if the firmware circled in blue is usable on my pixel 7 since labeling tda1 has changed to tq1a. I've got the global version so I figure I don't need to worry about the Verizon, telia, or o2 firmwares. Is this the right firmware for my pixel 7? If it is, why does Google change the labeling in, what to my experience is, such an odd way?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2New Release:
Apr 14, 2024 v6.9.2.0 change log:
- Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).
Credit to @tbalden for the discovery and @capntrips for the details of the process. - Select any img file and get additional image info.
- #190 fix, scrcpy launch improvement.
- Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).
- If KernelSU or APatch is installed, report their version as part of device details.
- Improved logging.
- Improved santization.
- Other minor improvements and added stability.
1
Did you follow the steps closely in the main thread?
It sounds like you might not have actually patched the image, or you didn't flash the patched image.📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an...
xdaforums.com
1New 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 MagisktoInstall Root Appas it now supports directly installing KernelSU and Apatch through PixelFlasher. - Add Install ZygiskNext module option in
Magisktool options. - Use UTF-8 encoding for the logifile instead of ISO-8859-1
- Miscellaneous minor improvements.
1 - Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).
-
21
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 Google Pixel 7 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
IMPORTANT:
Please do not ask questions the answers of which are already stated in the OP.
I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.
Troubleshooting:
If you need support or assistance, please generate and provide a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
And no, a screenshot of the console or an excerpt from the console, does not make a support file.
Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.
Do NOT modify the support file, keep it intact.
8New Release:
Feb 05, 2023 v4.7.0 release
- Added Magisk Backup Manager:
- List all Magisk backups currently on the device.
- Highlight the one that is backup of the current installed version.
- Delete backups.
- Manually add backup from PC.
- Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
- Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
- Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
- Magisk installer improvements:
- When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
- Magisk installer window displays the package name.
- You can now copy to clipboard, the download URL and package ID.
- Magisk Manager columns are now wider for better readability.
- Package Manager improvements:
- Added Search / Filter option.
- Show count of filtered packages.
- Application Name (label column).
- "Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
- Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
- Other under the hood improvements.
- When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
- More verbose logging that helps with troubleshooting.
- Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
- Moved existing links under Help Menu | Links, and added few more handy links.
- Added timestamp to support.zip filename.
- On request, spinning cursor with text "Please be patient ..." is now displayed in red.
- Flashing to inactive slot is now in basic configuration instead of advanced configuration.
- Preparation work for version 5.0 DB improvements.
8New Release:
Apr 30, 2023 v4.10.0 release
- Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
- Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
- Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
- Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
- Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
7New Release:
Mar 14, 2023 v4.8.1 release
- #47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
- Added more visual troubleshooting event flows.
- Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
- Improved support.zip redactions.
- Added Support.Zip generator button on the Main screen.
- APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
- Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
- Bug fixes and other improvements.
6New Release:
Feb 12, 2023 v4.8.0 release
- #50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro
- #48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.
- Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues
- Disable Magisk Backup Manager button if root access to adb shell is not granted.
- Button to Open adb shell connected to the selected device.
- Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
- Added Magisk Backup Manager:
