Firmware Updating Tip

[knowmiddlename]

I've discovered AZBox Elite firmware must be renamed "patch.bin" whenever doing a complete application area format. Long file names such as, "azbox-0.9.3932-patch.bin" must be changed to "patch.bin" for the upgrade boot menu to appear. Long file names work fine if loaded over existing firmware without reformatting. I hope this helps anyone having the same issue.

 

[B.J.]

I've discovered AZBox Elite firmware must be renamed "patch.bin" whenever doing a complete application area format. Long file names such as, "azbox-0.9.3932-patch.bin" must be changed to "patch.bin" for the upgrade boot menu to appear. Long file names work fine if loaded over existing firmware without reformatting. I hope this helps anyone having the same issue.

Strange. I've never gotten any file with a name other than patch.bin to show up on the list to choose from, whether reformatting or not. I was hoping to use longer names so that I could choose which file to use without pulling out the USB stick, but only the one named patch.bin showed up. I'll have to try that again, next time I want to upgrade.

 

[AcWxRadar]

I've discovered AZBox Elite firmware must be renamed "patch.bin" whenever doing a complete application area format. Long file names such as, "azbox-0.9.3932-patch.bin" must be changed to "patch.bin" for the upgrade boot menu to appear. Long file names work fine if loaded over existing firmware without reformatting. I hope this helps anyone having the same issue.

Strange. I've never gotten any file with a name other than patch.bin to show up on the list to choose from, whether reformatting or not. I was hoping to use longer names so that I could choose which file to use without pulling out the USB stick, but only the one named patch.bin showed up. I'll have to try that again, next time I want to upgrade.

Guys,

Be careful here. This is not quite correct as I have recently determined for myself. This subject is a little convoluted. It depends upon your PC's operating system and the original downloaded firmware file as to how you rename the firmware and how you are attempting to load it.

If your operating system embeds the file extension (.bin) automatically, then you will want to rename the file as "patch" only. In this case, if you rename it as "patch.bin" the AZBox will see it as "patch.bin.bin" and that file will be ignored.

The best strategy to adopt here is to rename the file as "patch" and copy that to a USB thumbdrive. Insert this thumdrive in your AZBox and REBOOT. If the AZBox OS recognizes the file as a legit patch, you will be prompted with a menu "Patch file found on USB" or something to that effect and all will be fine.

If the AZBox does not automatically identify the patch and simply reboots back to the TV menu, then power down and remove the USB thumbdrive. Reconnect the thumbdrive to your PC and rename the file as "patch.bin" and try again.

This is very confusing and caught me unaware as I was doing it one way (renaming the file as "patch.bin"), then they changed the tune here recently and I had to rename it as simply "patch".

You will know this right off if you are using a USB thumbdrive to upgrade your firmware. No harm will come regardless of how you rename the file, but the AZBox will simply not recognize that the patch file is there if it is not named correctly.

Do not force the file to load (if not automatically identified). You can do this (sort of circumvent the automatic detection of a new firmware file) through the setup menu, but the file won't load properly and will cause some annoying and unpredictable problems.

RADAR

 

[putney]

Yeah I found this whole thing kind of weird. How are you supposed to keep different patches on a thumb available for updating. You would think that the coders would've allowed for that!

 

[knowmiddlename]

Yeah I found this whole thing kind of weird. How are you supposed to keep different patches on a thumb available for updating. You would think that the coders would've allowed for that!

On your Windows PC, if you right click on the file and go to properties, then select details, you can get the exact file name of patch.bin.

ACWXRadar
I am referring to the long file names for "daily updates" at AZBox Daily Snapshot.

 

[Mr Tony]

I've never renamed any of mine and they loaded just fine...but then again I only keep the current software on the thumb drive

 

[putney]

On your Windows PC, if you right click on the file and go to properties, then select details, you can get the exact file name of patch.bin.

ACWXRadar
I am referring to the long file names for "daily updates" at AZBox Daily Snapshot.

On my mac it's even easier!

 

[guapoharry]

On my mac it's even easier!

 

[AcWxRadar]

Yeah I found this whole thing kind of weird. How are you supposed to keep different patches on a thumb available for updating. You would think that the coders would've allowed for that!

Putney,

In this instance I have created a file system where I download the individual firmwares into a file folder that is named with the version number of the release. I retain all the files in this manner so that I can differentiate between them fairly easily. If I need to apply (load) any one specific file, I apply the rules necessary for that individual file as appropriate.

On your Windows PC, if you right click on the file and go to properties, then select details, you can get the exact file name of patch.bin.

ACWXRadar
I am referring to the long file names for "daily updates" at AZBox Daily Snapshot.

Knowmiddlename,

I personally don't want to set my AZBox up to automatically update my firmware files. I want to have control over the whole thing. I don't exactly trust everything out there and if I test something, I want to be the one responsible if it screws up. I like to hear from others a few comments regarding a specific firmware application first, maybe give it at least a couple of weeks before I try it in case there is a bad bug.

I've never renamed any of mine and they loaded just fine...but then again I only keep the current software on the thumb drive

Ice,

You will have to make some adjustments with the newer software, otherwise it may not load from a USB drive. If they release it officially and offer it via the official URL, then I think the version will appear naturally and you can download it from there directly without any problem.

I was OK up to version 0.9.3686 and loaded all versions via my USB thumbdrive in the same manner. At or after version 0.9.3686, something was altered.

This is not a really bad thing as nothing will become fouled up as I mentioned earlier. Simply, you will know that it is not working properly as the AZBox will simply not realize or recognize that the patch is present. It will simply skip over the patch and reboot.

The receiver should find the patch file and stop somewhere during the reboot process and tell you that it detected a new patch file and give you some options before continuing.

EDIT: I want to ensure that everyone realizes that no harm or foul will come of your AZBox if you do this incorrectly. The AZBox will simply not find the new file if it isn't named correctly. So you can play around with the file name until it works for you, when the file name is correct, it (the AZBox) will play ball with you.

RADAR

 

[Mr Tony]

Ice,

You will have to make some adjustments with the newer software, otherwise it may not load from a USB drive. If they release it officially and offer it via the official URL, then I think the version will appear naturally and you can download it from there directly without any problem.

I was OK up to version 0.9.3686 and loaded all versions via my USB thumbdrive in the same manner. At or after version 0.9.3686, something was altered.

This is not a really bad thing as nothing will become fouled up as I mentioned earlier. Simply, you will know that it is not working properly as the AZBox will simply not realize or recognize that the patch is present. It will simply skip over the patch and reboot.

The receiver should find the patch file and stop somewhere during the reboot process and tell you that it detected a new patch file and give you some options before continuing.

RADAR

I made no adjustments. I downloaded the file and saved it to the thumb drive. Put thumb drive in azbox and went to settings. Selected USB and hit "OK"
newest popped up (3911 is what is in mine right now). Hit OK and it downloaded and rebooted with no errors.

Didnt rename it or anything

 

[AcWxRadar]

On my mac it's even easier!

Putney,

Your information may be highly important to other Mac users. I take it that your Mac is working very well with the AZBox.

RADAR

 

[putney]

Putney,

Your information may be highly important to other Mac users. I take it that your Mac is working very well with the AZBox.

RADAR

I was referring to renaming a file and copying files to usb thumb drive.

I use cyberduck or transmit for ftp file transfers.

Everything else is done on XP in parallels; Maz, Az Remote, etc.

 

[knowmiddlename]

Knowmiddlename,
I personally don't want to set my AZBox up to automatically update my firmware files. I want to have control over the whole thing. I don't exactly trust everything out there and if I test something, I want to be the one responsible if it screws up. I like to hear from others a few comments regarding a specific firmware application first, maybe give it at least a couple of weeks before I try it in case there is a bad bug.
RADAR

I'm with you, my AZBox doesn't automatically update nor would I want it to. The purpose of my initial topic was to help others perform a success applications format. So far, I have discovered the applications area formatting issues were due to bad firmware versions and, in my post today, the apparently bad firmware file name structure from the daily update site. :tux: