Cause: You relocked with modified system files.
Fix: This is a brick. You need to EDL (Emergency Download Mode) flash with an authorized account – a service center job.
fastboot flashing unlock
If you own a Sony Xperia device, you know that the bootloader process is not as simple as on a Pixel or OnePlus device. Sony uses a unique system of unlock tokens and a tool called Emma (or Newflasher) that ties your device's security state to its software.
Recently, advanced users have been discussing the "167" or "167z" status flags in relation to SE (Sony Ericsson/Sony Mobile) bootloader security. If you are looking to unlock your device, flash custom ROMs, and then safely relock it without breaking DRM keys or breaking your OTA updates, this guide is for you.
Here is the verified breakdown of how the process works.
No. Relocking always triggers a factory reset. Backup first.
Warning: This process will wipe your data. Proceed at your own risk. Unlocking may void your warranty and break banking apps.
Cause: The tool requires a logged-in OEM account (e.g., Xiaomi).
Fix: Log into your Xiaomi/Realme account on the device, enable "Find My Device," and wait 7 days. Then re-run the tool.
For 167z verified devices:
✅ Unlock – safe and community-approved.
⚠️ Relock – possible but only on full stock firmware; high risk if you’re unsure.
Recommendation: Unlock only if you need custom software. Avoid relocking unless returning to service center – one wrong step bricks the phone.
Unlocking and relocking a bootloader, particularly on devices like those from
(which frequently uses a "168-hour" wait period often mistyped as "167z"), is a technical process that grants administrative control over a device's hardware-software handshake. This capability is the cornerstone of Android customization, yet it carries significant security and stability risks. The Unlocking Phase: Gateway to Customization By default, most Android devices ship with a locked bootloader
to ensure only manufacturer-signed operating systems can run. Unlocking this "gatekeeper" allows users to: Android Open Source Project Install Custom ROMs
: Replace the stock operating system with community-driven versions like Obtain Root Access
: Gain deep system permissions to modify system-level files using tools like
For many manufacturers, this is a "verified" process requiring a specific tool or token. For instance, mandates a waiting period—typically
(7 days)—during which the device must remain bound to a verified Mi Account before the Mi Unlock Tool will grant permission. The Risks and Repercussions Unlocking is not without consequence. Manufacturers like warn of several "verified" downsides: Data Eradication
: The unlocking process triggers a factory reset, wiping all user data for security reasons. Security Vulnerabilities se bootloader unlocking relocking 167z verified
: An unlocked bootloader allows unverified firmware to access sensitive data, bypassing standard Android security layers. Integrity Failures
: Financial apps, streaming services (capped at 480p), and games may fail Play Integrity or SafetyNet checks. The Relocking Phase: Restoration and Danger
Relocking the bootloader is often attempted to restore a device to its "out-of-the-box" state or to pass security checks. However, this is the most hazardous phase of device modification. The "Brick" Risk : Relocking must only be done if the device is running 100% stock, untouched firmware
. If a custom ROM or modified boot image is present when the lock command is issued, the device will likely become a "brick" (unbootable) because the bootloader will refuse to load the unsigned software. Verification Match
: The security patch level of the firmware must be equal to or newer than what was previously installed; otherwise, the device may fail to boot after relocking.
Lock and unlock the bootloader | Android Open Source Project
SE Bootloader Unlocking and Relocking: A Guide to the 167z Verified Process
Unlocking a bootloader is a critical step for Android power users looking to install custom ROMs, root their devices, or perform deep system repairs. However, the process can vary significantly depending on the manufacturer and specific device security profiles, such as those labeled with "167z verified" or similar designations.
Understanding how to manage this state—and how to relock it for security—is essential for maintaining device integrity. What is the Bootloader?
The bootloader is the first piece of software that runs when you turn on your phone. Its job is to verify the operating system's signature before loading it.
Locked Bootloader: Only allows official, manufacturer-signed firmware to run, protecting against unauthorized system changes.
Unlocked Bootloader: Skips signature checks, allowing you to flash custom recoveries (like TWRP) or third-party OS versions like LineageOS. Unlocking the Bootloader (The "167z" Standard)
In many modern security configurations, unlocking requires a combination of software toggles and physical commands.
Enable Developer Options: Go to Settings > About Phone and tap the Build Number seven times until you see a message saying developer mode is active.
Enable OEM Unlocking: In the Developer Options menu, toggle on OEM Unlocking. This is a mandatory prerequisite that sets the device's "unlock ability" to 1.
Boot into Fastboot/Download Mode: Use a computer with ADB/Fastboot installed and run:adb reboot bootloaderAlternatively, use hardware buttons (commonly Volume Down + Power) while the device is off.
Execute the Unlock Command: On your PC, enter:fastboot flashing unlock or fastboot oem unlock. Cause: You relocked with modified system files
Confirm on Device: Your phone will show a warning screen. Use the volume keys to select "Unlock" and confirm.
Warning: Unlocking will erase all user data and may permanently trip security flags like Samsung Knox, voiding your warranty. Relocking the Bootloader for "Verified" Status Reddit·r/LineageOS
Based on the technical string provided, this appears to be a verification log or a specific status report related to Sony (SE/Sony Ericsson) bootloader manipulation using specialized service tools like Review & Breakdown
The phrase is characteristic of a "success log" found in mobile forensic or repair forums (like XDA or GSM-Forum). Here is what each part signifies: : Refers to Sony (formerly Sony Ericsson) . This confirms the device brand. Bootloader Unlocking/Relocking
: Indicates the tool successfully performed both operations. Unlocking allows for custom firmware (ROMs), while relocking is often used to restore warranty status or DRM functions. : This is likely a server-side transaction ID or a specific CID (Customer ID) Hardware Config
version. In the context of Sony devices, "167" often appeared in logs for older Xperia models (e.g., Xperia S, Z series) during the test-point unlocking era.
: Confirms that the security signature was checked and the process was completed without bricking the device. Is it "Solid"? If you are looking at this as a testimonial for a service: Authenticity
: It is a standard technical output. It proves the tool works for that specific hardware revision. Reliability
: Relocking "verified" is a strong green flag. Sony devices often lose "DRM Keys" (X-Reality, Noise Reduction) when unlocked; a verified relock usually means the security integrity was maintained or successfully spoofed back to factory state.
If you are planning to perform this yourself, ensure your specific Allowed Rooting Status (found in the service menu *#*#7378423#*#*
) says "Yes." If it says "No," standard methods won't work, and you'll need the specific paid services this "review" likely refers to. specific software tools generate these types of verification logs?
Here’s a piece based on your keywords, structured as a technical explainer / news snippet.
Title: The 167z Verification Enigma: Unlocking, Relocking, and the Verified Bootloader
In the modding community, the alphanumeric sequence “167z” has recently surfaced as a potential hardware or firmware revision tied to a new wave of bootloader security. Users report that on devices marked with this identifier, the standard fastboot oem unlock command is met with a new layer: “167z verified” handshake.
Here’s what that means for the unlocking and relocking process:
Unlocking (The “167z” Barrier)
Unlike older devices where a simple toggle in Developer Options sufficed, “167z verified” suggests a server-side attestation. Before the bootloader unlocks, the device generates a unique hash (the “167z” challenge), which must be signed by the manufacturer’s key. Without this verified response, fastboot flashing unlock returns a remote: 167z verification failed. Users have had to extract this token using modified engineering ABLs.
Relocking (The Catch)
Relocking (fastboot flashing lock) used to be trivial. However, on “167z verified” units, relocking triggers a full dm-verity check. If the system partition was ever modified—even if returned to stock—the relock process will mark the device as STATE = LOCKED, VERIFIED = FAIL. The bootloader will display a corrupt screen on every boot. fastboot flashing unlock
The Verified State To achieve a clean, relocked “verified” state on a 167z device:
Until the “167z” verification schema is fully reverse-engineered, users are advised to never relock a bootloader unless the device is 100% stock. Otherwise, the “verified” flag will permanently show tampering—with no known way to reset it without a factory blankflash.
tool (specifically version 1.6), a legacy third-party utility used for older Sony Ericsson Xperia devices (circa 2011) to manage bootloader states. SE Bootloader Unlocking Feature (Legacy Devices)
This tool was widely used for 2011-era Xperia phones (like the Xperia Arc or Neo) to bypass official restrictions, especially on carrier-branded units.
: It could unlock the bootloader even on devices where the official Sony service menu said "Bootloader unlock allowed: No". : It featured a "Relock BL" option. By flashing a specific
file through the tool, users could return the device to a "locked" state, which was often necessary to use official Sony Xperia Companion software for repairs or updates. Verified Status and Modern Devices
On modern Xperia devices (Xperia 1 series and newer), the concept of "verified" boot and relocking has changed significantly: Relocking Capability
: Unlike older models, modern Xperia phones (Xperia 1 and newer) can be relocked via command line or
: Unlocking often permanently loses some DRM keys (like those for high-quality Netflix or specialized camera features). While relocking may restore some functionality, the "Verified" status in the service menu will permanently record that the device "has ever been unlocked". Checking Status : You can verify your current status by dialing *#*#7378423#*#* and navigating to Service info Configuration
: Never attempt to relock the bootloader if you are running a custom ROM (like LineageOS), as this will likely brick the device . You must flash a stock Sony ROM before attempting to relock. Are you looking to use this tool on a legacy 2011 device , or are you trying to relock a modern Xperia
To unlock or relock the bootloader on most Android devices, you must use a computer with ADB and Fastboot tools installed. This process erases all user data through a factory reset and may void your warranty. Prerequisites
Backup Data: Ensure all important files are backed up, as the device will be wiped. Developer Options: Go to Settings > About Phone. Tap Build Number 7 times to enable Developer Options.
In Settings > System > Developer Options, enable USB Debugging and OEM Unlocking.
Hardware Setup: Connect your phone to a PC using a high-quality USB cable. Unlocking the Bootloader
Lock and unlock the bootloader | Android Open Source Project
For the 167z variant, the bootloader unlocking capability is whitelisted.