General ๐Ÿ›‘โ—โš ๏ธ WARNING! Read this before you upgrade to Android 13 Stable!โš ๏ธโ—๐Ÿ›‘

Search This thread

ctfrommn

Senior Member
May 25, 2011
7,341
10,711
Minnesota
Does this prevent you from flashing an older bootloader? It says you cannot run android 12 on the newest bootloader. But what if you downgrade the bootloader then flash android 12. How's that going to work?
If your bootloader is unlocked you can flash anything. This story is based around those using unmodified stock.
 

V0latyle

Forum Moderator
Staff member
  • Like
Reactions: kkjb and blackhawk

V0latyle

Forum Moderator
Staff member
So unlike Samsung, Pixel doesn't limit rom version with the bootloader to prevent rollback?
Sweet.
Don't think so, but remains to be seen. We've already proven that an older version will run on the newer bootloader, by updating bootloader only - but we have as of yet not proven whether it's possible to flash older builds on the newer bootloader.
 
  • Like
Reactions: blackhawk

blackhawk

Senior Member
Jun 23, 2020
10,491
4,171
Samsung Galaxy Note 10+
Don't think so, but remains to be seen. We've already proven that an older version will run on the newer bootloader, by updating bootloader only - but we have as of yet not proven whether it's possible to flash older builds on the newer bootloader.
Sounds scary backwards. The bootloader is the last thing I want to update. With Samsung's you generally get boned upgrading the bootloader... forget doing a rollback, and enjoy the future shock. It's an interesting experiment nonetheless๐Ÿ˜Ž
 

mike.s

Senior Member
Apr 2, 2010
1,012
367
Google Pixel 6a
I ran into some scary parts trying to upgrade. I was Magisk rooted.

Did my normal upgrade routine. Download factory image. Extract boot.img, put on phone, Patch with Magisk (25.2). Pull off phone.

Modify flash-all.bat to eliminate wipe and final reboot. Run it (no problems), then fastboot flash boot magisk_patched.img. Reboot.

Returns to bootloader, saying "Enter reason: boot failure". Oh sh... OK, fastboot flash the original boot.img. Now it gets the "your device is corrupt" screen. Doing another flash-all didn't fix it. Tried a lot of things before using a virgin factory image and letting it wipe. That didn't fix it. Everything I tried resulted in one of 3 things - bootloader w/"boot failure", "your device is corrupt" screen, or hung black screen w/"Google" (first stage boot? but never continues with the spinning balls, waited up to 20 minutes there) which needed a long power button press to get out of. Edit: it did end up on the "battery" screen a couple of times.

Finally got it booted on 13 using flash.android.com. Did a minimal setup, then fastboot flashed magisk_patched.img. "boot failure", so flash from web again. minimal setup, install magisk, do the patch thing starting with a fresh copy of boot.img, then flash it. This time it booted fine.

I'm not sure if the first boot.img I pulled got corrupted along the way, or ??? I also don't understand why flashing the original boot.img (which was done as part of both flash-all.bat and manually) didn't allow it to boot. Or why flash.android.com was able to fix it. I did notice that flash.android.com does a force flash (first time I've used it). What's the equivalent of flash.android.com's force flash? Just adding --force when using fastboot? I don't recall getting any errors which might have called for that.

tl;dr; I tried a rooted upgrade like I always do, it failed, needed to use flash.android.com to recover it.
 
Last edited:

V0latyle

Forum Moderator
Staff member
I ran into some scary parts trying to upgrade. I was Magisk rooted.

Did my normal upgrade routine. Download factory image. Extract boot.img, put on phone, Patch with Magisk (25.2). Pull off phone.

Modify flash-all.bat to eliminate wipe and final reboot. Run it (no problems), then fastboot flash boot magisk_patched.img. Reboot.

Returns to bootloader, saying "Enter reason: boot failure". Oh sh... OK, fastboot flash the original boot.img. Now it gets the "your device is corrupt" screen. Doing another flash-all didn't fix it. Tried a lot of things before using a virgin factory image and letting it wipe. That didn't fix it. Everything I tried resulted in one of 3 things - bootloader w/"boot failure", "your device is corrupt" screen, or hung black screen w/"Google" (first stage boot? but never continues with the spinning balls, waited up to 20 minutes there) which needed a long power button press to get out of. Edit: it did end up on the "battery" screen a couple of times.

Finally got it booted on 13 using flash.android.com. Did a minimal setup, then fastboot flashed magisk_patched.img. "boot failure", so flash from web again. minimal setup, install magisk, do the patch thing starting with a fresh copy of boot.img, then flash it. This time it booted fine.

I'm not sure if the first boot.img I pulled got corrupted along the way, or ??? I also don't understand why flashing the original boot.img (which was done as part of both flash-all.bat and manually) didn't allow it to boot. Or why flash.android.com was able to fix it. I did notice that flash.android.com does a force flash (first time I've used it). What's the equivalent of flash.android.com's force flash? Just adding --force when using fastboot? I don't recall getting any errors which might have called for that.

tl;dr; I tried a rooted upgrade like I always do, it failed, needed to use flash.android.com to recover it.
It sounds to me like you were using an Android 12 boot image by mistake - somewhere between extracting the boot image from the factory 13 update, and patching it in Magisk, you were actually patching a left over Android 12 image. This is why I like using Pixel Flasher - it removes any existing boot image, patches a new one, and flashes it for you. Zero issues on my wife's P5a. I performed the factory update manually via command line on my P5. Either way, it sounds like you were probably using an old Android 12 boot image by mistake; it might have been left over in your phone's storage.

FWIW, if you' come up against this corrupt problem again, try sideloading the OTA. When you flashed the "old" boot image by mistake, the system freaked out because of Anti Rollback Protection, as it's seeing an Android 12 kernel and Android 13 system, so it put the bootloader into EIO mode. Factory flash doesn't fix it, but sideloading the OTA does for some reason.

Are you talking about force flash all partitions? This option is only available with a data wipe, and is generally for restoring the original partition layout (as one might after coming from a custom ROM).
 
Last edited:
  • Like
Reactions: kkjb

96carboard

Senior Member
Jul 17, 2018
792
462

V0latyle

Forum Moderator
Staff member
  • Like
Reactions: blackhawk

96carboard

Senior Member
Jul 17, 2018
792
462
Yeah, so it looks like it's just in the bootloader itself - if you attempt to flash an older bootloader, it'll just reject it.

Shouldn't preclude flashing an older system version though.

And even if something in the OS did bail on the rollback version, it would be fairly simple to track down and either disable, or otherwise fake.

My guess is that they put the warning up because they don't want to re-publish the older builds with the new bootloader version.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Greetings to all. Ok my friends, let us please stop with the accusations, and the who's right and who's wrong disagreement. You all have exceptionally good knowledge
    of this recent topic, and all we ask is you respectfully disagree with each other, rather than trying to prove who's right or wrong with snarky, or disrespectful comments.

    Now please let us return to "On Topic" discussion. Thank you.

    -Regards: Badger50
    2
    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.
    Thank you very much for the help and the links! I think I'll be able to get by with the translation, thanks again!
    2
    But I've never claimed to know the truth. Only calling out those who are claiming absolute knowledge, without any authoritative support. There's a big difference between stating an opinion, and claiming a fact.
    It's an open forum, and everybody is entitled to their views and opinions, even if they're not authoritative truth.
    Just like any news / gossip / talk ... you take what's good and you ignore what's bad or what doesn't interest you.
    No way you can win by battling every poster you disagree with (justifiably or otherwise).
    2
    I 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.
    @mike.s
    I think that sums it up pretty well.

    There are a lot of unknowns, and asking proof or evidence goes both ways in the argument, you don't have proof or evidence either.

    Let's remain calm and civil, we want to help each other, not knock each other down.
    1
    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.
    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.
  • 10
    From the Pixel Images page:
    1660936653879.png


    This applies to ALL Tensor devices, regardless of whether or not you're rooted!

    What this means:
    Once Android 13 Stable boots, it updates an anti-rollback counter in the device hardware to prevent rolling back the bootloader. This will prevent previous versions of the bootloader from starting.

    Why this is a problem: The OTA only updates one slot, then reboots into that slot. It does not update both slots at once. If there is a boot failure at any point in the future, the device may attempt to "recycle" back to the old slot. If this other slot has a previous version of the bootloader, the bootloader will not start, rendering the device a brick.

    How do I make sure this doesn't happen to me?
    If you updated via OTA, simply sideload the OTA again. Since you are currently on the Android 13 slot, this will overwrite your old Android 12 slot with the new bootloader.
    If you have an unlocked bootloader and prefer to update using the factory image, you can flash the bootloader to both slots:
    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.

    What if I was on the Android 13 Beta? Same as above - the beta did not incorporate the anti-rollback, and the beta bootloaders are still considered "old".

    Will the new bootloader prevent me from flashing and running Android 12? The short answer is YES, for now. Contrary to what the warning above says, you CAN flash Android 12 on the Android 13 bootloader, and though it will boot, it will not run properly. See this post.

    How do I check my current bootloader version?
    Code:
    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.
    8
    That would be the scoped storage sucking up resources/battery to make you feel safe...
    Android 10 is ok, 11 so-so, 12 sucks and along comes 13 beta. Yeah that'll work.
    Blame Gookill for this fubar.
    I mean...I've kinda liked A12. But to each his own.

    You'd probably rather run command line Linux on your phone, you old bastard lol
    5
    1000% fake comment.
    5
    This is such BS. Drama
    @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.