QUOTE(Twis7eD @ Jul 3 2010, 07:09 AM)
I have FreeBOOT v.032, but I don't know if it has the correct patch that has dash launch installed on it. If I run the flash_installer, will it flash dash launch to my NAND or do I have to build a completely new image? Because I have no idea if I have dash launch already installed and I would just prefer to run the flash_installer instead of building a whole new image because I don't have my original NAND.
You shouldn't have to build a new image (especially if you had the nand option checked) And you will have to run the installer at least once or it(dashlaunch) won't be there.
QUOTE(avpdav @ Jul 7 2010, 07:42 AM)
Don't get too excited. I tried to take my Jtag online (after I updated to freeboot) and the second it tried to connect during setup, I got a message saying it was banned for ToS violations. (I wanted to connect it so I could recover my XBL account and get some game updates, but oh well.) Your's could be banned just as fast.
It's always worth saving ur KV (they're in very limited supply and in the future you may be able to do some very cool things that have nothing to do with MW2 or lobbys) Either way it's important to have Xbox Live blocked in ur settings as once it's banned (only takes an hour or 3) it will modify ur nand (not as big concern nowadays) and if it keeps trying to log on post fixing ur nand u r console will go on untrusted list and that will cause u issues with new games that have you on their list..(there's a workaround but it's a massive pain in the proverbial)
QUOTE(holyjewsus @ Jul 7 2010, 01:17 PM)
anyone have any experience with this, dash launch seems to only boot with my ini, to fsd, when launch.xex is on my usb disk. I have it in the nand installed with flash_installer as well, but that doesnt seem to work. I have the .ini everywhere.
Make sure when you do ur build you have nand checked, It will boot from nand, but without a drive of some description (with the actual app - fsd) and an accompaning .ini/and FSD to boot from it will default to NXE or worse.
It's always better to have a seperate .ini etc.. for each drive as dashlaunch doesn't like to traverse drives.
I've also noticed that dashlaunch DOESN't Mount UsbMU's properly like it claims to they just default to USB0 etc.. and having one plugged-in (even after boot) can stuff up ur .ini after the UsbMu gets mounted as a normal USB and enumerates the one ur trying to boot off. Doh'
Hope this helps/Dan
Edited by danthaman673, 22 July 2010 - 07:58 AM.