Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous 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] chrono | mission:log:2016:03:18:harder-soft-unbricking-a-bricked-ubiquiti-unifi-uap-pro-ap [2025-04-24 17:45] (current) – chrono | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{: | {{: | ||
| - | 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. | + | 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. |
| ===== The Symptom ===== | ===== The Symptom ===== | ||
| Line 58: | Line 58: | ||
| </ | </ | ||
| - | This may be due to the fact that it expects a bricked UBNT firmware and NOT an OpenWRT installation. | + | This may be due to the fact that this workflow |
| ===== Solution 2 ===== | ===== Solution 2 ===== | ||
| Line 178: | Line 178: | ||
| </ | </ | ||
| - | 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 ==== | ||
| Line 238: | Line 238: | ||
| ==== Step 6: Erase the corrupt jffs2 ==== | ==== Step 6: Erase the corrupt jffs2 ==== | ||
| - | Figuring out the correct address and length was a bit difficult, uncertain, not well documented and took us quite a while, because we didn't want to brick it more by writing stuff somewhere other than we intended. Unfortunately, | + | Figuring out the correct address and length was a bit difficult, unclear, uncertain, not well documented and took us quite a while, because we didn't want to brick it more by writing stuff somewhere other than we actually |
| < | < | ||