Is you bootloader unlocked which would let you fastboot/flash the image.I updated my Pixel 9 pro XL to December using the latest version of Pixelflasher. Unlike prior months, the update ended with my phone just showing "G" for some time and won't reboot. Have I bricked my phone?
Yes bootloader is unlocked and I installed Magisk as soon as I got the phone as alwaysIs you bootloader unlocked which would let you fastboot/flash the image.
I don't seem to get past the No Command error.I would try flashing the update file. Remove -w to avoid a wipe
You did not say anything about a No Command error previously. No one can help you until you provide all the details about what you did to receive that No Command error.
Understood. I have a Pixel 9 Pro XL rooted with Magisk. I've had Pixels since the first one and always rooted them with no problem. I got this one in the spring and have been flashing the monthly updates with Pixelflasher with no problem. Today I did y normal update for December. I went into ADB and all seemed fine, but at the end the phone wouldn't boot. It just has a "G" on the screen and gets hot. I have tried a variety of things. I got it into recovery mode and selected update with ADB. I connected the phone to my laptop and ran Pixelflasher again and it seems to progress normally but will not reboot into anything other than the "G". I also selected wiping the phone but that didn't help. Is there an app somewhere that will unbrick the phone?You did not say anything about a No Command error previously. No one can help you until you provide all the details about what you did to receive that No Command error.
I would suggest you head over to the PixelFlasher thread and submit a support zip for badabing to look at. He will be able to tell a lot about the current state of your device, what you did, etc...Understood. I have a Pixel 9 Pro XL rooted with Magisk. I've had Pixels since the first one and always rooted them with no problem. I got this one in the spring and have been flashing the monthly updates with Pixelflasher with no problem. Today I did y normal update for December. I went into ADB and all seemed fine, but at the end the phone wouldn't boot. It just has a "G" on the screen and gets hot. I have tried a variety of things. I got it into recovery mode and selected update with ADB. I connected the phone to my laptop and ran Pixelflasher again and it seems to progress normally but will not reboot into anything other than the "G". I also selected wiping the phone but that didn't help. Is there an app somewhere that will unbrick the phone?
Okay I'll try that . Thanks for responding.I would suggest you head over to the PixelFlasher thread and submit a support zip for badabing to look at. He will be able to tell a lot about the current state of your device, what you did, etc...
Sounds like you may have an incompatible Magisk mod, but he'll be able to tell more with that support zip.
For just this device?Magisk does not work with Android 16 QPR2, you have to unroot and wait for magisk to be updated or use apatch, kernel su, kernel-su next or something other.
no
Hmm, Magisk Stable 30.6 working fine for me on both my Pixel 7 and 8 Pros on A16 QPR2 stable. Was also working with the latest beta (A16 QPR2 Beta 3.3).no
for android 16 qpr2
It has been broken since android 16 qpr beta 2
Then the OP needs to update to magisk 30.6Hmm, Magisk Stable 30.6 working fine for me on both my Pixel 7 and 8 Pros on A16 QPR2 stable. Was also working with the latest beta (A16 QPR2 Beta 3.3).
The issue was with the last version of Magisk. It was not compatible with the December update. I sure wish I knew that before my phone got wioed. I finally got it up and running by flashing the unrooted December update. Thanks for your help!Can you get into Fastboot mode with
Vol down+Pwr?
If yes then Flash-all.bat from the December or November A16 update file.
Hmm, Magisk Stable 30.6 working fine for me on both my Pixel 7 and 8 Pros on A16 QPR2 stable. Was also working with the latest beta (A16 QPR2 Beta 3.3).no
for android 16 qpr2
It has been broken since android 16 qpr beta 2
You did not say anything about a No Command error previously. No one can help you until you provide all the details about what you did to receive that No Command error.
Okay I'll try that . Thanks for responding.I would suggest you head over to the PixelFlasher thread and submit a support zip for badabing to look at. He will be able to tell a lot about the current state of your device, what you did, etc...
Sounds like you may have an incompatible Magisk mod, but he'll be able to tell more with that support zip.
Hmm, Magisk Stable 30.6 working fine for me on both my Pixel 7 and 8 Pros on A16 QPR2 stable. Was also working with the latest beta (A16 QPR2 Beta 3.3).no
for android 16 qpr2
It has been broken since android 16 qpr beta 2
You did not say anything about a No Command error previously. No one can help you until you provide all the details about what you did to receive that No Command error.
Okay I'll try that . Thanks for responding.I would suggest you head over to the PixelFlasher thread and submit a support zip for badabing to look at. He will be able to tell a lot about the current state of your device, what you did, etc...
Sounds like you may have an incompatible Magisk mod, but he'll be able to tell more with that support zip.