QUOTE(Mr.RedRing @ Jun 30 2010, 05:29 AM)

I guess incorrectly :/ The first time I upgraded to Freeboot I used Freeboot Toolbox, entered my CPU Key, selected Xenon as the mobo, and updflash.bin as the file type. Then clicked generate Freeboot, selected my 7371.bin and got my freeboot dash. Did I do something wrong? Now I get an error saying something about my current nand being zeropaired in Flash360 :/
Ignore the warning as it doesn't apply to 9199 freeboot image (KV is in differnt place)
And as the post above says and as I said earlier in this same thread twice: USE THE NAND OPTION!!!
The rest of the info is in this thread if u need it...
QUOTE(philbee @ Jun 30 2010, 06:22 AM)

hi guys,
ive been suffering with this all day, ive used best pig to create freeboot from original nand dump, i selected the custom mode and usde the patch for my falcon from the dashlaunch installer folder, bestpig says freeboot image was created successfully. Ive flashed to nand using flash360. I installed the patch to the root of the xbox hdd and then ran dashlaunch installer default.xex, flashed launch.xex and launch.ini to the nand. Now when i boot the xbox it goes straight to the nxe dash, ive tried pressing B button or X button on startup but it always goes to the nxe dash. ive tried mw2 on xlink with the latest updates but to no avail. Ive modified my launch.ini to try and get it to boot into fsd but its not working. any ideas?
my launch.ini is
[QuickLaunchButtons]
Default = LHdd1:\Freestyle\FreestyleDash.xex
BUT_X = LHdd1:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
the FreestyleDash.xex is located in the Freestyle folder on the root of my xbox hdd.
Is your .ini file in UTF-8

*also in my earlier posts* (ie; UTF-8 saved in notepad as opposed to ACSII for those who don't know)
Sorry to be narcy but I've been getting repitive questions on this on xlink etc.. all night- The offical AGM tut will be out tommorow on the site in my sig (and on XS later if it hasn't already been done)
PS: If you can't get dashlaunch to launch then you can't be sure the patch has applied - Get that going 1st then put ur patch on the hdd root etc..
PPS: Oh yeah : I've heard that the .ini can be case sensitive also - just either cut and paste ur paths or use the sample and make sure everythings where it's meant 2b