Firmware-uppdatering avbruten på SSD, router, VR-headset eller spelkonsol: NAND Bootloader Recovery Mode, TFTP Unbrick och USB Offline OSU1 Restore¶

När ett strömavbrott, utlöst strömbrytare, lös USB-kabel eller automatisk omstart av systemet avbryter en aktiv firmwareuppdatering på en konsumentmaskinvaruenhet (such as a Wi-Fi router, an M.2 NVMe or SATA SSD, an Xbox Series X/S or PlayStation 5 console, a Meta Quest VR headset, or a PC motherboard BIOS), enhetens primära icke-flyktiga flashpartition (SPI NOR flash, eMMC, or reserved NAND blocks) lämnas halvraderad med en ogiltig CRC32 eller kryptografisk SHA-256 signatur. Vid nästa omstart, hårdvarans första stegs mask-ROM (BootROM) läser rubriken för den skadade fasta programvaran, stoppar exekveringen för att förhindra exekvering av felaktig maskinkod och släpper enheten till ett uppenbart "död kloss"-tillstånd: en Wi-Fi-router blinkar snabbt med strömlampan utan Wi-Fi-signal, en NVMe SSD försvinner från Windows eller visas 0 MB kapacitet (or "SATAFIRM S11"), en Xbox som har fastnat på System Error E100 / E101 / E106, eller en PlayStation 5 som pulserar blått och vägrar starta in i instrumentbrädan.

Lyckligtvis separerar nästan alla moderna inbäddade hårdvaruingenjörer den oföränderliga Stage-0/Stage-1 Bootloader (stored in write-protected BootROM or a read-only SPI flash sector) från den föränderliga Stage-2 Main Application Firmware. Även när den huvudsakliga operativa firmware är 100% raderas, den där lilla starthanteraren på låg nivå överlever nästan alltid och lyssnar tyst efter en hårdvaruutlöst felsäker återställningsinjektion: en TFTP (Trivial File Transfer Protocol) eller mini-web CFE-server på 192.168.1.1 / 192.168.0.1 för routrar, en 30 minuters tomgång 5V Power-only Flash Translation Layer (FTL) rebuild loop för SSD:er, en signerad USB OSU1 (Offline System Update) eller PS5UPDATE.PUP Felsäkert läge fullständig ominstallationsfil för konsoler, eller en USB-C ADB sideload / Fastboot rescue för fristående VR-headset. Om ett strömavbrott orsakade en aktiv elektrisk lukt eller brand inuti din PC eller UPS under avbrottet, ring ditt lokala nödnummer (911 i USA och Kanada, 112 över hela Europeiska unionen, 999 i Storbritannien) via vår nödnummer katalog först, och konsultera våra syskonguider om M.2 NVMe SSD-avståndsskruv saknas och kortslutning av kortslutning i PCB, Anfall av VR-headset, åksjuka och överhettning av batteriremmen, och UPS-batteriets sura lukt av ruttna ägg och kontinuerligt pip.

Gör det här nu¶

1. Vänta 15 hela minuter innan du trycker på strömbrytaren om skärmen bara "fastnar". 99% eller 100% utan fysiskt strömavbrott. Modernt TLC/QLC NAND och långsam 16 MB SPI NOR Flash-chips utför en kryptografisk verifiering efter skrivning och en paus för radering av sophämtning som kan frysa förloppsindikatorn för 5 to 12 minutes. Att koppla ur en enhet som bara verifierar kontrollsummor är #1 orsak till självförvållade tegelstenar.
2. Om strömmen redan har brutits och enheten inte startar ska du INTE mosa strömknappen upprepade gånger eller köra chkdsk / Format Disk på en skadad SSD. Varje misslyckat startförsök på en SSD med ett skadat Flash Translation Layer (FTL) kan skriva över journalblock som behövs för att rekonstruera dina användardata.
3. För en murad Wi-Fi-router (blinking Power/Amber LED, no Wi-Fi): Anslut en dator till LAN-port 1 via Ethernet, ställ in en statisk IPv4-adress (such as 192.168.1.2 eller 192.168.0.2, Subnät 255.255.255.0), håll det försänkta Reset-stiftet medan du slår PÅ routern tills strömlampan blinkar i långsam återhämtningskadens, och antingen öppnas http://192.168.1.1 i en inkognitowebbläsare (ASUS / TP-Link / Linksys CFE MiniWeb) eller tryck på den uppackade .chk / .bin firmware via en TFTP klient (Netgear / TP-Link).
4. För en M.2 NVMe eller SATA SSD som försvann från BIOS eller program 0 MB / RAW efter en uppdatering (or power loss): Utför 30-minuters tomgångscykeln med endast ström (Micron / Micron / Samsung / WD FTL Rebuild) genom att driva enheten med endast ström (no SATA data cable, or sitting idle on the motherboard BIOS screen) för 30 minutes, stänga av för 30 seconds, and repeating twice so the SSD's internal ARM controller can rebuild its L2P (Logical-to-Physical) mapping table from spare NAND blocks.
5. For an Xbox Series X/S or Xbox One stuck on System Error E100 / E101 / E102 / E106 or a PS5/PS4 stuck in Safe Mode loop: Download the complete 6 GB+ Full Reinstallation Firmware (Xbox OSU1.zip or Sony's 1.1 GB+ "Reinstall System Software" PS5UPDATE.PUP, NOT the smaller 500 MB incremental update file) onto an NTFS-formatted (Xbox) eller FAT32/exFAT-formatted (PlayStation) USB 3.0 flash drive and trigger the hardware two-button bootloader menu.
6. For a Meta Quest (Quest 2 / Quest 3 / Quest 3S / Pro) VR Headset stuck on a bootloop or blinking logo: Hold Power + Volume Down for 10 seconds för att komma in i Android USB Update Mode bootloader, välj Sideload Update, anslut en USB-C-kabel till din PC och kör antingen det officiella webbaserade Meta Quest Software Update Tool (WebUSB) i Google Chrome/Edge eller tryck på den signerade OTA .zip via adb sideload update.zip.

Decision tree: Hardware Bootloader Recovery Path by Device Category¶

Use this hardware rescue flowchart to select the exact low-level recovery protocol for your affected device.

flowchart TD
    A["Firmware Update Interrupted by Power Loss, Reboot, or Cable Disconnect"] --> B{"Which hardware device is failing to boot?"}
    B -->|"1. Wi-Fi Router / Mesh Node (Blinking Power LED, No Wi-Fi)"| C["Hold Reset Button While Powering On (10-30 Sec) Until LED Enters Recovery Blink"]
    B -->|"2. M.2 NVMe or SATA SSD (Not Detected, 0 MB, or Read-Only)"| D["Enter Motherboard BIOS Only (No OS Boot) -> Perform Two 30-Minute Power-Only Idle Cycles for FTL Rebuild"]
    B -->|"3. Xbox Series X/S or PlayStation 5/4 (Error E101/E106 or Safe Mode Loop)"| E["Format 16GB+ USB 3.0 Stick (NTFS for Xbox / FAT32 or exFAT for PS5) -> Copy Full OSU1 or PS5UPDATE.PUP"]
    B -->|"4. Meta Quest VR Headset (Bootloop / Android No Command Screen)"| F["Hold Power + Volume Down -> Enter USB Update Bootloader -> Use Meta WebUSB Tool or 'adb sideload'"]
    B -->|"5. PC Motherboard BIOS (Black Screen / No POST After BIOS Update)"| G["Use Rear 'BIOS FlashBack' Button with FAT32 USB Stick OR Trigger Dual-BIOS Backup Chip Switch"]
    C --> H{"Router Brand Bootloader Type?"}
    H -->|"ASUS / Linksys / Newer TP-Link"| I["Set PC Static IP (192.168.1.2 or 192.168.0.2) -> Open http://192.168.1.1 in Browser -> Upload .trx/.bin in CFE MiniWeb GUI"]
    H -->|"Netgear / Older TP-Link / Ubiquiti"| J["Set PC Static IP (192.168.1.10 or 192.168.0.66) -> Push Firmware via TFTP Binary Mode ('tftp -i 192.168.1.1 PUT fw.chk')"]
    D --> K{"Did SSD reappear with normal capacity?"}
    K -->|"JA"| L["Immediately Back Up Critical Files -> Re-run Official Vendor Firmware Updater (Samsung Magician / Micron / WD Dashboard)"]
    K -->|"NO: Shows 'SATAFIRM S11' / 'ROM Mode' / 2MB"| M["Controller Dropped Into Factory Mask-ROM Mode: Send to Data Recovery Lab (PC-3000) or Claim Vendor Warranty RMA"]

Part 1: Master Bootloader Recovery Matrix Across Routers, SSDs, Consoles, VR, and Motherboards¶

Every device listed below contains a hidden hardware failsafe mode designed specifically for factory assembly and mid-update power loss recovery.

Part 2: Step-by-Step Wi-Fi Router Unbrick Protocol (CFE MiniWeb GUI & TFTP Binary Injection)¶

When a Wi-Fi router loses power during a firmware update, its DHCP server and Wi-Fi radios do not start because the Linux kernel (OpenWrt / Broadcom / Qualcomm SDK) was erased. However, the U-Boot eller Broadcom CFE (Common Firmware Environment) bootloader is still alive on the first 256 KB of flash memory and assigns itself a hardcoded fallback IP address (almost always 192.168.1.1 eller 192.168.0.1) för 3 to 5 seconds at power-on (or indefinitely when you hold the Reset button during power-up).

+-----------------------------------------------------------------------------+
|   HOW ROUTER BOOTLOADER RECOVERY WORKS (STATIC IP + CFE / TFTP INJECTION)   |
+-----------------------------------------------------------------------------+
|                                                                             |
|  [ YOUR LAPTOP / DESKTOP PC ]                 [ BRICKED WI-FI ROUTER ]      |
|  - Disable Wi-Fi                              - Unplug WAN (Modem) Cable    |
|  - Set Static Ethernet IPv4:                  - Hold RESET Pin While        |
|    * IP: 192.168.1.10 (or 192.168.0.2)          Turning Power ON (10-15s)   |
|    * Mask: 255.255.255.0                      - U-Boot / CFE Bootloader     |
|    * Gateway: 192.168.1.1                       Listens on 192.168.1.1      |
|             |                                            |                  |
|             +=======[ CAT5e/CAT6 Ethernet Cable ]========+                  |
|                     (Plugged Into Router LAN Port 1)                        |
|                                  |                                          |
|        +-------------------------+-------------------------+                |
|        v (Method A: CFE MiniWeb)                           v (Method B: TFTP)|
|  Open http://192.168.1.1 in Browser          Run Windows/Mac TFTP Client:   |
|  -> Minimal Emergency HTML Page Appears      "tftp -i 192.168.1.1 PUT       |
|  -> Browse & Upload Unzipped .trx/.bin        firmware.chk" (Binary Mode)   |
|  -> Wait 5 Full Minutes for Flash & Reboot   -> Wait 5 Minutes to Reboot    |
+-----------------------------------------------------------------------------+

Step 1: Prepare Your PC and Download the Exact Hardware-Revision Firmware¶

1. On a smartphone or secondary computer, check the sticker on the bottom of your bricked router for the exact Model Number AND Hardware Version (e.g., Archer AX55 v1.0 vs. v2.0, eller RT-AX86U vs. RT-AX86U Pro). Blinkande v1 firmware på en v2 hårdvarukortet kommer permanent att mura radiokalibreringsbordet.
2. Download the official firmware .zip arkivera från tillverkarens supportwebbplats och packa upp/extrahera det så att du har den råa firmware binära (.chk, .img, .bin, .trx, eller .w). Byt namn på filen till något kort och enkelt utan mellanslag, som fw.chk eller fw.bin och placera den direkt i C:\fw\ (eller din användarhemmapp).
3. Anslut en trådbunden Ethernet-kabel från din dator till LAN-port 1 på routern (unplug the WAN/Internet modem cable and all other LAN cables).
4. Konfigurera en statisk IPv4-adress på din dators Ethernet-adapter (since the bricked router's DHCP server is dead, your PC will get a useless 169.254.x.x address unless you set a static IP):
   • In Windows 10/11: Press Win + R, typ ncpa.cpl, right-click your Ethernet adapter -> Properties -> double-click Internet Protocol Version 4 (TCP/IPv4) -> select Use the following IP address:
     • For ASUS, Netgear, Linksys, and Ubiquiti (192.168.1.1 bootloader): Set IP address to 192.168.1.10, nätmask till 255.255.255.0, standardport till 192.168.1.1.
     • For TP-Link and D-Link (192.168.0.1 bootloader): Set IP address to 192.168.0.2 (or 192.168.0.66 for TP-Link TFTP server mode), Subnet mask to 255.255.255.0, standardport till 192.168.0.1.

Step 2: Trigger the Router's Bootloader Rescue Mode¶

1. Turn the router's power switch OFF (or unplug the DC barrel jack), vänta 15 seconds.
2. Press and hold down the recessed Reset button with a paperclip.
3. While still holding the Reset button down, turn the router's power ON.
4. Keep holding the Reset button for 10 to 20 seconds until the Power LED changes pattern (on ASUS it flashes very slowly once every 2 seconds; on Netgear it flashes amber rapidly and then pulses; on TP-Link the System/WPS LED stays solid). Release the Reset button.

Step 3: Inject the Firmware via Browser (CFE MiniWeb) or Command-Line TFTP¶

• Method A: Browser Emergency Web Server (ASUS, Newer TP-Link, Linksys, D-Link):
  1. Open a private/incognito browser window and go directly to http://192.168.1.1 (eller http://192.168.0.1 for TP-Link/D-Link). (Be sure to type http://, NOT https://).
  2. A bare-bones emergency recovery page ("ASUSTeK CFE miniWeb Server" eller "TP-Link Firmware Recovery") will load.
  3. Click Choose File, select your unzipped .trx eller .bin firmware file, click Upload, and do not touch the router for 5 full minutes until the Wi-Fi LEDs light back up.
• Method B: TFTP Binary Push (Netgear Nighthawk / Orbi, Ubiquiti, Older Linksys):
  1. Enable the built-in Windows TFTP Client: open an Administrator Command Prompt (cmd.exe) and run:

     dism /online /Enable-Feature /FeatureName:TFTP
     

  2. Verify the router bootloader is responding by running ping -t 192.168.1.1 (you should see replies with TTL=100; TTL=100 specifically proves the router is in low-level CFE/U-Boot bootloader mode rather than normal Linux OS mode which returns TTL=64).
  3. With the router in blinking amber recovery mode, run the binary (-i) TFTP push command:

     tftp -i 192.168.1.1 PUT C:\fw\fw.chk
     

     (På macOS eller Linux-terminal, kör: tftp 192.168.1.1, typ binary, typ rexmt 1, typ timeout 60, skriv sedan put fw.chk).
  4. Inom 10 to 45 seconds, terminalen kommer att rapportera Transfer successful: XXXXXXXX bytes in XX second(s). Vänta 4 to 6 minutes medan routern raderar flash, skriver bilden och startar om automatiskt. Glöm inte att ställa tillbaka din dators Ethernet-adapter till "Erhåll en IP-adress automatiskt (DHCP)" afterward.

Part 3: Unbricking an M.2 NVMe eller SATA SSD After a Failed Update or Power Outage¶

When a Solid State Drive (SSD) vanishes from BIOS (or shows up as "SATAFIRM S11", "PS3111", "SM2258AB", or "MN-5236" with 0 MB capacity) after power cuts out during a firmware update or write operation, its cached Flash Translation Layer (FTL) / Logical-to-Physical (L2P) Mapping Table is out of sync with the physical NAND blixtblock. Vid nästa uppstart blockerar SSD-styrenheten värdåtkomst när den försöker skanna enheten, vilket orsakar moderkortets BIOS 3-second POST check to time out.

The 30-Minute Power-Only Idle Cycle (Micron / Micron / Samsung / WD FTL Reconstruction)¶

Before sending the drive to a data recovery lab, execute the manufacturer Power-Only Idle Recovery Protocol (built into Micron/Micron, Phison, Silicon Motion, Marvell, and Samsung controllers): 1. Isolate Power from Data Requests: - For a 2.5-inch SATA SSD: Unplug the skinny 7-pin SATA Data cable from the SSD while leaving the wide 15-pin SATA Power cable plugged in (so the SSD receives +5V power without the OS sending ATA read commands that interrupt self-repair). - För en M.2 NVMe SSD: Slå på datorn och tryck omedelbart på Del eller F2 to enter the motherboard UEFI BIOS setup screen (or put the M.2 drive in a USB-C NVMe enclosure plugged into a 5V phone wall charger). 2. Cycle 1 (30 Minutes ON -> 30 Seconds OFF): Leave the SSD powered on in this idle state for 30 full minutes so the internal ARM processor can scan NAND Out-Of-Band (OOB) metadata and rebuild the FTL lookup table. Then power completely OFF for 30 seconds. 3. Cycle 2 (Repeat 30 Minutes ON -> 30 Seconds OFF): Power back on into the idle BIOS screen for a second 30-minute period, then power OFF for 30 seconds. 4. Reconnect and Back Up: Reconnect the data cable and boot normally. If the SSD reappears, copy your critical files to another drive immediately, then re-run Samsung Magician, Micron Storage Executive, or WD Dashboard to complete the firmware update cleanly. If the drive remains stuck in "SATAFIRM S11" eller "ROM Mode (2 MB)", never run leaked forum "MPTool" utilities (which execute a cryptographic NAND erase that wipes 100% of your files); send the drive to a lab equipped with an ACE Lab PC-3000 system.

Part 4: Console Offline USB Recovery (Xbox OSU1 & PS5 Safe Mode) and Meta Quest ADB Sideload¶

1. Fixa Xbox Series X|S & Xbox One Update Bricks (System Error E101 / E102 / E106)¶

1. Förbered NTFS OSU1 USB Drive: Format a 16 GB+ USB 3.0 drive as NTFS on a Windows PC (FAT32/exFAT will fail). Download OSU1.zip (approximately 6.5 GB) from support.xbox.com/help/hardware-network/console/offline-system-update, extract it, and copy the $SystemUpdate folder directly to the root of the USB stick (E:\$SystemUpdate\).
2. Boot the Xbox Startup Troubleshooter: Unplug the Xbox power cord for 30 seconds, plug it back in, hold Pair (Bind) + Eject (just Pair on digital-only consoles), tap Power, and keep holding until two power-up tones sound (10 to 15 seconds). Plug in the USB stick and select "Offline system update". (Note: If your console was enrolled in the Xbox Insider Preview Program, its internal build is newer than public OSU1, triggering E101; select "Reset this Xbox -> Keep my games & apps" over wired Ethernet instead).

2. Fixing a Meta Quest (Quest 2 / Quest 3 / Quest 3S / Pro) Bootloop¶

1. Håll ned Power + Volym ned för 10 seconds för att öppna USB Update Mode bootloader, markera Sideload Update och tryck på Power (LED turns solid purple).
2. Anslut headsetet till en PC via USB-C, öppna https://www.meta.com/help/quest/software_update/ i Google Chrome eller Microsoft Edge, välj din Quest via WebUSB prompt, and click Start Update to re-stream the factory OS without wiping your apps.

(For related hardware and recovery guides, see M.2 NVMe SSD-avståndsskruv saknas och kortslutning av kortslutning i PCB, UPS battery acid rotten-egg smell, thermal runaway, and continuous beeping, VR headset seizure, motion sickness, fall trauma, and battery strap overheating, och PC-sidopanelen i härdat glas splittras på klinkergolvet och strömavbrott efter blixtnedslag.)

Regionala konsumentgarantirättigheter för enheter med fast programvara¶

Vanliga frågor¶

Can a device still be recovered if the power went out right in the middle of a firmware update?¶

Yes, in the vast majority of cases, because modern routers, gaming consoles, VR headsets, and motherboards store their low-level Stage-0/Stage-1 Bootloader (`such as U-Boot, Broadcom CFE, Xbox Startup Troubleshooter, or PlayStation Safe Mode`) inside a write-protected area of flash memory that is never overwritten during a standard firmware update. Even when the main operating system firmware is completely corrupted by a power outage, holding the hardware recovery button combination at power-on activates that protected bootloader so you can inject a clean firmware image over a wired Ethernet TFTP/browser connection or a properly formatted USB flash drive.

How does the "30-Minute Power-Only Idle Trick" fix a dead SSD after a power outage?¶

When an M.2 NVMe or SATA SSD loses power suddenly, the Flash Translation Layer (FTL) mapping table cached in its volatile RAM falls out of sync with the physical NAND flash blocks. On the next boot, the SSD's internal ARM processor blocks normal host access while it tries to scan the drive, which causes your motherboard BIOS to time out and report the SSD as missing or 0 MB. By supplying the SSD with power only (`either by unplugging the SATA data cable while leaving SATA power plugged in, or by leaving the PC sitting passively on the motherboard UEFI BIOS screen`) for two consecutive 30-minute cycles (`with a 30-second power-off pause between them`), you give the SSD's internal firmware uninterrupted time to scan every NAND block's metadata and rebuild its Logical-to-Physical (L2P) table without the operating system interrupting it.

Why is my Xbox Offline System Update (OSU1) failing with Error E101 even with a brand-new USB drive?¶

There are three reasons an Xbox OSU1 USB recovery fails with Error E101: (1) the USB flash drive was formatted as FAT32 or exFAT instead of NTFS (`Xbox Offline System Updates strictly require an NTFS-formatted USB 3.0 drive with the $SystemUpdate folder placed at the very top root level`); (2) your Xbox was enrolled in the Xbox Insider Preview Program (`which puts the console on a higher internal OS build number than the public OSU1 file on Microsoft's website, causing the bootloader's anti-rollback check to reject the USB stick`); or (3) a brand-new public Xbox update was released within the last 24 to 48 hours and Microsoft has not yet updated the downloadable OSU1.zip archive to match the newest build. If your console is on an Insider build, select "Reset this Xbox -> Keep my games and apps" over a wired Ethernet cable instead of using the USB stick.

Why did my PlayStation 5 or PlayStation 4 reject my PS5UPDATE.PUP USB stick in Safe Mode?¶

Sony's PlayStation System Software webpage hosts two separate download files that both share the exact same name (`PS5UPDATE.PUP` eller `PS4UPDATE.PUP`): a smaller approximately 500 MB incremental "Update File" and a larger approximately 1.1 GB+ complete "Reinstall System Software File." In addition, the PlayStation Safe Mode bootloader is case-sensitive and only reads MBR-partitioned FAT32 or exFAT USB drives (`never NTFS`). To make sure Safe Mode detects your USB drive, format an 8 GB to 32 GB USB stick as FAT32 (`MBR`), create an all-uppercase folder named `PS5` at the root of the drive, create an all-uppercase subfolder named `UPDATE` inside it, and place `PS5UPDATE.PUP` inside (`PS5\UPDATE\PS5UPDATE.PUP`). Always try Safe Mode Option 3 (`Update System Software from USB`) first so your games and save files are not erased.

Relaterade guider¶

• M.2 NVMe SSD standoff screw missing, bent PCB short circuit, or heatsink thermal pad peel
• Modular power supply cable mix-up, fried SATA SSD drives, and pinout incompatibility rescue
• VR headset seizure, motion sickness, fall trauma, and battery strap overheating
• UPS uninterruptible power supply battery acid rotten-egg smell, thermal runaway, and continuous beeping
• PC-sidopanelen i härdat glas splittras på klinkergolvet och strömavbrott efter blixtnedslag
• Nödnummer

Källor och officiell vägledning¶

• Microsoft Corporation (Xbox Support: Offline System Update [OSU1] & Startup Troubleshooter Error E100/E101/E102/E106 Official Documentation): NTFS USB Partition Requirements, $SystemUpdate Directory Structure, and Anti-Rollback Build Verification.
• Sony Interactive Entertainment (PlayStation 5 & PlayStation 4 Safe Mode System Software Update & Reinstallation Guide): Dual-Beep Hardware Entry Sequence and PS5/UPDATE/PS5UPDATE.PUP FAT32/exFAT Specifications.
• Micron Technology / Micron (Micron SSD Power-Cycle Recovery Protocol) & JEDEC (JESD218 / NVM Express Specification): Flash Translation Layer (FTL) Logical-to-Physical (L2P) Rebuild During Uninterrupted Idle Power States.
• ASUSTeK Computer Inc., Netgear Inc., & TP-Link Technologies (CFE miniWeb & U-Boot TFTP Bootloader Recovery Specifications): RFC 1350 Trivial File Transfer Protocol (TFTP) Binary Firmware Injection and Rear-Panel USB BIOS FlashBack Microcontroller Recovery.