you can't know what firmware there is on a x0xb0x unless you can identify it yourself (by some specific feature or behaviour)
when you start uploading a firmware to the x0xb0x - the bootloader starts overwriting the firmware sector
- if something goes wrong (the process is interrupted or some error occurs) - you will likely end up with a corrupted firmware - the x0xb0x will not restart normally, but the bootloader should still work afterwards
- if the process runs smoothly - you will have a freshly (over)written firmware, restarting the x0xb0x should run the firmware nicely...
so basically, if after updating the firmware - the process runs smoothly, and then the x0xb0x firmware runs after the restart - you have updated the firmware successifully
when i wrote c0nb0x, i added extended messages to the serial protocol, to make it possible for the app to "ask" the firmware "what firmware are you, and what is your version" - MSG_FW_VER
then, any firmware dev could add support for this in his firmware, and you will then be able to really tell what firmware you're running on the x0x by just connecting with c0nb0x
but that happened.. in 2012 or something.. that was too late for most firmwares
it can be added into the stock firmware - but what's the point?
it can't be added to sokkos, because there's no space left and sokkan would have to remove something else
MSG_FW_VER is supported in my firmware... yeah... oh well
to sum it up:
if c0nb0x says "(auto) ...." then it's autodetected/guessed ... the firmware itself didn't identify itself, so ignore what c0nb0x says about firmware name and version
if you aren't sure what firmware you actually have on your x0x - you could just upload one and then you'll know (of course, if you sell that x0x to another person - he won't know, unless you tell him... you get the point)