According to OP this does not disable bootloader unlocking in itself. It makes the up-versioned devices incompatible with all previous custom ROMs, but it should be possible to develop new ROM releases that are fully compatible with current eFuse states and don't blow the eFuse themselves.

▲

palata 6 hours ago | parent [-]

I understand that there is a nuance somewhere, but that's about it.

Can you explain it in simpler terms such that an idiot like me can understand? Like what would an alternative OS have to do to be compatible with the "current eFuse states"?

▲

Muromec 6 hours ago | parent [-]

People need to re-sign their releases and include the newer version of bootloader, more or less.

▲

zozbot234 5 hours ago | parent [-]

Yes, though noting that since the antirollback is apparently implemented by the bootloader itself on this Qualcomm SoC, this will blow the fuse on devices where the new version is installed, so the unofficial EDL-mode tools that the community seems to be most concerned about will still be unavailable, and users will still be unable to downgrade from the newer to older custom ROM builds.

	▲	Muromec 5 hours ago \| parent [-]
		Not being able to downgrade and using the debug tools was the exact point of doing this thing, as far as I understand.