nRF91 Unlock | Feasibility, Cost & Lead Time

nRF91 Unlock — What You Need to Know First

The nRF91 unlock process targets Nordic Semiconductor’s nRF9160 and nRF9161 system-in-package (SiP) devices — Arm Cortex-M33 based cellular IoT modules with integrated LTE-M/NB-IoT modem. These parts ship with multiple, layered security features that make firmware extraction significantly harder than on simpler Cortex-M0/M4 platforms. Authorized recovery is possible in many scenarios, but success depends on which protection features were enabled at provisioning time.

Our engineers evaluate every nRF91 unlock request individually because a blanket “yes” or “no” would be misleading. Below we break down the protection architecture, what recovery realistically looks like, and what it costs.

What Protection Does the nRF91 Series Use?

Nordic built the nRF9160/9161 on Arm TrustZone-M with its own proprietary access-port protection layer (APPROTECT). Understanding these layers is essential before any nRF91 unlock attempt.

The critical distinction on newer nRF9160 revisions (post-2020 silicon, QFAA-Bx0 and later) is that APPROTECT was hardened to close a glitch-based bypass that worked on earlier nRF52 parts. This means the voltage-glitch vector that succeeded on some EFM32G and similar Cortex-M devices is not directly transferable to the nRF91 without significant adaptation.

Is nRF91 Unlock Feasible?

Feasibility breaks into three tiers depending on how the device was provisioned:

Tier 1 — APPROTECT Enabled, SECUREAPPROTECT Disabled (or Default)

Some production boards ship with only APPROTECT engaged while the Secure-domain lock remains at its default (open) state. In this case, our lab can typically recover application-core firmware using a combination of fault-injection and custom debug sequences. Success rate in this tier runs roughly 75–85 %, with the main variable being silicon revision and PCB decoupling layout.

Tier 2 — Both APPROTECT and SECUREAPPROTECT Enabled

When both access-port locks are blown, the attack surface shrinks considerably. Recovery requires multi-glitch sequences targeting the Cortex-M33 boot ROM. Turnaround is longer, and success rate drops to approximately 40–60 %. We always run a paid feasibility assessment before committing to a full extraction on Tier 2 devices.

Tier 3 — UICR Fuse-Based Permanent Lock + Encrypted Storage

If the OEM used the permanent-disable fuses in the UICR and additionally encrypted flash contents with a device-unique key, firmware recovery is effectively blocked by design. We will tell you upfront if your device falls into this category rather than waste your budget. Honest assessment saves everyone time — a trait that separates experienced labs from those promising universal success.

How We Approach nRF91 Firmware Recovery

1. Device intake & visual inspection. We identify the exact part number, revision code (laser-marked on the SiP lid), and PCB characteristics. The revision determines which silicon errata and protection hardening apply.
2. Non-invasive probe. Before any physical intervention, we attempt a standard SWD connection. On roughly 10 % of “locked” devices we receive, the protection was never actually enabled — the developer assumed it was active but never blew the fuse.
3. Fault-injection campaign. Using voltage glitching on the VDDH/DECOUPLING rail with sub-nanosecond timing, we attempt to skip the APPROTECT check during the boot sequence. This step requires custom jigs and typically 4–48 hours of automated parameter sweeping.
4. Secure-domain extraction. If TrustZone partitioning is active, we use a staged readout — Non-Secure region first, then Secure region via a second glitch or via exploiting the SPU configuration if it was left partially open.
5. Verification & delivery. Recovered firmware is verified by comparing CRC against the running device’s behavior. Deliverables include raw binary (.bin), Intel HEX, and a memory map showing Secure/Non-Secure boundaries.

We do not attempt to extract the Nordic modem firmware (the LTE stack running on the separate modem core). That binary is Nordic’s proprietary IP and is available directly from Nordic’s download portal for licensed users.

nRF91 Unlock Cost and Turnaround

Prices depend on quantity (single unit vs. batch), urgency, and whether you need the output cross-referenced with a schematic or BOM. Rush service (≤5 days for Tier 1) carries a 30 % surcharge.

Authorization and Legal Requirements

Every nRF91 unlock engagement requires proof of ownership or written authorization from the IP holder. We work under mutual NDA, and our standard agreement explicitly limits use to authorized recovery — restoring access to your own firmware for maintenance, re-production, or failure analysis. This is not a service for extracting a competitor’s proprietary code.

If you are recovering firmware from a legacy IoT product where the original developer is unavailable, we can discuss the documentation needed to establish legitimate ownership. Similar authorization protocols apply to our work on other families, such as Renesas RA6 recovery and GD32 flash readout projects.

nRF91 vs. Other Nordic and Arm Cortex-M33 Parts

Engineers sometimes ask how nRF91 unlock compares to the nRF52 or nRF53 series. The short answer: the nRF91 is harder.

• nRF52 (Cortex-M4): Older APPROTECT implementation; well-documented glitch vectors; success rate above 90 % on most revisions.
• nRF53 (Dual Cortex-M33): Similar TrustZone architecture to nRF91 but without the cellular modem complexity. Comparable difficulty for the application core.
• nRF91 (Cortex-M33 + LTE modem): Hardened APPROTECT, dual-domain TrustZone, plus the modem core is a separate processor with its own signed firmware. The modem adds no direct attack surface for the application core, but it complicates board-level probing because of RF shielding and dense BGA routing.

For comparison, Cortex-M0+ parts like the Microchip SAMD20 or Nuvoton M051 typically present far simpler protection and lower cost to recover.

Common Failure Modes and Honest Caveats

Silicon Revision Surprises

Nordic has issued multiple errata-fix revisions for the nRF9160. A device marked QFAA-B00 may respond to a glitch parameter set that completely fails on QFAA-CA0. We maintain a revision-specific parameter database, but new steppings can require fresh characterization — adding 2–3 days to turnaround.

Decoupling and Board Layout

Tight decoupling capacitors near the SiP’s power pins dampen glitch energy. Some OEM boards have 100 nF + 1 µF caps within 0.5 mm of the VDD pad, requiring partial depopulation before glitching. This is non-destructive if done correctly, but it does add handling time and a small risk of pad lift on fine-pitch 0201 placements.

Encrypted Flash Contents

Even after a successful readout, if the OEM stored application data encrypted with a key derived from the device’s FICR (Factory Information Configuration Registers), the raw binary may not be directly usable on a different nRF91 unit without the original key material. We flag this during the feasibility phase.

Frequently Asked Questions

Related IC Unlock Services

If your project involves multiple microcontroller families, our lab handles a wide range of Arm Cortex-M devices under the same NDA and authorization framework:

• Renesas RA2 flash recovery — Cortex-M23 with TrustZone-M, similar dual-domain challenges
• MSP430F2 series unlock — TI’s 16-bit MCU with JTAG fuse protection

Each family has its own protection quirks, cost profile, and success probability. We provide per-device feasibility assessments so you know exactly where you stand before committing budget.

Related reading

• Oct 2026AT90 Crack | Protection Levels & Firmware Recovery
• Oct 2026Texas Instruments IC Unlock | Families We Can Read
• Oct 2026AT90 Unlock | Feasibility, Cost & Lead Time