Search the Community

Hi Im in the process of upgrading my ram. The mod chip im using is an x2.6 with ind-bios. I have the xblastos xbe installed on my HDD. My thinking was that I could boot to my dashboard then launch the xblastos xbe to check each ram chip. However, upon powering on the xbox, it boots three times and the led's flash red and orange. My question is do I need the xblast bios flashed to my modchip for the xbox to boot during the upgrade or have I made a mistake during the installation? Im quite confident about my soldering. Checking under x60 magnification and lots of light tia

Does someone have stock .BINs files of the bios for the DuoX 3 modchip? Both banks please. Would like to return it to stock. (Image source= https://www.nh-game.com/index.php?route=product/product&product_id=92)

So a day ago I got a 1.6 xbox with x3 (purple) model in it, and decided to flash force480p bios while I am waiting until my 1.4 with xboxhdmi returns from installer. Flashed that bios successfully, but console does not output any video signal. Also, about a year ago I had another 1.6 xbox with x3ce chip, and I do remember that force480p bios worked flawlessly. Anyone knows what the issue could be? Things I tried: Wiping X3 eeprom (a+b+x+y on bootanim) Downloading bios from multiple sources Flashing over various methods (http flash; ftp flash; flash from internal hdd) Flashing on both 1-4 and 5-8 banks Trying with different HD cables (I have component cables and chimeric systems hdmi adapter) Trying on 3 different tvs

So yesterday i decided to flash a new bios to my V1.1 Xbox Modchip Super Aladdin with the SST49LF020 to remove de DVD drive check and used EVtool to edit a EvoX M8+ 256K Bios, but me being stupid i also decided to change the EvoX logo to be sure the Bios was indeed changed, big mistake. The flashing completed, the Xbox turned off and now when i press for 1 second to activate the chip i get no signal from the TV, no animation, no sound nothing. I even put Hexen 2018 but nothing, it's dead. But it boot to the stock dashboard with a quick press. I've been searching for hours, but still have some questions: 1) If i buy one of those Aladdin XT PLUS2 XT+4032 that come with a SST49LF020A can i just replace that with mine and it will work? I saw that it comes pre-flashed with a EvoX M8 bios? 2) Do you know were to buy just the SST49LF020 with the Bios? I feel very sad about this, because i treasure my consoles and this was my main and first Original Xbox and would like to restore it.

Is this kind of in-BIOS FTP access really useful? Does it feature on many chips? I'd also like to try out the SmartXX Remote Flasher, but while it detected my xbox on the network, and I could select a BIOS, I couldn't get it to flash anything. Very cool nonetheless and just thought I'd share this.

Bios “FAQ”: What does CEE or EEC meen and what is different? CEE/EEC is the boot order of the bios file. CEE will boot it’s first Dashboard from the “C:\” partion of the drive. In most cases it’s “C:\evoxdash.xbe”. Which can be either a the EvolutionX Dashboard or a shortcut to a different Dashboard on any other partition (C,E,F or G). So you could place a shortcut on C:\ and point to E:\Dash\UnleashX\unleashx.xbe and when you boot up your XBox, UnleashX will show up as Dashboard. Screen : https://imgur.com/a/hf6nG5Z In some cases, the evoxdash.xbe can be found, for what ever reason. Then the bios tries to boot the second letter “E:\” which points to UnleashX (In the pic above – E:\Dash\UnleashX\unleashx.xbe). If that can be found it will boot UnleashX. And you guessed it, if that can’t be found either, the Bios tries a last time with “E:\Dash\EvolutionX\evoxdash.xbe”. When all of these options has failed, you will get an fancy error screen. Note: For some apps like Dashloader ect. you should use a CEE bios to avoid any trouble. I would say, a CEE is the most user frindly option even, if you have more experiences, it makes no differend. EEC will boot it’s first Dashboard from the “E:\” partion of the drive. They point mostly strait to a Dashboard like “E:\Dash\UnleashX\unleashx.xbe” or “E:\XBMC4Gamers\default.xbe” as you can see in the screen below. Screen : https://imgur.com/a/GsFOZCo So that’s the main difference between them and they are the most common bios variations. But every “rule” has his exceptions. Some times you have bioses like “EFC” or “FFC”. If I remember right, the X-Disk from FireFucker has those bioses. Not sure why but if I had to make a guess “FireFucker – FF” = F partition. But thats just a guess. So you see, you can point your bios to what ever you want. C,E,F or G, it just depends on you. But there is a little “twist” in here. Some old Dashboards lile tHc, BlackStromX (BSX) and some other will need a bios which boots C first because those are “Hacked” MS Dashbaords. Ofc you could HEX-Edit the hell out of it, like some ppl. Have done with BSX or tHc Lite but at the end, it’s not worth it. All “modern” dashboards boot from everywhere. So let’s move on to iND. iND bioses are a bit different. A iND bios has, not always but most likely, a config file in which the bootorder is stored (you could inject the config to the bios but, for 1 sec it’s not worth the trouble you could get into and in case you use a 5004.06 bios it could breake your XBox). To edit the config of the iND bios you can use the IND-BIOS Configurator or notepad. It just depends on your personal taste. Like you see in the screen below, in the “ind-bios.cfg” and in “ IND-BIOS Configurator” appears the same. It’s almoste or is the same like you have already seen in the EvTool for EvoX bioses. Screen : https://imgur.com/a/YSWRajj And they work the same way. You can do CEE, EEC configs if you want and inject them and you would have an EEC, CEE bios like you have with the EvoX bioses but that not very common. Most ppl. prefere to use the config. A plus here is, you can edit the config fast and you don’t need to re-falsh a bios just to make the change work. Example - iND bootorder (ind-bios.cfg) DASH1=\Device\Harddisk0\Partition2\evoxdash.xbe DASH2=\Device\Harddisk0\Partition1\Dash\UnleashX\unleashx.xbe DASH3=\Device\Harddisk0\Partition1\Dash\EvolutionX\evoxdash.xbe DEFAULTXBE=\Device\CdRom0\default.xbe The rest is the same like for EvoX. And now the last, the Xecuter bios. Like the iND, the Xecuter bios has a config, the “x2config.ini”. And like in the iND config you can edit it with x2-config-maker tool or with Notepad like you can see in the screen below. Screen : https://imgur.com/a/81liMNt nd yes, it’s the same like in EvoX or iND but you have 2 Dashboard options more which can fail before you get that fancy error I have talked in the beginning. You can change the boot order here as fast as in the iND and you don’t need to re-flash it in case of a change. One different here, you cant inject the ini to the bios like you could do it with the iND but again, who want’s that. Example - x2/x3 bootorder (x2config.ini) dash1Name = e:Dash\UnleashX\unleashx.xbe dash2Name = e:Dash\EvolutionX\evoxdash.xbe dash3Name = e:Dash\XBMC4Gamers\default.xbe dash4Name = c:evoxdash.xbe dash5Name = c:xboxdash.xbe So that it about the CEE, EEC, XBMC or X4G bioses. Some other interesting things which should be cleard up are, that even the name “noDVD” seems to say that you don’t have a DVD drive, that is not true. As we all know the XBox will not boot up when you remove your DVD drive or it’s gone bad. A noDVD bios just disables the check for it so the XBox simply didn’t care if it’s there or if it’s working. And because more and more drives beginning to fail because they get old it’s a smart choice to flash a noDVD bios. BUT you have to keep your eyes open. Because, since HeXEn/TruHeXEn has faulty noDVD bios on it, ppl. Start to belive that you can’ t boot a DVD and some just belive you can use it at all, like I said above. Both isn’t true. So if you have a “good” noDVD bios, you can boot/cold boot any DVD you want. Let’s take a look at the screen below. Screen : https://imgur.com/a/1KA1gmZ Like you can see, the left one is a “good” noDVD bios. It has still “default.xbe” in the DVD box. The one on the right is missing that. So even you have a good working DVD drive the bios don’t know what it should boot. That meens, when you have such a bios on your XBox, you will only be able to launch the DVD from your Dashboard but not if you power on your XBox with the DVD already in the drive. We have the well known HeXEn cold boot bug which hopefully get fixed in the 2021,2022,2023 version? We will see – or not. That depends on Heimdall and his finger. So whats left to say? Oh right. F, G or F+G. And what stand this letters for? They define the layout of the hard drive. So if you have a huge 2TB HDD in your XBox, you have to use F+G (Partition F and G) if you like to use that space. For smaller HDD’s up to 250GB max, a F only would be fine but, you could also use a F+G because there is basicly no downside (Did your PC care if you have just C partition even Windows supports up to 5 partitions? ). That leads us to the last question. Which bios you should choose? That depends. I would say. If you don`t have a 128MB XBox, I would recommend a “EvoX m8+ F+G noDVD CEE” bios. You flash it once and then you can forget it. EvoX is fast it does make the job well and you can do pretty much the same with it like you can do with the others. And if you have an v1.6 you have to use it in case you have a Aladdin, LPC2 or any other “cheap” modchip which just has 256kb. The other option for a 1.6 would be an x2 5035 but that’s an 512kb bios. But if you have a fancy schmancy bling bling 128MB XBox, I would choose the iND but, I have to point out here that there isn’t a “becasue of”. Some nerdynerds have a reason for that, I don’t. So… I think, thats it for this little weivrevo which turned out to be a little bit longer. I hope that I gave you some more or less usefull information and that I cleared things up a little for beginner or HeXEn/TruHeXEn noDVD user. If so, hit the like and subscribe button and don’t miss the next video … PEACE! PS. If you have found a typo, congrats, you have found the copy protection.

I'm currently looking into what BIOS images people prefer to use and which ones are more 'universal' than others.. Why? I want to make sure I hold the best compatibility for BIOSes built with Easy-Build.. Currently it uses the 2bl.img and remainder.img from iND BIOS 5001 (Which I use currently) I need to know what Bios Revision, size of ROM and MCPX version if you know it

Hello, i change my hdd drive to bigger 1tb drive and after succesful cloning i tried to format the new drive with XBpartitioner 1.3 and it complained about "LBA48 info not found! etc..(pic bellow) i tried to flash new bios with hexen 2018 but then that complained about "flash not writeable". i wonderd that do i need to get somewhere the newest bios and put it directly to my modchip via usb cable. our am i missing some step in this setup?

*Disclaimer: No links to file will be provided, this is for discussion only* Not sure if anyone has yet, but I have been running a diff between Barnabus Kernel Repack and the 4400 leak Kernel Tree.. I've only just started looking through, and I have next to no C++, C and C# coding skills so bear with me lol They seem somewhat the same, but there are quite a few files with parts of code removed or added, on both branches. But Barnabus is reliant on precompiled objects (obviously as it's a smaller, almost stripped down and made 'easy' release of the full tree) There are some comments in Barnabus code that isn't in the full tree + CPXXUPD code, and some are recorded more 'formally' (i.e private\ntos\init\init.c line 244 - 254 in both branches) One other thing is the 4400 tree is set to have 'complex's' edits definable where possible, which there are a lot.. One thing that really interests me, is Barnabus uses BIOSPack to pack: 2bl, remainder and kernel into a 'Working' rom (I use that word loosely). The 4400 tree uses rombld, which requires: preloaded, init table, bootloader, kernel and a rom decode file(I think).. this is a drastic difference to BIOSPack.. But the main issue with Rombld is it will not produce a full rom.. by default it will error on the 'preloader' being to big (9008 bytes not 1664 bytes).. To get around that, we can either build for XDK Systems.. Or as I discovered today: modify 'private\sdktools\rombld\rombld.cpp' Line 879 from (2 * 1024) to (21 * 512), to allow rombld to accept the 9kb preloader file.. (I haven't tested a bios rom built with this edit yet) I will post here anything else I discover!

Hi all, sadly the Xecuter X3 BIOS User's Manual has been removed from http://x3.bustedchain.com/ and from the team executer site. Does anyone have it saved as a complete webpage that I could go get a copy of? Would be most obliged if so thanks! Or does anyone know of any mirror still hosting these pages? Cheers!

I had xodus matrix on my ogxbox, and the original IDE HDD went bad, so I got my self 120gb SATA SSD harddrive, 80pin cable, IDE-SATA adapter. I decided to remove the chip when I removed the clock capacitor and reinstall it. I installed the new SATA HD with the adapter and I try to boot-up I don't get xodus matrix Bios at the bottom of the screen, and Hexen 2020 does not load. I am not sure if I need to re-program the chip and reload the Bios (which I no longer have) again. I still got the programmer board, and the loader winLPC tool...any advice what/where I get a BIOS to move forward and make sure it is not a modchip issue

Hi everyone. Recently I've been watching some ModernVintageGamer videos on YouTube and really wanted to get out of the drawer my old modchipped Xbox. It wasn t booting anymore because of a dvd reader failure(error 11 and 12) so I got a used xbox for spare parts off eBay,got the dvd player out of it and put it in my Xbox. The Xbox boots but it won't read even original disks. My question is how do I understand what modchip is installed? Can I run any sort of homebrew via USB and upgrade my HDD ? Thanks in advance.

Need to upgrade my original XBOX to SATA harddisk with IDE-SATA adapter Any BIOS flash recommendation for xodus matrix modchip? I do have the programmer and wintool to flash the BIOS, I believe xodus matrix is 256k

Really just double checking I've done everything correctly before going ahead with the flash on an Aladdin XT Plus2 in a v1.2/1.3 Xbox. It is an edited version of TruHeXEn's evox.m8plus.f.c.137.nodvd.bin. Changed the Xbox logo etc to match the Aladdin red chip theme, might modify this later if it doesn't look good. Also thinking about designing and importing another EvoX logo - details on how to do that are included wit the EVTool but if anyone has any additional information on this please share. Major changes are the boot priority: C:\evoxdash.xbe is default but I've changed the other two as the other HeXEn ones used are not applicable. The C:\default.xbe is UnleashX v584 whereas my main dash is UnleashX v572. I wondered if that was sensible. If the C:\config.xml they'll both use was corrupted neither would work but I'm not keen about using a different location ie. F:\ as I tend to copy/delete more stuff on that than anywhere else. Other significant change is the partitioning allocation. I don't envisage using any HDD bigger than 500GB and TBH I do not see the point of using a G:\ drive until it is actually required whatever the HDD size. So it made sense to change that to Partition 6 takes the rest of the drive instead. Size is 256KB and nothing apart from the above has been changed. I intend to use a dedicated EvoX v3935 dash for the flash rather than HeXEn simply because I do not want my dashboard messed around again as happened with the same unmodified BIOS TSOP flash I did on another Xbox. Any general comments, obvious mistakes, problems?

Is there a way to Force a BFM BIOS to set the clock speed of CPU,GPU,RAM?

Hello friends I opened my Xbox today to see which mod chip is installed because I bought the device used. It turned out to be a Super Aladdin live chip. I would like to install a larger hard drive with 2TB. I've already ordered the adapter and cables. Now I am wondering if I have to flash my BIOS and which one I should use on this chip. Since I almost never flash, I have to rely on external help. I have already figured out how to format the hard drive with Hexen. It looks like I have Evolution X as an app on the device, only the sign is not displayed to me when booting. My Xbox says OPENXDK at the bottom. Thank you in advance for your help.

As I've been TSOPing and chipping recently using customised BIOS I thought it would be a good idea to add the MD5 hash info to all the programs that can make use it: XBMC, EvoX and, of course, BIOS Checker. All three have slightly different syntax requirements apparently but whatever I did I couldn't get BIOS Checker to recognise the custom BIOS I'd added. The cause and solution turned out to be very simple: I was pasting in the MD5 code from EVTool, which has an option to copy it to the clipboard. Sensibly it uses lower case letters in the ID string and after half a day wasted, thinking I'd made some syntax mistake, that was the problem. BIOS Checker does not recognise lower case letters. It will report the correct MD5 hash but say the BIOS is unknown until you change them all to upper case. I'm sure somebody must have noticed this 'quirk' before but I couldn't find anything about it so I thought it worth posting about it here.

I have a crystal xbox with a aladin Live chip. i modded it very long time ago now i want to give it to my kid and updated everything then flashed the bios before i know it it wont start up anymore. i have eeprom and the hd is 250gb. I have no old computer to prepare a new hd. I have a other modded xbox with a aladin xt (not plus) but i dont know the what diffrent. I have 4 xboxes 2 without working DVD drives, i bought them when they came out. (Softmodded) Can i prepare a new hd in a other xbox. i was trying to put bios chip from one modchip to another that did not work , dont know why bothe had evo x on them before. Crystal xbox i try to repair is my first xbox so i really want to fix it. i have a backup of all the files on de hdd. Please anybody have option to fix this. i live in the netherlands.

I"m seeking advice on upgrading the Bios on my original Xbox due a larger hard drive installed which also needs a 32k cluster size. Therefore I'm after a better and known BIOS which has LBA48 (+137GB) and only enables partition6 (f:). Xbox info (Known) Console model: v1 (0a) Mod chip: Super Aladdin Live Hard drive WD 500GB (PATA) *NOS DVD: Thomson (yuck!) so little luck making it boot CD/DVDs Kernel Version: 1.0.4981.6 Current Bios: Unknown - possibility custom (Xecuter2 4981) Currently the xbox HD is formatted 16k cluster size and I am experiencing issues in relation to this and want it to be 32k. When I run XBPartitioner to correct this, it displays: Therefore I just need a more recent bios with LBA48 v2+ that also keeps other feature like In Game Reset (IGR) Which is why I'm asking this question to you. From my research I've learnt that for BIOS that enables partition #6 is labelled as x.06 for both partitions #6 and #7 is x.67. I've read that Aladdin (mod chips) will only take 256k (default). Inside the xbox is the Super Aladdin Live and know little about chip size or amount of banks as only I've found was on the knightdiscount website. Since my xbox possible has Xecuter2 4981, thought these would be go choice: Xecuter2 4983 however after looking at: I have been look a the All Retail Bios Information chart on this forum. All I know if I flash the wrong bios I'll have to re-flash it with hardware I just don't have. Thanks in advance!

Hey guys, So I have a project where I was able to come in possession of what im assuming to be a original Xbox test kit motherboard. The reason I say this is because it is an xbox motherboard with an MCPX X2 as appose to the X3 and yet it only has 64mb of ram soldered to it. It also looks like one of the previous owners tried to run Hexen and flash a retail bios on it since the solder points have been connected. Since (I'm assuming) it has a retail bios loaded on it it wont boot due to the lack of hidden boot sector in the X2. Ive finally fixed some OpenXeniums ive been working on so I have access to a couple modchips that can fit 1mb bioses in them. I am wondering, with the lack of 128mb of ram on the board, does anyone know if the development bioses will still boot to a screen showing something at least like the startup animation? I would like to see if the board is at least still functional with a proper bios and not completely nuked since it is currently in a state of FRAG that I hope is due to a retail BIOS being flashed on there. Thanks

i flash custom evox bios, after that it just not boot, and switches to stock bios. i use raincoat to flash. board is 1.6 and i use evox.m8plus.v16.fc.137.bin from aid 4.5.3 i have no idea what i do wrong. i then reflash it with hexen 2017 and it work OK.

I have a v1.0 original modded Xbox, it had an old Aladdin mod chip, I wanted to upgrade the hard drive and after doing some research I found out I can brick it by flashing a new bios. The bios is unknown but after running bios checker it reads I have a lpc sst49lf020, it boots up xecuter2 into an evolution x dashboard. If I use the hexen 2019 disc, what steps can I take after I install a larger hdd? I don’t need to clone it, I backed up everything using ftp, and I want a fresh install. Here are some images that may help... Thanks for your time.

Picked up a crystal green OG last week. When I power it on I’m getting 3X boot and frag. The person I bought this from suggested I flash bios but he doesn’t remember what mod chip or bios it has running now.

https://gyazo.com/8f116b4a34f4e478647879340b7f74aa what bios @SS_Dave do you think i should go with? 1.4v revision

Hello all and sorry for the "newb" question. I have just purchased 2 OG Xbox's, one is a 1.0(shown in picture) and the other is a 1.6. I currently have the 1.0 with a openXenium, upgraded to 2tb and just recently painted / led'd it up! I have it booting to the openXenium screen, I can FTP to this machine and see all folders. What I'm looking for is, what bios and dashboard do I need for these two? Its been years since I did this stuff and originally had the X3ce but sold it long ago...... Any help would be greatly appreciated!