Print

[omegastar]

Nice

This post has been edited by omegastar: Jun 30 2010, 01:25 PM

[Julets]

I finally got this installed. Worked fine, but when I turned the xbox off and back on, now it just keeps rebooting at dash load (holding RB to get to NXE doesn't work either). Is it that it is looking for a .xex it can't find and just panics? I have a Cygnos v2, the OEM nand that doesn't have dashlaunch 1.0 doesn't do this, but this one does, so I know it's dashlaunch related.

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.

[Julets]

I'm starting to think this is a Cygnos v2 problem. It just keeps rebooting once it tries to load the dash. I've now got iBuilding working to the point this 2.4 toolbox maker thing is...which is rebooting. So iBuild and this AiO app are not working. I did replace the xell-2f.bin with the cygnos using both applications, didn't help either way. I have flashed launch.xex and the .ini to the flash. It did work once, but I can't remember if I rebooted (think i started and exited a game).

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

[Julets]

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.

[sthetix]

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..

[Julets]

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.

[antisniperspy]

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.

[hfmls]

this is to hard for me, i think i'm gonna pass (IMG:style_emoticons/default/smile.gif)
i really wanted to use always freestyle dash but i dont want to screw my xbox360

[danthaman673]

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

[colt45joe]

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

This post has been edited by colt45joe: Jul 18 2010, 11:55 PM

[antisniperspy]

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

[Midnight Tboy]

works no problem for me with launch.xex and .ini on the usb drive.....choosing USB as the option when using Freeboot Toolbox Maker 2.4

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

[flxfxp]

Hello,

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

[flxfxp]

So I went ahead and did it myself:

1. Made a fresh dump with Flash360
2. Downloaded freeBOOT 0.032 ToolBox Maker 2.4
3. Used the Dash Launch NAND option
4. Created the updflash.bin
5. Flashed updflash.bin with Flash360
6. Created launch.ini
7. Put launch.ini in flash_installer and upload that to root of hdd1
8. Run flash_installer\default.xex and update
9. 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

[dschu012]

20% of the time it will launch my default dash and 80% it launch NXE. Usually after playing a game though it will launch the default dash. Any idea's on what I can do to fix this?

This post has been edited by dschu012: Jul 20 2010, 10:23 PM