Samsung Galaxy S III i9300 Boot Loop, No Recovery, after Cyanogenmod Installer Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:

I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:

1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring. 
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL! 

2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers. 

So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin. 
Any ideas? 

Thanks in advance.
If you have access to the Download mode, then nothing is lost.

I suggest you not to repartition the device first, just try to get a standard ROM flashing done. Based on my experience Odin usually fails because of driver issues (I had plenty of problems using Win 8.1 x64, while just doing the exact same procedure on Win7 worked well)

Also if you had USB debugging enabled, you might catch what's the problem during the startup/bootloop using logcat. With some luck you might push the missing files to your device as well.