XeDK Boot Path I have succesfully mapped out the boot path's and modified the dashboard.xbx to reflect the HDD as the defualt boot path. Inject this into your nand http://rapidshare.com/files/372894106/dashboard.xbx.html And then place a folder in your DEVKIT drive and name it "Boot" Now anything you place in boot must be named default.xex and once turned on the xbox 360 will auto boot this. I have booted the following: XeXMenu 1888 Kernel And all loads up as it should, now the dashboard.xbx is not needed for the development kit to behave correctly so if you corrupt it no worries just re-run the recovery. If it becomes corrupted or missing it will just boot you to dash.xex and if you mess up in the boot folder you can just detatch your hdd and it will boot dash.xex So pretty much I found an alternative for Development kit's as opposed to the JTAG kernel patching. Hope this helps with research.
Ok I deleted the first thread because is got way out of hand,lets just keep everything nice and civil guys.
While it is a nice reminder for those new to the Xbox, this isn't really anything new (and it certainly isn't anywhere near analgous to patching the kernel). This is the same dashboard.xbx that was discussed in detail when the first 360 dev kits leaked out back in 2005 and prior to that on the original Xbox. This is not a "hack" or an "exploit", but rather a well documented and totally standard function of the kits. In short, thisis how it is supposed to work. Rather than have people run around downloading files and not knowing why they do what they do, I figure it's much better to highlight what's going on so others can make the edits for themselves. And since this is old news, there's no harm done in detailing the info again. For the uninitiated, dashboard.xbx is nothing more than a settings file that sets a path to the default executable. It's not an executable itself, it's not encrypted and it has zero security. It is simply a config file, akin to any number of INI files in Windows. If you want to edit your system to do what lllsondowlll is talking about all you need to do is open your current dashboard.xbx file, delete the existing line and replace it with the following: You are also free to change the path and executable file to pretty much anything you want. -hl718
Hl718 when I edited it in a text editor it wouldn't boot, also the struct to the hdd hasn't been discussed and cmd360 will not redirect you will also need to edit your xbdm.ini in your recovery or use an alternate method to inject into your flash. Also no that is not how the xbx is suppose to work, its directed at flash files and only allows to be changed with cmd360 which gives an illegal output if you change the path you must edit the file with the correct path which cannot be pulled out of devkit information I used xorlosers TheLoader files to match the path of the drive map. Also can you provide sources of the location where this was talked about for the Xbox 360 development kit detailing the drive paths?
So now you're taking a private app, reversing it, and viewing how it accomplishes things? Very classy. Also, this is a fresh dashboard.xbx directly off of my Xbox. This is ALL it contains: There is no required mapping, at all. It doesn't take someone with brains to go in to XeXMenu, and see what their hard drive is named locally, then put the pieces together that forms the file path. It's nice that you decided to write all of this up for the people that DIDN'T know, but you're taking far too much credit than what's deserved (if any), plus I bet only about 5% of the people on this site with kits have read/write access to their flash anyway.
I just said I modified the xbx and gave partial credit to TheLoader and I gave out nothing of the private app. And no the path isn't in xexmenu or freestyle first thing I checked and it doesn't give the path. People are misinterperting my statement. I simply said I modified the xbx I never said it was a great accomplishment Im simply sharing the info.
You said: I never said that you gave anyone anything, I said: Looks like you're the one misinterpreting things... And sorry to Pikkon since I will admit these posts aren't exactly civil, but I wanted to prove a point. Oh, and about the path not being in freestyle/XeXMenu, that's another misinterpretation of yours, as I said that you can see what the hard drive is named locally, I did not say you can find the entire path in XeXMenu
Ya know what I'm high as hell and I'm about to burn this motherfucker down. This is what I get for being nice. Two options 1. Use it 2. Don't Either way I don't want to hear about it anymore, for the love of christ.
A few things: 1) I don't think "struct" means what you seem to think it means as you appear to be using it as the equivalent to path. It's not. 2) Dashboard.xbx is just a config file. You can point it to any device on the system. 3) The device paths used by the Xbox 360 are of the same type as those used by the Xbox as well as those used by current versions of Windows. While the overall systems are quite different the underlying core kernel components do have many similarities. \Device\Harddisk#\Partition# is a standard layout for accessing devices directly on a low level. 4) Device paths for the Xbox 360 specifically have been discussed on Xbox Hacker (among other places) many times over the past five years. I know you haven't been a member there that long, but I would suggest searching through the archives of the "necro threads" as you call them. You should turn up references from as recently as last year. The availability of JTAG systems refreshed the interest in programming a bit. 5) There's also the thread from Feb of this year which was talking about launching 1888 from the hard drive and in which 4cc3ss posted the exact path that you are using in your edited dashboard.xbx file. He even mentioned in the post that it was pulled from xam.xex from an xedk NAND. Yes, the exact same thread where you were warned against requesting copyrighted files since you were asking publically for someone to give you a copy of 1888. http://www.xboxhacker.org/index.php?topic=14396.0 Dumping xam.xex is how all the device paths were originally confirmed on the Xbox 360. People were up and running before that since the paths were more or less the same as the previous system, but once xam.xex was pulled out a NAND everything was confirmed. But I'm sure you already knew all of this since you "have things that will make your head spin and endanger everything," right? -hl718
See this is exactly where the 360 scene fails horribly right here. Here is the misinterpertation. I used terms exactly how they should be used struct means structure standing for file structure which cannot be found in neighborhood or any other file system except xam. I simply stated 100% fact you tear the post down for what exactly? Because you think I made it sound harder then it really is? I never claimed it to be anymore then I presented it to be and everything I presented was 100% fact. This was never meant for you ambiant or gamerfreak this was meant for people who don't work on stuff like this. When I asked you to changing the boot path you provided me with a link to loading 1888.xex with the file structure already found. Thats fine but this hasn't been discussed before and I am simply sharing. See what you guys don't understand is I'm not making it more then it really is you guys are. I presented and you guys tear it down like I said. 1. Use it 2. Don't You guys make up these scenerios in your head that I make it sound harder then it really is when I simply stated what I did. I didn't do this for credibility I did this for the everyday user and since no one has on record publiclly done this with an xbox 360 I had every reason to share it with people who don't know how to do things like this. Now you stated your opinions so please leave it be.
Struct has a very specific meaning when it comes to programming. Implementation differs slightly between languages, but in general the concept is the same. http://en.wikipedia.org/wiki/Struct_(C_programming_language) When you start talking about accessing devices programmatically and tossing around coding terms such as "struct" people are going to assume that you know what you're talking about. Especially since you've told the forum (more than once) about all these secret "badass" projects that you've worked on. Honestly, it's not the sharing of information that anyone has a problem with. There is nothing wrong with republishing old info if you want to do it just to get it back out there and help make sure it's all newbie friendly. The issue arises when you make claims of "discovery" and then equate it to kernel patching on JTAG kits. That is a huge overstatement of what is actually being done. Then you made the claim that no one had ever shared the device paths and you discovered them yourself. That got modified to you taking them from xorloser's The Loader. When it was pointed out that the device paths had been talked about publically you insisted it had never been done. Yet the very path you used was lifted from a thread on Xbox Hacker that you had obviously read last month. So you can't even claim that you missed it in search. I provided that link because you argued previously that no one had revealed the device paths in the 360. The link provided is but one which shows the path you used. There are plenty more which list out all of the device paths on the site. If you want to see more dashboard.xbx discussion, read some more on Xbox Hacker. I'm more than happy to help with specific questions, but I'm not going to do all your searching for you. People in general are very helpful to those that simply ask when needed. It's when misrepresentation and ego creep in that others will chime in with all the details. You'll note that in my first response all I did was detail out exactly what you were doing. You were the one that made the claim that this had never been discussed before and asked for sources. I simply provided what you requested. I did not "tear you down." -hl718
Sorry, but no. All hl718 explained was that you could edit with any text editor, which makes it no where as complicated as you are trying to make this seem to be. We aren't making up "these scenerios[sic] in our head", it's just easier to tell someone how to do it, so they can get the full picture of what is being done. From my experience, doing this means there are fewer questions about the process of the modification. Also, as has been said before, this has been done numerous times in the past, and publicly too.
This is why 360 community has such a bad rep, it's not about finding stuff it's purely about bragging rights. Someone mentions something, people want to get all angry because they are so awesome and they knew about this ages ago etc.. I've never seen so much childish envy in one spot.
:shrug:but how to change the dashboard.xbx with what app you made the change? a little tutorial would be welcome
I prefer UltraEdit. But you can use any other editors. For copy the dashboard.xbx use some puplic app like FreestyleDash. It has nand access. Or, if you have sdk installed, use the xbox360 command prompt with ->xboxsetcfg
I forgot to tell you that I not access the console, I would like to change these files in a dump of nand
