Well I know the older recoveries (atleast 4xxx and lower) unintenionally brick Falcon/Jaspers as they are too new. The symptons sound very similar, won't turn on, no fans, etc. Could be the same in this case, but in a reverse fashion. Just like how the old old Beta Development Kits for the 360 can't go past certain recoveries. What board revision are you guys trying to run the 9328.9 on? Xenons? Zyphers? Not saying this is the cause, but it's just food for thought. It's perfectly reasonable that the source of the 9328.9 leak just built it to brick. -Doom
mines a 2005 xenon test kit, i'm pretty sure mine went wrong because i started default.xex from launcher instaed of rebooting with the disk in the drive
sorry just telling you the truth. you will end up frustrating yourself reading/writing at 4 hours a pop. trust me ive been through this before...
ehhh if SMC is damaged You can repair Your console... check it http://forums.xbox-scene.com/index.php?showtopic=700983&st=0 but if You haven't got Your NAND dump, just get from friend, and read Your kv.bin and config.bin, and replace... Checked.
I remember seeing this a little while back, might be worth a shot ;o. http://www.team-xecuter.com/forums/showthread.php?t=52213 -Doom
ive never been successfully able to perform those methods on adevkit. if you guys wanna further kill your kits be my guest.
Don't listen... if the SMC is corrupt this is all you need to do. http://ep-comps.com/free60/diagrams&tutorials/Bad_SMC_Flash_2.pdf Also I have no clue why sonic is discouraging you bearkiller, if your dev is "screwed" then you couldn't "further kill" your kit trying could you...
Well what else are they to do with a kit that won't even power on? Sure there's a chance they could fry the nand, but that's always replaceable. It might even be easier because they could just flash the Kit Dump onto a retail nand, desolder it, and swap it over onto their dev board. -Doom