FIXED Not booting to FSD after 16547 system update?

[codswallop]

Our xbox 360 slim (trinity) had a TX DemoN installed a while back (by myself) and has worked until now without any issues. Over time I've been able to apply system updates (required for xbox live access via xbox NAND only) and each time have used Jrunner to apply the corresponding build image to the DemoN Nand.


I've just however updated to the 16547 system update (works fine from XBOX Nand) but I'm now unable to get Demon Nand to boot into FSD, (I've tried using J-runner and XEBuild programs). In each case the update image is applied but it fails to then boot into FSD (goes to the XBOX dash instead).


Can anyone steer me in the right direction to resolve this? I suspect I need to do some additional config as something has changed with the 16547 update - but I'm not clear on what exactly (LDV's ?)


Many Thanks.

 

[BL4K3Y]

You need to install DashLaunch or build the image with DashLaunch patches included.

 

[codswallop]

Thanks Bl4k3y,

So within Jrunner (latest version that supports 16547), under the dashlaunch tab I have selected "Use Dashlaunch" and "Include Dashlaunch.ini" - I've also selected "liveblock" and created the ini file. I select the xbox NAND image dumped previously and then create the XEBuild image (XEbuild options - 16547, Trinity, RGH2).

But still getting the same issue after writing this image to the DemoN Nand?

 

[BL4K3Y]

You need to set the default path to FSD.

For example: Default = Hdd:\FSD\default.xex.

 

[xzanox]

I think you don't have dashlaunch 3.11 am I correct. If so, download dashlaunch 3.11, copy the installer from that map to your xbox hdd (I.e FTP), run xex menu from original dashboard (games it should be) and launch the installer. It will ask you to update, click yes and after this close dashlaunch. It will start again to fsd after a restart.

Had the same a few days ago. Update went fine, but kept booting into normal dash. Found out that I didn't run dashlaunch 3.11

 

[codswallop]

Issue resolved! It was actually my external USB disk that seems to have failed (or at least the caddy it sits in had). Swapped into a new caddy and it is now booting back into FSD.

Thanks for your input, but seems to have been a h/w fault in this case.

 

[xzanox]

Nice.