Aladdin Xt 4032 Problem, Once Again Options

[ryn_o]

I just swapped an aladdin 4032 49lf020 for a aladdin xt 4032 49lf020A due to some issues with booting and have now run into another issue. The chip now boots every time but if i do IGR or select reboot from any application it boots the factory bios. This did not happen with my old chip with the same bios. I have tried several bioses and even another chip (A revision) with no success. I have a 1.6 box and the wires are all correct. Please help.

[HackDaBox]

this is normal for for xt 4032 , this is not a preblem ... if you hate this just enable this chip in allways on mode by linking bt to ground on the chip itself ( ground is the last pad on the edge and is it not the pad next to bt but the one after that ) a very small piece of wire can be used.

HackDaBox !

[3fifty1]

what isues did you have with the chip booting? the xt 4032 chip

[ckh2004]

The chip now boots every time but if i do IGR or select reboot from any application it boots the factory bios.

My Aladdin XT 4032 with 49LF020A also has this problem. Yes, it can be very annoying. Whenever you eject the DVD, the xbox will reset and boot into the original bios and dashboard. IGR can only use the "Quick" method and not the usual "Compatible" method.

I tried one batch of Aladdin XT 4064 with 49LF020A, they don't have this problem,

DuoX 2 doesn't have this problem.

[ryn_o]

Concerning the problems with the 49lf020's It would boot to aftermarket bios about50-75% of the time. The other times it would appear to boot but no audio or video.

For the 49lf020A, should I try a different batch of chips then from my lamma since you said that that has fixed the problem for you. Anyone here wanna trade for a 49lf020A that doesn't do this reboot? Otherwise, please point me to a good place to buy the X3 or the Duox for pretty cheap and maybe even locally. (llamma does not sell the executer chips yet only aladdins, i'm in the mpls/st paul area). Any help would be appreciated. Thanx.

EDIT: ONe last question, Will this same problem happen on non 1.6a/b boxes as I will be putting a few in this week and don't want this to happen?

This post has been edited by ryn_o: Jan 12 2005, 03:44 PM

[radish28]

the no video is an error with 1.6(B) in the CPLD code and if you flash the bios on the chip with the X2 bios (if you got a v1.0-1.5) the IGR should work fine. Just swapping the 49LF020-A wont fix any of your issues btw, if its a bios issue flash the chip and if its any other get a new batch.

This post has been edited by radish28: Jan 12 2005, 06:42 PM

[ryn_o]

I just swapped an aladdin 4032 49lf020 for a aladdin xt 4032 49lf020A due to some issues with booting and have now run into another issue.  ....I have a 1.6 box and the wires are all correct.

the no video is an error with 1.6( in the CPLD code and if you flash the bios on the chip with the X2 bios (if you got a v1.0-1.5) the IGR should work fine.  Just swapping the 49LF020-A wont fix any of your issues btw, if its a bios issue flash the chip and if its any other get a new batch.

I swapped my old 49lf020 for a 49lf020A to get the corrected cpld code but then this issue arose. I am going down to llamma in a bit to try some chips from different batches otherwise i am going to get a DuoX 2 or X3.. THanx though

[Chancer]

I swapped my old 49lf020 for a 49lf020A to get the corrected cpld code

You are missing the point here. The CPLD code is not altered by changing the Flash Rom.
The problem is in the Lattice chip so you can't cure the No video stuff by putting in a newer Flash rom

[ckh2004]

One last question, Will this same problem happen on non 1.6a/b boxes as I will be putting a few in this week and don't want this to happen?

Yes, whatever the xbox version or bios used (X2 4981/4983 or Evox M8/M8+), the "reset on eject" or reboot to original MS bios will still be there. It has to do with the screwed up CPLD code again. The new CPLD code can't remember the state at power up - whether it was in mod mode or not.

All my new Aladdin XT 4032 with SST 49LF020A also suffer from the same problem, regardless of what xbox version or bios used. I have installed 60+ of them in v1.0, 1.1, 1.2, 1.3, 1.4, 1.6 and 1.6b (never seen a v1.5 myself) so I know what am I talking about.

Aladdin XT 4064 with SST 49LF020A apparantly doesn't have this problem based on just one batch that I tried.

if you flash the bios on the chip with the X2 bios (if you got a v1.0-1.5) the IGR should work fine.

Definitely not true. Any bios will not solve the problem because it is the hardware (CPLD) design problem.

This post has been edited by ckh2004: Jan 12 2005, 10:18 PM

[radish28]

no? I've had a customer that wanted IGR to boot back to the modchip so i flashed the X2 bios for him and havent heard anything back... Also from apps liek XBMC reboot boots back to the modchip enabled. If you really want IGR thoguh and the X2 bios indeed doesnt work then just wire so the chip is always on (ground BT on the chip and D0 on the mobo).

[HackDaBox]

it isn't really that X2 bios works and evox m8+ doesn't , it is becuase the x2 must of had the quick igr enabled and the evox m8+ must of had the more compatible igr enabled.

And to be honest there is allmost no difference ( in use ) of the X2 bios and the Evox m8+ bios even on old machines these days. The crap about X2 is more campatible is wrong it's just people remembering that X2 was beter before because it had more features but Evox M8+ patched using Evtool is just as stable for all model xboxes. But i suggest using the Quick IGR on these new aladdin xt's so it will IGR back to your dash instead of back to MS DASH. Or install the chip in allways on mode by hooking up a samll wire from bt to ground.

HackDaBox !

[ckh2004]

But i suggest using the Quick IGR on these new aladdin xt's so it will IGR back to your dash instead of back to MS DASH. Or install the chip in allways on mode by hooking up a samll wire from bt to ground.

But this is not fool proof. Under the following conditions, the xbox will always reboot to the original MS bios:

1) eject half way through the game

2) select "reboot" from main dashboard, e.g. Slayer's Evox dashboard. Select "reboot" in other secondary dashboards might have the same problem (I think so).


I hope all Aladdin XT 4064 chones don't have this bug cos I am getting some in. BTW, I can confirm that DuoX 2 doesn't have this issue.

This post has been edited by ckh2004: Jan 13 2005, 06:06 AM