Uniti Update failed. Fault 61

Thank you, osprey,

I saw this thread before. There are two things mentioned that I could try:

1) do a factory reset. But I would need to know how to do this by the front panel without using the menu that disappears after some seconds because of fault 61.

2) try to downgrade to 3.22 again. But the update instruction tell not to do this!? But as it is bricked anyway?...

I did try his, but it seems to be the wrong button. I also tried another one without success.

I was able the quickly navigate through the menu to activate the factory reset, but I am not sure if it was successful as it might got interrupted by the fault 61 message again.

Reinstalling of the same version 4.1 did not help either.

What I have learned: Never upgrade on weekends.

A warning: do not try to hold the "next" button while turning on the uniti. This brings the device into the "soak mode". And now I do not know how to get it back out of this. You certainly have to hold another key (combination) while turning on the uniti again.

MUTE seems not to help here. I am writing a mail to the naim support. I hope they can help me remotely without needing to send them the uniti. So many weeks without music would be hard.

The answer of the naim support was that I had to send the unit in. I should contact my dealer.

Brought the uniti there and got a call from the german naim support http://www.music-line.biz/naim one day later that I could have fixed the problem myself by simply installing firmware 3.22 again. 4.1 has a bug that leads into the Fault 61 on older devices. This will be bugfixed in a forthcoming version. He was not sure if I can do the update while the uniti is in the soak mode. But he could not tell me how to exit this mode without looking up this detail. So I will visit my dealer again to get my uniti back home. Perhaps it is already fixed because they wanted to try the update remotely.

Warning: Usualy you should not downgrade to older versions. But in case of 4.1 and 3.22 it is possible because they are compatible enough somehow.

Gert, firmware errors in hifi equipment can be very annoying but have at least little consequences. At least when compared to firmware errors in, e.g., medical equipment. Still, errors are errors.

Does your device have "an n-Link connection" ? If yes, you should not have upgraded yourself and you cannot blame Naim for the error. If not, the documentation at https://www.naimaudio.com/updates is obviously incomplete. In this case it would be useful if Naim could provide complete update documentation.

Hi nbpf,

as I do not know what an "n-Link connection" is I think the uniti 1 does not have any.

Because naim offers the firmware updates for download for normal users they certainly are meant for being run by the customer. Otherwise the supporter who phoned me up had told me, I guess.

Naim's official site reads:

"Please note: the streaming product must already be on version 3.00 before updating,, To check what software your product is on click here. If your product is running a sofware version prior to 3.00 or has an n-Link connection please contact Naim Support."

Thus, since you upgraded from 3.22 > 3.00 there are only 2 possibilities. Either your Uniti does have an n-Link connection (whatever this is) or it doesn't. In the latter case, Naim's documentation would be obviouly incomplete. 

As far as google told me, the N-Link seems to be the Apple-iDevice Connection where you need a special N-Link cable for http://www.goodwinshighend.com...iPod_integration.htm ? Later Unitis came with an USB port where you can connect an iPad, etc. I think this is not called N-Link-Connection, is it?

My naim does have the USB socket in the front for connecting an apple device.

As the german support told me, the english update documentation is incomplete. This was fixed in the german documentation only.

When I updated my Uniti1 (n-link version, with a board upgrade) to v.4.1, I relied on the then press release (https://www.naimaudio.com/news...rives-naim-streamers) according to which the essential element seems to be whether your device has a 24/192 board or not. And indeed, I did not encounter the slightest problem with my device (now transferred to a second system) after the update. Maybe, someone could clarify whether the information of the then press release the has been superseded by the more restricted information quoted by nbpf.

adca

An update to this story:

i have got my uniti back from the dealer. Nothing was done with it as the the dealer himself is on holiday and the substitution (right word?) did not know what to do. So I downgraded the unit to 3.22 myself and now it seems to work again (I will connect it after this post).

Problems with the downgrade:

1) as the uniti was not able to connect to the network it had no IP address. but the update wants one. I typed in the IP that the uniti usually has and the update continued even if the uniti could not be found by this address. Maybe it works without entering an IP address after two retries? I only tried to continue without entering an IP address once and the update process returned to the same input field again after a while. So if you have the same problem you probably can input any unused IP address from your network.

2) The soak mode was active the whole time while the update was running. Even after resetting it to factory settings the soak mode was still active. So I tried around and found the following solution to exit the soak mode (the uk naim support did not answer my second mail regarding this question): turn off the device, hold the stop button from the front panel, while holding it turn on the uniti. This will bring up the menu for switching to the factory settings. Press the mute button to start the reset. After this the soak mode was turned off. Maybe there is a direct way to turn it off,, but even naim seems not to know it. Ok, they keep this secret.

Now wish me luck that everything works again.

Hello Gert,

I had exactly the same problem (upgrading a naim Uniti 1 from 3.13 to 4.1), and same error message.

For your information, the device started to crash when I reentered the wifi key (wifi had been disabled when I plugged a network cable for the upgrade).

I managed to get my Uniti back to life by plugging again the network cable. This temporarily deactivates the wifi, and you can then definitively deactivate from the main menu.

Now the device works fine, apart from the fact that I have no wifi.

Hope this helps.

On my own side, I nevertheless brought back the device to the resealer, which is delaying to send it back to the French importer, for some bad/legal/technical reason. When I get by device back, if unrepaired (which is likely), I will try to downgrade to 3.22, as you suggest.

Thanks to you for having posted this.

CM.

All this reminds me of all the trouble I had getting my Uniti 1 to install 3.22, now it is sold and I am back to the silver discs, thank god.