Print

[AlkaliV2]

I got a JTAG'ed 360 recently and I loaded up XeXLoader 0.26 and tried using the CopyDVD option.  Worked perfectly for MW2 so I wanted to try Mass Effect.  Worked up until about 87% and then hung on the install with CopyDVD so I reset the console(tried to install it 6 times).  The last time I used Viper360 to finish the transfer of Layer1 by copying it over to the hard drive and then modded the default.xex with XeXTool.  When I loaded the default.xex Mass Effect loaded perfectly and started running like a pro.  Until I held down the Xbox button and the screen tore graphically ruining the game graphics even when I exited the 360 menu.  Now that I've shut it down every time I start the console it gives me an E79.  Things I've tried after Googling E79:

+Checked video connection and power connection
+Started console with and without the HDD
+Started system with the DVD drive disconnected and re-connected
+Verified the solder joints of JTAG connection (No multimeter to check connection but joints were solid and no shorting)
+Checked for any other loose connections and can't find anywhere else to check

Console is a Xenon with the JTAG hack, unsure of the exact dashboard version but I believe it's 8955_2, and hard drive was the standard 120GB Xbox 360 HDD.  I'd be willing to give anything a shot.  Like I said I don't have a multimeter but I could come across one if need be.  Any help is greatly appreciated I've only been using it two hours and I miss my hacked dashboard.  Thanks!

[AlkaliV2]

Solid advice.  I'm hoping they'll rework stability of CopyDVD in version 0.30 like they mention in the forums.  But for now I'm going to use my Kreon and XBC to make copies and just put them directly on my HDD.  I will avoid XeXLoader for now and stick with Viper360 since I know it copies/pastes correctly.  Thank you for the advice I'll give the E79 boot another try to make sure it goes away this time.  Viper360 from now on for me.

[AlkaliV2]

Can't get past the E79 screen.  Must have booted the console at least 25 times.  Probably bad for the 360 but it just felt good tormenting it   Aside from all that I tried booting it to E79, turning it off, waiting 5 seconds, and starting it back up.  Did not fix it.  Tried that 5 times and then tried it at 5, 7, and 9 seconds and was still unable to boot into dashboard.  Tried it with my HDD connected and disconnected and even tried a completely different HDD.  Attempted holding in the sync button and starting up the console several times and it did nothing for me.  I even got desperate and tried having a game with a $SystemUpdate folder in it to see if it would repair the xam.xex but as expected, it did not help.  It's not freezing like other people have reported after E79 errors.  There is no E71 and I can't believe it would be the nand flash considering it was working and all I did before it shut down was copy a folder and launch a .xex from the hard drive.  Anything else I could try?

[bulle48]

QUOTE(krizalid @ Jan 7 2010, 01:10 PM)

Boot Xell, I think you power on with DVD Eject Button... let it run for a bit. Turn off 360, unplug power for at least 2 mins and turn back on.

If this doesn't help, than recheck solder points and joints. If solder is fine, reflash keyvalt

nandpro lpt: -w16 rawkv.bin 1 1 (this is what I do)
If not, than erase whole nand ( nandpro lpt: -e16 0 400 ) and than flash clean xbr.bin (without any patches, clean as they are released), and after it's done, flash your keyvault again.

Leave 360 without power for at least 2 min, an it should all be good.
good luck, cheers!

NandPro is very unstable... causes lots of read/write errors without reporting them.  That is why most people have to do multiple dumps and compare them to make sure it matches.  If you can get Xell to run, then boot up Gentoo and use Lflash to update using the latest xbr image for your MB with your rawkv and rawconfig injected.  Lflash will backup your current NAND, write a new image, and read it back to verify... it will also take care of re-mapping any bad blocks... all in about 5mins... sure beats the 90+ mins that nandpro takes just to write over LPT.  And if you can't get Xell to boot, you can use Nandpro to flash only Xell (which is only about 2megs instead of 16), and then update to XBR using lflash...

Just to note... Lflash does not work with Big Block NAND yet (256/512 consoles)

[AlkaliV2]

Awesome, don't need it to work with big block cause mine is 16MB.  I'm going to try to boot Xell first.  Thanks for the advice I'll post back when I get an updated status.  I need to come across a computer with a LPT port first.  I'm definitely going to go with Gentoo and LFlash on this one.

[krizalid]

I don't have a USB keyboard    or else I would use lflash within Gentoo  


I hope they release that new flasher I've been reading about in xboxhacker.net, it's suppost to load from Xell and using your xbox controler choose what bin to flash and as easy as pie. I can only wait