Quote from: LASERminer on December 18, 2016, 05:26:45 PM

Quote from: elokk on December 18, 2016, 01:46:10 AM

One of my R4's that stopped hashing on one board has stopped hashing completely after trying to restore the original firmware. The hardware version listed under system overview says " Socket connect failed: Connection refused".

I have tried powering off several times, reboots, updating firmware, etc. No more hashing. There has to be an easy fix to this without sending to Hong Kong or letting sit in Denver for weeks on end. Any thoughts?

EDIT: unplugged the original board that did not hash and fired back up, the one remaining board is hashing again at 4th/s!

Exactly same fault here - I think we discovered common issue.

What are you doing about a fix? Sending back to Hong Kong? Denver? Entire unit or only board? Bitmainwarranty is not answering the phone or replying to emails