Well I went a head and flashed my 360 with freeboot plus dash launch v1.0 using freeBOOT ToolBox v2.4 to build the nand.Last time I flashed freeboot I used flash 360 and selected the flash raw and it worked great but not this time. My 360 will only boot xellous so my question is can I flash my nand using just xellous,I really don't want to solder the lpt back on to reflash.
1) Yes. You can flash with Xellous. If I'm not mistaken Redline wrote both the Xellous flash code and the Flash 360 code. 2) If the flash didn't work, it was likely a bad build. Rebuild it manually and give it a go. -hl718
Well Im at a lost right now,I reflashed a few times and when its done I turn off then turn back on using the power button and it boots back to xellous.
Well I made a new freeboot without using the dash launch v1.0 and flashed with xellous and it works now.
Sounds like whatever you were doing with dash launch was corrupting the image. How were you building? -hl718
Ok if you can still boot xellous which it says you can, then take your new nand image and name it updflash.bin put it on a usb stick start xellous and it will flash itself. No need to hook up the lpt or usb flashers. Hawk
I was testing out the new freeBOOT ToolBox v2.4,it seems other people have had the same problem.Im going to mess with it some more,I might know what the problem is.
From my personal experience, these hacks (stuff like freeboot and dash launch) aways work the best when you sit down, study their documentation and do the procedures step by step on your own. This is a personal comment of mine about the toolbox app, slightly unrelated to the thread, though: :lol: I have nothing against BestPig or his tool, it's just that this "scene" has became too much spoon-feeding friendly which brings a lot of bottom-feeders atop plus a whole lot of new problems to the table. I believe that making hacks too easy is a HORRIBLE idea as it only help the pirates out. Therefore, I don't believe that tools like this toolbox should exist... Back on topic, I'm also curious about what made it fail.
Well I got it working but still have a little problem. I can boot Freestyle dash on boot but when I return to the dashboard it kicks me to NXE. I had my ini originally like this. LUSB:\Freestyle Dash\default.xex; So made a new one like this. [QuickLaunchButtons] Default = LUSB:\Freestyle Dash\default.xex BUT_X = LUSB:\emulators\Snes\default.xex Now when I use this one I can't even boot Freestyle on boot,anyone know what Im doing wrong.
TOOLBOX probably made it fail! That app was so buggy it was constantly being worked on all while iBuild was doing just fine, its ridulous cuz iBuild was actually easier to use than Toolbox? Don't edit the .ini just leave it as is and use only for autoloading to the dashboard of your choice, the FSD from the internal hard drive which has worked for me great, but yeah whenever I edit that .ini to point at another dash it would just fail and fall back to NXE not sure why prob just cuz it wasn't saved in a proper format but I just couldn't be arsed to play with FSD some more since it'd just reindex and ruin the Thumbnail images at boot if it was ever set to use \ launch from USB only, everytime the kids powered on the 360 without the USB HDD in it'd corrupt the index file since FSD is set to index and search at boot every time, if they'd just add a option to disable content scanning at every boot then maybe I'd still use it but so far I've done great with just NXE and ISO2GOD ;-) If your wanting to just add them to Quick Launch or the guide button there's a simpler way and no need for these .ini files in the root of the HDD but the files for this setup are in dash launch or the 1.09 release of FSD Just follow the readme instructions, theres 2 files that let you set this up but one is for USB and another is for HDD only.
here's mine, at first I thought you were missing semicolons, but I guess they detect the end of the line differently now because its working for me. Code: [QuickLaunchButtons] BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558 Default = LHdd:\Freestyle\FreestyleDash.xex you might someday be glad if you set another shortcut to xexmenu on the off chance that you mess up freestyle's skins not that I know from personal experience. when you upgraded dashlaunch did you rebuild your nand image with the newer patches? did you use the installer to put the new launch.xex and your launch.ini in flash, or do you have them in the root of your hdd/usb-drive? Edit: Mine will go back to NXE occasionally anyway but after running my dash again it seems to sort its self out
