u/AssociationOk699

Well, based on everything we've seen so far, and from my perspective after following Grimdoomer's posts, I think we already have a few solid facts along with some educated guesses.

For example, in one of his posts he mentioned that the Softmod will no longer be limited by the FATX file system, as it apparently will use exFAT instead, which is far superior in many ways. In fact, I already have a video explaining all of FATX's limitations.

Another interesting detail is that he demonstrated the Softmod running from a 26 TB Seagate hard drive. As we know, a stock Xbox 360 officially supports drives up to 500 GB, while modified consoles typically support up to 2 TB. In some cases, using FATXplorer, users can reach 16 TB, but there are still several limitations. Currently, this is generally restricted to certain Western Digital drives manufactured before 2020. More recent FATXplorer updates have also added support for some SSDs with specific controllers.

However, judging by what Grimdoomer has shown, many of these limitations appear to have been eliminated. He's using a 26 TB Seagate drive, which is not only far larger than what we can currently achieve but is also from a brand that isn't currently supported for these modifications. This strongly suggests that the new Softmod could bring much broader compatibility with hard drives and perhaps even SSDs.

Another important point comes from his latest post, where he mentioned that the release could happen in July. He also revealed that the Softmod will feature automatic updates, which obviously means the console will need to be connected to the internet. In addition, he said that the only remaining feature to implement is the ability to uninstall the Softmod, which is fantastic for anyone who wants to remove it later or recover the console if necessary.

Now, here's my own speculation.

I don't believe this process will directly modify the console's NAND. My guess is that something is injected or loaded during the boot process rather than permanently written to the NAND. The reason I think this is because, so far, everything suggests the project is heavily focused on the storage device and the way the Xbox 360 loads the system, rather than making permanent changes to the console's internal flash memory.

Of course, this is only my theory based on the information available so far. I could be completely wrong, but at the moment it seems like the most logical explanation.

What do you think? Let me know your thoughts in the comments!

I have been developing a tool to analyze Xbox 360 ISO files and extract metadata directly from the game files, especially by reading information from the .XEX.

Initially, the goal was to automatically create a JSON database containing information such as TitleID, MediaID, region, disc number, and other metadata. After having difficulty finding reliable and consistent sources, I decided to build my own solution.

In the latest update, I added more information that can be extracted directly from the ISO/XEX, including:

• TitleID
• MediaID
• Region
• XGD Type
• Disc Number (Disc 1, Disc 2, etc.)
• Publisher
• PublisherID
• GameNumber
• XEXCRC32

These fields are generated directly from the game files, meaning they represent actual data from the specific release being analyzed.

For other information such as:

• Genre
• Release Year
• Developer
• Number of Players
• Kinect Support

I decided not to fill these fields automatically because different databases and websites often contain conflicting or inaccurate information, especially across different regions, editions, and releases.

Instead, the JSON structure already includes these fields as empty placeholders, allowing users to manually complete and enrich the database using their preferred sources or personal knowledge.

The idea is to create a reliable foundation based on data extracted directly from the game itself while allowing the community to contribute and enrich the additional metadata.

I would also like to give special thanks to hadzz46, the developer who continued the development of ABGX360. Some of the advice and explanations he provided were extremely helpful during the development of this project and improved my understanding of several aspects related to Xbox 360 game image identification and verification.

I would be interested to know how others approach this problem. Are there any reliable databases, tools, or methods that you use to accurately identify Xbox 360 games and their metadata?

XboxIsoAnalyser

banco dados json

I've seen a lot of people using different methods to install games on modded Xbox 360 consoles. Some extract ISOs to XEX, others convert them to GOD, and some still do everything manually.

After trying a few ways to automate parts of the process, I became curious:

What's the most annoying part of the workflow for you today?

• Converting games?
• Extracting ISOs?
• Organizing your library?
• FTP transfers?
• Multi-disc games?
• Something else?

What's your current process like, and are there any parts you wish were easier or less time-consuming

Estou desenvolvendo uma ferramenta para analisar ISOs de Xbox 360 e extrair informações como TitleID, MediaID, região, número do disco e outros metadados, gerando automaticamente um banco de dados JSON para uso em projetos. Depois de ter dificuldade para encontrar fontes confiáveis e atualizadas, resolvi criar minha própria solução. Gostaria de saber como outras pessoas abordam esse problema e quais fontes ou métodos utilizam para identificar corretamente os jogos.

Metadados

Banco dados json

Good observation - you're right, this could really confuse. I adjusted it to be faithful to what the script really does 👇

---

These days I had commented here about Aurora's problems, especially when we start messing with the games.

In my case I removed and moved some games and it ended up becoming a mess... Aurora kept showing game cover that didn't even exist anymore, duplicate thing, input that didn't lead to anything, that mess 😅

Then I made a script to clean this.

He basically sweeps Aurora's list and removes only what is really invalid, like:

* game that you have already deleted

* folder that no longer exists

* entry without file to open

* incomplete or lost thing

It doesn't delete anything from the HD, it's just an internal cleaning.

I also took care not to touch important things like emulator, dash, app, things like that.

Here it was solved well after I messed up everything by messing with the games manually 😅

If anyone has been through this and wants to test it or has an idea to improve, send it there 👍

Aurora Dashboard is excellent overall and solves many problems on the Xbox 360, but while developing scripts I ran into some limitations that are starting to have a significant impact.

In the most recent version, from the tests I've done, the **scanpaths work with relative paths**. In practice, this makes it difficult to create more advanced scripts, especially for **optimization and cleanup**.

The problem is that, in some scenarios, operations that should only affect a specific device (such as a single HDD or USB) can end up applying to others as well. Depending on the case, this can generate undesirable effects—especially in automated scripts—and requires much greater care with validations and security.

Another related point is the limitation on **creating database backups while it is in use**. I understand that this may be a system protection measure, but at the same time it prevents the implementation of safer routines, such as automatic backups before changes and restoration in case of error.

For context, I've already developed the **“Aurora Drive Fixer Smart”**, focused on fixing scanpaths and Title Updates after drive cloning, with intelligent duplicate handling. It worked very well, but when trying to evolve to more complete cleanup scripts, these limitations started to become a problem.

This isn't a negative criticism—it's more of a point that could perhaps be improved (such as support for absolute paths or greater control over scanpaths), or even something that someone has already managed to work around.

**Has anyone who develops scripts for Aurora dealt with this or found a better approach?**

I was having this problem on my Xbox 360 RGH/JTAG after changing or cloning a hard drive, and I noticed many other people seem to face the same issue.

Games would disappear from Aurora, turn gray/dark, or Title Updates would stop working and stay stuck at 0%.

Because of that, I created a script called Aurora Drive Fixer Smart to help automate the fix by correcting scanpaths, repairing broken Title Updates, and removing duplicate entries that cause conflicts inside Aurora’s database.

The idea was inspired by EmiMods’ FixClonedDrive, but with a more focused approach on safer and smarter handling of duplicates and database fixes.

I’d like to know if anyone else has experienced this issue and whether this kind of solution would be useful for the community.