Print

[bucko]

QUOTE (fujitech @ Nov 3 2004, 10:00 PM)

I dont need speculations! I need facts,proof! Have them? If no then ............... Thank u!

I'm getting a  crystal tomoz (england time) fujitech but someone will most likely beat me.

[fujitech]

[A.Z.BEST]

QUOTE

It seems there is a new Xbox that is crashing randomly when booting to the dashboard. This box has been labelled as v1.6B (the power/eject cable is brown instead of yellow - however there are many that of Xbox's with the Brown cable that work just fine - except for FlashBIOS booting to a black screen, but still functions correctly for flashing from http, hdd or disc - we found the manufacture date of these was 2004-9-13) The manufacturing date of the boxes that seem to be affected is 2004-9-16. The Dashboard version is 5960 and the kernel version is 5838 (kernel seems the same as v1.6)

It would be called 1.7 if there were any visual hardware changes. It's easy to deduce from this quote that it's just a 1.6 with some small software modification. It's possible that there's something more, but you cant yell on everybody around to post the picture of something that is more than rare... I hope you also read the thread on executer team forums. Just chill out and give it some time.

[gerzand]

I just dont get it... why some people are taking this so personally....Its just a damn xbox revision. Sit down and be quiet, if there is proof itll come - if want to know so badly, go buy one.

[jokk]

QUOTE (A.Z.BEST® @ Nov 3 2004, 11:30 PM)

It would be called 1.7 if there were any visual hardware changes. It's easy to deduce from this quote that it's just a 1.6 with some small software modification. It's possible that there's something more, but you cant yell on everybody around to post the picture of something that is more than rare... I hope you also read the thread on executer team forums. Just chill out and give it some time.

M$ doing a revision w/o changing the kernel ID ?
Weird no ?

Btw m8 is based on 5838, the same kernel as this "new" revision.

[bucko]

QUOTE (CrayZEE @ Nov 3 2004, 10:39 PM)

Taking it personal is different. Did you know Xecuter 2 4982 works fine on any modchip except Xecuter 2.x Series? See, it was faulty hardware, and i don't think they fixed this problem with the X2.6. What do i dislike about it all now? Well, Team EvolutionX is the only team that made a free bios for us, they didnt get paid to do so, they don't have it built from the source code, they actually hacked it. Their work wasn't for nothing, many except a few x3 users use this bios, dissing it because of faulty hardware is just cruel. It's like taking their hard work, and spitting on it, yet everyone uses it. Why am i rather thinking on a faulty modchip? Well x2.x series had the problem before with some bios's, now add to it that the Evox Bios is hacked, so it just gotten removed some security, so there is no way of fucking this up, not in this way that it wouldnt happen on other modchips. PS : the Xecuter 3 Embedded XBE Bios still doesn't boot outrun 2.....

STFU! sit tight, have a wank then wait until pics arrive then you will be sorry

[jokk]

What modchip ? what bank ?

[A.Z.BEST]

QUOTE (jokk @ Nov 3 2004, 11:53 PM)

M$ doing a revision w/o changing the kernel ID ? Weird no ? Btw m8 is based on 5838, the same kernel as this "new" revision.

Maybe there was some code for the new Xcalibur firmware in K:5838, but M8 doesn't have it anymore. It was just cut out. Don't you think? K:5101 works both on Conexant and Focus VEs, but it took some time to get the M7.

I don't know how it is with this 1.6B and I don't want to talk about it when the situation so unclear. But I think that code from 1.6's Xcalibur should be sampled with normal 1.6's code. Too bad most of us don't know how to do it .

[nachomans]

[jokk]

date ? modchip ? bank ?
Post some usefull info please.

[PlaStiCam]

I bought 5 xboxes recently (UK crystal) all ranging from 13.09.04 - 19.09.04.
All had Samsung drives and only some had brown cables.
I'm having tremendous problems with these xboxes randomley freezing during gameplay and it seems i have just found out why after reading this:(
All are fitted with Aladdin XT mods with M8_16 bios.
Ive fitted these mods to many other consoles manufactured before these dates and they are flawless.

[vmehta211]

Manu Date: 2004-14-09
Bought in CA, USA
Modchip used: Super Aladdin Live (and I tried the Aladdin Live)
Bios: Evox M8_16

Avalaunch Version: Latest via webupdate
Evox: +3935
UnleashX: Lastest

Problem:
The xbox will freeze just idling on any of the above dashboards.  I've reflashed the chips thinking it was a bad flash.  I've reformatted and reinstalled all the dashboards and apps thinking it was a currupt drive.  

I've had this problem with 2 different Xboxes with different size/model drives.  One has a Maxtor 250 and the other a Seagate 160.

These xboxes will randomly freeze and sometimes stay on as long as 5 hours.  Most of the time they will freeze within the hour.  

I then can press the Eject button and the Xbox will restart after it has frozen instead of releasing the drive.

edit:
These xboxes came in the new xmas bundle with NCAA 2k5 and Top Spin.

[Lurrch]

Sorry .. X2.6 bank2

[keefyboy]

13 Sep 2004, brown cable.

SmartXX v1, every time the chip was hooked up, it would power on for 1 second, then power off for one second, repeat... Tried everything, relflashed on an older Xbox, resoldering, etc.

Checked soldering w/multimeter, all connections read 0 Ohms.

Installed the same damn chip into a v1.5 (or maybe 1.4, I thought 3.3v and ground was no go on lpc), and it works flawlessly.

ps - fujitech, you're an idiot.

[Lurrch]

Mine also came as tha new Xmas bundle