ixtreme + spoofing = doesn't work?

[p1nky]

hi people!

am i being stupid or does the ixtreme firmware just not work when spoofing when the "drive string" is altered to "spoof" a hitachi drive? in my case a 0078FK... i flashed back and forth between my spoofed xtreme 5.3A and ixtreme (and i'm 1000000000000% sure the correct key is in the ixtreme firmware) and each time the xtreme 5.3A boots everything fine and the ixtreme gives me an "insert disc into a xbox 360" dvd video... (also i'm 100% sure the discs i tried are stealth and i even tried a couple of original game discs - they ALSO show the dvd video that i should insert the disc into a xbox 360).

is the ixterem firmware made in some way so that it won't read any disc when spoofed...!?
or am i making some stupid mistake... (i wouldn't know what coz i replaced the strings in the very same way i did with the 5.3A and also i do NOT get an E66 error when booting the 360 with the ixtreme firmware in there, it just won't boot any game but show the video part instead).

please no discussion about spoofed drives being detectable by MS anyway, i know that.

also the readme doesn't mention anywhere that to be able to flash the ixtreme again u need to have the enable0800 on a DL disc (for 5.3 it did also work on a SL disc, so if anyone has problems trying to flash the drive with ixtreme on it then put the enable0800 iso onto a DL disc)

[Obveron]

I use ixtreme samsung spoofed to hitachi 78fk.. Everything works fine.

[Havok]

I am 100% sure your key is incorrect or not inserted properly...

[p1nky]

well this is very strange...

i have the original xtrem10a.bin (the one I used has a MD5 of a1bc652689cb03bdc04e4ca802be465e)

the only difference of the original to the one I flashed are those:

at offset 0x4116 I have the 16 byte key - that key is 100% the key that this box uses and needs, I checked that around 10 times now

at offset 0x202e I have "0087    LHD--TTSVD-DOR MDG3R21L0                " (instead of "sm82    STTSocprVD-DOR MSTH-49A3                ")

at offset 0x20bc I have "HL-DT-STDVD-ROM GDR3120L00780BM" (instead of "TSSTcorpDVD-ROM TS-H943Ams28   ") note that I manually added the "0BM" instead of the 3 spaces that samtool.exe puts in here at the end (so I overwrote the spaces with that, I did not insert of course), but I don't see how that could cause a problem (as I also don't get the E66 error)

I did a binary file compare and those are the only 3 differences in the file.

all other bytes are 100% identical to the original xtrem10a.bin with MD5 a1bc652689cb03bdc04e4ca802be465e I have

[sosotiit]

and what are the 10 hex values before your key starts in the fw.
what does it say in the key and spoof field in FWtoolbox when you open the hacked fw.
-soso

[sosotiit]

if your key is at position 4116 after the '0e' placeholder that might be your problem, if you have the first package that was issued.
if fact redownload your fw package it think it was corrected, or in your Fw position 40fc should be 0d not ff (that is just before the 4 pair of 11)

again believe it was corrected, redownload or correct in hex
-soso

[jelle2503]

just use samtool on an original firmware file, and on ixtreme10a.bin

that's not really smart what you 've been doin lol

and remember samsung firmware spoofed as a hitachi, this firmware cannot be read proper in firmware toolbox, or used by samtool. in this case the firmware dump of your drive xtreme5.3 is a spoofed file.
get your orig.bin out

[p1nky]

i noticed a strange thing now: when i use samtool with my original samsung firmware and ixtreme it puts the key at offset 0x4044, NOT 0x4116, also loads of other stuff changes - if i use samtool with the original hitachi 0078FK FW it puts the key into 0x4116 and doesn't change anything except the 3 things mentioned above.

how did you people for who it worked spoof the drive? with samtool or did u use samtool with your original samsung firmware and then afterwards changed the key and the strings?

[sosotiit]

Is that the latest package?

the one you have done with samtool (key @4116), is the position 40fc now 0d (zero d) and your key right after a sequence "0e ee ee ee ee". Then the key should be OK.

also you can open it to see if it is seen as a V78 in fw toolbox (note that you key will not appear since fw toolbox will think this is a v78 that has its key at a different place, do not worry about that and do not change the key in Fwtoolbox.)

-soso

[p1nky]

i have downloaded both "releases" and both gave me the MD5 sum shown above for the untouched firmware.

it does work now after i used samtool.exe with the original samsung firmware and then manually changed the key and both strings.

looks like samtool.exe writes the key to a wrong location when using it directly with a hitachi firmware.

[mcmanic]

i've just put a ms25 with ixtreme in my new hitachi core 360. I took the key from hitachi 47dj and replaced the key in the orginal ms25 with hitachi using toolbox 3.1B, then used Make iXtreme firmware.cmd and selected N to change ms25 to ms28 f/w iXtreme, then put that  output new iXtreme file back through toolbox and selected "spoof drive as Hitachi 47", then flashed it to samsung, put in 360 and all is fine.



Only thing i'm not sure of now is if i want to put back orginal Hitachi with new hitachi iXtreme when it comes out if it'll flag my systems as changed drive or because the samsung is spoofed as my orginal 47 hitachi it won't notice the change because as far as its concerned the samsung is a hitachi

[edrock]

Pinky, could you elaborate on how you did it? My co-worker is running into the same exact problem.

sosotiit: He tried downloading the latest version of ixtreme but the md5 of both firmwares were identical.

[sosotiit]

yes, but the one that xtreme10a.bin has a md5 starting with a1bc.. is not the good one, it has the FF in position 40fc.
the one that is good has a md5 starting with D832...

anyway, is prob is solved 

-soso

[edrock]

It is, thank you. 

[sasoseso]

i have the same prob

but with backup's that worked with x5.3 orginal is worked fine that mean the key is correct

so how to make a compatible backup with ixtrme1.0

I use ixtreme samsung spoofed to hitachi 78fk.. Everything works fine.

are u playing backup ??

how did u make it

drive/software

[p1nky]

well as I wrote I used samtool with my original ms25 firmware, ie "samtool ms25orig.bin ixtreme10.bin" and then manually changed the key and the 2 strings, the key is at offset 0x4044, the 2 strings should be pretty straight forward to change with a hex editor, just put in
at offset 0x202e "0087    LHD--TTSVD-DOR MDG3R21L0                " instead of "sm82    STTSocprVD-DOR MSTH-49A3                "
at offset 0x20bc "HL-DT-STDVD-ROM GDR3120L00780BM" instead of "TSSTcorpDVD-ROM TS-H943Ams28   "

do NOT use "samtool hitachifw.bin ixtreme10.bin" as it will put the key into the wrong place.

[sosotiit]

you can use the new samtool 0.7 that was released yesterday with iPrep 101 (the new release of XBM that changes its name)
available at http://x-projects.org/
-soso

[caster420]

well as I wrote I used samtool with my original ms25 firmware, ie "samtool ms25orig.bin ixtreme10.bin" and then manually changed the key and the 2 strings, the key is at offset 0x4044, the 2 strings should be pretty straight forward to change with a hex editor, just put in
at offset 0x202e "0087    LHD--TTSVD-DOR MDG3R21L0                " instead of "sm82    STTSocprVD-DOR MSTH-49A3                "
at offset 0x20bc "HL-DT-STDVD-ROM GDR3120L00780BM" instead of "TSSTcorpDVD-ROM TS-H943Ams28   "

do NOT use "samtool hitachifw.bin ixtreme10.bin" as it will put the key into the wrong place.

It does not put the key in the wrong place.  It places the key at the last place holder in the ixtreme firmware.  It works for others who have spoofed hitachi firmwares, after the byte was corrected.  Samsung key placement is variable, not static.  As long as it is at a valid key location, followed by byte of 'FF' to $5fff, it should be fine.  Simply because your ms25 has the key in a different location, doesnt make it the only correct solution.  Study a lot of samsung firmwares, and you will see the key moves a lot.  I have tested moving my key around to many places with a hitachi spoofed sammy, and have had no issues IF the key structure is intact.   

If you use 360 Firmware Toolbox to insert hitachi keys (or any key into Samsung firmware), it is always placed at the second location.  So, that throws your theory of putting the key in the wrong location out of the window.  As long as your key structure is intact and correct, samtool's placement is fine.  I dont know what your particular issue was but samtools placement of the key is no different than if you were to hex the key in at the last key location in the ixtreme firmware.  As i stated, i have helped many many people spoof with samtool and have had no issues (except for the byte, as stated).

As for the version strings, they look exactly the same as spoofed samsung firmware that was included in Xtreme 5.x releases.  Download the package and take a look.  360 Firmware Toolbox inserts it the same as what you have above but i followed c4eva's method of inserting the version strings.

Caster.

[p1nky]

hehe, sorry if u got this the wrong way, I appreciate your work and everyone's work, who invests time and then provides his tools for free to the public.

I just said that it will not work, at least it didn't work for me, coz it puts the "key in the wrong place" - whether it's the "wrong place" because the it's just plain wrong or it's wrong coz it could theoretically be there but just the "key structure" is wrong in the other place doesn't matter a lot does it?

don't get me wrong, but if a tool is bundled with a firmware and suggests it can spoof the firmware correctly, but then does not (for whatever reason) then imho it's ok to write here that this will not work "out of the box". in no way this is meant to critizise you, but just to warn others so that they don't have to waste time on this the same way i did.

and again i appreciate your work a lot - and if u added some code in the new version to avoid this problem then something good has come from this already - thank you!

[caster420]

The point is, samsung key placement doesnt have a 100% 'correct' location.  I could see this being true if you were taking your samsung original firmware and creating an Xtreme firmware from it.  In this case, however, the entire key range is copied to the Xtreme firmware (assuming a key is found), reducing any such associated issues (if they existed).

So, my point to you was, when you are taking a hitachi drive and replacing it with a samsung drive, we have no basis for where your key is meant to be placed in the samsung firmware.  Is it supposed to be in the same location as the original firmware on the samsung, even though it had a different key?  I dont know for certain, but i do not believe so.  If that is the case, we have to change the approach that is taken when spoofing for hitachi replacement drives. 

There is only so much i can fix with code.  I have fixed many issues but this one i can't fix.  I can't predict what the proper key placement of your hitachi key in samsung firmware is supposed to be.  I dont know if you know this, but hitachi key locations/structure vs. samsung key structure is totally different.  I have no basis to work off of when using original hitacih firmware as a source.   All i can do is make the program place the key in what is known in as a valid key location, as it should work.  This is what 360 Firmware Toolbox does, as i stataed before, any key injected to samsung firmware goes to the second key location (which is supposed to be an out of the box solution).  So, this would make it a valid location but NOT valid according to your statment, and shouldnt work with your drive. 

I am not trying to argue with you but make a point so that you and others can understand.  It does work out of the box in probably 99% of cases.  I have helped many people use samtool to created hitachi spoofed samsung firmware without any issues.  What your case was, i am not sure.  Maybe you should PM me and send me all your info.  Maybe there is another reason behind this.

If this truely was an issue, you could have simply done the following if you had: A) original samsung firmware from ms25, B) original hitachi firmware, C) ixtreme firmware...

1) samtool ms25orig.bin ixtreme.bin
2) samtool hitorig.bin ixtreme.bin

That would of,

A) copied your original ms25 key and key structure over to your ixtreme firmware
B) then overwrote your ms25 key with the key from your hitachi firmware, and, if you selected 'Y', it would have spoofed your firmware.

This would have been the exact same as what you did above, except for the three bytes you wanted to change in your version strings.

Caster.