All Activity

@OGXbox Admin right now I'm focused on what's in my write-up as it highlights the more important parts. It's a lot of information and I don't believe I can copy and paste it all here. There's a couple of questions you have though that are not covered in the write up though. I'll answers those really quick. X_boxHD+ Runtime This is software from X_boxHD+. Released around the begining of 2020. It's about 4,700 lines of code, but obviously a lot less once compiled. The work was copied to Cerbios and first appeared in the v2.3.2 release on December 31st 2023. It appears to represent the full work. This would also include PrometheOS as uses the Cerbios kernel in it's releases. HDD Unlocking This is software from Project S_tellar. Released on December 29, 2023. It's about 1,000 lines of code, but obviously a lot less once compiled. The work was copied to PrometheOS and first appeared in PrometheOS V1.2.0 on February 25, 2024. It appears to represent the full work. CPU Upgrade Support I'm cautious to go into the full details here as it seems Cerbios does not fully understand how this works and it appears only the core of it has been copied and made available. The sample I studied is the v2.4.2, but it could apply to previous releases either via Cerbios directly or PrometheOS. Everything else in the article is provide for context. I started researching this a week before the article was published. I've heard rumors that the X_boxHD+ and Steller were being reverse engineered, but never looked into it until then. This was after the constant claim that I was fabricating that these "projects are based on the stolen work of others". --- At some point, the authors of the stolen work need to respond. Ultimately, it’s up to them to refute the evidence that’s been presented.

Legend

@LoveMHz Ok. Thank you for that clarification. Could you please detail with as much specificity as possible exactly what software you're alleging has been copied or parts of it have been copied? If I can narrow that down to a file or two (I don't need filename per se but just something that distinguishes it would suffice.) I could start to make sense of what is at issue. What I need is: Product name / Creation date of said code / software or firmware? (choose one) / entire code or partial code? (choose one) / How many lines are in the original work? / How many lines do we believe were copied? / To where was it copied? (Name of alleged "product" that contains alleged unauthorized code use.) / when this copy was done or when you discovered it. I am trying to piece this all together.

I’ll do my best to respond, but I want to keep this on the topic of the theft of our work. It’s difficult to have any kind of civil or productive conversation when false claims about us are still being pushed without actually addressing the core issues. To be clear, I have no legal issue with Harcroft or O_XHD as a product. My concerns are with specific individuals associated with the project. Either directly or not. --- As for the GitHub repository that was linked. Yes, that is correct. This part of the project is shared as CERN OHL. The kpatch firmware source was shared under GPLv2, and it still is. That hasn't changed. --- At one point, someone mentioned that the sentence "Firmware is shared under GPLv2." was unclear. It was removed for clarity, not to retroactively change the license. For further context: the GitHub repo never included the on-device firmware for X_boxHDMI or X_boxHD+, in either source or binary form. --- Regarding open source: My long-term goal has always been to open source all of my projects, including S_tellar. And despite everything, that’s still the plan. But saying “I do not expect LMHz to open source anything” ignores the fact that every major release of Project S_tellar has included meaningful open source contributions to the community. I’ll fully admit and apologize for the delay in making more of the work public. But what I’m asking for is some perspective. From the beginning, there have been bad actors who think it’s okay to take our work without permission. That makes it much harder to confidently move forward with releasing more. Respect for open source also requires respect for closed source. Without that baseline, open collaboration becomes significantly harder.

@LoveMHz Do you dispute the validity of the github link above? Help me understand your position better please.

What I want and what would be fair are in two entirely different reams. LMHz absolutely owes an apology for every single comment they made that they knew to be false. LMHz absolutely should delete every reference to myself, Skye and Eaton on their blog post. LMHz absolutely should post a retraction and apology regarding myself, Skye and Eaton on their blog. I expect and honestly have no want for any of these things. LMHz made their choices and they can live with them. I also do not expect LMHz to open source anything for their modchip when they have already deceitfully released a product (HD+) as OS, scrubbed the license discreetly to try to revoke it https://github.com/MosesofEgypt/xbox-hd-plus The original license can be seen here. I posted that screenshot as another data point in the pattern of deceit I detailed in my first response, not to get them to behave differently.

After reading your entire post AND reading LMHZ comments regarding your project on this forum, it seems as though he is agreeing with you now. It seems in the past damage may have been done between you two, but from what I can tell right now, nobody disputes your work on OXHD being original. If I'm wrong then so be it but I don't see anything other than old things you provided. At this moment in time, I think your work regarding OXHD is unquestioned in its uniqueness and validity. As far as the screenshot you provided that said "everything would be open source at some point." I found that most interesting and thought about it for a long time. Then I did some research. Do you believe you or anyone else was deceived into collaborating with LMHZ at that time into providing work you believed would be open source, only to have it be closed source, used for an official product, and the contributor uncredited? If yes, that screenshot and said collaboration can be proven it has a LOT of merit. If no, it has none. Here's why: It doesn't give a firm commitment nor does it give a timeline. Everyone has the right to change their mind. If he were to wait until he was on his deathbed to make it open source, he has complied with that non-binding statement in his post. It just has no teeth unless someone can make the argument that their work was used for profit without their permission due to deceptive practices. It seems you want a public apology from LMHZ. I think if everything you say is true then that would be reasonable... however. Calling someone a liar repeatedly publicly won't help that. Few people in the world would do that. It could be seen as discrediting his other claims as though he could be wrong on them as well. (I would disagree. I think it would actually strengthen those claims because if you're willing to admit you're wrong when faced with proof, then when you won't admit you're wrong it is strong evidence that you are not wrong.) Extremely few people publicly apologize and admit they made a mistake.

I do not feel for a moment that you are attacking me. You may have seen my sympathetic response for your original lockdown post. I respect the extremely difficult position you are in. You didn't choose for clone devices to be posted on your site, you didn't choose for a user to issue you legal threats in order to control what speech is allowed. Rest assured though, if you are under the thumb of a single user based on legal threats like this, that will be the death knell for the forum. Controlling speech leads directly to controlling thought. The message is clear. The only Xbox HDMI talk allowed to be talked or thought about in the entire retro community is about a product by LMHz. I am not here to play for a mock trial. I am here to offer screenshots and links to facts. I have done that. I have displayed a clear pattern of deceit by LMHz. LMHz keeps posting vague accusations without any evidence. Believe them if you want. My experience tells me to not believe a single word they type. If you feel my post isn't safe to host on your site, you have every reason and right to delete it and I respect that. Thank you for giving me the opportunity to show the pattern of attacks, deceit and libel.

I apologize if it seems like I'm attacking you. I'm NOT. Right now everyone feels that if you're not on their side then you are against them and siding with someone else. I don't side with anyone. Who has ever sided with me? Lol... I'm only trying to make this productive. If this were a trial and you were called to the stand, you can't just keep calling someone a liar. They won't allow it. You can have facts to back it up, but everyone else has to reach that conclusion on their own. That is ALL I'm taking issue with. Name-calling even if you believe it is justified only serves to ignite the fuel that is already abundant around this topic.

Please show me exactly where I made any single insulting remark. Literally every word was backed up by facts. If you feel anything specifically is too harsh, please give me the ability to edit it for longer than normal tonight and I will make efforts to be less direct. I provided screenshots for everything I said. Anything you might be missing would be on my twitter posts about the OS video board project I can't name. I blocked several users so they could not keep posting hateful comments about MMHz/LMHz on my posts. I literally bullied the owner of a site called SourPineapples to take their site down off the internet as I felt it used my work in an unfair way to attack and belittle LMHz. I have been civil for over a year and a half. I have sustained all the attacks shown above, and more from LMHz that I don't have screenshots of. I have reached out in good faith. Friends of mine, customers of MMHz, friends of LMHz have reached out to them to tell them that he is dead wrong about the project. Months after explaining to xbox7887 why I chose the specific microtroller I did (to make it extremely difficult for an end user to switch it to use the HD+ MCU) I placed a populated 1.04 board in his hands. His exact words were "Yeah this is Ryzee's board." I have literally made every effort I can do not only do things cleanly, but to share that I am doing things cleanly. I have burned countless bridges with users who tried to get Op_enX_HD to be another HD+ clone. This isn't a matter of opinions. This is a matter of facts. MMHz chooses to ignore reality and continually attacks me and my work with libelous comments and blog posts that can't be interacted with. They have literally doctored screenshots to mislead the viewer into seeing falsehoods. I urge you to read my full response and Skye's full response on the X-S forum. We are extremely clear and direct about everything LMHz falsely accuses us of. We both include private screenshots of conversations that led up to VSC discoveries. I did not, and am not speaking on behalf of TR because I am not part of TR. LMHz' complaints about them have nothing to do with me. My concerns are the blatant lies and misleading comments regarding myself and Op_enX_HD. LMHz themselves have said they don't have a legal issue with the project. This is an admission they know there is nothing nefarious going on with my work. Yet they choose to lie, slander, libel, attack, the work and myself unfettered. Edit: The one good thing coming from all this is LMHz has angered enough of the community that people are actively contacting me to find out how they can contribute to the codebase. Being the sole source of the current hardware design this gives me control over who can and can't contribute. If I start to see anything underhanded I can remove that contributor from the project.

I don't mean to discount anything... but I'm trying to get to the bottom of this. I'm trying to (albeit with very limited knowledge) pretend as though I'm the judge in this case and how I might rule. (not outwardly. I know I have no authority in the grand scheme of things. I'm talking about in my mind to try to determine who is right.) The judge will view the case in the light most favorable to the plaintiff to test and see if it has merit. If I were that judge, I'd first ask for the timeline of when the code first existed and concrete PROOF of WHEN that was, then who created it. Only then is there a case. All of this he said/she said back and forth and character assaults don't matter. The ONLY thing that matters is the timeline and PROOF of it and who created what. Once that is established, this all becomes clear. Until then, it's just a mudslinging circle jerk... one that I'm attempting to avoid. @Harcroft - I can tell you feel passionate about what you say but given that this very easily could go to court I was hoping to keep all of the insulting remarks out of this and stick to JUST the facts. It can only cause the thread to devolve or become ignored. This is tearing up the community at present and it would be extremely beneficial to sort it all out and put it all to rest rather than continue character assaults etc. I understand that both sides feel as though character assaults are happening to them. It's happening to me too. We just have to stop caring about that. What other people think of any of us truly does not matter. Their opinions do not matter. The facts and the truth is what matters. Let's sort this out prior to any lives being needlessly ruined during litigation. If you've seen the leaked screenshots of my chat you know I cannot afford to be sued. I simply cannot afford the representation and even though I don't believe I have any liability to this point, I'd like to end this. So EVERYONE please, let's keep it civil. Let's get to the bottom of this once and for all. Establish your timeline and provide FACTS you created what you created since both parties are claiming credit. Whoever can PROVE what they say is the victor and gets their way. Whoever CANNOT or DOES not prove that, obviously cannot prove what they say and that also puts this whole thing to bed. Let's act like adults and get this over with once and for all.

I'll start with I know this is a giant waste of time. I know even when clear proof of deceit and wrongdoing is shown, LMHz will never admit to being wrong, he will double own, and lie more, feign ignorance, and pretend the proof does not exist. I am used to this and would expect nothing different. With that being said, here we go. Two people can not have a civil discourse if one party is dishonest. This is exactly why I do not communicate with you directly anymore. LMHz, there is one single glaring issue with your post here, one long standing commonly repeated problem with literally any words from you. You are a liar. You are deceitful. I do not mean you may have accidentally misspoken, or incorrectly commented on something you didn't fully understand. I mean you seem to be incapable of writing literally anything truthfully; whether it's a forum post, a blog post, a discord comment in a public or private server. a marketing post on your site, a marketing post on social media. Every single interaction I have had with you, every single interaction I have seen you have with the Xbox community you have either tried to deceive the community somewhat covertly, or you have directly and overtly lied. I am not saying this to attack you, this is something you have shown again and again to the entire retro gaming community. I'm not going to get into details about when you held customer orders for more than 6 months so they couldn't do a chargeback, while ignoring customer inquiries about shipping. I'm not going to get into details about you promising features on your modchip that either get pulled, or show up years later than promised, despite still advertising those features as currently supported on your website. I'm not going to get into details about the many times you claimed features on your modchip are the first of their kind while they have existed in the Xbox homebrew community for well over a decade. I'm not going to get into the details about how you released your firmware under a GPLv2 license, never posted the source, then tried to hide you scrubbing the license from GitHub when you found someone (not myself) was trying to clone your hardware with the intent to use the firmware you lied about being open source. No, instead of focusing on the above things you have absolutely done and are well documented on Github, Reddit, trustpilot.com, etc, I'm going to focus on my direct interactions with you and the times you lied about me and my projects. January 10, 2023 I had a discussion with you and Redherring32 on the Insignia discord server about needing a replacement for XLAST for my Xbox Live data preservation work. You claimed every tool in the XDK had an open source replacement. That simply was not true.The only way I was able to get any answer out of either of you was to answer the question for you based on your unwillingness to be honest and/or direct. The conversation ended with you claiming you were "...just trying to put that into motion." That was a lie. Bonus points for lying about open sourcing any components of your modchip. These things are extremely minor, so lets move onto more important matters. "I do not believe this rule was aimed at O_XHD. We have no legal issue with that project." You have no legal claim against Op_enX_HD because you know it is clean, free from any inspiration from your hardware. You just have many, many lies to tell about the project and myself to discredit it and mislead anyone who reads your words about it's clean development. Lets begin: Early December 2023, on this very forum there was a huge amount of drama regarding hardware that I completely agree appeared to be a clone of your video output board. Instead of joining in to a pointless battle, I in good faith started working on Ryzee119's HDMI concept board to try to bring it to completion. https://github.com/Ryzee119/Xbox_HDMI-Ryzee119 The goal of this was to give the entire community/scene an outlet. Somewhere to focus their energy positively instead of continuing with you feud between yourself/your friends and Nemesis. This worked! It worked for a while anyway. Tensions simmered down, people stopped talking about the Nemesis vs MMHz drama. December 25, 2023 I announced I was working on Ryzee119's HDMI board on Twitter. By then the community had nicknamed it Op_enX_HD. https://x.com/OGX_Harcroft/status/1739303743538037205 On this post, and every post I made about Op_enX_HD after it about your customers told me the way you treated them, or they outright attacked you as a person and a business. I asked every single one of these people to refrain from commenting about you and their terrible experiences with you on my twitter posts as I felt that it was both unfair to you as a person, and unfair to tie your product to this Open Source project regardless if it was positive or negative. I made many shows of good faith toward you during this time. The regular slander back from you proved my good faith gestures were a waste of time and effort. December 29th, 2023, after hearing from GrimDoomer and xbox7887 how gaasedelen engineered HDD VSC unlocks for stock xbox HDDs on an Xbox, and how he gave the code to you many months earlier, you finally released it. https://make*m*hz.com/blogs/news/project-ste**ar-firmware-update-1-4-0 Unfortunately as usual you were deceitful in your marketing. You tried to make it seem the only way to unlock a hard drive with an unknown key was buying your modchip. You also claimed "This is what preservation looks like with Project Ste**ar!" Of course the timing here is suspicous, but that's not the greater issue. This is the one and only time you have mentioned preservation publicly. You used something very important to the future of the Xbox community (especially Insignia), something I happen to be knowledgeable about, as a marketing gimmick. You tried to deceive the community into buying more of your modchips in the process, all falsely in name of preservation. I literally congratulated you on the achievement, and informed owners of your modchip that it was something they could do. It is extremely fortunate the small group of dedicated people we had already unlocking hard ohphaned drives caught other people, not customers of yours before they could scrap their hard drives because they did not want to spend that amount of money for preservation efforts. Who knows how many we missed. You also show off an impressive stack of Xbox hard drives at this time. Nobody has seen you undertake any archiving or prevervation efforts to share the contents or images from your drives publicly or privately. You used something important to the future of the Xbox community as a marketing gimmick. Lets skip forward to April and May 2024 now. You made several accusations about Op_enX_HD (aka OX HD) that you had literally no evidence, proof or even rumours to support. You just made blanket statements to try to smear and discredit the project. Op_enX_HD had no association with Cerbios, EqUiNoX, TeamFoxbox (foxbat?), Phantom as you claim. I did copy one feature for Op_enX_HD from a picture FoxBat posted which can still be seen on their github. Offset resistor arrays. Ryzee119 noticed the same picture and I was able to show him that's where I took the idea from. FoxBat borrowed/stole/copied some of my work from images and part numbers I shared in the Op_enX_HD development channel on the Xbox-Scene discord. They also used Ryzee119's schematic and your microcontroller choice. If your claim of collaboration is based on them taking my ideas, then you are just as much of a collaborator with them on their project. There was no "collaboration" as you claim. Multiple of your paying customers told you that you were wrong. You continued with the lies. The only remotely possible claim you can make to me collaborating with anyone is with Ryzee119. I did not talk about "working with others on this." Another lie. I expressed hope the firmware efforts would be a community effort in the future. Of course you attempt to misguide people into believing I said something else I did not. What team? I was the team, I had hundreds of good and bad ideas from dozens of people, and a lot of helpful advice from Ryzee119. What history of theft? Is this like when you sold a debug unit on Assemblers games, then never shipped it? I am not like you. Please explain to me exactly how Op_enX_HD was or is supposed to your firmware on completely different microcontrollers than yours. The original one Ryzee119 chose lacked a 2nd i2c interface to communicate with the Xbox. This is something you either knew, or could have very easily checked before making your baseless and malicious claims. Shorly after your deceitful and defamatory comments on May 2nd 2024, Ryzee119; someone you collaborate with, someone I know considers you a friend very specifically sent this to you on your discord server: Even if you try to excuse away your previous comments with more lies, this comment clear as day, tells you that the hardware work I was doing was not cloning your product. Later that same day I made the last good faith effort to reach out to you directly on the Insignia and VGPC discord servers, knowing full well you would ignore it, or pretend you did not see either message. I made an honest effort to reach out, clear the air, to show you I was not copying your work and intended to keep the project clean. After the message from Ryzee119 and this one you have absolutely no excuse to ever claim that my work continuing Ryzee119's project is a copy of your work, "tainted" or dirty in any way. Yet you continue to talk slander/libel the project and myself when in fact you simply did not know what was going on with the project. I went radio silent on Twitter about the project as I wanted to avoid any more drama from you. You still found a way to lie about myself and the project though. September 12th, 2024, XboxDev discord: Team Resurgent was not leading or contributing to the project. The only contribution anyone from Team Resurgent has given to the project is EqUiNoX designing a 3D model of a spacer and back cover. This occured around April 25 2025, you may notice that is over 5 months after your slander here. You would not have seen an update on the project being on hold due to technical difficulties since that simply did not exist, ever. A complete fabrication from you to once again discredit the project. Refer to my opening comments, you are a liar, you can not communicate with the community without lying. EqUiNoX responded to you on this and you did not respond. You were again informed that you had lied about the project, is anyone else seeing a pattern here? There are a few more scattered comments here and there, but let's get to the meat of it. The elephant in the room, your complete fabrication of events and alternate reality hit piece blog post: https://love*mhz.com/blog/xbox-scene-theft/ I responded to this false claim here: https://www.xbox-scene.info/forums/topic/981-truth-in-the-xbox-scene-a-united-community-response Since I know you either did not read it, or are pretending my response didn't exist, I will repeat it. "I am Harcroft. To be absolutely clear, I am not Cerbios, I am not Nemesis, I am not Foxbat, and I am not a member of Team Resurgent and am not affiliated with the development of any of their projects." You cherry picked an old screenshot from a mistake on a readme from a github repo to support your point here. This mis-credit was a mistake by Haguero/HoRnEyDvL when I was a smartass to him about not crediting me with running a bios he asked me to test. This mistake was corrected in this update, an update from August 24, 2024, ten months before your lie filled blog post. https://github.com/Team-Resurgent/CerbiosTool/commit/b687cf4e711759deaaab131f42fd294118269e09 You had to go back almost a year to try to find evidence to support your deceit. You chose to ignore reality, to push your lies again. Onto your doctoring of screenshots to again support your malicious and deceit filled blog post. This is a screenshot you included on your post. This is the rest of the conversation you chose to omit, to support your lies. I specifically say I'm not going to buy your modchip or undertake any reverse engineering efforts on it. I suggested founchki, a user with limited technical knowledge, but big ambitions about things he does not understand, go on an impossible fetch quest. Founchki directly states that he is unable to do any of the things he suggests. I later removed founchki from that discord server partially due to the constant suggesstions he made about hardware and software he did not understand. In your blog post you seem to blame me for founchki knowing something about an XBE in your modchip firmware. Once again, more comments meant to mislead the community. You also cropped out something absolutely critical: Skye talking about finding VSCs in C code, which we did with the Open Source HDD Super Tool/Clone. Again you doctored this image to lie to anyone who would read your libel piece. Skye also documented where she found more VSCs that she shared with Eaton in her response. Her response completely debunks your fraudulent claim that Eaton and/or Skye stole anything from you. In your blog post you also shared screenshots of random reddit users not affiliated with myself, Team Resurgent, or Op_enX_HD suggesting people not buy your product. You then once again mislead your audience saying: "Stop promoting the idea that an open-source HDMI mod like OX_HD is going to exist." and "Claiming OX_HD will be open source is dishonest when it depends on CERBIOS to function and is being developed alongside the same people who have cloned our work before. Public reverse engineering of Xbo_xHD+ continues to guide its development." The pattern repeats itself. You made misleading, false and malicious claims that have no basis in reality, claims you know simply are not true. I have not, will not and will never have any of your products in my posession, and believe me people did offer to send them to help with development. I have taken the hard road, designing everything myself and iterating again and again until things work. Op_enX_HD currently, today, using Ryzee119's FW functions on a stock console, or with any other bios. Cerbios is not required. There is no development like you are describing. You fail to show a screenshot, even a doctored on to support the claim that public RE's of your video product is being done publicly. Another series of complete fabrications. No reverse engineering of your products were done at all, let alone publicly. This picture was posted on the Xbox-Scene Op_enX_HD development channel on June 2nd, 2025, almost three weeks before your hit piece: This is a sample of several of the iterations of a 1.0 to 1.4 flex cable for Op_enX_HD This is not cloning, reverse engineering, copying, stealing, borrowing, or taking from your video output device in any way. This is honest, clean development work. If you had seen talk of the project being "on hold for technical difficulties" you must have seen this post too, before your fraud blog. Here's an older message from Ryzee119 that clicked in my brain between P11 and P12. Taking ideas from independent development and putting them into hardware iterations. Real development work. One of the screenshots you included on your blog as a citation while claiming Op_enX_HD would not exist was this: The pattern repeats again, you crop out my response to the user making this comment (with an early development picture from a board I never had produced). I showed the user the current board as of June 18th, 2025. You can even see the top of my message and icon in this crop. You again try to mislead the reader, albiet poorly this time. The board I displayed shows significant changes from the boards posted in the past, signs of independent development that you chose to try to conceal. Frankly I am amazed you chose that reddit post specifically to support your claim with how easy it was to expose your again misleading doctoring of images in an attempt to distort reality. You have absolutely no excuse for this veritable cornucopia of deceit. The only appropriate response from you on this subject is to recant your statements about myself, Op_enX_HD, Skye and Eaton, to apologize for the lies you have spread, for the libel you have commited on your blog, and to take down all parts of the blog post referencing myself, Skye, Eaton, and Op_enX_HD. I am not asking you to do any of this, I know better than to ask, I know you wont. You have fabricated a false reality around yourself where everyone is out to get you, meanwhile you attack and deceive the very community you want to buy products from you. Finally I will end with these points. LMHz has not once shared any actual side by side code for a number of reasons. - Doom created the VSC unlocking tools the modchip in question uses, it's possible LMHz does not even have the source code for that. - Functions that complete the same task compiled from different C code will look extremely similar in assembly. - They refuse to show any C code because they know it will not match the code shown on GitHub, likely proving it is not stolen. If LMHz is willing to blatantly lie about myself and my projects, to doctor screenshots to tell a narrative they know to be false, to mislead their customers with obvious fallacies in their marketing, to make baseless accusations about myself they know to be false so quickly, easily, and often, why would they for a moment be honest in this forum? Why would they come forward in good faith and honest intentions now, after being so willing to lie to anyone who will read their words in the past? Please forgive any typos or grammatical errors, I only have so much time to clean up a mess LMHz created. Apologies for the bad abbreviations and edits for product names and LMHz name, I had no choice if this post was allowed to be submitted at all.

Thank you, OGXAdmin, I’ve been asked to step away from the thread, so I’ll leave it at that. Appreciate your perspective on this.

I don't want this post to come off as argumentative. I just think the reason everyone is so divided over this is because while it might seem clear to you, it isn't clear to anyone else. Are your screenshots to show similarities between right and left? If so where? I don't see it. If I understand this correctly, the issue currently being discussed is that you believe your hdd unlocking code has been used without your permission. (I surmised that mainly from the screenshot above talking about hdd unlocking.) Did you write it from scratch or did Eaton provide anything? What is it based on? You must have been referencing something whether it be a bit of logic or... something. Since this (hard drive unlocking) has all been done for 20 years, nothing is truly new and unique anymore. We're not blazing new frontiers. Your code was based on something, so what was that thing? Is it possible someone else based theirs on the same thing and the end result looked the same? You say it's identical but different and that is very confusing to me. You say the differences actually confirm theft which is also extremely confusing to me. If I were to be trying to achieve the same result, wouldn't I need very similar code structures? In your example you say you added a delay because you observed a problem. (This implies that a common code was used if we assume someone else MUST have encountered the same problem you did.) Is it not possible someone else saw the same problem and came up with the same solution? The compiler would then change them to machine code and they would necessarily be very similar to identical. If all of this were made more clear, I think it would be MUCH easier for people to understand the concerns. If everyone is on the same page, it makes it far easier to put this all to rest.

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.