BL4K3Y

The DashLaunch "contpatch" option will also do this, but it has been known to cause problems. XM360 works great and it will unlock DLC/XBLA titles without issue .

Windows doesn't support FATX partitions by default, but I'm sure that you can use Party Buffalo Drive explorer to make an image of the whole drive.

DLC must go on an internal or FATX HDD. If your pen drive is formatted to FATX, you can put DLC on it.

FSD will download every available Title Update for a game. You only need to activate the latest - older Title Updates can be removed. When FSD downloads them, it will put them in the correct folder (Cache or Content0000000000000000Media-ID000B0000). This means that you don't need to download Title Updates again when a new version of FSD is used.

I find that installing/ripping them from the original discs works 100% of the time. If you "install" them with Metro, use NXE2GOD to patch them so that they can be played without discs.

I let F3 handle cover art. When you set the correct path and scan depth, F3 will automatically download cover art (make sure livestrong = false in launch.ini).

I've just set this skin and I love it. Great work!

Do you have a way to read/write to the NAND? I strongly suggest writing the stock NAND image back to check that it boots. If you can confirm that it does, you can build a clean glitch image and write that to the console.

If you are in the UK, I'm sure I could get it going for you.

So you're getting E79 on an RGH Trinity/Corona? Does the stock NAND boot fine? You can't just download a NAND image and write it to your console because the CPU key wouldn't be correct to decrypt the key vault.

Use GOD2ISO to convert it back in to an ISO and then use exiso to extract it.

Extract the ISO to a folder on your HDD (like a JTAG rip). I'm sure I recall the game having issues when it was in GoD format.

Check the kernel version in System Settings (the OP explains this).

Why not 16203?

You can launch GoD games with FSD. As I said, set a path to your "Games" folder (even if it has GoD packages in there) and they will appear under the "XBOX 360 Games" tab in FSD. The NXE/Metro dashboard is very basic compare to FSD .

By default, NXE/GoD containers go in Content0000000000000000 on an internal HDD, but they can be placed anywhere when using FSD (as long as a path and scan depth is set). You can format your external HDD to FATX using the console, but as you said, you will be restricted to the amount of space you can use.

A JTAG shouldn't ever go on XBL.

No problem, I'm happy to help .

Use the update feature in F3 or download the latest version and install/transfer it to your console.

I think you are getting confused between a system update and a hacked image. When you update your JTAG/RGH, you build a new image using modified dashboard files (this is what XeBuild, J-Runner and XeBuild GUI use).

You only need 64MB from a BB Jasper. Upload that somewhere and PM me the link.

It's possible. Your console should always be running on the latest JTAG/glitch kernel anyway. I suggest you update it to 16203.

The latest build of F3 should have the "new" HUD.

Did you read this ?

Check that nohud isn't enabled (nohud = true) in launch.ini.