:facepalm: it was all going so well right up to the point when you suggested that video, there is no "pro way" to use a heat gun, no matter how you use it it's still going to do more damage than good, but apart from that you are correct

It is cheaper then getting it reballed which could cost $50 but is not certain to always work.

My friend asked me to fix his jtag for him after he got E79.he had been using the xbox for a while and then it got error for no reason,I replaced the diodes and still no go.Just wondering if it could be a bad NAND,if not what could it be?(there is no hdd plugged into the console)

If it is HDMI, e79 occurs randomly and can be fixed with just rebooting

It can also be a HDD issue

Take a pic of your soldering though

hey i need mw2 help i need packfile1.pak can u aim me it or pm it to me aim krispycreammods
thanks bro last file i need

Hey I just installed world at war onto my jtag then put the patch for "THE NEW W@W Infectable Mod Menu v3". then i went and launched the default_mp.xex and got a message saying disc is unreadable. could you help?

ps. I am reinstalling now hoping that will work.

XeXsp0rts wrote Hey I just installed world at war onto my jtag then put the patch for "THE NEW W@W Infectable Mod Menu v3". then i went and launched the default_mp.xex and got a message saying disc is unreadable. could you help?

ps. I am reinstalling now hoping that will work.

What it the patch named because usually it has to be named patch_mp.xex or patch.xex for it to work. And most of the time not always the disk reading error come from the default_mp.xex if you have replaced that then try switching it with the old one that might work.

Ok thank you! I think I fixed it.

Joltz wrote

XeXsp0rts wrote Hey I just installed world at war onto my jtag then put the patch for "THE NEW W@W Infectable Mod Menu v3". then i went and launched the default_mp.xex and got a message saying disc is unreadable. could you help?

ps. I am reinstalling now hoping that will work.

What it the patch named because usually it has to be named patch_mp.xex or patch.xex for it to work. And most of the time not always the disk reading error come from the default_mp.xex if you have replaced that then try switching it with the old one that might work.

Your completly wrong.
The fastfile always has to be named patch_mp.ff

Man0nTheMoon wrote
Your completly wrong.
The fastfile always has to be named patch_mp.ff

Cant be completely wrong if he fixed his problem

All the files have to be named correctly except the Xex. It can be named whatever you want it to be