Containers Created Using Quickboot Not Showing Up In Nxe Dash

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
I have a JTAGed Xbox 360 console (Falcon, with latest FreeBOOT - JTAGed it myself). I am using an original Xbox 360 HDD as well as an external FAT32 formatted USB HDD (plugged into USB port 0 on the front of the console).

I have copied over XeXMenu v1.1 and NXE2GOD v1.1 (the LIVE containers) to my Xbox 360 HDD and they both show up (in the NXE dash) and work fine. XeXMenu v1.1 also recognizes my USB HDD and I am able to launch the files I have on it (ex. I launched FSD).

I have Flash360 and Freestyle Dash on my USB HDD in the following locations:

usb:\Flash360\Flash360.xex
usb:\Freestyle Dash\default.xex


I know I can use DashLaunch to boot directly to FSD and load my things form there, and I have set this up on many consoles before, but I do not want to do that for this Xbox 360.

I tried using both QuickBoot v2.1 & v1.2 ...




As you can see I did the same thing with QuickBoot v1.2 and it created the container for me. I copied it over to my Xbox 360 HDD but it didn't show up. I did copy it to the correct location... Content\0000000000000000\C0DE9999\00007000\.

What am I doing wrong here?

Any help is appreciated. Thanks!


EDIT: Here are some more pictures of how I have things set up:



I redid it multiple times, modifying the path name, pictures, the type of container, etc. I have no clue why it is not working :(.

Is there a way to make an actual container (not a shortcut to the files at a different location)?

EDIT 2: I made a container using XLAST (Xbox 360 and Live Authoring Submission Tool) following this guide, and FSD showed up under game demos in the dash, but when launched, it did not work properly.
 
Last edited:
First, have a look here: http://team-xecuter.com/forums/showthread.php?t=55626

Secondly, when you are using QuickBoot 2.1 you don't type "usb:\" or "hdd:\" before the actual path. For example, instead of writing "usb:\fsd\default.xex", try writing "\fsd\default.xex". OK?
 
Last edited:

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
Thanks M AzeeM K, that worked! I was able to create containers for XM360 and Flash360, but I am still having problems with FSD2. I used the one you created and it worked the first time, but then after deleting it and trying it with my own, neither my container nor yours showed up in the dash.

Are spaces allowed in the title and/or path? Does the name of the container and/or title/name (that you input in QuickBoot) have to be the same as the name of the folder the .xex is in?
 
Thanks M AzeeM K, that worked! I was able to create containers for XM360 and Flash360, but I am still having problems with FSD2. I used the one you created and it worked the first time, but then after deleting it and trying it with my own, neither my container nor yours showed up in the dash.

Are spaces allowed in the title and/or path? Does the name of the container and/or title/name (that you input in QuickBoot) have to be the same as the name of the folder the .xex is in?
No problem ;)

Although there shouldn't be any problem with using spaces, but it seems like that it does cause some problem. Probably this is the reason your Quickboot container didn't work. Try creating a container with no spaces in the path and see if it works.