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

[Nekromantik]

You shouldn't have lost root, a simple oversight of selecting the stock boot instead of the patched boot after creating a patch and before hitting the flash button could cause that.
You'd think you wouldn't make a silly mistake like that, well I've got news for you, I did that mistake and lost root, and wondered if I had introduced a regression in the latest release, only checking the logs exposed my shortcomings.

I can take a look at you logs if you want.
Another possibility is that the last step in flashing is actually flashing the patch, if anything goes wrong during that, the phone will remain in stock state, not that something should go wrong, but anything is a possibility.

No need to look at logs
I am sure I did select the patched boot img as there were 2 there to choose from.
On March update if it happens again I will post logs

 

[viper8u2]

You shouldn't have lost root, a simple oversight of selecting the stock boot instead of the patched boot after creating a patch and before hitting the flash button could cause that.
You'd think you wouldn't make a silly mistake like that, well I've got news for you, I did that mistake and lost root, and wondered if I had introduced a regression in the latest release, only checking the logs exposed my shortcomings.

I can take a look at you logs if you want.
Another possibility is that the last step in flashing is actually flashing the patch, if anything goes wrong during that, the phone will remain in stock state, not that something should go wrong, but anything is a possibility.

Just noticed I lost root also, going to go back and reflash again, maybe I didn't select the patch?

**Edit I must have not selected the patched boot, just flashed again and all is good with root. Thanks again

 

[badabing2003]

Just noticed I lost root also, going to go back and reflash again, maybe I didn't select the patch?

Now I'm really curious, can you submit support.zip please?

 

[niko26]

@badabing2003, updating from Jan to Feb on P7P worked fine for me, preserving root.

 

[badabing2003]

@badabing2003, updating from Jan to Feb on P7P worked fine for me, preserving root.

Thanks, I'm pretty confident that there is no issue, as it worked for many.
But just to be sure that there is no corner case issue that I might have missed, I asked for the logs.

 

[viper8u2]

Now I'm really curious, can you submit support.zip please?

I edited my original post boss, I have a ton going on right now and my office is a mess, I went through and did everything but probably didn't select the patched boot when flashing, all good now, thank you

 

[EtherealRemnant]

I totally spaced it until now but here's the support.zip from when the patched boot image wasn't flashing. I hadn't used PixelFlasher on this computer since then so hopefully it's still useful.

I did just view the log myself and see that I did indeed select the correct patched file both times I tried to flash it and it reported it flashing successfully both times too yet for some reason, I still had to flash the same patched image manually to get root back.

 

[Slim2none4u]

I totally spaced it until now but here's the support.zip from when the patched boot image wasn't flashing. I hadn't used PixelFlasher on this computer since then so hopefully it's still useful.

I did just view the log myself and see that I did indeed select the correct patched file both times I tried to flash it and it reported it flashing successfully both times too yet for some reason, I still had to flash the same patched image manually to get root back.

Are you using Minimal ADB Fastboot?

 

[EtherealRemnant]

Are you using Minimal ADB Fastboot?

No. I have never used that garbage. I don't even understand why anyone ever did because it's not like adb and fastboot are massive programs.

Also, if I was, I wouldn't have been able to manually flash either.

 

[miimaa]

I also lost root updating from December to January a week ago. I used the newest version of Pixel Flasher.

I'm 99 % sure I did everything right. And that's why I was pretty confused of what happened. One percent of me was afraid that I was a noob and didn't dare mention it.

I didn't save the logs.

 

[badabing2003]

I totally spaced it until now but here's the support.zip from when the patched boot image wasn't flashing. I hadn't used PixelFlasher on this computer since then so hopefully it's still useful.

I did just view the log myself and see that I did indeed select the correct patched file both times I tried to flash it and it reported it flashing successfully both times too yet for some reason, I still had to flash the same patched image manually to get root back.

Thanks for the support file, there is not enough data in your logs to conclude anything.
All I see in there is that you boot flashing, not the full factory flashing.
And yes you selected the patched image, but the logs don't display if flash to inactive slot was selected or not, that's an oversight on my side, I will add that to the logs so that we can tell.
If that option was selected, then definitely rebooting to system would not have been rooted.

Furthermore your logs don't include anything after flashing, meaning that I don't see it in adb mode loaded to say if it was rooted or not.

I also lost root updating from December to January a week ago. I used the newest version of Pixel Flasher.

I'm 99 % sure I did everything right. And that's why I was pretty confused of what happened. One percent of me was afraid that I was a noob and didn't dare mention it.

I didn't save the logs.

Please, get me the logs, I need to look into this, you don't have to save the logs, PF does it for you, and it is already saved.
Just launch PF, go to help menu and select Create a Santized support.zip
That's all, and you can close PF
And don't worry leaking sensitive information, PF sanitizes the logs and removes any sensitive information like device ID, username ...

Thanks, logs go a long way towards making this tool more robust and reliable.

 

[miimaa]

Thanks for the support file, there is not enough data in your logs to conclude anything.
All I see in there is that you boot flashing, not the full factory flashing.
And yes you selected the patched image, but the logs don't display if flash to inactive slot was selected or not, that's an oversight on my side, I will add that to the logs so that we can tell.
If that option was selected, then definitely rebooting to system would not have been rooted.

Furthermore your logs don't include anything after flashing, meaning that I don't see it in adb mode loaded to say if it was rooted or not.


Please, get me the logs, I need to look into this, you don't have to save the logs, PF does it for you, and it is already saved.
Just launch PF, go to help menu and select Create a Santized support.zip
That's all, and you can close PF
And don't worry leaking sensitive information, PF sanitizes the logs and removes any sensitive information like device ID, username ...

Thanks, logs go a long way towards making this tool more robust and reliable.

Here you go buddy. Hope this helps.

If I'm a total noob, don't mention it.

 

[badabing2003]

Here you go buddy. Hope this helps.

If I'm a total noob, don't mention it.

Thanks

Observations:
The logs show that on February 1st, you ran PF 4.6.1.0 (not the latest today)
With an unsupported older Platform tools

2023-02-01 19:26:05 ERROR: Detected older Android Platform Tools version 30.0.1-6435776
2023-02-01 19:26:10 User accepted older version 30.0.1-6435776 of Android platform tools.
SDK Version: 30.0.1-6435776

And flashed the January image cheetah-tq1a.230105.002
Selecting the unpatched boot

Boot image:             59363c5b / 59363c5b

Notice how both sha1 values are the same.
It should have showed this on one side

SHA1 of magisk_patched_59363c5b.img file: 72da70ccd63f413e6eb5db8c5b853f98a52f42c6

Can you please update the platform tools (just click the link in PF to get the latest)
You should also update PF.

You can choose to just flash the patched boot from January, or full January or even better go full February.

 

[EtherealRemnant]

Thanks for the support file, there is not enough data in your logs to conclude anything.
All I see in there is that you boot flashing, not the full factory flashing.
And yes you selected the patched image, but the logs don't display if flash to inactive slot was selected or not, that's an oversight on my side, I will add that to the logs so that we can tell.
If that option was selected, then definitely rebooting to system would not have been rooted.

Furthermore your logs don't include anything after flashing, meaning that I don't see it in adb mode loaded to say if it was rooted or not.


Please, get me the logs, I need to look into this, you don't have to save the logs, PF does it for you, and it is already saved.
Just launch PF, go to help menu and select Create a Santized support.zip
That's all, and you can close PF
And don't worry leaking sensitive information, PF sanitizes the logs and removes any sensitive information like device ID, username ...

Thanks, logs go a long way towards making this tool more robust and reliable.

Maybe disable flash to inactive slot when flashing boot image only? Or at least prompt if it's selected warning that it won't work if you're not updating the phone at the same time? I am pretty sure I didn't have flash to inactive slot selected but I was in a hurry to run out the door so it's possible.

 

[badabing2003]

Maybe disable flash to inactive slot when flashing boot image only? Or at least prompt if it's selected warning that it won't work if you're not updating the phone at the same time? I am pretty sure I didn't have flash to inactive slot selected but I was in a hurry to run out the door so it's possible.

Actually you had it selected.
I just checked the logs before flashing, and after flashing.
You had this

    "flash_to_inactive_slot": true,

Knowing that PF logs it when you change it, I can safely assume that while flashing it must have been set.

In future release I might block that choice when doing boot flashing.

 

[miimaa]

Thanks

Observations:
The logs show that on February 1st, you ran PF 4.6.1.0 (not the latest today)
With an unsupported older Platform tools

2023-02-01 19:26:05 ERROR: Detected older Android Platform Tools version 30.0.1-6435776
2023-02-01 19:26:10 User accepted older version 30.0.1-6435776 of Android platform tools.
SDK Version: 30.0.1-6435776

And flashed the January image cheetah-tq1a.230105.002
Selecting the unpatched boot

Boot image:             59363c5b / 59363c5b

Notice how both sha1 values are the same.
It should have showed this on one side

SHA1 of magisk_patched_59363c5b.img file: 72da70ccd63f413e6eb5db8c5b853f98a52f42c6

Can you please update the platform tools (just click the link in PF to get the latest)
You should also update PF.

You can choose to just flash the patched boot from January, or full January or even better go full February.

4.6.1.0 was the latest at the time. I just updated to that version before I flashed the update.

So was it me doing something wrong or something else?

I will update the Pixel Flasher and flash the February firmware tomorrow.

 

[miimaa]

Just wanted to post as this was the 2nd time I've used the tool and everything went flawless. Up and running in approximately 10 minutes. Thank you for making the monthly update process so easy.

If it helps anybody, below are the steps I use:

1) Download SDK Platform Tools and extract to desktop
2) Download monthly factory image
3) Download updated version of PixelFlasher
4) Uncheck all magisk modules on phone
5) Open PixelFlasher, select Platform Tools, select device, select factory image, process the firmware file and extract the boot image. Patch the boot img and then select patched img, check "Keep Data" and "Flash to inactive slot" and then "Flash Pixel Phone"
6) Let it do it's thing, boot up, open Magisk, re-check modules and restart phone
7) Success! Enjoy updated phone with exact same setup as 10 minutes prior.

These are the instructions I've been using while flashing with Pixel Flasher. Success two times and the third was when I lost the root.

 

[badabing2003]

4.6.1.0 was the latest at the time. I just updated to that version before I flashed the update.

So was it me doing something wrong or something else?

I will update the Pixel Flasher and flash the February firmware tomorrow.

You selected the stock boot instead of patched boot before hitting the flash button.
You should also always use the latest platform tools.

 

[badabing2003]

These are the instructions I've been using while flashing with Pixel Flasher. Success two times and the third was when I lost the root.

1- you don't have to do it each time if it is current, PF will tell you if it is or not

Your steps are good, you just missed this part and then select patched img

 

[miimaa]

1- you don't have to do it each time if it is current, PF will tell you if it is or not

Your steps are good, you just missed this part and then select patched img

Thanks for the info! I will try again tomorrow.

And thank you very much for your good work! I'm an old school recovery-flasher since Android 2.3. Adb and coding is cryptonite to me and that's why your software has been a lifesaver for me.