User question
How to lock bootloader on P Smart 2018
Artificial Intelligence Response
Direct answer to the question
- Short answer: On a Huawei P Smart 2018 (FIG‑LX1/LX2/LX3), the only safe way to lock the bootloader is to return the phone to completely stock firmware and run fastboot oem relock with the original 16‑digit Huawei unlock code. If the device was unlocked with PotatoNV/testpoint (no official code), returning to a true LOCKED state is generally not possible without high brick risk; in that case, restore full stock firmware and leave the bootloader UNLOCKED.
- Key points:
- Relocking wipes the phone (full factory reset).
- Stock boot/recovery/system/vendor/cust and verified vbmeta must be in place (no Magisk/TWRP).
- Without the original Huawei unlock code, do not attempt to relock; use dload/eRecovery to restore stock and accept UNLOCKED/RELOCKED.
Detailed problem analysis
- Huawei bootloader states:
- LOCKED: Factory state; Secure Boot chain trusts only signed Huawei images.
- UNLOCKED: Permits non‑Huawei images; warning at boot; some security features disabled.
- RELOCKED: Fastboot state after relocking a previously unlocked phone. Functionally “locked” for most users, but some firmware or apps can still detect it was unlocked in the past.
- Why the original code matters:
- P Smart 2018 (Kirin 659) validates a Huawei‑specific token when changing lock state. The fastboot “oem relock/lock” path requires the same 16‑digit code originally used to unlock. Since Huawei discontinued code issuance in 2018, many units were later unlocked via service/testpoint (e.g., PotatoNV). Those units typically cannot transition back to factory LOCKED; attempts often trigger “Your device has failed verification and may not work properly” or bootloops because rollback indexes and verified partitions no longer match.
- Stock integrity requirement:
- The verified boot chain checks boot, recovery_ramdisk, system, vendor, product, cust and vbmeta signatures. Any residual modification (Magisk‑patched boot, TWRP, mismatched cust/region, downgraded build) will cause verification failure after relock.
- FRP/OEM toggles:
- OEM unlocking toggle in Developer options affects unlock operations; for relock, the critical factor is partition integrity. However, some fastboot builds reject state changes when the toggle is off; enabling it avoids “command not allowed.”
Current information and trends
- Practical 2024–2026 community experience shows:
- Devices unlocked with PotatoNV/testpoint rarely (if ever) return to true LOCKED. Re‑locking attempts commonly lead to verification failure screens or non‑booting states.
- Full stock restoration via eRecovery or dload reliably returns the phone to stock software but generally leaves the bootloader state UNLOCKED/RELOCKED.
- Industry trend:
- OEMs increasingly tie boot integrity to rollback indices and per‑device attestation, making post‑modification relock more fragile unless every partition and version strictly matches.
Supporting explanations and details
- Anti‑rollback/version matching:
- If you relock on a build older than the last recorded rollback index, verified boot fails. Always use same or newer firmware for your exact model (e.g., FIG‑LX1 C432) and the correct cust/region.
- Partition checklist before relock:
- boot (stock, unpatched), recovery_ramdisk (stock), vbmeta (stock, not “disable verification”), system, vendor, product, cust all from the same build.
- What “RELOCKED” means:
- The fastboot banner may show RELOCKED or PHONE Locked; SafetyNet/Play Integrity may still flag historical unlock on some firmwares.
Ethical and legal aspects
- Relocking to conceal prior modification can mislead secondary buyers or service centers. Be transparent if selling the device.
- Regional warranty laws vary; modifying the bootloader may void warranty even after relock. Respect OEM security policies and user data privacy.
Practical guidelines
- Path A — You have the original 16‑digit Huawei unlock code (safest way to lock):
- Back up everything (relock = full wipe).
- Restore 100% stock firmware for your exact model/region:
- Preferred: dload method or eRecovery to install a same‑or‑newer full service/OTA package.
- Ensure stock boot and recovery_ramdisk; remove Magisk; no TWRP; stock vbmeta (verification enabled).
- Enable Developer options and USB debugging; optionally enable OEM unlocking.
- Boot to fastboot (power off, hold Volume Down, connect USB).
- Verify connection: fastboot devices
- Check current state (any one that works on your setup):
- fastboot oem get-bootinfo
- fastboot oem device-info
- fastboot getvar all (read‑only)
- Relock:
- fastboot oem relock YOUR_16_DIGIT_CODE
- If your fastboot build only accepts lock: fastboot oem lock YOUR_16_DIGIT_CODE
- Confirm on‑device; phone wipes and reboots.
- Verify:
- Re‑enter fastboot and confirm “locked/Phone Locked”.
- Boot to system; complete setup.
- Path B — You do NOT have the original code, or you used PotatoNV/testpoint:
- Do not attempt fastboot oem relock; high brick risk.
- Fully restore stock with dload/eRecovery:
- Prepare microSD, create dload folder, place UPDATE.APP (and any required components).
- Power off; hold Vol+ + Vol‑ + Power until update starts.
- Let it complete; the phone will boot stock EMUI.
- Accept that the bootloader will likely remain UNLOCKED (or show RELOCKED) even on stock firmware.
- Risk mitigation:
- Keep vbmeta/verification enabled; avoid custom kernels.
- Disable OEM unlocking in Developer options after setup.
- Avoid OTAs from mismatched regions; update only with correct region builds.
- Recovery options if you already relocked and now see “failed verification”:
- Try entering eRecovery (hold Volume Up ~3 seconds at the error screen), then “Download latest version and recovery.”
- If that fails, return to fastboot (if accessible) and flash stock via dload. If fastboot is no longer available and the device is truly bricked, service tools (board software, testpoint) may be required—proceed only if you understand the risks.
Possible disclaimers or additional notes
- Even a successful relock on these models may present as RELOCKED and can still be detected by some integrity checks.
- There is no supported way (as of January 2026) to obtain new official Huawei unlock codes from Huawei. Third‑party “code generators” are unreliable and may be fraudulent.
- Downgrading below the last booted rollback index can permanently prevent boot with verification enabled.
Suggestions for further research
- Search community threads specific to “FIG‑LX1/LX2/LX3 Kirin 659 relock,” PotatoNV documentation, and Huawei dload/eRecovery guides for your region code (e.g., C432 Europe, C185 MEA).
- Look for “service/board firmware” packages for FIG‑LX1 that match or exceed your current build number to avoid rollback traps.
- Review Android Verified Boot (AVB) behavior and vbmeta signing to understand why patched images cause post‑relock failures.
Brief summary
- If you have the original 16‑digit unlock code and a completely stock, version‑matched firmware set, use fastboot oem relock CODE to safely lock; this will wipe the device. If your phone was unlocked via PotatoNV/testpoint and you lack the original code, do not attempt to relock—restore stock with dload/eRecovery and leave the bootloader UNLOCKED/RELOCKED to avoid bricks.
If you want exact, step‑by‑step files and commands tailored to your phone, please provide:
- Exact model (e.g., FIG‑LX1) and region (Cxxx code from About phone or fastboot).
- Current build number.
- How it was originally unlocked (official code vs PotatoNV).
- Output of fastboot oem get-bootinfo or fastboot oem device-info.
Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.
