[Galaxy S II Q&A, Help & Troubleshooting] Clonkex:
I guess so. I hope you didn't think I was being too serious; I was only joking that I expected a reply that quickly :P Some areas of this site, people often reply in minutes, that's all :)

Really? I'm using Windows and I've never had any problems with Heimdall. In fact, I found Odin to be buggy and confusing. Heimdall seems far better (it's not leaked software, for a start), and I like the cmd-line interface.

I can't tell if you're annoyed that I didn't search or if you're joking. In fact I did search but couldn't find any information. And I wasn't going to elaborate here because all this info is in the Cyanogenmod forum thread, but if you insist:

1) Begin by reading the instructions on the wiki page: wiki.cyanogenmod.org/w/Install_CM_for_i9100

1-a) This means READ THE WARNINGS

2) When it tells you to download the recovery, ignore - the link is broken. Download from here: xdaforums.com/galaxy-s2/orig-development/kernel-clockworkmod-recovery-6-0-2-9-t1118693

3) Extract the zImage file from inside and continue with the wiki instructions

4) When it tells you to click replace driver (which, btw, is badly worded - you must select "Install Driver" from the drop-down and it'll turn into "Replace Driver"), use the up-down arrows next to WinUSB to select libusbK. Otherwise you may get errors with Heimdall

5) After flashing the first CWM recovery, if you want to flash CM11, download the newer CWM from here: xdaforums.com/galaxy-s2/development-derivatives/cwm-clockworkmod-recovery-kit-kat-4-4-t2628412

5-a) Start your S2 into Recovery and connect it via USB. On your PC, open a cmd and check that your device is showing up properly (adb devices). It it's not, download and install the Samsung USB drivers from here xdaforums.com/showthread.php?t=2038555 or here xdaforums.com/showthread.php?t=2038555 (or Google it - they're everywhere)

5-b) Use "adb push [recovery-zip-name-here] /emmc"

5-c) On your S2, find and flash the new recovery zip, then reboot into recovery again. You'll now be using the newer CM11-compatible CWM recovery

5-d) Now the device will no longer show up in ADB, even with the drivers installed (if it does for some reason, you can ignore this step). Open Device Manager on your PC and find either something called "i9100" or "Unknown Device" (of which there may be many on some computers - you'll have to work out which). Right-click > update driver software > browse my computer > let me pick > have disk.

5-e) Browse to the file and click ok "SAMSUNG\USB Drivers\16_Shrewsbury\ssadadb2.inf". This folder is normally in Program Files (not x86)

5-f) Continue by clicking next or whatever it is (I forget) to finish the installation of the driver. Test that it was successful (after it's finished) by doing "adb devices" again

6) If you're using the older CWM recovery: Use "adb push [cm<11-zip-name-here] /emmc" and flash it via the recovery

7) If you're using the newer CWM recovery: Use "adb push [cm11-zip-name-here] /storage/sdcard0" and flash via recovery

8) Push the correct gaps package (if using CM11, remember the warnings on the wiki - get the one that's small enough to fit on the S2's system partition) and flash it

9) At this point, you should be safe to wipe the cache and do a factory/data reset. I didn't (not immediately - I did a little later on), and just booted up, and it worked fine, but you'll probably want to do it at some point anyway to get rid of the crapps that are probably still on your S2 and it wipes all your data and settings, so best to do it now

10) Reboot an enjoy a freshly CM'd device! Remember that the first boot can take 5-10 mins. I'm currently using cm-11-20140609-SNAPSHOT-M7-i9100.zip, and so far it's been very stable, fast and reliable, only I've had issues trying to connect to the wifi. As there was a new snapshot released yesterday, I'm going to be updating to cm-11-20140708-SNAPSHOT-M8-i9100.zip shortly

There. It's not a complete beginner's guide, but it may help someone who's having problems with their S2 and Cyanogenmod. Hopefully this will show I don't expect anyone here to do all my work for me or to be at my beck and call; I should rarely be taken too seriously, and while I was genuinely surprised that no one replied faster, it was entirely a happy, curious surprise, not in any way an annoyed or unhappy surprise. Kinda feel like I got off to a bad start with that post :eek:

If anyone has any specific questions, I'll be happy to elaborate :)