All Activity

My intentions are not to be vague. Showing that the initial release is lifted from S_tellar also affects the other releases. The method names are visible in all of the screenshots. If you would like to reference the later source code releases you can take the method/function name and do a search on the GitHub project. In this example you would arrive at https://github.com/Team-Resurgent/PrometheOS-Firmware/blob/f2ac58894fa71af0c4fcb7e98cd10ee9ff3829a9/PrometheOSXbe/PrometheOSXbe/hddVscUnlocker.cpp#L767 Because commit history is deleted when the main branch of the repo is updated (merged vs rebased), the commits are not meaningful for carrying any development history. . In the couple of places that the logic differs it appears to be compiler related or odd object oriented refactoring. I believe this shows an even stronger case of theft because it does not add up and is already addressed in the writeup.

You're being intentionally vague here. If you're confident your code was stolen, then cite the specific source file, function, or line from that GitHub repo. Right now, all you've provided are a few screenshots of disassembled code that don’t match 1:1, along with accusations of theft based on correlation rather than concrete evidence.

The samples provided have all the necessary labels that correspond to both that binary release and all later source code releases. https://github.com/Team-Resurgent/PrometheOS-Firmware

If the same connection can be made to later source releases as you said, why have you not cited that source? Clearly if it's there then it's there? Assembly level similarity doesn’t automatically prove source level theft, especially when dealing with functions that are standard across kernels or BIOS'. If the concern is code theft, shouldn't we be looking at actual source code, function signatures, or comments? Assembly will naturally resemble each other when implementing the same logic on the same hardware when things are built for the same purpose. Your screenshots show nothing more than similarities in the assembly, not actual blocks of the same assembly. This would imply that the end result is the same or similar, not the code that was compiled to get there.

The examples provided in this case are based off the initial release of the feature as it's the original source of the theft and the same connection can be made to the later source release. As to why our code exists in PrometheOS, and Cerbios, I couldn't tell you. If it was a case of reverse engineering then we would not see our code in any release (binary or source).

So at one point in time, there *may* have been code theft and you cannot verify this is the case now via the opensource code that is available? You're also citing common development techniques as stolen, if they had ripped your code by decompiling it, wouldn't they be able to release a clean decompile of the Xbox Kernel since that's what you claim to have done? Why would someone go through the trouble of decompiling your entire stack, for that nugget of code, and not the rest?

The samples provided for PrometheOS are from the release binaries of PrometheOS that include Cerbios. The code in question is labeled. The release in question regarding HDD unlocking does not have a source reference because the source code to v1.2.0 was not released, but correlation can be made to the source that is published. For the portions covering theft in Cerbios the only reference is from their own releases since the project is closed source. Version information is included in the samples provided.

Ok, so with any other XBE on the Xbox, are we going to accuse those projects of being part of Crb? In your own words, Prom is an XBE. It's a similar design as X3 Config Live and the X3 BIOS, where the XBE can be injected. Prom does not *require* Crb to run, and again the source is available, so please cite the source that was ripped from you and let the community come to a conscious conclusion and take reasonable action.

Cerbios and PrometheOS are addressed separately in the write up. PrometheOS is grouped with Cerbios in terms of discussion since it's shipped with it as the kernel/BIOS. The screenshots are cropped to highlight the topic of discussion. It would be pointless to post screenshots of the whole article as that would make following the additional written context a challenge

You're once again grouping two separate projects together. Crb and Promo are not maintained by the same people and one of thems source is easily explorable and verifiable. Your screenshots are also conveniently cropped to not really explain anything to the end user.

The issue with PrometheOS and Cerbios are in the article and go beyond a simple GPL issue. These are the issues that are unaddressed and unresolved. * This screenshot is just a portion of the write up. We have no issue with Modxo by itself. It's the boards that are sold as circumventing the X_boxHD+ with an STM32 to run our firmware and code.

Understood. Thank you for being clear. I want to clarify, and I implore you to check the links I provided. Dustin is well within his right to protect himself and his products, when he and/or his products are actually being targeted for something.

I'm enabling post approval. I want people to be able to communicate but I don't want it to devolve into a completely unproductive flame war. I'm trying to get to the bottom of all of this but my understanding is pretty limited.

Once again, you're lying and making absurd claims. Every single one of your claims was debunked, and you've done nothing more than continue to block the people you have accused when they came forward. You're trying to pass off a narrative as being the victim of something, while bullying others. You're grouping everyone together, because you cannot take the time to be honest and decipher who's working on what. If you have a problem with Nemesis, or Foxbat, then call them out. "PrometheOS and Cerbios boards" makes zero sense. PrometheOS is opensource, it's code is available. The code you filed a DMCA complaint against was a C-Struct, and the code used was open source as well. That's how they got it. They attributed it to GPL3, not GPL2.. OH NO. ModXo is not an HD+ circumvention device, again, you're blatantly lying. It's a RaspberryPi based Modchip. Furthermore, Microsoft's code is not yours to defend, which is wild considering you yourself use "stolen code" to test your HDMI products. That dolphin sample isn't yours to use. Stop attacking an entire community, because you have a god complex and need to be right, you can also put your dog back on its leash, when his history is just as dirty as yours. The entire answer that you keep avoiding is located here: https://archive.is/Tnet1 When this was brought to your attention, you once again blocked it, saying it was never done: https://bsky.app/profile/milenko.org/post/3ltaod3fiw22h Many people enjoy your products, and you're on this downward spiral of self destruction because you need to be the center of attention, and the authority on something you didn't create (the community, not your product) Stop making the false accusations and solely go after the actual issues surrounding your products, not trying to take down portions of the open source code or making stuff up to fit your narrative.

Download: https://bitbucket.org/prehistoricman/lpcmod_os/src/master/releases/ Changes since 0.64: Can now flash Sharp TSOP Xboxes. No need to use GentooX any more! Safer flashing. Xbox won't reboot if flashing fails, which is most important for TSOPs.

Hey everyone. There’s been a lot of confusion lately, and I want to clear the air as best I can. I’ll try to keep this post short and focused on the core issues. The Blog Post The reason any of this is being discussed right now is because of my recent write-up, Theft in the Xbox Scene. The post focuses specifically on the theft of code from X_boxHD+ and Project S_tellar. Everything else in the article exists to explain how and why that theft happened. That issue, the code theft, remains unresolved. And until it is, it’s something we need to address as a community. OGXbox Rule Changes We've had no part in the recent rule changes regarding Xbox HDMI projects or Cerbios/PrometheOS. I was honestly shocked to see them, but I understand why. I'm not the owner of the site, so I can only state on why I believe this change felt like it was needed. All Current Xbox HDMI HARD Mod Discussion Disallowed Counterfeit copies of X_boxHD+ have recently started appearing more often. These are not forks or open projects, but direct hardware clones made to run our firmware without permission. The OGXbox staff has been professional and responsive in removing posts about these devices, and I truly appreciate how they’ve handled it. I do not believe this rule was aimed at O_XHD. We have no legal issue with that project. Cerbios and PrometheOS Links DISALLOWED The blog post outlines in detail what was taken and the concerns we raised. I understand the forum’s decision to take a cautious approach, especially when the parties involved have yet to address the issue directly. DMCA Now that we have proof of theft, we are required to take steps to protect our work. That includes submitting DMCA takedown notices for products and listings that include our stolen code. Unfortunately, we have no direct contact with the people behind these projects. In the case of PrometheOS, while part of it is open source, many parts of the codebase have no identifiable authors. This lack of transparency makes it impossible to have a productive conversation or resolve the issue privately, leaving us with no choice but to pursue formal action. I know this can feel like it affects more than just those directly involved, and that is not something we take lightly. Our focus is solely on removing content that knowingly uses our work without permission. This includes. PrometheOS or Cerbios boards being sold with either included. OpenXenium products with PrometheOS or Cerbios include. Modxo devices designed to circumvent the protected works of the X_boxHD+. Acknowledgement At the end of the day, we all understand that this scene exists in a fragile space. Microsoft could step in at any point. But while we’re here, we have a responsibility to look out for each other and to create a space where ideas are respected and contributions are protected. None of this is about drama, gatekeeping, or picking sides. It’s about setting a standard that says theft and retaliation are not acceptable. If the theft is addressed, everything else can move forward. That is all we are asking. Even if you don’t agree with me personally, I hope you can see the bigger picture. We’re all here because we love this hardware and want to see what’s possible with it. Let’s make sure we’re building something worth being proud of. --- Please keep this thread on-topic. I’m here to talk about the actual issue at hand and I’ll do my best to answer any questions related to that. Thanks for taking the time to read.

Which site?

New to this forum (and this thread), but not the scene. I'm not interested in scene drama, but I do want to share my thoughts on this. I've been in and out of the scene since the early '00s in the X-S days as a contributor/modder, and love it when I find absolute gems like the work you've been doing, as it's hard to find any good/new work for a legacy platform (especially quality work like yours). I wholeheartedly agree with your take here - it's hard to feel appreciated when you have people trolling and/or making low-effort unfounded claims against you for no reason when you put in so much effort to help the community. I (and I'm sure others) greatly appreciate the work you've done, and honestly, would put in the effort to use your website and a PCB manufacturer over buying the Team Resurgent PSU anyways. I found the initial thread in question on reddit and the replies seem reasonable and in no way disrespectful. If you find this work is what makes you feel whole, I recommend you continue to do so and disregard the ignorant people - they are everywhere, and when I encounter them I don't let that dissuade me when I know the work I'm doing benefits the community at large for the next several years (or, forever - after all, The Internet Never Forgets). Whatever your final decision may be, I wish you the best of luck and thank you for the work you've done so far, both on your personal website, and GitHub (thank you so much for the Xbox USB-C PSU V2.0 update!). I hope to one day soon make some Xbox USB-C PSU's using the quality work you've done so far.

Just a quick heads up for you all - This thread will soon be moved to another site.

That's what I was gonna suggest. Use an LPC device. The TSOP may be damaged beyond what a reflash would provide or remedy.

I have been made aware that these are contentious bits of software as well. Do not link on this site to where to download them. Do not upload them to your post if that's possible. If you find them here somewhere, report them. You can discuss them. You just can't provide them or links to them here. Why? I was contacted by someone from another site who was given a DMCA notice. It doesn't really make sense that only that site would get a DMCA notice and this one wouldn't. This person even went through our site and provided the relevant links to remove. This WAS NOT the person from the company you're thinking. It was a person from another site who received a DMCA notice giving me a heads up. I have received several hate messages since posting this one. To a certain degree I understand. Do what's best for you. I have to try to do what's best here. Life's decisions aren't always easy.

Edit: To clarify, while legal concerns were raised, we were not directly threatened. They have reached out professionally in the past to express their concerns without any DMCA or legal action. We have worked with them to resolve those issues. Due to ongoing disputes over IP infringement claims, we have decided to attempt to stop all discussion of Xbox HDMI HARD mods on this site. We will not be discriminating based on brand. All discussion is hereby banned in an effort to not be sued. The HDMI mods are really for people trying to build the ultimate modded Xbox. The results yielded by the HDMI mods are very slightly sharper than the component to HDMI converters by reputable brands. They are almost indistinguishable and so are hard to justify for many due to their expense and installation difficulty. If the truth were really told, the installation difficulty is the main reason anyone has them... so they can show off their skills. The quality of the video output simply isn't that much better than component. (These comments are specific to the Original Xbox. Other consoles can actually have a dramatic improvement.) Component to HDMI adapter discussions are allowed. Hard modded adapters that intercept the raw video signals prior to the built-in video encoder discussions are disallowed. The threat of lawsuit against us is that we allegedly choose what can and cannot be published on our site. We are actually protected by law as media and exempt from most litigation due to our First Amendment rights to publish whatever we want as long as we are not directly providing something unlawful. We aren't, but this is also a public forum. We don't have the time to constantly monitor it nor are we attorneys. We don't intend for anything unlawful to be published on this site or to allow it to remain, but we simply can't catch everything and even if we could we do not know what is in compliance with the law and what isn't. Quite frankly, if you're not an attorney, neither do you. I'm referencing section 230 here. Section 230 protects this site from most things third parties (people posting to this board) could expose us to. One thing it doesn't protect us from, are claims of intellectual property theft. I have no idea who owns what intellectually property, who may or may not have used it unlawfully, etc. So, we've had to look at what to do about this. We can't continue in the current state because I cannot afford to be sued simply because I chose to create a site covering a topic I once loved when the main site had gone offline or was about to. So since we have no protection from this specific claim and since there is no clear indication of what is right and what is wrong I have only this one option to protect this site. The only reasonable thing for this site to do is attempt to stop all discussion regarding the HDMI mods creating all of the controversy, the company threatening litigation, the main person behind said company, any products they offer, AND any competitors to those products. I don't know what HDMI HARD mod is legal and what isn't, so the best way to protect this site is to block discussion of all of them. If you can sue us for (passively or unintentionally) allowing certain discussion, then we will attempt to comply and attempt to disallow all of it. There is absolutely no way for us to find every mention of every HDMI device that happened in the past. Please report those if you find them and if they are indeed HDMI HARD mods we will take them out of public view after we see the report. There is a lot of content on here and we can only do so much. -HARD mod means some part of the adapter installation requires the original hardware be modified in some way. HARDware was added to the circuit board somewhere OTHER than a port designed for devices to be plugged into it in order to modify the behavior of the device. Usually this means soldering was required, or traces on the circuit board were cut in order to intercept or redirect certain signals to make that modified behavior possible. -HARD mods vs SOFT mods. Hard mods mean hardware was added. Soft mods mean the mod was achieved via some form of software exploit. Soft mods aren't relevant here, but to understand the term HARD MOD it's important to understand the distinction.

Going to be brief. 1) I dont see any reason why anyone should avoid RedHerring32's power supply option. I have no doubt in my mind it works great. 2) I feel Redherring32 and I may have a common problem. Communications can be.. difficult.. Things dont always come across as intended. I have yet to see exactly what is incorrect with details on why, I say this because maybe you have and I failed to understand. If you want to reach out again, feel free. If not, I understand. Yes, there's room for improvements in my design. Already working on a improved version. The PMIC I'm using is an older chip. Because of that it's well documented, perfect for someone just learning. And that is why choose to do this project, to learn. 3) This is not the place. If we want to continue this, let's start a new topic here or somewhere else specificity for it. I ask that it stays strictly technical. Now my ears are ringing, I smell like burnt gunpowder, eyes burn from the bright fireworks... I hope everyone had a great 4th. -Andr0

So I tried the fix for the coma console, jumping wires A18 and A19 (All combinations) with no change, I know I have a modchip in another console, will try to boot that to see if I can get something to work, from what I have seen it has the exact symptoms of a "Coma" console.

A few quick questions for Rredherring32. Do you know which specific PMICs that Team Resurgent PSU is using? Do you have any real world objective measurements of what you claim? Is it all subjective eyeballing from pictures on reddit? Can you see the inner layers of the board (if there are any)? I'm genuinely curious. I can critique a PCB design too, but unless I have the board, or gerber files, or the board in hand I can't know with any certainty what's going on with that PCB. I doubt anyone can objectively.