Procedure for installing old firmware?

I tried version 4.0 - I havent the horror stories that others have but the drive now no longer works remotely ie via wdtgo

Whaty is the prcedure for going back to the old firmware as I understand iot wont let you install an older firmware by default.

I do wish wd would sort this abomination ogf a drive out.

Or perhaps they’re gradually making it worse and worse on purpose?

There is no official procedure. In fact, there is a check in place to avoid just that. I was able to do it, but haven’t created any guide. Too lazy to do it, I might do it later. But if you know a bit, you can do it:

Commnt out lines 256 through 259 of updateFirmwareFromFile.sh:

 

if [-z “${update_container}”] && [“${vnew}” -lt “${vnow}”]; then

error=“failed 200 "invalid firmware package"”

pre-update_error $error

fi

wget  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

unzip  sq-030401-230-20140415.deb.zip

# /usr/local/sbin/updateFirmwareFromFile.sh sq-030401-230-20140415.deb

  

(of course, I don’t take responsability if your disk crashes, your girlfriend leaves you or your nany goes homicidal :P)

8 Likes

sorry

how do I access this file?

Thanks,

It worked for me.

I commented the whole pkg_update_verify() section and it worked lika a charm.

we need an option that doesn’t use ssh

Phew just downgraded. Back to V3. Teach me to apply a firmware update before checking the forums for the horror stories. Will not be upgrading again in a hurry!!!

I need this drive performing well…like a week ago , and seeing that WD is not doing anything urgent about the V4 FW,  I’m going o take a leap of faith and downgrade using this method.

But first I would like some clarifications from users that have done so.

  1. What FW version apears in Dashboard?..If i later on decide to upgrade to a official fixed version (Let’s say V5) is there going to be an issue?

2.Do I lose my settings (users, shares …etc)?

3.Is it the same performance as before?

Thank You.

1. v03.04.01-230 and it wont stop you upgrading. 

  1. No

  2. Not sure I don’t move a lot of large files so not sure if transfer speeds are any different

as a failsafe - we need an option to downgrade firmware properly not via ssh

Thanks for your quick reply. I did it and it works flawlesly.

I folowed this guide :

http://community.wd.com/t5/WD-My-Cloud/GUIDE-Transmission-2-82/td-p/619597/page/10

My speeds are back to 45-50 megs and the dashboard is quite responsive.

Of course I was hoping for a quick fix from WD , like a resigned v3 FW, but my lesson is learned here  :NEVER TRUST WD SOFTWARE UPDATES !!!

1 Like

*repeats*

we need a guide that dosn’t involve ssh

Worked perfectly for me.

Sadly, without SSH enabled I don’t think a downgrade is possible.

i , whitch command i have to send to edit “updateFirmwareFromFile.sh” file ?

Hi,

i found to myself .

First this :

cp  /usr/local/sbin/updateFirmwareFromFile.sh /shares/Public/./updateFirmwareFromFile.sh

after edit the file (i used textpad)

and after this:

cp  /shares/Public/./updateFirmwareFromFile.sh /usr/local/sbin/updateFirmwareFromFile.sh

if you need to download the deb fie , it can be found here :

http://drivers.softpedia.com/get/HDD-SSD-NAS-USB-Flash/Western-Digital/

Worked like a champ.  

Now I have to update the other 3 that I have deployed at customer locations to get them back up to proper operating status. 

What a pain in the arse.  

Unless you know your way around Linux and vi, this is best left alone and pray that WD fixes this Fv(|< up soon.

OK, I’m going to try to make this easy.  Please don’t use this until other experienced users here have verified I’ve not missed anything.  

1.) Download a copy of putty from here:  http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

2.) Copy these two files to your Public folder on your MYCloud:

  a:)   https://drive.google.com/file/d/0B-0paIVBKCR2bmhDX1Vwb3hRRnM/edit?usp=sharing  #This is the .deb file

  b:)   https://drive.google.com/file/d/0B-0paIVBKCR2bEJuU3ZrS3psMU0/edit?usp=sharing   #This is the updateFirmwareFromFile.sh file that has been edited to allow downgrading.

3.) Run putty and ssh to your mycloud.  username: root   password: welc0me

4.) copy and paste the below commands one at a time in order, into the ssh window.  Do not include the # symbol at the beginning.

cp /usr/local/sbin/updateFirmwareFromFile.sh /usr/local/sbin/updateFirmwareFromFileOLD.sh (this creates a backup of the old update file)

cp /shares/Public/updateFirmwareFromFile.sh /usr/local/sbin/updateFirmwareFromFile.sh

cp /shares/Public/sq-030401-230-20140415.deb /CacheVolume/sq-030401-230-20140415.deb

cd /CacheVolume

 ls (you should see sq-030401-230-20140415.deb listed here), if not STOP and start over).

 updateFirmwareFromFile.sh sq-030401-230-20140415.deb

That’s it.  There will be several long pauses during the process, be patient in about 10 mins the NAS will reboot and be back on 3.x firmware.

Again, until someone post below this and verifies all the steps are proper DO NOT USE THIS!

1 Like

Your linked file  “updateFirmwareFromFile.sh” is original, unedited one.

I Hashed out the 4 lines, and now it is working.

Try to change the link.

So:

The tutorial worked, but my WD My Cloud page still reports firmware 4.0…

You can’t downgrade without SSH.  To downgrade in SSH, change the version number to the one you want, i.e. 03.04.01-230 in the file /etc/version

Then just manually update it via Dashboard.

3 Likes

So simple, Tnynyn.

Thanks.

It worked.

Added in a few details to tquame’s instructions (which are awesome by the way) to help the newbie to ssh complete the firmware downgrade successfully…hopefully this helps. Thanks again to tqaume, Lorrenzo and JoaquinAR which helped me to figure it out for myself: 

1.) Download a copy of putty from here:  http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe (and make sure via the WD My Cloud dashboard to enable ssh in settings)

2.) Copy these two files to your Public folder on your MYCloud:

  a   https://drive.google.com/file/d/0B-0paIVBKCR2bmhDX1Vwb3hRRnM/edit?usp=sharing  #This is the .deb file (don’t forget to right click and extract or unzip the file to just get to the deb file itself)

  b   https://drive.google.com/file/d/0B-0paIVBKCR2bEJuU3ZrS3psMU0/edit?usp=sharing   #This is the updateFirmwareFromFile.sh file that has been edited to allow downgrading. (if it doesn’t work then in putty type in >>

nano /usr/local/sbin/updateFirmwareFromFile.sh        

and scroll down to the bottom of the file to find where it  should say the following, you’ll need  to enter in the # signs before each line then press ctrl X  and then Y to save the file then you can go onto step 4 and continue on

    # if [-z “${update_container}”] && [“${vnew}” -lt “${vnow}”]; then    

    #         error=“failed 200 "invalid firmware package"”    

    #         pre-update_error $error 

    # fi

3.) Run putty and ssh to your mycloud.   username: root   password: welc0me (this is done by entering in the IP address within the "Host Name (or IP address) field within putty and clicking on “Open” at the bottom, then the username will be prompted for, and then the password, you won’t see the password as you type it in though, then just press enter)

4.) copy and paste the below commands one at a time in order, into the ssh window.  Do not include the # symbol at the beginning (after each command press enter, to paste within putty you simply after copying the text from the instructions “right” click within putty to paste where you see the cursor location)

cp /usr/local/sbin/updateFirmwareFromFile.sh /usr/local/sbin/updateFirmwareFromFileOLD.sh (this creates a backup of the old update file)

cp /shares/Public/updateFirmwareFromFile.sh /usr/local/sbin/updateFirmwareFromFile.sh

cp /shares/Public/sq-030401-230-20140415.deb /CacheVolume/sq-030401-230-20140415.deb

cd /CacheVolume

 ls (you should see sq-030401-230-20140415.deb listed here), if not STOP and start over).

 updateFirmwareFromFile.sh sq-030401-230-20140415.deb (if you get an error that says invalid firmware package look at step 2 again in detail and make sure to edit the FirmwareFromFile.sh file within putty)

1 Like