ATtiny Unlock: Recovering Firmware from Atmel’s Compact AVR Line
ATtiny unlock is the process of reading protected flash and EEPROM contents from Atmel (now Microchip) ATtiny-series microcontrollers whose lock bits have been programmed. Our engineers recover firmware for clients who own the original design but have lost source code, need to maintain legacy hardware, or must migrate to a new silicon revision. Authorization and proof of ownership are required before any work begins — see our trust and legal compliance page for details.
How Does ATtiny Code Protection Work?

ATtiny devices use a two-level lock-bit scheme (LB1 and LB2) stored in a dedicated fuse area. When both bits are programmed, the ISP and JTAG/debugWIRE interfaces refuse read-back of flash and EEPROM. Some newer ATtiny parts (ATtiny817, ATtiny3217, etc., in the tinyAVR 1-series and 2-series) use UPDI with a different SYSCFG0 CRCSRC-based protection model rather than classic lock bits.
Understanding which protection layer your specific part uses is the first step in any ATtiny unlock assessment. Classic lock bits on older 8-pin parts behave differently from the UPDI-based protection on newer 0/1/2-series devices, and each requires a distinct recovery approach.
Classic ATtiny Lock-Bit Protection (tinyAVR Legacy)
- Mode 1 (no lock): Flash and EEPROM freely readable via ISP — no unlock needed.
- Mode 2 (LB1 programmed): Further programming of flash/EEPROM is disabled via ISP/parallel, but read-back may still be partially blocked depending on silicon revision.
- Mode 3 (LB1 + LB2 programmed): Full read/write lock on flash and EEPROM. Verification also disabled. This is the configuration that demands a physical or semi-invasive unlock technique.
UPDI-Based Protection (tinyAVR 0/1/2-Series)
Newer ATtiny parts such as ATtiny402, ATtiny814, ATtiny1616, and ATtiny3227 use UPDI (Unified Program and Debug Interface). Protection is set through the BOOTEND and APPEND fuses plus a LOCKBIT register. When the LOCKBIT register is written to 0x00, the NVM controller blocks external read-back entirely. Recovery from UPDI-locked parts requires different tooling than classic ISP-locked devices.
Which ATtiny Parts Can We Unlock?
Feasibility depends on the exact part number, its silicon revision, and the protection mode in use. The table below summarizes our current success status across common ATtiny variants.
| ATtiny Family | Example Parts | Protection Type | Unlock Feasibility |
|---|---|---|---|
| Classic 8-pin | ATtiny13A, ATtiny25, ATtiny45, ATtiny85 | Lock bits (LB1/LB2) | High — well-characterized silicon |
| Classic 14/20-pin | ATtiny24A, ATtiny44A, ATtiny84A | Lock bits (LB1/LB2) | High |
| Classic with USI | ATtiny2313A, ATtiny4313 | Lock bits (LB1/LB2) | High |
| Classic 28-pin | ATtiny48, ATtiny88 | Lock bits (LB1/LB2) | High |
| tinyAVR 0-series | ATtiny202, ATtiny402, ATtiny804 | UPDI LOCKBIT | Moderate — part-dependent |
| tinyAVR 1-series | ATtiny814, ATtiny1614, ATtiny3217 | UPDI LOCKBIT | Moderate |
| tinyAVR 2-series | ATtiny1627, ATtiny3227 | UPDI LOCKBIT | Under evaluation |
“High” feasibility means our lab has repeatable, validated processes for these devices across multiple silicon revisions. “Moderate” means success depends on the specific revision and may require a preliminary die inspection. Parts listed as “under evaluation” may still be recoverable — submit your device for a free feasibility check.
Check feasibility for your project
Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.
Request a feasibility reviewWhat Does the ATtiny Unlock Process Look Like?
Every ATtiny unlock engagement follows a controlled sequence designed to protect both the device and the extracted data.
- Intake & authorization: Client provides proof of IP ownership or a signed authorization letter. We execute an NDA before any physical work begins.
- Device inspection: We verify the exact part number, package marking, and date code under magnification. Remarked or counterfeit parts are flagged immediately.
- Fuse & lock-bit assessment: Using non-destructive ISP or UPDI probing, we read accessible fuse bytes to determine the protection level without risking the flash contents.
- Recovery procedure: Depending on the protection model, our engineers apply the appropriate technique — ranging from electrical fault injection on classic parts to controlled UV or chemical decapsulation followed by micro-probing on hardened revisions.
- Verification: Extracted firmware is loaded onto a blank ATtiny of the same type and functionally tested against the client’s hardware where possible.
- Delivery: We provide a binary (Intel HEX or raw .bin), a fuse-byte map, and an optional disassembly listing.
The entire chain is logged and auditable. Devices are returned to the client along with all extracted data.
Cost and Lead Time for ATtiny Unlock
Pricing varies with the protection level, part family, and quantity. Below are representative ranges based on recent projects.
| Category | Typical Cost (USD) | Lead Time (Working Days) |
|---|---|---|
| Classic ATtiny (LB mode 3, single unit) | $300 – $600 | 3 – 5 |
| Classic ATtiny (batch of 5+ identical parts) | $200 – $400 per unit | 5 – 8 |
| tinyAVR 0/1-series (UPDI locked, single unit) | $500 – $900 | 5 – 8 |
| tinyAVR 2-series (evaluation required) | Quote after assessment | Assessment: 3 – 5 days |
Rush service (≤2 working days) is available for classic ATtiny parts at a 40–60% surcharge. UPDI-locked parts cannot be rushed because die-level inspection timelines are less compressible.
Common Failure Modes and Honest Caveats

Not every ATtiny unlock succeeds. Transparency about failure modes is part of our process:
- Die damage during decapsulation: Older ATtiny13 and ATtiny25 packages (SOIC-8) have thin die substrates. Aggressive chemical decap can crack the die. Our current breakage rate on these parts is under 3%, but it is non-zero.
- Flash degradation: Devices that have been through thousands of erase/write cycles (e.g., in-field data-logging applications) may have marginal cells that read inconsistently. We flag suspect bytes in the delivered hex file.
- Newer silicon revisions: Microchip occasionally hardens lock-bit implementations between silicon revisions of the same part number. An ATtiny85 Rev. C may respond differently than Rev. G. We always check the revision before committing to a method.
- UPDI LOCKBIT + CRC: On tinyAVR 1/2-series parts where CRC validation is enabled alongside LOCKBIT, the recovery path is more complex and may require a second sample device for calibration.
If we determine during assessment that recovery is not feasible, you pay nothing beyond any agreed evaluation fee (typically waived for single-unit jobs).
ATtiny vs. Other AVR and 8-Bit Families
ATtiny parts share architectural DNA with other Atmel/Microchip families but differ in protection implementation. If your project involves related microcontrollers, the following resources may help:
- The ATxmega unlock page covers the more advanced AVR XMEGA protection scheme, which uses a different boot-section lock model.
- For legacy Atmel 8051-core parts like the AT89C51 or AT89S52, see our AT89C51 unlock and AT89S52 unlock guides — these use entirely different lock-bit architectures.
- If you’re working with Microchip PIC parts instead, our PIC16 unlock page addresses the CP/CPD fuse model common in that family.
Who Needs ATtiny Unlock Services?
Based on the projects our lab handles, ATtiny unlock clients typically fall into a few categories:
- Legacy product maintainers: The original developer left the company or the source repository was lost. The product is still in the field and needs a firmware patch or hardware revision.
- Contract manufacturers: An OEM client provided programmed ATtiny chips but no source. The CM needs to reprogram replacement units for warranty repair.
- Reverse engineers (authorized): Companies acquiring another firm’s product line as part of an M&A deal, where firmware source was not included in the asset transfer.
- Academic and failure-analysis labs: Researchers studying silicon security or performing quality audits on their own designs.
Deliverables You Receive
| Deliverable | Format | Included By Default |
|---|---|---|
| Flash contents | Intel HEX (.hex) + raw binary (.bin) | Yes |
| EEPROM contents | Intel HEX (.hex) | Yes |
| Fuse byte map | Text report (low/high/extended fuse, lock bits) | Yes |
| Disassembly listing | AVR assembly (.asm) | On request (add $100–$200) |
| Functional verification report | PDF with test log | On request |
Check feasibility for your project
Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.
Request a feasibility reviewIs ATtiny unlock legal?
ATtiny unlock is legal when performed on firmware you own or are authorized to access. Common lawful scenarios include recovering your own lost source code, maintaining legacy products, and firmware migration during authorized product transfers. We require proof of ownership or a signed authorization letter before beginning any work. Visit our compliance and trust page for full details.
Can you unlock a tinyAVR 2-series part like the ATtiny3227?
The tinyAVR 2-series is currently under active evaluation in our lab. UPDI LOCKBIT protection on these parts is more robust than on classic ATtiny devices. We accept these parts for a no-cost feasibility assessment — if we cannot recover the firmware, you owe nothing. Turnaround for the assessment alone is typically 3–5 working days.
What if the ATtiny chip is damaged or partially erased?
We can often still extract usable data from physically intact but electrically degraded devices. If specific flash pages have marginal cells, we perform multiple read passes and flag inconsistent bytes in the delivered file. Severely cracked or delaminated dies are generally unrecoverable, but we assess before charging.
How does ATtiny unlock differ from ATxmega or AT89 series unlock?
ATtiny uses a simpler two-bit lock scheme (classic) or UPDI LOCKBIT (newer series). ATxmega parts have boot-section locks and a more complex NVM controller. AT89 series (8051 core) devices use an entirely different architecture with separate lock bits per memory region. Each family requires specialized tooling and techniques.
Do you need the original PCB or just the chip?
We only need the ATtiny IC itself, desoldered from the board. If you prefer, ship the entire PCB and our team will safely remove the part. For QFN or WLCSP packages, professional desoldering reduces the risk of pad damage, so sending the full board is recommended.
Working on a board like this?
Send the chip marking or two photos. You get feasibility, lead time and price within 24 hours, and the check costs nothing.
Get a free quote