[skiboatm]

I'm at my wits end with this issue... I've got a Bullet M2 that I updated the AirOS to the latest version, and then downloaded and flashed the proper firmware from the website with the TFTP. Everything came up fine, but in Trial mode. Purchased professional activation, showed activated on the website. Copied coped into activation screen on router, clicked activate. It looks like it was working, then it flashed "Invalid Code" real quick and rebooted, wiping the config. Tried this a dozen or so times, reflashed router with same version, no change. Tried to rollback to AirOS via TFTP method (put Bullet in recovery mode, TFTP PUT proper firmware, device rebooted after it processed the firmware) and now it will not respond to ping or post. If I put it in recovery mode again, it responds to 192.168.1.20, but it won't respond to ping on any other address, and I'm pissed.

I spend the money on the activation and it failed, and I followed the instructions to revert to factory OS and it failed... what should I do now?

[skiboatm]

Anyone able to help on this?? Please?

[n0kfb]

Have you found an answer to this problem?

I just installed DD-WRT on a Bullet M2 a few days ago, and am trying to activate the full license without success.

I have not yet given up. If I don't find a solution soon I might.

--Dan Meyer

[Sash]

should be fixed in the latest beta.

[x3mspeleo]

Hello, I have the same problem with RocketM5. I installed the BETA version of DD-WRT and gets the exact same possible that the problem - I can not go back firmware UBNT ........ TFTP does not help. I had the intention to buy DD-WRT, but now it appears that I have broken Rocket M5 or at least allow me to restore the original firmvare.100% and others will eat this tree. What we do from now on, my dear specialists from DD-WRT

[x3mspeleo]

U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

DRAM: 64 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Board: Ubiquiti Networks XM board (rev 1.0 e1b5)
Hit any key to stop autoboot: 0
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: /
Receiving file from 192.168.1.5:50369
Received 7537126 bytes
Firmware Version: XM.ar7240.v5.6.6.29183.160526.1225
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x7a sector size 0x10000
...................................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

DRAM: 64 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Board: Ubiquiti Networks XM board (rev 1.0 e1b5)
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS Ubiquiti Linux-2.6.32.68
Created: 2016-05-26 9:26:41 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1008243 Bytes = 984.6 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...



SO STANDS TO THE END OF THE WORLD

[n0kfb]

Since I am not getting anywhere with DD-Wrt, and I could not back out to stock Ubiquiti firmware, I've opted to install OpenWRT on my Bullet M2 for the time being.

--Dan Meyer