Originally Posted by T-Macgnolia
How can the OP do this, the device will not even turn on to boot into fastboot or the bootloader therefore the instructions in the thread you linked are pretty much useless to the OP. It seems that the OP has hard bricked the device somehow,maybe fried the processor Blythe back to back flashes or fried the NAND memory with the back to back flashes, who really knows at this point. But right now my money is on JTAG or replacing the mainboard willbe the only fix.
he mentioned nothing about trying it with adb/sdk fastboot using command prompt,
i was in similar situation with my friends phone last week, after 3 days of searching and reading i finally followed that thread and now the sensation is running ordroid 2.1 rom. the buttons on the phone got disabled somehow. had to manually install drivers in device manager, like he mentioned that comp detects the phone. so before giving up adb/sdk is worth a try atleast in my case it was.
Omnia i900 >Galaxy S >Galaxy Tab 10.1V >Galaxy S2 >Htc Sensation >Galaxy S3 >Nexus 7>Galaxy Note II
>SGS4>Note3+Gear>Note8>Nexus 7 v2>??? $$$