kit bricked?

i got (aparently had) a dev kit, and while awaiting to get it upgrdaded to a later recovery i stumbled across a recovery 9829.9 . put it in my console and it rrod 0022 and then now wont even power on. my guess is nand is erased.kinda bummed, hadnt even had it for like 3 weeks or done anything with it up until it bricking. any info?

 

apparently i fell victim to someones idea of a joke by creating a fake recovery. awesome... now if i dump a nand from a second dev kit and leave it un tampered and force flash it on to this kit by shorting pins on nand will it revive the console? should have backed up nand before i did anything with kit too many things on my mind and wasnt thinking straight before i decided to run that stupid disk...

 

yup figured that out... but if i use a doner nand and flash it on there, will it work?

 

if your sure its not a pnet brick. you can write the first block of any dev image and the console will boot then give a EXX erro.r stick a real recovery in and it should sort it out. worked for me before.

 

def not a partnernet brick. hadnt even been on partnernet

 

the recovery.exe xex strike again.

 

any one see it was put on 360iso yesterday hidden as the new halo reach maps.

 

just fill the xex with zeros lawls.

 

weird was able to dump nand of bricked kit completely without having to short anything. was able to get two matching dumps, i think the brick recovery just rewrites some smc values and wipes maybe part of it, going to try writing first block of nand from another console on it. like you said

 

wrote first block to nand console now powers on goes into rrod somewhat living.

 

seems to search at dvd drive before rrod i dont think this other xdk disk i downloaded is valid still rrod. at least im on some kinda path to revival

 

Boot chain is longer than just the 1st block.

1st block contains the SMC (program for the microcontroller inside the Southbridge).

I'd say you need to write something around 35(hex) blocks to get all the boot chain in place (some filesystem blocks will be written too but that doesn't matter as the recovery will overwrite them).

 

Hrm... I don't really know anything about the 360, so forgive me for the ignorance...

But isn't the boot chain protected with some kind of per-console key, signature, or hash that would prevent any kind of swapping NAND data shenanigans?

 

On retail units what you said is exactly how things are laid out ... :thumbsup:

 

well, im going with 3 different things, either #1 disk seriously does some messup to console other then just messing with nand. #2 stuff isnt working because none of the recovery disks i have are legit, #3 nand reader is not correctly reading or writing(not likely being as though i can validate and have used it to jtag a few consoles) tried multiple blocks of hex stepping a single block untill i got to the upwards of 50. then just tried flashing entire nand i dumped from another working console all leave me with rrod same error code still, anybody got any ideas?