Hi guys. Just acquired a Prototype falcon xbox 360. I got the console as a red ringer but recognised the side car cables straight away and sure enough the rear sticker is listing it as prototype. When powering it up there is no TV output and after a short while the three red lights kick in. From what i can tell the fans speeds are set quite high also based on the noise. I took the outer shell off to see the mainboard and it has two leds on. A green one down by the power inlet and a yellow one up by where the side car cables come out. Im guessing the green LED is the BGA test circuit. Once the unit is powered the green LED is lit and steady. I dont have cpu key, history or nand dumps of the console. Once the console does red ring its shows the standard 0022 error, very helpful! Upon inspection i would say there has been no xclamp fix done on this thankfully, but judging by some of the screw heads im not the first person to open it up. I have a guy local that can reflow the sucker but im also thinking this could be nand related. I also tried running recovery iso 20500.1 but it still just errors, its been a while but im sure this recovery disc is upto date enough to take HDMI consoles into consideration. I guess my question would be what other option do we have? If not the reflow, perhaps the zero paired image method to boot a disc recovery? Any suggestions worth taking a look at would be great!
Don't reflow unless you absolutely are out of options. Fans running high when it's booted typically means the filesystems table is corrupted/deleted within the nand. I had a slim prototype do this when a recovery failed half through.
I was thinking dodgy nand primarily. I dont have a nand x myself but a friend does so will get it round there and hooked up at some point. Forgive me if its against the rules to ask but is there any generic donor nands for xdk motherboards kicking around?
Cant link warez as far as I know, but talking about it I don't think it's an issue. How I fixed my slim was I used a donor nand from another prototype slim. That replaced the missing fs table. Then I reflashed the original nand, fans turned to normal. Still RROD after, but now it would take a recovery disc and finish it all the way. Console rebooted and has been working ever since. Problem is finding a donor nand for a prototype Falcon. I have a falcon stress test but it's my one and only XDK that has an error currently, it's E71-ing right now. Otherwise I have every other XDK nand for every model, but I don't have more Falcon's right now. I reflashed mine with a Nand-X too. I plugged it into the appropriate ports through the stress test cables, so I did not have to open or solder, I would suggest the same if it's possible for you to do.
Yes stress cables are still there sticking out the top, and thanks for the info! Guess the hunt for a donor nand commences. Is there any reason you would recommend against a pre-emptive reball? \looking at teh solder on the board its pretty cloudy haha
If you get a reball done, just make sure it's a trustworthy engineer. I have had too many retails botched, can't really replace an XDK as easily if it messes up. I will double check all my kits and see if I for some reason missed a hiding falcon.
I assume you need the CPU key for the donor nand? Got a dump from my Falcon proto here, but no key unfortunately. And presently, i'm not with my consoles at all. But, depending on what you need and/or if someone else helps you out first, i'll be home by Friday. I assume you need the CPU key to actually be able to zero pair the image?
Hi thanks for the reply. From my understanding the cpu key is not needed as without the cpu key there is still enough to get a disc recovery booting. Thanks again!
I did not need to create a nand or zero pair it like you would on a retail console. All I did was flash the incorrect nand, reflash the correct (still bad nand),power off, then I placed recovery disc in tray and boot with disc in tray and began recovery. During the recovery the bad nand was wiped and replaced with a new one. Its all about getting the xam to boot to at least be able to recover.
I gave this a shot with a donor nand that was very kindly sent to me and then back to the "bad flash" still no go on the recovery disc. However since i now i have a dump to look at, everything looks like it should in the file system so that kinda confirms the gpu error. Cant thank you enough man, it may not have been the solution but it at least eliminated a possibility. At least now i can send it in knowing it was tried!
No problem. Hopefully it'll work after the reball. Otherwise I have a few Jasper stress tests kicking around if you need a replacement.
To be honest i picked this up by chance, sold to me as faulty but not sure the seller knew it was xdk, so its surplus to needs anyway hehe. Laying out for a rework to save a proto, even if its not really an exciting model seems worth a shot.
For a reball, contact Shawnunderse7en on this site via PM or on Se7ensins.com As for the NAND, you should be able to build a Zero-paired NAND dump using the 66mb NAND build feature of XeBuild. I've never done this, but in theory, it should work, then you can run a recovery to generate new tables for your console.
Sorry to bump this somewhat old thread, but turns out the stress kit I have is exactly the same model as yours (prototype falcon) and has that nice beta sticker on the side. I'm guessing it's worth a bit more than I thought, sounds really desirable
