Hi, How to update a dev with a new system update (dash) on iso image/disk? I can't figure out how to do it. When I try to launch the game (Prototype) it states that I need to go to xbox support for an upate. I have 7978 running (NXE). What do I need to do?
Please don't try to update a debug with a system update from a retail disc. Really. DON'T do it. In the words of Egon, "It would be bad." -hl718
Really now, that is some bad advice considering the most it would do is make your executable not launch. Also downloading a title update through partnernet, for a game made for Xbox Live(retail build) wouldn't work. Also the update you're thinking of is entirely different.. He's not patching his kernel.. Nor is it asking him to download an update from what I gather.. but the game was made on a higher kernel version, and he therefore would need to upgrade to something such as 8276. Also bob, you can apply retail updates to an XEX if you know what you are doing, but the process would take place on your computer, and you'd need extensive knowledge of both xexp and xex formats.
This is my understanding of his description of events. 1) He downloaded an ISO of Prototype. 2) He converted the main XEX and tried to boot it on the debug. 3) The game realized the kernel was too low and tossed a generic "You need to update your system" error. This wouldn't have been a title update. 4) Normally the game would just pull the kernel system update from the disc, but that won't work by default here partially because the system update files aren't properly signed and partially because whoever ripped it likely didn't get the whole thing, 5) A debug unit isn't going to pull a system update off PartnerNet like a retail unit will from Live, so he can't do that either. At this point, I got the impression the OP was thinking "Hey, there's this System Update folder, how about I try to convert that and use it to update the kernel on my system?" Unless I'm entirely mistaken about how the flash is setup, forcing in an incorrectly signed file will cause the system to fail on the next boot. From there, if you're lucky you can restore from a recovery disc and if you're unlucky you're sending your system into MS for service. If he's just working with the game files, he's safe. If he starts mucking with a kernel flash, he can damage the system.
That's horribly incorrect.. It wouldn't load the system boot file at all. RSA keys for Live, PIRS, and CON containers are different between retail and development consoles.. The container would not verify the RSA(first thing it does before it loads anything really), and would skip any operations using said container. And I hope you are aware that if a console screwed up to patch certain executables in the flash, your Xbox would turn on to a black screen, not even a logo, and not read any recovery discs, if the boot sequence executables were still fine however, it would show some boot screen, and probably give you a Failed to Load Executable error of some sort, whether it be because of xam or etc. Regardless, your logic is flawed, and I'm not trying to be a douche, but if you really don't know what you're talking about, don't spread false information, causing others to believe the wrong idea. ~Xenon.
Sure.. but what I don't understand is why this user keeps creating new topics for a question, instead of asking in the prior topic he made.. If I remember, he addressed about this before, they he shouldn't do that, but evidently the message wasn't clear enough. You already asked this same question in your other thread, was it really necessary for you to go out of your way to post there, then decide to write up an entirely new thread for that same question you already asked in the previous thread? Seems redundant, and retarded.
Yes, it's a given that a debug system is going to ignore a container from a retail disc (or one that was downloaded from Live on a retail unit and then transferred over). However, considering that "off-the-shelf" homebrew tools have no problem extracting the contents of said update, I don't see how that's really a safety net for a new user. I could very easily see someone who knows a little about the system they just bought thinking "hey, I don't have the official update disc, but I know how to resign games with the patcher, why don't I unpack the system update, resign it and use that?" This depends on what specific part of the flash is corrupted. Remember, you can load the flash as a filesystem, you don't have to update the entire thing at once. If you're booting to xshell and end up corrupting the dash, you'll still boot the system. Even in that case however, someone without access to a recovery disc would be screwed. Like everyone else here I'm simply sharing what I've learned. Remember, I've only been discussing system updates here since that is what the OP asked about, not title updates (which you also mentioned in your posts). If you think a particular aspect of what I've posted is incorrect, please feel free to point it out and highlight the error. I've no problem being corrected on an issue if I am wrong, so long as you can explain why I'm wrong. I promise not to take offense. -hl718
Hmm? I'm aware of all you said in your last post. That all makes sense. I was just debating the fact that a retail system update being put on a developers kit wouldn't load stock. You then later indicated you meant if extracted, resigned, and repackaged, you were vague to mention that at first, so I said it just wouldn't boot, now that you mention it, I have nothing to say. If I missed something in this topic here with this last post, my apologies, it's late and I don't intend on rereading this entire topic to see all that was said, hehe. ;P
