Search the Community

What are the advantages and disadvantages of injecting bios config? Is it difficult?

On a TSOP v1.0 Xbox running x2 5035 bios, is there anything I have to to do to enable using the additional ram?

Hello All, I have what seems to be a fully working Xecuter 2.6CE in a Revsion 1.6. XBMC4GAMERS and games are working, but I can't seem to find anywhere in settings where it shows the bios version or that it even recognizes the Xecuter 2.6CE mod chip. If I hold the black or clear button on controller during boot, it just loads normal to XBMC4GAMERS. Same if I hold the power and eject button at same time on startup. I do NOT get a "Xecuter Rox My Box" logo on startup screen, but only "Microsoft". Is the "Rox My Box" only a X3 thing? I get a "Evo X" in top left corner of the same green xbox loading screen. Just curious if my bios could be a better version or if I should just leave it all as is since it is working. If I select Bank1 or Bank2 on the switch on front of unit, both load fine and work, but seem identical. Where do I find what bios version I have? Thank you!

Hi everyone, I'm new here. Long story short. I'm trying to install MakeMhz XboxHD+ Hdmi Mod to my Xbox with 1.6v motherboard and 2TB HDD. I'm stuck with BIOS patching. Patched BIOS gives coma Console issue. All I get is steady green light on Xbox and black screen. All patching was done following official MakeMhz guide with EvTool 1.0.9 and correct ips file. Unpatched BIOS works just fine. I'm using Evox M8+ 16 Bios with OpenXenium modchip. Can't figure out what I'm missing. Tried different Bios'es. Also tried Using my old Aladdin Chip with same result. After patch is applied and flashed, I'm getting coma console. Also EvTool 1.0.9 won't recognize patched BIOS, gives me Unsupported kernel error. BIOS that I've tried to use, MD5 Checksum matches (as per MakeMhz website). Any help would be much appreciated. As I've been trying to work it out for two weeks now.

So I modded a 1.6 with a OpenXenium chip and flashed Evolution M8Plus 1.6. I upgraded the harddrive successfully and was launching into my new dashboard with no issues. I then went to flash a version of the EvoxM8plus that forces 480p and when I restart to test the flash I am greated with an error code 9. Brand new Seagate Barracuda 2tb HDD(ST2000DM008), brand new 80pin IDE cable, brand new startech ide to sata connector. I have removed the 480p bios and still getting the same result. I have removed the disk drive and still getting the same result. From my limited knowledge I feel that flashing the 480p bios is not my issue but that was literally the only thing that changed between my last successful boot. Trying to dig out my SATA to USB to look at the HDD on my PC but I have no other ideas of what could be happening, do I need to recheck my solder points?

Hello All, I finally got my Xecuter 3 CE working! I had to swap to a whole new console since the video out died on the old one. Somewhere in the troubleshooting of the old console the bios seems to have been wiped from the Xecuter 3 CE. Currently I am succesful getting it to boot to FlashBIOS 3.0.1, but don't have a file to load there. I've been googling, but most of the old download links are broken. What is the latest version Xecuter Bios that I am looking for? Anyone have please? Should I load it on both 1MB banks so this doesn't happen again? I've been out of the scene 10+ years, so I welcome any advice. Thank you!

Hello So I have a Chip called a jafar, Its an upgraded Aladdin XT with Xblast. 1 Bank of 512, 1 256 and the last 256 is reserved for the Xblast which always boots first. My Question is how do I get Dual Dashboards with this? I have UnleashedX as I've always liked it but want to give XBMC a try Ideally I'm looking to have say Unleashed X boot with the 512mb X2 5035.137 bios and XBMC Boot with the evox.m8plus bios or visa versa After extensive searching online I am none the wiser, Could someone point me in the right direction to get started?

I'm thinking the Ind Bios 5003-5004 as they also have support for 128mb ram

G'day mates ! (typical aussie speak i swear) I've had a bit of a break from the OGX scene however I am back now and picking up the peices after I did what I wanted to with some old projects. Thanks to @SS_Daveive got a $20 bargain 1.4 board working again (afte I butchered an LPC build) however I want to extract an old bios file I wrote a couple of years ago on my Duo x3 chip. Whats the best tool to estract it and then edit it to see what is in it so I can modify it for this new box. As I have a strong feeling the file I wrote was for a slimeline I made with a DVD delete, however It has some colours and settings I changed that I want to use for this new OGXBox. Cheers - Dan

I have a 1.1 Xbox with a tsop. I've done a few and normally stick to Evo, Xecuter or Ind BIOS but the 256k versions I'm looking to flash my 1.1 with a 1bmb bios and have 2 questions. Which should I use from the list below? Once Flashed, Will my Xbox boot as it normally would onto the dashboard with the full 2tb HDD or am I likely to encounter issues? This is from Hexen2020 I'll be using XblastOS to flash the bios

Hi, I want to get back into making custom x2 4981 bios's but need the XBOX TEXT.3ds file as mentioned in the screen grab below (x-projects.org is long gone). I know I could use a newer bios but I liked messing with this particular one and having everything on the tsop rather than having a config file on the hdd. If anyone has it could you please PM me? I have 3ds max and deep exploration but I can't find this, any help or links appreciated

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.

As in the title, my xbox is TSOP'ed and splited with a switch for dualboot.

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.

I'm looking for a replacement sticker for the X3 BIOS bank selection switch or a replacement switch if anyone has one spare in the UK? I am also looking for an Xecuter XLCD kit to complete my X3 install (this isn't a huge loss if I can't buy one and I don't mind going down the DIY route for this if nobody has one they want to sell - I've had some great advice from the XBOX-SCENE guys regarding what parts to buy). Please let me know if you can help. Thanks.

Hi Everyone, I am new to this forum and despite looking, I couldn't find an answer to my question. Basically, I have an Xbox v1.1 with an ST TSOP. Awhile back I TSOP flashed it using HEXEN 2018 and I flashed on the EvoX M8 + F & G Bios. After this I installed a 2TB Sata HDD and Set up the HDD with 1TB assigned to F and 1TB assigned to G. Over time I have filled up most of the F partition and a lot of the G partition. I want to reflash a customised version of M8 + with no evox logo and my own boot colour scheme but I am worried about some of the options (I am basing the new customised bios on the file "evox.m8plus.fc.137" taken from my HEXEN 2018 iso.) I think I installed the 256k bios initially (even though i know my TSOP has more room) and I'm thinking of keeping it as 256k. Is this what is recommended? BUT mainly, do you think that keeping the LBA48 support setting as "Partition 6 takes up to 137GB/Partition 7 takes rest" will ruin/alter the partitions of my current installed hard drive as described above? I ask because I have about 1.3TB of data already on the HDD and I don't want the BIOS re-flash to wipe all of that just to get rid of the EvoX logo and change the boot colours. Thanks in advance people!

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