It will not be a consolation, but the cause is maybe that you started doing something BEFORE the previous process finished.
You need to RMA the unit. Contact Bitmain warranty if this is a November miner. Warranty is 90 days.

You are now raising the possiblility that you have not bricked the board ... do you have any other S3+'s on your network and if so is any of them on the default static IP?
When you flash a unit that (usually) is on DHCP, th web UI will NOT register a response because the flashing resets the IP to the default one and turns the network settings to static. Thus you have to log onto the default static IP (192.168.1.99) rather than the on you had on DHCP. And if you have 2 units on the default IP, ofcourse one will not show up on your network, and that will be the last to ry to use that IP (which in this case is the rebooting reflashed rig).

It's pretty clear to me that the firmware cooked my controller.

Here's what Bitmain replied to me- re: the same issue as Patriotminer:

https://bt.irlbtc.com/view/671189.msg9845178#msg9845178
     "antMiner_S320141126.bin don't surpport adjust voltage. Hash board's power maybe cut off when you over clock."

and https://bt.irlbtc.com/view/671189.msg9845434#msg9845434
      "Now miner hardware modified, I want know your hash board's num. Can you help me? Thanks."

I provided him the details here:
https://bt.irlbtc.com/view/671189.msg9846032#msg9846032

and also sent an RMA request to: info@bitmaintech.com

Their day should be starting soon. So I anticipate hearing something from them given how many people have posted problems here re; the Nov firmware.

I have 2 S3s and 1 other S3+. They survived the ordeal just fine. In fact, i set back their frequency to the level for a standard S3... as they were all running between 470 and 590 with the Oct firmware. Evenso, one of my standard S3s is still close to 600. Am a bit worried about that one- but it smells ok.

You are a very clever person bitsolutions. Now, can you kindly tell us how to open and read the code in that hex file please? If these jombas from bitmain are not going to be honest with us, their customers, then I think they've earned us the right to pore over their little secrets. I thank you in advance.

You can't read it since its compiled.

The pic firmware seems to change every other release or so. For example antMiner_S320140811 and antMiner_S320140826 have the same pic firmware as do antMiner_S320141013 and antMiner_S320141024. Right now the main issue with antMiner_S320141013 is the broken webui, I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue), the latest firmware has the correct filesystem and fixed webui but a bad pic firmware. If you want to use antMiner_S320141013 you should ssh and execute the following command to fix the webui.

I'm not exactly sure if there's any improvements other than the webui fixes. Kind of your choice on whether you prefer to fix the webui or the pic firmware as both appear to have the same end result as far as I can tell however I haven't tested performance differences extensively. I have yet to check if cgminer was updated between those versions either so you may want to do a more detailed comparison.

@bitsolutions

".... I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue)...."


I have the bricking problem you mention. Bitmain just told me my warranty has expired. (They must start counting the 90 days from the time they ship instead of teh day I received it )

Questions:

1. Instead of buying another control board, how do i use ttl to recover it? Sorry, I 'm gonna need step by step instructions.

2. My other S3s are running okay on the Oct 24th release. Should i re-flash them to the Oct 13th firmware?

Not being one to take good advice when given some, after realising the miner_pic.hex file was an ASCII file, I decided to deploy my secret reference material (read google) and seem to have found something, though I can not make any sense of it. I am sure bitsolutions, the clever clogs on our side, can so here goes.

1. My reference material suggested a site to view a hex file: http://en.webhex.net/
On visiting the site, I browsed to the file and uploaded the miner_pic.hex file

2. On the next screen, I scrolled to the bottom of the box and clicked on the Export link

3. When the Export screen was loaded, I un-checked the Headline, Offsets and Readable Characters check-boxes then clicked on the Export button on that screen.

4. I was then presented with the hex data in a web page. I had not mentioned this, but earlier,  my reference material had also suggested to me an online dis-assembler here : http://www2.onlinedisassembler.com/odaweb/

5. I copied all the exported hex data (Ctrl + A then Ctrl + C) then flicked over to the dis-assembler, clicked on the Platform button and changed it to avr (this may b wrong), and in the box below that I pasted the hex data into it.

The page then did a little spinning wheel and after a short while, spewed out something like this:



Now the easy bit, @bitsolutions or any of you clever clogs out there, can you make any sense of that?