Quote from: nitrox1 on December 21, 2014, 02:26:49 AM

Well for the next person like me I think it's only fair I explain how I got here.
I flashed a firmware over WiFi and I ended up with a corrupt bootloader/kernel.
After contacting Bitmain (bitmain wanted a lot of bitcoin for a new board) and reading on Here (bitcoin.org) it was suggested to start by getting a £3 usb to serial/TTL converter, I have the one I have pictured in previous posts.
I connected my serial connection to the 3 debug pins, and opened putty using a serial connection on the right COM port, and at a baud rate of 115200
After presuming the square debug pin was earth/ GND, I had rubbish output.
I connected my serial converter as shown in previous photos, but from right to left, square to round, round, went TX (Square), Rx (Middle Round) GND (Outer round). I found using GND made a lot of things better.
After starting a putty terminal, and then turning on the flashing red led of death S3, I got a very large output of information. But if I turned it on and pressed "p" it would holt the boot process, and allow me a connection into the S3 "Easy-Link> "
As you can see from previous posts typing help allowed me to make sure that my computer was talking to the S3

I had a stable firmware already in possession, but they can be found here https://www.bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633 (mind you this is how I got here to begin with, check for a good firmware, cross reference bitcoin.org S3 support forum)
Unzip the firmware to get a .bin file

I'm using Windows 8.1 64-Bit
So I next had to get a TFTP sever program which I acquired from http://tftpd32.jounin.net/

In windows network center I found out the IP address of the S3 with both a LAN cable connected directly from my S3 to my computer and the serial to USB connected, which in my case happened to be 192.168.1.250.
I had to change this by going in to "network and sharing center" and the click on "ethernet", then under "internet protocol version 4 (TCP/IPv4)" select properties, and use the static IP address of 192.168.1.100 subnet 255.255.255.0

While putty is open, and the S3 is on, and the Easy-Link> prompt is still there
Type ping 192.168.1.100 and check the output says that the IP address is alive

After that start TFTPD64 or 32
Set current diectory to where your firmware is
Set the server interface to 192.168.1.100 (If you can't do this, you need to go back to network and sharing center part)
In the settings menu you need to set TFTP menu setting to "Bind TFTP to this address 192.168.1.100"
THEN TURN OFF YOUR FIREWALL EVEN WINDOWS FIREWALL, ESPECIALLY WINDOWS FIREWALL, but you don't need internet if your worried

Then fingers crossed type in to putty after the "Easy-Link>" prompt

Easy-Link>tftpboot 0x80000000 antMiner_S320xxxxxx.bin (your firmware name)

Easy-Link>erase 0x9f020000 +0x7c0000

Easy-Link>cp.b 0x80000000 0x9f020000 0x7c0000

Easy-Link>bootm 0x9f020000

You will get a lot of output from putty, and after the last command, the S3 should actually boot up, and then allow you to have web GUI access through the default IP address 192.168.1.99

I hope this helps someone as much as others have helped me. Thanks
Ty Excuse bad spelling, grammar, and typos

Thanks a lot guys! Your explanation worked very well for me and I managed to unbrick one of my S3s.