Bowlsnapper

Well I think the power cable is bundled with it, kinda like how it is with the regular startech. Could be wrong about that though.

This is so unbelievably sick. REALLY nice work.

There's also this thing. I could've sworn I've seen people use it before. No IDE cable whatsoever. That would be a good candidate for the Nemesis Dual Fan Kit. https://www.startech.com/en-co/hdd/ide2sat25?srsltid=AfmBOopWd9DLTktm0UrvFIDlnlfEX9iQ_GocpmIGZnO26s6itMNyAUTWHGk

Also, keep in mind that if it is a normal IDE cable not designed for the Xbox, its connectors will be backwards and mirrored, which means you will have to do a lot of folding. and it will be messy looking. If you are able to order from the links I provided above, they should be a direct drop in. @properauthority Didn't know you were in Canada. I thought there may be a reason why you were trying so hard to locate a seller.

I'm glad you got yourself soldered and are doing an X3 hardmod 100 percent! Rock on.

@OGXbox Admin Posted this guide several years back, showing what points to solder. Once you do, the flashing options will be your only concern. Other than that, there is really no need for an updated guide. It's thankfully relatively simple.

There are a couple options. The first is a roundabout way of doing it and requires utilizing a game save exploit, whereas the Endgame exploit only requires you to be running the MS Dash at that moment. Both accomplish the same end. You know how to TSOP your console and have found a worthy and helpful guide?

What the HELL? It looks like the Xapter inserted some kind of sleeves to your LPC holes. Those are not normal. The spots you see open are what they are supposed to look like.

OGXbox Installer and Cerbios 2.4.1.

Hell, it's only a few bucks. Try it! Worse comes to worse, you could get one female and one male with wires, solder one end onto the contacts on the chip and then solder the other fitting to all the solder points you need, then just plugging the two together.

Link to the Ebay one.

Sorry, I had no idea what you were asking at the time. Why is LFRAME me necessary, even on non-1.6 consoles?

Which video? What are you trying to do?

Yes, the member pulled his links late last year. The download no longer exists and does not work. Why do you need Evox? Does Cerbios not meet your needs?

Good point. I failed to catch the ".ca" in his Amazon link. https://www.ebay.ca/itm/285741611164?itmmeta=01J33VP4X7Q2YYWCD2F6XSE0R4&hash=item428786f89c:g:DpsAAOSwsQRly4bo&itmprp=enc%3AAQAJAAAA8ECnIncpP0mg3dO9zJcb2VEb2rM0kiV1r93Y0QfOO7NA4010NNB1a0SXl%2FNetUQ6vZBee4fo532kFZSVCWfDbHifXT87SuW75gxTa1D5NVxzhcWrKtdLG4GUYs8VXON3Be5NtIC2qWZ3P8NJku2Mqxfnos8ovKib%2FNp7EskKHx6ymTBFVFtrPtqwNdDNEQrnqhAM9wstvb7%2BmOoQruT162pIYm4QCUKlkeYedWYML7rDXiWAOGI45zv%2B7qhnBmT%2F2Q63KmF7i3MdTKshlDGQ3PM5tjE1DE0828pgHiAN%2B1nNMtBEmL3E9gf1SMtBcZJBqA%3D%3D|tkp%3ABk9SR9rO2PuYZA

If you use the amazon IDE cable, it will work, but will require much folding and back tracking, as the connectors are mirrored and backwards. This ebay cable has the proper orientation and length. https://www.ebay.com/itm/264927666468?hash=item3daeeb6124:g:fDoAAOSwYVZfNwU1 I would NOT want to do this without a modchip! Good guide on doing so. I hope it helps people.

You should verify what revisions these motherboards are, as putting a 1.6 into any previous revision case can kill your motherboard, as a transistor grounds out into one of the screw posts that does not have a corresponding "screwhole" in the motherboard. Identify your motherboard: https://consolemods.org/wiki/Xbox:Versions#:~:text=The official PCB version markings,is found in 1.6 Xboxes. You can tell which screw it is by comparing the motherboard footprint against the screw posts that exist. You will find it. Remove/break off the RF shield linking at the post and it should be safe to install the 1.6 into a 1.0 - 1.4 case, if that is your situation. The AV port posts are also shorter in the earlier revisions, so take care not to overtorque the screws there. Swapping a 1.0 - 1.4 motherboard into a 1.6 case has no risk of shorting, however, the AV posts will be too tall and will need to be clipped/shortened in order to have the motherboard sit flush in the rear and become mountable.

If you do decide to buy a new console, I usually buy mine in the "Parts" category. Usually I go for "stuck" DVD drives, because this is easily fixed with either refurbishing the existing belt (by cleaning the spindles and boiling the belt) or by just replacing it since they are so cheap. I have like 20 sitting in a drawer ready to go. Sometimes I'll get other consoles if I am familiar with the issue and know that it will be an easy fix, such as dashboard or HDD error codes, if the seller is actually honest and posts what the issue is instead of simply pulling that "untested" nonsense and hoping that their console sells. Lol.

The readme does not say to "Smoke Weed". Lol. It says "4:20". I am Bowlsnapper, and so that is what I put as my signature. "Peace Out" Is Dark's signature. Although I've put in a few things already that make a small statement here and there at random just for fun, telling people to smoke weed is not something I would feel comfortable with saying outright and I think this would make the installer look unprofessional. Now, if people see this and decide that they wanna' smoke a bowl at that particular moment, I would not be opposed to this one bit. I actually noticed the VMWare/Virtualbox discrepancy in the OP there and I planned to address that. I use the HDD image with VirtualBox, but it can be used with VMWare as well. The point I was making is that virtual PC software has its own software that enhances the VM experience, with VM video drivers, as well as LAN and a few others so that the user can have a more complete experience without generic drivers. I absolutely recommend this. I imported the HDD image file into VirtualBox and I use it myself. The disk image provided is VMDK file format and should be perfectly usable for anybody else as well. I loaded the image into my new virtual machine and then installed Guest Additions. It works perfectly. What the OVF will have however, is settings for the VM so the user does not have to configure them manually. This would be helpful and I will try to get it done before the week is over. https://smallbusiness.chron.com/open-vmdk-virtualbox-28847.html The "Default" or "BFM" options are not a point at which anything is wiped. It is simply selecting what environment you would like to boot the installer into. Formatting occurs when you would like to use the standalone option of the installer, and this is well into the menu of both the BFM and Default selections. "Default" will boot you into the installer using the bios you have booted your Xbox with. "BFM" boots the installer by loading a Cerbios BFM bios into memory and booting the installer with that. The installer is identical, using both options. The readme's of the Standalone and Application modes of the installer describe the differences between both methods. This is not in the readme of the opening screen because you are not at that point in the installer yet. Perhaps I will add this information into the readmes so that there can not possibly be any doubt as to what is being done and what is offered at every step. I am looking at the Boot Menu readme now and I understand why you are bringing this up... the readme is practically blank. I don't know how I overlooked this. I will update this and make sure people are able to know what to select and why. I am now seeing that it does not state anywhere in the readme or the interface/installer that formatting will occur, so I will remedy this in a hotfix, hopefully by the end of the night. Hopefully the OP will tide people over for the next few hours. Like I mentioned, when softmodded, you have no risk of bricking your xbox attempting to install as an application. I believe that the application mode loads Cerbios Debug through PBL and should reveal the true C partition allowing for the boot of the XDK Launcher. Installing using BFM mode should also reveal the true C partition and allow people to access the true C partition and install the XDK Launcher. A standalone install is what is problematic. That's all. It can be done, but there is no reason to go through all the effort to do so when most people will be running on 64MB of memory anyway, and running a retail game is not guaranteed to work. Maybe somebody can convince me otherwise, but I feel that trying to debug retail games on 64MB of RAM reliably is something that would necessitate even MORE support and cause even MORE problems for people. "Heeeelp. I used your XDK installer because you said you can run it on softmodded consoles and the game I'm trying to run is crashing. What do I do pleeeeeeze!?" If you are softmodded, I would say that the installer is probably not a great option, even though it can theoretically be done. There are limits within reason for when this installer should be used and not be used and people should rely on common sense and reason in this instance. Nothing is stopping them. I assume MVG did not mention softmodded consoles in his video because this was an obscure use case. Anybody wanting to create a Debug Kit using a retail Xbox should do so after installing 128MB of RAM and this is what he covered. The Microsoft XDK recovery disc and remote recovery are tools meant to restore a damaged or blank HDD with a debug/development kit. The reason that this bricks your Xbox is that it flashes an MS debug bios that is meant to run on an Xbox that uses an MCPX V2. Commercially sold Xboxes use a V3 MCPX. This incompatibility causes the unit to brick with an MS debug bios. You seem like an intelligent guy and I have faith that you will not brick your Xbox and I feel confident that you have no reason to be scared to do anything since I'm sure you understand how this installer works, at least to some extent. I'm sure you can understand that the thread already contains much explanation and if my readmes are too long in the installer, people may get bored or overwhelmed and simply exit them and just proceed without reading everything. I do not want this to happen, so I will create a zip instead of simply hosting the ISO and put a lot of this information in there. I will also update the readmes so that things are as clear as possible in them. This will benefit the project in the end and I am glad that you have raised the points you have, as I stated in the OP that I am welcome to suggestions so that I can make the installer better. The thread that you are linking to was deleted for a few reasons. I made an effort to clear the slate and start anew. That is why this thread was created and this is the one you should reference from now on. The thread you are linking to is a google cached page. This means that you have been following the thread for some time and actually went out of your way to recover it. I am not sure why. I appreciate your suggestions as they are helpful and I am glad that you have taken such a strong interest in the XDK Installer in particular, especially for an extended period of time, but lets try to focus on the here and now, as opposed to the past, okay?

What country do you live in and from what websites are you able to order? Amazon, Ebay, etc? https://www.ebay.com/itm/264927666468?hash=item3daeeb6124:g:fDoAAOSwYVZfNwU1 These are direct clones, since the cable is a bit custom and is reversed and mirrored, compared to a standard IDE cable. https://www.amazon.com/CablesOnline-24-inches-80-Wire-3-Connectors-FI-U02/dp/B0B8RMS5CN/ref=sr_1_3?keywords=80+wire+ide&qid=1698428053&sr=8-3 This is a cable that many people use, however, it is standard IDE, which means that it will have to be folded quite a bit and will not fit as well as one custom designed for use with the Xbox. @nikeymikey I think that MVG may see it as an impressive technical feat, since the Stellar is capable of things that nothing else has been so far and I would like to think that he is impressed with it and wants to cover it, knowing that he has great enthusiasm for the Original Xbox. That being said, I find it surprising as well, for the reasons you stated. "Pimping" that Xbox was done rather incompletely, with that 40 wire IDE cable. Using something that is very closed off and not open-source is something that is unexpected from him and I can understand why that would raise people's eyebrows and have them wonder why. Even with Stellar's huge technical showcasing, what the scene has done in response to the product releases, with no real funding behind it, is jaw-dropping to me and worthy of its own special video by him, and there is much to talk about pertaining to this; much more than a 17 minute video could provide. You could go on for hours about the OX, ModXO, OXHD and other various things like Cerbios, ElpisHD and PrometheOS (let's not forget about XCAT!) that unlocks the potential of this hardware and provides some decent competition to MakeMHZ products... and there is no real money to be made here, which makes it all the more impressive. The motivation behind them would seem to be enthusiasm for the scene and a genuine desire to progress things, rather than to make a profit or corner the market, as it were. Lantus has thrown me for a loop for the first time ever. I'm sure he's watching the comments and understands that this is probably going to be a bit of a divisive video. I would be surprised if he does not have a beat on the pulse of the scene/community.

Thank you! I will attempt to actually put some of these things in the OP and try to be very clear about what options to choose and why. In the readme's in each section of the disc, I did try to be a bit descriptive about what each item was and how they were being performed, but perhaps the project release would benefit from some clarification. I appreciate your input and would be glad to do so. I'll work on it tonight. Option 2 above states that the installer "wipes" the partitions (As well as the readme of the Standalone" install section), so I was hoping that this would be clear in it's own respect, but perhaps not and could have been a bit too brief, allowing the reader to glance over it if they were not reading too closely. Yes, the readme states that it is for those versions of the Xbox, and that is because the RAM upgrade is so difficult to pull off on the 1.6 that it was just intended for those consoles, since most people would not have a RAM upgrade on a 1.6. Softmodding is tricky, since things need to be done a certain way in order for this to happen. As an application (utilizing PBL), I think it would work fine, but a standalone install needs to be done a certain way and there is no reason to do it, especially if you have 64MB of RAM. I plan on researching softmodding a bit more so that I can create an option for it, if the user wishes. Maybe I could get with @Rocky5 a bit and if he is willing, he could provide me with a bit of guidance in this respect. However, doing this install on a softmodded console in any state, either semi-permanent or as an application, still leaves the issue of having 64MB of RAM, since a softmodder is almost guaranteed to still have a stock amount. I think this is fine for very small applications, but is going to cause issues for a developer if they code something that takes up a fair amount of memory. In other words, it will run, but anything intensive that is run will probably experience issues since there needs to be room for the debug overhead. That is the reason for needing 128MB in a true Debug environment. In the spirit of having a true debug environment, I would like to mention here for the time being that if somebody wants to utilize the SuperIO serial debugger as I have done with my development kit, versions 1.0 to 1.2 is what I would choose, since LFrame was still hooked up to the LPC and you could extract debug output through the LPC connection. Versions 1.3 and 1.4 have LFrame disconnected from the MCPX, which necessitates some modification. But I know that most people will not be using the serial debugger and so this really is turning your box into a "Debug Kit" rather than a "Development Kit" which requires some hardware modification. At least that is the distinction as I see it. This project means a lot to me and I certainly don't want anybody to make a mistake that irreversibly damages their Xbox. I only want good things and good vibes! However, I can only put in so many disclaimers and warnings before I start getting repetitive and annoying in the readme's and OP and I don't want to make the disc seem like a ticking time bomb. "Danger, Will Robinson! Danger! If you run this installer, your Xbox may set on fire and burn your house down... and un-neuter your cats!" Lol. It is no more dangerous than an installer disc, as this regularly wipes partitions in many ways, albeit with fair warning. Thank you for taking the time to express your concerns in a constructive and polite way. I truly appreciate it. I will take what you're saying into consideration and try to be very explicit in the OP.

Matty Suds is THE MAN. His guidance and 3D prints helped me get my SuperIO internalized with the USB-C out in the rear. He recommended the adafruit USB-C breakout board and gave me the 3D prints to mount it. I'm surprised he doesn't have a place of higher prominence in the scene. His work is amazing. Do you happen to know what PETG filament that is in the top photo?

I was gonna suggest the same thing that @nikeymikey did. There are two ways to get at D0. One is at the top, just below the TSOP (which is notably harder to solder to) and the other is the classic point underneath. I would go underneath, as it's easier to solder to. I don't think I've ever used the top point. Some people don't like running a wire underneath and I think some people feel that it's cleaner to just go to the right of the chip and terminate the connection there.

This is SICK. I second @PRince404. Please tell us more.

I'm having trouble understanding. What price is the crystal?