Ok so I'm trying to figure out the CB version of a refurbished Falcon I received from Microsoft about 2 weeks ago (German repair center). I had planned to keep this console for homebrew as it has dash version 7371 but I've heard some of the refurb units have a non exploitable CB version.

So far I've dumped the Falcons nand over 7 times but each and every dump fails to open in either Degraded v1.1 or 360 Flash Tool. While dumping I receive no errors and everything appears to go as it should. I have a Xenon 360 which I've also dumped several times using exactly the same set up and I've encountered no problems whatsoever. I've tried adding resistors, shortening the cable between Xbox and PC but the resulting Falcon nand.bin still refuses to open in Degraded or Flash Tool.

I've also followed tmbinc's info on how to check CB version using a hex editor. I use Hex Workshop to open the Falcon's nand.bin and I see "2004-2009 Microsoft Corporation" in the top right corner so it looks to have at least partially dumped the nand correctly. I select to go to offset 0x8202 (as per tmbinc's instructions) but I'm not too sure what I'm supposed to be looking at. I'm not too familiar with using hex editors so I'm a little lost at this point. I can see the letters "CB" writted halfway down the right of the screen but see nothing that might suggest version. I could post a screenshot if that helps anyone work this out.

So in brief, I appear to have no problems dumping the Falcon's nand. I am however unable to open the .bin files in either Degraded or Flash Tool to decipher CB version. I'm not sure how to use a hex editor to do this. Basically I just want to know if I should keep this 360 or not. If it can't be used for future homebrew then I need to sell it.

Any help with this would be greatly appreciated. I've wasted several hours on it already and I have a bad feeling it's going to end up being a non exploitable box .

You take the two bytes after CB and put them into windows calc in hex mode, then switch to decimal mode and you have the CB version. Requires you to select advanced calculator mode instead of standard in calc's menu.

example, hex editor display:

0x43 = C
0x42 = B
0x07 = version high byte
0x80 = version low byte
put calc in hex mode (or find an online converter), type 780 (or 0780), then switch to dec and you see that 0x780 is 1920 in base10, which is in this case CB1920.

Ahh ok, thanks!. That really helped. Unfortunately that tells me it's CB version 5771 which according to tmbinc's thread over on xboxhacker is "fixed" and of no use to me for homebrew . Anyone need a pre flashed Falcon? (Microsoft actually sent me it with a pre flashed ix DVD drive ). Thanks cory1492.

NP

Just to fill in the info in case others come across this thread, the offset to look to in a NandPro dump (with ecc) is 0x8400 and the list of CB versions that are G/NG for the exploit:

I just checked my falcon dump becouse i also get the error message with degraded. Hex editor shows 0781 so it should be a CB 1921. Does that mean degraded needs to be updated in order to work with newer models/dumps?

afaik if you are getting CB1921 from a retail dump you have a xenon... does that machine have hdmi? My own falcon has 5770, degraded opens the dump just fine and reports versions, but that is (of course) without CPU key and just the 1BL key entered.

Not to try to stray from the topic, but how exactly did you manage to dump your nand? I thought the JTAG points/everything you need to do it was only given out for the xenon? After a little searching on xboxhacker it seems like a few people have been trying to dump their nands as well, but this is the first I have heard of it.

The JTAG points are only needed for running homebrew. They have nothing to do with dumping/flashing the NAND. You can dump the NAND on all versions of console right now. It's just as of now only the Xenon info/files for running homebrew have been released to the public.

I took a photo of my Falcon mobo and put together a simplified diagram of where to solder to create a db-25 cable for dumping/flashing.

It's the same for Xenon boards and I'd imaging Jaspers too (Although I don't have a Jasper/haven't bother to check).

Oh, sorry I had no idea, thank you for clarifying this for me

P.S.

Thank you for the db-25 cable flashing diagram, I will be sure to try to read my nand when I get the chance.

Man thats weird im sure its a falcon couse it has hdmi and its manufactured mid 2008. It also shows "2004-2007 Microsoft Corporation. All rights reserved" in my hex editor. Nandpro only gives 1 error (block error) and all dumps are identical (tried 6 dumps).


I thought i was using degraded 1.1b but it was an old version. I got 1.1b now but the program crashes as soon as i load the bin, flashtool opens the bin without errors.

It is odd, but it could be there just isn't enough data known at this point to be sure, though tmbinc was fairly direct in saying flat out that CB version 5xxx is falcon and 6xxx is jasper. The box I have here is from the time when they were switching over to jasper in the lines so I just missed getting one, late sept 2008.

Is the box you are trying on working for dash and such, or did someone possibly try degrading it before? Have you looked at the 'bad block' contents with a hex editor?

I'd try filling/overwriting the block in question ((512user+16spare*32) with 0x00 and see if degraded responds differently as perhaps it dumped bad spare data when it errored. My own experience suggests that on error the buffer that is dumped into the file for the erring block is somewhat random.

I really have no clue where to look in the hex editor. I dont know where to find the offset becouse nandpro only says "Error: 250 reading block DB". I think its better for me to wait and leave it to robinsod. I hope he has a fix coming


Oh ya i forgot to tell that the xbox is working fine. Ive played prototype a few hours yesterday.

When i scroll down in flashtool i see names with xenon