A guided TFTP Server recovery tool for macOS
Use this page when a China Mobile RAX3000M eMMC, RAX3000Z enhanced, or XR30 eMMC has broken Wi-Fi after flashing ImmortalWrt. Start by identifying the current state of the router, then choose the safest next step instead of randomly flashing another image.
eMMC edition: The 64GB storage version of RAX3000M or XR30/RAX3000Z enhanced. It has different partition and bootloader assumptions from the ordinary SPI-NAND model.
factory / EEPROM: The partition and calibration data that help the wireless chips know their radio settings and MAC identity. Losing or replacing it blindly can make Wi-Fi fail even when the router boots.
Wi-Fi driver and firmware: The MediaTek wireless driver and related firmware files used by ImmortalWrt builds. A wired router can boot while the wireless stack still fails.
U-Boot Web recovery: A bootloader recovery page that some community U-Boot builds expose at 192.168.1.1 after the computer is set to 192.168.1.2/24. This is not the same as normal LuCI.
The ordinary RAX3000M SPI-NAND model and the 64GB eMMC edition do not share the same assumptions. Before choosing firmware, confirm whether the label, storage, LEDs, and partition layout match RAX3000M eMMC, RAX3000Z enhanced, or XR30 eMMC. If you are not sure, do not flash a random NAND or eMMC image because the name looks close.
This is the best recovery state. Keep using Ethernet, open LuCI, export a backup, record the current firmware name, and check whether the wireless page shows any radio device. If no radio appears, the next checks are driver and firmware packages. If radios appear but SSIDs are gone, rebuild the wireless network from LuCI before reflashing.
Use SSH only to inspect, back up, and confirm state unless you already know the exact commands. Check whether the device is the eMMC edition, whether factory data still exists, and whether Wi-Fi MAC addresses are present and not duplicated. Avoid writing factory or EEPROM data until you have backups.
Set the computer to the recovery network requested by the U-Boot build. In the referenced community path, that can be computer 192.168.1.2/24 with the recovery page at 192.168.1.1. Upload a known-good eMMC firmware for the exact model, then wait for the router to reboot. Do not upload NAND firmware or unrelated images.
Prepare the Mac before powering the router into recovery mode. Use Ethernet, set the temporary static IP required by the model guide, place the firmware in the served folder, confirm the filename, and allow TFTP traffic through the firewall. Router Recovery can help check these Mac-side pieces, but the router still decides whether it accepts the file.
At this point the page should save you time: this is no longer a normal beginner repair. The likely path may involve TTL serial, bootloader repair, GPT repair, or eMMC-specific recovery. Stop repeated power cycling and collect model-specific references before opening the device or writing partitions.
The referenced community build includes an option that uses an NX30 Pro EEPROM file and fixes Wi-Fi MAC handling from the factory partition. That can explain why a used eMMC router may boot but lose wireless behavior. It is a useful clue, but it is not the first thing an ordinary user should write to the device.
First restore stable wired access. Second confirm the model and firmware. Third back up factory and settings if possible. Fourth rebuild Wi-Fi configuration in LuCI if radios exist. Fifth use a known-good eMMC build if the wireless driver stack is missing. Only after those checks should EEPROM or factory repair be considered.
This page summarizes a community reference and one real recovery pattern for a used 64GB eMMC router. It intentionally leaves out dangerous command dumps and partition-write recipes. Read the original community repository before performing any EEPROM, factory, GPT, or bootloader operation.
No. It is a model-specific advanced checklist. Router Recovery can help with Mac-side recovery preparation, but EEPROM, factory partition, GPT, and TTL repair remain outside the app scope.
Do not treat that as a universal answer. The referenced community path uses an NX30 Pro EEPROM option and fixed Wi-Fi MAC handling for this device family. Use it only after understanding your exact hardware and backups.
No. TFTP or U-Boot Web upload may restore a firmware image, but lost or damaged calibration data is a separate problem. If wired access still works, backup and inspect first.
Probably not. This model is mainly a China-market router, but an English counterpart keeps the bilingual site structure consistent and helps document the boundary clearly.