New Bootloader found in newly manufactured units

[tmbinc]

User "jc" in #free60 found that his Jasper, built June-30th 2009, already contained the new bootloader (but with a 7363 Kernel).

We don't know when Microsoft switched it in production, but this discovery means that they did this at least over a month before the update.

So far, we don't know what Boxes are safe to buy. If you want to check your box, dump the flash, at look at the "CB" Version (offset 0x8202, the two hex bytes after "CB"). For Jasper, CB Versions 6750 (and up) are bad, CB Version 6723 is still good (at least we think so), CB Version 6712 is good for sure.

If you find that your jasper is still either  "good" or "bad", please post the mfg date (and CB version) here so we can determine the cutoff date.

Let me remind your that we are not completely done with the adaptation of the hack to jasper yet. We've sorted out most things now, so we'll release it soon. The recent build.py changes will make an adaptation easily possible, and nandpro already supports jasper. Remaining things are the SMC and the J1F1-replacement points. We're working on this, don't worry.

My Jasper, built 2008-10-10, is "good" (CB version 6712).

[l_oliveira]

I've dumped (RAW, using a chip reader) the nand of a Jasper console made in July 16 2009... 
Is there any way of manually checking the CB version in the dump ?

It's a Jasper with 512MB nand flash (K9F4G08UOB-PCBO)

[ArtVandelae]

Along these lines, what is the manufacture dates on the units that the big online retailers like Dell and Amazon are currently shipping?  With their high turnover rate it seems that the odds of getting a system with a more recent manufacture date (and thus the new bootloader) are fairly high.

[l_oliveira]

tmbinc,
I found the CB version at offset 0x8400  (following your instructions and considering the fact that this is a large page NAND device)
This is what I got:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00008400   43 42 1A 43 00 00 00 00 00 00 03 C0 00 00 95 50   CB.C.......À..•P    (1A43 hex=6723 dec)

Sadly this console is lost (owner extracted the wrong key from the new liteon drive and didn't check if the key was valid with another drive before running lo-erase.
Oh well... Paperweight...

Edit : Ops...  I somehow misread your post (just re-read it) and seems like this unit is on the "maybe works" range...

[DarkstarTM]

My Elite Jasper (date 2009-05-14) has 6723

[Oggy]

Ive a June09 Jasper Elite here.

Ill check when I get time (and lay off the beer!)

[tmbinc]

l_oliveira: CB=6723 is pretty sure exploitable, as it seems. Sure it's July-16? That would be after June-30th, which was "bad" already.

[l_oliveira]

l_oliveira: CB=6723 is pretty sure exploitable, as it seems. Sure it's July-16? That would be after June-30th, which was "bad" already.

Sorry I was drunk (no I just tend to misread stuff)
It's 2009-06-18 (triple checked) so this is likely to be one of the last exploitable units they made

[Intersect]

Tmbinc, do you have the smc config blocks figured out ?

[tmbinc]

Please let us stay on topic here.

So, bottom line:

Everything after 2009-06-30 already has the new bootloader. Everything before 2009-06-18 seems to have the old one.


IF YOU WANT TO BUY A NEW CONSOLE FOR THE HACK, MAKE SURE THAT IT WAS MANUFACTURED BEFORE 2009-06, TO BE SAFE. There should be enough old consoles out. I remember how hard I had to search to get a Jasper back in 2008-12. Also make sure that it was never turned on (so nobody could update it), and wasn't a refurbished console.

[jelle2503]

well this sucks.. guess i'll have to get a new 360 NOW... so there's no way telling that it has the new bootloader unless you dump the flash? 

clever moves from MS, but very sad for the homebrew

[havelln]

would that be saying every 360 with 512mb will have the new bootloader

i dont have the original case for mine was swapped
only one way to be sure
ill dump the nand later

[Arakon]

the 512 MB flash has been out longer than 2-3 months, I believe.

[katzoo]

Arcade Jasper 512 mb NAND
MFG 2009-05-25
CB = 6723

[havelln]

just dumped my nand
it is 16.5mb  is that the right size
at 00008400   43 42 1A 43 00 00 00 00 00 00 03 C0 00 00 95 50     CB.C...........P

so thats 1a43 which is 6723

to let anyone know i tried 3 diff comps to dump the nand which kept getting error 0 reading 0 and so on
but then i used an old dell latitude d600 laptop which worked fine straight away

couldnt find much about how to dump the nand but i did it with all leads plugged in normally with the xbox not powered on is that how it should be done

[JBDizzle]

Along these lines, what is the manufacture dates on the units that the big online retailers like Dell and Amazon are currently shipping?  With their high turnover rate it seems that the odds of getting a system with a more recent manufacture date (and thus the new bootloader) are fairly high.

I just received a 2009-04-09 arcade from dell. Will check nand when im able.

[doolittle123]

I just dumped a jasper with manufacturing date of 2009-6-12 and I have confirmed that it also has the old one.

edit:
Manufacturing Date: 2009-06-12
CB Version: 6723
Type: Arcade with 512MB Nand

[tmbinc]

Thanks for all the input.

Reminder: Please post:

a.) Manufacturing date (as written on the box),
b.) CB version number (please not just "the old" or "the new", but the number, as there are different ones. It doesn't matter much in the effect, but I'd like to be sure there are no surprises)
c.) Type (Arcade/Pro/Elite) + nand size (if you know)

Thanks!

[dtrmad2004]

What are the chances of an Xenon refurb having 7371 or lower having the new bootloader? what CB would I be looking for there? or am I pretty much safe aslong as it is 7371 or lower since it is not new?
Will be recieving it tomorrow.

[B1N4RY]

@dtrmad2004, don't worry about it.
I have send in a broken Xbox with Blades dashboard, and when I got it back, it came back with NXE 7371, and a exploitable CB