Post by: WarriorSan on May 22, 2010, 06:59:00 AM
http://xbins.org/nfo.php?file=xboxnfo1849.nfo
This means keeping BC and reboot for example back into FSD..Nice!
This post has been edited by WarriorSan: May 22 2010, 02:20 PM
Post by: BrooksyX on May 22, 2010, 07:38:00 AM
Post by: hfmls on May 22, 2010, 07:48:00 AM
can someone post screenshots or videos pls?
Post by: dustin6908 on May 22, 2010, 09:04:00 AM
Post by: scuba156 on May 22, 2010, 10:12:00 AM
QUOTE(WarriorSan @ May 22 2010, 10:59 PM) 
Team XeDev released Dash Launch v1.0
:http://xbins.org/nfo...xboxnfo1849.nfo
This means keeping BC and reboot for example back into FSD..Nice!
it means much more that that
QUOTE
- added dll/plugin loading support
- added export to allow the loading of other system modules
- added export to allow the loading of other system modules
QUOTE(dustin6908 @ May 23 2010, 01:04 AM)
cant find in xbins?
/xbox360/dashboards/xexmenu/
Post by: BrooksyX on May 22, 2010, 10:16:00 AM
QUOTE(scuba156 @ May 22 2010, 09:12 AM)
it means much more that that
So what kind of stuff are you thinking this will allow for?
Post by: infidelity on May 22, 2010, 10:16:00 AM
Post by: Sonic-NKT on May 22, 2010, 10:17:00 AM
Post by: BrooksyX on May 22, 2010, 10:23:00 AM
QUOTE(Sonic-NKT @ May 22 2010, 09:17 AM)
I think it allows for example going back to FSD as Dash... also this could allow debugging on retail consoles in the future
Well obviously it allows you to go back to freestyle dash.
But i wanted to know what other features he was talking about.
Post by: Sonic-NKT on May 22, 2010, 10:35:00 AM
Post by: dufc1983 on May 22, 2010, 11:02:00 AM
Post by: dalton_743 on May 22, 2010, 11:14:00 AM
This post has been edited by dalton_743: May 22 2010, 06:15 PM
Post by: Sonic-NKT on May 22, 2010, 11:25:00 AM
but want to be sure that i did understand everything correctly.
1. add patches to freeboot folder and compile a new nand image with the new patches included
2. Flash this new freeboot image to your console
3. add launch.ini to the root of the HDD (i dont want to flash it straight to the nand)
thats it? or is a launch.xex still needed? do i have to use the one from the "flash installer" folder?
Post by: dufc1983 on May 22, 2010, 11:26:00 AM
QUOTE(Sonic-NKT @ May 22 2010, 06:25 PM)
Ok now i want to try this
but want to be sure that i did understand everything correctly.
1. add patches to freeboot folder and compile a new nand image with the new patches included
2. Flash this new freeboot image to your console
3. add launch.ini to the root of the HDD (i dont want to flash it straight to the nand)
thats it? or is a launch.xex still needed? do i have to use the one from the "flash installer" folder?
just wait dude sure a new freeboot image maker will be released to support this
Post by: BrooksyX on May 22, 2010, 11:30:00 AM
Post by: cory1492 on May 22, 2010, 11:36:00 AM
QUOTE(Sonic-NKT @ May 22 2010, 11:25 AM) 
thats it? or is a launch.xex still needed? do i have to use the one from the "flash installer" folder?
You have to run the flash installer to put launch.xex into flash.
Post by: scuba156 on May 22, 2010, 11:53:00 AM
QUOTE(BrooksyX @ May 23 2010, 02:16 AM)
So what kind of stuff are you thinking this will allow for?
It will allow for custom plugins running all the time in the background (ftp no matter what app your in, custom guide menu, debugging) that sort of thing
Post by: BrooksyX on May 22, 2010, 12:02:00 PM
QUOTE(scuba156 @ May 22 2010, 10:53 AM)
It will allow for custom plugins running all the time in the background (ftp no matter what app your in, custom guide menu, debugging) that sort of thing
Sweet, definitely looking forward to custom guide, hopping they can make one that strips away all the xbox live stuff since we wont be using it at all. Always having FTP in the background would be nice too.
Post by: DMAddict on May 22, 2010, 12:21:00 PM
Post by: WarriorSan on May 22, 2010, 12:42:00 PM
QUOTE(scuba156 @ May 22 2010, 06:12 PM)
it means much more that that...
I know it means much more then that but that was theoretically already possible when applying the memory protection patch (for plugins, trainers, emus etc. which rely on dynamic compilation) but then you would lose BC with this you ain't...
Post by: sanni on May 22, 2010, 02:15:00 PM
I copied the patches to the freeboot directory, build freeboot and renamed it to updflash.bin. Then flashed it with Flash360.
Then I edited the launch.ini and placed it in the root of the hdd.
After that I copied the flash_installer to the apps dir on my hdd and launched its default.exe to flash the launch.xex.
I didn't flash the launch.ini because it's better if its on the HDD, so I can change it via ftp.
Post by: iEzio on May 22, 2010, 03:30:00 PM
QUOTE(sanni @ May 22 2010, 10:15 PM)
Works like a charm.
I copied the patches to the freeboot directory, build freeboot and renamed it to updflash.bin. Then flashed it with Flash360.
Then I edited the launch.ini and placed it in the root of the hdd.
After that I copied the flash_installer to the apps dir on my hdd and launched its default.exe to flash the launch.xex.
I didn't flash the launch.ini because it's better if its on the HDD, so I can change it via ftp.
I did the same thing and it's working, but I think mine isn't working like it should.
I want to use Button 'A' for XeXMenu 1.1 and as 'Default' my FreeStyle Dash.
FreeStyle Dash is starting, if I'll start my console, XeXMenu is starting, if I hold the 'A' Button at starting my Xbox, that's fine.
But if I try to go back to FreeStyle Dash via the mini-dashboard, I've to hold the right trigger (RT) for it. The readme says, I just need to do this for booting in NXE, but mine will boot to NXE, if I klick nothing then.
So, I even tried to start XeXMenu that way, it won't start.
I just got the choice between FreeStyle Dash and NXE if I'll hit the 'Y' button in the mini-dash.
So, what's wrong there? - Shouldn't I boot back to FreeStyle Dash, if I klick nothing? - Shouldn't I be able to boot to XeXMenu, if I klick 'A' then, and shouldn't the NXE just came up, if I click the right bumper (RB)?
out of the readme: "Default is what loads when you hold no buttons"
help would be awesome, mates!
This post has been edited by iEzio: May 22 2010, 10:33 PM
Post by: antisniperspy on May 22, 2010, 03:56:00 PM
Example
rename patches_jasper.bin to updpatch.bin
then flash with flash360 1.0
Post by: royvedas on May 22, 2010, 04:08:00 PM
Post by: iEzio on May 22, 2010, 04:09:00 PM
QUOTE(antisniperspy @ May 22 2010, 11:56 PM)
Can we use Flash360 instead of creating a whole new image?
Example
rename patches_jasper.bin to updpatch.bin
then flash with flash360 1.0
You've to create the complete freeBOOT image out of the patches, then you can rename it to udpflash.bin and flash it via flash360 (even worked with my cygnos this way).
Post by: Kitkat on May 22, 2010, 04:19:00 PM
Here's a little video i made for showing the new basic fonctionnality
Post by: antisniperspy on May 22, 2010, 04:45:00 PM
QUOTE(iEzio @ May 22 2010, 06:09 PM)
You've to create the complete freeBOOT image out of the patches, then you can rename it to udpflash.bin and flash it via flash360 (even worked with my cygnos this way).
Ok thanks for the input. I was just hoping you would not have to do that because I have a 512 jasper. I just wanted to patch with the new patch.
Post by: Jurai on May 22, 2010, 05:35:00 PM
This post has been edited by Jurai: May 23 2010, 12:46 AM
Post by: xxpittbullxx on May 22, 2010, 05:39:00 PM
Thx Team Xedev
Post by: antisniperspy on May 22, 2010, 05:53:00 PM
QUOTE(xxpittbullxx @ May 22 2010, 07:39 PM)
Confirmed working on a Jasper256 BB
Thx Team Xedev
Did you compile a whole new image? And if you did how did you flash and how long did it take?
Just wondering because I have a 512 jasper.
Thanks
Post by: Kitkat on May 22, 2010, 06:00:00 PM
QUOTE(antisniperspy @ May 23 2010, 01:53 AM)
Did you compile a whole new image? And if you did how did you flash and how long did it take?
Just wondering because I have a 512 jasper.
Thanks
You need to build a 64mo freeboot image like a nomal nand for BBnand.
You can flash it with 360flash the redline99 soft (don't forget to rename the nand updflash.bin)
Post by: ddxcb on May 22, 2010, 06:02:00 PM
Post by: Jurai on May 22, 2010, 07:16:00 PM
edit: reuploaded all the compat xex, now it works. how is dash launch detecting the xb1 loader? do not all of the diff compat xex originally in xorlosers pack work?
This post has been edited by Jurai: May 23 2010, 02:20 AM
Post by: DarkProphecy on May 22, 2010, 09:08:00 PM
Post by: cory1492 on May 22, 2010, 09:26:00 PM
QUOTE(iEzio @ May 22 2010, 03:30 PM)
But if I try to go back to FreeStyle Dash via the mini-dashboard, I've to hold the right trigger (RT) for it. The readme says, I just need to do this for booting in NXE, but mine will boot to NXE, if I klick nothing then.
So, I even tried to start XeXMenu that way, it won't start.
I just got the choice between FreeStyle Dash and NXE if I'll hit the 'Y' button in the mini-dash.
So, what's wrong there? - Shouldn't I boot back to FreeStyle Dash, if I klick nothing? - Shouldn't I be able to boot to XeXMenu, if I klick 'A' then, and shouldn't the NXE just came up, if I click the right bumper (RB)?
out of the readme: "Default is what loads when you hold no buttons"
Not so much a "click" as a "hold button down" so after you press Y and OK in the mini dash, immediately after hold the button of the thing you want to start. Are you serious about the Right Trigger, or are you talking about the right bumper? It really should be going back to default item if you hold no buttons after telling it OK to exit to dash in miniblade.
QUOTE(DarkProphecy @ May 22 2010, 09:08 PM)
Doesn't seem to want to work when returning from an XB1 game. It goes to the NXE still. Works from 360 games and applications though, loads FSD. Anyone else have this problem?
Works fine here...
CODE
Known Bugs
- will very rarely wind up at NXE, usually related to ODD activity
- will very rarely wind up at NXE, usually related to ODD activity
Have a listen to your ODD in this case, see if it is spinning up from a low speed.
QUOTE(Jurai @ May 22 2010, 07:16 PM)
how is dash launch detecting the xb1 loader? do not all of the diff compat xex originally in xorlosers pack work?
I had a problem with some xefu too, it was because I had a xbox1 compatibility title update (some call it Fusion Update) in the main content partition $SystemUpdate folder - for the longest time all I could get to work was avalaunch.
Post by: ZprivateZ on May 22, 2010, 09:48:00 PM
- with the included patch set, launch.xex acts as a helper to detect when
xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
to function together.
Does it mean memory unlock is always there except when you launch an xbox1 title then it knows to switch to xbox1 emulator?
Post by: schubi on May 23, 2010, 04:04:00 AM
but the readme doesnt tell u need to use the flash installer in any case (option1 in readme doesnt say anything about that). or am i wrong ?
there also seems to be one problem.
default boot is freestyledash
when i go to nxe (by holding the RB override button) and then want to go back to freestyledash with the miniblades-thing, it just loads nxe again
going back to freestyle dash with the miniblades thing from any game works fine, just from nxe i cant get back to freestyle (usually xbox asks u if u do really want to go back to nxe bla bla, this is also not the case if u are already in nxe it just restarts nxe, nomatter whats in ur launch.ini).
anyone else having this problem ?
Post by: garus on May 23, 2010, 05:08:00 AM
I flashed launch.xex and launch.ini to nand with correct path to FreeStyle dash and it still boots to NXE, and sometimes there's just middle green light.
Post by: Lisko on May 23, 2010, 05:11:00 AM
Post by: iEzio on May 23, 2010, 05:11:00 AM
I tried to immediately hold the button, after I wanted to boot to XeXMenu, it's not working for me.
And yes, I'm talking about the right TRIGGER. With the bumper, nothing will happen for me.
Still, my DashLaunch 1.0 launches the NXE, if I klick nothing. But, if I start my Xbox360, it's working perfectely even with XeXMenu and FSD.
Post by: cory1492 on May 23, 2010, 05:50:00 AM
QUOTE(schubi @ May 23 2010, 04:04 AM)
when i go to nxe (by holding the RB override button) and then want to go back to freestyledash with the miniblades-thing, it just loads nxe again
It doesn't load nxe "again" - it only catches dash loads when dash.xex is actually run, when you are in a dash and use miniblade and tell it to exit to dash all it does is close miniblade app just like if you pressed the big X button again. I'd suggest just leaving miniblade open and make use of the quick launch feature it provides when in NXE... or alternately launch anything else and quit from it.
garus:
I was always under the impression that FSD 1.20 had to run from hdd? Or is that just the shortcuts for dash/cd loading that forces that path?
iEzio: do you have a disk (DVD/CD) in the drive when this happens and are you using a wireless or wired controller? It's very odd because this isn't even looking at anything that should be related to either trigger.
Lisko:
Can you try putting ini on flash and remove any others?
QUOTE
Why?
good question... when you figure it out let us in on it
I hear the answer is 42? funny no one seems to have read the readme for "known bugs", I see absolutely no mention of ODD (cd/dvd) disk presence from anyone who have mentioned a problem.
Post by: Lisko on May 23, 2010, 06:02:00 AM
This post has been edited by Lisko: May 23 2010, 01:06 PM
Post by: iEzio on May 23, 2010, 06:21:00 AM
Look at this:
(IMG:http://www.freewebs.com/junglefender/xbox360controller.jpg)
I've to hold '2' to boot back to FSD, that's the right TRIGGER for me.
EDIT: Everything is working fine now. Don't know why. I loaded the launch.ini to my flash, deleted it and loaded it back to my HDD. - Now, it's working!
This post has been edited by iEzio: May 23 2010, 01:52 PM
Post by: pulz on May 23, 2010, 06:57:00 AM
Anybody knows why, i have chosen option 1. Hd always connected.
I changed the freeboot patches, and uploaded a launch.ini file to the root of the hd.
Post by: garus on May 23, 2010, 07:53:00 AM
QUOTE(cory1492 @ May 23 2010, 01:50 PM)
garus:
I was always under the impression that FSD 1.20 had to run from hdd? Or is that just the shortcuts for dash/cd loading that forces that path?
Well, FSD 1.2 works perfectly ok when run manually through XeXmenu or by using freestyle-usb package in C0DE9999. it's just the DashLaunch that doesn't boot anything.
This post has been edited by garus: May 23 2010, 02:54 PM
Post by: dustin6908 on May 23, 2010, 07:58:00 AM
QUOTE(pulz @ May 23 2010, 01:57 PM)
After making my freeboot with the dash1.0 patches it just defaults to NXE.
Anybody knows why, i have chosen option 1. Hd always connected.
I changed the freeboot patches, and uploaded a launch.ini file to the root of the hd.
same situation here slashed launch.xex to flash to still not wirking lounch.ini is on hdd1 root
Post by: kettenschutz on May 23, 2010, 08:36:00 AM
gotta problem here and hopefully someone of u could help me out
the readme says
QUOTE
As prerequisites you will need an image of your
console updated to kernel 2.0.7371 [recommended] and an archive "9199.zip" available
at the usual places.
console updated to kernel 2.0.7371 [recommended] and an archive "9199.zip" available
at the usual places.
so, where to get this 7371 image ?
should a current updated kernel backup of my 8955 kernel works, or do i need the 7371 image for creating the bin ? :-/
Post by: opticd on May 23, 2010, 09:19:00 AM
QUOTE(kettenschutz @ May 23 2010, 03:36 PM)
hi there
gotta problem here and hopefully someone of u could help me out
the readme says
so, where to get this 7371 image ?
should a current updated kernel backup of my 8955 kernel works, or do i need the 7371 image for creating the bin ? :-/
This isn't the case. You do need 9199 and Freeboot to have this work though (not sure why you are on 8955). Anyways, build a kernel with anything you have previously used in a freeboot image to get it to 0.32 and then send it on over and it'll work fine.
Post by: kettenschutz on May 23, 2010, 10:00:00 AM
QUOTE(opticd @ May 23 2010, 05:19 PM)
This isn't the case. You do need 9199 and Freeboot to have this work though (not sure why you are on 8955). Anyways, build a kernel with anything you have previously used in a freeboot image to get it to 0.32 and then send it on over and it'll work fine.
hey, thanks for the answer
i just checked the ongoing tuts and i saw that i need a backupimage BEFORE the JTAG
(thats the 73** kernel image i mean before)
i didnt have that image from my nand, cause i not did the JTAG for myself, i bought the box "as is"
so shame on me, no update for me :-(
Post by: Sonic-NKT on May 23, 2010, 10:02:00 AM
flashed the launch.xex into the nand with included program
copied a launch.ini in the root of my HDD
everything is working fine, the console boots straight to freestyle dash and if i press Y on the miniguide it goes straight back to it. Also Xbox1 games work and going back to Freestyle from them.
Great work guys! Cant wait would patches come out next (IMG:style_emoticons/default/wink.gif)
PS: tried everything on a jasper 512
Post by: antisniperspy on May 23, 2010, 10:09:00 AM
QUOTE(Sonic-NKT @ May 23 2010, 12:02 PM)
Just created a new freeboot nand images with the new patches, flashed it with flash360
flashed the launch.xex into the nand with included program
copied a launch.ini in the root of my HDD
everything is working fine, the console boots straight to freestyle dash and if i press Y on the miniguide it goes straight back to it. Also Xbox1 games work and going back to Freestyle from them.
Great work guys! Cant wait would patches come out next
PS: tried everything on a jasper 512
How did you build your nand? ie Command Line or Freeboot Toolbox 2.3
Thanks
Post by: xxpittbullxx on May 23, 2010, 10:16:00 AM
QUOTE(antisniperspy @ May 23 2010, 11:09 AM)
How did you build your nand? ie Command Line or Freeboot Toolbox 2.3
Thanks
I used ibuld Command line for my Jasper 256 image.
All working well Here
Post by: xxdylanxx on May 23, 2010, 10:32:00 AM
Post by: Sonic-NKT on May 23, 2010, 10:33:00 AM
Post by: DarkProphecy on May 23, 2010, 11:08:00 AM
Post by: Arbiter34 on May 23, 2010, 01:04:00 PM
Post by: ddxcb on May 23, 2010, 01:18:00 PM
Post by: SBEEZY on May 23, 2010, 01:27:00 PM
QUOTE(ddxcb @ May 23 2010, 02:18 PM)
LOL to all who had to rebuild an image, i ididnt xD
well spill the beans mate
Post by: antisniperspy on May 23, 2010, 01:44:00 PM
QUOTE(ddxcb @ May 23 2010, 03:18 PM)
LOL to all who had to rebuild an image, i ididnt xD
Yes please it would be nice of you to let us know
Post by: Sonic-NKT on May 23, 2010, 01:46:00 PM
QUOTE(ddxcb @ May 23 2010, 09:18 PM)
LOL to all who had to rebuild an image, i ididnt xD
you are a really funny guy and a huge help for the community ...
PS: after playing arround with it some more it seems to work for me quite well, i didnt have any errors yet, goes back to freestyle all the time without any problems (ini on hdd). going back to the normal dash works also just fine by pressing RB while going back
Post by: rocky5 on May 23, 2010, 02:18:00 PM
i flashed with flash360 and i got the error ... Zeropaired kv so any one else have this problem.
the xbox worked all morning so haven't a bloody clue lol
Post by: soulwarrior on May 23, 2010, 03:02:00 PM
QUOTE(dufc1983 @ May 23 2010, 04:41 PM)
when using flash installer i get error opening GAME:\launch.ini for read
did not open GAME:\launch.ini for read, error 2
everything is were it should be any ideas?
It's because you didn't have the ini file in the flash installer folder when you ran the program. You don't need to have there as long as you have your ini file in the root of your hdd/usb/memory card
Post by: dufc1983 on May 23, 2010, 03:04:00 PM
QUOTE(soulwarrior @ May 23 2010, 10:02 PM)
It's because you didn't have the ini file in the flash installer folder when you ran the program. You don't need to have there as long as you have your ini file in the root of your hdd/usb/memory card
yeah only just noticed luckily i did put it on root of hhd and its working perfectly none of this pressing rb or rt bla bla it just works pressing yellow button
Post by: dryan433 on May 23, 2010, 04:33:00 PM
QUOTE(ZprivateZ @ May 23 2010, 04:48 AM)
Can someone please explain this to me
- with the included patch set, launch.xex acts as a helper to detect when
xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
to function together.
Does it mean memory unlock is always there except when you launch an xbox1 title then it knows to switch to xbox1 emulator?
yes this is what the read me say so you can have it patched for system mem hacks and still be able to run xbox1 emu as it suppose to be able to detect when you run xbox1 mode if I'm correct please correct me
Post by: cory1492 on May 24, 2010, 12:06:00 AM
QUOTE(DarkProphecy @ May 23 2010, 11:08 AM)
I guess it works on xb1 games, it just doesn't work sometimes. I never have a disc in the ODD, so I can't say why. Can it have 'activity' if there's no disc in the drive?
There are some random/fluke things that can mess it up, but it's pretty rare (mostly ODD disk related, but in some cases not) and seems it's not possible to reproduce on a machine that doesn't have the issue to begin with. Most people aren't having issues, the ones that can be reproduced will be solved, and either way the code is there for anyone who has run into NXE when they shouldn't to try and tinker a bit.
pulz:
it was a omission in the nfo on #1, you still have to install launch.xex to flash before it will work.
garus:
Ah, you are right, it does seem to work from USB. You can try pointing it at the freestyle-usb USB CON instead, also be sure you have the path correct (if you have multiple usb devices you will probably have to try each of the usb#'s) all I have for usb drives here is a 2G data traveler and everything seems to work great from there. I've even used it to launch xexmenu con in USB MU created by the new MU thing for 9199 on this same card.
launch.ini (on usb device so it overrides my flash one, since I disconnected the HDD) - as I have only one usb drive hooked to the machine, I know I can safely use Lusb0 and have it work.
CODE
[QuickLaunchButtons]
BUT_X = LHdd:\Freestyle\FreestyleDash.xex
BUT_Y = LMuu0:\Content\0000000000000000\00000001\00080000\000000010F586558
LBump = LHdd:\Freestyle\FreestyleDash.xex
Default = LUsb0:\Freestyle\FreestyleDash.xex
[plugins]
plugin1 =
plugin2 =
plugin3 =
plugin4 =
BUT_X = LHdd:\Freestyle\FreestyleDash.xex
BUT_Y = LMuu0:\Content\0000000000000000\00000001\00080000\000000010F586558
LBump = LHdd:\Freestyle\FreestyleDash.xex
Default = LUsb0:\Freestyle\FreestyleDash.xex
[plugins]
plugin1 =
plugin2 =
plugin3 =
plugin4 =
output in cygnos toolbox:
CODE
Booting....
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0PartitionFile\Storage\ to LMuu0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: launch LUsb0:\Freestyle\FreestyleDash.xex
[t:XEX2]
[dv:LUsb0:]
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0PartitionFile\Storage\ to LMuu0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: launch LUsb0:\Freestyle\FreestyleDash.xex
[t:XEX2]
[dv:LUsb0:]
(note that symbolic links can be successfully created for devices that don't exist but have kernel driver objects registered.)
Hope that helps some?
Post by: Lisko on May 24, 2010, 03:07:00 AM
Post by: dufc1983 on May 24, 2010, 03:24:00 AM
QUOTE(Lisko @ May 24 2010, 10:07 AM)
Me again. If I boot in xexmenu all works well. If I boot in FSD 1.20 the hooking doesn't work, it returns to NXE. But if I eject the tray while playing it reboots into FSD. Why using miniblades won't work?
you have to hold rt then press y as normal should work
Post by: kettenschutz on May 24, 2010, 03:52:00 AM
it seems like i finally got the flash right
freestyle is booting up fine, flashed launch.ini into nand
if i now power on my box and hold a,b,y or y button the box just reboots and starts in nxe after that
if i didnt press any button, fsd boots fine
if i press the guide in freestyle, then y and then "yes" after that holding a,b,x or y then happens nothing
some ideas ? :-/
Post by: Sonic-NKT on May 24, 2010, 05:12:00 AM
PS: you have to press RB and Y in the miniblade, and it will bring you back to NXE! Read the Readme correctly.
Post by: Lisko on May 24, 2010, 07:31:00 AM
QUOTE(Sonic-NKT @ May 24 2010, 01:12 PM)
Xexmenu is your Default in launch.ini? maybe try setting FSD the default and see what happens then
PS: you have to press RB and Y in the miniblade, and it will bring you back to NXE! Read the Readme correctly.
If Xexmenu is the default item all goes well. If FSD 1.20 pressing y in the miniblade will return to NXE. To return to FSD I have to open-close tray. I don't understand why xexmenu works and FSD not....
Post by: dustin6908 on May 24, 2010, 11:23:00 AM
launch.xex flashed to flash
my ini looks like this
Default = LHdd:\Freestyle\FreestyleDash.xex;
old dash lounch worked .01 and .02
cant get this one to work
i got my image the same way i built my org freeboot .032 one except i changed out the patches file.
It was build with wasy freebooot 2 and everything thing else but works
any ideas?
Post by: ZprivateZ on May 24, 2010, 12:12:00 PM
QUOTE(dustin6908 @ May 24 2010, 01:23 PM)
i never get nothing but nxe ive tried launch.ini on usb0 hdd1 and flash
launch.xex flashed to flash
my ini looks like this
Default = LHdd:\Freestyle\FreestyleDash.xex;
old dash lounch worked .01 and .02
cant get this one to work
i got my image the same way i built my org freeboot .032 one except i changed out the patches file.
It was build with wasy freebooot 2 and everything thing else but works
any ideas?
Try taking the ; out of your default line behind FreestyleDash.xex
Post by: Midnight Tboy on May 24, 2010, 12:16:00 PM
Yesterday, I just finally updated my Xell XBR3 xenon.....first to Xellous, and then (with an E72 problem - sorted afterwards) to Freeboot v0.32 using FreeBoot ToolBox Maker v2.3.
can I ask.....
I read this bit
"- with the included patch set, launch.xex acts as a helper to detect when
xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
to function together
"
I'm trying to work out what that means exactly?
Does it mean we no longer have to set in the Freeboot Toolbox Maker, between "Maintain Xbox 1 Emulator Functionality" and "Full Memory Access (RAM)"?
Also......Is there a way to find out which option I chose by dumping the nand again or any other means? I was meaning to choose the Full Memory Access, but after having to reload the app and try again cannot remember if I did set it the 2nd time round as it defaults to the xb1.
Post by: dustin6908 on May 24, 2010, 02:34:00 PM
QUOTE(ZprivateZ @ May 24 2010, 07:12 PM)
Try taking the ; out of your default line behind FreestyleDash.xex
still not working
just nxe over and over
no disc in drive at all
any more ideas?
i got a zephyr 4558 if that matters
Post by: p4r0l3 on May 24, 2010, 02:40:00 PM
Always goes to NXE so I tried installing xex/ini to flash, said it was a success. However, still the same behavior.
Any ideas? Falcon box here
Post by: ZprivateZ on May 24, 2010, 02:48:00 PM
QUOTE(dustin6908 @ May 24 2010, 04:34 PM)
still not working
just nxe over and over
no disc in drive at all
any more ideas?
i got a zephyr 4558 if that matters
I guess best thing to do would be recheck your steps,
1.Rebuilt freeBOOT with supplied patches from dash launch and reflashed console
2.Edit launch.ini to your liking and copy it over to the root of your hdd
3.Copy over flash_installer folder and run default.xex
4.Reboot console
If still not working after this then I have no answer for you and maybe someone else will have an idea.
Post by: dustin6908 on May 24, 2010, 02:53:00 PM
QUOTE(ZprivateZ @ May 24 2010, 09:48 PM)
I guess best thing to do would be recheck your steps,
1.Rebuilt freeBOOT with supplied patches from dash launch
2.Edit launch.ini to your liking and copy it over to the root of your hdd
3.Copy over flash_installer folder and run default.xex
4.Reboot xbox
If still not working after this then I have no answer for you and maybe someone else will have an idea.
those are the same exact steps i took before but i may redo it again.
i just dont like reflashing my nand more than i need to.
thanks for your help.
and if any more suggestions come i will try also.
i may wait a day or two till i redo completely so please give suggestions if you have them.
thanks in advanced
Dustin
Post by: p4r0l3 on May 24, 2010, 03:29:00 PM
QUOTE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
It seems to work for me if all you include is the default line.
EDIT: I now know what was the problem for me, and it may be the same for you.
If you are editing the ini file on unix, you will need to write the file in DOS format or use unix2dos to convert your ini. This is due to a difference in the way end of line characters are stored. Once this is done, adding parameters other than the Default line works well.
Post by: dustin6908 on May 24, 2010, 03:58:00 PM
QUOTE(p4r0l3 @ May 24 2010, 10:29 PM)
dustin6908, try editing launch.ini as follows.
It seems to work for me if all you include is the default line.
EDIT: I now know what was the problem for me, and it may be the same for you.
If you are editing the ini file on unix, you will need to write the file in DOS format or use unix2dos to convert your ini. This is due to a difference in the way end of line characters are stored. Once this is done, adding parameters other than the Default line works well.
omg dude ima try that i am editing it linux thankkk youu ima try thisss and report back
Post by: dustin6908 on May 24, 2010, 04:26:00 PM
dude your the fuckin man
thank you peace
Post by: miller420 on May 24, 2010, 08:31:00 PM
QUOTE(rocky5 @ May 23 2010, 04:18 PM)
Mine was all working fine till this afternoon then error 1033 (sync and eject button) have to send it off to get fixed as i don't have the stuff to flash the nand (outside of the 360 software solutions).
i flashed with flash360 and i got the error ... Zeropaired kv so any one else have this problem.
the xbox worked all morning so haven't a bloody clue lol
I just flashed my freeboot image built with ibuild to my falcon with Dash Launch patches. The console booted 3 times with Dash Launch working as normal, then the power went out for a second while i was transferring some games. Now when I boot the console I get secondary error 1033. Either tonight or tomorrow I'm going to solder on my lpt and flash it again to see what happens. With my Zephyr I used the hacked SMC extracted from XBR3, and its been working flawless. With my Falcon I just used the hacked SMC from the Cygnos pack from the usual places. Just wondering if that could be it, or if something went wrong with ibuild. I flashed with flash360 and i didn't get the zeropaired warning with my falcon, I did with the Zephyr and its working fine.
Post by: p4r0l3 on May 24, 2010, 08:51:00 PM
Post by: miller420 on May 24, 2010, 09:40:00 PM
Post by: opticd on May 25, 2010, 02:55:00 AM
Hardware used
-512MB Jasper
-Non Hacked 500GB Seagate HDD
*Note: the launch was installed to flash memory.
Post by: kettenschutz on May 25, 2010, 03:38:00 AM
i reflashed it completely again with the placed xenon_patchset at the bin folder
but if i holf A,B,X or Y at startup at the xbox logo the XBOX reboots itself and starts in NXE
i i wont press anything the box boots up straight to FSD. so this is fine
maybe the problem could comes from the original nand, cause i didnt have any1
i used another tutorial to flash my 360 without this backup
the freeboot stuff works fine, kernel is updated to 99', but dashlaunch wont work
i tried both ways, flashing the launch.ini and just copy it to HDD and USB
check the path's several times, but this damn thing just reboots if i hold any button
same problem is if i try to boot another dash from the lovely called "miniblade"
it just boots to NXE, whether if i hold RB or RT in combination with A,B,X or Y
maybe someone could have an idea for this :-/
are there a possibilty to check if dashlaunch is correctly installed?
cause it boots in both ways, with the OLD LAUNCH.XEX (from dashlaunch 0.2) and the new LAUNCH.XEX to FSD
its damn strange
Post by: dryan433 on May 25, 2010, 02:49:00 PM
QUOTE(opticd @ May 25 2010, 09:55 AM)
Yeah there's for sure a bug with this that has happened to a few previous members. Basically the full run down. I flashed it and it worked great for a lil while. I unplugged my xbox and WHILE IT WAS NOT HOOKED TO ANY POWER SOURCE, I took the harddriive off and put it back on. Hooked it up to a wall and powered it on and it E79d on its own. It's for sure not my wiring because I have used everything perfect and it worked just fine with Freeboot .32 and Dash Launch previously. Something needs to get fixed.
Hardware used
-512MB Jasper
-Non Hacked 500GB Seagate HDD
*Note: the launch was installed to flash memory.
so i guess this patch don't work as well as it says then as my nand had corrupted on me after power cut xbox was off at the time and when i came back to it to play on i got nothing wont power on like the smc has fucked up but yet it was working just fine before this happened with this patch as after i re flashed my box i was playing on it for a few hours just fine then out the blue this happened to me so unless this is fixed i would advice to stay away
Post by: ddxcb on May 25, 2010, 03:39:00 PM
QUOTE(dryan433 @ May 25 2010, 01:49 PM)
so i guess this patch don't work as well as it says then as my nand had corrupted on me after power cut xbox was off at the time and when i came back to it to play on i got nothing wont power on like the smc has fucked up but yet it was working just fine before this happened with this patch as after i re flashed my box i was playing on it for a few hours just fine then out the blue this happened to me so unless this is fixed i would advice to stay away
Its the patches you guys did.
Post by: dryan433 on May 25, 2010, 03:45:00 PM
QUOTE(ddxcb @ May 25 2010, 10:39 PM)
Its the patches you guys did.
what you mean patches we did i said that in my post lol or you meaning that we all patched with wrong patch ??
i used falcon patch for my falcon its this patch that's broken as i think my smc is broken from this patch on mine as chip/flash controller is not detected in nandpro
Post by: ddxcb on May 25, 2010, 04:01:00 PM
QUOTE(dryan433 @ May 25 2010, 02:45 PM)
what you mean patches we did i said that in my post lol or you meaning that we all patched with wrong patch ??
i used falcon patch for my falcon its this patch that's broken as i think my smc is broken from this patch on mine as chip/flash controller is not detected in nandpro
did u use ibuild to apply the patches ?
Post by: dryan433 on May 25, 2010, 04:06:00 PM
QUOTE(ddxcb @ May 25 2010, 11:01 PM)
did u use ibuild to apply the patches ?
no i didn't this time
for the first time i used easy freeboot before hand i used ibuild when i first flashed my box with freeboot but this time i used the easy freeboot app as this worked for my friends box fine when he flashed freeboot the first time as ibuild would not build them right for his box yet easy freeboot works a charm for him
when i try to flash it again will be trying one more time but with ibuild as i did first time round
Post by: ddxcb on May 25, 2010, 04:11:00 PM
QUOTE(dryan433 @ May 25 2010, 03:06 PM)
no i didn't this time
for the first time i used easy freeboot before hand i used ibuild when i first flashed my box with freeboot but this time i used the easy freeboot app as this worked for my friends box fine when he flashed freeboot the first time as ibuild would not build them right for his box yet easy freeboot works a charm for him
when i try to flash it again will be trying one more time but with ibuild as i did first time round
Any of thoes apps uses ibuild, and did u put the patch in there folder ?
Post by: krizalid on May 25, 2010, 04:20:00 PM
Dashlaunch patches replacement for ibuild works and works well, no issues there.
We are talking about it missing a patch on the xenon.patches that allowed unsigned sata hdd to be mounted properly.
Does work on my Falcon, but not my xenon.
Let's read with more attention please.... I feel like big bird from sesame street saying this
Post by: dryan433 on May 25, 2010, 04:53:00 PM
QUOTE(ddxcb @ May 25 2010, 11:11 PM)
Any of thoes apps uses ibuild, and did u put the patch in there folder ?
yes i did i written over the existing patches i had and rebuilt my image with easy freeboot was working but then died the day after
QUOTE(krizalid @ May 25 2010, 11:20 PM)
Let's not get all this confused.
Dashlaunch patches replacement for ibuild works and works well, no issues there.
We are talking about it missing a patch on the xenon.patches that allowed unsigned sata hdd to be mounted properly.
Does work on my Falcon, but not my xenon.
Let's read with more attention please.... I feel like big bird from sesame street saying this
not getting confused mate if this has done this to hdd on one type of console its done something different on mine and killed my xbox after it was working sweet after this patch then died after a full night of it working fine
so no im not talking about the hdd issue but a different issue related to the exact same patch on my falcon 3.0 xbox 360
Post by: antisniperspy on May 25, 2010, 04:56:00 PM
QUOTE(ddxcb @ May 25 2010, 05:39 PM)
Its the patches you guys did.
Ever going to tell us how you patched your xbox without building a new nand??
Post by: daze81 on May 25, 2010, 05:23:00 PM
CODE
Copy the patch suitable for your console to the bin\ folder of your freeboot image folder, then compile as per the instructions included in the readme for freeboot. After doing so, edit the launch.ini so that it fits your needs by following the examples it sets. Once having done that, launch either Freestyle Dash or XeXMenu and ftp the files to the root of HDD1 turn off your console and turn back on, and the settings you have chosen in the launch.ini will have taken affect.
so i made a launch.ini:
CODE
[QuickLaunchButtons]
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
and copied the launch.ini and launch.xex out of the folder "flash_installer" into the root of the internal HDD.
it defaults every single time into NXE and ignores all defined buttons as well.
so if anyone can enlight me ... i've got no more ideas want could be wrong.
thanks in advance.
Post by: dryan433 on May 25, 2010, 05:35:00 PM
QUOTE(daze81 @ May 26 2010, 12:23 AM)
hi,
so usually i read more instead of posting questions already answered.
i've build my freeboot nand twice now with these new patch and i can't get it to work at all.
here is my config:
- jasper512
- extracted crl.bin, extended.bin, kv.bin, odd.bin, secdata.bin and smc_config.bin from original nand
- extracted smc.bin from xbr3 (because of the known problems with the original smc & freeboot)
- dash launch 1.0 patches copied to bin directory
- build updflash.bin by commandline
- flashed with flash360 & xbrflash
i have chosen the option #1 from the readme:
CODE
Copy the patch suitable for your console to the bin\ folder of your freeboot image folder, then compile as per the instructions included in the readme for freeboot. After doing so, edit the launch.ini so that it fits your needs by following the examples it sets. Once having done that, launch either Freestyle Dash or XeXMenu and ftp the files to the root of HDD1 turn off your console and turn back on, and the settings you have chosen in the launch.ini will have taken affect.
so i made a launch.ini:
CODE
[QuickLaunchButtons]
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
and copied the launch.ini and launch.xex out of the folder "flash_installer" into the root of the internal HDD.
it defaults every single time into NXE and ignores all defined buttons as well.
so if anyone can enlight me ... i've got no more ideas want could be wrong.
thanks in advance.
i had this issue before my xbox bricked it self after this patch at first i did not change the last version of dash launch and the ini with new one and if booted into my fsd as before when i put the new version there it wouldn't boot only nxe but next day when i came back to xbox it wouldn't power on and nandpro will not detect so will have to short pins to re flash it now lol fun
wile i was at work there was a power failure too but was back on when i got home
by the looks of it thou you have it correct how you have done it
Post by: soulwarrior on May 25, 2010, 06:53:00 PM
****
at time of this writing, this is ONLY compatible with freeBOOT 0.03x
releases built with the included patch set which expects launch.xex
to be installed to system flash.
****
ie you must use the flash installer in addition to creating your freeboot image with the new patches. You don't need to install the ini to flash though.
That being said, I also have not gotten the quicklaunch buttons to work. I have freestyle dash as the default and it returns to fsd just fine. I have xexmenu set for A but for some reason it only goes back to nxe. Pretty sure I don't have typos either.
Post by: ZprivateZ on May 25, 2010, 07:37:00 PM
QUOTE(dryan433 @ May 25 2010, 04:49 PM)
so i guess this patch don't work as well as it says then as my nand had corrupted on me after power cut xbox was off at the time and when i came back to it to play on i got nothing wont power on like the smc has fucked up but yet it was working just fine before this happened with this patch as after i re flashed my box i was playing on it for a few hours just fine then out the blue this happened to me so unless this is fixed i would advice to stay away
What smc did you use? Because I could be wrong but if I remember correctly when freeboot first released for single nand people were having this issue also due to either using the wrong smc.bin or using the smc_enc.bin instead of using the smc_dec.bin. I myself have a jasper 512mb and have not had problem one I extracted my smc from the xbr image for my board type. I have unplugged my box for 30 minutes and reconnected and powered on after seeing your post and still have no issues. So it just makes me curious as to what smc.bin you used.
Post by: daze81 on May 26, 2010, 12:20:00 AM
QUOTE(dryan433 @ May 26 2010, 01:35 AM)
i had this issue before my xbox bricked it self after this patch at first i did not change the last version of dash launch and the ini with new one and if booted into my fsd as before when i put the new version there it wouldn't boot only nxe but next day when i came back to xbox it wouldn't power on and nandpro will not detect so will have to short pins to re flash it now lol fun
you have to use the SMC out of XBR because the SMC out of your original nand backup does not work. had the same issue some time ago.
QUOTE(soulwarrior @ May 26 2010, 02:53 AM)
It appears people seem to be skipping over the part of the readme (the very beginning) that says:
****
at time of this writing, this is ONLY compatible with freeBOOT 0.03x
releases built with the included patch set which expects launch.xex
to be installed to system flash.
****
thanks. you're right i did not see that. i'm courious that they/he did not point it out in the option list.
Post by: Lisko on May 26, 2010, 08:20:00 AM
Post by: dustin6908 on May 26, 2010, 08:20:00 AM
Post by: BrooksyX on May 26, 2010, 12:28:00 PM
Post by: cory1492 on May 27, 2010, 03:31:00 AM
QUOTE(BrooksyX @ May 26 2010, 12:28 PM)
love what this patch promises but it just seems like it is causing way to many issues. I think im gonna wait it out until they iron out some of the bugs and they come out with it already part of freeboot. Shouldnt be to much longer now.
Out of about a dozen testers with approx 6 weeks test time, this build has the only issue found (aside from user error) mentioned in the readme - some consoles just behave slightly differently than others and wind up in NXE without ODD envolved, though turning the controller on or closing the tray at exactly the wrong time can cause problems too. The rebooting box mentioned once above was a failsafe, if subversion happens too early without the reboot patch the cosole will freeze (with patch it reboots instead so one doesn't have to get up and such), if it happens to late (more common, especially with disk in ODD) then NXE will appear instead of default setting.
dryan433: the only question I can ask, is have you repeated the outage too? Usually a brown out or power outage is accompanied by a surge (which is part of why it is recommended to unplug electronics from wall outlet in a storm, lightning arcing through wall aside.) If the box is turned off, the patches and launch aren't running and can have no effect while a surge can easily cause all sorts of random havok. I assume you pulled the power plug and any cable going to a powered video unit (applies to hdmi/vga) for a half minute or so before trying reflash.
krizalid: open the patch set you used with a hex editor and search for
CODE
0012837800000002386000014E800020
It should be at 0x6EC in the xenon patches - this is the hdd sig skip. If it's not working change the 00128378 to 0012837C and let me know if that makes a diff. It shouldn't but you never know, allowing LR to be moved to %R12 may be required.
Post by: ZerOneX on May 27, 2010, 10:01:00 AM
I did not undertand the differences between then.
I tried to connect with Xbins several times but I couldn´t... I don´t know why.
Many thanks.
Post by: juggahax0r on May 27, 2010, 10:15:00 AM
I think the NAND USB and HDD settings in freeBOOT toolbox has to with where you are going to be installing your launch.xex in the NAND USB or HDD.
Post by: antisniperspy on May 27, 2010, 10:21:00 AM
QUOTE(juggahax0r @ May 27 2010, 12:15 PM)
Yes i to was having xbins issues.
I think the NAND USB and HDD settings in freeBOOT toolbox has to with where you are going to be installing your launch.xex in the NAND USB or HDD.
I think cory1492 said above that the launch.xex has to be in flash so it seems to me like the USB and HDD settings are useless. Plus dont you have to install the launch.xex to flash after you have rebuilt your nand with the new patch? So those three options make no sense at all. Maybe someone can clear them up.
Post by: kettenschutz on May 27, 2010, 10:28:00 AM
QUOTE(antisniperspy @ May 27 2010, 06:21 PM)
I think cory1492 said above that the launch.xex has to be in flash so it seems to me like the USB and HDD settings are useless. Plus dont you have to install the launch.xex to flash after you have rebuilt your nand with the new patch? So those three options make no sense at all. Maybe someone can clear them up.
its correct that the launch.xex HAS TO BE FLASHED in the NAND directly. DONT put it on HDD or USB0, this could make trouble ..
this option is for the LAUNCH.INI file which define the linked dashboards to the buttons on ur controller
this file can be flashed directly to the NAND, or could be putted on USB and / or HDD
the boot order for this INI is :
USB
HDD
FLASH
there are peoples who reported they ony got full functionality if they flashed this ini (put the edited INI in the FLASH INSTALLER folder on your xbox to directly flash it via the /flash_installer/default.xex)
but normally it should be enough to put it on the USB root
Post by: antisniperspy on May 27, 2010, 10:46:00 AM
QUOTE(kettenschutz @ May 27 2010, 12:28 PM)
its correct that the launch.xex HAS TO BE FLASHED in the NAND directly. DONT put it on HDD or USB0, this could make trouble ..
this option is for the LAUNCH.INI file which define the linked dashboards to the buttons on ur controller
this file can be flashed directly to the NAND, or could be putted on USB and / or HDD
the boot order for this INI is :
USB
HDD
FLASH
there are peoples who reported they ony got full functionality if they flashed this ini (put the edited INI in the FLASH INSTALLER folder on your xbox to directly flash it via the /flash_installer/default.xex)
but normally it should be enough to put it on the USB root
I still dont see a reason for the three options in freeboot toolbox 2.4 as all you have to do is include the new patch. You still have to run the installer on the xbox 360 and choose where you want your ini files (flash, hdd1 or/and usb0).
Post by: juggahax0r on May 27, 2010, 10:59:00 AM
I understand it better now after your explanation cory1492 so I appreciate it. Nothing against team Xedev but for me at least the readme was a little vague or rather just worded in a confusing manner for me.
I won't be able to test it anymore until next week , I busted a MOSFET from under my GPU trying to put X-clamps on and it's 0001 now and the pad has been lifted so i can't reattach it , it's a bitch but i get my Jtags cheap so i will be rockin again soon.
@antisniperspy
I think the reason for the option in freeBOOT toolbox maker is to select which version of the patch to use , you will still have to run the installer app , but you also still need to select this option. freeBOOT toolbox maker also is not the only way to build the image the dashlaunch.rar has subfolders for the different patches if i remember correctly.
Post by: antisniperspy on May 27, 2010, 11:11:00 AM
QUOTE(juggahax0r @ May 27 2010, 12:59 PM)
@antisniperspy
I think the reason for the option in freeBOOT toolbox maker is to select which version of the patch to use , you will still have to run the installer app , but you also still need to select this option. freeBOOT toolbox maker also is not the only way to build the image the dashlaunch.rar has subfolders for the different patches if i remember correctly.
Yeah the patches folder has these but these only change for the type of nand you have
- patches_falcon.bin
- patches_jasper.bin
- patches_xenon.bin
- patches_zephyr.bin
the patches have nothing to do with where you want to store the ini files
Post by: antisniperspy on May 27, 2010, 12:15:00 PM
QUOTE(ZerOneX @ May 27 2010, 02:13 PM)
For me did not work aswell.
1) I used "FreeBoot Tool 0.032 Maker 2.4"
2) In the Dash Launch 1.0 patches I used NAND option
3) Using flash360 I wrote my NAND again
4) I built this .INI
5) Using my pendrive I made a copy of this folder "flash_installer" with default.xex, launch.xex and launch.ini inside.
6) Through XeXmenu and running default.xex I flashed launch.xex and launch.ini to my NAND, but nothing happened.
Someone know waht I´m doing wrong?
Thanks folks.
Everything you did sounds correct.
Post by: dryan433 on May 27, 2010, 12:21:00 PM
QUOTE(cory1492 @ May 27 2010, 10:31 AM)
The ini file needs to be ASCII/UTF-8 format, paths are case sensitive. And once again, it was an omission in #1 - with this patch set launch.xex is required to be on FLASH.
Some additional info on SMC, if you use the cygnos SMC without a cygnos it's not going to work... cygnos does it's own JTAG injection instead of relying on SMC to do it. There are two hacked SMC currently, one for xenon (based on xenon smc), one for everything else (based on jasper big block SMC) which can be found in the xbr or xell images - do not use the xenon one on a non-xenon console.
Out of about a dozen testers with approx 6 weeks test time, this build has the only issue found (aside from user error) mentioned in the readme - some consoles just behave slightly differently than others and wind up in NXE without ODD envolved, though turning the controller on or closing the tray at exactly the wrong time can cause problems too. The rebooting box mentioned once above was a failsafe, if subversion happens too early without the reboot patch the cosole will freeze (with patch it reboots instead so one doesn't have to get up and such), if it happens to late (more common, especially with disk in ODD) then NXE will appear instead of default setting.
dryan433: the only question I can ask, is have you repeated the outage too? Usually a brown out or power outage is accompanied by a surge (which is part of why it is recommended to unplug electronics from wall outlet in a storm, lightning arcing through wall aside.) If the box is turned off, the patches and launch aren't running and can have no effect while a surge can easily cause all sorts of random havok. I assume you pulled the power plug and any cable going to a powered video unit (applies to hdmi/vga) for a half minute or so before trying reflash.
krizalid: open the patch set you used with a hex editor and search for
CODE
0012837800000002386000014E800020
It should be at 0x6EC in the xenon patches - this is the hdd sig skip. If it's not working change the 00128378 to 0012837C and let me know if that makes a diff. It shouldn't but you never know, allowing LR to be moved to %R12 may be required.
yes i tried all this i had to re-flash the box it was totally messed up power is fine it was just that the nand had corrupt but i had built it with easy freeboot first time i rebuilt with ibuild how i know and it seams fine now as mad as it sound both programs are not working exactly the same as my friend when he did his xbox he had to use easy freeboot for his as a manual build from ibuild just would not work full stop but one from easy freeboot did but with me the opposite by the looks of it so its a strange one
oh i had to short the pins on the nand just to get it to pick it up again so it seams to me that the smc had corrupted its self some how with all the nand version of freeboot iv used the same smc from my compiled xbr image
atm I'm struggling to get it to load the ini its in UTF-8 format as notepad do not save in ASCII
this is whats in my ini so is this correct as i did forget about it being case sensitive but corrected it and still no joy yet the launch.xex is on nand and as far as i know its working because with mini blades if i hold left trig and y it reboot to nxe and if i hold down x at same time if fully reboots my xbox because it cant load something so I'm totally stummbed on this now
Post by: antisniperspy on May 27, 2010, 12:28:00 PM
QUOTE(ZerOneX @ May 27 2010, 02:20 PM)
mysteries of the beyond eheh, I´m trying to find the solution
ow, thers is one thing, my donor nand is 6717 and not 7371, this could be the source of my problem?
Problem could be that its a donor nand and that its at 6717. Not sure though
Post by: ZerOneX on May 27, 2010, 12:36:00 PM
QUOTE
[QuickLaunchButtons]
BUT_X = LHdd:\Content\0000000000000000\00000001\00080000\000000010F586558
BUT_Y = LUsb1:\Freestyle\FreestyleDash.xex
Default = LUsb1:\Freestyle\FreestyleDash.xex
BUT_X = LHdd:\Content\0000000000000000\00000001\00080000\000000010F586558
BUT_Y = LUsb1:\Freestyle\FreestyleDash.xex
Default = LUsb1:\Freestyle\FreestyleDash.xex
PS. YOU HAVE TO SAVE THE .INI FILE IN UTF-8 FORMAT, any other encoding will not work.
5) Using my pendrive I made a copy of this folder "flash_installer" with default.xex, launch.xex and launch.ini inside.
6) Through XeXmenu and running default.xex I flashed launch.xex and launch.ini to my NAND,
7) Everything is working fine.
Thanks folks.
Post by: dryan433 on May 27, 2010, 12:51:00 PM
Post by: sudeki300 on May 27, 2010, 02:44:00 PM
Post by: dryan433 on May 27, 2010, 03:18:00 PM
QUOTE(sudeki300 @ May 27 2010, 09:44 PM)
i have tried to see this in the thread but could not find it. i have freestyle dash as my default, but if i want to go into nxe dash how would i write that on the ini file. would it be "default.xex" or "NXE". thanks............................sudeki300
when returning to dash with mini blade as soon as you have pressed y and yes press RB immediately after and hold this will take you back to the nxe dash the same wile booting xbox hold same button wile its booting and will go to nxe dash simple
well after i managed to get it to work lolif you want it permanently back to dash you need to remove the ini file i have it on my usb drive so if i want it to be nxe dash only i just unplug my usb hdd to make it simpler
Post by: kettenschutz on May 27, 2010, 10:27:00 PM
QUOTE(dryan433 @ May 27 2010, 11:18 PM)
...you have pressed y and yes press RB immediately after ...
hmmm, maybe this is my problem.
booting customized dashes at xbox startup works fine (beneath every button works including flash360 via LB), but the miniblade-jump never works.
maybe i pushed the buttons to late
but why there boots no FSD via Y and YES at the miniblade? only NXE :-(
will try the faster button smashing for this
Post by: kettenschutz on May 28, 2010, 10:18:00 AM
QUOTE(maliceshaun @ May 28 2010, 04:37 PM)
My button shortcuts to switch dashes does not work. I have original nand dump, created new freeboot 0.32 with dashlaunch patches. It boots straight to FSD and when I exit to dashboard goes to FSD. I have my launch.xex and launch.ini in my NAND, launch.ini in the root of my HDD. When I bring up the mini blade and hit RB + X nothing happens. What's wrong?
This is the launch.ini and it is in UTF-8.
CODE
[QuickLaunchButtons]
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
BUT_A = LHdd:\XeXMenu\default.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back = LHdd:\Flash360\Flash360.xex
BUT_A = LHdd:\XeXMenu\default.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex
nah, u have to HOLD X,B,Y or A Button immediately after u press "YES" in the miniblade
RB is only to boot in NXE
next is, u dont have to use the launch.ini on FLASH and HDD, one is enough
the third time i show the boot order of launch.ini :
USB
HDD
Flash
if u got the ini on HDD, the one in the FLASH wont be used
Post by: Inuyasha152 on May 29, 2010, 12:00:00 AM
Thanks in advance!
P.S. I get an error that the kv.bin cannot be extracted as the CPU key is invalid with freeboot toolbox, but have confirmed multiple times that the CPU key is correct and its simply a programming error on the creators part. Also, the issue with the MAC address being changed is another reason I wish to take an alternate route (perferably the tutorial mentioned above as I do not have a full backup of my original NAND.)
Post by: Inuyasha152 on May 29, 2010, 11:32:00 AM
QUOTE(dryan433 @ May 29 2010, 03:46 AM)
dont know what the toolbox do as i used ibuild but the launch xex looks for ini on usb if non found it will then look on hdd if non found then it will default to flash for ini so you only need one ini i have mine on usb my self
and you need the smc config from orig nand so your mac and all calibration data for that box as this has mac calibration data for temp reading and showing the display of the correct temp the region of the xbox is stored in there too so this in essence needs to come from the original image
hope this helps
danny
Hey, thanks for the reply. I guess my main question is when building your image with ibuild did you need to do anything to the patches or did you simply replace the ones in the /bin folder and build the image? In regards to the smc, I can extract that from my XBR image and it should be fine, as per the tutorial I mentioned.
If anyone could confirm that this tutorial (Link) would work with dashlaunch by simply replacing the patches with dashlaunches in the /bin direction, I would greatly appreciate it. If not, what would be missing (or need to be done to accomplish this?)
Thanks!
Spec's/info
Jasper 512mb XBR3.
Post by: cirkator on May 30, 2010, 06:49:00 AM
worked like a charm
jasper 512 with orig.bin
what i have noticed:
when updating from XBR3 to freeboot i got a blackscreen...
reflashed XBR through Xellous...
removed "launch.ini" and "launch.xex" from the old Dashlaunch version (stored in the root of hdd1)
after that flashing freeboot worked instantly
hope it helps someone
Post by: kettenschutz on May 30, 2010, 07:12:00 AM
QUOTE(cirkator @ May 30 2010, 02:49 PM)
i did it like ZerOneX did a few posts above me
worked like a charm
jasper 512 with orig.bin
what i have noticed:
when updating from XBR3 to freeboot i got a blackscreen...
reflashed XBR through Xellous...
removed "launch.ini" and "launch.xex" from the old Dashlaunch version (stored in the root of hdd1)
after that flashing freeboot worked instantly
hope it helps someone
hmm, maybe there are a problem with old launch.xexand ini's stored on hdd at flashing
will delete them all and reflash my image, hopefully it works
there are others with the same issue on xenon, so that the miniblade.jumps allways goes to NXE, but the bootup works like a dream ?
Nope : flashed in the above mentioned way
booting up to flash360 works fine, but the quickjump via the miniblade wont work
hmm okay there were 2 moments the miniblade launch to FSD and to flash360 works fine
im on to try to find out if this could be an application issue ?!?
Post by: kettenschutz on May 30, 2010, 11:01:00 PM
QUOTE(dryan433 @ May 30 2010, 11:36 PM)
nope there is no issue with old launch.xex as i had left it on my hdd drive when i flashed the new patch on my falcon and my fsd dash was still booting on boot up just that you don't get the extra stuff with it lol if you flash your xbox just put the ini on a usb drive and launch.xex in flash then if something don't work you pull your usb drive and your back to nxe xbox boot to nxe if there's no ini found or path is not set correct they are case sensitive and has to be set like this
[QuickLaunchButtons]
Default = LUsb0:\Applications\FreeStyle\FreestyleDash.xex
BUT_X = LUsb0:\Applications\XeXMenu_v1.1\default.xex
BUT_B = LUsb0:\Applications\xm360v1.5\XM360.xex
...
hmm thanks for the very, very long answer. i really appreciate your upcoming steps to help
but like i said, i reflashed it without any old dashlaunch crap on hold but with the same issue
the strange is that a few games ALLWAYS work, f.e. Alan Wake works with reboot to FSD via the miniblade every time
maybe it IS a problem with xenon and/or the DONOR NAND :-(
Post by: antisniperspy on May 31, 2010, 12:45:00 AM
QUOTE(kettenschutz @ May 31 2010, 01:01 AM)
hmm thanks for the very, very long answer. i really appreciate your upcoming steps to help
but like i said, i reflashed it without any old dashlaunch crap on hold but with the same issue
the strange is that a few games ALLWAYS work, f.e. Alan Wake works with reboot to FSD via the miniblade every time
maybe it IS a problem with xenon and/or the DONOR NAND :-(
I would say user error
j/k But in all seriouness it is probally the donor nand that is giving you your problems.
Post by: kettenschutz on May 31, 2010, 01:37:00 AM
QUOTE(antisniperspy @ May 31 2010, 08:45 AM)
I would say user error
j/k But in all seriouness it is probally the donor nand that is giving you your problems.
yes thats the way i thought, too
because there were another user with the same issue like me, on xenon, on donor NAND ..
this cant be an accident ...
maybe someone are also on XENON with a donor NAND and dont have trouble !?
Could u place ur used donor nand in a place 2 download ?
so i could check if this real is a problem of the donor nand i used
cant find more NANDS at google
Post by: kettenschutz on May 31, 2010, 09:51:00 AM
QUOTE(omegastar @ May 31 2010, 05:26 PM)
In freeboot Toolbox 0.032 Maker 2.4 the Dash Launch 1.0 options are for where you must put the launch.xex. You can have the launch.ini anywhere root it will search for it. This also eliminates the need for running flash_installer and injecting into nand if you choose usb or hdd in the toolbox.
One issue I'm having is into launch.xex but when I go miniguide then Y to exit to dashboard it goes NXE no matter what button I hold or dont hold. I have it loading launch.xex from USB.
What ?
In dashlaunch 1.0 the launch.xex has to be flashed in the NAND, not putted on HDD or USB o.O
Post by: soulwarrior on May 31, 2010, 11:46:00 AM
QUOTE(omegastar @ May 31 2010, 01:28 PM)
But I still have the issue using guide button and returning to dash always goes NXE.
Put it in the flash and it will work properly.
Post by: genio123 on May 31, 2010, 11:50:00 AM
I want to be able to boot freestyle dash (FreeStyle/FreestyleDash.exe - on internal HD) whenever i plug in my external HDD with Games...
So, Checked "USB" option in toolbox and flashed... Not Working
CODE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
(UTF-8 Format)
So i tryed(or tried?) to flash launch.xex on the nand with the flash_installer... nope again... it's not booting anything... Plz help
==================
GOT IT TO WORK!!
Small Walktrought for everyone:
My need was to boot up freestyle dash everytime a plug in the HDD with the games...
So, I made the updflash.bin with Freeboot toolbox 2.4 w/ the "USB" option, flashed the updflash.bin using flash360, then saved this launch.ini in the root of the USB HDD:
CODE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
(SAVED IN UTF-8 Format)
(Pay Attention to the path... It'S CaSe-sEnSiTIvE!)
then i placed the launch.xex in the root of the usb hdd.
IT WORKS!!
Post by: omegastar on May 31, 2010, 12:19:00 PM
QUOTE(genio123 @ May 31 2010, 01:50 PM)
Not Working For Me... Using Freeboot toolbox 2.4
I want to be able to boot freestyle dash (FreeStyle/FreestyleDash.exe - on internal HD) whenever i plug in my external HDD with Games...
So, Checked "USB" option in toolbox and flashed... Not Working
CODE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
(UTF-8 Format)
So i tryed(or tried?) to flash launch.xex on the nand with the flash_installer... nope again... it's not booting anything... Plz help
==================
GOT IT TO WORK!!
Small Walktrought for everyone:
My need was to boot up freestyle dash everytime a plug in the HDD with the games...
So, I made the updflash.bin with Freeboot toolbox 2.4 w/ the "USB" option, flashed the updflash.bin using flash360, then saved this launch.ini in the root of the USB HDD:
CODE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
(SAVED IN UTF-8 Format)
(Pay Attention to the path... It'S CaSe-sEnSiTIvE!)
then i placed the launch.xex in the root of the usb hdd.
IT WORKS!!
When you press guide then y then yes does it boot to FSD or NXE for you?
Post by: kettenschutz on May 31, 2010, 12:21:00 PM
but i cant really believe that its supported to put the launch.xex on the usb or hdd
thought this has to be in NAND; cause this is the only location the flashed image searched for ...
Post by: genio123 on May 31, 2010, 01:19:00 PM
QUOTE(omegastar @ May 31 2010, 07:19 PM)
When you press guide then y then yes does it boot to FSD or NXE for you?
It returns to FSD... It return to NXE only if i press RB
QUOTE(kettenschutz @ May 31 2010, 07:21 PM)
im glad to read that u could solve ur issue
but i cant really believe that its supported to put the launch.xex on the usb or hdd
thought this has to be in NAND; cause this is the only location the flashed image searched for ...
And it use the 1.0 patches cos if not how it could support the new ini file? :S
Post by: omegastar on May 31, 2010, 03:34:00 PM
Post by: dryan433 on May 31, 2010, 04:10:00 PM
QUOTE(omegastar @ May 31 2010, 10:34 PM)
Ok I'm an idiot it does work when I use the guide to go back to dash. The problem was I was only trying wile I was already in NXE or FSD but in games it works as it should.
you need to hold the left trigger if you already in nxe wile you pres yes the screen goes black and as soon as it do you press your shortcut or press nothing to go back to default
this works a charm for me not once has it hiccuped on my since i fix my xbox when i return to dash it always go to my fsd never once so far has it gone to nxe by mistake like mentioned in readme
Post by: kettenschutz on May 31, 2010, 10:07:00 PM
if i could make a question to yours were the dashlaunch works fine :
which mobo are u using ?
Did you got an original NAND backup ?
Do the back2fsdfromMinibladeStuff works from ALL Games ?
And, last but not least, are there others with XENON and donor NAND who have issues ?
Post by: dryan433 on June 01, 2010, 12:15:00 PM
QUOTE(kettenschutz @ Jun 1 2010, 05:07 AM)
okay im happy so your problems could be completely solved :-)
if i could make a question to yours were the dashlaunch works fine :
which mobo are u using ?
Did you got an original NAND backup ?
Do the ?
And, last but not least, are there others with XENON and donor NAND who have issues ?
I'm using a falcon
yes back 2 fsd from Miniblade Stuff works from ALL Games even from nxe dash
yes i have my original nand backup no donor nand used
the last don't apply to me as I'm not on a xenon xbox my xbox live box is the only xenon i have but not chipped in anyway all in it orig state
everything is working how it should with out any hiccup whats so ever its working perfect no random rrod soon I'm planning on redoing my jtag wiring for new type to stop my funky led issue and pad sync issues that arises from the jtag so see how that goes next lol
Post by: kettenschutz on June 02, 2010, 12:07:00 AM
alan wake, AVP f.e.
the other games everytime turns back 2 fsd
including Red Dead Redemption
hopefully there will be updates or maybe a new found donor nand for me to test with
thanks for your hints
Post by: X-hacker on June 02, 2010, 01:04:00 PM
QUOTE(kettenschutz @ May 31 2010, 11:10 PM)
okay im happy so your problems could be completely solved :-)
if i could make a question to yours were the dashlaunch works fine :
which mobo are u using ?
Did you got an original NAND backup ?
Do the ?
And, last but not least, are there others with XENON and donor NAND who have issues ?
I've flashed freeboot to a virgin Xenon with 1920 CB - got 3 good solid backups with infectus - flashed the freeboot image and it boots correctly.
Problem I'm having is getting it to boot into FSD on bootup. I've installed dash launch to NAND same as I did with my falcon, but only the falcon will boot FSD when I hold X...
Both images were built with FB image builder 2.4 - but only the falcon will boot FSD. I've got the launch.ini pointing to the FSD installed on the hard drive.
Does it matter if the hdd belongs to the console or not? (HDD is off the falcon which works)
Post by: dryan433 on June 02, 2010, 05:02:00 PM
QUOTE(kettenschutz @ Jun 2 2010, 07:07 AM)
this will only work at a handfull of games at me
alan wake, AVP f.e.
the other games everytime turns back 2 fsd
including Red Dead Redemption
hopefully there will be updates or maybe a new found donor nand for me to test with
thanks for your hints
to be honest with you mate i really don't think there will be a perfect donor nand image as all xbox 360 are unique to themselves and not in the sense of keys lol all have there unique smc config settings for one as this is one that can cause rrod 0020 it did with me when i forgot to put my orig smc config in image and i was getting random e79 (0020) errors until I replaced it with my own and they have gone now
there maybe a more stable donor but never will be perfect for you plus I'm not even using the updated dash image its an old image as most have updated there's to the 7*** dash as I'm on an old image 6717 to be precise and I'm not having a single issue so far every game iv played has gone back to my default fsd and never back to nxe
so Iver I'm lucky or its all to do with the image you start with your guess is as good as mine but i know I'm not going to even attempt to update my orig image
QUOTE(X-hacker @ Jun 2 2010, 08:04 PM)
I've flashed freeboot to a virgin Xenon with 1920 CB - got 3 good solid backups with infectus - flashed the freeboot image and it boots correctly.
Problem I'm having is getting it to boot into FSD on bootup. I've installed dash launch to NAND same as I did with my falcon, but only the falcon will boot FSD when I hold X...
Both images were built with FB image builder 2.4 - but only the falcon will boot FSD. I've got the launch.ini pointing to the FSD installed on the hard drive.
Does it matter if the hdd belongs to the console or not? (HDD is off the falcon which works)
try placing your ini on a usb drive the ini was being funny with me anywhere else i put it this may help but all are having issues like this i did from start now mines perfect now
no it don't matter what xbox the drive has come from
Post by: kettenschutz on June 02, 2010, 10:46:00 PM
i know donor nands arent the perfect basics, cause there comes from another consoles, but thats the only chance i have atm
there arent much other options to do
if this damn retailer could send me a nand backup .... blahblah ...
Post by: kettenschutz on June 03, 2010, 10:41:00 PM
QUOTE(genio123 @ Jun 3 2010, 06:06 PM)
With my config (posted on page 10) RDR works like a charm, returning to FSD when do the miniblade y yes thing
tried the same and 100 other combinations
there are games without any problems. and like i said the bootup to fsd from cold is fine.
the bootup to other dashes and tools is fine, too
only the miniblade stuff is strange
cant really get this
Post by: dupfold on June 05, 2010, 09:41:00 AM
Read though this tread as was keen to boot straight to fsd. I didn't do the jtag myself so wasn't keen on flashing NAND. I found a guide on another website (not sure if I can post link?) where by I simply copied Launch.ini & Launch.XeX to root of partition and sorted, fsd on boot.
Is there any downside to this or extra benefits via the flash route?
Post by: dupfold on June 05, 2010, 12:17:00 PM
Post by: kettenschutz on June 06, 2010, 03:32:00 AM
QUOTE(genio123 @ Jun 5 2010, 02:09 PM)
It could be the donor nand? Mine was from my original nand (only the XBREBOOTED one... cos the original gave me error with the toolbox -lol-)
i dunno if the donor nand is really the ticket, but it IS(!) the only thing that differs me from all others which dont have any issues
(P.S. glad to see that the wordcombo "back2fsdfromMinibladeStuff" is appreciated at some peops here
)
Post by: kettenschutz on June 08, 2010, 12:20:00 PM
i notived just now that the RT-HOLD mechanism in the NXE just works fine, so it boots to FSD EVERY time
its only the game2FSD thing what just wont work o.O
Post by: GTRagnarok on June 08, 2010, 03:38:00 PM
All I'm doing is building the freeBOOT 0.032 image with the dash launch v1.0 patches instead of the ones that come with freeBOOT. After building the image, flashing it, and then using flash installer to install launch.xex, I can boot into freestyle from games and on bootup just fine. But everytime I try to launch an Xbox1 game, it shows the Xbox1 logo and then the Xbox reboots.
Using freeBOOT ToolBox 2.3 with the Xbox1 emu option works just fine. Does it have anything to do with the fact that I'm using the hacked v5829 compatibility files?
Post by: kettenschutz on June 08, 2010, 10:08:00 PM
QUOTE
Halp! I can't seem to get Xbox1 games to work with this.
All I'm doing is building the freeBOOT 0.032 image with the dash launch v1.0 patches instead of the ones that come with freeBOOT. After building the image, flashing it, and then using flash installer to install launch.xex, I can boot into freestyle from games and on bootup just fine. But everytime I try to launch an Xbox1 game, it shows the Xbox1 logo and then the Xbox reboots.
Using freeBOOT ToolBox 2.3 with the Xbox1 emu option works just fine. Does it have anything to do with the fact that I'm using the hacked v5829 compatibility files?
All I'm doing is building the freeBOOT 0.032 image with the dash launch v1.0 patches instead of the ones that come with freeBOOT. After building the image, flashing it, and then using flash installer to install launch.xex, I can boot into freestyle from games and on bootup just fine. But everytime I try to launch an Xbox1 game, it shows the Xbox1 logo and then the Xbox reboots.
Using freeBOOT ToolBox 2.3 with the Xbox1 emu option works just fine. Does it have anything to do with the fact that I'm using the hacked v5829 compatibility files?
got the same here
did u have a non-original NAND-backup ?
Post by: GTRagnarok on June 08, 2010, 11:13:00 PM
QUOTE(kettenschutz @ Jun 8 2010, 11:08 PM)
got the same here
did u have a non-original NAND-backup ?
No, I have the original. But I figured it out. You have to do that kxam patch thing. I put the appropriate emu patch from the freeBOOT folder into the bin folder in the kxampatchbuilder zip which is in the dash launch folder. I don't know if that actually did anything or was necessary......Anyway, then I ran the batch file to build the patch and finally placed the kxam.patch into the root of Hdd1. After doing that, it still rebooted once more but then works from then on. Hope it works for you.
Post by: kettenschutz on June 08, 2010, 11:26:00 PM
didnt really get those "kxampatchblah"stuff. i am not the biggest crack here
thought we could only flash bin files
or is this possible via xell/xellous ?
maybe i try it when im at home
thanks again
Post by: Inuyasha152 on June 10, 2010, 06:28:00 PM
QUOTE(dryan433 @ May 29 2010, 12:54 PM)
as far as i can see the tut is correct and from that i guess you don't have an orig nand backup to get your smc config and rest of files from
yes you just replace the patches that are in bin folder
create a copy of your xbr image so you have one safe and open it up in 360 flash dump tool v0.94 with your cpu key click tools and edit config and put your right mac to the console in and set your correct region if needed but mac you will want to change to the correct mac of console and save it and extract with ibuild
its best to have this from orig nand as it do help stop the rrod iv found out (only the case with freeboot makes no difference to xbr images so far lol)
hope this is of some help to you
Danny
Hey, just wanted to say thanks for the info and it worked out perfectly. I also extracted my SMC from my XBR image and then flashed using Xellous. Works great! Thanks to all who worked on this
P.S. I can play Xbox 1 games fine, not sure what the kxampatch is or what it really accomplishes.. If anyone would shed some light on this I'm sure everyone would appreciate it
*Edit*
A little more info... Used donor files (upgraded from XBR3) on a Jasper512. Hacked compatability files installed. Games load and returning to FSD from them works as well.
Post by: danthaman673 on June 14, 2010, 05:59:00 AM
I have a box that is Cygnos V2 running on a Falcon. I did a pretty standard build (I confess lately I've started cheating with toolbox 2.4 - in this case I used the Nand option, the HDD option seems only to produce black screens) I then ran the Flash installer for dashlaunch and flashed the utf-8 .ini etc.. No worries there I double check with cygnos toolbox to see that it's mounting the drives (only seems to happen when patch is correctly applied) BUT 50% of the time either when it boots (but usually after leaving game or JTAG app) it will not go to default ooption (Xexmenu 1.1) instead it will go to dash and then behave like a retail box (it won't boot JTAG apps , it just says 'unable to boot <_Insert_JTAG_app_name_here>' or words to that effect.
My guess is that dashlaunch might be affecting Cygnos's SMC JTAG injection (It might explain some of other's ealier problems - not much to do with donor nands) It could be voltage related (It's more likely to boot properly if nothings plugged-in) I'm not sure but I will muck around with it some more and try to nail down when/what is causing it to 'mal-load' for want of a better term.
Perhaps if any of the dashlaunch guys are still reading this topic they might be able to point me in the right direction
Brgds/Dan
Post by: dupfold on June 19, 2010, 12:56:00 PM
UPDATE: Sorted it, found a vid tut. Flashed and xbox 1 games working now!
However, xexmenu now hard resets 360 without a USB plugged in? I have already deleted the 'unknown xbox game' save which caused xexmenu to not boot (black screen) before, but this hard reset is new to me and not heard of this problem before? Any ideas?
Post by: MegaUltraCh1ckn on June 28, 2010, 07:50:00 AM
QUOTE(antisniperspy @ May 25 2010, 11:56 PM)
Ever going to tell us how you patched your xbox without building a new nand??
Post by: kettenschutz on June 28, 2010, 09:46:00 AM
there are more and more games now which boots fine up to FSD, only a few hardliners only want to go back to NXE
if i use here RT and Y at the miniblade i come back2fsd without problems
so the issue, isnt really an issue anymore. its more like a little bug yet
hopefully there comes a lots of cool plugins with dashlaunch now, maybe ftp plugin for all-time-transferring or a mp3 player plugin. this would be cool
a little filebrowser would be awesome, too
dont to forget xlink kai, cause we have the killed ping limit
Post by: neil321 on June 28, 2010, 12:17:00 PM
Post by: danthaman673 on June 28, 2010, 10:24:00 PM
QUOTE(neil321 @ Jun 29 2010, 03:47 AM)
When using toolbox maker 2.4 and needing usb & internal HDD dash lauch do you tick HDD or USB.
Niether, Tick NAND and then use flash_installer to flash the .ini (that should ref the hdd - assuming it's always there) and launch.xex to your Nand, Make sure you edit your .ini in UTF-8 , Put a .ini on th Hdd that refs the Hdd, one on the USB that refs usb0 etc..
Brgds/Dan
PS: If you just want to do a normal build without dashlaunch then still use NAND.
Post by: 360720 on June 29, 2010, 12:50:00 PM
Quick question, can i use the 'smc_dec.bin' i extracted from my 'flashdmp.bin' when creating the freeBOOT image ?
I downloaded the 'flashdmp.bin' via Xellous HTTP interface.
I've once before flashed this 360 and only got a black screen on boot, which i'm told is SMC related. Just want to be sure i have this right before doing anything.
I'm already running freeBOOT on Falcon.
Thanks !
This post has been edited by 360720: Jun 29 2010, 07:52 PM
Post by: doveman007 on June 29, 2010, 02:06:00 PM
I've flashed the .xex to the NAND and I've got the following .ini in the root of my HD:
CODE
[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex
BUT_B = LHdd:\Applications\xm360\XM360.xex
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Default = LHdd:\Freestyle\FreestyleDash.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex
BUT_B = LHdd:\Applications\xm360\XM360.xex
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
It does boot to Freestyle from cold and if go to the MiniBlade from there and press Y and Yes it goes back to Freestyle. However, when in NXE, if I go to the MiniBlade and press Y it goes straight back to NXE without showing the Yes or No prompt and the same if I select Xbox Dashboard from the MiniBlade. So the only way to get back to Freestyle is going Quick Launch - All Programs and finding it, which is what I used to have to do and was hoping wouldn't be necessary with Dash Launch.
Any one know how to fix this?
Post by: doveman007 on June 29, 2010, 02:38:00 PM
It first did this when I was in xexmenu and then used the Miniblade to go back to Freestyle. I heard a click and it rebooted and then kept rebooting at the same point until I turned it off.
I turned it on again and the same thing happened. I don't know if this is anything to do with the dashlaunch patched freeboot I just flashed, or the Ping Check removal patch.
I managed to boot into NXE and then xexmenu and delete the Ping Check patch, which made no difference. I've got a brand new spare PSU so I tried that, thinking that maybe the old one was on the blink, but the same thing happened.
I'm wondering if it's anything to do with the fan speed as when I boot into NXE the fans stay slow, but I've got them set to 90% in Freestyle as it's very hot here at the moment (31c ambient), so when that boots the fans speed up and that happens to be the time it's rebooting.
If I boot into NXE and then XexMenu, so that the fans are on default/auto, the temps are:
CPU 55.8C, GPU 59c, EDRAM 62.9C, MB 39.9c
but all the temps are slowing climbing, which doesn't seem right. In the time it's taken me to type these couple of lines they've now reached:
CPU 58.1C, GPU 62.8c, EDRAM 66.5C, MB 40.6C
I checked and the fans seem to be both working as I can feel (very hot) air being blown out the back. There is the odd tick/click coming from somewhere though.
Anyway, probably nothing to do with the flash or the patch, just a wierd coincidence
Post by: c_b_n on June 29, 2010, 03:33:00 PM
QUOTE(doveman007 @ Jun 29 2010, 09:38 PM)
If I boot into NXE and then XexMenu, so that the fans are on default/auto, the temps are:
CPU 55.8C, GPU 59c, EDRAM 62.9C, MB 39.9c
but all the temps are slowing climbing, which doesn't seem right. In the time it's taken me to type these couple of lines they've now reached:
CPU 58.1C, GPU 62.8c, EDRAM 66.5C, MB 40.6C
That's not that strange. Turn up the fans to 60%.
Did you make your nand image with BestPigs tool? Then install the launch.ini and launch.xex on the nand?
Just try again.
Post by: doveman007 on June 29, 2010, 05:10:00 PM
QUOTE(c_b_n @ Jun 29 2010, 10:33 PM)
That's not that strange. Turn up the fans to 60%.
Fair enough, just been a while since I've seen such high temperatures.
QUOTE
Did you make your nand image with BestPigs tool? Then install the launch.ini and launch.xex on the nand?
I didn't need to, as I'd already built a working Freeboot, I just put the dashlaunch Jasper patch file in place and rebuilt it.
I've dismantled the Xbox just to check the fans were OK but they're fine. I put Freestyle on a USB stick along with a Launch.ini and booted into that fine. Booting from the HD still resulted in Freestyle rebooting though.
I then flashed back the previously working non-dashlaunch Freeboot and booted from HD, which booted into NXE as I'd deleted the old Launch.xex from the HD. I then tried to load Freestyle from the Quick Launch and it just locked up whilst scanning. I loaded Dragons Age fine though but didn't want to play with the fans on auto.
If ran Freestyle from a USB stick with the HD connected, and it scanned the HD fine and worked normally.
I then deleted the Freestyle and fsdata folders from the HD and copied Freestyle from the USB and that seems to have sorted it. I've also re-flashed the dashlaunch Freeboot and the launch.xex and it's booting into Freestyle OK at the moment.
I wonder if there's something dodgy about my HD connecter/casing/lead as I had some problems a couple of weeks ago with games locking up. I connected the HD to my PC and copied a couple of games back over, but I'm not sure if they were actually corrupt or if the HD just wasn't connecting properly. The problems only started since I changed from XBR to Freeboot but that's probably just a coincidence.
Post by: chrisco93 on June 29, 2010, 07:51:00 PM
QUOTE
WARNING: Your current nand is not the zeropaired
If you have a way to switch the nands, do so now
If you have a way to switch the nands, do so now
I have no clue what the means or what i am suppose to do
PLEASE HELP!
Post by: antisniperspy2 on June 29, 2010, 07:57:00 PM
QUOTE(chrisco93 @ Jun 29 2010, 09:51 PM)
ok please some one help me out please, ok so i am trying to get the new updflash.bin into my xbox by using flash360 " i used freeBOOT_ToolBox_Maker24 to make that file" and when i try to write updflash.bin to NAND it says this..
I have no clue what the means or what i am suppose to do
PLEASE HELP!
What type of console do you have? I had that exact warning on my jasper 512 but did not have it on 2 falcons and a 16mb jasper. And all 4 went well when flashing. Hope this helps
Post by: chrisco93 on June 29, 2010, 08:19:00 PM
QUOTE(antisniperspy2 @ Jun 29 2010, 07:57 PM)
What type of console do you have? I had that exact warning on my jasper 512 but did not have it on 2 falcons and a 16mb jasper. And all 4 went well when flashing. Hope this helps
i have a xenon
Post by: doveman007 on June 29, 2010, 08:34:00 PM
QUOTE(chrisco93 @ Jun 30 2010, 02:51 AM)
ok please some one help me out please, ok so i am trying to get the new updflash.bin into my xbox by using flash360 " i used freeBOOT_ToolBox_Maker24 to make that file" and when i try to write updflash.bin to NAND it says this..
I have no clue what the means or what i am suppose to do
PLEASE HELP!
I get the same flashing Freeboot to my Jasper. Doesn't seem to be anything to worry about.
Post by: omegastar on June 30, 2010, 05:27:00 AM
This post has been edited by omegastar: Jun 30 2010, 01:25 PM
Post by: Julets on July 01, 2010, 11:44:00 PM
BTW, I created the image with the 2.4 toolbox maker thing. Nand was ticked and I did _NOT_ do the SMC patch by using the custom freeboot image option. I tried iBuild, maybe for a hour or so, but I just kept getting E79. I first installed freeBoot with ibuild before dashlaunch, and it worked fine. However, now that I have added in the dashlaunch patch, always E79. Anyways, Toolbox maker thingy seems to work fine, just not sure what dashlaunch is looking for that it can't find causing the restarts.
Post by: Julets on July 02, 2010, 10:07:00 PM
In the below launch.ini, I have took into account that the .ini needs to be in UTF-8 (BOM or not? Using BOM), case sensitivity, and that Freestyle is actually on the hdd. I hope this is just user error, and not something that might render me from using this.:-)
CODE
; launch.xex V1.0 config file
; parsed by simpleIni http://code.jellycan.com/simpleini/
; note that Right Bumper is ALWAYS default to return NXE, you MUST hold it if you wish to see NXE
; currently supported devices (for ones with numbers it is up to the user to find out which is correct):
; HDD use: LHdd:\
; USB use: LUsb0:\ LUsb1:\ LUsb2:\
; Memory Unit use: LMu0:\ LMu1:\
; USB memory unit partition use: LMuu0:\ LMuu1:\ LMuu2:\
; CD/DVD use LCd:\ (not recommended to use this one)
; buttons can point to any xex, or any CON with default.xex in it on any of the above devices
[QuickLaunchButtons]
BUT_A = LHdd:\Freestyle\FreestyleDash.xex
BUT_B = LHdd:\Freestyle\FreestyleDash.xex
BUT_X = LHdd:\Freestyle\FreestyleDash.xex
BUT_Y = LHdd:\Freestyle\FreestyleDash.xex
Start = LHdd:\Freestyle\FreestyleDash.xex
Back = LHdd:\Freestyle\FreestyleDash.xex
LBump = LHdd:\Freestyle\FreestyleDash.xex
; Default is what loads when you hold no buttons
; leave this blank if you want NXE as default
Default = LHdd:\Freestyle\FreestyleDash.xex
; plugins are started from a sys thread and must have a sys path defined here
; examples of valid paths are:
; \Device\Harddisk0\Partition1\somedllxex.xex
; \Device\Mass0\somedllxex.xex
; these are NOT based on mount points
;[plugins]
;plugin1 =
;plugin2 =
;plugin3 =
;plugin4 =
;plugin5 =
; all comments and fields in this file are optional, you can remove anything you don't need
; njoy, XeDev/cOz
Post by: Julets on July 06, 2010, 02:16:00 AM
Any help on this is welcomed. Not trying to be a self helpless person, but I've really tried just about everything I can throw at it to get it working. Again, the xbox just keeps rebooting right as it tries to load the dashboard. I get just a shimmer of a glimpse of the NXE dash, then it reboots. That is the end result I get with using either the pig app, or ibuild.
Post by: sthetix on July 09, 2010, 01:44:00 AM
QUOTE(Julets @ Jul 6 2010, 03:16 PM)
Bump.
Any help on this is welcomed. Not trying to be a self helpless person, but I've really tried just about everything I can throw at it to get it working. Again, the xbox just keeps rebooting right as it tries to load the dashboard. I get just a shimmer of a glimpse of the NXE dash, then it reboots. That is the end result I get with using either the pig app, or ibuild.
i found this issue too........
here's what I did...
delete content.xml and config.xml from Freestyle.
it boots to fsd..
Post by: Julets on July 10, 2010, 07:50:00 PM
Again, I'm on a Falcon using a Cygnos v2. I believe I have taken the appropriate patches for the cygnos and Dashlaunch. I must be doing something right at least, because FSD boots sometimes, just sometimes it doesn't.
Post by: antisniperspy on July 10, 2010, 11:14:00 PM
QUOTE(Julets @ Jul 10 2010, 09:50 PM)
Well thanks for the info. I'm not sure if that really had anything to do with it, but after deleting those 2 it does work...sometimes. Dashlaunch works 50% of the time booting FSD, the other 50% it boots m$ dash. Not too sure if this new Dashlaunch is as stable as previous versions, or the documentation is lacking a underlying topology of how to, or where to, put the launch.ini. Some unknown variables seem to be in play though. For instance, without the USB HDD plugged in the front, it boots to FSD 70% of the time (tested this just by turning it off and on 10 times). With the USB HDD plugged in, it boots FSD 20%, 70% of the time m$ dash, and 10% locks up. The launch.ini and all copies of it are identical on all devices.
Again, I'm on a Falcon using a Cygnos v2. I believe I have taken the appropriate patches for the cygnos and Dashlaunch. I must be doing something right at least, because FSD boots sometimes, just sometimes it doesn't.
Sorry if you posted this in another post but did you install the launch.xex into the nand. Some people seem to miss that. Again sorry if you already stated this.
Post by: hfmls on July 11, 2010, 04:41:00 AM
i really wanted to use always freestyle dash but i dont want to screw my xbox360
Post by: danthaman673 on July 18, 2010, 10:26:00 AM
QUOTE(360720 @ Jun 30 2010, 04:20 AM)
Hi Guys,
Quick question, can i use the 'smc_dec.bin' i extracted from my 'flashdmp.bin' when creating the freeBOOT image ?
I downloaded the 'flashdmp.bin' via Xellous HTTP interface.
I've once before flashed this 360 and only got a black screen on boot, which i'm told is SMC related. Just want to be sure i have this right before doing anything.
I'm already running freeBOOT on Falcon.
Thanks !
Yes you should be able to use the previous smc for the build, but freeboot puts it in a different place to XBR etc.. so don't expect to be able to circumvent the build or use a substandard version of XBR to build from as ur lucky that it's even possible to build from XBR, try ur original dump if you have it
PS: Sorry got some wires crossed on the above : u downloaded it from xellous http:?? You SMC has info unique to ur box (sort of - 4 want of a better way to put it) and I'm pretty sure u need the base SMC to patch into freeboot BUT You could try downloading the hakd SMC for ur box from the usual places... But I'm not entirely sure what it is ur trying to do exactly and how?? - Do you have your original nand OR a working version of XBR ?? , I'm assuming your trying to upgrade to freeboot.. Does ur KV match ur nand??
PPS : Black screen does not 100% mean SMC btw
QUOTE(chrisco93 @ Jun 30 2010, 11:21 AM)
ok please some one help me out please, ok so i am trying to get the new updflash.bin into my xbox by using flash360 " i used freeBOOT_ToolBox_Maker24 to make that file" and when i try to write updflash.bin to NAND it says this..
I have no clue what the means or what i am suppose to do
PLEASE HELP!
Don't worry about the KV warning as flash 360 was built in XBR days back when KV's resided in a predictable spot (no longer the same place) so that error/warning is irrelevant.
Hope this helps.
@Julets - I have the same problem - It's got to do with how the cygnos v2 injects the JTAG etc.... etc.. Anyway I'm hoping those guys will <eventually> patch it with (cygnos)toolbox otherwise you could use that SMC modding app (I knew it had to be usefull for something other than fixing 2nd rate JTAG installs !!) It's name escapes my. With mine it has to do with (how/whether/howmany controlers are on at boot, igf there is dvd in drive etc... otherwise it behaves like retail box)
Brgds/Dan
Post by: colt45joe on July 18, 2010, 04:39:00 PM
i flashed my jtag console, and it is now updated to 9199 with freeboot.
i put launch.xex, and launch.ini in the root on my usb0 external harddrive, and it is not working.. am i missing something?
my launch.ini looks like this:
[QuickLaunchButtons]
Default = LUsb0:\Freestyle\FreestyleDash.xex
This post has been edited by colt45joe: Jul 18 2010, 11:55 PM
Post by: antisniperspy on July 18, 2010, 05:50:00 PM
QUOTE(colt45joe @ Jul 18 2010, 06:39 PM)
i used freeboot toolbox maker 2.4 and i chose the usb option for dashlaunch.
i flashed my jtag console, and it is now updated to 9199 with freeboot.
i put launch.xex, and launch.ini in the root on my usb0 external harddrive, and it is not working.. am i missing something?
my launch.ini looks like this:
[QuickLaunchButtons]
Default = LUsb0:\Freestyle\FreestyleDash.xex
Launch.xex needs to be flashed to nand and not on the usb0
Post by: Midnight Tboy on July 19, 2010, 11:28:00 AM
First thing.....Edit that ini file with notepad and make sure you save it as UTF-8 format. I used the sample ini file to begin with which was in regular ascii
Second...if it still doesn't work...if you have a regular 360 hdd try having the ini file point to Freestyle running from there instead.
Here's my ini file (running from usb still)
[QuickLaunchButtons]
BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Default = LHdd:\FreeStyle\FreestyleDash.xex
The only reason I chose USB in Freeboot Toolbox Maker, was when choosing HDD the console would not boot to any dashboard for me...only xellous....and apparantly I'm not the only one with that problem
This post has been edited by Midnight Tboy: Jul 19 2010, 06:32 PM
Post by: flxfxp on July 20, 2010, 01:12:00 PM
I recently bought a Jtagged Xbox 360 Elite (Falcon) and I'd like to get Dash Launch to work with the new FSD2.
I haven't done any of the FreeBOOT stuff myself (yet) so I'd appreciate it if someone could explain to me what I exactly should be doing. It should use the internal HDD for launching since I don't have an USB HDD attached to it. Help would be very much appreciated.
Thank you in advance,
Dennis
Post by: flxfxp on July 20, 2010, 02:31:00 PM
- Made a fresh dump with Flash360
- Downloaded freeBOOT 0.032 ToolBox Maker 2.4
- Used the Dash Launch NAND option
- Created the updflash.bin
- Flashed updflash.bin with Flash360
- Created launch.ini
- Put launch.ini in flash_installer and upload that to root of hdd1
- Run flash_installer\default.xex and update
- It now boots FSD2.0
However, when I turn the xbox off and on I get a RROD. When I turn off/on again it boots FSD2.0. Any way to prevent the RRODs from happening?
Thanks,
Dennis
Post by: dschu012 on July 20, 2010, 03:23:00 PM
This post has been edited by dschu012: Jul 20 2010, 10:23 PM
Post by: hazed69 on July 28, 2010, 01:29:00 AM
QUOTE(iEzio @ May 22 2010, 10:30 PM)
I did the same thing and it's working, but I think mine isn't working like it should.
I want to use Button 'A' for XeXMenu 1.1 and as 'Default' my FreeStyle Dash.
FreeStyle Dash is starting, if I'll start my console, XeXMenu is starting, if I hold the 'A' Button at starting my Xbox, that's fine.
But if I try to go back to FreeStyle Dash via the mini-dashboard, I've to hold the right trigger (RT) for it. The readme says, I just need to do this for booting in NXE, but mine will boot to NXE, if I klick nothing then.
So, I even tried to start XeXMenu that way, it won't start.
I just got the choice between FreeStyle Dash and NXE if I'll hit the 'Y' button in the mini-dash.
So, what's wrong there? - Shouldn't I boot back to FreeStyle Dash, if I klick nothing? - Shouldn't I be able to boot to XeXMenu, if I klick 'A' then, and shouldn't the NXE just came up, if I click the right bumper (RB)?
out of the readme: "Default is what loads when you hold no buttons"
help would be awesome, mates!
im lost...
i have freeboot (newest with dashlaunch) ive edit my launch.ini
im lost on the part were we put the launch exe
Post by: hazed69 on July 28, 2010, 08:21:00 AM
QUOTE(hazed69 @ Jul 28 2010, 08:29 AM)
im lost...
i have freeboot (newest with dashlaunch) ive edit my launch.ini
im lost on the part were we put the launch exe
it wont let me edit my own post?
i ran default.exe installed my ini
to the nand im not sure what to do with launch exe
i ran it but didnt work said to in stall the game
i also redid my ini and saved them as utf8
its all in the flash folder on the hdd
This post has been edited by hazed69: Jul 28 2010, 03:26 PM
Post by: DynaMight on July 28, 2010, 10:07:00 AM
I wanted to use DashLaunch on my JTAGGED Xbox, so I used FreeBOOT Toolbox to create a image with DashLaunch, I entered my CPU Key, choose HDD as the ini option. Copied my launch.ini to the harddrive, used Flash360 to flash the new image but now the Xbox will not boot. Turns on (even with the controller) but never any picture on the screen, I tried holding the right bumper to default to NXE but no use.
I guess what I want to check that if the launch.ini is incorrect it wont cause this? so it saves me re-soldering the JTAG connections to reflash again.
Post by: mku on July 28, 2010, 10:34:00 AM
QUOTE(DynaMight @ Jul 28 2010, 05:07 PM)
I wanted to use DashLaunch on my JTAGGED Xbox, so I used FreeBOOT Toolbox to create a image with DashLaunch, I entered my CPU Key, choose HDD as the ini option. Copied my launch.ini to the harddrive, used Flash360 to flash the new image but now the Xbox will not boot. Turns on (even with the controller) but never any picture on the screen, I tried holding the right bumper to default to NXE but no use.
I had the same problem, it would only boot if I had the nand option selected in FreeBoot toolbox. The .ini can still be on the xbox hdd or a usb hdd. Check if Xellous will boot by turning the console on with the eject button and maybe you can reflash that way.
Post by: ZprivateZ on July 28, 2010, 11:06:00 AM
QUOTE(hazed69 @ Jul 28 2010, 10:21 AM)
it wont let me edit my own post?
i ran default.exe installed my ini
to the nand im not sure what to do with launch exe
i ran it but didnt work said to in stall the game
i also redid my ini and saved them as utf8
its all in the flash folder on the hdd
Did you have your launch.ini in the "flash_installer" folder when you ran default.xex? If not then launch.ini is not in your nand. Me personally would recommend that you don't put the launch.ini in the nand and just keep it on the xbox's internal hdd, easier to edit in the future without having to flash the nand every time with
default.xex out of the default_flasher folder but choice is yours. If it was there then you need to double check your launch.ini and make sure it's correctly setup and if you make any changes then copy the newly edited launch.ini back to flash_installer folder and reflash it for changes to take effect.
Post by: DynaMight on July 28, 2010, 03:34:00 PM
QUOTE(mku @ Jul 28 2010, 05:34 PM)
I had the same problem, it would only boot if I had the nand option selected in FreeBoot toolbox. The .ini can still be on the xbox hdd or a usb hdd. Check if Xellous will boot by turning the console on with the eject button and maybe you can reflash that way.
Thanks for the help, reflashed in Xellous and all is well now.
Post by: hazed69 on July 28, 2010, 05:49:00 PM
QUOTE(ZprivateZ @ Jul 28 2010, 06:06 PM)
Did you have your launch.ini in the "flash_installer" folder when you ran default.xex? If not then launch.ini is not in your nand. Me personally would recommend that you don't put the launch.ini in the nand and just keep it on the xbox's internal hdd, easier to edit in the future without having to flash the nand every time with
default.xex out of the default_flasher folder but choice is yours. If it was there then you need to double check your launch.ini and make sure it's correctly setup and if you make any changes then copy the newly edited launch.ini back to flash_installer folder and reflash it for changes to take effect.
yup its in the folder
i looked at freebot allinone. this is what i used to make my freeboot nand
the read me says it has the dash pathes
"III. New Features
=================
- updated to kernel 2.0.9199
- now supports all consoles and flashing solutions (ikari)
- removed memory protections
Code can be executed and modified anywhere in the range from 0x80000000
to 0x9FFFFFFF. This can be used to create game trainers and will allow
for porting of emulators, which rely on dynamic compilation.
[2 different patches 1 with this: xbox1 emu doesn't, 1 without xbox1 emu does work]
- encrypted DevKit XEXes are now working
- includes dash launch patch
- LIVE/PIRS/GOD content fully working
- internal security breach reports deactivated (Redline99)
- easier image generation process (ikari)
- ibuild can now also generate single flash XeLL and original images (ikari)
if i follow this correctly i should have the dash patch right?
im just checking making sure i do have the dash patch since nothing is working for me.
what do i do with the launch exe
were does that go?
Post by: ZprivateZ on July 28, 2010, 06:37:00 PM
QUOTE(hazed69 @ Jul 28 2010, 07:49 PM)
yup its in the folder
i looked at freebot allinone. this is what i used to make my freeboot nand
the read me says it has the dash pathes
"III. New Features
=================
- updated to kernel 2.0.9199
- now supports all consoles and flashing solutions (ikari)
- removed memory protections
Code can be executed and modified anywhere in the range from 0x80000000
to 0x9FFFFFFF. This can be used to create game trainers and will allow
for porting of emulators, which rely on dynamic compilation.
[2 different patches 1 with this: xbox1 emu doesn't, 1 without xbox1 emu does work]
- encrypted DevKit XEXes are now working
- includes dash launch patch
- LIVE/PIRS/GOD content fully working
- internal security breach reports deactivated (Redline99)
- easier image generation process (ikari)
- ibuild can now also generate single flash XeLL and original images (ikari)
if i follow this correctly i should have the dash patch right?
im just checking making sure i do have the dash patch since nothing is working for me.
what do i do with the launch exe
were does that go?
You don't do anything with launch.xex it was installed to nand when you ran default.xex in the flash_installer folder.
What does you launch.ini look like?
Post by: hazed69 on July 29, 2010, 11:35:00 AM
QUOTE(ZprivateZ @ Jul 29 2010, 01:37 AM)
You don't do anything with launch.xex it was installed to nand when you ran default.xex in the flash_installer folder.
What does you launch.ini look like?
[QuickLaunchButtons]
Default = LHdd:\Freestyle 2.0\default.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex
BUT_B = LHdd:\Applications\xm360\XM360.xex
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Post by: xboxhaxorz on July 29, 2010, 01:08:00 PM
when i used the nand way i put the launch ini in the flash installer folder and flashed it but the launch ini was not on the root and it booted directly to nxe. when i put the launch ini back on the root of hdd it worked fine. i thought the point of the nand way was to not have the launch ini on root?
Post by: ZprivateZ on July 29, 2010, 01:20:00 PM
QUOTE(hazed69 @ Jul 29 2010, 01:35 PM)
[QuickLaunchButtons]
Default = LHdd:\Freestyle 2.0\default.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex
BUT_B = LHdd:\Applications\xm360\XM360.xex
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Default = LHdd:\Freestyle 2.0\default.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex <------- wont work
BUT_B = LHdd:\Applications\xm360\XM360.xex <------- wont work
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558 <------ not needed since you have xex version set to button X
change to this
[QuickLaunchButtons]
BUT_X = LHdd:\XeXMenu\default.xex
BUT_B = LHdd:\XM360\XM360.xex
Default = LHdd:\Freestyle 2.0\default.xex
reflash with flash_installer since that is the method you choose (with launch.ini in the flash_installer folder as you did before) then leave a copy of your launch.ini on the root of your internal hard drive.
Post by: hazed69 on July 29, 2010, 02:40:00 PM
QUOTE(ZprivateZ @ Jul 29 2010, 08:20 PM)
Default = LHdd:\Freestyle 2.0\default.xex
BUT_X = LHdd:\Applications\xexmenu\default.xex <------- wont work
BUT_B = LHdd:\Applications\xm360\XM360.xex <------- wont work
BUT_Y = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558 <------ not needed since you have xex version set to button X
change to this
[QuickLaunchButtons]
BUT_X = LHdd:\XeXMenu\default.xex
BUT_B = LHdd:\XM360\XM360.xex
Default = LHdd:\Freestyle 2.0\default.xex
reflash with flash_installer since that is the method you choose (with launch.ini in the flash_installer folder as you did before) then leave a copy of your launch.ini on the root of your internal hard drive.
my xm360 is in game demo for nxe and my xexmenu
how would i do that?
cant remember what folder they are in
i guess i can just moved
it didnt work
[QuickLaunchButtons]
BUT_X = LHdd:\XeXMenu\default.xex
BUT_B = LHdd:\XM360\XM360.xex
Default = LHdd:\Freestyle 2.0\default.xex
lol i havent tryed this yet but it shows as hdd1 on my xbox you think!!!!
ill try it
update didnt work i changed both of them to this
This post has been edited by hazed69: Jul 29 2010, 09:51 PM
Post by: krizalid on July 29, 2010, 04:09:00 PM
Like sometimes loading NXE after exiting game/emu/etc.?
Thanks.
Post by: reprec on July 30, 2010, 11:50:00 AM
QUOTE(krizalid @ Jul 29 2010, 11:09 PM)
Anyone knows about an update to fix stability issues?
Like sometimes loading NXE after exiting game/emu/etc.?
Thanks.
Is this happening to you with FSD2? Try changing your default launch.ini path, instead i.e. use xexmenu to launch. You'll see it always come back to xexmenu, doesn't matter which game/emu/etc.
I know because it happened to me and it freaked me out a lot, it's some weird FSD2 issue, after updating it to the latest alpha. I rolled back to a previous version and it goes perfectly fine, it's not about dashlaunch.
Post by: f0xrolder on July 31, 2010, 08:12:00 AM
I'm a newbie to the 360 homebrew scene, just recently got a jtagged console running 9199 dash its a pro 60GB console has freeboot xexmenu etc.. I've recently put freestyle dash 2 alpha on and updated but no matter what i try to get dashlaunch to boot directly to fsd2 alpha i cant get it to work. its a Jasper 16mB console. Ive also got no idea where to put the Patches_Jasper.bin file from dashlaunch\freeboot_patches\ so I havent yet
my launch.ini looks like
[QuickLaunchButtons]
BUT_X = Usb0:\fsd2 alpha\default.xex
Default = Hdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
I put the .ini into the flash installer directory installed it nothing.
Copied it to the root of my hdd and usb drive. Nothing. I wasnt sure it it would work or not so im not surprised as I dont know much about the 360 atm, im trying, but if it were a pc or a wii then there wouldnt b a problem So any help would be greatly appreciated or if u could point me to a tutorial or two would b great.
Decided I would'nt muck around and jtag it myself as im not planning to mod or soft mod anyone elses consoles like i did for family and friends wiis. purely a gaming console for me. so i got it from this guy here...
This is the console ----> http://www.ozmodchips.com/premodded-freebo...-pro-p-316.html it has xexmenu its a jasper 16mB with Freeboot 2.0.9199 installed
Thanks.
This post has been edited by f0xrolder: Jul 31 2010, 03:50 PM
Post by: hazed69 on August 02, 2010, 04:09:00 PM
Post by: Aldanga on August 02, 2010, 04:12:00 PM
Post by: hazed69 on August 02, 2010, 04:23:00 PM
why cant i get this thing too default freeboot?
Post by: Aldanga on August 02, 2010, 04:50:00 PM
Post by: hazed69 on August 02, 2010, 05:45:00 PM
QUOTE(hazed69 @ Aug 2 2010, 11:23 PM)
ok good!
why cant i get this thing too default freeboot?
(IMG:style_emoticons/default/uhh.gif) freeboot lmao i mean Freestyle
Post by: Aldanga on August 02, 2010, 05:48:00 PM
Post by: hazed69 on August 02, 2010, 06:03:00 PM
[QuickLaunchButtons]
BUT_X = LHdd1:\XeXMenu\default.xex
BUT_B = LHdd1:\XM360\XM360.xex
Default = LHdd1:\Freestyle 2.0\default.xex
Post by: f0xrolder on August 02, 2010, 07:07:00 PM
xexmenu is a nxe or god container file in 000000000000\code9999\00080000\xexmenucode etc.. on my console show up in game tab as a demo and doesnt run from an xex and i have fsd2 alpha on the external usb hdd at \fsd2 alpha\default.xex
tried to get it to boot directly to fsd2 alpha by editing the launch.ini file and flashing that and launch.xex to the nand which it did with no luck still goes straight to xbox dash, and have copied both launch ini and xex to the root of the 60GB hdd and external usb hdd with no luck either.
First attempt
[QuickLaunchButtons]
BUT_X = Usb0:\fsd2 alpha\default.xex
Default = Hdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
second effort
[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.
Post by: WarriorSan on August 07, 2010, 05:36:00 AM
From the readme:
QUOTE
Changes from dash launch 1.0 patch set:
-Jasper big block machines need only apply
- fixes flash MU corruption issues
*note that flash mu is contained in:
blocks 0x10 thru the end of block 0x15B
blocks 0x200 to end of NAND
in small block notation (for nandpro) this is:
blocks 0x80 thru the end of block 0xAD8
blocks 0x1000 to end of NAND
if you update at some point in the future, keep this in mind.
[cOz]
This post has been edited by WarriorSan: Aug 7 2010, 12:48 PM
Post by: dschu012 on August 07, 2010, 10:24:00 AM
QUOTE(hazed69 @ Aug 3 2010, 01:03 AM)
i have flash installer on thr root in a folder name flashinstaller and in there i have the launch exe and the launch ini plus i have the ini in the root of hdd and i went ahead and flash them to my nand wich i see it in under flash folder
[QuickLaunchButtons]
BUT_X = LHdd1:\XeXMenu\default.xex
BUT_B = LHdd1:\XM360\XM360.xex
Default = LHdd1:\Freestyle 2.0\default.xex
Don't flash launch.ini to nand. When I did I could never get stuff to boot. You just need the one launch.ini in the root of your hdd.
Post by: hazed69 on August 07, 2010, 12:35:00 PM
QUOTE(dschu012 @ Aug 7 2010, 05:24 PM)
Don't flash launch.ini to nand. When I did I could never get stuff to boot. You just need the one launch.ini in the root of your hdd.
well do I need to reflash my NAND or can I just delete ini and launch exe in the flash folder?
Post by: finalman on August 07, 2010, 11:16:00 PM
QUOTE(WarriorSan @ Aug 7 2010, 12:36 PM)
[c0z] released an update for Dash Launch v1.0 for jasper BB 256mb / 512mb users so they can finally safely use their internal memory. Please note that you first backup everything you got on the internal memory because after the re-flash its getting formatted...
From the readme:
Changes from dash launch 1.0 patch set:
-Jasper big block machines need only apply
- fixes flash MU corruption issues
*note that flash mu is contained in:
blocks 0x10 thru the end of block 0x15B
blocks 0x200 to end of NAND
in small block notation (for nandpro) this is:
blocks 0x80 thru the end of block 0xAD8
blocks 0x1000 to end of NAND
if you update at some point in the future, keep this in mind.
[cOz]
Where do we get this from? I can't find it on xbins.
Post by: cory1492 on August 08, 2010, 12:11:00 AM
QUOTE(hazed69 @ Aug 7 2010, 12:35 PM)
well do I need to reflash my NAND or can I just delete ini and launch exe in the flash folder?
just put one on your hdd or on your usb, it uses whichever it finds first with flash being the last place it looks.
Post by: danthaman673 on August 08, 2010, 05:22:00 AM
QUOTE(f0xrolder @ Aug 3 2010, 10:37 AM)
so my jasper 16mB console with Freeboot 2.0.9199 installed should work also?? Or not???
xexmenu is a nxe or god container file in 000000000000\code9999\00080000\xexmenucode etc.. on my console show up in game tab as a demo and doesnt run from an xex and i have fsd2 alpha on the external usb hdd at \fsd2 alpha\default.xex
tried to get it to boot directly to fsd2 alpha by editing the launch.ini file and flashing that and launch.xex to the nand which it did with no luck still goes straight to xbox dash, and have copied both launch ini and xex to the root of the 60GB hdd and external usb hdd with no luck either.
First attempt
[QuickLaunchButtons]
BUT_X = Usb0:\fsd2 alpha\default.xex
Default = Hdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
second effort
[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.
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)
Good to hear the fixed BB, no if they could only fix all the other probs we have with dashlaunch eg; USBmu's being mounted as USB (so .ini's fail when friends bring over their profile's on a USBmu etc.. - Huge pain) And that thing it does on several of my personal consoles where it goes back to NXE when it's not meant to anbd then wont boot unsigned code eg; Can't launch Xexmneu 1.1 is the error I get when trying to go back to what
I was doing. (Not using any buttons only default
It's an awesome bit of code, I just wish they could iron-out the faults (there's more ,not all 100% casued by Dashlaunch eg; strange shutdowns and other stuff - But I have to go cook dinner...)
Brgds/Dan
This post has been edited by danthaman673: Aug 8 2010, 12:26 PM
Post by: cory1492 on August 08, 2010, 07:17:00 AM
QUOTE(f0xrolder @ Aug 2 2010, 07:07 PM)
[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash
Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.
There is a good reason why samples were included... you're forgetting the enumeration number on USB
CODE
; HDD use: LHdd:\
; USB use: LUsb0:\ LUsb1:\ LUsb2:\
; Memory Unit use: LMu0:\ LMu1:\
; USB memory unit partition use: LMuu0:\ LMuu1:\ LMuu2:\
; USB use: LUsb0:\ LUsb1:\ LUsb2:\
; Memory Unit use: LMu0:\ LMu1:\
; USB memory unit partition use: LMuu0:\ LMuu1:\ LMuu2:\
danthaman is right too, I don't think spaces in folder names or file names is 'proper' for the OS.
QUOTE(danthaman673 @ Aug 8 2010, 05:22 AM)
Good to hear the fixed BB, no if they could only fix all the other probs we have with dashlaunch eg; USBmu's being mounted as USB (so .ini's fail when friends bring over their profile's on a USBmu etc.. - Huge pain) And that thing it does on several of my personal consoles where it goes back to NXE when it's not meant to anbd then wont boot unsigned code eg; Can't launch Xexmneu 1.1 is the error I get when trying to go back to what
I was doing. (Not using any buttons only default
It's an awesome bit of code, I just wish they could iron-out the faults (there's more ,not all 100% casued by Dashlaunch eg; strange shutdowns and other stuff - But I have to go cook dinner...)
Brgds/Dan
See above, the MU partition on a USB stick is NEVER mounted as USB, they each have individual mount points - the problem is, when you have more than one usb device, they don't enumerate per plug socket but basically "whatever I find first is Mass0" (and thus LUsb0/LMuu0) regardless of which socket it is in or whether it was plugged into the machine ever before (and the same is true for MU, not the usb kind though regular MU still are USB devices) - it has something to do with the way usb hubs and such work under NT kernel and really should be up to the end user to sort (ie: plug in the extra/abnormal usb stick AFTER booting the machine.) The same goes for bringing foreign usb sticks with launch.ini on them too, no program can be a mind reader.
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.
Shut down reboots occur on unhandled exceptions. Normally your machine would just freeze, the freeze has little or nothing to do with dash launch (but it is kinda nice to not have to get up to force the machine to turn off.)
This post has been edited by cory1492: Aug 8 2010, 02:19 PM
Post by: dschu012 on August 08, 2010, 07:57:00 AM
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.
Post by: jayboy86 on August 08, 2010, 10:18:00 AM
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
Post by: jhoff80 on August 08, 2010, 01:23:00 PM
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
Post by: hazed69 on August 08, 2010, 08:55:00 PM
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
Post by: f0xrolder on August 08, 2010, 11:21:00 PM
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
Post by: finalman on August 08, 2010, 11:54:00 PM
Post by: garus on August 09, 2010, 01:09:00 AM
This post has been edited by garus: Aug 9 2010, 08:21 AM
Post by: madusmacus on August 09, 2010, 02:18:00 AM
was this not a freeboot issue ?
i have 2 512 jaspers and im to scare to use MU :¬)
Post by: CasioNo15 on August 09, 2010, 09:22:00 AM
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
Post by: hazed69 on August 09, 2010, 11:49:00 AM
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?
Post by: manbearpig_06 on August 09, 2010, 08:05:00 PM
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
Post by: madusmacus on August 09, 2010, 08:40:00 PM
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 :¬)
Post by: Saleian on August 10, 2010, 01:11:00 AM
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
Post by: f0xrolder on August 10, 2010, 01:26:00 AM
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
Post by: ImRickJamesB1tch on August 10, 2010, 06:01:00 AM
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
Post by: jayboy86 on August 10, 2010, 09:48:00 AM
thx
Post by: juggahax0r on August 10, 2010, 02:57:00 PM
QUOTE(jayboy86 @ Aug 10 2010, 11:48 AM)
any decent guides around as i would love to auto boot fsd2. im running freeboot 0.032 9199
thx
The readme included and the sample launch.ini should be as good a guide as you really need...maybe someone will make an editing tool for noobs but it's pretty easy to follow the sample they give you..use flash installer to get the files on your nand , get the launch.ini ready put it in the folder with the flashinstaller xex and it will flash them to the nand for you. the main thing you need to worry about is the syntax of the paths one mistake and it will fail to do what you want it to do. I fought for an hour with a launch.ini only to find out i had made a grammatical error in the path listing. Once i fixed it everything was good.
Post by: sm32 on August 11, 2010, 02:14:00 AM
it always launches FSD when first turned on, but most of the time whenever i hit ( X ) and go to dashboard, it loads NXE.
this only happens on one of my hard drives (750gb) and not the other (640gb). To check if it was the hard drive that may be failing or something of the sort, i copied FSD to USB0:\ and the same issues arose as with the 750gb drive DL alone (though I did have the 750g hdd still plugged into HDD port).
any ideas what might be causing it to work on first boot but not subsequent dash requests?
if it is any consolation i added a lot of avatar DLC today; i was also playing around with trying to get saves transferred from an older xenon box (most of them worked, some didnt--like forza3).
thanks
Post by: sm32 on August 11, 2010, 03:16:00 AM
not sure what the deal is at all!
Post by: Vel on August 12, 2010, 06:47:00 AM
I'm having a few problems getting this working.
These are the steps I've followed:
1. Using FreeBOOT Toolbox Maker v2.4 I created a new FreeBOOT image using my original NAND image and CPU key. I had to choose the NAND option as after selecting HDD my 360 boots with a green light on the console and produces no display on my TV.
2. Created launch.ini file saved in UTF-8 format which reads as follows:
[QuickLaunchButtons]
Default = LHdd:\FreeStyle\FreestyleDash.xex
BUT_Y = LHdd:\FreeStyle\FreestyleDash.xex
3. Added newly created launch.ini file to the flash_installer folder and copied the folder to the root of my internal HDD (so I can find it).
4. Located flash_installer folder on the xbox and ran the default.xex which is stored inside.
5. Pressed A to flash the files my NAND.
6. Pressed Y to Exit.
7. Console boots back to NXE, turned Xbox off and back on and still booted back into NXE.
8. Tried adding a copy of the launch.ini to root of my HDD, MU and HDDX (no success, having the .ini file in any of the locations individually or together)
9. Tried adding launch.xex to the above locations as well, but still no success, my Xbox keeps booting to the NXE dash.
I am using a 512MB Jasper, does anyone have any idea what my issue could be, I've read through all the posts in this forum, but none of the suggestions have helped.
Also please note my Freestyle folder does have a capital S when it's in the root of my HDD,
Thanks,
Vel
EDIT: Turns out for some reason my FreestyleDash.xex was actually spelt FreesyleDash.xex all sorted now
Post by: Vash3k on August 15, 2010, 08:33:00 PM
Post by: Aldanga on August 15, 2010, 08:35:00 PM
Post by: th0r615 on September 01, 2010, 09:35:00 PM
CODE
[QuickLaunchButtons]
BUT_A =
BUT_B = LHdd:\FreeStyle\default.xex
BUT_X =
BUT_Y =
Start =
Back =
LBump =
Default =LHdd:\FreeStyle\default.xex
and Yes its saved as UTF-8 and its also located at the root of my Hdd1.BUT_A =
BUT_B = LHdd:\FreeStyle\default.xex
BUT_X =
BUT_Y =
Start =
Back =
LBump =
Default =LHdd:\FreeStyle\default.xex
I just dont understand. dashlaunch 0.2 works.
*EDIT* also wanted to add that it is a falcon box, in case that helps.
Post by: WarriorSan on September 02, 2010, 12:29:00 PM
QUOTE
This patch is given as is and I am not responsible if anything happens.
Thanks to XeDev fot the kxam patch builder and included the demo patch which started this,
FBDev for the 30ms ping limit bypass that is included, and TheFallen93 for powerpc tips.
Update:
Fixed a bug that caused the xbox 360 to crash upon loading an xbox 1 game
UnlicensedContentFix
Post by: soulwarrior on September 02, 2010, 10:55:00 PM
QUOTE(th0r615 @ Sep 1 2010, 11:35 PM)
[QuickLaunchButtons]
BUT_A =
BUT_B = LHdd:\FreeStyle\default.xex
BUT_X =
BUT_Y =
Start =
Back =
LBump =
Default = LHdd:\FreeStyle\default.xex
1. You forgot the space in the default line between the = and LHdd:\
2. Copy it as you see it now
3. Save as asci not utf-8
Post by: p4r0l3 on September 03, 2010, 07:45:00 AM
QUOTE(WarriorSan @ Sep 2 2010, 01:29 PM)
What does this patch do exactly?
Post by: p4r0l3 on September 03, 2010, 11:41:00 AM