Binflash - NEC/Optiarc firmware flasher and dumper

...and another successful flash on a host running FC8/kernel 2.6.23.9-85.fc8, to a ND-4570A from 1.02 to 1.03.

I successfully flashed my NEC 5100A drive with patched firmware of NEC 5500A using Binflash with GUI utility. However I still do not have DVD-R write capability.

Can some one help

Thanks

Would mean it were NOT successfully flashed.
Maybe you need to use the drive converter.........??

But maybe writing to DVD-R won't work at all. It's probably the same issue as with the ND-1100A and ND-1300A drives. Some of them did work while others did not.

Yeah, a painful hit & miss thing.

Hi,

I have just bought a DELL Inspiron 530 which has a SONY~NEC Optiarc AD5170S DVD Writer with firmware version 101B

This drive only manages to copy (read) DVD-Video discs at a rate of around 5x when the drive is actually capable or reading 16x

I have tried flashing the firmware using various version that are supposidly for this model with no joy.

The message that I get from the official Optriac Flasher (firmware v1.12 and v1.13) is 'Target Optriac AD-5170S is not found correctly'.

When I try to flash with Liggy's LD5170S 1.M1 Firmware Package I get a message along the lines of 'Flashing your drives firmware is not yet supported'. Here is the identity dump that the tool produces:

--- Start of identification ---
Optiarc - DVD+-RW AD-5170S
Optiarc - DVD RW AD-5170S
5131373551313735302E30350000000081000000000000000000000081F5C2BA
FF5EC6D13162E41C5D13E4F600090B8FDACA631080FF1D1C003FCE70C7
--- End of identification ---

All I want to do is remove the read speed ristriction, can anybody help me please?

I have downloaded both the 'LD5170S 1.M1 RPC1 Firmware Package' and the 'LD5170S 1.M1 Firmware Package' but can not flas my AD-5170S as previously posted. The interesting thing is that the window title of these packages when run is reported as being 'Binflash GUI 1.39'. yet the change logs (and your response above) states that support for this drive was only available from v1.40 - could this be why the drive can't be flashed with either of these packages?

download latest standalone BinFlash and flash your drive with any 5170S firmware (.bin or .exe).

Sorted, thanks.

First of all I flashed the drive with the standard Optriac v1.12 firmware (using Binflash v1.44) downloaded from Liggy's and Dee's site. Then I downloaded the standard Optriac v1.13 firmware and took this into MediaCodeSpeedEdit and checked the 'Increase Read Speed' option. I saved the patched firmware package and then ran it and it reflashed my drive to firmware version 1.13 with 'Riplock' removed. I can now read DVD-Video discs at 16x.

Thanks again for the advice and to everyone else that posts in this forum for all of the useful information!

I know this might be posting the wrong place to post but I havn't found any better place to ask this. How can I help make BinFlasher work for me? If I can do anything at all...? And if so, what information do I need to supply? I've got a Dell OEM Optiarc AD-7640A. Thanks - Geezy

Hello
I need help, I have Optiarc AD-5170A, and I want to make this one into AD-7173A with Labelflash technology.
So, I made cross-flash with bootcode 0.08 and now my OS say that I have AD-7173A, but I can't flash it with any firmware.

[edit Dee-27]
Sorry we can't help with crossflashing and please do NOT post links to bootcodes.

---

Last edited by Dee; 22-05-2008 at 01:45. Reason: removed links

Thank you for your attention, but I solved the problem already.

Now I have 100% Optiarc AD-7173A with labelflash.
Sorry for links, I didn't know this.

Hello!
I have NEC 4551A (earlier it was 4550A). I dumped it firmware on winXP and on Mandriva Linux, with the help of your necflash utility. And these dumps not equals, in dump which was made under GNU/Linux the last byte has value of 31h, in winxp - 30h. Is this last bit important? or it's a buggy software?

Binflash version 1.45 has just been published. It mainly adds support for Optiarc AD-7910A and AD-7913A drives. There's is also an untested support for some AD-5170A drives used in duplicators.

Users of the Mac version please note that this version was compiled on OS X 10.5 with XCode 3.0. As a result this version might not run on 10.2 or older anymore but I couldn't test this myself.

Hello,

tried to flash a AD-7633 on a Mac Mini G4.
Dumping the original image seems to works as it creates a ~1.8MB file, but flashing gives me an error message.
What's wrong?

Thanks,
Wolfgang


> ./necflash -version
Binflash version v1.45
Drive interface v1.34
NEC interface v1.45
NEC internal v1.45

> ./necflash -scan -v -s
List of supported devices:
Trying to query device A:
Device : A:
Vendor : Optiarc
Model : DVD RW AD-7633A
Firmware : 1.00

> ./necflash -dump -s ./Original_Firmware.bin A:

> ./necflash -flash -v -s 100bt_rpc1.bin A:
Identified drive: 43
Detected drive from Firmware: 43
Entering safe mode
Error entering safe mode
Error while flashing firmware

There seems to be a problem on Mac that prevents people from flashing their drives. The only way around that was to use bootcamp and Windows to flash the drives (or use a different PC)

Not sure if anyone already tried running the command as root user (i.e. using sudo)

Thanks so far,
good point, I will try to flash as admin (with and without sudo) today evening.
Will post the results tomorrow.
Wo.

Hi again,

login as admin and using sudo makes no difference.
Any other ideas?

Thanks,
Wo.

Hi there.

I got a Fujitsu Siemens Scale-X pc with a Optiarc AD-7170a FW 1.85 drive in it, i want to flash it with Optiarc 1.05 firmware, is that possible?

The drive is not found by binflash, i tried PIO mode, safe mode, and nothing works, i have been scanning google for days, im not about to give up, but i would appreciate a little help, in fact, i'd love it.

Im clueless, anyone?

/Alex

Don't flashing fw1.05(orig)...
Optiarc AD-7170a fw1.02
Binflash GUI 1.44
"Error submitting checksum"
help me.

Hi I was just wandering if you can help me with a little issue I'm having with my burner. I've got an optiarc ad-5170a and some point last year I started getting dma/crc errors everytime I tried to burn something. After a bit of research I found that it might of been down to the firmware, so I found your website and downloaded the firmware and binflash and updated it. Everything worked up till about 2 weeks ago when I had to format my pc. After I'd done it the burner program started throwing up the same errors again so I downloaded everything again to change the firmware and this time it hangs everytime I try to flash to the drive - with either the old or new firmware.

Any ideas?

Could be an issue with your IDE drivers. Maybe you used different ones for your new installation?

First post, only to say that (I think) I have sucessfully flashed my Sony AW-Q170A with the Liggy's firmware for the Optiarc AD-5170A (RPC1 version), on Arch Linux. I didn't have time to test it, but at least K3B recognizes it well.

Anyway, I have a little question. When I made the backup of the original firmware, it tooks only a few seconds. However, when I flashed the drive, it tooks about 20 minutes or so. In fact, I had considered cancel the process and start again, but when I decided to do it, the flash, fortunately, finished.

Is this normal? I've readed in the Binflash homepage that the process only took a few seconds, in both ways (dump and flash). At least, it seems that was sucessfull. Soon I'll make a few tests, and the truth will be revealed.

Cheers,
Javier

PD: I'm from Argentina, and crap is great compared to my english. Sorry about that.

This is definitely not normal. While flashing might take a few seconds longer than dumping, it should not even need a minute. I can only guess that Linux had a problem when the drive switched back from the bootcode to the real firmware. I only know similar problems when updating a drive's bootcode which almost never allows access to the drive again without rebooting the machine. In case you add a "-v" to the commandline you should be able to see which step was the one that needed so long.

I don't suppose you can point in the direction of where I can find if it is and also how to repair it.