Print

[dschu012]

QUOTE(hazed69 @ Aug 7 2010, 07:35 PM)

well do I need to reflash my NAND or can I just delete ini and launch exe in the flash folder?

launch.xex needs to be flashed to your nand. the ini does not.

[jayboy86]

hi guys, i have been looking to auto boot to FSD2.0 and i have been using scene and google to find a decent guide as i havnt got a clue :/

i have a xenon 360 with cygnos360 v2, on the cygnos i have freeboot 0.032 dash 9199 and i would love to be able to use dash launch to start FSD2.0 on boot.

any help would be an amazing help, or any known guides too.

thanks guys

[jhoff80]

QUOTE(finalman @ Aug 8 2010, 01:16 AM)

Where do we get this from? I can't find it on xbins.

It's definitely there.  I believe it was in a system tools section or something like that.

There's not much of a readme though.  Can this be flashed without having to rebuild an entire freeboot image?

This post has been edited by jhoff80: Aug 8 2010, 08:25 PM

[hazed69]

QUOTE(dschu012 @ Aug 8 2010, 02:57 PM)

launch.xex needs to be flashed to your nand. the ini does not.

what i was trying to say is do i just go to my flash folder and delete the ini from the nand
thats were they go when you flash it to the  or should i just get my freeboot nand and flash my console again

this is really a pain
can somone check there launch .xex and see what it does when trying to run it
mine says that the game was not found and try downloading it again

This post has been edited by hazed69: Aug 9 2010, 04:24 AM

[f0xrolder]

QUOTE(danthaman673 @ Aug 8 2010, 09:22 PM)

Try renaming the fsd2 alpha folder to: FSD2Alpha (no space) also watch cases and save in UTF-8 also cut and paste ur paths, they seem wrong for freestyle, get ur default working off the HDD with something like xexmenu using the example.ini and then use flash installer to flash ur newer .ini Also if the dashlaunch patches were incorrectly applied it can cause issues, If ur using bestpig's toolbox then I find checking then Nand option worx best (Don't forget to flash ur UTF-8 .ini from the flash installer folder afterwards)

I got it to work by editing the INI to look like this

[QuickLaunchButtons]
Default = LUsb0:\FSD2 Alpha\default.xex
BUT_X = LHdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

also coppied the xex and ini to hddx so im not sure if it was by doing that or the ini edit but when i restarted and it went straight to dash a few days back was as happy as larry

[finalman]

Is it okay to use the xbox to format the unformatted MU (Erased with nandpro command: nandpro lpt: -e512 1000) after flashing the updated dashlaunch BB patch to the nand?

[garus]

Sure, there's no other way to format it, AFAIK. I tested that patch by filling the MU and then restarting Xbox. Still works ;p

This post has been edited by garus: Aug 9 2010, 08:21 AM

[madusmacus]

I find this a bit wacky that dashlaunch fixes a bug in freeboot?
was this not a freeboot issue ?
i have 2 512 jaspers and im to scare to use MU :¬)

[CasioNo15]

QUOTE(madusmacus @ Aug 9 2010, 10:18 AM)

I find this a bit wacky that dashlaunch fixes a bug in freeboot?
was this not a freeboot issue ?
i have 2 512 jaspers and im to scare to use MU :¬)

It´s not really a freeboot/xbr bug. It´s just that Xell is written to offest 0xC6000 on the nand, but that´s also a part of the reserved area for the MU on BB Jasper boards. So if you are writing something to your MU, this area may become overwritten. This patch just forbids NXE to write on that area, so it should be good to use the MU now with the patch.

Casio

[hazed69]

QUOTE(f0xrolder @ Aug 9 2010, 06:21 AM)

I got it to work by editing the INI to look like this

[QuickLaunchButtons]
Default = LUsb0:\FSD2 Alpha\default.xex
BUT_X = LHdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

also coppied the xex and ini to hddx so im not sure if it was by doing that or the ini edit but when i restarted and it went straight to dash a few days back was as happy as larry

do me a favor delete the hddx ini and xex and see if it still works?

[manbearpig_06]

QUOTE(cory1492 @ Aug 8 2010, 08:17 AM)

As to going back to NXE "when it's not meant to" - usually a disk is involved - especially if it's spun down to idle (ie: playing NXE installed game, leaving a disk in while playing a GOD), I believe it was stated that this is a known bug though I've never seen any issues with running xexmenu con or whatnot after, and I've caused it to happen on purpose a few times by messing with the dvd tray.

The exact same thing happens to me. It boots to xexmenu, but when you click Y on the guide it goes to the NXE and refuses to let xexmenu run from the con. No disk involved, so I don't know.

This post has been edited by manbearpig_06: Aug 10 2010, 03:25 AM

[madusmacus]

QUOTE(CasioNo15 @ Aug 9 2010, 04:22 PM)

It´s not really a freeboot/xbr bug. It´s just that Xell is written to offest 0xC6000 on the nand, but that´s also a part of the reserved area for the MU on BB Jasper boards. So if you are writing something to your MU, this area may become overwritten. This patch just forbids NXE to write on that area, so it should be good to use the MU now with the patch.

Casio

thank you for the explanation :¬)

[Saleian]

This is first post in any forum ever (desperate)

Hi everyone I finally got dashlaunch to start FSD2 on boot on freeboot v0.032. Actually its been working for awhile now. My question is how to I return to FSD2 from a game. My ini Looks like this. I'am using patch pack 5 Freestyle Launch.xex. I tried to use patch pack 5 custom launch.xex because when I put    Default = LHdd:\Freestyle\FreestyleDash.xex;   in my ini for Freestyle launch it wont boot up to FSD2. So I cant seem to have Default = in any launch.xex's. Also I tried holding BUT_Y and BUT_X before going back to NXE. Does people know that they have to change default.xex in freestyle to FreestyleDash.xex (case sensitive) because freestyle launch expects it. So the only thing that has ever worked is booting into FSD2...thats it. Dont get me wrong thats fantastic. Just want to know if I can return from game. Also plugin section is this correct. This is from the read me or is it supposed to be  plugin1 = \Usb0\hddalive.xex. I dont even know if hddalive is even working.  Can someone please tell me what im doing wrong if iam. Ive done everything there is to do with a jtag so I know my way around but this is crazy. A notepad/ini is going to be the end of me

[QuickLaunchButtons] (wont work if I use this)
LHdd:\Freestyle\FreestyleDash.xex;                                    Do I still need these ;;;;;;;
BUT_Y = LHdd:\Freestyle\FreestyleDash.xex;
BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558;
[plugins]
plugin1 = \Device\Mass0\hddalive.xex

[f0xrolder]

QUOTE(hazed69 @ Aug 10 2010, 03:49 AM)

do me a favor delete the hddx ini and xex and see if it still works?

I removed the two files, launch ini and xex from HDDX and it loaded straight to fsd2 buddy. This is exactly what my ini looks like

[QuickLaunchButtons]
Default = LUsb0:\FSD2 Alpha\default.xex
BUT_X = LHdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

[ImRickJamesB1tch]

QUOTE(Saleian @ Aug 10 2010, 09:11 AM)

This is first post in any forum ever (desperate)

[QuickLaunchButtons] (wont work if I use this)
LHdd:\Freestyle\FreestyleDash.xex;                                    Do I still need these ;;;;;;;
BUT_Y = LHdd:\Freestyle\FreestyleDash.xex;
BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558;
[plugins]
plugin1 = \Device\Mass0\hddalive.xex

You missing the default from the first line...And no I don't use the semi colons and it works fine. Save the below as the UTF-8 format and put it on the root of your harddrive:

[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
BUT_Y = LHdd:\Freestyle\FreestyleDash.xex
BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558