I am having problems trying to update to the latest firmware on my Azbox Premium HD. I have tried both via Internet method and USB with no luck. Via Internet, the file will download to around 50%, and then stop, giving me a "failed to update" message. Via USB, the box sees the file and I can select it. I get the "upgrading" message on the screen. After a few minutes, I get failed to update again. I tried rebooting with the USB stick in the machine, but it always reboots back to the settings screen. I never get that special upgrade screen. One strange thing that has happened, since I rebooted, is now my firmware version says 0.9.5020 Azbox Elite HD instead of Premium HD like it should. How do I get it to say Premium again? I have even tried to load older firmware to the box with the same results. Downloads go to about 50% and stop and the USB method fails to update. I have never had any problems up until now with updating firmware. What could be the problem?
Bruin95,
You might have a lot of territory to cover to find the answer on this one. Start off with the simple and easy things first and chip away at all the most logical and possible problems first.
First of all, using the USB stick to upgrade/update your firmware is the best and most safe method, so that is a good step in the right direction.
However, your USB flash drive - is it formatted with the FAT32 system? This is a must. If you suspect this to be a problem, try reformatting it again (save all the files to a backup if you have any on there that you really must have because you will lose them, obviously).
Secondly, do you have any other drives connected to your AZBox? An internal HDD, an external USB drive? Power down and disconnect these before you try to install the update.
Third, are all your attached drives (HDD's or other) formatted in FAT32 or formatted by the AZBox to ext2 or ext3 (linux)? If they are NTFS formatted, don't use them with the AZBox. They just don't like to play nicely together.
Fourth, when you are attempting to upgrade/update your AZBox firmware, which avenue are you using? In my sticky for doing this, I mention inserting the USB flash drive in the AZBox and rebooting. If the firmware file on the USB is properly "renamed" then the AZBox will detect this file during the reboot process and prompt you to install it. However, there is another method available to you in the MENU options. Press HOME > SETTINGS > SYSTEM INFORMATION > FIRMWARE UPGRADE > select USB and press OK and then proceed.
You might have to try this both ways to investigate and troubleshoot this problem.
Fifth, where did you download your firmware from? It might be best to try another source or maybe just try to download the same file over again. You might have inadvertently corrupted part of the file. This is rare, but it can happen.
Sixth, this is the bad one. I don't like to download the files (firmware) via internet directly to the AZBox. My internet connection is via satellite and it is slow. Since it takes longer than someone with a DSL connection, there is plenty of time for something to go wrong. A power dip or outage during the process would be really bad news. So, I like to get the file/s downloaded via my PC first, then (with my AZBox on a UPS) I can allow the box to upload without any fear of power interruption. If at anytime you suspect that this has occurred during your update process, you might have to perform a FORMAT APPLICATION AREA. Which basically means starting from scratch and reformatting the DOM/FDM. The DOM or FDM is just a SOLID STATE hard drive in the AZBox.
DOM = Disk On Module FDM = Flash Disk Module. They are basically just a hard drive, but they do not have the rotating disk or any moving parts. They are intended for industrial use most often. Places that could subject the unit to being dropped, banged and kicked around.
You understand what it is and why it is critical not to interrupt the process of updating? It is akin to the HDD of your computer. If you are in the process of updating and you lose power, even a glitch, you may have corrupted the DOM files. This would mean starting over from bare scratch.
I don't think that this happened to you. I think or I believe that you would detect much worse problems than what you are experiencing. But, I wouldn't rule it out completely. Try all other avenues first, use this avenue as a last resort.
I hope that my experience can help you in your situation. I purposely try to induce problems with my own equipment so that I can discover how to repair them, but sometimes I just don't know how to do everything and somethings are best left untested. I have compiled some good information, though. Please take advantage of it the best you can.
Do so at your own risk, of course.
Sorry, always gotta put that little disclaimer in there at the end.
RADAR