Soft Brick Bootloop After Doing Unlock Bootloader Looader

 This is my bad experience after doing unlock bootloader. I got soft brick after doing unlock bootloader, even when i'm still not root the devices. This is my analize

Before unlocking, ALWAYS check:

fastboot getvar snapshot-update-status

Safe result: 

snapshot-update-status: none

Dangerous results:  

merging

snapshotted

initiated

Second important thing

Avoid unlocking immediately after:

• OTA update
• first boot after OTA
• system optimization
• slot switch

Instead:

1. update completely
2. boot normally several times
3. wait a while
4. verify snapshot status is none
5. THEN unlock

Check Slot

There actually was an early warning sign in the “bad” state, but it’s subtle.

The most important difference is not a single flag. It’s the combination of slot state + firmware generation + OTA state.

Successful state now looks like this:

current-slot: a
slot-successful:a: yes
slot-successful:b: no
slot-unbootable:a: no
slot-unbootable:b: no
unlocked: no
secure: yes

That is a classic healthy A/B state:

• active slot marked successful
• inactive slot unused but valid
• AVB intact
• no merge/update weirdness

 the original broken state:

current-slot: b

slot-successful:b: yes

slot-successful:a: yes

slot-unbootable:a: no

slot-unbootable:b: no

unlocked: yes

secure: no

suspicious part is: both slots marked successful simultaneously

That often happens after:

• Virtual A/B OTA
• snapshot merge
• incomplete OTA cleanup
• or recently switched slots