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

[krakout]

I'm not sure what you mean by Magisk button.
The one in PF that installs Magisk Manager?


You should never install Magisk when you have one hidden, this is a known issue, the two fight with each other, and when you boot, Magisk might report that it is not rooted, even though root action work.

Yes, that button

I understand what you're saying (similar issues arise when you first install Delta), but I didn't get that far, was just trying to patch the image

 

[badabing2003]

Yes, that button

I understand what you're saying (similar issues arise when you first install Delta), but I didn't get that far, was just trying to patch the image

That button installs Magisk on the phone, the apk.
As you may already know, Magisk is two parts.
The core / daemon (which you flash)
The Manager, which is what you install with that button.
You use the manager to create a patch, or the daemon.

PF gives this warning when you attempt to install Magisk Manager

"WARNING! Do not install magisk if you already have a hidden (stub) Magisk installed.\nFirst unhide Magisk before attempting an install."

You should never install multiple versions of Magisk, specially if one is hidden.
Best is to unhide then uninstall then install another.

 

[TheLizardMonkey]

Successful upgrade to March feature drop,

Magisk: 25200
Platform Tools: 33.0.3
PF: 4.8.1.0
Factory Image: 13.0.0 (TQ2A.230305.008.C1, Mar 2023)

Flash took about 5 minutes.

Thanks to everyone here and the creator of the tool.

 

[OzBoy1]

@schmeggy929
Exactly what @Lughnasadh said, it's a personal choice, I alternate each month, mainly because of like to keep the two slots as close to each other as possible, even though only one remains useable.

@krakout You're not getting root on p7p ?


For starters you don't have to keep logs, or try again to get logs, PF records them, so you can just start PF and generate the sanitized zip by clicking on the support button.
I suspect a Magisk moduls is causing the bootloop, if you provide the support file I can confirm the hypothesis and provide you the steps to fix it, it if it is something else support file would tell me where things went wrong.

Quick Edit, I see @badabing2003 asked the same question but I suspect it's the version of Magisk you're using. Try flashing with Stable and see how that works

I had deactivated the modules before flashing, using stable Magisk 25.2 (25200). I saw your post, fired up FP, processed firmware, patched boot file, flashboot the patched file, bootloop. Flashed the original init boot file and back up. Attached are the support files. Thank you so much for all your help.

I uninstalled Magisk and reinstalled thinking this may help...it didn't.

Thanks again everyone appreciate your help.

 

[Beefheart]

Are you rooted?

I am.

 

[SirRhor]

I have made a terrible mistake. Earlier today I flashed stock on a Pixel 3XL (crosshatch).
After that, I wanted to try AncientOS on my Pixel 7 Pro but because I got distracted at work, I ended up flashing the Pixel 3XL ROM on the 7 Pro. Pixel Flasher even warned me about but I did not paid enough attention.
Now the Pixel 7 Pro does not turn on.

Any way to revive it or any ideas on what I might try please?.


Thank you.

 

[krakout]

Try the following.
Uninstall Magisk
Flash stock, keep data (choose the unpatched boot in PF)
Install stable Magisk (you can do this in PF)
Create a patch of init_boot (you can do this in PF)
Flash just the patched boot. Flash Boot button in PF
If it does not work, provide a support file.

All the steps are required, don't skip any.

So I'm hopefully going to try this list today, just to make sure: these steps refer to my current ROM version, right? And *after* I complete this successfully I should try to install qrp3, correct?

[EDIT] Following these steps worked for "properly" rooting my device on the previous QRP beta, and now patching QRP3 was successful! Installed just fine and patched, finally!!!

So it seems I royally screwed up with using a hidden manager. I noticed that the warning about restoring the manager appears as a popup, perhaps that's why I had missed it?

Now the funny thing is, System Updater tells me there's an update to T3B1.230224.005, while About says I'm on... T3B1.230224.005. That's weird, anyone else seen this?

I'm sorry for taking up your time, and can't express how thankful I am for your support!!!

 

[HipKat]

I have made a terrible mistake. Earlier today I flashed stock on a Pixel 3XL (crosshatch).
After that, I wanted to try AncientOS on my Pixel 7 Pro but because I got distracted at work, I ended up flashing the Pixel 3XL ROM on the 7 Pro. Pixel Flasher even warned me about but I did not paid enough attention.
Now the Pixel 7 Pro does not turn on.

Any way to revive it or any ideas on what I might try please?.


Thank you.

I highly doubt it.
Warnings happen for a reason - life lesson!

 

[badabing2003]

I had deactivated the modules before flashing, using stable Magisk 25.2 (25200). I saw your post, fired up FP, processed firmware, patched boot file, flashboot the patched file, bootloop. Flashed the original init boot file and back up. Attached are the support files. Thank you so much for all your help.

I uninstalled Magisk and reinstalled thinking this may help...it didn't.

Thanks again everyone appreciate your help.

On March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.

I don't see anywhere that you disabled modules, and tried to flash again? stock? why?

I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.

So you flashed stock, and created a patch and tried to flash just the patched boot?
Are you bootlooping after that or just the phone is in bootloader mode?
I don't see it in the logs.

You've paid attention to this note right?

Note: The device is intentionally kept in bootloader mode
in case you want to flash or do more things before booting to system.
You can reboot to system by pressing the button in PixelFlasher, or on your phone.

I have made a terrible mistake. Earlier today I flashed stock on a Pixel 3XL (crosshatch).
After that, I wanted to try AncientOS on my Pixel 7 Pro but because I got distracted at work, I ended up flashing the Pixel 3XL ROM on the 7 Pro. Pixel Flasher even warned me about but I did not paid enough attention.
Now the Pixel 7 Pro does not turn on.

Any way to revive it or any ideas on what I might try please?.


Thank you.

Sorry for your troubles, that stings.

If you cannot get into bootloader or recovery, I'm afraid this is a hard brick, and I don't believe anyone has ever revived a hard-bricked Pixels.

Let us know if find a solution.

 

[Slim2none4u]

I have made a terrible mistake. Earlier today I flashed stock on a Pixel 3XL (crosshatch).
After that, I wanted to try AncientOS on my Pixel 7 Pro but because I got distracted at work, I ended up flashing the Pixel 3XL ROM on the 7 Pro. Pixel Flasher even warned me about but I did not paid enough attention.
Now the Pixel 7 Pro does not turn on.

Any way to revive it or any ideas on what I might try please?.


Thank you.

If you hold Power and Volume down for like 30 seconds or so does it take you to bootloader?
I did this very thing and was able to revive my Pixel. I just cant remember what it was now that i did. Pretty sure i had to hold those buttons for like a minute and eventually it booted to bootloader.
Good luck bro!

 

[OzBoy1]

On March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.

The logs may show this but the phone doesn't. I disabled the modules via PF on my very first flash back on the 17th.
I don't see anywhere that you disabled modules, and tried to flash again? stock? why?
As the phone was in a boot loop if I flashed stock I could boot up, just no root. I have flashed probably around 6 or 7 times since then.

I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.
It removes the battery icon.

So you flashed stock, and created a patch and tried to flash just the patched boot? Yes
Are you bootlooping after that or just the phone is in bootloader mode? Once I flash the patched boot i end up in a boot loop.
I don't see it in the logs.

You've paid attention to this note right? Yes, however I am not sure of the intent of this question, without further clarification of your intent I am not sure this answers your question the way you are asking.

Thanks for the above I hope I have clarified the points you are asking about.

 

[Homeboy76]

On March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.

The logs may show this but the phone doesn't. I disabled the modules via PF on my very first flash back on the 17th.
I don't see anywhere that you disabled modules, and tried to flash again? stock? why?
As the phone was in a boot loop if I flashed stock I could boot up, just no root. I have flashed probably around 6 or 7 times since then.

I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.
It removes the battery icon.

So you flashed stock, and created a patch and tried to flash just the patched boot? Yes
Are you bootlooping after that or just the phone is in bootloader mode? Once I flash the patched boot i end up in a boot loop.
I don't see it in the logs.

You've paid attention to this note right? Yes, however I am not sure of the intent of this question, without further clarification of your intent I am not sure this answers your question the way you are asking.

Thanks for the above I hope I have clarified the points you are asking about.

Stand alone Clock, Battery Icon Gone, etc. Mods - Thread starter: Tulsadiver
Tulsadiver Mod may need updating for the March 2023 firmware update.

 

[OzBoy1]

Stand alone Clock, Battery Icon Gone, etc. Mods - Thread starter: Tulsadiver
Tulsadiver Mod may need updating for the March 2023 firmware update.

Ok, how do I do that without root?

 

[Homeboy76]

Ok, how do I do that without root?

First, Boot Safe Mode on your phone. After, Safe Mode boots up, reboot.
Second, repatch the March 2023 init_boot.img.
Third, flash the NEW repatch March 2023 init_boot.img.

Do you have root?

If yes, install your Magisk modules individually and reboot after each module.

If a module does not install or work, that module needs updating.

 

[OzBoy1]

First, Boot Safe Mode on your phone. After, Safe Mode boots up, reboot.
Second, repatch the March 2023 init_boot.img.
Third, flash the NEW repatch March 2023 init_boot.img.

Do you have root?

If yes, install your Magisk modules individually and reboot after each module.

If a module does not install or work, that module needs updating.

If I flash init_boot.img I go into boot loop. No, I don't have root. Can't install modules as don't have root and can't flash init_boot.img without going into boot loop.

Any other suggestions?

 

[badabing2003]

On March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.

The logs may show this but the phone doesn't. I disabled the modules via PF on my very first flash back on the 17th.
I don't see anywhere that you disabled modules, and tried to flash again? stock? why?
As the phone was in a boot loop if I flashed stock I could boot up, just no root. I have flashed probably around 6 or 7 times since then.

I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.
It removes the battery icon.

So you flashed stock, and created a patch and tried to flash just the patched boot? Yes
Are you bootlooping after that or just the phone is in bootloader mode? Once I flash the patched boot i end up in a boot loop.
I don't see it in the logs.

You've paid attention to this note right? Yes, however I am not sure of the intent of this question, without further clarification of your intent I am not sure this answers your question the way you are asking.

Thanks for the above I hope I have clarified the points you are asking about.

You might believe you had all the modules disabled when your bootloops started, but the logs don't lie, they can't be there out of thin air.
Yes I see earlier on March 18, your were on December release and had only 3 modules which you disabled

Selected Device on 2023-02-18 08:58:46:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.221205.011
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:         
    Magisk Path:                     None
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              1384d5ad7ee8ca37ad0de2b20ca44dd2a4d8bc0a
    Magisk Modules:
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.5 (6649)

Opening Magisk Modules Manager ...
2023-02-18 09:01:41 User Pressed Ok.
Module: Systemless Hosts                     state has changed,       DISABLING the module ...
Disabling magisk module hosts ...
Module: Universal SafetyNet Fix              state has changed,       DISABLING the module ...
Disabling magisk module safetynet-fix ...
Module: Zygisk - LSPosed                     state has not changed,   Nothing to do. [Kept DISABLED]

And flashed February image. (first you did a dry run before flashing)
At, 9:19 you were rooted on February release
You had 5 modules, 3 of which enabled.

Selected Device on 2023-03-18 09:19:36:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230205.002
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9288096
    Magisk Manager Version:         
    Magisk Path:                     None
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              5657f3ea760bb2201873f67c89d000ff1491ef4f
    Magisk Modules:
        AOSP Mods (Full version)            disabled  2.6.0
        Tulsadiver Remove Battery Icon      enabled   v1
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.6 (6712)

You disabled the modules

Opening Magisk Modules Manager ...
2023-03-18 09:22:53 User Pressed Ok.
Module: AOSP Mods (Full version)             state has not changed,   Nothing to do. [Kept DISABLED]
Module: Tulsadiver Remove Battery Icon       state has changed,       DISABLING the module ...
Disabling magisk module Tulsadiver_Mods_For_Removing_Battery ...
debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/Tulsadiver_Mods_For_Removing_Battery/disable'"
Module: Systemless Hosts                     state has changed,       DISABLING the module ...
Disabling magisk module hosts ...
debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/hosts/disable'"
Module: Universal SafetyNet Fix              state has changed,       DISABLING the module ...
Disabling magisk module safetynet-fix ...
debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/safetynet-fix/disable'"
Module: Zygisk - LSPosed                     state has not changed,   Nothing to do. [Kept DISABLED]

And flashed March release.
And yes you ran into issues and the phone was in recovery mode and then bootloader mode, but you eventually got it working rooted on March release at 9:57 with 3 modules enabled.

Selected Device on 2023-03-18 09:57:33:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:         
    Magisk Path:                     /data/app/~~tskLuhNaN-GZpri7UAu57w==/com.topjohnwu.magisk-KsKj7DnmAFYjEc12NvGP4g==/base.apk
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        AOSP Mods (Full version)            disabled  2.6.0
        Tulsadiver Remove Battery Icon      enabled   v1
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.6 (6712)

But you kept on flashing again, I don't understand why

==============================================================================
 2023-03-18 09:58:28 PixelFlasher 4.8.1.0              Flashing Phone   
==============================================================================
Android Platform Tools Version: 33.0.3-8952118

You tried more flashing, you even loaded Raven image (not sure why)
and again you were in good state at 10:30

Selected Device on 2023-03-18 10:30:19:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:         
    Magisk Path:                     None
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        AOSP Mods (Full version)            disabled  2.6.0
        Tulsadiver Remove Battery Icon      enabled   v1
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.6 (6712)

And again at 10:34

Selected Device on 2023-03-18 10:34:20:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:          25.2:25200
    Magisk Path:                     /data/app/~~rSGL9RijF_SWcyOpJ_655w==/com.topjohnwu.magisk-YM6wK9dkpKoVR4WDuGf_qg==/base.apk
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        AOSP Mods (Full version)            disabled  2.6.0
        Tulsadiver Remove Battery Icon      enabled   v1
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.6 (6712)

Tell me, are you flashing multiple phones?
Because this cycle of being in good state and then flashing again kept on going.

==============================================================================
 2023-03-18 10:36:46 PixelFlasher 4.8.1.0              Flashing Phone   
==============================================================================
Android Platform Tools Version: 33.0.3-8952118
2023-03-18 10:36:46 Flashing device REDACTED ...

Selected Device on 2023-03-18 11:00:00:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:          25.2:25200
    Magisk Path:                     /data/app/~~rSGL9RijF_SWcyOpJ_655w==/com.topjohnwu.magisk-YM6wK9dkpKoVR4WDuGf_qg==/base.apk
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        AOSP Mods (Full version)            disabled  2.6.0
        Tulsadiver Remove Battery Icon      enabled   v1
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0-MOD_1.2
        Zygisk - LSPosed                    disabled  v1.8.6 (6712)

This was the last time your phone was rooted and in good state, and had 3 modules enabled.
But then you flashed again stock (SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d)

==============================================================================
 2023-03-18 11:01:18 PixelFlasher 4.8.1.0              Flashing Phone   
==============================================================================

Which booted to an unrooted state (as expected)

Selected Device on 2023-03-18 11:08:08:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:         
    Magisk Path:                     None
        Checked for Package:         com.topjohnwu.magisk

And finally this today

Which basically an attempt to flash a patched image (
730259795e63e29e940e851f309a9f7761cca8da)
, and then another attempt to patch stock image.

Probably because you are bootlooping, but please realize that the last state before your flashed stock, was a rooted phone on March release with 3 active modules.
Unless of course these are logs from different devices..

It's not uncommon to think that the phone is in a particular state (example modules disabled) but it actually is not, it happens to all of us, just peruse the thread and see the mistakes we make, myself included.

to recover from a bootloop caused by Magisk modules you can do the following.

Unhide + Uninstall Magisk Manager
Click on Magisk installer button and choose the special Magisk

You can read the notes
and follow the steps.
When you create a patch with this special Magisk, you get root, but modules will not be loaded.
This gives you a chance to disable the modules reboot and then apply the normal Magisk patch

Good luck.

 

[Homeboy76]

If I flash init_boot.img I go into boot loop. No, I don't have root. Can't install modules as don't have root and can't flash init_boot.img without going into boot loop.

Any other suggestions?

No, see the post below yours.

 

[Fishawy]

to recover from a bootloop caused by Magisk modules you can do the following.

Unhide + Uninstall Magisk Manager
Click on Magisk installer button and choose the special Magisk
View attachment 5867339

You can read the notes
and follow the steps.
When you create a patch with this special Magisk, you get root, but modules will not be loaded.
This gives you a chance to disable the modules reboot and then apply the normal Magisk patch

Good luck.

I didn't even know such thing existed. Thank you so much for this! It helps to know that there's a backup option - next to safe mode - to recover bootloops and repatch at the same time.

 

[krakout]

I hadn't noticed the special Magisk option either! But how do you unhidde if you're in a bootloop?

 

[simplepinoi177]

I didn't even know such thing existed. Thank you so much for this! It helps to know that there's a backup option - next to safe mode - to recover bootloops and repatch at the same time.

I hadn't noticed the special Magisk option either! But how do you unhidde if you're in a bootloop?

If it ever comes up for you guys that a bootloop happens because of a Magisk module, there's also the option to running the adb command: adb wait-for-device shell magisk --remove-modules so that it doesn't erase everything set up in Settings like it does in Safe Mode (supposedly from what I've read, haven't experienced it myself). You'll have to re-install all the modules, but for most people that's more preferable than re-initializing and setting up everything in Settings...

But I, too, am fascinated by the "Special Magisk" build!