This might be a really dumb question but are you opening adb from Command Prompt? If you double click on either adb.exe or fastboot.exe from Windows they do open and close really quickly. If you open Command Prompt to navigate to wherever your file is using the cd command (so "cd path/to adb"; obviously put your own path in!). Then type "adb" and the sucker should open. Once adb is open all you have to do is cut and paste Diamondback's commands into adb. I think that the boot.img attached to the OP that you are pushing to the sd card has to be in the same folder as adb in Windows (I might be wrong on this but I am sure someone more knowledgeable will correct me).
Sorry if I have misinterpreted your question (noob warning!). Hope that helps and good luck with the debricking.
For those who have been having issues with the adb not seeing your device with either the Asus or the naked drivers I had the same issue.
I ended up doing it the old fashioned way (aka the long way) by actually installing the SDK tools step by step. It was the only way I could get it to recognize my 1a bricked device after hours of trying a dozen different drivers.
|Thread Tools||Search this Thread|