if you started the update procedure with @alext firmware, then it will have unpacked it, and started to do the update… and started overwriting files, which now are being used even if you try to install a new firmware 
there are a few ways to try to get ‘unstuck’
a) if you know linux
then you can attempt to ssh into nebulae, and see what process is sticking… what is mostly likely (in my experience) is that the main nebulae.py is failing, and keeps getting restarted.
that said, given you have not seen the other green leds etc, that implies the calibration may be failing for some reason… but impossible to know.
(note: you may find you need a few attempts to ssh into it… if the main nebulae process is failing the constant failing/restarting - means the neb has little cpu left to process the ssh request - also I find using an ethernet cable can be more likely to work)
unfortunately, I cannot walk you thru this, as there are too many ‘moving parts’
but, if you can do this to debug, then this is useful, since hopefully the underlying ‘issue’ could be fixed,
but you need to know your way around linux, read scripts - and be able to track down what is going wrong.
b) revert firmware
the nebulae looks for a file on the usb stick called
revert_to_factory_firmware
(no extension)
this attempts to revert to the original firmware that shipped with the nebulae.
however, Ive heard its not always successful.
c) re-flash the sdcard
this will work… basically take the sdcard and use an sdcard read/writer to put the original image back on it.
see : this link when someone has uploaded the firmware.
obviously b/c will put you back to the beginning, so if you want my firmware again, you will have to re-apply it.
edit: yeah, not surprising the wifi stuff still works, as it runs in parallel to the nebulae process - so if its die-ing the wifi/browser will still work ok (assuming enough cpu left over to process requests)
