i have the following problem. I flashed one Unifi AC Pro and configured it manualy with the settings we needing.
I saved the config via Webgui. The tar ball contains the "etc" folder with all configs.
I made an image with the imagebuilder and followed the instructions which described here:
I create the files folder at root of the image builder where I execute the make command.
I copied the etc folder from the config backup of the manual configured AP to the files folder of the image builder.
I checked with "make info" which profile I need for the Unifi AC Pro and executed the make command.
The FW was build.
I take a new Unifi AC pro AP and downgrade it to first Version 3.7.8
I copied the custom built FW to the "tmp" folder of the new AP.
I followed the instructions of the "Non-invasive method using mtd from unifi"
SSH to your UniFi:
default ip address is 192.168.1.20
default login is ubnt
default password is ubnt
Copy this fils to /tmp
You can use tools such as nc or scp to transfer files
Flash new firmware:
mtd write /tmp/openwrt-*-squashfs-sysupgrade.bin kernel0
mtd erase kernel1
Set bootloader to boot from kernel0
dd if=/dev/zero bs=1 count=1 of=/dev/mtd4
Reboot the device
After reboot, the white LED keeps blinking. The AP didnßt request an IP via DHCP and i can´t reach it via the static IP 192.168.1.20 (in this case my PC has the static IP192.168.1.10/24)
Anyone nows what the Problem is and how I can recover the AP. I tried to hold the reset button for round about 5 sec. after I power on the AP with POE. The AP makes a reboot.
After a while the AP began to blink the white LED again.
I can´t reach the AP. It looks that the AP didn´t have any IP.
The default address for OpenWrt is 192.168.1.1 unless you've changed it
EDIT: and wrt recovery - press the reset button while plugging in power and keep the button pressed until you see the tftp recovery led pattern (white - blue - off - repeat). This might take more than 5 seconds.
I got the dead APs working again with pumpkin. So the AP has the static IP 192.168.1.20. It was possible to tftp the first unifi fw 3.7.8 to the AP with pumpkin.
I thought the AP has no IP cause it didn´t answer to my ping, but the tftp connection to the AP worked.
Now I setting up a new Ubuntu VM and try to built the custom firmware again....
You don’t need to define them as packages, the packages defined in the profile config are installed automatically if you choose that profile.
“PACKAGES=“ are only for ad ons like luci, luci-ssl, openvpn, banip, adblocker or what ever you want to have for ad ons in your build. You don’t specify depenables ether since image builder installs them automatically.