Huawei P Smart 2018 FIG-LX1/LX2/LX3 Bootloader Locking with Original Code vs PotatoNV

User question

How to lock bootloader on P Smart 2018

Artificial Intelligence Response

Direct answer to the question

• Short answer: You can only safely “lock” a Huawei P Smart 2018 (FIG‑LX1/LX2/LX3) with the original 16‑digit Huawei bootloader code and completely stock, unmodified firmware. Use fastboot oem relock from Fastboot mode. Without that original code (e.g., if the phone was unlocked via PotatoNV/testpoint), there is no reliable way in 2025 to return the phone to a true factory LOCKED state; attempts often lead to “Your device has failed verification…” or a hard brick.
• Key points:
  • Relocking forces a full data wipe.
  • Stock firmware and stock recovery must be present and match your exact model/region build.
  • If unlocked with PotatoNV, “fully locked” is generally not achievable; at best you may reach “RELOCKED,” which can still trigger integrity warnings.

Detailed problem analysis

• What “locking” actually enforces:
  • Huawei implements Verified Boot (dm‑verity/AVB). A locked bootloader will only boot Huawei‑signed, untouched partitions for your exact device variant and region (CUST/Cxxx).
  • If any partition (boot/ramdisk, recovery_ramdisk, vbmeta, system, vendor, oeminfo) is modified or mismatched, locking will fail verification and you’ll see “Your device has failed verification and may not work properly,” or the device won’t boot.
• Why the original code matters:
  • Huawei ceased issuing unlock/relock codes in 2018. The fastboot oem relock command validates against that 16‑digit code. Without it, the bootloader will refuse a true LOCKED state.
• PotatoNV/testpoint caveat:
  • PotatoNV bypasses Huawei’s code check by altering low‑level NVRAM/oeminfo. Devices unlocked this way typically cannot be returned to factory LOCKED. Fastboot may show RELOCKED or refuse to change state; forcing a lock with non‑matching firmware risks an unrecoverable brick.
• Firmware matching is critical:
  • You must be on a complete stock build for your exact model and region (e.g., FIG‑LX1 C432/C185/C782, etc.), including stock recovery_ramdisk and vbmeta. Mixing cust/region or major-version builds (EMUI 8 vs 9.x) with the wrong rollback index can trip anti‑rollback and brick the device.
• What “RELOCKED” means:
  • Some tools or processes can flip the state to RELOCKED. This is not the same as factory LOCKED and can still fail SafetyNet/Play Integrity and show trust warnings at boot.

Current information and trends

• Since mid‑2018 Huawei no longer provides official bootloader codes.
• Community experience through 2024–2025: devices unlocked via PotatoNV generally cannot be put back to true LOCKED; repeated relock attempts frequently yield “failed verification” or non‑booting devices. eRecovery or DLOAD can restore stock firmware but typically do not change bootloader state to factory LOCKED.
• App and OTA behavior: Even with RELOCKED, some banking/DRM/Integrity checks continue to fail; OTA may refuse to install if the state isn’t factory LOCKED and partitions aren’t pristine.

Supporting explanations and details

• Verified Boot path:
  • vbmeta contains hashes/signatures for partitions. If vbmeta or any hashed partition is non‑stock, locking forces signature enforcement and the boot chain aborts.
• Partition notes for P Smart 2018 (Kirin 659/hi6250 family):
  • EMUI 8 uses separate recovery; EMUI 9.x uses recovery_ramdisk. Ensure you’re flashing the correct images for your EMUI major version.
• Regionalization (CUST):
  • FIG‑LX1/LX2/LX3 require firmware with the correct Cxxx region (C432 EU, C185 MEA, C636 Asia Pacific, C782 UK, etc.). Cross‑flashing then locking is unsafe.

Ethical and legal aspects

• Warranty/service acceptance: Many service centers reject devices that are UNLOCKED/RELOCKED or show modified system states. Paid third‑party “code” services often violate terms and carry fraud/security risks.
• Safety: Testpoint/PotatoNV operations require device disassembly and can short or damage hardware if mishandled.

Practical guidelines

• Path A — You have the original 16‑digit Huawei code and want a true LOCKED state: 1) Back up everything (locking wipes data). Charge ≥60%. 2) Return to 100% stock firmware for your exact model and CUST:
  • Use eRecovery or the DLOAD/“three‑button” method with a full firmware package for your exact FIG‑LXX Cxxx build. Ensure stock boot/ramdisk, recovery_ramdisk, vbmeta, system, vendor are restored. Avoid cross‑region packages. 3) Verify from Fastboot:
  • fastboot devices
  • fastboot oem get-bootinfo (expect UNLOCKED before relock) 4) Relock:
  • fastboot oem relock YOUR_16_DIGIT_CODE
  • Confirm on the handset when prompted. Device will wipe and reboot. 5) Verify:
  • If needed, re‑enter Fastboot and run fastboot oem get-bootinfo (expect LOCKED). Boot should be clean without verification warnings.
• Path B — Unlocked with PotatoNV or you don’t have the original code:
  • Do not attempt to force a lock. Best practice is: 1) Flash full stock firmware for your exact model/CUST (eRecovery or DLOAD) to restore a bootable, stable system. 2) Leave the bootloader UNLOCKED (or accept RELOCKED if the tool toggled it), understanding you may still see trust warnings and some apps may refuse to run. 3) If you absolutely must present a “locked‑looking” device for resale/service, understand that attempting to toggle to LOCKED without the code frequently results in a brick; proceed only if you accept that risk.
• DLOAD refresher (if you choose that route):
  • Place UPDATE.APP (from the correct full package) in dload on a microSD card. Power off. Hold Vol+ + Vol– + Power until update starts. Do not interrupt power. After flashing, factory reset.

Potential challenges and how to overcome them

• “FAILED (remote: Command not allowed)”: You don’t have a valid code for this device/firmware state, or the bootloader refuses relock due to integrity checks.
• “Your device has failed verification…” after relock:
  • Cause: Non‑stock partitions/vbmeta mismatch. Fix: Reflash complete stock (including vbmeta and recovery_ramdisk) that matches your CUST and build. If no code is available, consider leaving it unlocked to boot.
• Device bootloops or bricks after relock:
  • Likely anti‑rollback or partition mismatch. Recover with DLOAD eRecovery if available; otherwise, you may need service/JTAG.

Possible disclaimers or additional notes

• There is no supported way in 2025 to generate a valid factory lock state without Huawei’s original code. Any service claiming otherwise is high‑risk.
• Anti‑rollback: Some EMUI builds enforce rollback indices; downgrading across those boundaries can hard brick even before relocking.

Suggestions for further research

• Search community threads specifically for “FIG‑LX1/LX2/LX3 relock,” “PotatoNV relock,” and “FIG CUST Cxxx full firmware/DLOAD” to confirm a package that matches your region and current rollback index.
• Look up “fastboot oem get-bootinfo” output examples for Kirin 659 to interpret LOCKED/UNLOCKED/RELOCKED states.
• Investigate eRecovery availability for your region/carrier variant; older servers sometimes no longer host images, making DLOAD the practical route.

Brief summary

• If you still have Huawei’s original 16‑digit code and are on pristine, matching stock firmware, lock with fastboot oem relock and expect a full wipe. If you do not have that code or used PotatoNV/testpoint, a true factory LOCKED state is generally not achievable; forcing it risks a brick. In that case, restore full stock, keep the device usable, and accept UNLOCKED/RELOCKED status.

If you want, tell me:

• Your exact model (e.g., FIG‑LX1) and CUST (C432/C185/…),
• Current EMUI version/build number,
• Whether you have the original 16‑digit code or used PotatoNV, and I’ll tailor exact firmware and command steps for your case.