NAD M66 Bricked after 4.4.11 Update

Answered

Comments

17 comments

  • Official comment
    Mark T.
    Sr. Support Crew Member

    Hi Jeremy,

    I see that you have submitted a support request regarding this issue. A member of our support crew will reach out to you shortly.

    Thanks for #LivingHiFI

  • Alex

    I had the same no sound issue on my Powernode 2i. Scared me as I thought something had completely died. Reboot didn't fix it but unplugging from power and restarting did the trick. If you haven't tried it yet give it a go.

    0
  • Jeremy Gray

    I have tried just about everything I can think of. 

    Soft reboots, hard reboots, factory reset, bluOS update, etc. 

    0
  • Dieter Verbanck

    Same happened with my C399 only the update completely failed and it's now bricked

    0
  • Chris J

    Had the same problem with my Pulse Mini 2i speaker and my C3050LE. Had to do a factory reset on both to get them up and running again. 
    @Bluesound: Would be great if u implemented a setting where I as a user could deactivate the BluOS controller searching for updates or at least give me the choice to install or not. 

    0
  • Jeremy Gray

    Day 1 Update:

    NAD Support reached out with a generic email asking for basic information. Nothing else. 

    All I want is a version of the previous firmware to load onto the preamp to be able to listen again. 

    0
  • Dieter Verbanck

    Any luck Jeremy? I tried factory reset on both the MCU and BluOS module but nothing seems to work, as soon as it boots it will download the update and try to install it again, with the same result.

    My system is entirely unusable right now and it's starting to piss me off

    0
  • Jeremy Gray

    Day 3 Update:

    NAD says my only option is to send the unit into a authorized service center. 

    Closest one to me is 8 hours away. 

    I have sent a response requesting the pervious firmware to load onto the unit VIA USB before spending hundreds of dollars on shipping. I am very doubtful this will happen. NAD is insisting this is a hardware issue, if this is the case its a hardware issue caused my a firmware update, and if that is the case this will be the end of my NAD experience if all repair costs and shipping are not covered. 

    I am thankful I have my old C658 sitting around, however at this point I am pretty sure both units will be getting traded in as soon as this is resolved. 

    The response from NADs support team is really sad. 24 hours plus per response that are emails that couldn't have taken more than 10 minutes to write.  

    0
  • Jeremy Gray

    Prompt response from customer service this morning. 

    The development team is looking any possibility to remotely restore the unit. Fingers crossed. 

    0
  • Jeremy Gray

    Just want to follow up. 

    NAD service has been extremely helpful and proactive. They have offered to log into the unit remotely and attempt to fix the issues. I unfortunately had to leave town so I will work with them next week to get them logged in. 

    They have mentioned that there is potentially a hardware issue and not just a firmware issue. Something in the debug log is making them think this, and it sounds like they have had other similar issues.

    I will update this post next week. 

    0
  • Dieter Verbanck

    Update from my side: NAD support was able to remote in my amp and diagnosed the same thing. They asked me to move the MDC module to a different slot, then had me update the MCU. After that the MDC seemed to be able to update. As of right now everything seems to be functioning again, I hope your issue is fixed in the same way

    0
  • Andrew Fraser

    Dieter, I said I would update re my experience.  After a week or so of NAD support attempting to remote in to my card, they eventually succeeded and advised me also to move the card to the other slot.  By then, as they had gone silent for a few days (due to illness as it turns out), I had given up and decided to do a back panel reset on my C389; this didn't work until I remove the MDC2 card but was successful once the card was removed. So I have my music system back at last. I've lost confidence in the software (it should be able to recover if it encounters a problem during a firmware update; this is not a new or esoteric problem these days) and am not willing to go through this again.  I was able to return my card and opted to do so.  I'm going back to my previous arrangement with a stand-alone Node. I'll miss out on Dirac, but I won't get locked out of my music system again!  Hopefully NAD will invest a little more time in improving the update process and eliminate this issue.  All the best

    0
  • Dieter Verbanck

    Thanks for the update Andrew. My confidence in the software and future updates definitely took a hit as well, I won't be updating in the future without checking forums first and waiting a few weeks, hoping any bugs that might be there are worked out

    0
  • Tony W.
    Product Support Manager

    Thanks for your feedback Gentlemen. 

    We monitor customer feedback carefully and take the upgrade process very very seriously. Though coincidental in your two cases, they were unusual given the amount of BluOS MDC modules in the wild. Both cases have been sent to QA for review.

    We do understand your concerns, but honestly these appear to be isolated incidents and do encourage you to upgrade with confidence in the future. 

    Andrew, your DIRAC filters should be still stored in the laptop or associated with your DIRAC account, so can be easily re-added.

    0
  • Dieter Verbanck

    Thank you for following up Tony. I must add, I have 0 complaints about the service I received from the moment the problem presented itself, service and communication were both on point, compliments there

    1
  • Tony W.
    Product Support Manager

    aw shucks

    0
  • Andrew Fraser

    I do agree with that.  There's definitely a genuine desire to solve the problem and that was appreciated.

    1

Please sign in to leave a comment.