Topic: Antminer s3 bricked with reset button (Read 1739 times)
I keep forgetting to dig stuff out, but I might have some time this afternoon. Had a couple folks asking already. If you want something, PM with an offer.
You know, I got a bunch of S3 around the shop (courtesy of NotFuzzyWarm) that'll probably never get used. Who needs a good controller?
what are you charging for a board? im assuming +shipping added on to it as well.
You know, I got a bunch of S3 around the shop (courtesy of NotFuzzyWarm) that'll probably never get used. Who needs a good controller?
Werks fer me. Some are s3+ as well if it makes any difference. Please do part out hashboard assemblies for replacements as well if you don't need anything off of them. Glad for anything to put them to good use and help folks out . Also hopefully more burger money for ya as well 
You know, I got a bunch of S3 around the shop (courtesy of NotFuzzyWarm) that'll probably never get used. Who needs a good controller?
The firmware can be reflashed using a USB TTL programming dongle wired directly to the controller board. There are instructions out there. Of course that method isn't for everybody but the usb dongle costs almost nothing on ebay.
I also have a S3 stuck on restart...
Would be great to find some clear instruction on how to connect to the S3 with such a device and the how to reflash the firmware...
The chip on the controller formed a bump on top, all the led lights were ON while it was burning.
The wires were connected: TX (Square), Rx (Middle Round) GND (Outer round).
I managed to get some info from it with putty. But after it read: initialization completed! I could not input anything with the keyboard. Then I went for a powercycle, and at that point I started to smell the burning.
And now the waiting game begins, as I need to order a new controller x)
The wires were connected: TX (Square), Rx (Middle Round) GND (Outer round).
I managed to get some info from it with putty. But after it read: initialization completed! I could not input anything with the keyboard. Then I went for a powercycle, and at that point I started to smell the burning.
And now the waiting game begins, as I need to order a new controller x)
Well, I tried connecting to it with putty and a usb-ttl adapter. I got some data, but after initialization competed text, it started to burn. I melted my adapter.
It melted your serial to usb adapter? I would make sure to check points as that is something I just have not seen on here. But if it is just the controller you still could contact bitmain support and send it in and have them take a look at it.
But do you have pictures? If your able to take a picture of what burnt and where it was wired.
Well, I tried connecting to it with putty and a usb-ttl adapter. I got some data, but after initialization competed text, it started to burn. I melted my adapter.
The firmware can be reflashed using a USB TTL programming dongle wired directly to the controller board. There are instructions out there. Of course that method isn't for everybody but the usb dongle costs almost nothing on ebay.
If you have a lot of S3's and plan on keeping them long term this is a good idea. But it does take a more technical user then one who gets new flashed board from Bitmain.
I will admit on the one S3 I bricked I just paid for a new one with good flash on it. They did a good job getting it to me pretty quick. Just was easiest option at the time for me.
The firmware can be reflashed using a USB TTL programming dongle wired directly to the controller board. There are instructions out there. Of course that method isn't for everybody but the usb dongle costs almost nothing on ebay.
if still no success, please mail the control PCB (without the data cable) to the following address with $20 money order and your return address. The replacement control PCB be sent to you
Bitmain Warranty
3700 Quebec Street
Unit 100-239
Denver, Colorado 80207
*Please send it in with a carrier service with a tracking number for your record. (1st class mail with tracking, or priority mail or UPS/FedEx)
Bitmain Warranty
3700 Quebec Street
Unit 100-239
Denver, Colorado 80207
*Please send it in with a carrier service with a tracking number for your record. (1st class mail with tracking, or priority mail or UPS/FedEx)
"Power cycle" = "powering off and on again", so yeah sounds like it.
Power-cycle? Meaning holding reset, waiting 3 minutes, holding reset again, powering off and on again?
Did you power-cycle after holding the reset?
holding the reset for a long time didn't help.
I could not reach 192.168.1.99 with a browser or with pinging. But Advanced IP scanner found it. So now its like a dead fish in the pond. I see it, but after poking it with a stick, it doesn't react.
Could it be that the reset erased some part of the firmware?
I could not reach 192.168.1.99 with a browser or with pinging. But Advanced IP scanner found it. So now its like a dead fish in the pond. I see it, but after poking it with a stick, it doesn't react.
Could it be that the reset erased some part of the firmware?
S3 doesn't default to DHCP, as far as I know. 192.168.1.99 possibly? It's been a while. Also if I'm remembering right, the reset button has to be held for a pretty long time to work right.
Hello,
I got an used antminer s3 from ebay and once I managed to get it working, PSU wise, and everything worked like a charm, I wanted to reset all the settings for a fresh start, so I pushed the reset button.. two times, as I missed the first time. But then the led lights started flickering in a weird way, so I thought the reset boot was compromised. And thus I powered it down and tried again, this time holding 3-10 second and all that.
But it looks like it got stuck in the reset limbo, as it never boots back, if I dont shut it down manually. And now it doent show on the network, although the green led flickers and it procedes to start normaly (at least as for the led lights and fans).
My question is: have I bricked it?
Thanks for any answer!
I got an used antminer s3 from ebay and once I managed to get it working, PSU wise, and everything worked like a charm, I wanted to reset all the settings for a fresh start, so I pushed the reset button.. two times, as I missed the first time. But then the led lights started flickering in a weird way, so I thought the reset boot was compromised. And thus I powered it down and tried again, this time holding 3-10 second and all that.
But it looks like it got stuck in the reset limbo, as it never boots back, if I dont shut it down manually. And now it doent show on the network, although the green led flickers and it procedes to start normaly (at least as for the led lights and fans).
My question is: have I bricked it?
Thanks for any answer!
Jump to: