MadMartigan

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.

Wow I am doing what they did to me lol. My bad. I started making the post and realized that it’s most likely the next person will be having an issue with updating theirs to XOS 2.3.1 as well. That’s where all my issues started. So I should first, test to see if the Xenium tools would detect the chip now. I’m going to test again in a few and I’ll post results.

Got this all sorted out and upgraded to Prometheos. I’ll make a new post with the explanation since this was a new issue without any info. The dev team will be addressing it as well.

Correct. I have two programs giving me the cold shoulder and one playing hard to get. If only there was a recovery.bin for 2.3.2 and above. The main goal is Prometheos which is a no go without xenium Tools working. Here is the same issue reported on github https://github.com/Ryzee119/Xenium-Tools/issues/8

I have tried that, yes, but it doesn't recognize the chip. Neither does the new Xenium tools. Xenium Tools Blue is the only program that recognizes the chip. I feel like I just keep saying this over and over lol. Addition: Recovery mode flashing works fine also, but there doesnt seem to be any recovery.bin files for 2.3.2 to allow that. That is where it switched to the FW Update.xbe method.

No matter what order I try to update in, I always get the error of " Xenium not detected", when attempting to run the xenium-fw-update.xbe That is a 1:1 of a Xenium Ice. I have the original. While they might actually operate the same exact way, I've not received any confirmation of this yet. I really need someone with experience on an ORIGINAL XENIUM to help with this.

This is the Blue version that was able to get me this far. It currently goes through as successful, but no update is actually applied and I reboot back to the 2.3.1 menu. While attempting to use the other Xenium tools to get PrometheOS, it can’t detect my chip. I’m stuck either way at the moment. Correct. This is the original Xenium chip. I’ve already done my diggin and see on Reddit where this seems to be a common theme amongst the first Xeniums. Of course they never come back and update the threads. Funny enough, a lot of it was old comments from Dtomcat18 in deferent places.

@ThairannyDid it say it can’t detect your Xenium as well or just overall issues? And do you have an original xenium? I fear this could be an issue with the OGs only.

2.3.1 currently. I had issues updating to that with the new Xenium Tools, but was able to get to 2.3.1 with Xenium Tools Blue. Blue goes through all the steps of 2.3.5 and says it was successful. But after the reboot, it reverts back to 2.3.1.

I have an original Xenium that I've tried to load this to and I’m being told by Xenium Tools that it cannot detect my Xenium. I see where others have had a smiliar issue with an OpenXenium, but I'm wondering if the OG is able to upgrade to this.

Yes, LPC rebuild is a very strong contender on being your issue. It's worth mentioning that you can get a small pcb board that rebuilds the LPC much more easily than the older ways with the jumper wires. You may already be aware of these. I use them on every 1.6 these days.

Yes, that's always a possibility. Check to be sure all the appropriate cerbios files are in your root C such as bios.bin, cerbios.ini, boot animations, etc. Also be sure you've got your dash files in there also.

First thing I would recommend is to look for bad solder joints on the pin header, under the board. Even if you don’t find any, it’s probably a good idea to give them a good reflow with the use of flux. Flux is important being how old and dirty these things are. It also doesn’t appear to have any wires for the chip, only the header. If that’s the case then it’s very strange that banging the console allows it to boot sometimes. Where are you banging on it to be exact?

Please provide all of the extra details as you can. Along with the questions in the above post, did you mod this yourself? Have you checked to see if all of the cables all seated properly? Error 07 could mean something is disconnected or your HDD is on its way out.

I swapped this out on a baord for the exact issue @KaosEngineer is speaking off. It fixed the 1.6 on the first try. I just pulled one from a donor board I had. I also agree that you can sell it or it would make a good donor board If you can't get it fixed.

I’ve refreshed more than I prefer and the files you’ve provided got it sorted. I’m not sure why this Xbox doesn’t play nice with the artwork installer. I don’t ever run into this issue, but that’s the fun of working on these. Always something new you’ll find. No my games are ion my F: partition and artwork is on the E: I’ve set custom paths to E: and everything else worked fine except for Tenchu. Works fine now after I manually installed the pack above.

From what I can tell on my end, Tenchu is indeed in the artwork installer, but it’s just a generic picture of the title. I’ve run the newest installer several times and it doesn’t download anything but that picture. No spines, 3D, case, dual, or anything. Now that I mention it, the current installer isn’t installing any of that stuff for me. Only the game covers for most games. I’m making one for a friend that only wanted 5 games backed up and Tenchu is the only one o the 5 I cannot for the life of me, get installed properly.

THIS. This is why Dark left the first time. Why can’t I just make a suggestion or ask the OP a question without you having some sort of comment either defending why your suggestion is the correct one or passive aggressively telling another member that they don’t know what they’re talking about? There is no point is such comments. I’m fully aware of multiple possibilities of why his picture may be messed up. If cleaning the ports out fixes the issue then that’s terrific. So I ask nicely, can you please stop stepping in front of other peoples suggestions? This is a public forum for everyone to post and this type of elitism makes even old users not want to stick round. We don’t need any gatekeepers

What region are you in? I know it's your old xbox but I'm curious if maybe you've moved or changed regions. Reason being is running a PAL xbox on an NTSC TV can also output in black and white.

Understood. I still should point out that the Wii2HDMI is very much a viable option for internal HDMI.