📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

[deepak jr]

Hey there,
I just bricked my pixel 6 pro and i was wondering if you could somehow make pixel flasher show serial/com devices and flash bootloader from there? Also wanted to know if you could get a .tar version of the bootloader for the Pixel 6 pro.
Thanks )

 

[badabing2003]

Hey there,
I just bricked my pixel 6 pro and i was wondering if you could somehow make pixel flasher show serial/com devices and flash bootloader from there? Also wanted to know if you could get a .tar version of the bootloader for the Pixel 6 pro.
Thanks )

Sorry to hear about your problems.

How did you brick your phone?
were you using PF?
If so, please generate support.zip file so that I can take a look at what might have happened.
I'm not sure if I follow you about showing Serial / Com devices.
Your phone is detected as a serial device?, how did it end up like that?
What do you mean by getting tar version of bootloader?

 

[deepak jr]

Sorry to hear about your problems.

How did you brick your phone?
were you using PF?
If so, please generate support.zip file so that I can take a look at what might have happened.
I'm not sure if I follow you about showing Serial / Com devices.
Your phone is detected as a serial device?, how did it end up like that?
What do you mean by getting tar version of bootloader?

Sorry for being blunt but I didn't flash A13 on both slots and when the boot failed, it switched to A12 and bricked it. I tried everything but no luck. The only thing that shows this as a com device is an old odin (1.3.x). In order to flash bl using that I needed the.tar image of the bootloader. Hope it clears that.

 

[badabing2003]

Sorry for being blunt but I didn't flash A13 on both slots and when the boot failed, it switched to A12 and bricked it. I tried everything but no luck. The only thing that shows this as a com device is an old odin (1.3.x). In order to flash bl using that I needed the.tar image of the bootloader. Hope it clears that.

I doubt that it would work, but you can give this a try.
I think You can send it To Google and they would fix / replace it.
Lots of people have done that.

 

[deepak jr]

I doubt that it would work, but you can give this a try.
I think You can send it To Google and they would fix / replace it.
Lots of people have done that.

Unfortunately this didn't work :/
I did try sending it to Google but they denied it because the glue on the device was not original apparently xD

 

[badabing2003]

Unfortunately this didn't work :/
I did try sending it to Google but they denied it because the glue on the device was not original apparently xD

Really sorry to hear that, I find Google accountable for this mess, and they are denying to service a problem they created because of the glue not being original?
It sucks that you are left with an expensive brick.

 

[J.Michael]

Sorry for being blunt but I didn't flash A13 on both slots and when the boot failed, it switched to A12 and bricked it. I tried everything but no luck. The only thing that shows this as a com device is an old odin (1.3.x). In order to flash bl using that I needed the.tar image of the bootloader. Hope it clears that.

What is this A12 and A13 you have that do not include a bootloader?

If you have a bootloader image file, you can make a .tar file -- there's nothing special about the format. But Pixel is not Samsung, and Samsung is the only thing I've ever heard of using Odin and .tar files. Odin doesn't actually burn anything to the device, it just communicates with the download mode of the device -- which a non-Samsung device will not have the right one of.

How many times have you tried to boot? I thought there was a "failsafe" whereby after failing to boot some number of times, it would automatically switch slots. If the original problem was not flashing both slots, you might have a good boot in the other slot.

 

[deepak jr]

What is this A12 and A13 you have that do not include a bootloader?

If you have a bootloader image file, you can make a .tar file -- there's nothing special about the format. But Pixel is not Samsung, and Samsung is the only thing I've ever heard of using Odin and .tar files. Odin doesn't actually burn anything to the device, it just communicates with the download mode of the device -- which a non-Samsung device will not have the right one of.

How many times have you tried to boot? I thought there was a "failsafe" whereby after failing to boot some number of times, it would automatically switch slots. If the original problem was not flashing both slots, you might have a good boot in the other slot.

Google has apparently trips a efuse when theres A12 bootloader in one slot and A13 on the other and you manage to boot in A12 somehow. So kinda ****ed xD

 

[J.Michael]

Google has apparently trips a efuse when theres A12 bootloader in one slot and A13 on the other and you manage to boot in A12 somehow. So kinda ****ed xD

This thread, in amongst the doom and gloom, repeatedly has someone saying "try harder, and try for fastboot mode".

The cited post goes into more detail about how he thinks it can be done

 

[mohamed_emad10]

After I updated pixel 6 to android 13,​

phone doesn't work became bricked and I can't fix it because when I plug it into my computer and see the device manager in windows,​

but it is not detected by `adb devices` or `fastboot devices`.​

I see it detected in seconds and disappear by watching device manager as a " USB serial port device (COM 3)" in windows 11

in windows 7 & ubuntu detected as pixel CDC- ACM (Pixel ROM Recovery )device because devices manager in win7 can't find any driver compatible so it detected as itself in "Other devices"​

​

in VM box :

while I hold down the power button so I can't fix it,​

how to restore my phone and flash it in this mode I think this mode is EDL​

I tried to boot in bootloader by pressing press power + volume down and power + volume up and all together but nothing work , the phone is dead​

I have tried to fix by this post but unfortunately it doesn't work https://xdaforums.com/t/guide-unbrick-pixel-6-oriele-or-pixel-6-pro-raven.4441245/​

​

I have escalated this issue in google tracker since 2 months but i got NO ANSWER and NO HELP https://issuetracker.google.com/issues/243636259​

is anyone have any idea to fix my ? i will appreciate any try PLZ help me

 

[badabing2003]

@mohamed_emad10
Just scroll up above your post, the same thing is discussed literally on this same page.
Short of sending your phone to Google, I'm not aware of any success stories unbricking due to the ABR issue.

Oh by the way, it's not cool to post the same thing in multiple threads.
I wish you good luck, and if you ever manage to unbrick it without sending out to Google, please do share your story and method.

 

[krkhaha]

What's that mean verbose. Should I select that or no? I'd like to keep unlock bootloader, disable Verity, disable verification. What options should I select and deselect? Thank you.

 

[krkhaha]

Sorry

 

[badabing2003]

What's that mean verbose. Should I select that or no? I'd like to keep unlock bootloader, disable Verity, disable verification. What options should I select and deselect? Thank you.

See my response here
No need to double post.

 

[HipKat]

@badabing2003
Too easy.
Here's the thing. From the Nexus 6 til now, I was out of the game, completely, so all this that goes into rooting and modifying has gotten very technologically advanced. WAY more commands to learn, files to patch, etc but this app makes it easy for an old guy like me. An old-school guy like me.

Instead of my head spinning over all these commands to do all these things, I flashed the Nov update, disabled Verity and Verification, wiped, updated/reinstalled Magisk while I did my dishes and now my files are being restored while Swift restores my apps/data so I can flash a kernel and any Magisk Mods that need to be restored.

I could learn the advanced methods, easily, and I will, but I'm going in 4 directions all day long. My time is limited between working long hours and raising two teenage girls on my own!

Dude, you're a genius. I can't express enough appreciation

 

[badabing2003]

I could learn the advanced methods, easily, and I will, but I'm going in 4 directions all day long. My time is limited between working long hours and raising two teenage girls on my own!

Happy to see you found it time saving, focus on your daughters and work, let PF do it's thing.
The process should be the same each time there is a new update, although you don't have to wipe anymore, if anything changes and you need to do it differently PF should warn you, pay attention to those (don't expect to see many)

I can't express enough appreciation

You already did, thank you.

 

[HipKat]

Happy to see you found it time saving, focus on your daughters and work, let PF do it's thing.
The process should be the same each time there is a new update, although you don't have to wipe anymore, if anything changes and you need to do it differently PF should warn you, pay attention to those (don't expect to see many)


You already did, thank you.

Right right. This wipe was only for verity and verification.
Mostly, I'm posting this so anyone with doubts can see it's nothing to stress over.

And you're welcome!

 

[rudge79]

Hey Badabing2003,

Just wanted to say thank you for this amazing PixelFlasher. I just did a November system update. Your program works like a charm!
Incredibly easy now to do a OTA update apply to a rooted Pixel 7.

Greetings,

Rudge79

 

[badabing2003]

Hey Badabing2003,

Just wanted to say thank you for this amazing PixelFlasher. I just did a November system update. Your program works like a charm!
Incredibly easy now to do a OTA update apply to a rooted Pixel 7.

Greetings,

Rudge79

Thanks
Just to be clear, you're doing OTA update?
Care to explain your process and reasons?

 

[iwearthebelt]

Hey Badabing2003,

Just wanted to say thank you for this amazing PixelFlasher. I just did a November system update. Your program works like a charm!
Incredibly easy now to do a OTA update apply to a rooted Pixel 7.

Greetings,

Rudge79

I basically said the same thing to him yesterday. It really is a great program he designed. Made it so easy to update to the November release.