Can someone from Firecore provide an ETA on a resolution for this issue. I suspect there are many of us experiencing this who, in fact, aren’t inclined to SSH into our ATVs. Thanks.
how can I do to acces in my ATV?? with SSH?? I must “delete” some file or “rename” it?? Sorry but I’m not an “Hacker”… thnak you so much if you help me!!
If you own a mac use the terminal programm with following command ssh root@<ip-adress of your ATV> then enter the password when asked. Follow the instructions in this thread. That worked fine for me.
If you are a windows user download a freeware ssh client to do the same. If you don’t know the root password of the ATV, just ask google ;-).
Don’t post crap like this, we’re all having enough trouble as it is trying to get this to work. It’s not difficult to follow instructions but we can’t very well follow them if you don’t provide the information necessary in order to do it.
For the next person that reads this and has to waste time googling for the info the password is alpine.
I’m sorry but it really ■■■■■■ me off when people do this. I do appreciate your help though.
Mate, it was a standard “don’t blame me if you ■■■■ it up” post preventing people who are inexperienced from destroying their ATV and then telling me I gave them the wrong details.
If you did manage to find the password on your own, then great, it means you have more than 2 brain cells to smash together and are more likely to not destroy your ATV with the wrong command which is very possible as root.
It’s unfortunate things like this piss you off, but remember, I could have been a real prick and said “I fixed it on my own, thanks” and left it like that without telling anyone how to do it.
There was an updated version of SeasonPass released yesterday that fixed issues with installing some packages (such as XBMC) so it might be worth grabbing tht and starting again as that could well solve your problem?
Note that if a 3rd party package (such as XBMC) has its install broken for any reason (other than the jailbreak itself being the cause of the problem) then this is outside FireCore’s control - you need to wait for a fix from the package maintainer.