you should go with option 2 (from the beginning and even now)
I had the exact same problem in my friend's galaxy win,
he asked me to root it and I did, but after rooting the phone, when I reboot it shows error,
and goes after it normally to system (with root in it), anyway this isn't the point.
The point is I assumed that this error was caused by the custom recovery,
so I had to flash the original one, but since the galaxy win is not popular at all,
I couldn't find a flashable stock kernel, so I had to create one.
I extracted the kernel from the stock tar ROM [from samsung website]
and put the command to flash it, and here is where the big mistake happened.
I tried a similar command to yours, and boom the device wont even show samsung logo or connect to adb.
I couldn't find a software solution, so I told my friend to take it to samsung and he did, and they fixed it for free [it was in the warranty period]
I find out the real cause of this problem, and it was:
when I searched for the command, I took it from other device's forum,
and later (after the break) I read that not all phones has the same partitions,
so when I flashed the recovery I entered ...../dev/block/mmcblk0p2
and that is where the kernel or the bootloader stays in galaxy win (not the recovery),
I should have entered ...../dev/block/mmcblk0p4 instead.
So when the recovery was placed in kernel's or bootloader's place,
the phone(or tablet) won't have the right data to start booting,
that is the case, sorry for the long story,
I hope it'll help you