Xbox 360 Hacks - News, Hacks, Cracks, Mods.

TingedAce released a new version of XNand Healer GUI – a GUI app to help you dump and manage NAND files, remap bad blocks and also uncripple your Xbox 360. Requires Nandpro 2.0 (b/d or e) and FindSecData 0.62

What’s new/fixed:
* Now able to browse to and select any file for Image Analysis or Remapping
* Option to Dump KV and config files either as part of the initial dump or afterwards
* Added 2 second delay between reads (for multiple reads)
* Fixed bug with file locations in the settings where it wouldn’t work with a space in the path

http://www.rigid360.co.uk

Of course they do!

Stephen Toulouse, Director of Policy and Enforcement for Xbox LIVE, posted some tweets about the early online Halo Reach leaks:

I’ve been asked about unauthorized pre-release play on Halo: Reach. Let me address that.

As with all unauthorized play on Xbox LIVE, anyone playing any unauthorized title runs the risk of account permaban and console.
Remember, legit store bought copy runs no risk of ban. Key word: UNAUTHORIZED. We have ways of knowing.

How can they know? Just like they do any other time…

Here’s a video posted on Youtube by SiddGoneWild that shows the old HDDs from the Original Xbox 360 will work just fine on the new Xbox 360 S. You’ll have to strip the HDD from the original HDD-case and slid it into the 360 S HDD-slot. Not ideal, as the Xbox 360 S proprietary slot is much larger than the 2.5″ SATA HDD, but it will fit in (SATA data/power ports match the standard) without needing any 3rd party hardware addons or so. I’d just suggest to add some rubber tabs on the sides or so to prevent the HDD from moving too much.

We are to assume laptop/PC HDDs modded with HDDHackr will work just fine in the Xbox 360 S as well (and save you a small fortune). If anyone tried this already, let us all know!

The company’s engineers created a chip that combined the machine’s microprocessor and its graphics chip on a single piece of silicon.  In the past, different versions of the console have all used two separate chips for those tasks.  The code name for the project was Vejle, named after a city in Denmark  (It’s not Valhalla, as we all thought?).

The new 3.2-gigahertz, three-core microprocessor, and 500-megahertz graphics chip design is on one chip. In order to create this, Microsoft and IBM engineers had to work together to build the necessary connectivity within the chip to route electrical signals in and out of the chip.  IBM had to get rid of its main communications channel between the chips, (FSB), and build a substitute for it.

The GPU side is packaged with a separate 10-megabyte embedded memory chip. So the two chips are packaged in a single module. The combined chip uses 60 percent less power than the original 2005 pair of chips, and it uses 50 percent less space. Robert Drehmel, senior technical engineer at IBM, said that one of the big challenges was to marry two chips that were built by different companies, designed by different engineering teams, and created with different chip design tools. IBM had to learn more about the unfamiliar ATI design, design specific tools to adapt it, and then recreate an overall design that did the same thin.

The new 250GB hard drive for the new “Slim” Xbox 360 S units begun appearing this week in some online retailers. As the tech blog circuit started getting excited over “OMG leak”, Microsoft spoiled their fun by confirming it via Larry ‘Major Nelson’ Hyrb video. The new 250GB hard drive is the biggest Microsoft has offered yet, and will set back Xbox gamers $130.

Continuing in the sad tradition of Halo 2 and 3 before it, Halo: Reach has apparently been leaked. Modders at Game-Tut.com found a way to trick Microsoft’s servers, which are currently hosting the full game download. The download is intended for select media and only accessible with a code — well, until Game-Tut apparently cracked that security measure. The site has yet to openly leak the files to the general public.It appears that the game is leaking other places as well. A Microsoft spokesperson told Joystiq, “We are aware of claims being made regarding a security exploit related to Halo: Reach and are aggressively investigating the matter. We have no further details to share at this time.”

You knew it was bound to happen, sooner rather than later… Team Xecuter, alongside Team Jungle and C4E, have successfully hacked the Xbox 360 S, or Slim, whatever you want to call it. The hack is tried-and-true by way of patching the DVD-ROM firmware (again).

Now this is only the first step. Much work is still needed before a public release happens. We’ll keep you posted.

- source: team-xecuter

After releasing FSD2 Config Editor, Scuba156 now comes with FSD2 Content Editor:

A application to edit FSD 2.0′s fsd2content.xml via a GUI Requires DotNet 4.0

UsageJust copy your fsd2content.xml from /fsd2data/ and load it into the application

http://code.google.com/p/fsd2contenteditor/

Node21 (Team XeDev) now released XM360 v1.8d to the public, a tool running on homebrew 360s that will allow to organize, scan and unlock XBLA and DLC content.

What’s new/fixed (since v1.7):
* Fixed fact that you couldn’t sort by ratings or raters in the collection manager (v1.8)
* Fixed new scraper (1.7b) getting ratings wrong. I made a change to the file format that breaks compatibility with old xbla_titles.csv, so make sure you are not using an old version of the file. (v1.8)
* Fixed initial scan crashing the 360 if there was no existing content.bin file. (v1.8)
* xm360_server is now aware of the last time xbla_titles.csv and dlc_titles.csv were generated. Every 360 that connects to xm360_server will *automatically* update the xbla_titles.csv and dlc_titles.csv on that 360. Furthermore, you can regenerate, or replace those files without stopping xm360_server from running. So, I leave the server running all the time, 24/7. I have scheduled a /X and a /D every night at midnight as well. It’s all invisible without any hands on maintenance. Basically, this feature means you shouldn’t ever have to worry about moving these files to your 360 anymore. On the server, these files should be in the same place as content.bin. (v1.8)
* Also, if you put an xm360.xex in that same directory, xm360 will *also* update itself if the version there is newer than the version that is running. It will automatically restart if this happens. This is a moot feature though, unfortunately. (v1.8)
* A request was made to include the DLC filename for missing DLC in the DLC_report.txt (v1.8b)
* A suggestion from a donater: The first scene now has the ability to seperate GOD from XBLA (use RB to toggle) (v1.8c)
* The server will now wait for you to hit enter after scraping XBLA or DLC (v1.8c)
* The server has a new command line option (/Q) to tell it *not* to wait for enter after scraping. Use this if you automatically scrape every night via a scheduled task, or something like that. (v1.8c)
* After “ATHiEST” leaked version 1.7b, I stopped work on xm360, except to support people who had donated. I’m releasing 1.8d to get everyone out there caught up to what has changed since then. Any future work on XM360 will once again go to people who donated first. (v1.8d)
* Due to a request, after unlocking XBLA, you no longer have to do a full re-scan for content (v1.8d)
* FTP is much faster thanks to the FSD team teaching me to assign threads to a CPU, go DONATE TO FSD PLEASE! (v1.8d)
* Because xm360_server became the only way to update the database, and it doesn’t work on linux. I’ve gone back to including the perl scrapers (but they are still not as good as xm360_server) (v1.8d)

http://xedev.xbins.org/

[c0z] released an update for Dash Launch v1.0 for jasper BB 256/512mb users so they can now safely use their internal memory:

Changes from dash launch 1.0 patch set:
-Jasper big block machines need only apply
- fixes flash MU corruption issues

*note that flash mu is contained in:
blocks 0×10 thru the end of block 0x15B
blocks 0×200 to end of NAND

in small block notation (for nandpro) this is:
blocks 0×80 thru the end of block 0xAD8
blocks 0×1000 to end of NAND