Themes / Apps / Mods ðŸ“³ðŸ”¥PixelFlasher for Google Pixel 7 Pro Support Thread.

Search This thread
Hi. Can anyone help? I`m new to pixel and after updating magisk (I chose ``direct install`` in magisk app) my phone is stuck in a bootloop. I don``t want to lose data though so could I just reflash factory image with ``Keep data`` ticked on? Would that be enough?

I`ve already tried flashing stock boot.img & init_boot.img to both slots hoping it would work but it didn`t.

Bootloader unlocked, verity and verification were disabled prior to the bootloop.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,873
2,460
Hi. Can anyone help? I`m new to pixel and after updating magisk (I chose ``direct install`` in magisk app) my phone is stuck in a bootloop. I don``t want to lose data though so could I just reflash factory image with ``Keep data`` ticked on? Would that be enough?

I`ve already tried flashing stock boot.img & init_boot.img to both slots hoping it would work but it didn`t.

Bootloader unlocked, verity and verification were disabled prior to the bootloop.
What version of Magisk you were on and what did you update it to?
Did you have any Magisk modules enabled?

If you already flashed stock boot.img and init_boot.img to both slots and you did it correctly, then I don't see how you got into a bootloop by just direct flashing in Magisk, because flashing stock would have reverted that.
So let's assume that you didn't do it properly considering you're new to this.

You can factory flash in PF , make sure you select keep data, start with stock (don't select a patched image)
If you boot normal, you can then just flash the patched img and be rooted.
 
What version of Magisk you were on and what did you update it to?
Did you have any Magisk modules enabled?

If you already flashed stock boot.img and init_boot.img to both slots and you did it correctly, then I don't see how you got into a bootloop by just direct flashing in Magisk, because flashing stock would have reverted that.
So let's assume that you didn't do it properly considering you're new to this.

You can factory flash in PF , make sure you select keep data, start with stock (don't select a patched image)
If you boot normal, you can then just flash the patched img and be rooted.

Yes I flashed boot.img to boot & init_boot.img to init_boot to both slots but phone reboots after sitting on Google logo for a minute or so. I can't even access recovery or rescue mode. Only fastboot (bootloader) is accessible.



I've been using this Magjsk Alpha for over a year without issuses on Samsung devices and it run fine on Pixel too until today when I decided to update it from 44643ad7-alpha (25205) to 6ecc04a4-alpha (25206) and it ended up in a bootloop.

Galaxy Tab S8+ with 6ecc04a4 works but Pixel doesn't. Magisk & LSPosed modules without the red X were installed on Pixel.



Should I only choose "Keep data" or "Disable verity & disable verification" as well? Should I tick "Flash to both slots" too?
 

Attachments

  • Screenshot_20230130_194746.jpg
    Screenshot_20230130_194746.jpg
    902.1 KB · Views: 46
  • Screenshot_20230130_195124.jpg
    Screenshot_20230130_195124.jpg
    391.3 KB · Views: 46
  • Wow
Reactions: HipKat

badabing2003

Recognized Contributor
Sep 17, 2012
1,873
2,460
I've been using this Magjsk Alpha for over a year without issuses on Samsung devices and it run fine on Pixel too until today when I decided to update it from 44643ad7-alpha (25205) to 6ecc04a4-alpha (25206) and it ended up in a bootloop.

Galaxy Tab S8+ with 6ecc04a4 works but Pixel doesn't. Magisk & LSPosed modules without the red X were installed on Pixel.
Sound like an issue with Magisk Alpha or a conflict with one of the modules.
But flashing stock and still not working suggests that something else got corrupted, which shouldn't happen, hence why I said if you flashed it correctly, then it would be an issue in Magisk Alpha.

Should I only choose "Keep data" or "Disable verity & disable verification" as well? Should I tick "Flash to both slots" too?
I would disable modules.
Keep Data
Flash to both slots. Inactive Slot
Are you using custom ROM? did you Disable Verity / Verification previously? if you're on stock, then don't select them, otherwise you will wipe your data, on the other hand if you had previously selected those, then you want to select again.
 
Last edited:
  • Like
Reactions: Slim2none4u
Sound like an issue with Magisk Alpha or a conflict with one of the modules.
But flashing stock and still not working suggests that something else got corrupted, which shouldn't happen, hence why I said if you flashed it correctly, then it would be an issue in Magisk Alpha.


I would disable modules.
Keep Data
Flash to both slots.
Are you using custom ROM? did you Disable Verity / Verification previously? if you're on stock, then don't select them, otherwise you will wipe your data, on the other hand if you had previously selected those, then you want to select again.
I used stock rom with verity & verification disabled so I must select both options again, right?

Using the commands below didn't make a difference. Phone won't boot past the Google logo.

fastboot --slot all flash boot boot.img
fastboot --slot all flash init_boot init_boot.img

Will try to reflash stock firmware.
 

Attachments

  • 20230130_202025.mp4
    142.5 MB · Views: 0
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,873
2,460
I used stock rom with verity & verification disabled so I must select both options again, right?

Using the commands below didn't make a difference. Phone won't boot past the Google logo.

fastboot --slot all flash boot boot.img
fastboot --slot all flash init_boot init_boot.img

Will try to reflash stock firmware.
sounds like you have a corruption
 
I would flash full stock, saving data, change active slot and then flash full stock again. Make sure you are using the latest ADB SDK also and not Minimal ADB.
Will try it now and hope for the best.

Is it possible to pull files from the internal storage with adb with phone in fastboot (bootloader) mode?
 
Last edited:
Last edited:
sounds like you have a corruption
Some magisk module was causing the problem. After flashing stock & disabling all modules phone booted normallly.

The weird thing is that after flashing stock firmware I first flashed magisk alpha and it caused a bootloop again. Then I flashed magisk canary (topjohnwu) and phone booted normally without having to disablle the modules.
After that I disabled all modules and flashed back magisk alpha and this time no bootloop.
 
Last edited:
  • Like
Reactions: Slim2none4u

badabing2003

Recognized Contributor
Sep 17, 2012
1,873
2,460
Some magisk module was causing the problem. After flashing stock & disabling all modules phone booted normallly.

The weird thing is that after flashing stock firmware I first flashed magisk alpha and it caused a bootloop again. Then I flashed magisk canary (topjohnwu) and phone booted normally without having to disablle the modules.
After that I disabled all modules and flashed back magisk alpha and this time no bootloop.
Add your modules in alpha, one at a time and narrow it down which modules was the culprit.
Then bring it up to Magisk Alpha and the culprit module developers.
 
Add your modules in alpha, one at a time and narrow it down which modules was the culprit.
Then bring it up to Magisk Alpha and the culprit module developers.
Done it just now. AOSP Mods is causing bootloops on Alpha but works fine on Canary (topjohnwu). Will stick to original Magisk for now on Pixel.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,873
2,460
New 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.
 
Last edited:

alexx096

Senior Member
Nov 12, 2015
62
41
New 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.
the link leads to 4.6.1
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    New 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 latest adb that 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.
    6
    Thanks @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.
    6
    New 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
    Trying to dirty flash any factory image dated later than TD1A.220804.031 results in a bootloop

    I know it's neither a magisk nor modules issue as a non-patched boot.img results in the same issues and the only way to have the phone working again is fastboot flashing TD1A.220804.031 or TD1A.220804.009

    any ideas as to why this may be happening?

    edit: it essentially gets to the material you themed G logo then restarts
    @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
    PF_promo-banner.png

    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.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • 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.
    Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
    28
    New 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.
    14
    New 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.
    14
    New 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.
    13
    Pre-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.