Print

[kero]

This is awesome news

[dark04templar]

wow, nice i cant wait to try it!!, this gonna save me to much time!!

[HomerSimpson79]

doesn't work for me  

i flashed it to an m25. Now it cant read anything. If i put in a original disk an white screen comes up: "Put this game in a xbox 360 console" or something like that.

HOMER

[x 360 x]

did you patch the firmware with your drive key?should work.

[HomerSimpson79]

yes i did it.
BUT:
The first time i use KDX1.5 to patch it. This doesnt work!
I tried a second xbox360 (also with m25) and patched the firm manually with a hex editor. SUCCESS!
Conclusion (for me): DONT USE KDX!

Now i will try to fix the first xbox360....


HOMER

[scrano]

What was it that Neil Armstrong said:

"One small step for man, One giant leap for mankind".
Just kidding, but great work though.

I used to have a Commodore 16 and the 64 for was like a rolls compared to it, man it was a brick.

I was beginning to wonder whether someone would actually get around to making a newer or improved version of the 1.0 firmware release. Everytime I asked, I got shot down.

I've never had any troubles with flashing my drive but I know this is gonna make things a hell of a lot easier for all of those who've bricked their drives because they've had to continually flash their drives and have had something go wrong.

Has anyone been able to patch the new firmware with KDX 1.5 successfully, or do I need to use a hex editor? I'm assuming that foros360 will probably release a version of the firmware that works well with KDX 1.5, like they did with xtreme_proper.bin

Anyways great work Commodore4Eva. You're the man.

[sHape oF gReY]

QUOTE(scrano @ Jul 14 2006, 02:17 PM)

Has anyone been able to patch the new firmware with KDX 1.5 successfully, or do I need to use a hex editor? I'm assuming that foros360 will probably release a version of the firmware that works well with KDX 1.5, like they did with xtreme_proper.bin

Tried KDX twice, both times it messed up the key. Patched it manualy via Hexworkshop, worked perfectly first time go.

[leandro]

QUOTE(leandro @ Jul 14 2006, 04:21 PM)

Not ok for me, the eject is not possible and the xbox 360 red light .
Patched it manualy with ultra edit 32.
When i re-flash with my ORIG.bin , it 's ok .
When i reflash with old Xtreme Firmware Proper ,it's ok  
my samsung is MS25 .
  thancks for your suggestions .

[scrano]

I was just wondering whether someone that knows about hex editing can clear a few things up for me.

I've used KDX 1.5 in the past, with xtreme_proper.bin, so I didn't have to manually hexedit the xtreme.bin firmware.

I already know what my drive key is from my original firmware. I got it using KDX 1.5 and have patched it succesfully to the xtreme_proper.bin firmware. I've played backups with this patched xtreme_proper.bin firmware, so i know that it's my correct drive key.

Anyways in the readme for the new Commodore4Eva 2.0 firmware it says to copy the data from between hex positions $4000-4400.

I tried going to 4000 and 4400 and neither of them takes me to the correct location of my drive key.

I've found the correct offset for my drive key in my original firmware, by using the key I found in KDX 1.5, and did a hex search in Hex Workshop and found that it begins at hex position 40EC and finishes at 40FC.

This has confused me a bit because it looks as though I only need the 16 bytes between 40EC and 40FC ('casue this is where my drive key is)

Is there a reason that I need to copy all of the data between $4000 and 4400 or can I just copy the 16 bytes between 40EC and 40FC (which is where my drive key is) and inject that into the new firmware.

Is there some other data between those hex offsets ($4000 and 4400) that needs to be copied, or does it say to copy all of the data between those two offsets because the drive key is sometimes at different hex offsets between $4000 and 4400?

If I only need to copy the 16 bytes between 40EC and 40FC, do I just overwrite the data at the hex offset 40EC in the new 2.0 firmware and leave the rest of the data between $4000 and 4400 as it is?

I'm asking 'cause I've seen that a few people have had trouble using KDX 1.5 with the 2.0 firmware and have had to hex edit it and don't want try and copy uneccessary data. If all I need is those 16 bytes then I was just going to copy those instead of all of that data.

Any help would be greatly appreciated. Thanks in advance

[garyopa]

WARNING: Do not use "Xtreme2.0" with KDX v1.5
================================

KDX v1.5 is NOT compatible with the original "c4e"
release of Xtreme v2.0 or with his earlier v1.1.

The authors of KDX v1.5 released a Proper-Patch
for the v1.1, and it should work on v2.0 but I have
not personally tested it, to see if it is compatible.

There is no "proper" release yet for Xtreme2.0, as such
please don't use the Xtreme2.0 with KDX v1.5, you must
only manually copy your key by using a HEX editor.

For the "hackers" out there, in the original "c4e"
releases of Xtreme v2.0, all the >4000 area is
filled with >FF, and KDX v1.5 does not like that.

The Xtreme v2.0 bin needs to be patched like so,
replacing the strings of >FF with the following HEX,
to be compatible with the KDX v1.5 program:

At address >4000 = 01 11 11 11 11
At address >4015 = 02 EE EE EE EE
At address >401A = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Many thanks to "c4e" for his great release.

[leandro]

QUOTE(leandro @ Jul 14 2006, 04:21 PM)

it's ok for me at 100% with Hexworkshop