You are here

My Bullet Titanium won't take the 3.20.3.1 upgrade

5 posts / 0 new
Last post
wa2ise
wa2ise's picture
My Bullet Titanium won't take the 3.20.3.1 upgrade

I did my other nodes (two Airrouters, and two M900's) and only the Airrouters were a bit reluctant to do the upgrade (had to do them twice).  But I have a Bullet M2 titanium that just won't do it.  It keeps booting back to the old version, 3.20.3.0   Doing it over their LANs  hard wired. Must have tried it about 5 times, no dice.  
Maybe I'm using the wrong file aredn-3.20.3.1-ar71xx-ubnt-bullet-m-sysupgrade.bin

WTF.....

w6bi
w6bi's picture
SCP to the rescue
Try scp'ing the file to the node (put it in /tmp).
Then ssh to the node and run sysupgrade -n on the file.  If it fails, it'll tell you a bit more about why.

W6BI
wa2ise
wa2ise's picture
I tried SCP and ssh, got:

I tried SCP and ssh, got:

root@WA2ISE-QTH:~# sysupgrade -n aredn-3.20.3.1-ar71xx-ubnt-bullet-m-sysupg
rade.bin
Image metadata not found
Use sysupgrade -F to override this check when downgrading or flashing to ve
ndor firmware
Image check failed.

I'll try dpwnloading the file again, maybe it got corrupted?

Did this, same result.   Do I risk sysupgrade -F to override this check?

w6bi
w6bi's picture
-F
I wouldn't - you could end up with a genuine brick, IMO.

If you can do an md5sum on the binary file, it should be 5312852b64de0c6ef5de61d271692878
 
wa2ise
wa2ise's picture
I got it to do it, XM FW

I got it to do it, but I used the FW listed for the titanium bullet XM, with md5sum: c7779834840a58491d65e231d752f473
And it looks to be working normally. 

I suspected I might brick it if I did the -F

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer