Hello,
I just bought a regular XBOX today manufactured March 18;
K: 1.00.5713.01
D: 1.00.5659.03
manufacture date.... 2004-03-18

The original V1.6 reported had a different Kernel;
K: 1.00.5838.01
D: 1.00.5659.03
manufacture date.... 2004-03-22

Do you think I got a V1.6? I don't want to open it since I have lots of XBOXs already but I was just looking for the 1.6.
Let me know what you guys think.
Thank you.

thats probably a 1.4 or possibly a 1.5

i bet the reason thery dident do this before.. is because they used the motherboard for debug and retail units... they just added the ramchips and changed the tsop to a debug kernel...

now they stopped making debug units.. they can put the bios in the mcpx because it wont need to be changed.. that also explains the loss of the extra ram spots...

this sucks :/

V 1.4 - D1

Well, we should still be thankfull that the LPC port is still there, because if it retains its original use, there WILL be someway to force the XBOX to load from it (heck MS must be doing it someway). What would totaly fubar most hacking attemts, would be the removal of the LPC port.

It seems Team SmartXX has got themselves a 1.6. . I'm hoping we can expect more info from them soon.

OzXodus Xbox v1.6 research/findings
>> From The_Mad_Maragan on ozxodus.com:

All halo boxes should be 1.4 i bought 2 of them and looked at about 8 boxes..

Both had v1.4 MB, WD 8GB, Phillips DVD, and 5659 5530.. chip-able but no exploit yet..

About the 1.6..

1. I believe its all in the Xyclops chip..
2. I dont believe MS could release a MB that cant be reflashed.. they make some money on refurbished xbox's and the're not going to just toss the boards...
3. Debug xbox is gone.. so no more need for the header.. plus i might not be right but they use recovery/builder disk to flash/install everything on the boxes.. so maybe no need of a chip anymore.. just a hacked disk.. So go ask Billy if you can borrow one of the disks..
4. still thinkin..

no flamin.. just throwin ideas.. remember if a human makes it.. theres NO reason it cant be hacked.. unless they go to some controlled environment.. like a xbox terminal.. hehe that would suck..

Snyper

Anyone still has a v1.6 they want to sell? Please PM me.

Would be useful if I also had one so I can take HD pictures and so.
And it'll probably take some time before they become available here in europe ... most stores still have tons of stock of xmas 03.

Halo Xbox 02-13-2004 - Philips Drive - 8GB WD - Looks like a 1.4 but didn't voltmeter the LPC yet - Ordered it from Newegg.com on 4-30.

Damn, that's a shame. I wanted a 1.6. They didn't start getting them until almost the end of April, so I thought maybe, just maybe..

Ah well, to Xenium I go.

--D

I work in a gamestore, so I know the halo xbox's have been selling quite well......

I KNOW my halo xbox is 1.6 because i checked it out. I am gonna try to get you guys some pics tonight, but here's my guess......

They've simply began to outsell their old stock and have been redoing them with the new parts. My store gets 4 green xbox's every 2 days so...... That's how fast they're selling here in Baltimore.

I just got a xbox last week, and open it up and has an nvidia encoder on it, instead of the focus or the conexant, is there a way to mod this, here are the kernal and dashboard version number

K: 1.00.5713.01
D: 1.00.5960.01

Yay mod chip devs got 1.6ers , we don't really care if they are appearing in Halo boxs (just a green case), we gotta crack the board first.

Note: for those who wonder ... I'm deleting posts here.
I try to keep the thread on-topic and cleaner. I did not delete any post with any useful information (or atleast I hope so) nor did I censore any information (what would there be to censore anyway).
If I deleted one of your posts, don't take it bad ... doesn't mean your post was 'crap', I just try to make it easier for those who want to read/update about what we have so far here about the v1.6.

"I have a august 2002 xbox, do you think I have a v1.6?", "YEAH! Hack IT!!!" and totally offtopic posts about what-modchip-should-I-install-in-my-v1.4, refurbs, ... are removed to make the thread easier to read.

Also about naming ... it's a v1.6 ... v2.0 would not be logic ... v1.2 should have been v2.0 and this one v3.0 then in this logic. Even if we would like to change name, it would be too late. What comes after v1.9 ? v1.10 ... (!= v1.1.0)

saw this on xbox-scene news. suppose it can be useful here too.

from hamtitampti on http://www.smartxx.com/forum/thread.php?threadid=703

isnt saying "we dumped the bios and the BIOS md5 is blah blah" a little show-off?

the tools used to do so, where the bios is located or if u have to 'bridge' something to make it readable would be a usefull news..

5838 bios dump is up on xbins for those who want to take a look at it. (thanks smartxx team)

i tried a HomeBrew29 with that 5838 bios on a v1.2 mobo.

u get no video signal (and no audio).

Sometimes the front light stays solid green and the DVD drives makes some ticking noises.(the light flashes green on eject press but no tray eject at all ~only ticking noises); sometimes it's a FRAG, or a 2 boot attempt and solid green.

Looks like the next gen mod chips will have an expanded LPC host if the prelimenary reports of no LADS on the LPC port are true. No info on clk and lrst signals making me wonder what they are doing at the factory with the LPC port or the LPC host that's built in and how critical timing becomes if there is more than one host on the bus on signals with complex timing.

A nice road map to the address and data lines as they corrrespond to the MCPX PCB vias and traces was posted for reference from a 1.0 machine and that will help a lot of the kitchen table hackers. I'm working on a reliable way to get signals off the MCPX pcb and back to the LPC Port by hot glueing magnet wire exactly over the traces and soldering them all together and wicking them clean ala the smd technique. I just have a feeling the first modded 1.6's will pull signals off of there or or maybe the factory has an easy way but it's looking like the factory now uses a remote/external LPC host

anyone tried say using the mechassault trick and flashing the TSOP?

so is the Xyclops the Bios chip?

is it read-only or is it flashable?

do the available modchips right now work on it?

is there a "D0"?

is there a posibility that the ram could be upgraded or the only way is removing the ones that it haves and replace them with bigger ones?

Xyclops = bios + audio, "d0" is grounded
For the ram a quick look at the board is enough to se you cant "add" ram chips.

Flashed the 5838 bios to a SmartXX in a 1.3Box
Using the latest Dash from LIVE!

No Video or Audio.
Eject will not work.
Does not Frag
Will not boot original games on Disc, not that I thought it would, but tries to read the Disc.

Can some people with Focus Chips please try it.

I flashed split_5838 on to a sst 49lf020 and set it up cheapmod style and now I call my v 1.0 model xbox fraggy. Frag, no eject, no games load. As expected.

Flashed split_5838 to a 1.1 and as soon as i launch it from smartxx os i get red flashing.
Eject works (wont even try to boot a game), and no a/v output.

K: 1.00.4817.01
D: 1.00.5659.03

Ok, i finally got to the end of it, and im going to add my $0.02

First off, I am not an electronics guru, but is it right to assume since the Xcalabur chip is where the video encoder went, that it is the video encoder? And the same goes for the Xyclops being a bios chips of sorts, how do you know its not the video encoder?

I'm going to go to EB tommorow and buy one, (it looks like ones made after march 22nd are 1.6's) If anyone wants one, PM me and ill see what i can do (i will charge actual cost + actual shipping)

I just bought my halo xbox as an XBL box, im going to mess with the 1.6, no matter what its going to be hackable, its just right now the only way it could get easier is if MS sold them with modchips pre installed, so god forbid you might have to solder something.

hippo, the rc4 key has changed since 1.0, not sure if thats what you meant by expected, but that is one reason

http://www.smartxx.com/forum/thread.php?threadid=703&sid=

hamtitampti: Can you confirm/deny that the MCPX has _not_ changed? I have no v1.6 to play with - but I've been under the impression that since the MCPX-change for v1.1 debacle between MS and nVidia no more MCPX revisions could be done.

Thus, all the changes will be bus/new chips/new logic related.

Also, I'm guessing due to your LPC-findings that not only will v1.6 need a new bios - it will need new modchip-designs as well?

hehe
good question
it is YES / NO

best look regulary int he thread in our forum.
i will not work here, as there are to many n00b beliving what groups like "xenium" tell.

for Your question:
as the TEA hash == same
the bios has same structure
and the secret rom dump shows no change, there is no "new" security concept
but the mpcx itself is "new"

(seems, i have to invite you now to lab)

franz