xboxscene.org forums

Author Topic: New, Skin Now After Flubber Locks Up  (Read 54 times)

sokignano

  • Archived User
  • Newbie
  • *
  • Posts: 16
New, Skin Now After Flubber Locks Up
« on: March 03, 2006, 11:16:00 PM »

Ok, I FTP'd Media Center Edition 2005 skin over to my Xbox, then I seleced it in the skin selector, after a couple of seconds the screen went black and I had no controls? So I waited thinking it needed time to load, but after about a min I see a Progression bar in the upper righthand corner move from low to high, then disappear, I try hitting A, B, X, Y, all the buttons. Nothin, so I clicked the Right analog stick and I got a menu, so I told it to Reboot, I didnt. So I manualy turned off the console then turned it back on. After the Flubber screen it changes to the grey XBMC logo, and does nothing, I tried FTP'ing to it but nothing, then I tried removing the ethernet cable and still locks up at XBMC logo. Any help would be great.

Take care and God bless,
Brian
Logged

pike

  • Archived User
  • Full Member
  • *
  • Posts: 222
New, Skin Now After Flubber Locks Up
« Reply #1 on: March 03, 2006, 11:54:00 PM »

use that bootdisc u created before starting messing with stuff
Logged

shloader

  • Archived User
  • Newbie
  • *
  • Posts: 39
New, Skin Now After Flubber Locks Up
« Reply #2 on: March 04, 2006, 12:11:00 AM »

1) FTP into your Xbox, Go to the E:\TDATA and E:\UDATA folders and delete any folders that start with the characters 0fac*****. Should be four altogether. (oh and delete any skins you added, leave PM3 skin)

2) Restart your box and it should be back to default settings.

3) Be happy with the Project Mayhem 3 skin (and if you're running a build that comes with Project Mayhem 2 then you have an old build. Update). No starwars or dragonball z themes or crap like that (I know you). Each CSV build breaks compatability of some skin or another as you've just seen. I've ran into too many issues with loading skins it's just not worth the headache. PM3 really is the best for current builds.

4) Check your email if you haven't already.
Logged

sokignano

  • Archived User
  • Newbie
  • *
  • Posts: 16
New, Skin Now After Flubber Locks Up
« Reply #3 on: March 04, 2006, 12:19:00 AM »

As of right now I cant FTP, I doesnt connect to my Xbox, but if ya know a way to get into my box then please. throw some knowledge my way. LOL shloader i didnt notice it was you till i got midway though the post when the starwars/dbz crack came in, then i had to look at the name.
Logged

Hades_666

  • Archived User
  • Full Member
  • *
  • Posts: 119
New, Skin Now After Flubber Locks Up
« Reply #4 on: March 04, 2006, 07:23:00 PM »

QUOTE(sokignano @ Mar 4 2006, 01:50 AM) *

As of right now I cant FTP, I doesnt connect to my Xbox, but if ya know a way to get into my box then please. throw some knowledge my way. LOL shloader i didnt notice it was you till i got midway though the post when the starwars/dbz crack came in, then i had to look at the name.



Boot disk with evox or some other dash. Then ftp over and clean it up e:\tdata\0000008 and e:\UDATA\0000008, reup the xbmc and the skin.  You are either using an incompatible version of xbmc which doesn't have the safety skin loader, which when an imcompatible or corrupt skin is attempted to launch PMIII will load still.

Hope it helps
Logged

shloader

  • Archived User
  • Newbie
  • *
  • Posts: 39
New, Skin Now After Flubber Locks Up
« Reply #5 on: March 04, 2006, 08:45:00 PM »

QUOTE(sokignano @ Mar 3 2006, 10:50 PM) *

As of right now I cant FTP, I doesnt connect to my Xbox, but if ya know a way to get into my box then please. throw some knowledge my way. LOL shloader i didnt notice it was you till i got midway though the post when the starwars/dbz crack came in, then i had to look at the name.


What you COULD do is boot the system with the mechassault disc and start the process all over again or atleast get to the point where ltools loads and you'll have FTP access. Yeah, try that. Once you do get FTP access clean out all those 0fac**** directories like I said and then completely kill your current XBMC install. I think you're using a rather out of date version.

Now refer to your email. I'm going to tell you exactly where to get your XBMC install so we're on the same page.
Logged