BL4K3Y

Your version of DashLaunch is old - install the latest version (3.07). Once that is done, check that you set a path to your games in F3 (don't forget to set the scan depth).

Run the DashLaunch v3.07 installer. Each option has a description with it so you know what you are enabling/disabling.

If the console is already glitched, the latest DashLaunch installer will display the CPU key.

For phat consoles on dashboard version 15572+, you simply write one of TX's "new" ECC images to your console's NAND (they are named for each board) and use a standard CoolRunner (wired up for RGH2) to boot into XeLL and get the CPU key. Once you have the CPU key, you treat the console as a regular RGH2 install. J-Runner was updated recently to include these new ECC files.

Use XexTool.

Zephyr RGH2 is a real pain in the ass at the best of times. What have you tried so far? Which timing file are you using? Can you post some images of the wiring/routing please.

Great tut JP - very n00b friendly and easy to follow !

Party Buffalo Drive Explorer works great .

Apply some pressure to the HANA as you boot the console. If the console boots whilst doing this, reflow or reball the HANA and if the console still shows E74, reflow or reball the GPU.

Since you posted this in the F3 section, one can only assume that you have a JTAG/RGH system. FSD/F3 will recognise FATX drives above 32GB.

Why can't you update the console's JTAG image?

I suggest you use the original NAND to build a glitch image. You can use a donor NAND, but only if you know how to encrypt the key vault with another CPU key (from the console you have). This is probably why you are getting the Christmas lights .

As far as I remember, demos go in 000D0000. I don't think you can create "custom" tabs for F3 though, but I could be wrong.

Try flushing the DNS cache and resetting your router.

30ms is the limit on retail systems.The DashLaunch patch overrides that allowing you to play without issue, but it also means that JTAG/RGH users can't play system link games with retail consoles (for example, LAN parties).

Have you tried installing the game to your HDD using Metro (I think you press "Y" on the game's tab and select "Install Game" or something)? Once you've done this and it has installed successfully, you will need to run NXE2GOD so that it can be patched and played without the original game disc in the drive.

Don't forget to add "pingpatch = true" in launch.ini (I believe it is disabled if the entry isn't present in the INI file).

You do realise that F3 can do everything XeXMenu can do and more?

XeBuild allows you to modify temperatures, thresholds, fan speeds and such, but I don't think it allows us to change the ROL colour based on the current system temperature.

Setting AutoFake to TRUE in launch.ini will enable/disable it when required .

Not all XBOX 1 games will work with the hacked emulator files. With that said, I can confirm that the PAL version of the game works fine. Which emulator files did you use?

Try clearing the database and start again. Add the correct path, set the relevant scan depth, save and reboot the console.

This is true for the "standard" Corona RGH, but when using the DGX, you should get video output. If you don't get video output for XeLL and you need the CPU key, simply use J-Runner's COM monitor or HTTP to get the CPU key once the DBG LED on the CR/DGX stops blinking.

The XBOX 360 won't see NTFS drives/partitions. FSD will see FAT32 drives, but the NXE/Metro dashboard will only see those formatted as FATX (the XBOX file system). OP: You can tell if FSD has recognised the HDD when you click the right thumb stick - you will see available drives and free space at the top right-hand side of your screen.

Does FSD see the HDD? The NXE/Metro dashboard will not see a FAT32-formatted HDD.