The "SE Bootloader Unlocking Relocking 1662 Patched" saga is a masterclass in asymmetric warfare. Manufacturers moved the goalposts from software to hardware (Secure Enclave), and the 1662 patch is the penalty flag thrown at any user who tries to play by the old rules.
You cannot brute force it. You cannot downgrade out of it. And if you relock out of nostalgia, you convert your smartphone into a paperweight.
The only winning move against Error 1662 is to know when to hold 'em (stay locked), know when to fold 'em (buy unlocked hardware), and know when to walk away (skip the relock command forever).
Stay safe, keep your backups offline, and may your verification tokens always match.
For most modern Sony devices, unlocking is officially supported if the "Rooting Status" in the service menu allows it. However, certain regional or carrier-locked models—often identified by this "patched" status—will show Bootloader unlock allowed: No, meaning the official Sony unlock code will not work. 🛠️ Unlocking the Bootloader
Unlocking allows you to install custom ROMs and gain root access, but it also triggers a factory reset and may affect proprietary features like DRM-protected content. The Official Method se bootloader unlocking relocking 1662 patched
Check Eligibility: Dial *#*#7378423#*#* -> Service info -> Configuration -> Rooting Status.
Enable Settings: Go to Developer Options and toggle OEM unlocking and USB debugging.
Get Code: Visit the Sony Bootloader Unlock page and enter your IMEI 1 to receive your unique unlock code.
Fastboot Unlock: Connect your phone in fastboot mode and run fastboot oem unlock 0xYOURCODE. The "1662 Patched" Workaround
If your device says "No" for unlocking, you are likely on a patched firmware. Some older exploits like Xperable once allowed bypassing this for the XZ series. For newer patched devices, unlocking is currently considered impossible without expensive proprietary tools (like S1 unlocking) that are often no longer accessible to consumers. Bootloader Unlock: NO - General - Sailfish OS Forum The "SE Bootloader Unlocking Relocking 1662 Patched" saga
The most dangerous part of this process is not the unlocking, but the relocking.
If you have unlocked your bootloader, flashed a custom ROM or kernel, and wish to return to stock to sell the device or claim warranty service, you must flash the stock firmware and relock the bootloader.
The "Patch" Danger: If you are running a newer firmware (like the 1662 build) and you attempt to relock the bootloader using an older "Unmodified" kernel or a mismatched firmware version, you risk a Hard Brick.
Sony devices utilize a security check called the S1 Boot. If the bootloader detects a mismatch between the security version of the firmware and the bootloader state during the relock process, the device may fail to boot entirely, requiring professional hardware repair (EDL mode or JTAG).
To the modding community, 1662 is a villain. To OEMs and carriers, it is a savior. If you flashed unofficial or modified boot/firmware images,
Short answer: Usually no, unless you have a factory flash image from the exact build you’re on—and even then, it’s a gamble.
If you try to run fastboot oem lock on a device where the 1662 exploit was used to unlock, you’ll often get:
FAILED (remote: 'token verify failed, 1662 patched')
or simply a bootloop after relocking, because the bootloader now sees the custom images as invalid.
The only safe way to relock after a patched SE unlock is to fully restore the device to 100% stock firmware, including:
Then, and only then, can you run fastboot oem lock (or the device-specific command). But if the 1662 patch was applied via a firmware update, the exploit chain is broken—and any attempt to relock may permanently disable the device.