No power to Falcon board after XBReboot flash

Kooga

Inactive User
Joined
Mar 4, 2009
Messages
9
Reaction score
0
Location
Bucks
Falcon V3 board fails to power up after flashing the XBR.bin file back onto the NAND. The whole jag process worked absolutely fine to the last stage. Then disconnected the LPT port and tried to power on the xbox 360 but it would not power up. The power block was providing the 5 Volts and could also be found on relevant transistors on the board. After failing to start it with the cd eject button and the power button on the RF board I decided to try and regress by flashing the original NAND file back onto the NAND but that did not work with the error 'unable to find flash device'. The entire board appears to have gone dead. Anyone met a similar issue or any ideas on how to get the original NAND back onto the board?
 
When you press the main power button does the green light flash for less than a second, also does the power brick light change colour as you do so?

Jama
 
Sounds like you have a short somewhere, give the board a good checking over and check you Jtag wiring too.
 
There is absolutely no change in LED colour on the RF board or the Powerbrick. The Jtag wiring and the lpt port all look good and do not short (tested with avometer). Also it worked fine when doing the XBReBoot flash. When finished flashing it all I did was disconnect the lpt from the pc and tried pressing the eject button and nothing happens. When it wouldn't power from the on/off button I thought well i better flash the original.bin back onto it but it fails to even detect the lpt is present. Will desolder the lpt etc again and try again.
 
Reflash again it just didn't go well at all giving you a dead box been there myself a few times first time i thought i had killed it but flashed again and away it went. If you can still see the flashconfig its a straight forward flash over if not short the pins on the chip google to see which ones to erase so flashconfig can been detected, and above all DON'T PANIC.
 
Thanks DJJama. Been away for a little while. It does look quite interesting and shall give it a try. It was a bit ambiguous about what pins to short so I got them to confirm that all 4 pins need to be shorted at the same time. Will probably give it a go tomorrow and report back on how it goes.
 
I can vouch for this officially now.

Due to me being an idiot I flashed a falcon with a xenon image causing this issue.
Sellotaped so only pins 29-32 were showing. Hit the with a screwdriver and second time round it worked :).
Xbox is back to life.

I really do winder how they came up with this though.

Jama
 
Shorting the pins definitely works to ressurect the NAND. Had a bit of trouble with the screwdriver method so have soldered 4 wires to R2D3, R2D4, R2D5 and R2D7, for pins 29,30,31 & 32 and used a croc clip to short them and release after 3 secs. Flashed the orig.bin file back onto the Nand which appeared to go ok but still cannot power up the XBox after it has completed.
 
A bit of further investigation and testing has come up with some very interesting outcomes.
1. The NAND has only had to be ressurected once with the shorting of the 4 pins. The LPT port can now see it every time. We have found 3 different settings for the LPT port in the bios, ECC, ECP and General. ECP appears to be the better one to set this to.
2.When doing the XBReBoot the guide I was following the procedure advised to use Nandpro20b version of Nandpro and the command to use was "nandpro xbr.bin: -w16 rawkv.bin". I have since opened the text file that accompanied the xbr.bin file and it has an additional command "nandpro xbr.bin: -w16 rawconfig.bin 3de 2" which I did not enter when doing the xbreboot procedure. Can this have contributed to the xbox not powering up after completing the xxreboot procedure? If anyone understands the function of the second command then I would very much like to know. Can this command be reapplied at a later date to complete the process? The important point from this is that it is important to read the txt files that accompany the xbr.bin file.
3. I have tried several attempts at writing the orig.bin file back onto the NAND and the process appears to write without any issue and not a single bad block coming up. Badblock mover shows no back blocks on the file. For a Falcon board the procedure shows that the image to be used should be 0x01198010 where as the image I have is
0x01198030. Is this an indication of the file size in hex (the 0x... suggest this) or is it a reference to an address? Does the slightly larger size of the file make a difference and is actually a sign of an error? The result for each is the same, the Falcon board will not power up after completing the writing to the NAND.


Can anyone expand on any of this? Your contributions would be most appreciated. I have to say that even though I have a Falcon board that does not power up this is a very interesting bit of troubleshooting.
 
After many tries the Falcon is back up and running on its orig.bin file (not jtagged) but working which is a relief. The shorting reserructed the board and the rewriting to the NAND required the removal of all the jtag-smc wires. After we tried writing the orig.bin file back to the NAND we tried to read it and it came back with numerous bad blocks from a very early stage. To overcome this we found that erasing the NAND before writing the orig.bin back will give a clean write of the original NAND. Erasing the NAND does not kill the LPT connection and you do not need to short the pins to communicate with it again however if you try to power it up after erasing the NAND it is totally dead. Don't Panic!! Write the orig.bin back and then try reading it again to make sure it is a clean write and you should be fine. We also ran the new read in Total Commander to compare it with all the orig.bin files to make sure we lost nothing and they all came out perfect. All the moving of the board about etc did RRoD the board but a blast of the heat gun and reapplying the heat sinks resolved that issue. Shall retry the jtag process on it again soon, reading the accompanying txt files with the xbr files etc each time and checking little items such as the Flash config code being the right value for the appropriate board, CD version being one of the correct values to make it Xell Compatible etc. Thanks to all that contributed and hopefully my next update will be the successful completion of the complete jtag process on my Falcon. To speed things up I have also started making the USB version of the NAND reader as the LPT one sure uses alot of time if you are doing lots of reads and writes when things don't quite go to plan.
 
Back
Top