BL4K3Y

They are. I have a wireless controller here that came with a 4GB Trinity and it works perfectly fine with phat and slim consoles.

An RF board is very simple to replace - Google or YouTube (look for "XBOX 360 Replace RF Board" or something) should be able to help you. You have another issue elsewhere because the wired controller is having issues as well and I think that it is an issue with the USB ports (or at least one of them). Connect a USB stick (a spare one preferably) and format it for XBOX 360 storage - do you have issues with this? Are you connecting the wired controller to one of the front USB ports on the console?

You downloaded the game? It's not for me to really say here, but that's piracy my friend. Rip your original retail disc(s) and you won't have any issues .

Is the latest version of XexTool (v6.3) present in the ISO2GOD directory? If I remember correctly, ISO2GOD won't work with "modified" XBOX1 .xbe files.

Responses for what and why are you scared?

Did you pay for phat RGH2, Xenon RGH or Corona RGH?Did you pay for any BIOS files back in the XBOX1 days?Nobody apart from Team Xecuter knows what the hack consists of and for all we know, it could be done using cheap parts like the original JTAG hack was (diodes and some wire).

This is true and you will find that 4GB of storage space will get filled pretty quickly, especially when you are downloading box art and such.

You never write anything to the XBOX 360 NAND.You can put any glitch image (kernel version) on the DemoN's NAND.Nothing has ever been proved, but it's not wise to use the same HDD for XBL and RGH - an external HDD is recommended (or a separate internal HDD) for RGH.

If you'd like the hardware installing, I can do it for you. If you are interested, send me a PM and I will give you a quote.

Are you both running the same Title Update?

You can "clone" your LIVE profile. As long as you don't take it back on XBL once you've used it on the RGH (glitch) NAND, there won't be any issues.

I don't know for certain, but I believe it involves the CR3 Pro .

Why don't you just transfer your existing launch.ini file across to the new HDD? Place FSD in the same directory as it was on the old HDD and it will continue to load when the console does.

Instant glitching on ALL phats lol. I take it you've not had the misfortune to come across a Falcon RGH2 or Zephyr RGH/RGH2 unit yet? Anyone who has will know exactly what I'm talking about lol.

I've updated the OP to explain this - thanks JPizzle .

What do you mean by "Q2 error"?

I didn't think that one through lol.

The link in the OP will give you the latest available system update (at this time of writing, that is 16202).

Can the console boot to XeLL? Are you certain that you have a JTAG/glitch kernel on there? Try the GOD installer - place the F30000F3 folder in Content0000000000000000 and run it from the Games tab in Metro.

Update your JTAG/glitch image to 16202, install DashLaunch 3.05 and see if the issue remains.

Write your stock NAND dump back to the console and check that it boots. If you can verify that it does, build a new JTAG image (16202) and write that to the console using RawFlash or a hardware flasher.

You should always keep your JTAG/RGH kernel updated. You can use older versions if you like, but new kernel versions include changes, bug fixes, additions etc.

Are you using the correct system update?

That log looks fine. I'm assuming your NAND dump doesn't have any bad blocks?

Can you upload a copy of the log to Pastebin and link it here please.