"Failure to write update.bin"

3 replies [Last post]
hindsight
hindsight's picture
User offline. Last seen 1 year 32 weeks ago. Offline
Joined: 10/09/2008
Posts: 37

I know this problem has appeared in other threads, but it's not getting answered.

I updated from the original firmware to 1.1.2.37 as I had problems with the green screen issue. This then gave problems with the sensitivity of the remote, so then tried 1.0.1.30 which didn't fix the problem so I decided to go back to 1.1.2.37. That's were my problem starts - all I get is the message "Failure to write update.bin" about 10 seconds after it tells me it's updating the firmware. Happens with all the firmware versions available.

Seems like it's a common problem judging by other threads - perhaps it doesn't like loading a previous firmware version over a later one. Am I stuck now?

I found a thread on here that explained how to revert back to the original "shipped" firmware, but the "procedure" actually does nothing other than the equivalent of a reset.

Does anyone here know how to get the box back to the original "shipped" firmware or at least how to force a firmware update? The reset button on the back seems to have no more function than the software driven menu reset.

I have talked to D-link who just send me in circles. It's as though they know nothing about this box.

Help, help, help please

Nicox
Nicox's picture
User offline. Last seen 2 years 44 weeks ago. Offline
Joined: 02/13/2008
Posts: 8
Failure to write update.bin

I hope too
I've the same problem

slightlyoffbeat
slightlyoffbeat's picture
User offline. Last seen 35 weeks 6 days ago. Offline
To everyone who is having

To everyone who is having this issue, can you please PM me with the size of the firmware file that you rolled BACK to. By size i mean MB. This is important and should help us figure out what is going on.

Thanks!

[dan]

hindsight
hindsight's picture
User offline. Last seen 1 year 32 weeks ago. Offline
Joined: 10/09/2008
Posts: 37
The sizes of the update.bin files I used are:

Thanks for coming back. Here's the details (properties) of the update.bin files I used to get myself into this pickle:

The 1.1.2.37 is 7,392,670 bytes in a folder called DSM-330 1.1.2.37.EU - last modified 18th Aug '08

I then went back to:

The 1.0.1.30 is 4,736,121 bytes in a folder called DSM-330 1.0.1.30.EU - last modified 7th Apr '08

I hope this help to find the problem.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.