Okay, so I tried like 3 different USB hubs and none of the them worked for em, but I'll be damned, when I used a USB A port on a Thunderbolt 4 Dock, it finally worked. It would not work on the Thunderbolt ports, though. Nice find!
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
- Thread starter badabing2003
- Start date
You really should consider giving @badabing2003 those logs to see if he can't correct what might've gone wrong and give you a solution -- temporarily until he applies it to the PF program -- and/or doing as I originally suggested and manually flash the Full Factory image. Just because it states that the "data [is] corrupt" doesn't necessarily mean all is lost and you can't correct things and are relegated to only attempting to recover what is stored; it probably could easily mean that one or more of the partitions simply wasn't flashed or applied correctly and that is what has become corrupted. Applying the Full Factory image via flash-all (with "-w" removed) might get things back on track -- as it will re-apply all the partitions once more over any corrupted partitions -- without loss of internal data, apps, and settings.
I earnestly hope you consider it...Good luck!
djensen777
Member
And in PF, if you select the unpatched boot instead of patched one, then you are practically doing flash_all (script rebuild using platform tools path and device ID to avoid picking up wrong platform tools and flash a specific device (if multiple devices are connected to the PC)
djensen777
Member
Have to dig out the old HP laptop with win on it. Not having any luck with PureOS.
Does being in the beta program make any new variables? How to get back to stock and start over?
Get back to cheetah-tq1a.221205.011-factory-b144b426.zip Any suggestions would be appreciated.
Thanks in advance.
Does being in the beta program make any new variables? How to get back to stock and start over?
Get back to cheetah-tq1a.221205.011-factory-b144b426.zip Any suggestions would be appreciated.
Thanks in advance.
beta has no relevance in this.
Going back would require a wipe, if that is ok with you, just follow the usage and flash the image (patched or not, it's up to you)
Hi all,
I'm trying to figure out how to use pixel flasher.
My P7pro is rooted with verity and verification disabled. But, PF does not recognize my device to be rooted. So, my question is how do I get PF to recognize root and to update + retain root and verity & verification left disabled?
I'm trying to figure out how to use pixel flasher.
My P7pro is rooted with verity and verification disabled. But, PF does not recognize my device to be rooted. So, my question is how do I get PF to recognize root and to update + retain root and verity & verification left disabled?
Did you allow root access for "[SharedUID] Shell" (com.android.shell) in Magisk? That's used by PF to detect root.
If you use Magisk Hide you can also set the new package name (not app name) in the PF settings.
@nIsmoAddict
Like @mko000 said. You need to allow root access to shell so that PF can operate as root as it does all its operations over shell.
See the usage in the main thread or Github.
Like @mko000 said. You need to allow root access to shell so that PF can operate as root as it does all its operations over shell.
See the usage in the main thread or Github.
EtherealRemnant
Senior Member
I have tried using PixelFlasher to root the QPR2.1 beta twice now and when it says it has flashed the patched image, the phone boots back up with Magisk still not having root. I don't really have time to troubleshoot it so I'm just going to have to do it manually.
EDIT: Manually fastboot flashing the patched image that PixelFlasher made was successful so it wasn't the image.
EDIT: Manually fastboot flashing the patched image that PixelFlasher made was successful so it wasn't the image.
EtherealRemnant
Senior Member
I'll get it for you when I get back to my house on Tuesday or so.
Yeah it is a known issue, while using a Macbook you need to use a type-C to USB-A cable(obviously with a hub) on the newer MacBooks.
Just tried to use this and I'm getting boot loop I think ( boots up, shows Google words then shows the G sign in full colours before going sepia and has loading bars then goes blanks and repeats)
Not really sure what I should do now. Any help would me much appreciated!
Not really sure what I should do now. Any help would me much appreciated!
First step would be to submit a support.zip so dev can look at it.
Yup, already PMed Dev. I did somehow manage to get it into safe mode just now...
PF detects it, just somehow disabled all magisk modules through PF just then too I think....
As @Lughnasadh stated, support.zip would help me investigate.
No need to PM, you can post here, the files are sanitized and don't contain any sensitive information.
I took a look at your logs, nothing stands out, everything looks good.
The only thing I can think of is Magisk Modules.
You should always disable modules (at least the suspect ones)
I never had any issues keeping Systemless hosts and Safetnet Fix enabled, but I can't say the same about other modules you are using.
If you disabled modules, just reboot, and you should be fine.
Report back.
will this work on a t-mobile pixel 7pro?just so im clear this isnt a unlocking and rooting tool correct just a flashing tool?
If the phone is locked by your mobile provider, this tool will not unlock it.
However if you phone is oem / booltloader unlockable, then this tool will help you unlock it, and then root.
Hope that answers your question.
Similar threads
Top Liked Posts
-
1
Looks like a communication issue.
Try another cable
Try another usb port (preferably usb2)
Make sure you don't touch the cable, phone during flashing.
Try flashing again, if it fails, provide a support file.1
Typically you don't need to flash older firmware,
You're using a good version of Android Platform tools
But without full logs, I don't know other details like Magisk version, modules used, your existing firmware, what you selected as boot image ...1
The default is to flash to the inactive slot. You can change it to, however you wish, but most of us just let it flash to the inactive slot each month.1
Correct, just set the checkbox, and PF will remember it, and after flashing to inactive slot it will switch to the correct slot that you just flashed. -
12New 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.
7
For anyone else looking for the latestadbthat actually works, here are the official links to adb/fastboot 33.0.3:
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux
Google doesn't keep the links to previous versions of adb on the platform-tools page.6Thanks @simplepinoi177 for finding relevant posts.
What I want to add is that, although the initial thought process was to use the alternate slot as a fallback.
Unfortunately that only works with older devices, and does not work for newer ones.
Even for older devices one needs to remove system_other.img from the update image to get it to work.
I have posted about the details, unfortunately I'm not very good at finding my own posts.
The gist of the matter is that, factory images contain system_other which is flashed to the alternate slot's system partition, they contain the optimized dex files which are copied to the active slot after booting to system to save time.
This effectively deems the alternate partition's system unusable.
Removing system_other before flashing theoretically would get around that issue, at a small performance hit at first while the dex files are optimized on first use, and that works on older devices.
I managed to setup Pixel XL with both slots bootable, and alternate between them at will, even one was rooted and the other stock.
Sadly this no longer works on newer devices due to AVB.
Having said all that, I still flash to alternate slot every month, knowing well that it I wouldn't be able to system boot to the alternate slot, I do this mainly because I want to keep all the partitions at most one release behind.
Flashing to both slots makes sure that the bootloader is current on both slots, which avoids issues like what happened in August.
I don't flash to both slots mainly because if there is a regression in the bootloader (I doubt it) or a disruption during flashing, I will have both bootloaders corrupt, effectively hard brick the device.
I rather flash the alternate and in case something goes wrong, at least I can get into boatloader mode and fix things.
There are a lot of posts about all this if you search the forums.6New 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.
6
@badabing2003 is going to ask you to pull a log and post it here. May as well get a head start and do that so he can see where the issue is -
49
This is the support thread of PixelFlasher for Google Pixel 7 Pro
PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.
Basic mode: Should suit most users. Some of the features in basic mode are:
- Simple UI interface, click and go. No more command line, no more placing all files in one directory.
- boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without manual steps) and perform upgrades without losing root.
No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
No more setting airplane mode and clearing storage to retain Safetynet passing. - Display details of boot.img (or init_boot.img for Pixel 7 / 7 Pro).
- SHA1 checksum.
- Origin (file it was extracted from).
- Whether it is patched or not, and if it is patched.
- What version of Magisk was used to patch it.
- On what device it was patched.
- Date of patching.
- The SHA1 of the source boot.img file.
- Option to Live boot from a choice of boot.img or patched image.
- Flash just the boot / init_boot image.
- Choose to keep data or wipe data while flashing.
- Ability to flash even if multiple devices are connected to the computer.
- Option to flash to inactive slot.
- Display information about the phone.
- ID
- Hardware model.
- Device architecture.
- Current installed firmware (build).
- If it is rooted with Magisk.
- Magisk version (Magisk Tools).
- Magisk Manager version (the app).
- List installed Magisk modules.
- Connection mode (Adb | Fastboot | Sideload | Recovery).
- Bootloader version.
- Active slot.
- Android OS API version.
- Convenient quick links to download Android platform tools or device firmware.
- Magisk Manager installation UI, screenshot. Supported versions:
- stable (official)
- beta (official)
- canary (official)
- debug (official)
- alpha
- delta
- special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
- Magisk Backup Manager, screenshot.
- 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.
- Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
- Name
- Version
- Description
- Enabled / Disabled.
- Display Android Platform Tools (SDK) version and warn / block if the version is old.
- Install APK (an app) file from the computer onto the device.
- Advanced features are hidden to keep the interface simple and easy to follow.
- A lot of checks and validations for smooth operation.
- Automatic check for program updates.
- Package (Application) Manager, screenshot:
- Disable (Freeze)
- Enable
- Uninstall
- Install APK
- Download APK
- Multi-Select
- Show Package Details.
- The ability to flash custom ROM (with or without patching boot.img)
- Option to flash to both slots.
- Option to flash to inactive slot.
- Options to disable verity and or verification.
- Ability to change the active slot.
- Ability to live boot to custom boot.img (temporary root).
- Ability to boot to recovery.
- Ability to flash custom image: boot, recovery, radio, kernel, ...
- Ability to sideload an image.
- Lock / Unlock bootloader.
- Option to gain temporary root (good for testing or checking things out).
- SOS Disable Magisk modules to get out of bootloop (experimental).
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.
Troubleshooting:
- See this post.
- Generate Sanitized support.zip file (File Menu) and submit that with your report.
28New 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.
14New 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.
14New Release:
Nov 09, 2022 v4.4.0 release
- New feature: Font and Font size should be configurable by the user #33
- New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
Handy to access a device remotely.
Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
I personally use this to test patching on remote devices, and also use it to access / install apps to my watch. - Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
- Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
- Minor UI Improvements
- If Magisk does not create a backup attempt to trigger Magisk to create one.
- Update readme to include Pixel 7 / 7P specific info.
13Pre-Release:
Oct 13, 2022 v4.2.0 pre-release
- Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
- Added Pixel 7 / 7p partitions flashing options to custom flash.
- Improved patching process using boot_patch, add more patch file validations.
- Check for Magisk backup and trigger Magisk to backup if missing.
- Add more logging messages for troubleshooting.
- Code optimization / improvements.
- Bug Fix #28 Error when opening download link without a device selected.
- Added set_version script to easily set the product version.
- Print path of the selected boot to console, for easy copy / paste.
New posts
-
-
-
-
X96 mini RK3228A firmware needed ?
- Latest: yasaraslanovy
