Binflash - NEC/Optiarc firmware flasher and dumper

vbimport

#1645

Binflash v1.59 has just been uploaded including support for the AD-7710H drive.


#1646

[QUOTE=Liggy;2614447]Providing the firmware would be great. I’ll try to provide an updated Binflash later today.[/QUOTE]

Sorry Liggy, may attach the firmware here?


#1647

[QUOTE=Liggy;2614469]Binflash v1.59 has just been uploaded including support for the AD-7710H drive.[/QUOTE] I have tried downloading Binflash, will not extract tried Win.Zip when trying to open it just flashes off the screen, tried saving it in a file folder and when I tried to open got a message as to " No Support" ?


#1648

Which Binflash download did you try? Win32 or 64 Bit? GUI or command line?

I just tested downloading and running all Windows versions. The GUI came up as it should and also the command line versions showed help information when started without parameters.

Perhaps you should try downloading again. If you’re able to calculate md5 checksums, these are the values you should get:
8afbed17aa170d2428ed9d3b591b5374 *necflash_windows.zip
5eb7de19b12ed9164adcf3b8c9917915 *necflash_windows_x64.zip
48c6e437d2224b8617f9a4dc8fa2a980 *necflash_wingui.zip
0e7dd23c2134ade3f3f3b0eb6f68598b *necflash_wingui_x64.zip


#1649

Perhaps you should try downloading again. If you’re able to calculate md5 checksums, these are the values you should get:
8afbed17aa170d2428ed9d3b591b5374 *necflash_windows.zip
5eb7de19b12ed9164adcf3b8c9917915 *necflash_windows_x64.zip
48c6e437d2224b8617f9a4dc8fa2a980 *necflash_wingui.zip
0e7dd23c2134ade3f3f3b0eb6f68598b *necflash_wingui_x64.zip

Excuse my ignorance Liggy, I know how helpful you can be, but to a newbie like me this is like Greek. I have tried downloading it about 5X. I may be missing a step?


#1650

[QUOTE=durkinjt;2615611]Excuse my ignorance Liggy, I know how helpful you can be, but to a newbie like me this is like Greek. I have tried downloading it about 5X. I may be missing a step?[/QUOTE]
It’s not ignorance :wink:
There are tools (like this one) which can calculate checksums of a file and this way you could have compared them to what they should be.

If you downloaded 5 times, it could in theory still be some browser caching issue. But you still didn’t tell me which of the 4 Windows versions you downloaded. Was it really a GUI one?

Something else you could check is if there is still a necflash.exe or necwinflash.exe process after the program terminates. This could indicate that the program hangs when scanning for devices.


#1651

Binflash v1.59 does not support to dump firmware from my Optiarc AD-7280S Drive (Iodata OEM).

--- Start of identification ---
Version: 1.59
Normal : Optiarc  - DVD RW AD-7280S  - 1.20
Boot   : Optiarc  - DVD RW AD-7280S  - 0001
|Sony Optiarc Inc.               AD-7280S        |
0000000000000000000000000000000000080000000000000000000000000000
4733303547333035302E3131XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX01FF0000
000000000000000000000000000000000000000000000000000000008BXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFF
--- End of identification ---

#1652

Your drive identifies as a completely different drive compared to other AD-7280S drives and also has a different bootcode. Looking at the identification it should rather be AD-7300S instead of AD-7280S - following the naming schemes for previous drives.

This also means that you won’t be able to flash any other AD-7280S firmware and others won’t be able to flash this IOData firmware. I’ll send you a link with an updated Binflash version via PM. I think commands will be the same as for other AD-7280S drives. Does this one still have only 1 MB RAM?


#1653

Thanks Liggy! The Drive still has 1 MB RAM.


#1654

Got your firmware. Thanks. Will release the updated Binflash and perhaps some patched firmwares later.


#1655

[QUOTE=Liggy;2616343]Got your firmware. Thanks. Will release the updated Binflash and perhaps some patched firmwares later.[/QUOTE]

Thanks.


#1656

Binflash has been updated to version 1.60 and it should now support the IO-Data AD-7280S OEM drives


#1657

Hi Liggy

Just signed up today looking for RPC hacks for the Optiarc AD-7717H (Firmware 102A?) that comes installed on some Dell laptops (mine’s an L702x).

NEC Winflash 1.60 successfully scans the drives, and a flash dump gives a file 1,769,480 bytes large.

I can send this dump to you if its any help hacking it?


#1658

I just attempted to dump the firmware from my new AD-7283S drive, but Binflash doesn’t seem to work … shouldn’t it suppose to work OK with this drive?

Here’s the ID file:

--- Start of identification ---
Version: 1.60
Normal : Optiarc  - DVD RW AD-7283S  - 1.01
Boot   : Optiarc  - DVD RW AD-7283S  - 0001
|Sony Optiarc Inc.               AD-7280S        |
0000000000000000000000000001000000000000000000000000000000000000
4732383847323838302E3037XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX00FF0000
0000000000000000000000000000000000000000000000000000000068XXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFF
--- End of identification ---



#1659

Apparently binflash v1.60 for Win32 (either GUI and command line) doesn’t run on Windows 2000. When I try to run the executable it says that it’s not a Windows application. By using the dependency walker it seems that a couple of kernel32 calls are missing (DecodePointer and EncodePointer). Since I’ve overwritten the previously working version and I don’t remember which one it was (I know, I’m stupid :p), is there some archive where I can download the older versions? Thanks!


#1660

[QUOTE=cvs;2617166]I just attempted to dump the firmware from my new AD-7283S drive, but Binflash doesn’t seem to work … shouldn’t it suppose to work OK with this drive?


Normal : Optiarc  - DVD RW AD-7283S  - 1.01
|Sony Optiarc Inc.               AD-7280S        |

[/QUOTE]
This seems to be the issue. Although your drive is an AD-7283S, there is one memory location which identifies the drive as being an AD-7280S. Unfortunately this is the value that Binflash needs to use if it is available. I wonder why your drive lists the wrong value. :confused:
I could provide you with a special Binflash build for your drive but I cannot change the general behaviour of Binflash without spending too much time.

[QUOTE=anto12358;2617995]Apparently binflash v1.60 for Win32 (either GUI and command line) doesn’t run on Windows 2000. When I try to run the executable it says that it’s not a Windows application. By using the dependency walker it seems that a couple of kernel32 calls are missing (DecodePointer and EncodePointer). Since I’ve overwritten the previously working version and I don’t remember which one it was (I know, I’m stupid :p), is there some archive where I can download the older versions? Thanks![/QUOTE]
I’m using Visual Studio 2010 to compile Binflash for Windows since version 1.51 and that’s probably where Binflash stopped supporting Win2K. Although it looks like it’s not impossible to add support for W2K again, I’m probably not going to implement these changes as W2K is EOL for 1.5 years now and not even supported by Microsoft anymore and for security reasons you should really consider upgrading your OS to something more recent.


#1661

[QUOTE=Liggy;2618035]I’m using Visual Studio 2010 to compile Binflash for Windows since version 1.51 and that’s probably where Binflash stopped supporting Win2K. Although it looks like it’s not impossible to add support for W2K again, I’m probably not going to implement these changes as W2K is EOL for 1.5 years now and not even supported by Microsoft anymore and for security reasons you should really consider upgrading your OS to something more recent.[/QUOTE]
I normally use Linux, but with the i386 Linux version I couldn’t upload the firmware (that’s why I tried Windows). No matter which firmware I try to download, the message is always:
Error while flashing firmware
Error submitting checksum
But probably it’s the drive itself that doesn’t work anymore; when i try to burn a DVD it fails with a “power calibration error”. I hoped that restoring the original firmware could make it work again, but it’s a very long shot, I’d better buy a new one :slight_smile:


#1662

[QUOTE=anto12358;2618053]I normally use Linux, but with the i386 Linux version I couldn’t upload the firmware (that’s why I tried Windows). No matter which firmware I try to download, the message is always:
Error while flashing firmware
Error submitting checksum[/QUOTE]
Can you give some more details (e.g. which drive your have what exactly you’re trying to do, which firmware, etc.)? You could also try starting Binflash with one or two -v as additional option. Just paste the terminal output in a new post here.

But probably it’s the drive itself that doesn’t work anymore; when i try to burn a DVD it fails with a “power calibration error”. I hoped that restoring the original firmware could make it work again, but it’s a very long shot, I’d better buy a new one :slight_smile:

Most of the power calibration errors are caused by incompatible or low-quality media


#1663

[QUOTE=Liggy;2618063]Can you give some more details (e.g. which drive your have what exactly you’re trying to do, which firmware, etc.)? You could also try starting Binflash with one or two [B]-v[/B] as additional option. Just paste the terminal output in a new post here.

Most of the power calibration errors are caused by incompatible or low-quality media[/QUOTE]

The drive is rather old and I haven’t used it from quite a while, but the DVDs are the same I’ve always used without problems. I think it is a AD7170A, and apparently some time ago I’ve uploaded the AW-G170A v1.75 firmware into it (which seems wrong; are these two drives 100% compatible?). Actually I don’t remember if I upgraded the firmware because of the power calibration error or for another reason (it’s been at least one of two years ago). Anyway, this is the output with -v option:

$ ./necflash -scan -v
Binflash - NEC version - © by Liggy and Herrie
Visit http://binflash.cdfreaks.com

List of supported devices:
Trying to query device /dev/sg1

Device : /dev/sg1
Vendor : SONY
Model : DVD RW AW-G170A
Firmware : 1.75
Trying to query device /dev/scd0
device SONY DVD RW AW-G170A 1.75 unsupported

$ ./necflash -flash -v -s ad7170a_105_orig.bin /dev/sg1
Binflash - NEC version - © by Liggy and Herrie
Visit http://binflash.cdfreaks.com

Identified drive: 29 - 3036
Detected drive from Firmware: 29

You are about to flash your drive with the following firmware:

Vendor: Optiarc
Identification: DVD RW AD-7170A
Version: 1.05

Remember no one can be held responsible for any kind of failure!
Are you sure you want to proceed? (y/n) y

Entering safe mode
Sending firmware to drive at 0x030000
Sending firmware to drive at 0x038000
Sending firmware to drive at 0x040000
Sending firmware to drive at 0x048000
Sending firmware to drive at 0x050000
Sending firmware to drive at 0x058000
Sending firmware to drive at 0x060000
Sending firmware to drive at 0x068000
Sending firmware to drive at 0x070000
Sending firmware to drive at 0x078000
Sending firmware to drive at 0x080000
Sending firmware to drive at 0x088000
Sending firmware to drive at 0x090000
Sending firmware to drive at 0x098000
Sending firmware to drive at 0x0a0000
Sending firmware to drive at 0x0a8000
Sending firmware to drive at 0x0b0000
Sending firmware to drive at 0x0b8000
Sending firmware to drive at 0x0c0000
Sending firmware to drive at 0x0c8000
Sending firmware to drive at 0x0d0000
Sending firmware to drive at 0x0d8000
Sending firmware to drive at 0x0e0000
Sending firmware to drive at 0x0e8000
Sending firmware to drive at 0x0f0000
Sending firmware to drive at 0x0f8000
Sending firmware to drive at 0x100000
Sending firmware to drive at 0x108000
Sending firmware to drive at 0x110000
Sending firmware to drive at 0x118000
Sending firmware to drive at 0x120000
Sending firmware to drive at 0x128000
Sending firmware to drive at 0x130000
Sending firmware to drive at 0x138000
Sending firmware to drive at 0x140000
Sending firmware to drive at 0x148000
Sending firmware to drive at 0x150000
Sending firmware to drive at 0x158000
Sending firmware to drive at 0x160000
Sending firmware to drive at 0x168000
Sending firmware to drive at 0x170000
Sending firmware to drive at 0x178000
Sending firmware to drive at 0x180000
Sending firmware to drive at 0x188000
Sending firmware to drive at 0x190000
Sending firmware to drive at 0x198000
Sending firmware to drive at 0x1a0000
Sending firmware to drive at 0x1a8000
Sending firmware to drive at 0x1b0000
Sending firmware to drive at 0x1b8000
Sending firmware to drive at 0x1c0000
Sending firmware to drive at 0x1c8000
Sending firmware to drive at 0x1d0000
Sending firmware to drive at 0x1d8000
Sending firmware to drive at 0x1e0000
Sending firmware to drive at 0x1e8000
Sending checksum bf86 to drive
Error while flashing firmware
Error submitting checksum


#1664

[QUOTE=Liggy;2618035]This seems to be the issue. Although your drive is an AD-7283S, there is one memory location which identifies the drive as being an AD-7280S. Unfortunately this is the value that Binflash needs to use if it is available. I wonder why your drive lists the wrong value. :confused:[/QUOTE]

Who knows? Maybe its a new Sony Optiarc internal ‘branding’ trend … or they simply forgot to fully re-brand the base model properly? :confused:

I’ve got my drive from Play.com just before the new year … the drive was manufactured June 2011 (20110623, Made in China) and its the Silver bezel variety AD-7283S -0S.

It would be interesting to see if the AD-7281S drives also identify like this when they finally get released …

[QUOTE=Liggy;2618035]I could provide you with a special Binflash build for your drive but I cannot change the general behaviour of Binflash without spending too much time.
[/QUOTE]

That would be great, thank you! :flower: