Closed srett closed 9 months ago
The content of AVM's answer is solely in responsibility of AVM.
But the previously installed version of firmware was rather old - it was lacking the newer version of the configuration file (juis_boxinfo.xml
). Even if the script tries to get the correct values from the older version (jason_boxinfo.xml
) it seems, the values from your device aren't supported by the JUIS server. If you add a Version=141.06.60-00000
parameter to your call, the current firmware version will be found:
...
vidar:~ $ juis_check fb6490 Version=141.06.60-00000
usr/local/bin/juis_check: Found newer version: 141.07.57
URL=http://download.avm.de/fritzbox/fritzbox-6490-cable/deutschland/fritz.os/FRITZ.Box_6490_Cable-07.57.image
vidar:~ $
...
So your result wasn't the expected one, but the script isn't in charge for this.
Feel free to reopen this issue, if needed ... I'll close it with my answer for now.
Thanks for the quick reply; that's odd indeed. I actually ended up with a second 6490 which was running some early 7.x version, and also got the same result, i.e. nothing. What's weird is that both boxes seemed to be unbranded, regarding both the box design itself and the readout of firmware_version (but I'm not sure about provider additives). Yet they didn't have an update option in the WebUI: neither online check nor manual upload of an image file. With the older box from the initial post, I could use the devtools hack described here to upload the 7.57 image via browser, but the second box with the 7.x firmware required me to use the adam2 method. Both boxes now show the update feature in the WebUI. Both appear to be working so far, but I'll only find out about the cable modem part over the holidays when it's time to fix all the family IT issues. :smile:
Well hopefully search engines will pick this up and people will end up here should they have the same problem.
but the second box with the 7.x firmware required me to use the adam2 method
It's the safest and fastest method for ("external") firmware updates on the cable boxes by AVM, anyway. There aren't any preconditions, which a device had to met - and it will work always (at least with Puma6-based devices).
There are some options in AVM's firmware, where online updates may be disabled - it's not a "one and only setting" thing, that may be reverted/circumvented in ONE safe way. Therefore the safest approach is to install a fresh retail firmware version, after the device has been initialized with factory settings first.
However, after some googling I simply found https://download.avm.de/fritzbox/fritzbox-6490-cable/deutschland/fritz.os/ so was in the end able to update my box, but just to let you know in case this is not expected behavior.