Changelog:
v2.06
- update to fbbuild 0.11 patches
- fixed bug with fatal freeze options
- changed installer to use zeropair CB version to determine patch set
- added new options dvdexitdash and xblaexitdash
- added regionspoof, dvdexitdash and xblaexitdash to ini updater
- added instructions to this readme regarding boot time buttons and diagnosing
non-ASCII ini files

Again, it's for 12611 only!

ownload: n/a (built with XDK)

XBOX 360/development/system apps/dash_launch/

Download: n/a (built with XDK)

Is there a need to upgrade if we're already on 2.05 successfully?

I'm gonna say no as long as you aren't running into any issues.....when/if you DO run into issues, then you know there's an update that will probably fix it!

I'm currently on 2.05 also and have no problems at all with anything so I'm not gonna update yet....even tho it is really easy and quick to do. lol

Well, I just upgraded to 12611 using Easy Freeboot and to be honest, I've never used Dash Launch, but I know part of it has to be injected into the NAND. So will I need to rebuild my NAND now?

No, it has it's own installer that you run from your 360 now. Very simple!

i wonder if this will fix the installer seeing my falcon 5770 as a zypher....

nevermind....

Thank you for adding the exit to nxe or custom dashboard options...

So, we are talking about Dash Launch v2.07 as anounced in front page or v2.06 ?

Working Great

Soz for the links, Ranger72

@ RolF2, typo on front page. It's 2.06 as can bee seen here http://www.xbins.org/

If we use this, will this update our patchset/fbbuild to .11?

Yes this will update your patch set to the latest freeboot build v.011.

So when I use this, I don't have to use fbbuild or FreeBOOT Toolbox.
It will give me AP2.5 support, right?

I'm asking because "cOz released a new version of Dash Launch for JTAG 360s with "freeBOOT" 12611/v0.04(1) (fbBuild 0.11)" indicates that we need to install freeBOOT first but I read system_over_ride2006's post as "you don't need a new freeBOOT if you run this installer"

Zak you need to be running 12611 to install dash launch for 12611. And yeah, between the new patch set from fbbuild (which tells kernel the drive doesn't support it) and the priv filter in dash launch (which tells xam the xex doesn't support it) hopefully games that support "AP25" can run from wherever.

Obviously you need 12611 installed but I was wondering if Dashlaunch alone is enough to enable the patch "which tells kernel the drive doesn't support it [AP2.5]". In my case I installed using fbbuild v0.1 and was wondering if installing the new Dash Launch (so fbbuild v0.1 + Dash Launch V2.06) results in the same NAND state as using fbbuild v0.11.

I'm confused....If I run this will it update my fbbuildto 0.11 or do I need to reflash my JTAG?

I originaly updated and flashed my console to 12611 using easyfreeboot and found that i still had problems loading AC:B, the dashlaunch 2.05 update fixed that. Read reports that Bestpigs flasher didnt require any additional patches and would load the game with out a problem so I reflashed to test it out and it worked perfectly. Since reflashing I reapplied dashlaunch and updated to 2.06 and all is working perfectly

Many thanks to c0z for his excellent work and really fast updates for the scene

Havent used my JTAG for months. Today I updated to latest dash with freeboot.
Now I installed Dash Launch and my controller does not work anymore. Didnt find any solution with google so I tought I ask if there is something I didnt do properly or so?

You'll need to be more specific.

If I try to re-pair my controller, green lights does circle in xbox and controller but xbox cant find my controller.
I can't do anything on nxe dash or xex loader.

install instructions say to place launch.ini where you want.

Ive never used dashlaunch before, not sure where to put it. or what it even is or does

thanks

" note that Right Bumper is ALWAYS default to return NXE" (taken from "info_launch.ini")"

seems like that is broken on dashlaunch 2.06 (xenon 360 - had no problems using dashlaunch 2.05)

Apart from that, great program!

I'd like to know the answer to this as well.

Does fbbuild v0.1 + DL v2.06 = fbbuild v0.11 + DL v2.06?

Right now I have fbbuild v0.1 + DL v2.05

I take it that it wasn't a problem before you installed this, but had the new freeboot working? Usually indicates a keyvault issue when your controller can't sync.

Read post #13 in this thread.

Broken from where? It's working fine here... but I doubt I've tried all paths myself. Keep in mind dash launch only monitors the controller sync'd to the top left quadrant.

fbbuild 0.11 and Dash Launch 2.06 still hangs on Fable 3 booting from internal HDD ripped from disc. GOD container still works.

I can confirm this too

Controller was working ok before Dash Launch install. I updated back to nand I had before Dash Launch install and controller is working fine again.

some say it does some says it doesnt,on xbox360iso forums.
I had gone through dumping-rebuilding with FreeBOOT Toolbox 0.04 Maker v2.6 to include fbBuild 0.11 patches then Re-flashing with flash360.

IF dashlaunch 2.06 does fbBuild upgrading %100 then I wont go through those painful steps again,please someone with knowledge shed some light upon this matter

Dashlaunch 2.06 fails to return to NXE when holding the right bumper on the 360 controller (synced to slot1, top left).



Thx for trying to help, any comments are welcome!
The problem remains however and the 360 controller is synced as controller#1 just as before (top left on the ring).

I have now reflashed on yet another 360, this time a Falcon, and experience exactly the same problem as on the Xenon 360 - Dashlaunch 2.06 fails to launch NXE when holding the right bumper on the 360 controller.

Q: What happens when holding the right bumper and selecting "xbox dashboard"?
A: Boots freestyle 1.20 (default dash). This also happens when not holding the right bumper or when booting the 360.

Q:Where does it happen?
A: Everywhere except when using the the guide button on the 360, selecting the "settings tab" and thenselecting "system settings" - that is the ONLY way that I can go back to NXE (when having my usb hdd plugged in).

This problem didn't exist for me on dashlaunch 2.05 - there I could e.g. just push the guide botton and just hold the right bumber and select "xbox dashboard" to get back to NXE (which would be the preferred way for me in 2.06 also if I had the choise).

I used the same 9199 flashdump that i used when first creating the 12611 dash when creating my fbBuild 0.11 firmware. I flashed the same way (updflash.bin on usb using xellous). After booting I re-applied the basic settings (country settings etc) as was necessary on the Kincet dash. Turned of 360, plugged in my usb hdd, turned back on, booted freestyle 1.20 (default dash) and installed the "dashlaunch 2.06" patches using freestyle 1.20.

My launch.ini on my usb hdd looks like this:

[QuickLaunchButtons]
BUT_X = Usb:\Freestyle\FreestyleDash.xex
Default = Hdd:\Content\0000000000000000\C0DE9999\00007000\freestyle-usb


[Settings]
nxemini = true
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true


Have also tried the following with the same result:

[QuickLaunchButtons]
BUT_X = Usb:\Freestyle\FreestyleDash.xex
Default = Usb:\Freestyle\FreestyleDash.xex


[Settings]
nxemini = true
;have also tried with nxemini = false
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true

Have also tried the following with the same result (original 2.05 dashlaunch settings)

[QuickLaunchButtons]
BUT_X = Usb:\Freestyle\FreestyleDash.xex
Default = Hdd:\Content\0000000000000000\C0DE9999\00007000\freestyle-usb
[Settings]
nxemini = true
pingpatch = true



(there is another dude also that have reported this problem, see last page on the dashlaunch 2.05 forum thread)

I had a problem sort of like this, what I did to fix it was went to the auto boot settings in the console and it was on disc which was causing some clash i think. When I put it back to dashboard it wrked fine.

Stupid question. I'm using the NXE dash, nothing custom. I recently used the easy gui freebooter to update to 12611. Couldn't get bestpig's app to work for me (still not sure why).

If I run XexMenu, navigate to the installer for dashlaunch 2.06 and run it should I be able to bypass AP2.5? Will my JTAG boot differently or anything? I'm just looking to keep the stock NXE/kinect dash.

Sorry if this sounds stupid but I'm trying to figure out exactly what Dash Launch is and how it affects the 360 before I start messing around.

Yes if you install dashlaunch everything will stay the same and you will bypass AP 2.5 games to date.

Dashlaunch has a file called launch.ini which you can edit so that when holding different buttons during the 360 launch it will load specified .xex files.

s_0 I always get consistent results... if I hold RB like it says in the readme, but elsewhere

That is for the miniblade inside of nxe, but if I do the same from FSD for example, press guide to bring up miniblade, press Y to go to dash, select yes, press A and THEN push and hold RB. It sounds like you are holding it throughout that process? Any rate, I don't see any code around this that has been changed at all.

Popple thanks, I hadn't even considered that autoboot dvd issue could be related.

pudink pay attention to the installer and the release notes... it updates freeboot patches for you if you tell it to - and unless you have a jasper16 that is all that is needed to bring your current image in line with what fbbuild 0.11 will build.

Jyffe when you installed it via xex, did it detect the correct console model based on what you told fbbuild to create when it offered to update patches? Did you try installing it but skipping the patch update to see if it is dash launch or the new patch set causing the issue?

That clears it up for me, thanks. I'll try it out tomorrow.

Hi

I have found a strange bug with dash launch 2.06.

I use ping limit and mojobojo content unlock. No button remap, default = (for nxe direct boot)

After flash, the console shutdown. When back to NXE the first time, the console shutdown after 1 minute. If i power up, sometime, boot ok, but shutdown after 1 minute, or Error 79

The hard drive is internal, 2,5" official, and fresh (buyed 2 days ago)

launch.ini is in root of internal hdd

QUOTE

[QuickLaunchButtons]
Default =
[Settings]
pingpatch = true
contpatch = true

Sorry, the problem is not with dash launch. I reflashed nand builded with fbbuild 0.11, without installing dash launch, and the problem is always here. So, i wait in the dash to see if it's the update from fbbuild 0.1 > 0.11

So I installed Dashlaunch without issues and AP 2.5 is bypassed. Everything works OK however when I try to run XeXMenu 1.1 my JTAG Falcon hangs... Any suggestions?

Plug in a usb drive in one of the front usb port and then try xexmenu. If that works rename the games folder on your hard drive to something like "xbox 360 games". Xexmenu has a bug that renaming the games folder fixes.

Worked, thanks! Why does the console insist on telling me I need to connect to Live to retrieve an update whenever I sign in with any profiel, Live or offline?

XBOX 1 compatibility seems to have dropped off with this release. (Tested using original XBOX1 DVDs)


It partially worked with dash_launch_v2.05_for_12611 As I got passed the XBOX1 logo and it let me into the options for HALO 2 some FMV played and then it would bomb out again.

I then installed dash_launch_v2.06_for_12611 and no more XBOX1, Bombs out to the original dash stating that family settings are preventing the game from being played, even though they are disabled on my system.


Can anyone else confirm this or maybe suggest a workround?


Cheers


StalkS

I also have the family settings problem, but without dash launch
Certain game just show : hey, you have to enter the unlock code!

When you know i set all game rate accepted

StalkS: you're going to have to look elsewhere for the problem, I just played through the entire opening sequence and tutorial of halo2 using the hacked emu files and a burned disk.


Is it saying "you need to connect to live", or is it saying "to be able to connect to live the console needs to create some data"? Either way, all it's telling you is it wants to generate the data that is used to auth with live, pull your network cable and say yes and you won't see it again.

cory1492 Thanks for the confirmation. Appreciate it. I'll head over to XBins to get my hands on the hacked emu files. Should I be looking for any in particular?

Is weird though flashed back to 2.05 and it worked again?!?!

Cheers

All good!! Used "xb1_5829_nov_2007-hacked" and XBOX1 is backup and running! Thanks again!


StalkS

After install of DL v2.06 I have no network (no IP) anymore and the box didn't recognize the USB hdd!

Any idea?


my launch.ini:


additional:
console settings/startup and shutdown/
"Start xbox dashboard" is enabled!

If I renamed the launch.ini it starts NXE, but there is NO IP ADDRESS too.

I cannot get the regionspoof to work, its true in ini. Am I doing it right by selecting game then immediately holding RB? Playing PAL Unleashed 2 game on NTSC console all I get is black screen.

My problem was with the USB HDD case (mobilrack).
Sadly with the old xbreboot it was working as it should, but with the new freebooter not.

(in the meantime with my PC it works great!)

Keksz: do you know if it worked on 8955/9199 or just xbr/8498? IIRC they messed with USB devices in a big way in 9199.

Yeah, its in there and worked - tested with quantum theory. You may have to set the region spoof to a specific region if the game is using the kernel function to get the console region instead of going with the default one (0x7FFF) - in this case it is up to the developer if/how they want to use this region check.

edit:/ just got a PM and want to clarify something, fb 0.1 had patches ported from the last 9199 dash launch release, including jasper big block memory unit no-corruption patch. Every release from dash launch and fbbuild for 12611 has been safe to use NAND memory unit - I've even tested this myself, filling and formatting the 212M NAND MU on my jasper 256 4 times and shutting down and booting each time with no issues.

cory1492: I had XBR 8955 before that, and the usb mobil rack with the SAMSUNG SATA 500gb worked...


It's a Spire USB mobilrack, but maybe the HDD inside is the problem?!
Samsung SATA 250GB and 500GB

I read about a guy who tried 3 HDDs external and none was working with Freeboot!


And here is a link:
http://forums.xbox-scene.com/lofiversion/i...hp/t713785.html

That guy wrote that the non-JTAG-ed box wasn't also be able to recognize his HDDs...
Maybe M$ is messing arround with "us", against piracy??