BL4K3Y

Thanks BL4K3Y just wasnt too sure about the common zip folder wether that needed to be changed or not

They are called "common" files for a reason.

They work with any file system version.

I followed this tutorial last time and it worked flawlessly:

 

http://www.realmodscene.com/index.php?/topic/2205-xebuild-freeboot-nand-update-tutorial/

 

Could this be updated or one similar be made so i can follow that tut again. Its just i kinda forgot and would like to follow that tut again. Thanks.

It doesn't need updating.

You simply need to replace 16537 with 16547.

The -f switch specifies the file system version to build your image with.

Swizzy explained how to go back to the stock dashboard.

You can also assign a button to Sfc:dash.xex.

If XeLL doesn't boot with the HDD attached, I suspect that something else may be wrong.

Open up the console and check that everything is connected properly, including the cables for the HDD.

Does the console still boot to XeLL with the hard drive connected?

Have you tested the hard drive in another console?

Is it a phat or slim console?

Do you see an error code on the screen or any red lights on the front of the console?

The game runs fine from the original disc.

I don't know the rules here, but I'm pretty sure piracy isn't supported (and for good reason).

Will that work on a corona?

Yes - 16MB and 4GB.

Forget Flash360 - it's old and out of date.

Use Swizzy's Simple 360 NAND Flasher to update the NAND image.

Just to let you know guys, I have changed the link in the OP temporarily to grab the 16537 update from my DropBox folder.

I have done this because M$ are now pushing update version 16547 (the original link grabs the update directly from M$) and we don't need to use that just yet .

So there is absolutely nothing I can do besides a GPU replacement or a reflow or reball? It seems I caused this by deleting or launching some software, so why isn't it a software issue?

A reflow/reball probably won't fix it because the issue is with the eDRAM on the GPU.

It has nothing to do with you changing anything on the console - it's just a coincidence.

Your issue has nothing to do with XeLL or the JTAG image.

The E74 error is usually caused by bad eDRAM on the GPU.

You need to replace the GPU with a new one.

What are you using to update the NAND?

You can put updflash.bin on a USB stick and update using XeLL or you can use Swizzy's NAND Flasher app.

Swizzy answered your question already.

Why do you need DashLaunch 3.11?

A donor key vault is no good for your console if you want it to boot in a retail state.

The key vault for your console is hashed with your console's CPU key and using a donor KV will cause it to show flashing red/green LEDs (KV hash failure).

If the original NAND or key vault is missing, your only way to get the console going is RGH.

yes but i dont know how to connect xbox to network

You can use LAN (wired) or wireless.

As long as the console's IP address is in the same IP range as your PC/router, things will work fine.

The XBOX 360 "E" models have missing POST_OUT.

You need to remove the heatsink and fit a POST Fix adapter (or use another solution) to get access to POST_1 which is required for the glitch.

My guess is that the person who modified your console didn't apply fresh thermal paste to the XCGPU (the original paste isn't of the best quality) or he/she cleaned it without applying fresh thermal paste.

sorry im not a computer guy so hopefully someone will help me out. What is the 111 files, how do i connect pc to xbox wirelessly because my xbox360 cant connect to internet (dns error)

Did you read the tutorial?

I don't think cover art shows in Metro like it did with NXE.

If you like the Metro interface, there is a Metro skin available for FSD.

To trick the console in to thinking it is connected to XBL, enable FakeLive in DashLaunch.

You can create the Content0000000000000000 folder on an XBOX 360 storage device.

My avatars are back but my kinect still n eeds an update wich does not come????

Run the same update again with the Kinect sensor connected to your console.

Use the latest version of XeBuild to update the dashboard version to 16537.

Once your console has been updated, download the latest version is F3 from this forum.

There isn't a PS2 emulator, but a PSP emulator was recently released (PPSSPP).

The XBOX 360 can only just emulate the PSX at this stage, so I don't think we can expect to see a PS2 emulator any time soon.

Has the console ever been modded before?

Does it boot up with the stock NAND written?

The SMC might be corrupted.

Did this fix the Splinter Cell Blacklist disc swap issue? Just curious.

There was an issue with that game?

FSD handles disc swapping - you can use that or the DashLaunch Disk Swapper plugin, but not both.