Jump to content

UnleashX Returnes To Dash When Starting App/Game


Recommended Posts

Hi,

I just started up my xbox after having it stored in a box for around 10 years :) 
I have used HeXen 2018 to update to latest version of dash. But when I start my old games stored on the HDD it will first show the "Starting Game xxx" and after a couple of seconds boot back to the dash again.

The only things that works are:
- apps that are installed with the Hexen disk (Not XBMC)
- The Game Big Motha Truckers (starts but gets an error that the disk is dirty)

Any ideas of what the problem could be?

I have a Xecutor2 chip installed on the XBOX. If I turn off the chip it will not start but show an error.

BR

 

Link to post
Share on other sites

Error 05? That just indicates the HDD is unlocked which is what you expect with a chipped machine. So when you start with the chip off that is what you get.

What dash did you install from the HeXEn2018 disc (UnleaskX, XBMC?)? Did you install the new dash correctly for a chipped Xbox?

Can you post some screenshots from your file manager of the C:\drive and E:\drive contents and wherever your games are installed?

No point in trying to guess what is wrong until there is more information.

With a chipped machine you of course have the option to install any new HDD or blitz the existing one completely and restart from scratch. Copy (FTP) any stuff you want to preserve to a PC and make sure that includes the eeprom.

I'm not suggesting you do that but it is an option if there's no simple fix for whatever the problem is. 

Link to post
Share on other sites

Hi,

thanks for reply, I will try to answer all the questions.

  • I do not remember the error code when the chip was turned of. The switch is burried within the XBOX, so not easy to switxh it off.
  • I have installed all Dash from Hexen, at the moment I have UnleashX as active. I have started XBMC from UnleashX, but the as when starting games. Some noice from the HDD and after a few seconds going back to UnleashX.
  • I have the 0.39.0528A Build 584 of UnleashX. There was no special option when installing the Dash for Chipped XBOX.

You can see the files under C, E And F here:

https://ibb.co/K06TScZ
https://ibb.co/WkSNZH7
https://ibb.co/n3mFhwR

Link to post
Share on other sites

Not knowing what a chipped HeXEn install looks like but having experienced what it does post-TSOP if you let it "clean up" afterwards - I'm going by that. It seemed to install everything everywhere whether you were using it or not. There is purpose in that but hell's teeth it is a messy way of doing things.

Your C:\drive looks pretty normal to me for a chipped Xbox. The evoxdash.xbe there is probably your main dash. You can and should check that in UnleashX main menu > System > Settings > System >  Dash  Version (More Information) > UnleashX. It should show something like:-

Path C:\

Phy. Location \Device\Harddisk0\Partition2\evoxdash.xbe

If it shows something else - what?

The C:\xboxdash.xbe should be your working MS dash unless HeXEn has re-used the name for doing something else but there is no other XBE on C:\ so it is a good bet that is what it is.

The E:drive is where it starts to get odd (or maybe not for HeXEn). All fairly normal even the EEPROM backup being there if you used or HeXEn used ConfigMagic as "e" ie. the root of the E:\ drive is the default save location. But what that E:\Dash folder is doing there ..............I can only assume it is part of HeXEn's install everything policy and the contents of that would only be used if it was a softmod.

The F:\drive .........................I've seen nothing like that; a weird mix of EvoX, UnleashX and XBMC dashboards, even Avalaunch gets a look in. A loose "Skin" folder for XBMC and a second Skins folder for UnleashX and most peculiarly a second Item.xml and Config.xml. I know why they're there: because if that F:\evoxdash.xbe is used and it is an UnleashX dash they'd be automatically created. Similar the evox.ini if it were a Evox dashboard  XBE. But why that XBE is there. loose I can again, only assume it is HeXEn's install all policy ie. putting a backup main dash on F:\.  

TBH rather than trying to sort out what is causing the problem what I would do is get another virgin HDD and use AID v4.53 (Lite or Full) instead to set that up with a far cleaner dash install. It'll walk you through the initial formatting and then you can use its One-Click chipped/TSOP dash install option in the main menu. You cannot really go wrong with that.

The only downer is that most of the Apps it includes are not the most recent so you'll have to install them yourself from disc or by FTP. XBMC likewise: final version is v3.5.3.

Burn AID v4.53 on DVD-R with ImgBurn and be prepared for as long as 45 second delay when booting the disc.

Any idea what your chip BIOS is? You could try installing BIOSChecker and see if it recognises it.

       

Edited by HDShadow
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By halo-nine
      Hello everyone,
       
      i am new here and looking for some help! after over 15 years (possibly more) i got my old Xbox out of the attic for my children to play with. it has a Xecutor 2.3b Pro modchip, and had the EvoX M7 Bios. i happened to have an old redundant laptop with a 1tb 2.5" Sata drive not being used, so i decided to get the 80 wire cable, IDE to SATA converter and install a larger Hard drive.
      so last night i did this and discovered i needed to update the Bios to EvoX M8+ in order to see more than 130gb on the F: Drive. so i did this, initially selecting the wrong Bios (i assume!) as on the 'FLASHING BIOS NOW' screen (i used Hexen 2018) it got about 25% of the way through.... then just sat there, after 20 minutes,  I decided to had to turn off and it was FRAG!
      its been YEARS since i used the thing, and after some googled i realised i had the duel bios chip with the Dip Switches, so managed to get it to boot into the backup EvoX M7, this time, flashed again (the duff bank) with 256k EvoX M8+ F&G and everything worked perfectly (950+ GB on F:, way more than i will ever need!)
      so this morning, I managed to configure the FTP setting with a Crossover cable and transfer a couple of games to the HDD. they seem to run fine, but i have an odd issue:
      when i use the short cut on the controller (both shoulder buttons, Back + Start) to return to the dash.... the Bios WIPES itself!!! what the heck is going on!? anyone got any ideas?
      I can flick the Dip Switches and boot back into EvoX M7/Hexen and re-flash but this is a very odd issue! and i cant seem to find any info about it, has anyone experienced this? 
      thanks for your help, much appreciated!
    • By RexMundi
      I did search first before posting and couldn't find any threads specifically talking about this.  I'm sure I'm missing something obvious.  I have tested with an original XBOX S Type controller and a 3rd party controller.  I have also tested with a USB keyboard and an adapter.  None of which work when I enter XeniumOS.  However, the controllers work when modchip is disconnected.
      This is a 1.4 revision XBOX.  I assume it must be one of my solder joints to the modchip.  I have already reflowed these joints multiple times to fix another issue.  Unfortunately, I closed the machine up before I realized the problem.  Anyone know which pins I should focus on?  Is there a way to test continuity between LPC header pins and the motherboard?
      Thanks for any help you can provide.
    • By Amigaz
      I have an odd problem in XBMC4GAMERS, after my Xbox has been turned on for a while and I try and start a (hdd) game then progress "bar" just spins and nothing happens. If I then turn off the Xbox and turn it on again and starts the game without letting the Xbox be turned on for a while the game starts fine ... I have the same issue with the REBOOT and SHUTDOWN in XBMC4GAMERS .... this problem is not occuring when I start apps from XBMC4GAMERS.
      Any idea's?

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.