Smoke of death

So I accidentally connected 24V to one of the analog in ports on my Arduino.
A fissure of doom opened on surface of the atmega328 and started erupting noxious fumes of death.
I have replacement chips and a programmer, and I've successfully programmed a new bootloader onto a chip.
When I hook the board up to USB the lights all turn on.
However, when I go to program the board, it doesn't show up in the Serial Port list.
Does this mean the board has become a brick?

I accidentally cut my Arduino into two pieces with an axe.

Does this mean the board has become a brick?

don't worry, sparkfun sell a smoke refill kit Magic Blue Smoke Refilling Kit - TOL-10622 - SparkFun Electronics

lesto:
don't worry, sparkfun sell a smoke refill kit Magic Blue Smoke Refilling Kit - TOL-10622 - SparkFun Electronics

That only works the beginning of April.

You might be able to resurrect the board by replacing the DIP style chip, but that will depend upon what other damage may have occurred to the board.

wanderson:
You might be able to resurrect the board by replacing the DIP style chip, but that will depend upon what other damage may have occurred to the board.

I did put a new chip in, and I even successfully programmed the bootloader using the board that got fried.
It just doesn't show up as a board that can be programmed, boooo.
I'll just assume it's a brick I guess.

how did you programmed the bootloader?
probably the briked chip is the FTDI/8U2 for a problem like this

You may possibly be able to keep using the board by programming it via the serial pins (not the USB chip) if that is worthwhile. You would need an FTDI cable. Or, via the ICSP pins, in which case you need an external programmer. Depends how much of the board was damaged.

I was able to program the boot loader on the new chip through the ICSP on the Arduino using the AVR Pocket Programmer.
Would I need to upload the hex file at the command line?
If so... any idea where I could find that file when it's compiled?
I'm guessing I could use some avrdude command to do the actual uploading.

ok, if you used ICSP then you bypassed the fried serial-to-usb chip.

you can look where your temp file are stored by pressing shift + compile in arduino ide < 1.0, and setting a checkbox in preferencies menu into newer.

command line is not enought if you don't have a replace for the chip... i dunno if AVR Pocket Programmer can do it (it shurely can uplad hex WITHOUT using bootloader)

Thanks for pointing out those preferences, really useful.
I was able to program the board using the pocket programmer!
I enabled verbose output and then uploaded to a different board, changed the command to match my board and programmer, made sure to remove the -P option since I don't need it through ICSP, and it totally works.

Maybe I'll pick up a new FTDI chip and see if I can fix the board at some point.