Modern Warfare 2 and freeBOOT 0.01? (aka virtual 8498)

[AHippyHop]

Hello,

Can Modern Warfare 2 be run successfully under freeBOOT 0.01?

I have tried within the freeBOOT virtual 8498 nxe, and MW2 still
wants to apply an update (don't worry I said no). I know the difference.

Do I have to remaster to Wave 3 or remove the systemupdate file? I do not
want to actually update to a real 8498, as it will try to blow real fuses in the Xbox
NAND as opposed to my secondary NAND. My r6t3 is removed.

Any insights welcome

AHippyHop

[keine]

I would also be very interested in the answer to this question.

[iLLNESS]

doesnt modern warfare2 update to 8955?
that could be your problem.

[B1N4RY]

no it doesn't, MW 2 updates to 8459

[cmonkey]

I can't answer as to whether it will run or not as I haven't gotten round to installing my Cygnos yet but I can definitely tell you that if your R6T3 is removed you will NOT blow any real fuses at all (by the way, the fuses are in the CPU, not the nand).  The worse that will happen is that you'll have to reflash your Cygnos nand again with the 8498 image you built with ibuild, if the update messes it up (which I highly doubt it will).  Go ahead and do the update, safe in the knowledge that you will definintely NOT blow any fuses in the CPU as long as your R6T3 is removed.

[cory1492]

I have tried within the freeBOOT virtual 8498 nxe, and MW2 still wants to apply an update (don't worry I said no). I know the difference.

If you knew the difference you would dump the disk and manually check the $SystemUpdate file yourself to confirm the update version on the disk is 8498 or lower.

Run the update, you'll need around 128M free on your memory unit (it needs the avatar crap, probably for leaderboards or something equally odd) and will likely have to manually power off when update tries to reset the console. See cmonkey's note on R6T3, if you don't have it removed - do so before proceeding.

[Jack83]

You can run this update without problem.
After the update is completed, you have to restart you xbox manually. The kernel stays on 8498

[viericrespo]

Well,

Here it is what I did for not messing up with the update:

Open MW2 iso with a HexEditor and search for the string: $SystemUpdate. Then replace $ character by another one (S for example), and save the changes.

Burn the game normally and when you try to play it, you'll see that the update function won't annoy you anymore.

Regards 

[B1N4RY]

I've tried that before, expect that I got a error saying that "A required update is not found on the disk"

[viericrespo]

I've tried that before, expect that I got a error saying that "A required update is not found on the disk"

I only got that error when trying to do the same on a 7371 Kernel. On 8498 works flawlessly 

[AHippyHop]

Hello All,

Sorry slow to reply. Different time zone.

Interesting opinions. Thanks for the info.

I've tried that before, expect that I got a error saying that "A required update is not found on the disk"
I only got that error when trying to do the same on a 7371 Kernel. On 8498 works flawlessly  Wink

In addition, to what I said above (thread top), MW2 asks to install update twice. You say no to the first one, and it asks again.

Is this a showstopper to editing with a HexEditor, or is the update a 'two-parter'?

Also, I thought that all updates detect for a missing R6T3, and if they find it missing give you E79! Which means
the update could never execute in reality. Or are we talking virtual fuses here, in which case, it can execute?

AHippyHop

[nilezon]

Can Modern Warfare 2 be run successfully under freeBOOT 0.01?

I have tried within the freeBOOT virtual 8498 nxe, and MW2 still
wants to apply an update (don't worry I said no). I know the difference.

I have a Falcon board with Cygnos360 v2 and freeBoot v0.01 (dashboard 8498).

When I tried to play MW2 without my HDD present it worked fine, with no update required message.
Then I inserted my 60gb HDD (never used with freeBoot/8498 before) and MW2 stated that an update was required. I applied the update (IMPORTANT: R6T3 is removed!) and got RROD. Restared the Xbox and was still on 8498 (of course) and MW2 now works fine. No more update required messages.

I guess the HDD had some information regarding my dashboard version. Seems strange, but I don't know how else to explain it.

[AHippyHop]

Hi nilezon

Yes, just confirmed it! Remove the hard disk, and the SystemUpdate on MW2 goes away.

Good find. It must be something to do with Avatars perhaps, or other NXE stuff.

Thanks.

AHippyHop

[nilezon]

Does this mean that the HDD is "dirty" after this unsuccessful update, and will give you away as a hacker when you connect to XBL?
I'm using the dirty NAND trick with my Cygnos, but I am afraid that the HDD will somehow contain information that can get me banned.

[lenselijer]

i think the harddisk always stores the latest system update in a partition.
i read this somewhere on this forum, too bad the search function is not working for me.

[ddxcb]

System update on partion 3 or on MU 1, with a folder called SYSTEMUPDATE hope that helps.

[domina]

i also have a xbox with freeboot and desoldered r6t3. launch mw2 with freeboot and game wants to update if hdd was insert. i applied the update, xbox crashed, turn it on again and then it never asks again for update, jtag still works fine.

the hdd still works with 7131 after update.

so no problem at all.

[AHippyHop]

Thanks domina, ddxcb, lenselijer, nilezon et al.

Makes sense now. Does this mean that for people who wish to go back on-line that it is best to wipe both HDD and MU before you
reconnect? This follows on from nilezon's comment about a 'dirty' HDD or MU.
Seems to me that remenants are potentially lethal for the on-line people i.e. banning. Have never used LIVE/online myself.

HippyHop

[nilezon]

Is it possible for us Cygnos users to go online anyway? Doesn't XBL require the latest dashboard (8507), or is it possible to download game content (Guitar Hero songs, etc) with an older dashboard?

[AHippyHop]

Probably not doable. I was reading in other threads that XBL updates are mandatory i.e. forced upon you.
So you are probably right. Never been online myself. My point was about future disk updates. Some people
here are suggesting that the update scans the HDD and MU for bad update history.
Perhaps they are right!