How do i fix E79 1033

Got a dev kit that was RRoD 0020, thought it was an easy fix. after reflow/xclamp, it showed e79 1033. any ideas on how to fix this
EDIT: Ran a recovery disk through it, and it stays black screen.
what i had before wasnt a recovery disk, like i thought

 

hmm read that : http://www.assemblergames.com/forums/showthread.php?t=27094
Sorry but your Devkit must be bricked.

 

I think it was bricked, and you broke it even further?

 

it rrod'ed 3-4 months ago and have not done anything with it, idk how often they were bricking kits back then....

 

Bad flash. Do you have a dump from before the reflow\xclamp?

Have you tried booting with an XDK recovery disc?

 

i dont have the dumps. bought it rrod. where can i get a recovery disk

 

same place you got your kit?

 

TPB

 

alright i can do both, but im at school atm lol

 

Ofica1 g33k i see one more of those stupid posts you posted and then deleted come up again and you will be banned. Your childishness isn't welcome here.

 

:crying:Yea, that was probably one of my dumb ass friends or someone at school. I left it logged in because i was on a school computer and needed to leave. Sorry, it wont happen again

 

Not really a smart idea on so many levels. Especially being logged in a forum such as this nature on it. Security Fail!

 

Yes i know it was a bad idea, just forgot... IT WONT HAPPEN AGAIN, so...
Back to the topic...

EDIT: THE RECOVERY DISK MADE IT STAY A BLACK SCREEN!!!

 

Bad luck. Without a dump of the original, working flash, you're out of luck. Sorry. =(

 

RIP
Sorry.

 

I think E79 means "Could not start XAM.XEX"

And the practical effect is that E79 usually means the filesystem area of the flash is corrupted.

As there's no tool to rebuild flash images for devkits and it's likely that you don't know the device key (CPU key) then it's safe to assume it's indeed a case of R.I.P.

 

:gravedigging: ok, thanks any guys

 

One of the cases of how Xell could be useful for development kits. If you can get ANY part of your XAM intact you should be able to cold boot into recovery.

 

dont you mean shadowbooting into a recovery? and also XeLL for devkits is a bad and stupid idea. most of the people who killed their kits are noobs who just dont listen. i came in here back in november and made a post about backing shit up etc noone fucking listens.

 

OK, so i guess i had the wrong files(what i thought was a recovery). i downloaded a recovery and burned it to a disk. when i boot the dev with the disk in, it doesnt show an error screen, it just stays black.