BL4K3Y

Download the update from here, make sure your Kinect sensor is plugged in and try the update again.

As salford gunstar said, update your JTAG/glitch image to 16203 and install DashLaunch 3.07 and FSD again.

You can build an XeBuild image with temperature thresholds in place.

From what I understand, you've already installed Avatar data and then added your Kinect sensor at a later date/time. Accept the update - it should only install the required files for Kinect to operate.

That's true, but pressing Y and holding RB will take you straight back to Metro . OP: You can also boot straight in to Metro when you power the console on by holding RB just the same.

Which message do you get on screen?

Send me your NAND dump and I will build an image for you to try.

Try writing it back with XeLL again (it will remap the bad blocks for you). Your stock NAND will boot fine, even with bad blocks because a retail/stock NAND will take care of them automatically.

VitaminD: Try building your image with "noremap". If bad blocks are remapped in the final image and you write it with XeLL, those bad blocks will be remapped again.

If you use FSD, adjust the fan speed. The only real way to prevent RROD is to play on the console less often lol. Which part of the tutorial don't you understand?

You can enable the "nohdmiwait" patch before building your glitch image. This will skip waiting for the HDMI handshake on boot up.

I'm sure the limit is 32GB now. FSD will see the full size of the drive .

Why are you running a 16203 update on a console running dashboard version 16202? More to the point, why didn't you build a 16203 JTAG/glitch image?

You need to run the official 16203 system update. I posted a tutorial here.

Is there something wrong with LiNK?

XBOX1 emulator files must go on an internal/FATX drive (you can format an external HDD to FATX if you like). The HDDX partition (or Partition 2) will not be seen from other locations.

Are they saved in a "Screenshots" folder (in the F3 folder)?

To be fair, a JTAG console should have eFUSEs protected.

You don't need to enable/disable XBL access (a JTAG/RGH system shouldn't "talk" to M$ servers anyway). I suggest you make sure the console has been assigned a valid IP address and once valid IP settings have been set, FSD should automatically have internet access.

Just enable liveblock in DashLaunch (liveblock = true), but keep livestrong disabled which will still allow FSD to grab cover art and backgrounds.

You should update DashLaunch to v3.07 and also update to the latest version of F3. You can "hide" duplicate entries - simply press "Y" on a duplicate entry and move it to "No Section".

I'm sure Party Buffalo Drive Explorer has an option to create an image from a FATX device. Please correct me if I am wrong.

The J-Runner PDF explains everything. J-Runner supports the Xecuter DemoN 100% and has no issues with reading or writing .

Do you realise that J-Runner gives you the option to download dashboard/kernel files? Use "Add Dash" from the dashboard version drop-down list in J-Runner.

Write the image using J-Runner (connect a Micro USB cable from your PC/laptop to your DemoN). It should take no longer than 30 seconds to write a 16MB NAND image.