Upgrade Your VIA 6421 to dump 0225/0401... Slim Lite-On!

[CoDeFl@sher]

Thanks CoDeFl@sher.

I used my onboard ICH9R in IDE compatible mode to use the liteon v3 key method and got the key using dosflash16.
The thing is, I cannot load my dummy.bin in jungleflasher, I'm getting some parse error.
Could you check whats up?

Here's my dump: http://tabon.ath.cx/~mastag/0401.bin

The thing is, I've already deleted my flash because I assumed everythinig was correct.
At least the key.bin seems to be valid, so I can always create a firmware without serial.bin.

Sorry MastaG,but the KEY.bin isn't enough to rebuild/restore a FW of 0225,0401,1071...maybe you're screwed,and to make the things a bit more complicated  your link is dead.

[MastaG]

Whoops, it was a bit late.

http://tabon.ath.cx/~mastag/0401.zip

So this is what happened last night:

I unlocked my slim 0401 using my soldering iron, dosflash16 and the port on the back of my via 6421a card.
This went very smooth and it appears, that digging isn't as hard as it seems.

Of course I couldn't wait to go further so I spend an hour trying to dump it using my via.
No luck, if I enter vendor mode with MPX01 the flash will be recognized but the drive will not identify.
If I do not enter vendor mode the drive will identify but it will not detect flash.
So the via6421a is just not capable of doing a full dump it seems, not even when it's unlocked.

So I disconnected one of my raid disk (on ICH9R) and connected the sata cable to my slim (IDE compatible mode).
Then I started ms-dos 6.22, turned on my console and used dosflash16 again to dump my keys using the "liteon k" v3 key extract.
I got the above files:
identify.bin
inquiry1.bin
xtram.bin
key.bin
serial.bin
3d3esec.bin
dummy.bin

Afterwards I erased my drive because I assumed the files were correct.
However jf1.89 is giving me a hard time.

It doesn't want to open my dummy.bin and gives me a parse error.
My key.bin seems to be correct though.

I tried to open the stock 0401 firmware for slim (by c4eva) in the source buffer and I manually edited the serial, barcode, laser serial etc...
But it still won't let me alter the dvd-key which is FFFFFF on the stock firmware.

So if anyone could create a stock firmware using the above files it would definitely help me

[CoDeFl@sher]

Whoops, it was a bit late.

http://tabon.ath.cx/~mastag/0401.zip

So this is what happened last night:

I unlocked my slim 0401 using my soldering iron, dosflash16 and the port on the back of my via 6421a card.
This went very smooth and it appears, that digging isn't as hard as it seems.

Of course I couldn't wait to go further so I spend an hour trying to dump it using my via.
No luck, if I enter vendor mode with MPX01 the flash will be recognized but the drive will not identify.
If I do not enter vendor mode the drive will identify but it will not detect flash.
So the via6421a is just not capable of doing a full dump it seems, not even when it's unlocked.

So I disconnected one of my raid disk (on ICH9R) and connected the sata cable to my slim (IDE compatible mode).
Then I started ms-dos 6.22, turned on my console and used dosflash16 again to dump my keys using the "liteon k" v3 key extract.
I got the above files:
identify.bin
inquiry1.bin
xtram.bin
key.bin
serial.bin
3d3esec.bin
dummy.bin

Afterwards I erased my drive because I assumed the files were correct.
However jf1.89 is giving me a hard time.

It doesn't want to open my dummy.bin and gives me a parse error.
My key.bin seems to be correct though.

I tried to open the stock 0401 firmware for slim (by c4eva) in the source buffer and I manually edited the serial, barcode, laser serial etc...
But it still won't let me alter the dvd-key which is FFFFFF on the stock firmware.

So if anyone could create a stock firmware using the above files it would definitely help me

Now the link worked,I will open the files with Hex and later I post the results.

[mprace]

I was comparing the dummy created by Dosflash32 and JF,  they are quite a bit of difference  between both of them.

Is Dosflash creating the dummy correctly?  And for what other purpose is it created if JF refused to read it.

[MastaG]

Well the dump I made using dosflash does contain two extra files, xtram.bin and 3d3esec.bin.
I think it has enough info to recreate a nice original firmware.
Lets hope future versions of jf will support the doslfash dumps too.

[mprace]

See if my edit works:

http://www21.zippyshare.com/v/97839170/file.html

[MastaG]

Merci my friend.

I'll try it out tomorrow, I've received the sata<->ide adapter but if I fit it on the VIA card it'll be too large to fit inside my case.
So I'll have to buy a small 44pin ide female to male cable first in order to flash it.
Question, did you include the info from all files? (xtram, 3d3esec, inquiry, serial, identify) or only the dvd-key?

off-topic:
The reason I use dosflash16 is because the via card always freezes my windows7 when I connect a drive in vendor mode.
I can't even move the mouse pointer when it happens and when I turn off the drive everything starts working again.
I've seen posts about removing the via drivers but then it will not be detected anymore by jungleflasher.
So what's the solution to this?

[xjimdim]

hey there!!
Just got my ide<>sata chip and connected everything

I go to JF (dvdkey32 tab) everything is found except  the dvd key

When i click on the slim unlock though, everything goes perfectly well and i get all my files and a verified key...

Is that key alright???

[CoDeFl@sher]

hey there!!
Just got my ide<>sata chip and connected everything

I go to JF (dvdkey32 tab) everything is found except  the dvd key

When i click on the slim unlock though, everything goes perfectly well and i get all my files and a verified key...

Is that key alright???

Which FW version?

The only way to be sure if you dump is 100% valid is have a "test"drive to flash and perform a test on  console.

[xjimdim]

just downloaded the last version of JF and LT+ and everything checks out valid

Thnx so much for this idea.. you just saved me from a lot of money (because i had to buy xecuter usbpro)
Now the only think i need is to replace the pcb

[gavingt]

Some of this talk has me worried now. I just got done flashing a friend's 0272 drive (after unlocking, of course), but I don't have a USB Pro (and haven't yet made the modification described in this thread) so I used his old 9504 OFW dump as the source firmware instead of reading the new 0272 OFW before flashing. I took it over there and it worked for the ~10 minutes I was there, but I'm worried it will be hit with the random "Play DVD" errors. Is that a possibility?

Also, is there any difference between a Via 6421 9504 dump and a USB Pro 9504 dump? Because it's quite likely that my friend originally dumped the 9504 firmware that I used, and he DOES have a USB Pro.

EDIT: I guess it's good, after all. He's power-cycled it a dozen times, and it never gives the Play Disc error. Whew.

[MastaG]

I'd like to thank CoDeFl@sher, mprace and oc or their support

So I finally got the IDE female to male cable and hooked everything up...
But I already turned on my computer and accidentally connected the power supply for IDE to sata adapter upside-down (while my computer was running).
A spark and awful smell... and the IDE adapter is wasted

But since my slim drive was already erased I just connected it to the port on the back of via and flashed LT+ 2.0 using dosflash16 (since the via never worked on jf anyways).
I used mprace's dummy.bin to create the cfw, so thanks again.

After flashing it with the via card, I used my ich9r controller (in ide compatible mode) to lock the drive again.

It works and plays original discs, haven't tried any backups but I'm sure it works.
Now it's time to get it glitched..