Print

[sthetix]

This version confirmed not working. I have Jasper 16MB with 7371 original NAND. It gives me error.

[regedit]

"The kv,bin was not decrypted properly. The CPU key does not match the dump"

yes the KV is not mine. Its my friend's jasper512 onto my jasper256 (by bincrypt2 plus some KV modders) but freeboot 0.30 works fine for me (but the profile corruption is a bitch). Freeboot 0.32 kicked my ass with Christmas lights.

Can anyone disable KV checks from the "customize freeboot" option?

This post has been edited by regedit: May 30 2010, 07:59 AM

[360720]

Used original NAND backup, created image fine.

Flashed wth Flash360 and on re-boot, black screen.

[danthaman673]

QUOTE(duey2k @ May 27 2010, 11:16 PM)

after i build the image and with the new version, flash360 exclaims "your current nand is not zeropairred"

i went ahead and flashed it and blank screen, xellous still works and i reflashed my nand backup and everything is working again but i would love to use dashboot...

any help...using A B A in flash360
xexon board, running freeboot .32 xellous 1.0

Yes you will get that, You can ignore it as Flash360 has yet to be updated for FreeBoot (So it might not be a good idea to try to apply patches like DashLaunch 1.0 over an earlier 9199, I think it's safer to rebuild from scratch)

It's not long now before people find cool applications for DashLaunch ;-)



This post has been edited by danthaman673: May 31 2010, 02:03 AM

[cirkator]

QUOTE(360720 @ May 31 2010, 12:15 AM)

Used original NAND backup, created image fine.

Flashed wth Flash360 and on re-boot, black screen.

had the same thing....

what helped me, was to remove the "old" launch.ini & launch.xex from dashlaunch v.0.02.
after i ereased these 2 files from the root of hdd1, i reflashed the freeboot image through xellous and everything worked fine

when it boots just use flash_installer and flash the new launch.ini & launch.xex to nand

not sure if it has something to do with it, but i used the nand option in freeboot toolbox v.2.4


hope it helps

This post has been edited by cirkator: May 31 2010, 02:24 AM

[AlabamaHit]

QUOTE(antisniperspy @ May 28 2010, 11:32 PM)

From the posts I have read there will be no new XBR and if you are playing backups for hdd all you have to do is remove the $TitleUpdate folder. So you really dont need the new freeboot if you dont want.

Cool, so if you remove the titleupdate. THe game will still play? Even though it needs the new dash? Or is that all in that folder..

Only problem I see me running into if that is case. Is the way I install.
I install all my games with NXE, then run nxe2god. So I don't actually have folders. they are data files lol

[aclearersky]

Ok here is what i did and it worked perfect.... I used flash360 to dump my current nand which was xbreboot 3a and then took that file and used it in freeboot toolbox and it worked perfect then i used that image in flash360 and had it not edit keyvault or config. Worked perfect after boot.

[Zorn79]

is there anyway to get an original nand after the console has been jtagged, are you able to get them from other xbox 360's???

Would anyone be able to help me with this if you can get them from another 360, just I don't want to try and solder a nand flasher as my skills are less than adequate.


Regards,


Zorn

[MrMikeJJ]

I've been playing with this, manually build images and have noticed something disturbing.
Using Total Commander to comparing the images created by this in Manually Choosing (Xenon) and Auto Choosing,  the images are different. They are also both different from a manually created image.

Out of interest a manually created image also differs when made with Windows XP and Wine. So I even though it iBuild works in Wine, probably best not to use it just yet.

Anybody has any suggestions why Manually choosing and Auto choosing would produce a different image, when it automatically detects the correct  360 type ? And which would be the "safer" one to use ?

[pink1]

QUOTE(antisniperspy @ May 22 2010, 09:26 PM)

When you build an image it will never be the same as a previos one that you built. There will aways be a difference.

[FrostyWolf]

So, here are my steps:

Open Freeboot toolbox v2.4
put in my CPU Key
Uncheck Auto detect
Check Jasper 256
Pick USB for Dash Launch

Generate freeboot image

Pick my Nand dump

take the newly created updflash.bin
Flash on to 360 with flash360.

Download DashLaunch 1.0

Edit sample_launch.ini to:

CODE

[QuickLaunchButtons]
Default = LUSb0:\Freestyle\FreestyleDash.xex

Save sample_launch.ini as launch.ini
Copy launch.ini to root of USB

Also did this:

QUOTE

In the dashlaunch folder, you
    will see a folder named flash_installer, connect to your xbox via ftp with
    the option of your choosing, and upload this folder to the root of your
    xbox(optional, just know where you uploaded it to).  Open the file manager
    and navigate to that folder and launch the default.xex(NOT the launch.xex),
    follow the on screen prompts and it will install launch.xex file for you.

Start xbox. Boots to NXE.
Load FSD, start game, launch miniblades, hit y. Boots to NXE.

What am I forgetting/missing here?  Even when I don't edit the samplelaunch at all except to name it launch.ini, I still only get NXE.

This post has been edited by FrostyWolf: Jun 6 2010, 07:14 AM

[omegastar]

QUOTE(FrostyWolf @ Jun 6 2010, 01:44 AM)

So, here are my steps:

Open Freeboot toolbox v2.4
put in my CPU Key
Uncheck Auto detect
Check Jasper 256
Pick USB for Dash Launch

Generate freeboot image

Pick my Nand dump

take the newly created updflash.bin
Flash on to 360 with flash360.

Download DashLaunch 1.0

Edit sample_launch.ini to:

CODE

[QuickLaunchButtons]
Default = LUSb0:\Freestyle\FreestyleDash.xex

Save sample_launch.ini as launch.ini
Copy launch.ini to root of USB

Also did this:
Start xbox. Boots to NXE.
Load FSD, start game, launch miniblades, hit y. Boots to NXE.

What am I forgetting/missing here?  Even when I don't edit the samplelaunch at all except to name it launch.ini, I still only get NXE.

You need to put the launch.xex on the root of the usb. The option in the toolbox is for where the launch.xex goes, the ini can be any where nand, usb, hdd because it will search for it in all locations no matter where the xex is.

[FrostyWolf]

QUOTE(omegastar @ Jun 6 2010, 07:49 AM)

You need to put the launch.xex on the root of the usb. The option in the toolbox is for where the launch.xex goes, the ini can be any where nand, usb, hdd because it will search for it in all locations no matter where the xex is.

Sorry, I tried this also, and still had no luck.  Launch.xex and launch.ini on root of HDD and USB0, just for kicks.  No luck at all.

Reflashed, using the HDD option instead of the USB option.
Reboot, boots to black screen.
Suppress urge to crawl into corner and cry.
boot with eject button, reflash back to just Freeboot .32 with no dashlaunch patch.

Reflash again with nand selected.
Run launch installer, everything works perfect.

Now, I don't know what to make of this.  I had no luck with the USB option, no matter where i put the two files.
When I pick the HDD option, the 360 doesnt even boot anymore.
And when I pick the nand option, it all works perfect.

Now, that doesnt make sense...AT ALL.  First of all, I don't even understand why toolbox HAS a USB/HDD/NAND option.  Toolbox shouldn't be doing anything differently with the image for any of those, since in the readme for DashLaunch the instructions for compiling the NAND are the except SAME for all three options, the only difference is the next step, which is where to put the launch.ini.  Installing with launchinstaller is the same for all three steps also.

Tool box shouldn't be doing ANYTHING diffrent with those three options.  It should just compile with DashLaunch, and then you do one of the following:

1) Put ini file on USB, install xex with launchinstaller.
2) Put ini file on HDD, install xex with launchinstaller.
3) Punt ini file in launchinstaller directory, install both xex and ini with launchinstaller.

[danked]

tired my original dump and my XBR3 dump, both boot to a black screen

[danthaman673]

QUOTE(FrostyWolf @ Jun 6 2010, 04:31 PM)

Sorry, I tried this also, and still had no luck.  Launch.xex and launch.ini on root of HDD and USB0, just for kicks.  No luck at all.

Reflashed, using the HDD option instead of the USB option.
Reboot, boots to black screen.
Suppress urge to crawl into corner and cry.
boot with eject button, reflash back to just Freeboot .32 with no dashlaunch patch.

Reflash again with nand selected.
Run launch installer, everything works perfect.

Now, I don't know what to make of this.  I had no luck with the USB option, no matter where i put the two files.
When I pick the HDD option, the 360 doesnt even boot anymore.
And when I pick the nand option, it all works perfect.

Now, that doesnt make sense...AT ALL.  First of all, I don't even understand why toolbox HAS a USB/HDD/NAND option.  Toolbox shouldn't be doing anything differently with the image for any of those, since in the readme for DashLaunch the instructions for compiling the NAND are the except SAME for all three options, the only difference is the next step, which is where to put the launch.ini.  Installing with launchinstaller is the same for all three steps also.

Tool box shouldn't be doing ANYTHING diffrent with those three options.  It should just compile with DashLaunch, and then you do one of the following:

1) Put ini file on USB, install xex with launchinstaller.
2) Put ini file on HDD, install xex with launchinstaller.
3) Punt ini file in launchinstaller directory, install both xex and ini with launchinstaller.

Actually I tried A LOT of different combo's  And I couldn't seem to get it to boot under any circumstance  
Just to complicate things is the 'Nand' Flashing program (I had no problems with the old dashlaunch) It would seem now that my box won't boot with ceratin brands of USB attached (of course my new 500gb is one of these, I'm SURE it didn't have a problem under 8955(XBR3a) and I don't recall it having a problem under  older 9199 builds either , I'm using cygnos v2 and I wonder if dashlaunch has a problem with the way it patches Cygnosv2 SMC ?? I can't think of much else as others don't seem to be having a problem.
I think toolbox as applying dashlaunch patch, When I flashed everything on to the NAND I realised that I would still have to use the Launch.xex,Launch.ini flasher because that would now be the 1st place it looks. I gave up on getting it going for a while. (Also resisting urge to launch xbox through window giving new meaning to dash-launch. Now that I know that thew new version 0.32 has an issue with my USB-drive I will have a much better shot at it .I suspect it(USB problem)  could also be because it uses Xellous instead of Xell..

I'll figure it out and post back here AND do a tut also.