Jump to content


Photo

Problem Booting Aladdin Xt Lite On A V1.6 Xbox


  • Please log in to reply
11 replies to this topic

#1 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 23 January 2005 - 08:13 PM

I have some weird problems booting a V1.6 XBOX with an Aladdin XT Lite chip.
Whenever I boot with the original BIOS everythign works ok. When I hold down the power button for 2 seconds, it starts only once in a while.. something like 1 out of every 5 tries. But when it starts it works OK with burned CDs.

So I'm wondering what it could be..

When starting with the modchip BIOS, the times when it does not work, the screen simply stays black and the orange led is turned on.. but nothing goes on.. no CD or HDD read or anything. Any idea what it could be?


#2 ckh2004

ckh2004

    X-S Expert

  • Members
  • PipPipPip
  • 639 posts

Posted 23 January 2005 - 11:59 PM

Do a search on this forums for "Aladdin XT"... you will find plenty explanations.


#3 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 24 January 2005 - 01:47 AM

thanks ckh2004. I already did lots of searches on this forum and all I came up with is that there are tons of reasons why it could not work smile.gif

It seems that another guy with my same issue said that it could go away by flashing the m8_16.bin flash of EvoX on the chip, but the discussion interrupts just where he says he's gonna try that. So I am not sure this could solve the problem.

Is there any way to diagnose that out?


#4 shepd

shepd

    X-S Member

  • Members
  • Pip
  • 126 posts

Posted 24 January 2005 - 02:20 AM

Flashing the non-plus version of M8 bios should fix your problem.

I have seen that specific problem come up often when using the plus bios on a non-b v1.6 XBOX. Flashing it with the proper BIOS made the problem disappear.

#5 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 24 January 2005 - 02:35 AM

Here's another weird thing:

1) I burned a Slayer boot CDR (v2.6)
2) I tested the CDR on a v1.2 with X2 modchip and the CD works
3) I put it in the v1.6 XBOX with the Aladdin XT Lite chip (Team XT)
4) After a few trial I got the modchip to start and it load the CDR but when the GUI of Slayer should start I only get a blank screen.. so I canno flash the BIOS on the chip from there.

Is there any other way to flash the Aladdin chip without having to solder it on another version of the XBOX or through a PC programmer?


#6 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 24 January 2005 - 04:36 AM

Some news about my situation:

I have found a way to boot the Slayer boot disc and now it starts fine. Now, whenever I try to flash my BIOS with the EvoX M8_16 I get an unknown flash type error even if I added the following lines to evox.ini:

Flash = 0xbf61,"SST - 49LF020",0x40000
Flash = 0xbf52,"SST - 49LF020A",0x40000
Flash = 0xdab0,"SST - 49LF020A",0x40000


I'm sure my SST chip is a 49LF020A and that the Lattice is a 4032. What should I do to get it to work and flash it over?

The flash recognizer utility keeps saying that my chip is an unknown model (type 0xbf52). Any ideas?


#7 ckh2004

ckh2004

    X-S Expert

  • Members
  • PipPipPip
  • 639 posts

Posted 24 January 2005 - 06:04 AM

Copy evoxdash.xbe, evox.ini, skin, bios files and directories to c: and try again. Make sure the lines are added properly in the evox.ini in the correct section. Aladdin XT 4032 does NOT have flash protection. It should work.


#8 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 24 January 2005 - 09:30 AM

I made another ISO once again and this time it recognized my chipset, but after erasing the BIOS it just hang there and there was no way to get it to write something on the chip which is now no longer useable.

And now I wonder how I could hotswap it since it's a soldered one.. sad.gif


#9 ckh2004

ckh2004

    X-S Expert

  • Members
  • PipPipPip
  • 639 posts

Posted 24 January 2005 - 09:37 AM

QUOTE
I made another ISO once again and this time it recognized my chipset, but after erasing the BIOS it just hang there and there was no way to get it to write something on the chip which is now no longer useable.


I am very sad for you. I ever encountered one or two Aladdin XT Lites that could not be flashed no matter what, even if I tried hot flashing. When flashing was attempted again and again, the evox would freeze at about 90-95% through erasing sad.gif Your chip might be similar, so even if hotswap flashing is possible, it might not be of much use.

The problem turned out to be the screwed up CPLD code which afflicted early Aladdin XT 4032/Lite batches with 49LF020A. These 4032s tend to have "dab0" flash ID.

Edited by ckh2004, 24 January 2005 - 09:44 AM.


#10 tanis2000

tanis2000

    X-S Enthusiast

  • Members
  • 9 posts

Posted 24 January 2005 - 02:14 PM

This chip has the bf52 ID but is probablyone of those of the failed batches. I'm trying to arrange with my supplier to send them back to him and get another model. What's your suggestion? I can choose between DUOX2 which costs some more money that the XT Lite, or the Aladdin Advance XT Pro (price only a bit more that the Lite, but is that one working 100%?).

Thanks again for all the support! smile.gif


#11 HackDaBox

HackDaBox

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,783 posts
  • Interests:XBOX-SCENE
  • Xbox Version:v1.4
  • 360 version:v1 (xenon)

Posted 24 January 2005 - 02:57 PM


Well in my opinion your choice is easy , get the DUO X 2 modchip it is safer to use in a V1.6 and is rock solid stable ! Just for the piece of mind and hassle free install it's worth the extra couple of bucks for the chip and remember the duox2 has double the memory of the Aladdin XT and has 2 bios banks so a bad flash is not the end of the world !

HackDaBox !



#12 ckh2004

ckh2004

    X-S Expert

  • Members
  • PipPipPip
  • 639 posts

Posted 24 January 2005 - 04:26 PM

Aladdin XT 4064 is about the same price as DuoX 2. If you value your time, get DuoX 2. The latest DuoX 2s should come with Evox M8+_1.6 bios with IGR and LBA48 already edited in, and so work out of the box in both v1.6 and v1.6b.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users