phene!
@phene.dev
trans person online whom you might know from somewhere
This is an x-post from my Twitter page. Any reposts, shares, or anything to get this thread to the eyes of more people is appreciated. Google needs to do better, and nobody should have to pay anything at all for a software fix, or do low-level repairs on their phones.
August 23, 2025 at 5:15 PM
This is an x-post from my Twitter page. Any reposts, shares, or anything to get this thread to the eyes of more people is appreciated. Google needs to do better, and nobody should have to pay anything at all for a software fix, or do low-level repairs on their phones.
So until Google repairs ALL affected phones FOR FREE, I now have a glass doorstop. Google either needs to do this, or release factory tools to let users reprogram their phones at-home, for free. Nobody should have to pay for software faults. Even Meta is better about this.
August 23, 2025 at 5:15 PM
So until Google repairs ALL affected phones FOR FREE, I now have a glass doorstop. Google either needs to do this, or release factory tools to let users reprogram their phones at-home, for free. Nobody should have to pay for software faults. Even Meta is better about this.
There's no way for a user to fix this issue themselves either. If your phone is bricked, you have three choices:
1) Take the UFS off of the mainboard and flash it yourself (expensive, dangerous)
2) Use factory tools to reprogram the phone (not leaked yet)
3) Pay $339 for "repair"
1) Take the UFS off of the mainboard and flash it yourself (expensive, dangerous)
2) Use factory tools to reprogram the phone (not leaked yet)
3) Pay $339 for "repair"
August 23, 2025 at 5:15 PM
There's no way for a user to fix this issue themselves either. If your phone is bricked, you have three choices:
1) Take the UFS off of the mainboard and flash it yourself (expensive, dangerous)
2) Use factory tools to reprogram the phone (not leaked yet)
3) Pay $339 for "repair"
1) Take the UFS off of the mainboard and flash it yourself (expensive, dangerous)
2) Use factory tools to reprogram the phone (not leaked yet)
3) Pay $339 for "repair"
The fact that this issue can happen to ANYONE, and they can be totally left in the dark by Google is insane. There are multiple, long threads of people having this same issue and getting no luck from support.
xdaforums.com/t/may-2025-a...
xdaforums.com/t/may-2025-a...
May 2025 and newer BEWARE of permanent bricks if you don't handle the anti-rollback bootloader correctly on all Pixel 6, 6 Pro, 6a, 8, 8 Pro, 8a
TLDR: follow the instructions in post 2 exactly.
Thread re-opened. New rule for this thread. If it doesn't directly have to do with the May 2025 anti-lock bootloader for the stock ROM (not relatin...
xdaforums.com
August 23, 2025 at 5:15 PM
The fact that this issue can happen to ANYONE, and they can be totally left in the dark by Google is insane. There are multiple, long threads of people having this same issue and getting no luck from support.
xdaforums.com/t/may-2025-a...
xdaforums.com/t/may-2025-a...
Yet despite this, and a lot of arguing, the support representatives would not budge and eventually just closed the chat on me without warning, while I was typing a response. This is insane.
August 23, 2025 at 5:13 PM
Yet despite this, and a lot of arguing, the support representatives would not budge and eventually just closed the chat on me without warning, while I was typing a response. This is insane.
I should not have to pay over three times the value of the phone for a repair (it's only worth ~$140 as a refurb) or pay anything at all, really. A software fix should be FREE.
August 23, 2025 at 5:11 PM
I should not have to pay over three times the value of the phone for a repair (it's only worth ~$140 as a refurb) or pay anything at all, really. A software fix should be FREE.
I spent almost three hours with support yesterday, trying to get them to understand that this was an issue with the software, yet the only solutions they would offer were a $339 repair (!!!) or 20% off a new phone. Neither solutions were fair at all.
August 23, 2025 at 5:11 PM
I spent almost three hours with support yesterday, trying to get them to understand that this was an issue with the software, yet the only solutions they would offer were a $339 repair (!!!) or 20% off a new phone. Neither solutions were fair at all.
And because of this KNOWN ISSUE, my phone (and many other people's phones) have been PERMANENTLY BRICKED. And Google won't help.
August 23, 2025 at 5:11 PM
And because of this KNOWN ISSUE, my phone (and many other people's phones) have been PERMANENTLY BRICKED. And Google won't help.
They KNEW that there was a chance for phones to be bricked because of this if you switched back to the old slot for whatever reason (failed update, corrupt system, etc.) However this was ONLY mentioned on a DEVELOPER PAGE that most people will never see or know about.
August 23, 2025 at 5:10 PM
They KNEW that there was a chance for phones to be bricked because of this if you switched back to the old slot for whatever reason (failed update, corrupt system, etc.) However this was ONLY mentioned on a DEVELOPER PAGE that most people will never see or know about.
In May 2025, there was a security update released for Pixel 6 and 8 series that included a new bootloader to patch some serious security issues, and the anti-roll back index was incremented. This is standard process, but Google was aware of flaws with this update.
August 23, 2025 at 5:09 PM
In May 2025, there was a security update released for Pixel 6 and 8 series that included a new bootloader to patch some serious security issues, and the anti-roll back index was incremented. This is standard process, but Google was aware of flaws with this update.