MadMartigan

Yes, please enlighten us. I had never heard anyone say this before then. Seems it would’ve been much more widespread news if this were the case, long ago.

Look for something similar to these icons.

Just to clarify this a little for anyone reading in the future. Up until a year or so ago, it was required to softmod your xbox in order to perform a TSOP flash. It is now very much possible to flash the TSOP at the same point in which you were to trigger the softmod game save exploit. You just need the TSOP flash game save files instead of the softmod. Same process, different results. My how far we have come.

Are you using Fatx 3.0 Beta? If so, were you prompted to download .Net 7 for it?

Coming from the wizard himself

That's great! Many times it is the simple things that are overlooked. I'm definitely guilty myself which is why that was my first suggestion. Happy gaming. In addition, sometimes people say they have a startech adapter when they're just mistaking any sata adapter. Wanted to be sure that's what you actually had.

They could be converted the same way or they could be slightly different. The easy way to tell is to compare the size of the files between the two. Otherwise, it’s still .CCI so they should work just fine. Repackinator gives you the option to compress the files and then take an extra step to trim the extra fat. This is how you can reduce the files sizes by such an insane amount.

Sorry, I’m on mobile 90% of the time and on the go. If he wanted to test then safe mode would utilize the UDMA2 no? Anyways, the OP did already state that UDMA 2 made things worse with his setup. I’m very curious to see a picture of what he has on his end.

Yes but I’d always know it wasn’t the real thing lol.

You know, I completely forgot about that. Thanks for bringing it back up. Unfortunately, my Halo is a 1.6 and I'd love to find a 1.2. I've had this one forever. Also, don't sweat the post in the wrong thread. It happens. You fixed it and all is well.

Where are seeing that it isn’t a 1.6? Also, this thread is to document rare consoles. Try to keep posts on topic or just start a new thread if you’re unsure. Good heads up on the console though.

Amazing. Yes, you can convert them again later if you choose. I don't have any info on Insignia for you. Sorry. Could always hard mod it and make your life easier.

Can you take a picture of the adapter and HDD while everything is hooked up please?

Repackinator can convert the full redumps of original game discs into .CCI files, which are compressed ISOs. Last time I checked you needed a modified bios(Cerbios) to run this type of file. Soft mods are not able to run anything other than the stock bios.

Once you run the program it can locate all the games within your specific folder and do a mass conversion. However, you won't be able to use the .CCI converted files on your softmod. You will Cerbios as your bios to run them. Someone correct me if I'm wrong here. Haven't dealt woth soft mods in ages.

You DO NOT want to use UDMA2. That is for stock IDE HDDs. You want UDMA5-7. I recommend trying 6 since you’re using a Startech adapter and an 80 wire IDE cable. And as mentioned above, check your cluster sizes.

What cluster size did you choose before formatting? Ideally you’d want 256k for 4TB I believe. 512k is more for above 4TB.

When you say, “rebooting out of games”, are you referring to IGR(in game reset)? This is usually pressing both triggers, Back, and Black together.

Wonderful pickup and a hell of a deal

Would love to see some results of you guys’ prints. I’m looking for a cheaper alternative for my crystal or skeleton. I’ll never pay market price for them regardless of my wants, but would be happy to purchase a nice print from someone here. However, I do have standards.

Ok, first of all, when the recommendation was made, it was for the XOS update, which still didn’t work. There was no need to rename those files either as they’re already there and ready. So how does that solve a Prometheos upgrade issue? Secondly, how many people have you seen in the past 15-20 years post problems because they renamed or moved a file that they shouldn’t have? With me not knowing about Prometheos(since it’s fairly new) my brain doesn’t tell me go renaming and moving things. I’d rather proceed with caution until I have confirmation, which I did not get here when reaching out. From you or anyone else. Lastly, coming back to say, “I told you so”, when you really didn’t, is a big part of why Sweet left. If you knew the solution, then why not actually provide it? On that note, I guess everyone that isn’t a master modder is an idiot to you. What’s the point of the forum if everyone already knows everything? Sorry that you’ve come to a place of idiots. Unreal

The few guides that were available for Prometheos upgrades were strictly for OpenXeniums, which most ppl had up to date. They overlooked older chips and potential for customers having them. They acknowledged the oversight by Implementing the TeamXodus chips with a different version on Xenium Tools. (EVERY OLD VERSION WONT WORK). They created two, new modified versions. With the new you can navigate to your file and choose it, but not two that the old ones. It only looks in the file that xenium tools is opened from. This is where my backups were already and the guides said to simply drag your Prometheos files into a folder. They weren’t as specific as they should’ve been. Once renaming the Prometheos files to flash.bin, erasing all old traces of thes files and recovery.bins, it was now able to see the flash and execute it. THIS STILL WILL NOT WORK WITH NEW XENIUM TOOLS, but it does detect the chip now. Ok I’m done retyping this over and over.

You did simply mention to try the old version of Xenium Tools and change the order or XOS updates which I was already using because the new version and MakeMHz installers wasn’t detecting my chip. That’s not what solved the issue and the XOS updates still didn’t work before upgrading to Prometheos. Don’t try to take credit for that please. The Prometheos devs found the issue and are working to fix it.

I recently hopped into the Prometheos thread here with trouble getting my original Xenium chip updated. I searched all over the web and only found users with the same issue and not one shred of evidence on how to get passed this obstacle, until today. Being that Prometheos is new and most everyone doesn’t run into the xenium tools issue, there was no step by step guide on what to do otherwise. Embarrassingly, it was a fairly easy fix, but risky without having full confirmation and no success stories to go off of. It occurred to me to just rename the files so the old Xenium tools would see them, since it doesn’t allow you to choose your file. I didn’t write these files and do not know the full extent of what they do behind the curtain so I ruled that option out and continued my research in fear of making a brick. I also had other flashers in different folders with backups for each one. In the end, with @Harcroft holding my hand, we got it done. He assured me it was ok to delete all the other files completely and go ahead to rename the Prometheos.bin file to flash.bin (this is also not mentioned in the text files) and put it in the folder with the the old xenium tools. That’s the fix and I just made you read all of that when I could have just told you outright LOL. The previous versions apparently weren’t designed to work with the old Team Xodus chips and this is already being addressed To summarize, users using very old XOS versions (2.3.1>) were not able to use the newest versions of Xenium Tools. The modified tools is included in the download for Prometheus 2.0.1. Be sure to be running a bios from your Xenium and not your TSOP, otherwise even the new tools will not detect your chip. Also you must rename the Prometheos.bin file to “flash.bin” and have it in the same folder as your xenium tools. DO NOT create a backup of your chip before flashing. This will cause the program to flash what you just backed up. I think that’s pretty much it. The dev team will have a much more professional explanation.

Confirmed working on an Original Team Xodus chip. After updating to Prometheos and adding the newest version of Xenium Tools, it does detect the chip as it added implementation for the Team Xodus release. So I guess technically it was a hardware issue, but is being addressed. I'm testing the different versions now and will post an update. Update: While the new Xenium Tools will detect the chip, it still would throw an error during the flashing process. I can confirm that I've now updated to Prometheos 1.0.2 using the older version of Xenium Tools.