Hi,

I've modded a 1.6 xbox (samsung) with an Aladdin XT lite, SST 49LF020A. I don't know which bios version is, but I've bought it as "1.6 compatible". I have a lot of problems..



1) Sometimes the XBOX does not start. The led turns yellow, but there is no image on the screen, just a black screen.

2) When the modchip starts, I see the "EVOX" logo, but then:

- Sometimes it hangs while loading the game (original or backup), some others after some minutes of play.

- Sometimes it gives me the green "xbox needs servicing" after the boot.

I've downloaded the Slayer's Evox boot disk: sometimes it loades, other times it hangs during the loading. I've exchanged the chip (only the socketed chip, not the entire modchip with another taken from another equal Aladdin XT lite, but nothing changed. I really don't know what to do.

Did you find a solution for problem number 1?

before anyone can really help we need more details ...

when you said xbox V1.6 (samsung) did you mean samsung dvd-rom or samsung ram ?

Because usually the samsung ram V1.6a does not has issues with the evox m8 v1.6 bios but it can have problems with the Evox M8 Plus V1.6 bios. so reflashing the non plus version may fix this issue for you.

Also have you unlocked the original hard drive or installed a new hard drive ?

HackDaBox !

Same old XT issues Again! I would not even buy the "supposed" new ones with fixed code because they quite clearly are not.
Use the chip in an older box and get a Duo X2

I just installed an XT chip in a 1.6 box.. booting problem
Installed a new XT chip.. booting problem
Both with 49LF020A chips
I used many different BIOS´s but no luck.

Then I used an old SST 49LF020 chip in one of the XT chips problem solved.. been playing around with that setup for 2-3days now.. still no problem.. one more user is happy
Just works with any BIOS.

Yes I defo think there are still issues with the new ones even

bonus info: the to XT chips i used was with white PCB..

So the supposed Xmas edition with fixed code do not in fact have fixed code then.
Cheers for the info.

This means that my brand new aladdin xt white wont work on my box (1.6a samsung ram)? I got it with the bios preflashed with m8_16. this is for my 2nd box. (The first1.6a had the same aladdn but was red. In the beginning it wasn't working but after it magically worked)

Also can i reflash it with a external flasher i used before with chips marked<mx 29l002f>?

EDIT: I forgot to mention it was an Aladdin XT Lite (4032) White Xmas edition with a SST49LF020A

i found out that they are not ALL bad.. some works sometime, some don't boot, and some just run´s with no error..

That shows that the CPLD code is still screwed up - no tolerance and timings bother on marginal, any temperature changes will shift the timings out and result in booting problem. Remind me of the famous Super Aladdin Live can't boot original MS bios saga - if SAL does work, then it is your luck... haha...

I have a bunch of Aladdin XT 4064s that even when flashed with Evox M8_1.6 bios and used in normal v1.6 (Samsung RAM), some won't boot consistently, some will boot quite consistently initially, then as the xbox warms up, the booting issue returns

What is the CPLD code? The cpld isn't the identifirer of make/model of the chip? And if its bad then can i replace the sst49lf020a with a sst 49lf020 non-a?

Also that flasher for macronix mx 29f002 would work for flashing the sst?

Thanks

I am referring to the programming of the Lattice v4032 CMOS Programmable Logic Device (CPLD). There are frequent changes in Aladdin XT CPLD code to accomodate 49LF020A and now v1.6b. Some revisions of the CPLD code have bug that prevents the mod chip from working properly with v1.6b and / or v1.6. You never know which revision of CPLD code comes with your Aladdin XT. To complicate the matter, there are too many clones of Aladdin XT out there, and whether the correct CPLD code is cloned