Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

[jimlightner]

I was 99% sure that was the answer I was going to get .. thanks for taking the time and explaining it in more detail..

 

[CiihanGiir]

Does the WIPE all data option also remove root?

 

[Blade22222]

Does the WIPE all data option also remove root?

Yes if you flash the stock non patched image. Will leave device like you just bought it.

 

[innit]

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]

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.

 

[innit]

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.

[Discussion] Magisk alpha/alpha-lite forks by @vvb2060 Support

This is the spot for general support of Magisk alpha/alpha-lite forks "Public Releases" by @vvb2060. Disclaimer: This Magisk alpha fork is not supported by @topjohnwu and is not an official channel for him. I am not responsible for any damage to...

forum.xda-developers.com

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?

 

[badabing2003]

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.

 

[innit]

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.

 

[badabing2003]

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

 

[innit]

sounds like you have a corruption

What does it mean exactly?

 

[Slim2none4u]

What does it mean exactly?

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.

 

[innit]

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?

 

[innit]

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.

This worked thanks a lot to you, @badabing2003, @Homeboy76 , @Lughnasadh and everyone else who tried to help.

 

[innit]

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.

 

[badabing2003]

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.

 

[innit]

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]

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.

 

[alexx096]

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

 

[badabing2003]

the link leads to 4.6.1

Thanks, fixed.
I'll go fix the other threads.

 

[krakout]

Another flawless update to b3 today... thanks again