CAN YOU SEARCH?

http://www.xboxhacker.org/index.php?topic=13180.0

why do people on here suggest stupid things? refurbs come with the updated CB

you just posted a hex compare of a hex program, and you still having problems figuring out what the difference is between both firmwares?

you could've used the search function but here:

http://forums.xbox-scene.com/index.php?showtopic=698256&st=0

solder only sticks to hot enough parts.. this is very basic soldering knowledge

works fine for me, it does say key @ n/a but does display my key

it's working for their purpose yes

did you load it as target?

no

frankly i don't give a $#!t. because i know the post was made by you

quote from xbox-scene to get your game updates working from usb (i think it was confirmed to be working ok):

How to patch an xex file with an xexp patch file.

Updates to games and system files are provided over xbox live in the form of
patch files. These updates are stored inside package files in the Cache folder
on you hard drive. A system update usually has "SU" as part of the filename,
and a title update (game update) usually has a "TU" as part of the filename.

A patch file will only work when used with an untouched version of the original
xex file it was created for. When you have the original xex file and the patch
file you want to use with it, do the following to create the updated xex:
xextool -p patch.xexp -o output.xex input.xex

Note: A retail xex requires a retail patch file, a devkit xex requires a devkit
patch file. If an xex has been converted from a retail to a devkit xex, you need
to use the retail patch file with the original retail xex, then convert the
resultant xex file into a devkit xex file.


so:

1. Re-extract the corresponding xex file from the Image/Disc (as it needs to be a retail xex). In the case of Modern Warfare 2, it'll be default.xex and default_mp.xex.
2. Extract the xexp files from the Title Update (I used le-Fluffie).
3. copy the xexp files for these into the same folder as xex tool.
4. Run the following commands:

xextool -p default.xexp -o default.xex.patched default.xex

do the same with the default_mp.xex:

xextool -p default_mp.xexp -o default_mp.xex.patched default_mp.xex

5. Save your original xex / xexp files elsewhere and remove the .patched extensions from the two created files.
6. Run X360GameHack and point it to this folder. It should report that 2 files have been patched.
7. Copy back to your game folder and (according to the document) it should work.

I've not tried this but this is what I'll be trying very shortly.

arakon had a visit from the future christmas spirit 

LOL nice.. that'll properly cool =)

i used to have a picture of a 360 with like 10 Nyko Intercoolers.. looked pretty fun too ^^

gotta be kidding me lol.
creating partitions manually sucks.. not to mention:

finally.... no more activate disc..

thanks and cheers

what I'd suggest is to get a via pci card... and use the brute mtk intro trick (10 seconds trick), where you powercycle the drive to force an intro. or whatever you wanna call it

works wonders on intro-ing mtk flashes, should help you get correct status

VIA or Nforce chipset, if so, tried to powercycle on the intro yet?

get a jtag Xbox 360 with XBReboot of Freeboot ... and you can run any software you made

except you'll be missing out on all the debug features that the XDK Xbox 360 has to offer

wish i could make something.. something useful

I wish they would've destroyed your homebrew capabilities while they banned you..

stupid little kids

why else would these firmware be released lol

just patch the traces after you have a valid dump, and you can erase/write the liteon anytime you like

dump the firmware more then one time? i just make 2-3 dumps on 9xxx.. compare keys..

if JF opens the firmware it's reasonably safe to assume you have a valid dump.. in advanced view you can check the inquiry/drive serial in hex data