boot.img; the name of this image never changes. You can download the oldest factory image you can find for the OG Pixel, and it'll still be named boot.img. So, it would be very easy to mix up an old one with a new one.
Doh. Not sure if there's even a version associated with boot, or how to find it. I still have the patched one which was giving me trouble.
Side by side, there's no way to tell.
Yeah, flashing the factory image doesn't seem to make the bootloader happy again once it's in EIO mode. Sideloading the OTA seems to work though.
Probably because Android 13 never booted. It seems the anti-rollback is officially activated once Android 13 boots.
EIO is new to me, never run into it before. When I look it up, Google says you're supposed to be able to continue the boot process by clicking Continue(? - power button) within 30 seconds. BTDT, just went back to the bootloader (or maybe that's when it went to the black Google screen and hung, even after a wipe).
How could they do this to us? Protect us from a security flaw, really? And then there's... Hey Google how about fixing the security flaw already, it's been weeks now. You just can't win.
Agree. Poor rollout in general. That bl unlock needed a factory reset is ridiculous.Very poor update plan is what is at fault here. Want to bump the anti-bootloader-rollback flag, go ahead, but make damned sure that the updated bootloader is written into BOTH slots before allowing the flag to be incremented, and make sure that there is some mechanism in place to prevent an older bootloader from ever being written.
Necessary like scoped storage?
Hey now, let's not discount Linux phones lol. I have a PinePhone and while it needs work it's pretty okay. Especially for $150
The only case where we know someone's device has been bricked because of the bootloader was a GrapheneOS developer. And, we have already established that not only is it possible to successfully flash the Android 12 system on the 13 bootloader, it will boot and function normally, too.Make.no mistake, it WILL PERMA-BRICK your phone.
One you successfully boot into A13 it triggers the anti-roll back to advance. So it's destructive and very permanent once the e-fuse blows...that's why they're calling it a fuse...cuz you can't un-blow a fuse after it's blown. One dev already found out the hard way...even the usb port is dead!
Some Pixel 6 users running Android 13 are stuck between a rock and a hard place with Google's anti-rollback protection.www.androidpolice.com
Now...my 2 cents. Imo...
That's soo wrong of Google. They have NO right...NONE!, to permanently brick someone's 'bought & paid for computer' or phone!! They can do whatever they want with their software...even ERASE it! But rendering your phone absolutely useless is nothing short of willful destruction of personal property...in the eyes o the law even. They may own their software but they do NOT own my $600+ phone that I paid cash for! End of story.
OP should change thread title to include 'can brick' or'WILL brick' if you've already booted into A13 (non-beta) and you flash back and try to boot A12.
This has always been the case, and it's intended to protect user data. If unlocking the bootloader did not wipe data, then an attacker could use that as a vector - unlock the device, flash or boot a compromised image, and use it to access anything on the device.
I appreciate knowing a little as to why a rollback to the old bootloader has been prevented but it still seems quite unnecessary. Unless the device is unlocked there wouldn't have been a way to restore the old bootloader anyway. And, if a device is unlocked, well, you're already insecure to an extent if someone gets their hands on your phone.
Thank you very much for the help and the links! I think I'll be able to get by with the translation, thanks again!You'll want to sideload the full OTA image once you have initially updated to Android 13 via OTA. Here's a good guide for sideloading an OTA for people who are not familiar with how to do it or have never done it before. You'll want to sideload the full OTA image. I hope you can translate the guide well.
It's an open forum, and everybody is entitled to their views and opinions, even if they're not authoritative truth.
@mike.sI do however understand the argument you're trying to make - that replacing the board shouldn't be necessary provided they reflash the updated bootloader, and I think you're right in that regard.
At the end of the day there's a lot of unknowns. We don't know exactly how Google fixed the brick, we don't know whether they opened the device, we don't know whether they reflashed the board or simply replaced it.
You'll want to sideload the full OTA image once you have initially updated to Android 13 via OTA. Here's a good guide for sideloading an OTA for people who are not familiar with how to do it or have never done it before. You'll want to sideload the full OTA image. I hope you can translate the guide well.I'm a bit confused about the procedure for some of the steps, see if someone can help me.
Once updated to A13 via OTA, I download the OTA again (from the mobile or from the pc?) but.... In what directory should it be for it to recognise it when I use the ADB command? should it be on the mobile or on the pc? Thanks and sorry for the inconvenience, I don't speak English so it makes it even more difficult for me to follow the steps.
fastboot flash bootloader --slot=all <bootloader image>It's highly recommended you do this BEFORE updating, but if you didn't, do it as soon as possible.
adb reboot bootloader #Reboots device to bootloader. fastboot getvar current-slot #Outputs current slot, should also be visible on the device screen: "Boot slot" fastboot getvar version-bootloader #Outputs current slot's bootloader version, should also be visible on device screen "Bootloader version" fastboot --set-active=a or b (set to inactive slot) #Use this to switch to the inactive slot - if current slot is A, set to B or vice versa. fastboot getvar current-slot fastboot getvar version-bootloader fastboot --set -active=a or b (set to original slot) #Set active slot back to what it was before. If you started on slot A, make sure you switch back to slot A. fastboot getvar current-slot fastboot continue #Commands device to resume boot, same function as selecting "Start" in the bootloader menu.
I mean...I've kinda liked A12. But to each his own.
@blackhawk is entitled to his opinion, just as you are. Remember to keep your conduct civil and respectful:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.