Print

[kc69]

Hi,

Used MTKFLASH to retrieve original firmware from my TS-H943 ms28 uing the 10 second via trick. All seemed to go ok, orig.bin created but looking at it now, the dvd key is set to FF. Other parts of the file look fine as I can see references to the firmware verison etc. Unfortunately, I didn't notice this until I had already flashed my drive. Can anyone help as I have only my orig.bin file now to find the key? Any ideas why that happened? Screen prints attached.

Thanks.

(IMG:http://freespace.virgin.net/k.compton/Image1.jpg)

(IMG:http://freespace.virgin.net/k.compton/Image2.jpg)

[xboxexpert]

in the orig.bin goto hex 4000 and see if you see a key.

[kc69]

00004000:01 11 11 11 11 ff ff ff ff ff ff ff ff ff ff       .....ÿÿÿÿÿÿÿÿÿÿ



This post has been edited by kc69: Oct 26 2006, 07:40 AM

[langnao]

QUOTE(kc69 @ Oct 26 2006, 02:04 PM)

00004000:01 11 11 11 11 ff ff ff ff ff ff ff ff ff ff       .....ÿÿÿÿÿÿÿÿÿÿ

Based on your pictures, look okay to me. The real 16bytes key start from 0x40EC. Goto 0x40EC, do u see 16 bytes of hex values starting from 0x40EC - 0x40FB (inclusive) ?

[kc69]

Around there, i've got the following:

000040e0:ff ff ff ff ff ff ff 0c ee ee ee ee 65 a2 b8 6d    ÿÿÿÿÿÿÿ.îîîîe¢¸m
000040f0:2b 54 65 96 15 e6 6d f5 6d ef 6d d5 ff ff ff ff    +Te–.æmõmïmÕÿÿÿÿ
00004100:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

Thanks.

[langnao]

QUOTE(kc69 @ Oct 26 2006, 02:19 PM)

Around there, i've got the following:

000040e0:ff ff ff ff ff ff ff 0c ee ee ee ee 65 a2 b8 6d    ÿÿÿÿÿÿÿ.îîîîe¢¸m
000040f0:2b 54 65 96 15 e6 6d f5 6d ef 6d d5 ff ff ff ff    +Te–.æmõmïmÕÿÿÿÿ
00004100:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

Thanks.

This is your key : 65 a2 b8 6d 2b 54 65 96 15 e6 6d f5 6d ef 6d d5 , looks okay. Did u try injecting this key to the new firmware?

[kc69]

Hi,

I just updated xtrem41b.bin using hexed, replacing locations 0x40EC - 0x40FB with the key and still got E65, any ideas what i'm doing wrong?

Thanks.

[langnao]

QUOTE(kc69 @ Oct 26 2006, 03:03 PM)

Hi,

I just updated xtrem41b.bin using hexed, replacing locations 0x40EC - 0x40FB with the key and still got E65, any ideas what i'm doing wrong?

Thanks.

Try the one that comes with the firmware pack that inject the key into the new firmware for u and compare it with the one that you had created? Is it correct?

Anyway, if still got problem flash back to your original firmware and see if everything is back to normal? You will need the enable0800 disc since u had already flashed to 4.x firmware ...

[kc69]

I tried the one that comes with the firmware pack and compared mine with the output from that and both are the same. I'm a bit stumped as to why it's not working.

I tried putting the original firmware back on yesterday, came up error E65, didn't use the enable0800, but it seemed to flash ok, what does the enable0800 do to assist flashing?

[langnao]

QUOTE(kc69 @ Oct 26 2006, 03:28 PM)

I tried the one that comes with the firmware pack and compared mine with the output from that and both are the same. I'm a bit stumped as to why it's not working.

I tried putting the original firmware back on yesterday, came up error E65, didn't use the enable0800, but it seemed to flash ok, what does the enable0800 do to assist flashing?

So u uses the 10 sec trick to flash, even after loading 4.x firmware? Anyway E65 is DVD drive error. Your original firmware looks okay. Have you check the SATA connection between your drive and motherboard? Change the sata cable and try?

[Textbook]

The 4.x firmware uses the MS28 core firmware.  That's why if your original drive already had MS28 firmware, you can continue to read/write to the drive using the methods you were using.  That's why if you have a VIA chipset, you don't really need to use the 0800 disc on the 4.x firmwares.  You can just use the bad flash recovery / 10 second trick like it was an MS28.

As for your drive...

If you flashed back the orig.bin and it still didn't work, then the only thing I can think of is a corrupted read ??  Anybody else offer their input ?

[majik655]

QUOTE(Textbook @ Oct 26 2006, 08:30 AM)

The 4.x firmware uses the MS28 core firmware.  That's why if your original drive already had MS28 firmware, you can continue to read/write to the drive using the methods you were using.  That's why if you have a VIA chipset, you don't really need to use the 0800 disc on the 4.x firmwares.  You can just use the bad flash recovery / 10 second trick like it was an MS28.

As for your drive...

If you flashed back the orig.bin and it still didn't work, then the only thing I can think of is a corrupted read ??  Anybody else offer their input ?

Textbook you are right...corrupted read.

I have a question for ya...

is it possible with these 10 second tricks...
that on SOME machine setups,  maybe it is even chipset combos or something...

say if it is not 10 seconds and maybe they did it in lets say 8 seconds or say 12..
would it be possible for the reading of the firmware to get corrupted because of the timing??

I hope this makes sense.   I do not use the 10 second trick or swapping I have not come across corrupted firmware.  its like something hiccupped or something durring the process.

is it possible that some peoples floppy drives are not up to par or even their floppy disks?
I see ALOT of this with floppies and or drives.

This post has been edited by majik655: Oct 26 2006, 05:28 PM

[Textbook]

The floppies .. DEFINITELY.

Story of mine (last day I used a floppy) flashed 3.3 to my drive from a floppy, all went 100% and said OK.  Drive worked, no errors, eject worked fine, games booted.  I thought "cool."  Brother was complaining that Oblivion kept going out right in the middle of the game with dirty disc errors.  At first I thought it was the faster read speed and my cheap media.  I was going to reflash with an older fw but first I flashed 3.3 back on there using my USB stick.  The problems stopped.  So yeah, the fw flashed 100% but it was somehow corrupted and was the cause of dirty disc errors.

I haven't used a floppy disk since.

For the timing..I doubt it.  The timing trick is only for getting the drive to have a certain port open to access the drive.  I've done the bad flash method using 2 seconds, 8 seconds, 10 seconds, 12 seconds.  They all worked fine for me.

[boofie75]

QUOTE(langnao @ Oct 26 2006, 08:09 AM)

Try the one that comes with the firmware pack that inject the key into the new firmware for u and compare it with the one that you had created? Is it correct?

I thought the newer versions of Xtreme inject the key into orig.bin for you?  Sorry, I'm a noob to this, just asking questions.

[majik655]

QUOTE(Textbook @ Oct 26 2006, 09:06 AM)

The floppies .. DEFINITELY.

Story of mine (last day I used a floppy) flashed 3.3 to my drive from a floppy, all went 100% and said OK.  Drive worked, no errors, eject worked fine, games booted.  I thought "cool."  Brother was complaining that Oblivion kept going out right in the middle of the game with dirty disc errors.  At first I thought it was the faster read speed and my cheap media.  I was going to reflash with an older fw but first I flashed 3.3 back on there using my USB stick.  The problems stopped.  So yeah, the fw flashed 100% but it was somehow corrupted and was the cause of dirty disc errors.

I haven't used a floppy disk since.

For the timing..I doubt it.  The timing trick is only for getting the drive to have a certain port open to access the drive.  I've done the bad flash method using 2 seconds, 8 seconds, 10 seconds, 12 seconds.  They all worked fine for me.

I know you have said this before textbook but I guess as of right now I am just lazy to go find it.. but what do you use for your usb boot stick?    usb boot maker?  

I personally do not like using any automated way of flashing.. meaning samread or whatever..
I personally do not care about rebooting and using toolbox to inject key etc etc then reflashing again.
So knowing that I guess all I need is to just have is bootable usb and the files for mtkflash just as if it was a floppy correct?    I do know my board boots to usb just wondering if I am missing something.