Xbox 360 ISO/Remote Recoveries & SDKs

I really hate to see all of the secrecy in this community. There is no reason that these files should have stayed so private for so long: they are really not that complex. In fact, most of the code you would need to recreate one was publicly released in 2009 as part of the Free60 project, here.

if you are interested in the technical and development side of the 360 I've made a wiki at https://free60.acabey.xyz/ . I'm doing research on shadowboot images, you can here and some image samples here. Included with that is a shadowboot ROM made some time ago by a knowledgeable scene member that will enable retail disk authentication and retail XEX verification.

Remember that the people who did the heavy lifting to break the 360's security were not the ones hoarding information from competitors and selling cheats to online games, it was the free software community who very openly shared and collaborated on their work and research. This community owes a lot to tmbinc, arnezami, Gligli, Robinsod, Takires, SeventhSon, TheSpecialist, Redline99 and many other Free60 contributors who would feel ashamed to see what it has become.

If you have any issues, want to help out or just want to learn more about the technical side of things, I'd be happy to help.

Side note: RGLoader is a very impressive project -- if what you want to do is make your XDK a hybrid retail and dev console, the cleanest way to do it (IMO) is to run a custom RGloader image on it.

I'm not sure what is meant by "RGLoader shadowboot." By default RGl disables shadowbooting. Maybe you just mean it is a patch file used by RGL's dynamic patching system? That is not a shadowboot at all

If someone could provide me a sample I'd like to analyze it, but I'm pretty sure it's just an rglp file.

 

An update on the RGloader shadowboot that was posted earlier.

It is a real shadowboot ROM in the technical sense, but very similar to Xell shadowboot from Free60 in that it is almost entirely crafted. What some don't realize about shadowbooting is that it effectively allows you to run a second NAND flash, one that was loaded on boot from your hard disk, without ever modifying the actual onboard flash chip. As far as I can tell, that ROM is an entire build (albeit with a few custom options disabling JTAG/RGH specific payloads) of RGloader that was crafted into a shadowboot ROM -- that means it (probably) carries RGloader's dynamic patching and plugin loading systems. Because RGloader was designed with 16MB flashes in mind, the creators also built in a system to load the XDK's larger flash filesystem from disk instead -- whoever made this ROM did not remove that feature/workaround, meaning that it assumes you are on a 16MB flash and will try to load the flash filesystem from the root of your disk. There might be size restrictions to shadowboot ROMs that I am not aware of that forced them to do this.

Funny enough, that ROM is accomplishing exactly what I said in my last post in a pretty clean way (in that you don't have to risk writing your NAND), it will use RGloader to turn your XDK into a hybrid retail / dev at boot time.

 

@acabey Wow, intresting maybe they can be combined with http://xboxdevwiki.net/Main_Page one day.
ontopic, items cannot be shared like Borman said if "retail Xbox Live is at risk". so if the tools or methods do so... it cannot be released from this website. I cant seem to find the exact rule but some here https://assemblergames.com/threads/rules-and-guidelines-for-sharing-files-as-of-june-2016.58502/ do reflect that piracy of active consoles is not allowed. Xbox live is kinda still alive too, so files that help hack it or pirate it...

But I gues its fine to talk about how stuff works, and if you keep the links click far away

 

Seconding reference to the rules.

I would like to mention that there is XBL source that's been passed around since 2012, so if people just shared it without a second thought it would most certainly be the end of someone's presence online or a site in full depending on the circumstances.

Some things are not meant to be shared on *this* site. The same holds true elsewhere, but may vary in results.

 

As far as I have seen, there are no "magic sauce" shadowboot files that could pose a danger to Xbox live, at least directly. Though, the live service people (Ninja and the like) are behind a lot of the secret-keeping and a lot of information / files will probably come down the line from them.

 

Don't know if I can drop this link but if its not ok just remove it thanks!
http://www.mediafire.com/file/6kw4f0c990r9rky/my_17511_spoof_xdk.rar

 

It is a slightly different version of the same RGloader shadowboot posted (and subsequently removed) earlier. This has some changes specifically for going on Xbox live... mods can do as they please with it.

 

yes they will allow you to go online but there is some other stuff required to do so.

 

The 21256.12 or 21256.18 SDKs would be greatly appreciated. I will also publish some of my developments regarding shadowbooting soon

 

I doubt microsoft cares about 360 anymore. Who knows.
They probably shut down all the dev live enviroments anyway. If not, keep in mind PNET is whitelisted and who knows what happened to the others. If all the dev live enviroments did shut down, rgloader on an xdk isn't such a bad thing.
Connecting to ProdNet with an XDK running rgloader is the same as using NiNJA to get online with a hacked retail. Both concepts achieve the goal of playing with mods on Xbox Live.
However i've been told by good bloke that xdk's have capabilities that the public shouldn't be exposed to, and that's probably the reason this was all kept secret.

Side note: RGLoader is not mine or yours to release. It's ED9's (tyedye81) project and we should respect that. He's a good man, give credit to the creator, don't be a Domo.

 

I have the .17 SDK from before it's removal. I could re upload it if you so desire. Also, @Falcon, what are those "capabilities the public shouldn't be exposed to"

 

I also have the .17 sdk if u need me to upload it. RGLoader may be tyedye81's but its was always open for public use until Jester got in his ear and greed took over...Yes he is a smart man but with that being said he also has said many times that one could update it and even gave a run down on how to do so. I don't use rgloader to build a nand image either this is a shadowboot file that I use with rghloader patching and such its a hybrid build.

 

I have .17, I'm just trying to match up my flash and SDK versions to make kernel debugging easier. If no one has either of those I can make do just messing around with symbol files until it works

 

Who are you replying to? XDKs really don't have anything that cannot be done on retails anymore. RGl can emulate shadow booting with its dynamic patch system and it enables real time kernel debugging. The only special thing XDKs have is 1GB of RAM...

The issue I have with people posting these ROMs is that they are assembled binaries. Tydye and stoker made a point of releasing the assembly behind their patches so you could see what's going on. I'm a pretty firm believer in not having any information be private, but the problem with this XBLS stuff is that they give no information, they are only for cheating online.

 

I don't really care to cheat online but I do like to play online with my games and they are not all purchased but that's my main reason for using it...I don't own a RGH or Jtag console as of now and was playing the xbox one I just got tired of it and broke out the XDK to play a bit and needed a way to get online to do so.

 

Nothing against you personally, but buying a retail would be cheaper than your XBLS subscription

 

I have my own personal server with xdk support.

 

How do you make an XBL server with XDK Support, @im twizt3d 24 7 ?

 

use code to patch the hv on the Fly console side in the servers .xex and then XDK XamPatchdata instead of retail XamPatchData.

 

So, basically, patch the HV on the console side then XDK XamPatchData?