Hi
Trying to install the 2.1 version from the maintenance menu but it fails without any entry in the log. Hitting “retry” gets me “installing (null)” but with no success at all and I stop the retry after a couple of minutes (10). Again there is no entry in the log.
My network is working fine, checked via ATV.
Any one else having installation problems on v 2.1?
I get the same problem when trying to update through the “Maintenance update” option. I get the spinner then the report that ‘Installation failed’ if I click ‘retry’ it just repeats the procedure if i click ‘View Log’ the log is blank
Anyone got any ideas??
So, it looks like quite a few different issues going on here. I’ll try and address a number of the most frequent ones people run into.
If you're seeing any kind of errors when attempting to update via the Maintenance menu on the Apple TV, you may try re-running the aTV Flash (black) installer from a Mac or PC. Usually this will clear things up, but if not then please open a support ticket and send in a diagnostic report as described here. http://forum.firecore.com/topic/4291
If you're seeing an error when running the installer on a Mac or PC, then it's best to send in the 'FC_Installer.log' file (found in your Documents folder) as that will help us track down what's going on.
If you're getting a black screen, or the Apple TV won't start up after installing aTV Flash (black) this most likely means you're running a very old Apple TV version and need to update. aTV Flash (black) 2.0 and later will require Apple TV version 4.4 or later. Updating the Apple TV is as simple as running the latest version of Seas0nPass on your Apple TV.
If you're seeing errors when trying to update/install via SSH, then simply stop using SSH. ;) But seriously, for our sanity it's best to just run the installer and send in the log (as described in #2 above) if you're having any trouble.
I just solved my own problem and it was al due to that my memory was full in the ATV. I found that out while I was trying to do a full re installation and was prompted with the error code 2.2. After some searching in the forum I found out that clearing the cache could free up some memory. That worked for me and the installation worked fine now.