451s>851s>451s?

vbimport

#1

I am just curious about the best utility to use to change my 451s@851s back to a 451s with GSB6.

Thanks.


#2

?:confused:?


#3

Flash your original backed up EEPROM and then flash the firmware with a tool of your choice will do just fine.


#4

The 451S’s EEPROM should never have been flashed in the first place.

To change it back, just flash with a 451S firmware binary using LtnFW.


#5

Originally posted by dhc014
[B]The 451S’s EEPROM should never have been flashed in the first place.

To change it back, just flash with a 451S firmware binary using LtnFW. [/B]

So, the official GS08 update definitely doesn’t modify the EEPROM? Sorry, but I haven’t converted my 451 to an 851 yet, otherwise I would check this myself. Do the unofficial GS0A and GS0C updates modify the EEPROM?

Of course, we all know that we should be backing up the EEPROM anyway, right? :slight_smile:

Thanks,
Glenn


#6

Flashing the firmware never modifies the EEPROM contents.


#7

Thanks, this helps me a lot.


#8

Originally posted by dhc014
Flashing the firmware never modifies the EEPROM contents.

That used to be my understanding also, but some threads in this forum indicate that Lite-On’s firmware upgrade program (the .exe, not the .bin) may sometimes modify the EEPROM. Sorry, I have no personal experience to back that up… just repeating what I read here in the forum.


Glenn


#9

Originally posted by dhc014
Flashing the firmware never modifies the EEPROM contents.
Right, but in this case this does not matter :slight_smile:
The question is if the 851 firmware modifies the eeprom in an way that the 451 firmware does not like. You can not be shure about this, so you have to restore the original 451 eeprom if you want to go back to the 451 firmware.


#10

Originally posted by dhc014
Flashing the firmware never modifies the EEPROM contents.
I am very confused now. In the thread: “451@851 info”, it is recommended to backup the eeprom first:
“BACKUP YOUR EEPROM AND CURRENT FIRMWARE! There are instructions and tutorials on how to do that in abundance on this forum.”

So why backup the eeprom if flashing the firmware (even with a patched 851’s firmware) never modifies it? Can a unsuccessfull firmware flash mess up the eeprom?


#11

Originally posted by oddjobb57
[B]I am very confused now. In the thread: “451@851 info”, it is recommended to backup the eeprom first:
“BACKUP YOUR EEPROM AND CURRENT FIRMWARE! There are instructions and tutorials on how to do that in abundance on this forum.”

So why backup the eeprom if flashing the firmware (even with a patched 851’s firmware) never modifies it? Can a unsuccessfull firmware flash mess up the eeprom? [/B]

Because it is so easy to accidentally flash the wrong drive. I think the tutorials should say to backup the EEPROM of every Liteon drive in your system.


#12

If I flash (firmware only) a wrong drive, the eeprom can be modified? I don’t understand very well…? If there is a problem, can not the writer be recovered only with a correct firmware flash?


#13

Originally posted by oddjobb57
If I flash (firmware only) a wrong drive, the eeprom can be modified? I don’t understand very well…? If there is a problem, can not the writer be recovered only with a correct firmware flash?

If you flash the firmware only, then the EEPROM is not modified. If you misflash the firmware, then you can recover the drive using mtkflash in DOS.


#14

If you flash a 451 to GS0A and then GS0C and then pull the eeprom and compare it to an eeprom pulled before the GS updates (i.e. a stock 451 eeprom) you find the following differences:

Comparing files stock451.bin and gs0a_c.bin
00000070: 00 01
00000072: 05 04
00000073: FF FE
00000080: 06 0D
00000081: 50 90
00000082: 17 00
00000083: 0A 54
00000084: 0C DD
00000085: 10 04
00000086: 28 3C
00000087: 90 8E
00000088: 01 00
00000089: 9D 9C
0000008A: 00 0C
0000008B: 00 10
0000008D: 00 04
0000008E: 00 FF
0000008F: 01 FF
00000090: 07 0D
00000091: 94 90
00000092: 22 00
00000093: 1A 52
00000094: A2 DB
00000095: 44 04
00000096: 3A 39
00000097: A6 B3
00000099: 8E 94
0000009A: 10 0B
0000009B: 10 0C
0000009C: 3A 00
0000009D: 01 04
0000009E: 00 FF
0000009F: 96 FF
000000A0: 16 0D
000000A1: 50 90
000000A2: 53 00
000000A3: 2F 8D
000000A4: 36 15
000000A5: 10 04
000000A6: 28 3B
000000A7: B9 A1
000000A8: 01 00
000000A9: 62 99
000000AA: 00 0A
000000AB: 00 10
000000AD: 00 04
000000AE: 00 FF
000000AF: 01 FF
000000B0: 0D 07
000000B1: 90 94
000000B2: 00 82
000000B3: D3 C9
000000B4: 5C 51
000000B5: 04 44
000000B7: BC 9B
000000B9: 9B 90
000000BA: 02 10
000000BB: 06 10
000000BC: 00 3A
000000BD: 04 01
000000BE: FF 00
000000BF: FF 97
000000C7: FF 41
000000E4: FF 24
000000E7: 23 26

So, yes Virginia, the .exe update programs CAN modify the eeprom contents!

So it appears one should pull an eeprom image as well as a firmware image each time one changes firmwares.

-Bob-


#15

The flash tool isn’t doing any modifications. Those are just normal changes that the drive makes for whatever reason. Those changes could happen when you turn on your computer, or when you put in a disc. It is not correct to assume that these changes were made on purpose by whatever flash tool you used or that they are anything significant.

Also, it looks to me like you played a DVD Movie and set the region to region one some time between the two EEPROM readings.


#16

I’ve bought 451S with FW GSB6 and at first I’ve upgraded it to latest FW - GSB7.

Then I’ve decided to try it @851. I’ve used hacked Win binary. Everything worked but then my drive started to give my problems - write errors etc. So I decided to get back to 451S.

I’ve uset ltnflash with my backed up FW GSB6. But this tool jus hung my whole PC (it went to 100% but never stopped to work). I’ve rebooted with my heart working really hard.

Fortunately my drive was still @851 :slight_smile:

So I thoughtt “if hacking tool removes check from Win binary it can do it with normal 451S FW”. So I decided to do it this way. And it works like a charm - great tool.

But anyway this drive still has write errors with all medias - even with TDK +RW x4 (philips 401) and Memorex -R x4, which have good opinions on all drives. I don’t know what to do with it…


#17

Did you test for write errors when your drive was still an unmodded 451s?


#18

Originally posted by tyfach
Did you test for write errors when your drive was still an unmodded 451s?

Yes - there were errors. That’s why I tried to install all these unofficial and unsupported (from 851S drive) firmware. but without good result.

So tomorrow I’ll exchange my drive to the new one (3 days after purchasing).