Then, the mobile switched off and never came back since. I tried to load it (even if the battery was high before). I pressed the start button for more than 30 sec, with and without the volume button. Nothing works.
Is the mobile definetely broken? What can I do? I am fed up.
I do have /OS running on an akita, so it’s not broken in general… maybe you can switch the aactive slot to “a” again or flash the additional partition also in the “b” slot (although I’m unsure if these also have alternate slots")
Thank you for your answer. Unfortunately, at that stage, I can do absolutely nothing with the phone. It is bricked.
I don’t know if there is even a solution except throwing it away .
Thank you for your answer.
No, I was not aware of the anti-rollback implementation on Pixel 6 and 8.
And no, I missed the steps you mention (my bad ). That might triggered the problem.
I tried with Android Flash Tool under a Window pc but it’s a fail. Could I be more lucky on Linux?
You never quite know with an online tool, but the expectation is that the tool is able to “see” the device. Always good to keep trying to the bitter end … the device is not bricked if it can be seen (at all) in Fastboot mode, after that EDL is required on some devices.
When I said this anti rollback is “severe” it is because, if I understand it right, the manufacturer discovered a significant vulnerability in earlier versions of the bootloader. They decided it could be fixed only with a certain upgrade path.
Worst case. If I understand it right, it is said that the manufacturer decided that devices exposed to the vulnerability should have a fuse on the motherboard permanently blown.
.
