If your device displays “1662 patched” or fails to unlock despite following guides, your bootloader is effectively locked for good unless an exploit is released for your exact model and bootloader version. For development, consider buying an international Exynos model or a Pixel device instead.
This report details the significance of the "1662 patched" status for Sony Ericsson (and legacy Xperia) devices, a term historically used in the modding community to describe a specific security hardening that prevents traditional bootloader unlocking. 1. What is the "1662 Patch"?
In the context of Sony Ericsson devices, "1662" typically refers to a specific manufacturing date code (Year 2016, Week 62 - often representing a transition period in hardware/software security) or a security patch version.
Pre-Patch: Older devices could often be unlocked via standard "Testpoint" methods or simple software exploits that bypassed carrier restrictions.
The Patch: Devices marked as "1662 patched" (or similar later versions) have updated bootrom or bootloader security that closes these hardware exploits. This means they can no longer be unlocked through "simpler" methods like the widely used S1 Unlock Tool. 2. Unlocking and Relocking Challenges Status for "1662 Patched" Devices Bootloader Unlock Allowed
Often shows as "No" in the Service Menu (*#*#7378423#*#*). If it says "No," official Sony methods will not work. Testpoint Method
Generally disabled or fixed by the patch, making hardware-level bypassing significantly more difficult. Relocking
For devices that could be unlocked, relocking is often done to restore DRM keys (needed for camera enhancements like X-Reality) or to re-enable official Sony Software Repair tools. 3. Current Workarounds and Risks
For modern Xperia or legacy Sony Ericsson users facing this patch:
Official Unlock: Check the Sony Developer Portal to see if your IMEI is eligible. If "Bootloader unlock allowed" is No, Sony will not provide an unlock code.
Third-Party Services: Some specialized tools (like paid S1 server credits) occasionally find new exploits for patched devices, though availability is inconsistent.
Risks: Unlocking (if possible) triggers a factory reset, erasing all data, and may permanently break DRM-related features unless a TA-partition backup is made beforehand.
Pro-Tip: If you are buying a used Sony device for modding, always check the Service Menu first. If "Bootloader unlock allowed" says No, the device is likely "patched" and cannot be easily customized. Se Bootloader Unlocking Relocking 1662 Patched
The saga of the SE (Special Edition) bootloader has reached a definitive turning point. After a period of flexibility that allowed enthusiasts to unlock, modify, and relock their devices, the latest 1662 security patch has effectively shuttered the most popular bypasses used by the community. The Rise of the 1662 Patch
For months, users relied on a specific exploit in the SE's firmware to toggle the bootloader status without tripping permanent security flags. This allowed for:
Custom ROM Installation: Swapping the stock OS for leaner, community-driven versions.
Safe Relocking: Returning the device to a "Green" verified boot state, which is crucial for passing integrity checks required by banking apps and secure streaming services.
However, as documented in recent community reports, newer security revisions—culminating in the 1662 patch—have integrated a "Rooting Status" check that can no longer be spoofed. If your device displays "Bootloader Unlock Allowed: No" in the service menu (*#*#7378423#*#*), the door is now hardware-locked by the provider. The Current State: Unlocking vs. Relocking
The "One-Way Trip": For many SE models, if you successfully unlocked before the 1662 patch, you may still be able to operate with a custom recovery. However, attempting to relock under the new patch often results in a "Red" integrity state, preventing the device from booting entirely or permanently disabling OTA updates.
Patch Persistence: Unlike previous updates where a factory reset or a downgrade could revert the bootloader's behavior, the 1662 patch modifies the TrustZone/TEE (Trusted Execution Environment). This makes the restriction persistent even across software downgrades. Why the Change?
Manufacturers and carriers have cited "device integrity" and "user data protection" as the primary reasons for the 1662 hardening. By ensuring the bootloader cannot be toggled at will, they prevent attackers from physically accessing a device and side-loading malicious firmware to bypass encryption. What This Means for You
If you are currently on an older patch and value your ability to root or flash custom kernels, do not update to 1662. Once the update is applied, the signature verification process becomes strictly enforced, and there is currently no known public exploit to bypass this "patched" state. How to unlock and re-lock the bootloader - Support
Unlocking the bootloader on certain devices, such as those using specific Sony (SE) or older chipsets, often involves bypassing security patches like the "1662" patch mentioned. Understanding Bootloader Unlocking
Unlocking a bootloader skips the signature check during startup. This is essential for installing: Custom ROMs like LineageOS. Root access through tools like Magisk. Custom Firmwares to extend the life of older devices. The "1662 Patched" Context
In technical communities, a "patched" bootloader refers to a security update that closes previous exploits used for unauthorized unlocking.
SE Devices: Sony Ericsson or modern Sony Xperia devices often require a unique unlock code from the manufacturer’s official portal.
Patched Versions: If a device's security version (like 1662) is "patched," standard exploits may no longer work, requiring hardware-level methods like EDL/QDL mode for recovery or deep-level modification. Relocking Risks
Relocking a bootloader is possible but dangerous if not done correctly:
How to unlock and re-lock the bootloader - Support - Fairphone
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.
Title: The Cat and Mouse Game: SE Bootloader Unlocking, Relocking, and the “1662 Patched” Enigma
Introduction
If you’ve spent any time in the Android modding community—especially with recent Xiaomi, Realme, or Nothing devices—you’ve likely run into three frustrating terms in the same sentence: SE unlocking, relocking, and the cryptic error code “1662” (or the phrase “1662 patched”).
For the uninitiated, these words signal a battleground between manufacturers’ security policies and the user’s right to fully control their device. Today, we’re breaking down what they mean, why “1662 patched” is a headache for modders, and whether relocking your bootloader is still possible after the patch.
"se bootloader unlocking relocking 1662 patched" appears to be a specific string or filename associated with a software patch or utility
for Sony Ericsson (SE) mobile devices, specifically regarding the modification of their bootloader status. Key Contextual Details
: This string is often linked to tools designed to either bypass factory security to a bootloader (allowing for custom ROMs or rooting) or to
it to restore the device to a "factory-like" security state. "1662" Identifier
: In the context of older Sony Ericsson modding (such as for the Xperia series), "1662" typically refers to a specific version of a S1 bootloader bypass
or a specific script version used in tools like Flashtool or specialized "SE Bootloader Unlocking/Relocking" utilities. Security Implications se bootloader unlocking relocking 1662 patched
: Unlocking a bootloader generally compromises the device's hardware-backed security, potentially disabling features like DRM keys (used for camera enhancements or premium video) and increasing the risk of unauthorized firmware access. Hacker News Technical Status
: The term "patched" in your query suggests that the software has been modified to work around specific restrictions or bugs in the original manufacturer's code, or it refers to a version that fixes previous vulnerabilities in the unlocking tool itself. Current Relevance
: While these specific tools were highly popular for legacy Sony Ericsson/Xperia devices, modern smartphones (like those from
) use significantly more complex verification methods (e.g., Xiaomi's HyperOS requirements
) that often require official account authorization or wait periods. Are you trying to unlock a specific device model , or are you looking for the download link for this particular legacy utility?
For legacy Sony Ericsson (SE) enthusiasts, the "1662 patched"
status marks a significant technical wall in the device’s lifecycle. This specific patch, introduced in later production batches of 2011 Xperia models (like the Arc S, Ray, and Neo V), effectively permanently locked the bootloader against the popular "testpoint" exploits used by tools like S1Tool. The "1662 Patched" Dilemma
In the early days of Xperia modding, devices with "Bootloader unlock allowed: No" could still be forced open using a
—a physical contact point on the motherboard—and specialized software. This allowed users to bypass carrier restrictions and install custom kernels.
However, Sony Ericsson eventually released a hardware-level patch, often identified by manufacturing dates or software versions associated with the 1662 build . On these devices: S1Tool and NCK
will fail or show a "NOT RECOGNIZED" or "PATCHED" error during the testpoint process. official Sony Unlock
method remains unavailable because the carrier has locked the "Unlock Allowed" flag to "No".
: These phones are widely considered "hard-locked," meaning there is currently no public, free, or even paid method to unlock the bootloader once this patch is detected. Unlocking vs. Relocking: Key Differences
If you are lucky enough to have an unpatched device, the workflow is straightforward but risky:
The Ultimate Guide to SE Bootloader Unlocking and Relocking: Understanding the 1662 Patched Bootloader
For Android enthusiasts and developers, unlocking and relocking the bootloader is a common practice that offers a world of possibilities. One of the most popular and widely used bootloaders is the SE (Sony Ericsson) bootloader, which has been used in various Sony and Ericsson devices over the years. In this article, we'll dive into the world of SE bootloader unlocking and relocking, with a specific focus on the 1662 patched bootloader.
What is a Bootloader?
Before we dive into the specifics of the SE bootloader, let's take a step back and understand what a bootloader is. A bootloader is a small program that runs on a device before the operating system (OS) loads. Its primary function is to initialize the device's hardware components, load the OS, and provide a way to interact with the device at a low level.
What is the SE Bootloader?
The SE bootloader is a custom bootloader developed by Sony Ericsson for their devices. It's designed to provide a secure and reliable way to load the operating system and provide a interface for developers and advanced users to interact with the device.
Why Unlock the Bootloader?
Unlocking the bootloader offers several benefits, including:
The 1662 Patched Bootloader
The 1662 patched bootloader is a specific version of the SE bootloader that has been patched to allow unlocking and relocking. The patch, released by a developer community, fixes a vulnerability in the original bootloader, making it possible to unlock and relock the bootloader without requiring a special key.
How to Unlock the SE Bootloader (1662 Patched)
Unlocking the SE bootloader (1662 patched) involves several steps:
How to Relock the SE Bootloader (1662 Patched)
Relocking the SE bootloader (1662 patched) is a relatively straightforward process:
Risks and Precautions
Unlocking and relocking the bootloader carries some risks, including:
Conclusion
In conclusion, the SE bootloader (1662 patched) offers a flexible and customizable way to interact with Sony and Ericsson devices. Unlocking and relocking the bootloader provides a world of possibilities for developers and advanced users. However, it's essential to understand the risks and precautions involved and to carefully follow the instructions to avoid any potential issues.
FAQs
Q: What is the SE bootloader? A: The SE bootloader is a custom bootloader developed by Sony Ericsson for their devices.
Q: Why unlock the bootloader? A: Unlocking the bootloader offers several benefits, including customization, development, and rooting.
Q: What is the 1662 patched bootloader? A: The 1662 patched bootloader is a specific version of the SE bootloader that has been patched to allow unlocking and relocking.
Q: How do I unlock the SE bootloader (1662 patched)? A: Follow the steps outlined in the article, including enabling Developer Options, enabling OEM Unlocking, and using the bootloader unlock tool.
Q: How do I relock the SE bootloader (1662 patched)? A: Follow the steps outlined in the article, including downloading and installing the bootloader relock tool and running it on your device.
Additional Resources
) refers to a specific security patch level found in older Sony and Sony Ericsson devices that effectively blocks traditional unofficial unlocking methods. Sailfish OS Forum The Verdict: A "Hard Mode" for Modders
If you find your device marked with this patch, you’re looking at a significantly more restrictive environment than standard Android devices. The Unlocking Wall
: In the "1662 patched" era, Sony and network operators implemented stricter checks. For many users, checking the service menu (via *#*#7378423#*#* ) reveals a dreaded "Bootloader unlock allowed: No" If you flashed unofficial or modified boot/firmware images,
status. This usually means the standard official Sony unlock code will not work, as the fastboot command is physically disabled in the firmware. The Relocking Risk
: While modern devices like Pixels or OnePlus allow for relatively safe relocking with custom signing keys, older Sony devices are far less forgiving. Relocking a bootloader while a non-stock kernel is present on these patched models is a near-guarantee for a hard brick
, as the "approved" signing keys are limited to factory-installed ones. Feature Loss
: Unlocking these devices often results in the permanent loss of unique Sony features. Historically, this included
required for high-end camera processing (X-Reality) and high-quality video streaming (Widevine), though newer devices have mitigated some of these losses. Key Takeaways for Users Check Status First : Before attempting any tools, always use the dialer code *#*#7378423#*#* to verify if your device even permits unlocking. Avoid "Magic" One-Click Tools
: Many third-party tools claiming to bypass the 1662 patch can be malicious or lead to permanent lockouts. Warranty and Safety
: Unlocking will void your warranty. On patched devices, it also removes layers of Verified Boot
, making the system more vulnerable to physical-access attacks. Sailfish OS Forum Bootloader Unlock: NO - General - Sailfish OS Forum
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
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
Unlocking and Relocking Bootloader on 1662 Patched Devices: A Comprehensive Guide
Introduction
The world of Android customization is vast and exciting, but it often requires taking risks and delving into the unknown. One crucial step in this journey is bootloader unlocking and relocking, especially on devices with patched bootloaders like the 1662. In this post, we'll guide you through the process, highlighting the benefits, risks, and step-by-step procedures for unlocking and relocking your bootloader on a 1662 patched device.
What is a Bootloader?
A bootloader is a program that loads the operating system into memory when a device boots up. It's a critical component that determines what software can run on your device. A locked bootloader ensures that only authorized software can run, while an unlocked bootloader allows users to install custom operating systems, recoveries, and kernels.
Why Unlock Your Bootloader?
Unlocking your bootloader offers several benefits:
Risks of Unlocking Your Bootloader
However, unlocking your bootloader comes with risks:
The 1662 Patched Bootloader
The 1662 patched bootloader is a specific security patch designed to prevent unauthorized access to the bootloader. While it's intended to enhance device security, it can also make it more challenging for users to unlock their bootloader.
Unlocking Your Bootloader on a 1662 Patched Device
To unlock your bootloader on a 1662 patched device, follow these general steps:
Relocking Your Bootloader
If you decide to relock your bootloader, follow these steps:
Conclusion
Unlocking and relocking your bootloader on a 1662 patched device requires careful consideration of the benefits and risks. While it can enhance customization and development possibilities, it also poses security risks and may void your warranty. Always research thoroughly and follow the recommended steps to ensure a successful process.
Disclaimer
The author and this blog are not responsible for any damage or issues that may arise from attempting to unlock or relock your bootloader. Proceed at your own risk.
How's this draft? I can make changes if needed!
The Digital Gatekeeper: A Perspective on Bootloader Security
The bootloader is the first piece of code that runs when you power on a smartphone. Its primary job is to verify the integrity of the operating system before allowing it to load. In the context of "patched" versions or specific build numbers (like "1662"), this process becomes a battleground between user freedom and manufacturer security. 1. The Mechanics of Unlocking
Unlocking a bootloader is the process of disabling the signature check that ensures only "authorized" software runs on the device.
Why users do it: To install custom ROMs (like LineageOS), gain root access, or remove manufacturer bloatware.
The Procedure: Typically involves enabling "OEM Unlocking" in developer settings and using fastboot commands like fastboot flashing unlock. 2. The Risks of Relocking
Relocking the bootloader is often done to restore a device to its factory state for warranty or security purposes. However, it is a high-risk procedure if the software is "patched" or modified.
The Brick Risk: If you relock a bootloader while running a custom recovery or a modified system image, the device may refuse to boot entirely, a state known as a "hard brick." Official guides emphasize that you must flash a clean, untouched stock ROM before attempting to relock. If your device displays “1662 patched” or fails
Security Integrity: Unlocking often permanently trips security flags (like Samsung's Knox), which cannot be reversed even by relocking. 3. The "Patched" Reality
Manufacturers frequently release security patches to close "loopholes" that allowed for unauthorized unlocking.
Build-Specific Barriers: A specific software version (such as a hypothetical "1662" patch) might fix an exploit that previously allowed users to bypass the 168-hour wait period (common on Xiaomi devices) or use third-party tools to force an unlock.
Irreversibility: Once a device is updated to a version that patches an unlock exploit, it is often impossible to downgrade the bootloader, effectively locking the device into the manufacturer's ecosystem permanently. Conclusion
While bootloader unlocking offers unparalleled control over hardware, it exists in a state of constant flux. As manufacturers move toward tighter "verified boot" ecosystems, "patched" versions represent the end of the line for many modding communities, turning a simple software toggle into a complex technical challenge.
It looks like you're looking for content related to unlocking and re-locking the bootloader on a device with a patched 1662 error — likely for a Samsung device (e.g., A series or M series with a known “1662” patch in the bootloader).
However, I must start with a critical warning:
Warning: Unlocking the bootloader on a patched device can trip Knox, void your warranty, permanently disable some Samsung features (Samsung Pay, Secure Folder, etc.), and may brick your device if done incorrectly. Proceed at your own risk.
Below is a structured, informational guide suitable for a blog, tutorial, or forum post.
The “SE Bootloader Unlocking/Relocking 1662 Patched” is a vulnerability-based bootloader modification specific to certain Samsung Exynos devices (and potentially others) around the 2016–2018 era. It allows unlocking without official token verification but comes with permanent Knox trip, no OTAs, and brick risk on relocking.
If you have a device with bootloader version exactly 1662 or lower, it’s a powerful freedom tool. If your bootloader is higher, the “patch” won’t work due to anti-rollback. Always verify your exact device model and bootloader version before attempting.
Last note: Most modern devices (2020+) have patched this vulnerability. This method is now obsolete for new phones. For current devices, look for official unlock methods (e.g., Xiaomi’s unlock tool, Motorola’s bootloader unlock, or Pixel’s fastboot oem unlock).
SE Bootloader Unlocking and Relocking: Navigating the 1662 Patched Landscape
Unlocking the bootloader on older Sony Ericsson (SE) devices is a foundational step for enthusiasts looking to install custom ROMs or gain root access. However, users often encounter specific technical hurdles like the "1662" patch, which can complicate the process. Understanding the 1662 Patched Status
In the context of Sony Ericsson modding (particularly the Xperia series), "1662" refers to a specific version of a S1 bootloader bypass. This bypass was originally used to unlock devices that did not support the official Sony unlock method.
The Patch: Modern firmware updates for these older devices often "patched" the vulnerability that allowed the 1662 bypass to work, effectively locking the bootloader again and preventing unauthorized modifications.
Checking Your Status: To see if your device can still be unlocked, enter the service menu by dialing *#*#7378423#*#*. Navigate to Service info > Configuration > Rooting Status. If it says "Bootloader unlock allowed: Yes", you can proceed with official methods; if it says "No", the device is likely restricted by a carrier or a permanent patch. How to Unlock (Official Method)
If your device shows "Yes" for unlock allowance, the official Sony Developer World process is the safest route.
Retrieve IMEI: Dial *#06# to get your device's unique IMEI number.
Get Unlock Code: Visit the official Sony Unlock Page and enter your IMEI to receive a unique unlock key.
Fastboot Mode: Power off your device. Hold the Volume Up button while connecting it to your PC via USB to enter Fastboot mode (the LED should turn blue).
Execute Command: Use the Android SDK Platform-Tools to run the following command in your terminal:fastboot oem unlock 0x. Relocking Your Bootloader
Relocking is often necessary to restore warranty or pass integrity checks (though on some older SE devices, a "relocked" status is different from "locked" and may still trip certain flags). Unlock bootloader allowed : No,Needa fix here! - Sony
Title: The Locked Door Paradox: A Technical and Practical Analysis of Sony Xperia XA2 (Model 1662) Bootloader Relocking with Patched Segments
Introduction
The Android aftermarket development scene is often described as a cat-and-mouse game between device manufacturers securing their hardware and enthusiasts seeking to unlock the full potential of their devices. The Sony Xperia XA2, bearing the model number 1662 (often associated with firmware variants like the 50.2.A.0.0 series), presents a fascinating case study in this dynamic. Specifically, the process of "relocking" the bootloader after it has been unlocked and modified with "patched" segments represents a complex intersection of security protocols, user customization, and software integrity. This essay explores the technical intricacies, motivations, and risks associated with relocking the bootloader on the Sony Xperia 1662 using patched firmware files.
The Architecture of Bootloader Security
To understand the complexity of relocking, one must first understand the bootloader's role. The bootloader is the first piece of code that runs when a device is powered on. Its primary directive is to verify the integrity of the operating system it is about to load. Manufacturers like Sony implement a secure boot chain, often utilizing technologies like TrustZone, to ensure that only authorized, signed software runs on the device.
When a user unlocks the Sony 1662 via Sony’s official web service, a "Unlock Bootloader" key is written to the device’s trim area (TA partition), specifically flipping the r_s1_bootloader_unlocked flag. This puts the device in an "insecure" state, allowing the flashing of custom kernels or Recovery images. However, Sony’s implementation is unique; even when unlocked, the device retains certain security checks, and the "Relocking" feature allows users to revert the device to a state where it passes SafetyNet checks and accepts official OTA (Over-The-Air) updates again.
The Necessity of Patched Segments
The phrase "patched" in this context usually refers to modifications made to the boot image (kernel) or the loader sin files. In the case of the Xperia XA2 (1662), advanced users often use patched files for two primary reasons:
The challenge arises because a stock bootloader will refuse to lock if it detects that the currently flashed software version does not match the expected security version. This is where "patched" firmware or specialized tools (often leveraging the S1 protocol) become necessary. Users must flash specific firmware segments that have been patched to bypass version downgrades or to align with the security expectations of the locking mechanism.
The Relocking Procedure and the 1662 Variant
The specific process for the 1662 model highlights the delicate nature of flashing protocols. Unlike generic ADB commands, Sony devices require the use of the Flashtool utility (Emma) or the NewFlasher command-line tool. The procedure typically involves flashing the bootloader and loader SIN files.
However, a critical error can occur if the user attempts to relock with a mismatched or corrupted patched segment. The device runs a security check upon receiving the lock command. If the patched segment used for the relock process was derived from a different firmware version or was improperly modified, the device may enter a "bootloop" or, worse, a "hard brick."
In the context of the 1662 model, users frequently discuss "patching" the TA partition itself. Some community-developed methods involve backing up the TA partition before unlocking and restoring it later. Others involve using a patched version of the bootloader file that essentially "tricks" the hardware into believing it is relocking to a secure, factory state, even if the software has been modified.
Risks and Consequences
The act of relocking with patched segments is fraught with risk. The most significant danger is the permanent bricking of the device. If the relocking process writes a corrupted key or a patched segment that fails the hardware's internal verification at the deepest level, the device may fail to boot entirely and may not be recoverable via standard flashing tools.
Furthermore, there is the issue of "soft bricking" where the device boots but fails SafetyNet checks due to a mismatch in the verified boot state. A patched relock might leave traces in the system logs (dm-verity) that flag the device as tampered, defeating the purpose of relocking for users who want to use banking apps or pass Netflix certification.
Conclusion
The saga of the Sony Xperia 1662 bootloader relocking process with patched segments serves as a testament to the complexity of modern mobile security. It illustrates that the binary state of "locked" or "unlocked" is mediated by a sophisticated chain of trust that can be manipulated but not easily fooled. While patched segments offer a bridge back to a secure state for modified devices, they require a high degree of technical proficiency to implement correctly. For the average user, the risks associated with patching critical boot segments far outweigh the benefits. Ultimately, the relocking phenomenon underscores the delicate balance enthusiasts must maintain between the freedom of open software and the rigid security frameworks designed to protect the device.
After analyzing community posts (XDA, 4PDA, Telegram), 1662 is typically a bootloader version (SW REV) or a security patch date (e.g., 2017–2018). The “patched” means:
So a “1662 patched” bootloader is either: