User Tools

Site Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
mission:log:2016:03:18:harder-soft-unbricking-a-bricked-ubiquiti-unifi-uap-pro-ap [2016/03/20 07:04] – [Harder Soft-Unbricking a Ubiquiti Unifi UAP-Pro AP] chronomission:log:2016:03:18:harder-soft-unbricking-a-bricked-ubiquiti-unifi-uap-pro-ap [2016/03/20 07:12] – [Step 3: Transfer jffs2 image to AP] chrono
Line 3: Line 3:
 {{:mission:log:2016:03:18:ubiquiti-unifi-uap-pro-inside-with-serial-debug-connected-sideview.jpg|ubiquiti-unifi-uap-pro-inside-with-serial-debug-connected}} {{:mission:log:2016:03:18:ubiquiti-unifi-uap-pro-inside-with-serial-debug-connected-sideview.jpg|ubiquiti-unifi-uap-pro-inside-with-serial-debug-connected}}
  
-Re-deploying the Ubiquiti Unifi UAP-Pro with OpenWRT (instead of Unifi) at the new base-camp revealed a problem: it simply didn't work anymore. No DHCP reaction, no default IP, nothing. Except for the LED blinking white after a reset, it seemed completely broken. After opening and attaching a terminal to the serial console, the boot output didn't look promising but at least it wasn't completely dead. So we had to get our hands dirty, pop the hood and hack around to fix this jffs2 corruption issue and revive the AP without costly and probably long/painful RMA.+Re-deploying the Ubiquiti Unifi UAP-Pro with OpenWRT (instead of Unifi) at the new base-camp revealed a problem: it simply didn't work anymore. No DHCP reaction, no default IP, nothing. Except for the LED blinking white after a reset, it seemed completely broken. Opening the case and attaching a terminal to the serial console, revealed bootloader output that wasn't promising but at least it wasn't completely dead. So we had to get our hands dirty, pop the hood and hack around to fix this jffs2 corruption issue and revive the AP without costly and probably long/painful RMA. Maybe this knowledge can help you too.
  
 ===== The Symptom ===== ===== The Symptom =====
Line 178: Line 178:
 </code> </code>
  
-The firmware image is stored in RAM now and occupies **0xf60000** bytes. Writing it from there to flash memory directly may fail when the target area has not been erased or if it is write-protected. Let's take care of that first.+The firmware image is stored in RAM now and occupies **0xf60000** bytes. Writing it from there to flash memory directly may fail when the target area has not been erased or is write-protected. Let's take care of that first.
 ==== Step 4: Reset partition table to defaults ==== ==== Step 4: Reset partition table to defaults ====
  
Trace:

Page Tools