Post by: booyeah on May 01, 2004, 11:34:00 AM
Post by: pascar 802.11 on May 01, 2004, 12:07:00 PM
Post by: _Cold_Fusion_ on May 01, 2004, 02:39:00 PM
and what drives it came with?
Post by: bucko on May 01, 2004, 12:42:00 PM
Post by: booyeah on May 01, 2004, 12:44:00 PM
Post by: pascar 802.11 on May 01, 2004, 02:46:00 PM
edit:::
sorry you guy exceded my 6gbit bandwidth this month
This post has been edited by pascar 802.11 on May 4 2004, 03:16 PM
Post by: XanTium on May 01, 2004, 02:47:00 PM
Goto the "settings" option in the XBOX menu and select "Sytem Info". You will see lots of legal text.
At the end of the txt you will see something like
K: 1.00.xxxx.01
D: 1.00.yyyy.01
xxxx is your kernel version
yyyy is your dashboadr version
Please give us the numbers you get there.
Thanks
Post by: bucko on May 01, 2004, 12:52:00 PM
Post by: _Cold_Fusion_ on May 01, 2004, 01:02:00 PM
Post by: tNCecil on May 01, 2004, 01:11:00 PM
Post by: jimmykaraff on May 01, 2004, 01:28:00 PM
Post by: SniperKilla on May 01, 2004, 01:36:00 PM
can we get some under board shots
Post by: _Cold_Fusion_ on May 01, 2004, 01:38:00 PM
Post by: brahm2 on May 01, 2004, 01:40:00 PM
edit: if anyone's having troubles with slow-loading pics: (removed with edit3)
edit2: whoa, and the d0 area is all mixed up.. interesting stuff!
edit3 (MUCH LATER): XS is hosting these pics now, my bandwidth is dry!!
http://www.xbox-scen...alibur_01xs.jpg
http://www.xbox-scen...alibur_02xs.jpg
http://www.xbox-scen...alibur_03xs.jpg
Post by: pascar 802.11 on May 01, 2004, 01:51:00 PM
Post by: heinrich on May 01, 2004, 02:01:00 PM
Post by: pROvIs on May 01, 2004, 02:17:00 PM
| QUOTE (SniperKilla @ May 1 2004, 04:36 PM) |
| where is the TSOP?!? can we get some under board shots |
yes please
underboard shots
Post by: Bwsk8 on May 01, 2004, 02:25:00 PM
Post by: CreziB on May 01, 2004, 02:31:00 PM
Post by: XanTium on May 01, 2004, 02:40:00 PM
| QUOTE (CreziB @ May 2 2004, 12:31 AM) |
| I swear, if it were me...as soon as I cracked it open I'd be taking it back to get one that was setup normally. I'd be a bit pissed to be the guy breaking onto the scene with my new...yet to be modable xbox version. Ha, I'd be taking a trip back to the store. |
or he could sell it to modchip teams looking for one of these new xboxes
Post by: HSDEMONZ on May 01, 2004, 02:49:00 PM
Post by: echto on May 01, 2004, 02:50:00 PM
| QUOTE (XanTium @ May 1 2004, 02:40 PM) |
| or he could sell it to modchip teams looking for one of these new xboxes |
Sounds like the best idea to me.
Post by: Master-Chief on May 01, 2004, 02:54:00 PM
Post by: pascar 802.11 on May 01, 2004, 02:57:00 PM
Post by: bucko on May 01, 2004, 03:00:00 PM
Post by: zeph on May 01, 2004, 03:31:00 PM
| QUOTE (Altima NEO @ May 1 2004, 11:49 PM) |
| It would be interesting to see if current mod chips still function on it... with the exception of the video encoder of course... |
How could it, nobody knows where to new d0 location is
.
Post by: Casper1786 on May 01, 2004, 03:37:00 PM
Post by: Bwsk8 on May 01, 2004, 03:42:00 PM
Post by: none_ya on May 01, 2004, 03:46:00 PM
noneya
Post by: Dolfhin on May 01, 2004, 03:47:00 PM
.
Post by: lookformeb on May 01, 2004, 03:55:00 PM
| QUOTE (Master-Chief @ May 1 2004, 05:54 PM) |
| What if they make new mod-chips for these Xboxes that are EVEN easier than what they are now! |
I wasn't under the impression that it could get any easier...
Go mod something difficult, like a ps2 and you'll see where I'm comming from...
Post by: SniperKilla on May 01, 2004, 03:55:00 PM
| QUOTE (Dolfhin @ May 1 2004, 11:47 PM) |
| This has to be the first ''unexploit-able'' Xbox. No TSOP, probably no font/audio hack/no modchip . |
you think ms put the tsop there for shits and giggles? it holds their own bios... there has to be one still there
we need underboard shots....
Post by: Corspegrinder99 on May 01, 2004, 03:59:00 PM
Post by: miazmaticdotcom on May 01, 2004, 04:03:00 PM
Post by: tNCecil on May 01, 2004, 04:04:00 PM
Post by: 60_Megabyte_File on May 01, 2004, 04:07:00 PM
My step-brother just bought an XBox recently after the price drop that I'm gonna mod for him. Tomorrow I'll see if this is, indeed, the 1.5/1.6 XBox, and if it is I'll take some high resoluton shots.
Post by: twistedsymphony on May 01, 2004, 04:07:00 PM
yeah buddy definilty sell it to one of the modchip devs to figure out. if it were me I'd send it to Xecuter as they seem to do some of the best work with the Bioses (haha and they thought they released their last bios ever)
or if you got it from best buy you still have 30 days to pay $20 no questions asked warantee...
some guy at best buy kept pushing it on my friend so he bought it... took it outside ran it over with his truck and returned it right then for a new one
Post by: cap269 on May 01, 2004, 04:10:00 PM
Of course it probably isn't, but wouldn't that have been sweet...
Post by: Monoxide-Child on May 01, 2004, 04:11:00 PM
| QUOTE (tNCecil @ May 2 2004, 01:04 AM) |
| Possibly another delay for the X3? :| |
*knocks on wood*
Anyone care to make a conjecture as to the purpose of the Xyclops chip? Could we be looking at a flashable chip not in a TSOP-package and not even realize it? Though the underboard shots will be needed before this could even be considered an educated guess... now it's more like a shot in the dark.
Post by: MagamiAKO on May 01, 2004, 04:13:00 PM
There's your "TSOP".
Btw, "TSOP" is the packaging type. It's no longer a 'TSOP'. heh.
Post by: Casper1786 on May 01, 2004, 04:15:00 PM
Post by: MagamiAKO on May 01, 2004, 04:19:00 PM
Try that one. It's on a page about how to reset the Dell BIOS password, that's what the arrows are pointing to. This is the dell BIOS chip. I unfortunately don't know much more about it. It's funny that these two pictures happen in the same day because I had never seen a BIOS chip like that before until I had to reset the password on a Dell laptop.
Post by: heinrich on May 01, 2004, 04:20:00 PM
| QUOTE (MagamiAKO @ May 1 2004, 09:13 PM) |
| That little chip near the LPC, that does appear to be the BIOS chip. http://qasimtoep.tri...dell/chip02.jpg It's exactly the same as to the one on the Dell laptops There's your "TSOP". Btw, "TSOP" is the packaging type. It's no longer a 'TSOP'. heh. |
the small chip with 8 pins? Looks exactly like the eeprom that has been on every previous xbox version.
| QUOTE |
| that picture of the dell chip doesn't load at all for me |
copy the link, paste it into your location box, hit enter, paste the URL again, hit enter, poof.
edit: hi A-KO
Post by: Monoxide-Child on May 01, 2004, 04:21:00 PM
| QUOTE (Casper1786 @ May 2 2004, 01:15 AM) |
| that picture of the dell chip doesn't load at all for me |
Same here.
We should also be asking ourselves what would posess M$ to re-tool their assembly lines now, when (from what I understand) there is supposed to be a miniaturized XBox (a la PSone) for this holiday season... don't they understand that the mod community is one of the main sales drivers for consoles?
Who else FRAGs more XBoxs (that aren't covered under warranty), unit for unit, than any other consumer group out there?
Post by: lordvader129 on May 01, 2004, 04:23:00 PM
| QUOTE (Casper1786 @ May 1 2004, 07:37 PM) |
| well for those that know where it led 2 before on other chips(I don't), they could check it, trace it back an possibly locate the D0 points, wonder if they're still an alt D0 point? |
i know one end leads to the 5th leg of the TSOP, which is also MIA on these xboxs
Post by: MagamiAKO on May 01, 2004, 04:23:00 PM
COuld it be that MS has now utilized the LPC for a BIOS chip?
Post by: Monoxide-Child on May 01, 2004, 04:27:00 PM
Post by: heinrich on May 01, 2004, 04:42:00 PM
regardless, its about time we have something new.
Post by: MovesInSilence on May 01, 2004, 05:36:00 PM
what ever the answer i do hope it's not going to end up being a swine to solder like doing a PS2 (V9/10). I can solder D0 to the top of most xbox's i do. I haven't come across one of the new ones yet in Australia (Western side) i guess by the time i do the new range of chips will be available
Post by: dethbunny on May 01, 2004, 05:36:00 PM
| QUOTE (Monoxide-Child @ May 1 2004, 06:27 PM) |
| I'm at work on a small monitor now... can someone tell what the numbers on that XYclops chip are? I can do a datasheets search on it... chances are, it's an off-the-shelf chip with a new logo silkscreened onto it. |
Nobody else did it, so here's my best interpretation:
Xyclops
X01202-002
A-A02
0408C65502.01
AA TAIWAN
Note the "8" in the second-to-last line may be a "B." Everything else I'm fairly sure about.
Edit: (clarification) This is the new chip by the LPC, not the video encoder. I'd try to read the markings off it, but they're rather obscured so anything I give you'd be an educated guess. Even then, we know what a video encoder does. The other chip is more interesting
Post by: Master-Chief on May 01, 2004, 05:42:00 PM
| QUOTE (tNCecil @ May 1 2004, 08:04 PM) |
| Possibly another delay for the X3? :| |
Possibly another delay for Xenium OS 2.0 I guess...
The later X3, the later OS 2.0!
I wonder what SmartXX and Xenium are going to do now. Make a new version of the chip? Possibly add the latest version of Xenium OS along with it for easier installations? Who knows!
Post by: Monoxide-Child on May 01, 2004, 05:55:00 PM
Post by: XB0X_Mod on May 01, 2004, 06:03:00 PM
Curious could you please get shots of the back of the motherboard, and also a closeup shotingh CLEARLY the MCPX / LPC AREA.
You'll see why when you get them to me
[email protected]
Thanks
Post by: derived on May 01, 2004, 06:17:00 PM
| QUOTE (Monoxide-Child @ May 2 2004, 02:55 AM) |
| I'm not coming up with anything on those numbers from the chip. |
I can't find anything about Xcalibur or Xyclops chips, let alone the numbers.
Could this mean that these are custom-made chips?
If this is the case, this could make it likely that the chips can only meet the specs of the Xbox, nothing more?.. no more flashable ROM or VGA encoder that linux can program for high-res/refresh rate VGA.
Post by: WaRnINg| on May 01, 2004, 06:29:00 PM
Lets just see what happens..
Please dont start creating 1.6 threads all over just keep it here
Post by: XanTium on May 01, 2004, 06:35:00 PM
| QUOTE (brywalker @ May 2 2004, 04:29 AM) |
| With such a radically different board design, I vote for calling this one a 2.0. |
v1.1 to v1.2 was also a big design change.
Anyway, the xbox with the new xcalibur videochip was named v1.6 some time ago already (when it was first announced as being one of the videochips in the MS XDK software). Call it v2.0 would only start confusing people (remember v1.1 was called v2.0 back then and confused lots of people when all xbox sites decided to uniformly call it v1.1)
keep v2.0 for the Xbox2 (Xbox Next, Xenon ... or whatever you want to call it).
Post by: Monoxide-Child on May 01, 2004, 07:01:00 PM
| QUOTE (derived @ May 2 2004, 03:17 AM) |
| I can't find anything about Xcalibur or Xyclops chips, let alone the numbers. Could this mean that these are custom-made chips? If this is the case, this could make it likely that the chips can only meet the specs of the Xbox, nothing more?.. no more flashable ROM or VGA encoder that linux can program for high-res/refresh rate VGA. |
I really doubt they are custom... I still believe that they are off-the-shelf with a new logo and numbers on top.
Post by: XBox-Savage (Clone) on May 01, 2004, 07:01:00 PM
whoa , M$ strikes back.I read the entire 6 pages and saw the pics.
so here are my guesses.
1. Xcyclops could be the new Bios Chip. (no under board pics yet so the TSOP could be under.)
2. The 4 pin chip on the right of the LPC must be the eeprom.
3. The LPC may have been redesigned to detect modchips together with the TSUNAMI upgrade.
4. This could be part of the new hardware design that will be used on XBox Next.
and ect.
If i were you , i would try to locate the D0 and try to install an Xecuter 2.3 or an Applex V , the bios wont work but if it frags it means that it might be modable , the only thing needed would be the bios that supports the video chip.
But also i would sell it to modchip designers , like Team Xecuter.
Post by: XanTium on May 01, 2004, 07:04:00 PM
This change is probably done in the first place to make productions cheaper - as that's most important for MS with their very expensive to produce Xbox. Ofcourse it's possible MS tried in meantime to make it harder for us.
What will probably needed at first ... find where the bios is on this new board, dump the new bios .... find the new "D0" (if any) and try to make a LPC mod with this 'original' MS bios work. That'll be the first try to see if there's any kinda of new protection and to see if it's still possible to boot from LPC.
Ofcourse 'hacked' bioses will need to get support for the new videochip before they even make a chance to boot. And it'll also have to be checked if there's maybe a new RC4.
As for the new videochip, Im a bit suprised MS is making their own chip. These v1.6 consoles are from end March 2004 ... was it still worth for MS to start making their own videochip?
Also note the new xcalibur videochip is not 1:1 (W:H) like the conexant/focus ... but wider.
Post by: XBox-Savage (Clone) on May 01, 2004, 07:04:00 PM
| QUOTE (NovaZero @ May 2 2004, 04:02 AM) |
| Manufacture date please? (So I can avoid this when I buy a new one) |
didnt you read the entire Thread?| QUOTE |
K: 1.00.5838.01 D: 1.00.5659.03 manufacture date.... 2004-03-22 |
Post by: sil247 on May 01, 2004, 08:12:00 PM
My opinon is that m$ has put a password to prevent people from changing hd,
using external chips and fashing the bios. The only way to use any of the above,
would be to desable the password on the securechip and we would have to get the
password from M$ or maybe is just nothing........ sorry,english is not my native langugue...
Post by: dethbunny on May 01, 2004, 08:20:00 PM
There has been no v1.6 LE reported yet, (this particular box is a regular black one) but there may very well be some in the channel. There are no guarantees as to Xbox version if the manufacture date is after mid-March or so, by current indications; if you want a V1.4 you'd best buy a 'box made in February or earlier just to be safe.
Post by: Arakon on May 01, 2004, 08:34:00 PM
@cheese: that's the PIC chip, it used to be above the tsop on the older models.. it controls powering on, resetting, and other things.
Post by: iamcheese on May 01, 2004, 08:41:00 PM
any way where are the underboard shots ... we need them badly
and would it be possible that the d0 is near the point labled r7d1?
Post by: Psilocybe on May 01, 2004, 08:41:00 PM
| QUOTE (Odium X @ May 2 2004, 05:02 AM) |
| Is the Limited Edition XBOX V6.0? |
technically yes some of them may be a version 6, aka 1.5. but most are version 5 aka 1.4
but this thread is for v7 aka 1.6
Post by: Jnadke on May 01, 2004, 08:54:00 PM
Looks like the BIOS must be on the Xyclops chip. The Xcalibur must be the new video chip. Probabaly an attempt to cut costs by making their own chips.
However, if they made their own chips, why wouldn't they integrate the EEPROM into the Xyclops as well?
The answer is that it's most likely still an off-the-shelf part, but renamed/re-etched.
The Xyclops chip is probabaly a Write-Once Programmable ROM.
Post by: RX3 on May 01, 2004, 09:11:00 PM
"hey dude. You know where I could find one of those old Xboxes that could be modded? Man, I'd give anything for one of those."
Post by: Arakon on May 01, 2004, 09:21:00 PM
Post by: XBox-Savage (Clone) on May 01, 2004, 09:27:00 PM
| QUOTE (drozek @ May 2 2004, 05:58 AM) |
| Well I am going to wal-mart next week or where ever i can find a halo limited xbox and try to find one of these suckers. |
is not a HALO XBox , those are v1.4/v1.5 ,but there could still be a v1.6 motherboard on a HALO Xbox.good luck ,
Post by: powercntrl on May 01, 2004, 10:21:00 PM
| QUOTE (RX3 @ May 2 2004, 12:11 AM) |
| If these new boards aren't moddable, in a year or 2 our Xboxes are gonna be like gold. Unlikely, but wishful thinking. "hey dude. You know where I could find one of those old Xboxes that could be modded? Man, I'd give anything for one of those." |
You'd be surprised... Once 1.6s start flooding the retail channels, you can bet the older, more easily-modded Xboxes will start going up in value on eBay. Probably not a crazy amount, but I'll bet people will pay more than retail.
Stock up on v1.4/v1.5s while you can if you want to beat the eBay rush!
Post by: seedyrom2003 on May 01, 2004, 10:33:00 PM
Post by: colibri on May 01, 2004, 11:03:00 PM
Post by: jokk on May 01, 2004, 11:13:00 PM
=> Convera Corp
Its formed out of excalibur coorp ( intel + buyout )
they produced semiconductors and videostuff...
could be related ? No idea
Post by: modrobert on May 01, 2004, 11:31:00 PM
| QUOTE (Arakon @ May 2 2004, 12:27 AM) |
| that small chip is the serial eeprom most likely. too few pins to hold the entire 256 kb bios. |
That 8-leg IC close to the LPC bus could be a SAIFUN (512kb/25Mhz) serial flash maybe, check this link for datasheet:
http://www.saifun.co...005-Jan2004.pdf
BTW;
A clear picture of that 8-leg IC would be nice, or if somone can read the label.
Post by: lordvader129 on May 01, 2004, 11:37:00 PM
| QUOTE (droobie @ May 2 2004, 02:49 AM) |
| It's possible that Xyclops and Excalibur are the code names for those particular chips, so finding data on them will be hard(er). |
i think its much more than possible, its damn likely, look at them, both have prominent X's in the name (Xcalibur, Xyclops)and both chips are screened with the xbox X logo, im sure they are retail chips, but with no retail ID left on them
i doubt MS is making the chips themselves, AFAIK they dont have any manufacturing setup to do that (being a software company) they wouldnt be able to save money buy building plants to construct these chips (unless they plan on making xbox2 more proprietary, but considering all the outside deals that have already been signed, doesnt seem liekly)
and my 2 cents is that the xyclops chip has got to be the TSOP (or this ones onboard bioschip)
whatsucks is that (as someone mentioned) its most liekly a write-once ROM
the LPC debug is still there (still labeled LPC debug) so it must be usuable, there must be a d0 somewhere, MS seems to have trimmed alot of fat with this board (in prep for the mini-xboxs?) so i doubt theyd leave the debug bus there if it was totally deactivated, we just need to figure out the pinout and how to force a boot
Post by: colibri on May 02, 2004, 12:04:00 AM
Post by: lordvader129 on May 02, 2004, 12:05:00 AM
| QUOTE (Arakon @ May 2 2004, 03:52 AM) |
| @lordvader: the lpc bus might be there, but it might not be usable for booting a bios anymore.. they could completely remove the possibility by changing the bios or the mcpx to refuse accepting a bios on the lpc port. |
i dont see why they would change the function of it that much, but your right, they could have changed something in the MCPX to prevent it from loading anything but an MS signed bios
Post by: pROvIs on May 02, 2004, 12:16:00 AM
I have a box here that is manufactured in march 11, 2004 and it is still a 1.4 with a focus chip
Post by: Pizza Pizz on May 02, 2004, 12:42:00 AM
Tsop may be out the window too - the easy peasy tsop pads or come to that any tracks used for flashing may be gone for good. Not hard for them to use a 5v operating tsop but a 12v flash routine chip...
I found a few dip32's that would flash using a 5v ID code in a pc's uniflash but under evox and raincoat it was identified as a different 12v flash ID code
EON 29F040 btw if you wanna look this dip32/plcc/tsop chip family up
used 041c - ergh i think it was in pc uniflash or was 1c04
entered both but evox/raincoat said it was 7f7f - the 12v flash routine and didn't seem to work very well - lumpy flashing bar in evox
(I gave up but may have another go at these homebrew chips one day through evox/raincoat in another mobo)
Didn't someone post about a xbox they bought in Hong Kong or somewhere that had the TSOP replaced with an intel one and thus was gonna need 12v to reflash it ?
Anyway they certainly have been busy reworking the mobo
All this is speculation and hope I am very wrong - please hope I am
I reckon the LPC is still gonna be the best bet though they may have changed the layout of it - reverse just 1 of the points used will mean newer mods needed if the points/layout are now upside down and back to front - heck they may have put the Lframe back in but don't hold ya breath - but change the pin layout and all the previous mods on header pins are out the window too
(suppose if they did that you could have a an adapter to change layout back to older lpc layout)
All this is loads and loads of speculation I agree but I'm in UK and probably - BLOOMIN' HOPEFULLY be a month or so before they spring up over here
The LPC has gotta be probed/tested to identify what is what
Besides - we probably gotta wait for a new bios that supports the Xcalibur video chip based on the recent bios
K: 1.00.5838.01
is this on some previous xbox's coz it's gotta be pulled off first before any of the Xecuter / Evox / Linux peeps can look at it
So if it ain't on say some 1.4's / 1.5's then hopefully linux raincoat can pull the bios of still on this new mobo
(did someone up this already a while back when we though all crystal xbox's were gonna have Xcalibur chips in ?)
Excuse the long post and me having a bit of panic in me raising loads of doubts/questions - but this is a much bigger change than ever before
1.2 changes still allowed old mods/bios to work just tsop was different size and the use of ST for evox but Winbond become quite common too needing raincoat
1.3's allowed older bios to work but lframe mods needed
1.4's new bios needed but tsop was still flashable
1.5's - ergh yeah not many but just a couple of wires to run for mods - tsop still cool
This bitch looks a whole new ball game - maybe xbox held back using xcalibur on nearly all 1.4's/1.5's a few months back thinking lets give them something to really chew on thus this 1.6 or 2.0 board whatever peeps wanna call it
(ver 2.0 is an option as it it really is a massive board change at first glance and maybe very little of the older mods/hacks may work on this at the moment)
Best of luck to all the hacking teams out there
Post by: Pizza Pizz on May 02, 2004, 12:50:00 AM
(they could of totally removed the test holes whilst they did the new board but the header pin holes are still there for some reason - perhaps they still use it a lot to test batches of boards etc....)
My money is on the LPC as still the best hope
(would be a bitch if homebrew's now use 29-31 tiny pin holes like the "top D0" connection point if the solder pads are gone underneath. TSOP may not be flashable via evox/raincoat no more if 12v flash needed)
lets hope the lpc can be probed/identified over the next few days - fingers crossed
Post by: walabie on May 02, 2004, 02:31:00 AM
Unless they fixed it in the kernel (it wasn't fixed in the last v1.4/5 kernek afaik) the gamesave exploits might still work. This might allow you to dump the new kernel/bios.
Then try to boot this new kernel/bios with the PBL. This doesn't say anything about booting from LPC, but it's a start.
I guess you can also give a try to boot cromwell ... as far as I know cromwell will boot even if videochip isn't supported (without screen output ofcourse - but you can try to telnet in or so). That would already tell if MS maybe fixed the methods to bypass the RC4 check.
Post by: bucko on May 02, 2004, 02:32:00 AM
, looks like a lot of changes on the motherboard. I only noticed that the space for extra ram chips was gone after looking again. Heck maybe this is what X3 have been waiting for, so they can support 1.6
Post by: shodanjr_gr on May 02, 2004, 05:01:00 AM
Post by: JayDee on May 02, 2004, 05:34:00 AM
| QUOTE (shodanjr_gr @ May 2 2004, 02:01 PM) |
| Damn, lots of interesting reading here, my head hurts. Despite not being too tech savvy as far as xbox hardware goes, i really think this is the first MAJOR change for the mobo. So i vote for version 2.0 |
1: check 1.0 vs 1.1 and you will see some major changes too.
2: there is no voting on this. It is a 1.6 not a 2.0 as that will be the xbox2 xenon or whatever ms will call it...
Post by: NFCTinken on May 02, 2004, 05:39:00 AM
Post by: derived on May 02, 2004, 06:04:00 AM
| QUOTE (lordvader129 @ May 2 2004, 08:37 AM) |
| i doubt MS is making the chips themselves, AFAIK they dont have any manufacturing setup to do that (being a software company) they wouldnt be able to save money buy building plants to construct these chips (unless they plan on making xbox2 more proprietary, but considering all the outside deals that have already been signed, doesnt seem liekly) |
MS doesn't have to make the chip for it not to be an off-the-shelf chip.
With Xbox 2 they'll be buying shiploads of ROMs and video encoders, so its not impossible that they went to a chip maker and said "this is what we want, whats the cheapest you can make it for?"
Post by: brywalker on May 02, 2004, 07:54:00 AM
| QUOTE |
| 2: there is no voting on this. It is a 1.6 not a 2.0 as that will be the xbox2 xenon or whatever ms will call it... |
2.0 would be the XBOX2? Are you retarded? Its a completely different system. Why would it follow the numbering scheme of the XBOX? So the first revision GameCube motherboard would be V 35.0 because of all the other systems before it?
Post by: M@n!ac on May 02, 2004, 08:03:00 AM
AV: Conexant TV encoder
_Conexant_CCRegisters
Conexant_CCRegisters
AV: Focus TV encoder
_Focus_MacrovisionHamp
Focus_MacrovisionHamp
AV: XCalibur TV encoder
_XCalibur_RSM53Regs
_XCalibur_RSMRegs
_XCalibur_RSMRegAddr
XCalibur_RSMRegAddr
XCalibur_RSMRegs
XCalibur_RSM53Regs
Post by: heinrich on May 02, 2004, 08:03:00 AM
Just drop it already, jeez.
Post by: CHRONOSTORM on May 02, 2004, 08:28:00 AM
try soft mod exploit and attempt anyway u can think of to extract the damn bios.
it was said the d0 looks to be in the same place. well ground that ho and see if it bypasses the bios.
if it works w00t!! then if u extracted the bios then try it on a chip.
simple testing that can be done by a n00b.
Post by: Monoxide-Child on May 02, 2004, 10:03:00 AM
Besides, why would M$ order X million units of a read-only bios, when if they updated the firmware, they'd have to order a whole new batch of chips? They are trying to cut costs, not increase waste.
The Bios being on the HDD is a total impossibility. The Bios controls HDD functions (not to mention unlocking the HDD so it can be accessed), so it's not possible for the XBox to load a Bios from the HD.
The serial EEPROM that everyone keeps thinking could be large enough for a Bios could not be. It's only 256kbits, maybe 512kbits. The old TSOP on a 1.2-1.4 was 2Mbits, or 256kbytes. 1 byte = 8bits. Besides, that same EEPROM was on all the previous XBox's. I'm not certain, but it probably holds the key for your locked HDD.
Underboard shots will be necessary. Hands down. Without those, though, these are about as solid a fact you can get from the previous pictures, and the way that computers function.
Post by: KingViper on May 02, 2004, 10:09:00 AM
I dont know about anyone else, but I think this is more exciting than anything. This is gonna give another shot of adrenaline to the xbox community.
KingViper
Post by: lordvader129 on May 02, 2004, 10:48:00 AM
| QUOTE (M@n!ac @ May 2 2004, 12:50 PM) |
| No, the crystal LE xbox has a Focus video encoder chip inside. |
someone found an xcalibur chip in a crystal LE, he never took any pics, i dont know if it had the full 1.6 motherboard though
at first i though it was just a hoax, since he never posted any pics and kinda vanished, but now seeing the xcalibur chip in this i guess it was real
Post by: fujitech on May 02, 2004, 11:05:00 AM
NO CRYSTAL HAS XCALIBER VIDEO DECODER
a reference to that video decoder was made in latest XDK
They presumed that crystal would have the new video decoder!
Post by: M@n!ac on May 02, 2004, 11:22:00 AM
| QUOTE (lordvader129 @ May 2 2004, 07:48 PM) |
| someone found an xcalibur chip in a crystal LE, he never took any pics, i dont know if it had the full 1.6 motherboard though at first i though it was just a hoax, since he never posted any pics and kinda vanished, but now seeing the xcalibur chip in this i guess it was real |
No. He had been able to get a Crystal Xbox and the video chipset had the inscription "XLB" and not "Xcalibur".
http://www.xbox-scen...FZpJDPGBATA.php
Post by: XanTium on May 02, 2004, 11:28:00 AM
Post by: Monoxide-Child on May 02, 2004, 11:42:00 AM
| QUOTE (fasmanza @ May 2 2004, 08:07 PM) |
| it seems M$ are replacing all the standerd chips with their own, Whats next no more pentuim 3 cpu's but Xentuim and Xvidia? |
M$ owns no foundry. They are paying someone to screen their logo and their numbers onto an off-the-shelf chip. Though it is possible, I sincerely doubt that Intel and nVidia will do the same. Their chips were one of the XBox's selling points.
M$ is a software company, that has started marketing their console. Every part of the XBox, down to final assembly, is contracted out. The new chips are silkscreened with their logo, probably as a part of a contract with the foundry to get them cheaper.
Post by: heinrich on May 02, 2004, 01:03:00 PM
| QUOTE (Kraven_UK @ May 2 2004, 05:31 PM) |
| Further to my previous posts, I have now checked for alignment of the new D0 point to the older points, I look like it is not in the same place. But untill I can get some images of the 2 boards that are taken at the same angle I can only guess. What I thought was the D0 point is around 1/4mm out of place. |
what are you talking about? I dont see how you can possibly even guess where a point would be by simply looking at a picture. Furthermore, I believe that 'd0' refers to a data line, specific to the TSOP packaging type; no tsop = no d0. Feel free to correct me if I am mistaken..
Post by: fujitech on May 02, 2004, 01:06:00 PM
Post by: Kraven_UK on May 02, 2004, 01:08:00 PM
| QUOTE (heinrich @ May 2 2004, 10:03 PM) |
| Furthermore, I believe that 'd0' refers to a data line, specific to the TSOP packaging type; no tsop = no d0. Feel free to correct me if I am mistaken.. |
You maybe right. I always thought the D0 acted as a switch to allow booting from the LPC. and had nothing to do with the TSOP.
And just because the 'Normal' TSOP has gone does not mean to say it's not there!
Whats more, as my posts said I'm only guessing, just like everyone else here.
Post by: Zomas on May 02, 2004, 01:13:00 PM
| QUOTE (M@n!ac @ May 2 2004, 08:22 PM) |
| No. He had been able to get a Crystal Xbox and the video chipset had the inscription "XLB" and not "Xcalibur". |
This guy didn't have a Crystal Limited Edition XBOX which is only sold in europe. He had a australian Special Halo Edition XBOX which is clear green. When people started asking for pictures he dissapeared. All other people in that thread reported that their Halo Edition's had Focus encoders.
http://forums.xbox-s...howtopic=183657
Post by: pROvIs on May 02, 2004, 01:59:00 PM
Two of the mare spoken for. Make me an offer if you want the last one PM me. you can try emailing me at [email protected] but my email has been down over the weekend so best way is PM
Also i have only opened one so far (i will check others before shipping them) and it had a seagate with a phillips drive.
Edit: Update all three checked and confirmed 1.6s. All have phillips and Seagates. PM of Email me if interested @ [email protected]
Post by: Zomas on May 02, 2004, 02:18:00 PM
| QUOTE (TigerHawk @ May 2 2004, 10:39 PM) |
| No, he didn't have a Halo Xbox... he said it if you read the whole thread... he said it was normal |
Ehm?...seems to me it is YOU who didn't read the whole thread.
| QUOTE (bourke @ Mar 3 2004, 12:22 PM) |
| I have just opened my spanking new green Crystal Limited Edition Xbox |
| QUOTE (A.Z.BEST® @ Mar 5 2004, 12:10 PM) |
| Heh, green crystal . I hope bourke can answer before 12 march . |
| QUOTE (bourke @ Mar 6 2004, 04:44 PM) |
| It's like the boring white one shown here: http://www.ladydragon.com/020204.html Except the Australian ones are coloured a groovy GREEN! They are boxed with Halo and a matching green controller. |
| QUOTE (bourke @ Mar 12 2004, 12:09 PM) |
| OK, I had a customer just bring their Green Halo edition Xbox in and it had: * Philips DVD - Manufactured: December 03 - also reads CDRs :-) * Focus video decoder * Kernel 5713 I successfully TSOP flashed it with the EvoX M7. Seems like some of them are version 1.5 maybe? |
| QUOTE (A.Z.BEST® @ Mar 17 2004, 12:29 PM) |
| bourke, can you tell me, are you from Australia or from Asia, cause my friends are very confused about that Halo edition pack (Halo fans )... where did you get one? |
| QUOTE (bourke @ Mar 21 2004, 12:52 PM) |
| Yes, I am from Australia - the Halo pack sells for about US$240 here. |
| QUOTE (mac4drew @ Apr 13 2004, 05:37 AM) |
| OK I have a question about exactly which XBox you have because what you have said names two separate XBoxes... there is the European Limited Crystal Edition which is clear white and the XBox special Halo edition which is clear green. I think everyone on this thread believes you are talking about the European Limited Crystal Edition when you are actually talking about the Halo Special edition |
Post by: heinrich on May 02, 2004, 02:29:00 PM
| QUOTE (Kraven_UK @ May 2 2004, 06:08 PM) |
| You maybe right. I always thought the D0 acted as a switch to allow booting from the LPC. and had nothing to do with the TSOP. |
And d0 does act as a switch, by reading data from the tsop. grounding this line results in an error in reading, and the xbox boots from the lpc bus.
| QUOTE |
| And just because the 'Normal' TSOP has gone does not mean to say it's not there! Whats more, as my posts said I'm only guessing, just like everyone else here. |
| QUOTE |
| TSOP Type I / Type II Thin Small Outline Package TSOP packages are thin body size components; thickness is 1.0mm. TSOP packages have four sides and are rectangular. Type I TSOPs have the leads protruding from the width portion of the package. Type II TSOPs have the leads protruding from the length portion of the package. Lead counts range from 28 to 48. Package body size ranges from 8 x 14mm to 12 x 20mm. |
Where do you see a chip that matches that matches that description ? Besides the "ICS" chip, which exact function seems to be disputed, but it definitely on every previous xbox version, located right 'above' the serial eeprom.
Again, feel free to correct me if I am wrong..
Post by: Pope-X on May 02, 2004, 02:54:00 PM
Just run raincoat with the 007 hack .... it should still work... since its a game bug.. not a hardware bug..
b shure to only dump the bios with raincoat...
this should still workand then make the bios available.. so we can make a compare with the old bioses.
Regards,
Pope-X
Post by: heinrich on May 02, 2004, 03:02:00 PM
| QUOTE (Pope-X @ May 2 2004, 07:54 PM) |
| and then make the bios available.. so we can make a compare with the old bioses. |
both 5530 and 5713 support all 3 known video encoders, and both kernels have been on xbins for a while.
Post by: bcforn64 on May 02, 2004, 03:26:00 PM
Post by: DaShiZNiT on May 02, 2004, 03:37:00 PM
UNKNOWN DEVICE
Post by: hippo on May 02, 2004, 03:43:00 PM
Post by: Psilocybe on May 02, 2004, 03:55:00 PM
Post by: Exobex on May 02, 2004, 04:04:00 PM
| QUOTE (Pope-X @ May 2 2004, 11:06 PM) |
| its also to see what raincoat says the bios chip id is and who knows for shure that the bios is the same... dump the bios.. and then try to flash the bios with that dumped bios .. (should not hurt...) then we will know if the chip is write disabled.. mayb m$ made it easyer AGAIN... so no more soldering is needed to flash the bios ... (this would b hillarious) Regards, Pope-X |
Raincoat is likely to report INVALID MANUFACTURER ID: 0x09
At least one of the TSOP flashing jumpers will need to be located in order to read the chip. Both will be needed in order to write the chip.
I assume the TSOP connects to the MCPX.
Therefore if the pins from, say, a 1.4 machine's TSOP can be traced to the little vias that are visible on the 1.4 MCPX, the same vias on a 1.6 MCPX can then be traced back, revealing which chip is the new BIOS chip.
We already know the pinout of a 1.4 TSOP (it's standard!), by doing this we will reveal at least a partial pinout of the MCPX, and from there a partial pinout of the 1.6's BIOS chip.
This can be compared with existing "off-the-shelf" memory devices. If the data and address lines correspond with one of these, we can guess that the rest of the pins match up, too.
The TSOP write-enable jumpers go to two pins on the TSOP. These pins on the 1.6 BIOS can be traced back to see if they go to anything resembling write-enable jumpers.
On a different note, M$ don't need to own chip foundries to get their logo on chips. Look at SmartXX!
Post by: Yoshihiro on May 02, 2004, 04:07:00 PM
Info Encoder ID : 8A=Conexant , 0D4=Focus & 0E0=Xcalibur
you need to make a new init table to be able to launch this bios
Support Xcalibur in kernal 5530 extract by Yoshihiro
.text:80014899 ; ---------------------------------------------------------------------------
.text:80014899
.text:80014899 loc_80014899: ; DATA XREF: sub_800148F0+8o
.text:80014899 mov eax, ds:xboxkrnl_322
.text:8001489E test ah, 4
.text:800148A1 mov dword_800377F0, offset loc_8001487F
.text:800148AB jz short loc_800148BA
.text:800148AD push 0Fh
.text:800148AF push 4
.text:800148B1 push 4
.text:800148B3 push 0E0h ;ID ENCODER XCALIBUR IN 5530
.text:800148B8 jmp short loc_800148E6
.text:800148BA ; ---------------------------------------------------------------------------
.text:800148BA
.text:800148BA loc_800148BA: ; CODE XREF: .text:800148ABj
.text:800148BA test al, 20h
.text:800148BC jz short loc_800148D1
.text:800148BE push 20Fh
.text:800148C3 push 2
.text:800148C5 push 0A0h
.text:800148CA push 0D4h ;ID ENCODER FOCUS IN 5530
.text:800148CF jmp short loc_800148E6
.text:800148D1 ; ---------------------------------------------------------------------------
.text:800148D1
.text:800148D1 loc_800148D1: ; CODE XREF: .text:800148BCj
.text:800148D1 push 3Fh
.text:800148D3 push 1
.text:800148D5 mov dx, 80D3h
.text:800148D9 mov al, 5
.text:800148DB push 0BAh
.text:800148E0 out dx, al
.text:800148E1 push 8Ah ;ID ENCODER CONEXANT IN 5530
.text:800148E6
.text:800148E6 loc_800148E6: ; CODE XREF: .text:800148B8j
.text:800148E6 ; .text:800148CFj
.text:800148E6 call sub_800146D1
.text:800148EB mov al, 1
.text:800148ED retn 4
.text:800148F0
Work in progress ......... wait & see
Sorry for my english very bad
GueuX'NeT French Team Web Site
Post by: derived on May 02, 2004, 06:29:00 PM
| QUOTE (busbyjon @ May 2 2004, 09:14 PM) |
| they can screen their logo onto the chips. This might be no more than a PR stunt to us modders... |
It just seems like such a pathetic thing to do... within a minute a hacker can read the flash (assuming it is) ROM ID from the chip and the cover is blown.
Post by: pROvIs on May 02, 2004, 06:44:00 PM
Two are going to the SmartXX team, the last one is up for the best offer.
all have phillips drives and seagates all from 3-22-04
Email me @ [email protected] if interested
Also i appolagize for my pics i cant seem to get very good ones but i will post what i have shortly
Post by: RoboChicken on May 02, 2004, 06:50:00 PM
| QUOTE (pROvIs @ May 3 2004, 03:44 AM) |
| ALL THREE OF MY XBOXS ARE NOW CONFIRMED 1.6 Two are going to the SmartXX team, the last one is up for the best offer. all have phillips drives and seagates all from 3-22-04 Email me @ [email protected] if interested Also i appolagize for my pics i cant seem to get very good ones but i will post what i have shortly |
I say donate the last one to Bunny!
Bottom pics please! This is driving me crazy!! I'm about to go out and buy five Xboxs
Post by: pROvIs on May 02, 2004, 06:52:00 PM
| QUOTE (RoboChicken @ May 2 2004, 09:50 PM) |
| I say donate the last one to Bunny! Bottom pics please! This is driving me crazy!! I'm about to go out and buy five Xboxs |
bunny?
Post by: oz_paulb on May 02, 2004, 07:14:00 PM
- getting custom silkscreening on a chip doesn't require a foundry
- My understanding of MS's new deal with IBM for CPUs is that they get the 'core' design - which sounds like MS may be doing their own chip manufacturing in the future (for Xbox 2). So, they could be setting up their own foundry (or have a close relationship with a foundry). Given this, MS could be manufacturing custom chips right now.
- Unless it's on the bottom of the board, the BIOS is probably inside another chip. My guess is that it is now ROM (not Flash), as they have probably reached a point where they consider the kernel stable enough for mass production. If a critical change is required, they'd have to discard some mask ROMs. But, considering that games will have to work with Xbox's shipped with the kernel in today's 1.6 Xbox, there can't be a required kernel change unless there are hardware changes (like a new video encoder) in the future.
- "d0" refers to the signal for the lowest data bit that happens to be connected to the TSOP chip on older Xbox's. There is a separate 'bus' coming out of the MCPX (separate from SDRAM, for example) that's used for the TSOP. The MCPX first tries reading the first address from this "TSOP bus". If the low bit (d0) is "0", then it knows that it should boot from LPC (the first byte of a TSOP bios has a '1' in bit 'd0'). This would allow MS to remove the TSOP, permanently strap "d0" on the "TSOP bus" to "0", and build-in an LPC boot ROM instead. It also (most likely) allows their factory test process to override the TSOP bios with a 'factory test bios' that does diagnostics/QC testing. It's possible that they also load the TSOP Flash with the 'final' BIOS at the factory via LPC - but they could also just manufacture the motherboards with pre-programmed Flash chips.
- Given the fact that v1.6 has an LPC connector, it's probably still used for factory testing, which means there's some hope for booting custom code via LPC. It doesn't necessarily mean that the built-in BIOS is stored in a re-writable Flash - it could be masked ROM as I said above.
- The physical location of "d0" on the motherboard is likely to change from one version of the motherboard to another. There may be a factory requirement to keep it in the exact same spot (in relation to LPC, for example) if they use some sort of 'bed of nails' adapter to connect to "d0". But, they could just use a different bed of nails configuration for a new motherboard.
- If MS has changed the MCPX as well, then their method of detecting 'LPC boot' vs 'internal boot' could also have changed. If there's no TSOP bios chip (example: they may use LPC internally), then there may be no need for the 'TSOP bus', so all of those signals (address/data lines/etc) could be re-assigned to different uses. Maybe a specific combination of (formerly) address/data line signals needs to be held low/high in order to boot from the 'external' LPC port. A factory bed of nails can hold any number of signals any way they need.
- It still would be a good idea to try tracing "d0" back to the MCPX on earlier versions of the Xbox, then try strapping that signal low (at the MCPX) on the 1.6 Xbox, to see if it's still usable. MS may not have made very drastic changes, so this could still be a simple way to force an external LPC boot.
- Paulb
Post by: jimmsta on May 02, 2004, 07:34:00 PM
Post by: Monoxide-Child on May 02, 2004, 07:42:00 PM
| QUOTE (jimmsta @ May 3 2004, 04:34 AM) |
| Interesting find... It's rather odd that the board design changed almost completely, as the xbox is years old... it's surprising that this didn't happen sooner. |
Erm... we've been over this. 1.0/1.1 to 1.2-1.5ish was a significant change also.
Post by: volcomman2003 on May 02, 2004, 07:48:00 PM
happy findings cant wait to see fi there is anyhting new for this baby
Post by: Monoxide-Child on May 02, 2004, 08:30:00 PM
http://www.damnned.n...ng/frontlpc.jpg
http://www.damnned.n...acking/rear.jpg
http://www.damnned.n...ing/rearlpc.jpg
http://www.damnned.n...hacking/top.jpg
http://www.damnned.n...ng/xcalibur.jpg
http://www.damnned.n...ing/xyclops.jpg
http://www.damnned.n...cking/p39a0.jpg
The p39a0 is on the bottom side of the board... it certainly looks like it could be out TSOP, but without numbers for reference or higher res, I can't be sure.
Please be kind to my bandwidth!
Post by: brahm2 on May 02, 2004, 08:39:00 PM
http://www.brahm2.com/xs/1.6/p39a0.jpg
http://www.brahm2.com/xs/1.6/rear.jpg
http://www.brahm2.co...1.6/rearlpc.jpg (very big, very blurry)
-------- edit: smaller, slightly sharpened w/ photoshop http://www.brahm2.co....6/rearlpc2.jpg
http://www.brahm2.com/xs/1.6/top.jpg
http://www.brahm2.co....6/xcalibur.jpg
http://www.brahm2.co...1.6/xyclops.jpg
Here's a mirror.
Post by: lordvader129 on May 02, 2004, 08:39:00 PM
| QUOTE (brahm2 @ May 3 2004, 12:39 AM ) |
| http://www.brahm2.com/xs/1.6/rearlpc.jpg (very big, very blurry) |
yeah. that one hurts my eyes, they keep twitching try to focus, lol
Post by: pROvIs on May 02, 2004, 08:40:00 PM
and the flamers. haha sorry for the bad resolution my camera sucks. anyway like i said i have one left contact me. [email protected] or AIM: provis420
Post by: Monoxide-Child on May 02, 2004, 08:40:00 PM
| QUOTE (lordvader129 @ May 3 2004, 05:39 AM) |
| hmm, im still thinking the xyclops is the TSOP that p39a0 seems way out of place (physically) to be the TSOP, plus it doenst look like any bioschip ive ever seen |
Yet the Xyclops does?
Post by: lordvader129 on May 02, 2004, 08:42:00 PM
| QUOTE (Monoxide-Child @ May 3 2004, 12:40 AM) |
| Yet the Xyclops does? |
it almost look sliek a socketed bioschip out of its socket, with more pins, lol, but some of the pins dont lead to any traces (unless they are underneath the first layer of the board)
Post by: KingViper on May 02, 2004, 08:47:00 PM
I wonder if there are going to be many more revisions in the near future. If M$ is going to release a new "smaller" version of the xbox, this v1.6 could be in preperation for that. It is possible that they are releasing newer motherboards, with electronically compact designs that could easily be compacted. That way they actually have the same parts on both the standard xbox and the compact one, which would save alot of money. This could also be the reason for the disappearing memory spaces.
Now we just need to wait and see what people make of this. It will be interesting.
KingViper
Post by: Devastate on May 02, 2004, 08:58:00 PM
http://www.motion-me...s/oem/index.htm
Possibly a CODEC Chip?
Post by: rms2001 on May 06, 2004, 04:10:00 PM
| QUOTE (lookformeb @ May 6 2004, 05:35 PM) |
| Been covered. |
Okay cool. Must have missed that in my reading.
Post by: Mr. Tom on May 06, 2004, 05:42:00 PM
Post by: lookformeb on May 06, 2004, 05:55:00 PM
didn't read correctly...
Full Album with high res pics can be viewed: here
I got two and am willing to get rid of one... PM me.
This post has been edited by lookformeb: May 7 2004, 01:31 AM
Post by: 67thRaptorBull on May 06, 2004, 06:06:00 PM
so how available are these new boards? anyone else get a V1.6?
what did/are you (the people that have V1.6's) gonna do with them?
and anything interesting discovered yet?
wow, what a find
this new board looks so much more alien then the V1.0's ive been working with for the last 3 years..................
This post has been edited by 67thRaptorBull: May 7 2004, 01:07 AM
Post by: 919 on May 06, 2004, 06:15:00 PM
| QUOTE |
| QUOTE (Mr. Tom @ May 6 2004, 08:35 PM) I just picked up mine at EB, manufacture date april 2nd. I'm uploading pics now You're saying you have a 1.6 manufactured on 03/02/04? Interesting... I've purchased several Xboxes around that date and had no 1.6's... |
No he said April 2 (4/2). Just thought I would point that out.
Post by: Mr. Tom on May 06, 2004, 07:26:00 PM
http://www.crackheadindustries.com/shit/xbox/PICT0275.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0276.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0277.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0278.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0279.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0280.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0281.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0282.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0283.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0284.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0285.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0286.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0287.JPG
http://www.crackheadindustries.com/shit/xbox/PICT0288.JPG
All the pictures are around 800kb
Some of them are really blurry, my camera has focus issues sometimes :/
I just took a bunch of random pics, so if anyone wants to see something specific let me know. Ill edit this post to show my kernal/dash version in a minute, i never even turned it on, i just opend it :D
Post by: Vinvin on May 06, 2004, 10:39:00 PM
my xbox manufactured on 03/15/04
Still V1.4....
Asia/j Set..
Post by: Mr. Tom on May 06, 2004, 10:48:00 PM
Damn that voided warrenty!
It took me less than 6 hours to destroy this xbox, thats a new record for me!
This post has been edited by Mr. Tom: May 7 2004, 05:51 AM
Post by: Josh Adams on May 06, 2004, 10:50:00 PM
They have cracked the v1.6 already!
http://www.ozxodus.com/modules.php?name=Ne...=article&sid=29 says:
| QUOTE |
Team OzXodus proudly announces another groundbreaking achievement for the Xenium. In less than a week from the first sighting of the new Version 1.6 motherboard, we have worked round the clock and now have our premium product, the Xenium, up and running. Once our new OS2 is inline and updated, the Xenium will truly live up to its billing as the premium chip on the market. For the meantime, Xenium solder less will not work as there is need to solder five jumpers under the mother board. For those of you who are interested, we have posted a picture showing clearly where the D0 is located. (Although it is no longer needed in the 1.6, it can still be used to toggle between LPC and standard flash bus interface). We have also included a video showing version 1.6 controlling the Xenium debug LED. We would like to take this opportunity to invite all of you over to our forums at www.ozXodus.com , where we will be discussing and working on all development and release issues exclusively. So if you want to hear news first , join us there! Xenium. Discover a whole new Xperience! |
They also posted this photo of the new d0
And have uploaded a movie of here!
I always had faith that OzXodus would come thru with the goods!
I would even consider myself an OzXodus fanboy now, congratulations to the team on their awesome work.
Post by: mcw on May 06, 2004, 11:00:00 PM
I haven't seen any topics in the OZX forums (the announcement says to join the forums for the latest - but they haven't even put the current announcement in... guess I'm too early)
Post by: lenballs on May 06, 2004, 11:05:00 PM
Great work.
Post by: Mr. Tom on May 06, 2004, 11:07:00 PM
Do you mean there were 5 points to bridge? or 5 points to solder to?
This post has been edited by Mr. Tom: May 7 2004, 06:09 AM
Post by: mcw on May 06, 2004, 11:13:00 PM
| QUOTE (Mr. Tom @ May 7 2004, 01:00 AM) |
| Well let us take a moment of silence to honor the the brave xboxen whom didnt make it (mainly mine) Do you mean there were 5 points to bridge? or 5 points to solder to? |
Good question.. then I wonder whether they made it Xenium specific (i.e. soldering to specific components on the Xenium - don't think they would do that, but, hey.. in the current modchip race, you never know what someone will do)
And - will they announce it now, or just let the video sit for a while until the other teams come up with something?
Damn. So anxious.
Post by: Mr. Tom on May 06, 2004, 11:17:00 PM
| QUOTE (_Cold_Fusion_ @ May 7 2004, 08:02 AM) |
| just a bummer they didnt explain how.. :/ |
They will, give it time. I mean really, how can they sell a modchip without explaining how to install it?
Post by: echto on May 06, 2004, 11:17:00 PM
Post by: BenJeremy on May 12, 2004, 07:09:00 AM
| QUOTE (GR8R-X @ May 12 2004, 07:50 AM) |
| I know this post is a couple of pages old, but it has to be said... That label you have noted as a v1.4, I believe that sticker to be BS. I don't know where it came from, but I have never seen one like it. All the Xbox's I have done have had a serial sticker almost identical to the v1.6 picture. The only difference is the serial number, man. date, etc. |
Actually, I've seen labels like that, I'll have to check the three Xboxes I have at my house tonight to confrim.
Don't knock the guy. He posted PICTURES of said label. The label differences might not be too significant, other than the factory the Xbox came from (though I thought all new ones were out of China)
Post by: lookformeb on May 12, 2004, 08:16:00 AM
| QUOTE (BenJeremy @ May 12 2004, 10:09 AM) |
| Actually, I've seen labels like that, I'll have to check the three Xboxes I have at my house tonight to confrim. Don't knock the guy. He posted PICTURES of said label. The label differences might not be too significant, other than the factory the Xbox came from (though I thought all new ones were out of China) |
Agreed. Seen tons of them. GR8R-X, your opinion of it being a knock off quite ignorant...
BJ, you're right.. they do all come out of China now. Curious though.. why do they use two different codes (05/06) for the same country? Perhaps they have two factories.. i dont know.
Post by: Exobex on May 12, 2004, 10:53:00 AM
| QUOTE (xbill @ May 12 2004, 02:44 PM) |
| That's why I was trying to get read-write permissions in linux, so I could change the raincoat.conf that contains the device IDs. I was wonding if the device could be a microcontroller with on-board flash. Something like ST's uPSD325X series |
It may be that the chip ignores any "identify device" commands. When I was gathering flash types for raincoat.conf 0.7 I came across a manufacturer that offered versions of its flash with no device ID.
You'll have to use raincoat 0.5 or 0.501 to read the chip. Raincoat 0.7 won't touch it if it has an invalid ID, no matter what you put in the raincoat.conf file. This feature was added because noobs kept adding a 0x0900 flash line to their conf file thinking that it would somehow cure their bad soldering job.
Post by: Red-vs-Blue on May 12, 2004, 05:11:00 PM
No, I don't want to know if this is a V 1.6 box.
I am only posting this info for community use and historical purposes.
Just traded in my old xbox for the last Halo SE bundle at my local EB. The old one was giving me memory write errors and crashing very occasionally. Besides, they have a helluva trade-in deal on old games and for the bundle right now.
This may be the first reported Halo SE V 1.6.
MFG. DATE: 2004-04-04
SN 6012874 41505
PID 161 6012874 41505
K: 1.00.5838.01
D: 1.00.5659.03
My torx set is at home, but I will try to pop it open and get pics later in the weekend.
Post by: oz_paulb on May 12, 2004, 07:27:00 PM
| QUOTE (xbill @ May 12 2004, 03:44 PM) |
| That's why I was trying to get read-write permissions in linux, so I could change the raincoat.conf that contains the device IDs. I was wonding if the device could be a microcontroller with on-board flash. Something like ST's uPSD325X series |
The point I was trying to make is that the command sequence that's issued in order to read the manufacturer/device ID is different, depending on the manufacturer.
I haven't looked at 'raincoat.conf' in a while, but I wouldn't be surprised if it just has a list of manufacturer/device IDs that are used to identify chips. The problem is: how do you read the manufacturer/device ID in the first place, if the method is different across different manufacturers (there is some standardization, but it's not 100% standardized).
For example, to read the manufacturer/device ID on a specific SST chip I've used, you issue the following write commands:
| CODE |
| Write 0xaa to Flash offset 0x5555 Write 0x55 to Flash offset 0x2aaa Write 0x90 to Flash offset 0x5555 |
At this point, you can read addresses 0 and 1 to get the manufacturer/device IDs.
On a specific AMD chip, the 'identify device' command sequence is:
| CODE |
| Write 0xaa to Flash offset 0xaaa Write 0x55 to Flash offset 0x555 Write 0x90 to Flash offset 0xaaa |
(again, reading from addresses 0/1 at this point will get the device/manufacturer ID)
On an Intel flash, you just:
| CODE |
| Write 0x90 to any Flash offset |
There are also differences in whether you read from addresses 0/1, or 0/2 (taking into account byte-mode vs word-mode. Each Flash chip manufacturer seems to do things a bit differently.
(there is also a standard called "CFI" (Common Flash Interface) that tries to get around the incompatibilities, but it's not 100% adopted)
So, it's possible that 'raincoat' has code to support reading manufacturer/device IDs from several Flash manufacturers (using several methods), but it's unlikely that it supports all methods of reading device IDs. As I said, I suspect that 'raincoat' has code to support Flash chips that were known to exist on the Xbox (the TSOP flash chips in pre-1.6 Xbox's) - there's a multitude of Flash/EEPROM chips out there that could be inside the 1.6 Xbox, which may/may not be compatible with 'read identifier' command sequences supported by 'raincoat'.
So, even if there were a writeable Flash inside the Xbox 1.6's chipset, it's not necessarily the case that 'raincoat' could be made to recognize it (even if you update the '.conf' file). (unless, of course, you modified the raincoat source code)
But, as I said, my guess is that the BIOS memory inside Xbox 1.6 is ROM, so it's all a moot point. I could be wrong, though...
- Paulb
Post by: BenJeremy on May 12, 2004, 07:37:00 PM
...The project I'm working on right now involves a product that incorporates a FlashROM for pre-production, and well into production. It's a far more static device than an Xbox, which has had quite a few kernel revisions over it's life cycle already, and expects to have a few more down the road.
The move to a Masked ROM is costly up front - time and money are needed to prepare a part, and any changes in code means that you need to retape the part, introducing a lot of overhead. My product will probably see volumes near to what the Xbox has. Even so, we are rethinking the MaskedROM, as the unit cost savings may not be justified by the up front expense of masking.
In other words, M$ had a custom chip built, but if it's ROM, then any changes means they have to RE-ENGINEER the chip. Masking isn't overly complex, but it does impose cost and time penalties. The smart money might be on the fact that M$ custom built a flash interface into the Xyclops to hedge their bets on the engineering costs for the inevitable Kernel updates.
Anyway, just my 2 cents worth to the technical discussion here.
Post by: BenJeremy on May 13, 2004, 03:04:00 AM
Post by: modrobert on May 14, 2004, 08:29:00 PM
| QUOTE (oz_paulb @ May 13 2004, 03:27 AM) |
| So, even if there were a writeable Flash inside the Xbox 1.6's chipset, it's not necessarily the case that 'raincoat' could be made to recognize it (even if you update the '.conf' file). (unless, of course, you modified the raincoat source code) But, as I said, my guess is that the BIOS memory inside Xbox 1.6 is ROM, so it's all a moot point. I could be wrong, though... - Paulb |
You are probably right...
The raincoat 0.5+ found at xbox-linux project supports 28xxx and 29xxx protocol according to Andy's comments. Here is a snip from BootFlash.c:
| CODE |
| if(nTries!=1) { // 29xxx protocol // make sure the flash state machine is reset pof->m_pbMemoryMappedStartAddress[0x5555]=0xf0; pof->m_pbMemoryMappedStartAddress[0x5555]=0xaa; pof->m_pbMemoryMappedStartAddress[0x2aaa]=0x55; pof->m_pbMemoryMappedStartAddress[0x5555]=0xf0; // read flash ID pof->m_pbMemoryMappedStartAddress[0x5555]=0xaa; pof->m_pbMemoryMappedStartAddress[0x2aaa]=0x55; pof->m_pbMemoryMappedStartAddress[0x5555]=0x90; pof->m_bManufacturerId=pof->m_pbMemoryMappedStartAddress[0]; pof->m_bDeviceId=pof->m_pbMemoryMappedStartAddress[1]; pof->m_pbMemoryMappedStartAddress[0x5555]=0xf0; pof->m_fDetectedUsing28xxxConventions=false; // mark the flash object as representing a 28xxx job } else { // 28xxx protocol, seen on Sharp // make sure the flash state machine is reset pof->m_pbMemoryMappedStartAddress[0x5555]=0xff; // read flash ID pof->m_pbMemoryMappedStartAddress[0x5555]=0x90; pof->m_bManufacturerId=pof->m_pbMemoryMappedStartAddress[0]; pof->m_pbMemoryMappedStartAddress[0x5555]=0x90; pof->m_bDeviceId=pof->m_pbMemoryMappedStartAddress[1]; pof->m_pbMemoryMappedStartAddress[0x5555]=0xff; pof->m_fDetectedUsing28xxxConventions=true; // mark the flash object as representing a 28xxx job } |
This source could easily be updated with another method if we find out what kind of flash device it is (if any) and get our hands on a datasheet. The routine which prints "Read Only???" only dumps the bytes pof->m_bManufacturerId and pof->m_bDeviceId after failed attempt. Here is a snip from that routine in BootFlash.c:
| CODE |
if(!fSeen) { if( (baNormalModeFirstTwoBytes[0]==pof->m_bManufacturerId) && (baNormalModeFirstTwoBytes[1]==pof->m_pbMemoryMappedStartAddress[1]) ) { // we didn't get anything worth reporting sprintf(pof->m_szFlashDescription, "Read Only??? manf=0x%02X, dev=0x%02X", pof->m_bManufacturerId, pof->m_bDeviceId); } else { // we got what is probably an unknown flash type sprintf(pof->m_szFlashDescription, "manf=0x%02X, dev=0x%02X", pof->m_bManufacturerId, pof->m_bDeviceId); } } |
BTW;
I doubt we will see any future official updates of raincoat considering Andy's current situation, but he is welcome to prove me wrong.
Post by: lordvader129 on May 14, 2004, 11:19:00 PM
http://www.geocities...h/raincoat.html
it has the source with it and everything, might be an interesting read for you, lol
Post by: BenJeremy on May 15, 2004, 05:47:00 AM
DO NOT POST "IS MY XBOX A VERSION 1.6?" QUESTIONS HERE!!!!
Posts of this nature, and all replies will be DELETED. This is a technical discussion. If you are incapable of exercising simple courtesy and reading the thread, proceed to the Newbie Chat and pose your question there.
Post by: majik655 on May 16, 2004, 05:31:00 AM
wanted to change out a modded xbox board AND POWER SUPPLY into the new green case...
I understood the power supply AND eject board needed to go with the new 1.6 to an old case...
however when trying to boot the 1.6 in a old case it does not even power on.
stuck 1.6 and all components including controller ports BACK into green case..and still no boot no power at all.
This is a customers xbox's and he did not give me the power cords with them..
stupid question.. the 1.6 does not need its OWN power cord to boot does it?
that just makes no sense to me if it does but I suppose it is the only thing I have left to think of... EVEN ESD was considered when moving cases.
Post by: bucko on May 16, 2004, 06:14:00 AM
Post by: majik655 on May 16, 2004, 06:22:00 AM
| QUOTE (bucko @ May 16 2004, 07:14 AM) |
| If I read correctly, you put your 1.6 internals in a different case except your PSU. So you put your old internals in your 1.6 case expecting it to work, well you might have fried the mobo, the 1.6 psu has a different standby voltage (same to pc psu now i believe). |
nono...
EVERYTHING that came with the 1.6 came out ..
(PSU, controller ports, and motherboard.)
these all went into a old case..but did not power on.
So I figured maybe I should see if it boots when put back to original green case...
same issue no boot at all nothing.
now the old modded xbox still works fine when taken apart durring this process..
My question is... does the 1.6 need its own ORIGINAL power cord to boot?
I know that may sound stupid but that is the one thing I do not have that came with the 1.6 (customer still has it..)
So I used power cords from versions 1.0-1.5
I guess has anyone seen if ANY version power cord turns on a 1.6
could this even be a factor?
This is just the last resort before saying 1.6 is dead...which just does not make sense..ESD was taken care of durring process and NO attempt to mod it was done.
Just a simple case gut change.
Post by: bucko on May 16, 2004, 06:28:00 AM
Post by: bucko on May 16, 2004, 12:53:00 PM
.
Post by: Exobex on May 16, 2004, 02:37:00 PM
| QUOTE (majik655 @ May 16 2004, 02:22 PM) |
| EVERYTHING that came with the 1.6 came out .. (PSU, controller ports, and motherboard.) these all went into a old case..but did not power on. |
Did you check the machine before attempting the gut-swap?
Just a thought, perhaps the customer's given you one he's killed in the hope of getting a good one back.
I had this with a PlayStation a few years back - ended up changing the motherboard. Also left a message inside warning any other chippers not to mod it. And fitted tamperproof screws for good measure. Can't remember if I superglued the case shut, though.
Post by: thewitness on May 16, 2004, 04:27:00 PM
Post by: Artifex on May 16, 2004, 06:03:00 PM
Best case - it won't power up.
Worst case - you fry your xyclops. If, after you get the board back into a 1.6 case, it still doesnt power up, try my previously mentioned "frankenstein a 1.6 back to life" trick. No promises, though....
--Artifex
Post by: majik655 on May 16, 2004, 08:09:00 PM
Yes the xbox did boot up before attempting to do a gut swap.
And yes it was difficult to fit into older case...
the main reason it does not fit is because of the plastic pegs on each side of the video connector.
once the pegs are sanded down to size it fits nicely.
HOWEVER ..yes I totally am thinking now.. the grounding points under the board that ground to the case (basically the screw holes) are different!
some differences are:
the new 1.6 case if you take the motherboard out.. the pegs on each side of the video connector HAVE grounding plates ..pre 1.6 cases do not!
ALSO one screw hole is totally moved. (did not notice if moved to totally removed.)
Also the screw hole I believe above the LPC points..the grounding plate covering this screw peg also has now change to COVER the old jumper connector on the motherboard. the grounding plate actually is folded over in a different direction.
I am assuming.. it is the case and the grounding's that have screwed this board.. however I am not a person that understands this type of stuff too much and what the causes may do to a motherboard..all I know is it is the ONLY differences. AND I have done many many xbox's and never a prob.. but this is the first gut change .
anyway I probably have confused many.. so if anyone actually cares I can explain a little better.. but if I were you... do not gut swap a 1.6 into another OLD case.
checking into the "frankenstein a 1.6 back to life" trick.. I have to search for it.. I must have missed it.
THANKS EVERYONE.
Post by: tk420 on May 16, 2004, 08:19:00 PM
I had a friend who did this one building a pc. He somehow managed to screw the motherboard into the case without using the leads to screw into. Not quite sure how he did that, but it caused tons of problems (see also: breaking the motherboard).
Post by: majik655 on May 16, 2004, 10:51:00 PM
| QUOTE (tk420 @ May 16 2004, 09:19 PM) |
| I don't completely understand your explination of the difference between the old and new case (diagrams would be helpful, but aren't really important). Anyways, if when you put the 1.6 mobo in the old case, and there was metal touching together 2 points on the back of the mobo that you could not seee, it could cause problems. I had a friend who did this one building a pc. He somehow managed to screw the motherboard into the case without using the leads to screw into. Not quite sure how he did that, but it caused tons of problems (see also: breaking the motherboard). |
I know I made it very confusing.. I would have taken pictures but the green halo le case is gone and in the customers hand now.
here is some pics and maybe more explaination..
I know this might be common knowledge but maybe it will stop someone else from screwing their board because of these issues...
Again this is when you are trying to put a 1.6 motherboard into a PRE 1.6 CASE.
Different screw intakes and metal tabs..(grounding tabs?)
Why the 1.6 MB will not fit in pre 1.6 case...
Post by: fujitech on May 18, 2004, 10:38:00 AM
V1.6 Resurrection Guide
Post by: majik655 on May 18, 2004, 03:54:00 PM
THANKS TO OzXODUS TEAM!!
I read their tutorial and figured they knew what was going on..
I too did nothing to the board just a simple transferring of the guts to a pre 1.6 case.
I took their part number for the new Transistor
to www.norvac.net (electronics store where I live..they are everywhere)
they then cross refrence with..
http://nte01.nteinc....Search?OpenForm
which provided part number NTE2407
We also cross refrenced the original xbox transistor part number
and it also refrenced the same NTE2407 transistor...
Replaced the original transistor with the new one and BOOM xbox immediately started perfect! and YES is ALOT MORE STABLE!!
man are these things small! but you get 2 of them in a package for 1.60$
They are 2mm in size but a pretty simple thing to solder (and I am NO guru at soldering lol)
Here is the xbox specs..
Green halo LE xbox
3/20/04
5713.01
5659.03
THANKS AGAIN TEAM OzXODUS!! You saved me 150$!!
I bought 6 of these bad boys for other boxes to come just in case!
Post by: pROvIs on May 18, 2004, 06:30:00 PM
| QUOTE |
| GUYS, the first BETA ! YUHUU Please only people who have an 1.6 box or 1.6 Box devs should install it. I decided to release, as it looks like, the Xenium just startet there Box the first time and almost killed it. (Why the hell did i write, that power supply changed ???) Also, maybe we see in Additional ??? 72 hours an Update from there side. So , download it from here: http://hamtitampti.t...m/beta_3313.zip (Relase and update notes and diagramms included inside the zip) sorry, the Website had a 200k limit (and somewhere i lost the pw for smartxx - website. ..) , i released it on tripod. (note, tripod does not allow refers, so you have to type the URL manually into your browser) So People, i think, it is time for you, to decide what you want to buy. :-) Note to Xbins / Xbox-Scene & others: Do not upload this bios to Xbins / Xbox-scene , as this is a really hard core beta. Also, you can expect very soon new betas/finals, and this would only confuse the normal people (they sure will try it to install too) thx. I will release them here in this channel. franz |
Post by: fujitech on May 18, 2004, 08:16:00 PM
The "what to buy" remarks and other remarks are retandand in this thread!
There are others threads were u can post!
Btw the missing hole on the 1.6 mobo will certainly cause u trouble
U can either cut the shielding or put some pvc tape over it!
But it is recommended to remove some of the plastic too!
Post by: pROvIs on May 18, 2004, 08:26:00 PM
| QUOTE (fujitech @ May 18 2004, 11:16 PM) |
| Please only post 1.6 matters in this thread! The "what to buy" remarks and other remarks are retandand in this thread! There are others threads were u can post! Btw the missing hole on the 1.6 mobo will certainly cause u trouble U can either cut the shielding or put some pvc tape over it! But it is recommended to remove some of the plastic too! |
if you read more closely you would realize that this was not a "what to buy" remark but a beta release of a working bios for smartxx on a 1.6 box. Next time read b4 your flame.
Post by: majik655 on May 18, 2004, 11:06:00 PM
| QUOTE (fujitech @ May 18 2004, 09:16 PM) |
| ... Btw the missing hole on the 1.6 mobo will certainly cause u trouble U can either cut the shielding or put some pvc tape over it! But it is recommended to remove some of the plastic too! |
yep and I also stated the plastic needed to be shaved down.. and it was more of a question of why the thing died so easily.. which was answered by a TEAM .. so thank you anyway.
Post by: bucko on May 20, 2004, 11:05:00 AM
Post by: pROvIs on May 20, 2004, 10:43:00 PM
| QUOTE |
SmartXX Team is proud to announce: The Final Beta for 1.x boxes. Beta Log for 3315 - Same things as 3313 Fixes: - EEprom Section fixed, works now flawlessly - PAL / NTSC works - Video modes now support all modes - Fan Confusion Fixed Standby for a release in the very near future (72 hours???). ;-) (Copyright Note: Parts of the text taken from Xenium posting ) SmartXX Team changes back to normal Development again, as the "1.6 issue" is over |
and once again Franz/Hamti from the SmartXX forums
| QUOTE |
Final Beta. SmartXX Team is proud to announce: The Final Beta for 1.x boxes. Standby for a release in the very near future (72 hours???). ;-) (Copyright Note: Parts of the text taken from Xenium posting ) SmartXX Team changes back to normal Development again, as the "1.6 issue" is over Download : http://www.smartxx.c...d/beta_3315.zip franz |
Seems pretty impressive to me they are saying a final os will be ready within 72 hours and declares the 1.6 issue over from their side (until a hacked bios is developed).
Edit: added front page quote.
Post by: majik655 on May 21, 2004, 11:12:00 PM
any ideas or guesses on how long before that is created?
Post by: lookformeb on May 22, 2004, 06:54:00 AM
| QUOTE (Casper1786 @ May 22 2004, 04:42 AM) |
| i think the only thing slowin them down on the BIOS is the new Video encoder, I herd it took 3 months for Focus support, and both the Connexant and Focus are documented Chips, this new 1 isn't yet known if it's just mis-labled(don't remember what it's called) or custom made, but support will come |
I wouldn't worry about that much... soon...
Post by: pROvIs on May 22, 2004, 08:08:00 AM
| QUOTE (lookformeb @ May 22 2004, 09:54 AM) |
| I wouldn't worry about that much... soon... |
i beleive my m8 is right.
Post by: anu|b|iss on May 23, 2004, 03:55:00 PM
Post by: hanster24 on May 23, 2004, 08:20:00 PM
i use a memory card that has the game save on it, and the 007 agent under fire game to load the saved game, i have all the files if any1 needs em
Post by: modrobert on May 26, 2004, 08:24:00 PM
Post by: bucko on May 27, 2004, 10:36:00 AM
I hope their working their socks of, OS2 is looking good on xenium and smartxx looks as though they have things sorted.
Post by: nfs924 on May 27, 2004, 04:15:00 PM
Post by: Mr. Tom on May 28, 2004, 07:36:00 AM
| QUOTE (nfs924 @ May 28 2004, 01:15 AM) |
| i think M$ like put invisble cream over the d0..... |
Didnt they already find the D0 point?
Post by: doriftu on May 28, 2004, 08:10:00 AM
| QUOTE (Mr. Tom @ May 28 2004, 04:36 PM) |
| Didnt they already find the D0 point? |
I believe so, seeing as xecuter says that even their solderless chip works, its just a matter of the bios being updated and finished for it. Maybe im wrong, but that's what i got from reading xecuter's site, as well as a few other posts.
Post by: pROvIs on May 28, 2004, 09:44:00 AM
| QUOTE (doriftu @ May 28 2004, 11:10 AM) |
| I believe so, seeing as xecuter says that even their solderless chip works, its just a matter of the bios being updated and finished for it. Maybe im wrong, but that's what i got from reading xecuter's site, as well as a few other posts. |
First off D0 isnt important in 1.6 boxes so that was just a trivial bit of information they gave to the public.
Second, That is not what i read at all at xecuters post. All they say is that a solderless option is possible not that they have one. Xecuter has been pretty quiet on the 1.6 front. I may be wrong but i dont think they have annouced support for it at all yet but simply that they are working on it.
Post by: doriftu on May 28, 2004, 10:52:00 AM
| QUOTE (pROvIs @ May 28 2004, 06:44 PM) |
| First off D0 isnt important in 1.6 boxes so that was just a trivial bit of information they gave to the public. Second, That is not what i read at all at xecuters post. All they say is that a solderless option is possible not that they have one. Xecuter has been pretty quiet on the 1.6 front. I may be wrong but i dont think they have annouced support for it at all yet but simply that they are working on it. |
well...like i said from what i read
"Not sure if we made it clear in the last news post but the X2.3 mod worked just fine on the v1.6 Xbox. Original test was with the 5838 MS Bios. New update is that we have now also tested with a crudly patched Bios to boot unsigned code however we are currently reverse engineering the Xcalibur code to implement into the X2 / X3 sources which will take some time."
I'm guessing your interpretation of that is different from mine, but it really doesnt matter until they announce that everything is working. Personally i think i will wait till the x3 and a new bios is out.
Post by: Pizza Pizz on May 29, 2004, 07:25:00 AM
kills xbox's ? - don't look good does it ?
Post by: Turbanator on May 29, 2004, 08:27:00 AM
Because the rest of the stuff their "Team" makes is utter wank, so has to lay claim to other peoples work?
Post by: HELLTICK on May 29, 2004, 08:40:00 AM
Post by: HELLTICK on May 29, 2004, 08:42:00 AM
Post by: A@ron on May 29, 2004, 09:40:00 AM
| QUOTE (nfs924 @ May 27 2004, 07:15 PM) |
| i think M$ like put invisble cream over the d0..... |
Im pretty sure the xbox no longer uses the D0 to control the LPC bus. The LPC bus control is now auto detected as far I understand it by the hardware.
A@ron
Post by: miazmaticdotcom on May 29, 2004, 09:45:00 AM
Post by: A@ron on May 29, 2004, 09:50:00 AM
</OT>
A@ron
Post by: Jesticles on May 29, 2004, 12:40:00 PM
Edit: Hmm so basically it just has a different chip inside, ok.
- Jesse
Post by: Mr. Tom on May 30, 2004, 01:43:00 PM
Post by: Twister22 on June 02, 2004, 09:00:00 PM
| QUOTE (JDBorges187 @ Jun 2 2004, 11:27 PM) |
| Does anybody know why the font exploit won't work. I have used 007:AUF and a memcard to get into evox. So atleast that part works. BUt when i FTP the necessary files over to the XBOX it starts up with a error 21. IF anybody has gotten farther than this please lemme know thanx |
You can´t use the front exploit.. they fixt the "hole" in the dash.. and you can´t use an old dash with the new bios..
Post by: Twister22 on June 04, 2004, 10:13:00 AM
| QUOTE (JDBorges187 @ Jun 4 2004, 05:37 PM) |
| o damn and no modchips work yet? |
modchip´s work´s BUT... no BIOS yet..
Post by: baddkar on June 06, 2004, 02:30:00 PM
Post by: MagicArc on June 06, 2004, 06:18:00 PM
magic
Post by: baddkar on June 06, 2004, 08:00:00 PM
| QUOTE (MagicArc @ Jun 7 2004, 03:18 AM) |
| i know they're saying the 1.6 works, but if the board has changed how will existing chips work....hrm....I'll wait to pick up a new chip once they say they're 1.6 installable....and hopefully by then a bios will be out too. magic |
exactly thats what my bro is doing too.
Post by: Mr. Tom on June 06, 2004, 08:08:00 PM
| QUOTE (baddkar @ Jun 7 2004, 05:00 AM) |
| exactly thats what my bro is doing too. |
heh, i bought mine as soon as i found out they existed, and killed it within a few hours.
Post by: baddkar on June 06, 2004, 09:49:00 PM
| QUOTE (Mr. Tom @ Jun 7 2004, 05:08 AM) |
| heh, i bought mine as soon as i found out they existed, and killed it within a few hours. |
I have a modded 1.4 with a Xenium chip, and X2 bios, but I haven't read anything about the 1.6 being able to be modded so, we wait.
Post by: strugglin on June 08, 2004, 02:35:00 AM
Post by: Ice9 Tech on June 08, 2004, 02:41:00 AM
Post by: bucko on June 08, 2004, 05:13:00 AM
| QUOTE |
am I able to use a Chameleon Chip with a cromwell 2.27 and Matrix Programmer on this new version 1.6 Xbox Motherboard? |
Hehe this person is lazy, don't even bother to read a few pages of the thread, ROFL
Post by: lookformeb on June 11, 2004, 09:53:00 AM
Post by: baddkar on June 16, 2004, 08:17:00 AM
Post by: spacemanson on June 16, 2004, 08:38:00 AM
Post by: Mr. Tom on June 16, 2004, 09:51:00 AM
| QUOTE (spacemanson @ Jun 16 2004, 05:38 PM) |
| BADDKAR....Thanks for the quick response but did you really have to dis me in front of all my peers...OK MOM I WILL READ 1st POST LATER......I am just pissed that I now have a doorstop for an xbox... |
Well had you read the first post, you wouldnt have been dissed. And at least you can still play xbox games on the mo'fo.
Post by: JohnnyVegas on June 17, 2004, 11:02:00 AM
Anything made before 3-22-04 is 99% NOT a 1.6.
Post by: DJAvu on June 17, 2004, 11:22:00 AM
Post by: pROvIs on June 17, 2004, 11:55:00 AM
| QUOTE (JohnnyVegas @ Jun 17 2004, 02:02 PM) |
| No you should have a 1.4-1.5. Anything made before 3-22-04 is 99% NOT a 1.6. |
3-19-04 is the eariest reported 1.6 MFD date.
Post by: bucko on June 20, 2004, 05:30:00 AM
.
Post by: garrcbs on June 21, 2004, 04:56:00 PM
Post by: bucko on June 22, 2004, 03:09:00 AM
| QUOTE |
My xbox v1.6 mfg date on the bottom reads 2004 04 01 inside the box 18 mar 04 |
Yer were not really bothered (why this thread died), try looking at the chip and mobo a lot more reliable method. So any more hacking/cracking news from you guys about this mobo?
Post by: Ben999_ on June 22, 2004, 05:35:00 AM
| QUOTE (bucko @ Jun 22 2004, 07:09 AM) |
| Yer were not really bothered (why this thread died), try looking at the chip and mobo a lot more reliable method. So any more hacking/cracking news from you guys about this mobo? |
He's already positive it's a v1.6, he was just reading off the date on the box.
Post by: TeaTime on June 25, 2004, 09:01:00 AM
I bought the xecutor 2.3BL (cheapest one) to my supposedly ver. 1.2 box (All Halo le r 1.2? yeah right...) only to find its a 1.6 (clearly the xcaliber encoder on it)
so a few questions:
1. Is the 1.6 can be modded with the x2.3? (I know there is no bios yet, how physiclly i am doing this...)
2. Even if i can connect the chip - how can i flesh it? (do i have to buy the progremmer?)
3. The smartxx guys posted a guide - how relevent is it to my chip?
the reason I am so confused is the chip comperision table here on x-s where the x2.3BL is listed a 1.6 cappeble without the progremmer while the the 2.2 needs it...
I think that I got F'ed pretty hard here as the 25 UK i paid for the chip is lost...
Post by: xFusioNx on June 25, 2004, 10:51:00 AM
The guide is fine, all it does it let you rebuild the LPC to install the chip and it gives the location of the d0.
I RECOMMEND WAITING TO ISNTALL UNTIL YOU GET AN OFFICIAL GUIDE FROM YOUR CHIP MANUFACTURER THOUGH! ABIOS WILL BE OUT SOON AND YOU SHOULD JUST WAIT FOR BOTH!
Christ how many times does this need to be said?
Someone should fucking pin a topic that says if you have a v1.6 fucking wait for a bios.
Post by: kherrod on June 26, 2004, 06:31:00 AM
Post by: redghost on June 26, 2004, 07:25:00 AM
Post by: Trevante on June 26, 2004, 09:46:00 AM
Post by: kherrod on June 26, 2004, 12:22:00 PM
Post by: hippo on June 28, 2004, 03:50:00 PM
Post by: bucko on June 30, 2004, 02:44:00 AM
then Xecuter (i'm sure it was Evox on the focus hurdle). Anyone know if any new bios teams are formaing to write a bios for this xbox? I think it would be a good idea, maybe ind-bios should also try and work on a 1.6 bios to take the work load of xecuter (so they can release there X3).
Post by: Oldmanjoe on June 30, 2004, 09:21:00 PM
Post by: Ben999_ on July 01, 2004, 08:51:00 AM
| QUOTE (Oldmanjoe @ Jul 1 2004, 01:21 AM) |
| Which chips work with the 1.6? I haven't done any research nor have I come across one. People get boxes modded by me all the time, and I haven't seen one yet. Where is the D0 point on it if there is one? I need lots of info on V1.6 |
Read the thread! The chips all support it, there is just no bios made for 1.6 boxes yet.
Post by: Oldmanjoe on July 01, 2004, 09:10:00 AM
Post by: Trevante on July 02, 2004, 07:12:00 PM
| QUOTE (bucko @ Jun 30 2004, 11:44 AM) |
| Anyone know if any new bios teams are formaing to write a bios for this xbox? I think it would be a good idea, maybe ind-bios should also try and work on a 1.6 bios to take the work load of xecuter (so they can release there X3). |
As far as I know, Team Evox is the only one working on a 1.6 compatible bios. Team Xecuter has said that the 1.6 is not a priority for them, so it's pretty likely that the X3 bios won't be 1.6 compatible at launch.
Post by: Oldmanjoe on July 02, 2004, 08:31:00 PM
Post by: markland556 on July 05, 2004, 10:35:00 AM
Post by: Trevante on July 06, 2004, 04:46:00 PM
| QUOTE (dcmander @ Jul 7 2004, 01:42 AM) |
| Anyone have a guess if or when TSOP flashing will be available for 1.6 xboxes? |
I'm not sure if I'm confusing it with the eeprom or not, but I think the TSOP is a flash once chip, so I'm not sure if this will be possible.
On a side note, has anyone modded an Xbox using Team Evox's M8 bios?
Post by: xFusioNx on July 06, 2004, 08:31:00 PM
Post by: majik655 on July 06, 2004, 08:48:00 PM
hopefully everything will be answered now..
what modchips state they support 1.6? only Xenium Ice ?
and is it for sure a fact that there will never be on board flashing? (tsop or bios chip onboard?)
Post by: A.Z.BEST on July 07, 2004, 04:28:00 AM
) posted their results as the first ones.How about an LPC cheapmod. The LFrame is back on the mobo, so installation of the LPC cheapmods is possible again. Please post your results if you can try (If I could only reach one 1.6 ;/).
Post by: ziomek on July 07, 2004, 05:49:00 AM
Post by: pROvIs on July 07, 2004, 08:31:00 AM
| QUOTE (majik655 @ Jul 6 2004, 11:48 PM) |
| question.. hopefully everything will be answered now.. what modchips state they support 1.6? only Xenium Ice ? and is it for sure a fact that there will never be on board flashing? (tsop or bios chip onboard?) |
Smartxx was the first to have full support for 1.6 though with points posted and a working os for everyone to use
Post by: spacemanson on July 24, 2004, 09:29:00 AM
Post by: brett720 on July 24, 2004, 02:48:00 PM