Page 1 of 1

Error flashing ispy to AirRouter

Posted: Thu Sep 21, 2017 4:34 pm
by foxyboy
Help !

I was looking to to avail of usb support for the ubiquiti airrouter as its been made available in the current ispy.
I had previously flashed the airrouter to the latest XM 6.0.7, when i attempted to tftp ispy it failed with invalid firmware, i searched about and found issues related to a newer uboot which has likely been flashed thus preventing gargoyle upgrades
viewtopic.php?f=8&t=7352

I have now successfully downgraded the airrouter to 5.5 but still no success, a gui upgrade results in '
Bad firmware update image'
I am wondering if i have the new uboot even though i have downgraded ? Seems like a possibility

M.v5.5# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00100000 00010000 "kernel"
mtd3: 00660000 00010000 "rootfs"
mtd4: 00040000 00010000 "cfg"
mtd5: 00010000 00010000 "EEPROM"

Could anyone shed some light on what the issue is and whether i can rectify before i end up bricking the router ?

Re: Error flashing ispy to AirRouter

Posted: Thu Sep 21, 2017 5:46 pm
by Lantis
What steps did you follow the downgrade?

Re: Error flashing ispy to AirRouter

Posted: Fri Sep 22, 2017 5:13 am
by foxyboy
Hi Lantis,

I upgraded AirRouter to latest AirOs (6.0.7), then put it in recovery mode and then simply transferred factory gargoyle ispy fw using standard "tftp -i host put fw.bin" which resulted in an error. Tried also via AirOs gui and got a similar error.

After a little research, I then downgraded AirOS, eventually to 5.5 which was successful but still cannot upgrade to ispy 1.9.x. Thats why i now suspect i have modified the uboot by upgrading AirOS.

I am a little confused though as if a later AirOS fw has modified the uboot layout then i surely wouldnt be able to downgrade airos for the same reason i cant upgrade to gargoyle ?

I subsequently found this article, which suggests i might have to revert to an older uboot.
https://forum.openwrt.org/viewtopic.php?id=64326

I will have to try and locate my usb uart and see what i can discover.

Id rather not venture into potential bricking territory but am willing to try as i have use for these as gargoyle enabled routers but not really with airos.

Re: Error flashing ispy to AirRouter

Posted: Fri Sep 22, 2017 6:01 am
by Lantis
I can’t offer any advice other than that article. I’m not familiar with those devices unfortunate.

Re: Error flashing ispy to AirRouter

Posted: Fri Sep 22, 2017 8:08 am
by foxyboy
No problem, i will try the steps in the article in an attempt to revert the uboot to an older version and report back.

Re: Error flashing ispy to AirRouter

Posted: Sun Sep 24, 2017 10:41 am
by foxyboy
Ok, this is a little confusing but i can at least report success
i now have full usb support on my Airrouter :-)
Hope the following is of use to others.

Device Name:Gargoyle
Gargoyle Version:1.9.X (Built 20170917-2159 git@47fd60c)
Model:Ubiquiti AirRouter
Device Configuration:Gateway
Memory Usage:17.3MB / 27.9MB (61.9%)

Kudos to instructions from post3 here https://forum.openwrt.org/viewtopic.php?id=64326

I connected my my USB UART (CP210x) rebooted and interrupted the boot with Esc, then overwrote the uboot and installed AirOS 5.5.11

urescue -f -e

(on laptop) c:\>tftp -i 192.168.1.20 put XM.v5.5.11.28002.150723.1344.bin

I let AirRouter reboot fully then pulled power and interrupted boot to install AirOS 5.6.3
urescue -f -e

(on laptop) c:\>tftp -i 192.168.1.20 put XM.v5.6.3.28591.151130.1749.bin

reboot
AirOS gui flash back to 5.5.11

Now from what i can gather there were changes in AirOS 5.6.3 when i noticed the uboot version went to
U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

Having flashed back to 5.5.11 i am now back to
U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

I think 5.5.11 is the latest that works as you can only load signed firmware from AirOS 6.0.X.

I think ill park it there for now.

Re: Error flashing ispy to AirRouter

Posted: Sun Sep 24, 2017 4:41 pm
by Lantis
I’m glad the USB support issue is finally resolved