davilla / atvusb-creator

Automatically exported from code.google.com/p/atvusb-creator
27 stars 53 forks source link

Stuck menu after patch #575

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Updated AppleTV 1 running v3.02 firmware with atvusb-creator 1.0b13 
patchstick, including all options.
2. Replaced ATVFiles to v1.3.0b1 via CyberDuck-SFTP and Terminal-SSH.
3. Installed latest XBMC and Boxee via Menu Launcher.
4. Everything working.
5. Played some songs (AACs) and then movie (MPEG-4 H.264 videoclip) thru normal 
aTV menu selection (like in the "old" days).
6. Music played fine, but movie got stuck, needed to deep restart with Remote 
Menu and Minus (-) keys.
7. aTV started again, but menu now stuck on first Menu item (Sapphire>...)
8. aTV "sees" Remote, as yellow light blinks when pressing keys on Remote, but 
nothing happens.

What is the expected output? What do you see instead?
Expected working menu (to follow Remote commands).
Instead I have stuck menu.

What version of the product are you using? On what operating system?
aTV v3.02
atvusb-creator v1.0b13 on OS X 10.6.6
XBMC v10.0
Boxee 0.9.... (latest)

Please provide any additional information below.
Can I get aTV running again by doing patch again?
What do I need to leave out? ssh tools, bin utils, SoftwareMenu, XBMC/Boxee for 
Mac?

Original issue reported on code.google.com by peter.bo...@gmail.com on 4 Feb 2011 at 11:07

GoogleCodeExporter commented 9 years ago
Wound up with being forced to reset the aTV to factory defaults (which meant 
v1.1 system software, duh!).
Synced it with iTunes, and upgraded again to v3.02 Apple system software.
Everything running smoothly, except... for that damn video file.
OK, so it's the videofile that's causing the stuck situation.
Strange, as it's running smoothly on my MacBook Pro (Unibody 2.53 GHz Core2Duo 
4 GB 15" w/ 24" LED Cinema screen attached) and my iPhone 4. I'll dig into that 
a bit more, but out of this realm really.
So now I only need to do all the patch work again...

Original comment by peter.bo...@gmail.com on 4 Feb 2011 at 8:06

GoogleCodeExporter commented 9 years ago
Oh, one more thing... (as I write this, it sounds strangely familiar...):
Running the faulty video on the patched aTV caused a stuck menu at the first 
menu item every time I went to reboot and restore. I could only get out of that 
by resetting to factory defaults.
Running the faulty video on the "standard" v3.02 aTV will cause the video to 
freeze, but I am able to reboot, restore and go to normal ops.
So, there is a difference...

Original comment by peter.bo...@gmail.com on 4 Feb 2011 at 8:10