[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dege13:
Hello,

I just rooted my Samsung Galaxy S3 today. I copied several ROM zip files (i think there were 4) to my SD card to test out using MTP. As you may know, MTP (on Windows 7) is not the greatest experience. Since the copy was taking so long, I canceled it. I now know that when you do that MTP seems to leave the incomplete file there with the fill file size. I suspect the is the root of the issue.

I went to install the Omega v46.1 Jelly Bean 4.2.2 ROM after testing a different one that I was not happy with. Omega game up with its installer, everything seemed to work good. It asked to wipe the user data, and reboot the device. All looks good. I could not wait to try another ROM.

Blank screen.... waiting, waiting... Maybe they just have no boot logo.... waiting. Okay after waiting several hours for it to boot I thought maybe I would try to reboot and clear the user data and cache myself. Tried to reboot. Nothing happened. No vibration, no LED, not logo.

Cannot get into Download mode. Cannot get into Recovery.

Pull battery, wait. Put battery in while holding Volume key, Power button and Home. Nothing at all. Battery pull and waited a few hours. Tried again. Nothing. Panic starts.... I remembered the MTP file copy and checked the ROM zip files. Incomplete zip file.... Damn.

It is not easy to cover everything I have tried to fix it or all of the research I have done, but I'll try.

Researched bricked devices. Learned of hard vs soft. This does not appear to be soft to me, but why would my bootloader be damaged by installing this ROM?? I am new to this, but I think I understand the difference pretty good.

I spent the last few hours trying to find a micro USB cable that I could use to make a USB Jig. I did that using this guide and it did not help :(

http://xdaforums.com/showthread.php?t=2121306

And this guide

http://xdaforums.com/showthread.php?p=8822843

Researched the Jig more to make sure I got it right. Tested again with multimeter... It all looks good to me. Damn, it must be a real hard brick.

When I plug the phone into my PC without the battery in the phone I get a red LED.

When I plug it in with the battery in, I get no LED, no screen/logo, ect. Nothing. Windows does detect a device called "QHSUSB_DLOAD". I got the Qualcomm driver and QPTS hoping that there would be something that I could do... maybe backup my friend's bootrom and put it on my phone... The COM11 port from the device is not detected, so even if I could figure out a way to do what I said, I have no way to do it. Could be a Windows 7 unsigned drivers issue, but I have tried 3 different solutions to that without knowing how the device should look in Device Manager if the driver is accepted.

Looked for other solutions...

Old thread, HTC specific, not really any help... http://xdaforums.com/showthread.php?t=822939

Bad news, need to send device back... http://xdaforums.com/showthread.php?t=1651149

This looks possible, but I have not tried it yet because the steps are not that clear and it requires a Linux box, and I don't really want to dig into that can of worms right now. (which distro, which PC do I use, what software/packages are required, ect) http://xdaforums.com/showthread.php?t=1916796

Possible solution with linux box... http://xdaforums.com/showthread.php?t=2239451

Goes on to this one, a lot like the other linux option above... http://xdaforums.com/showthread.php?t=2369125

If I am missing anything, please let me know. Is this Linux option really a possibility? Do I need a Rogers bootloader?

Perhaps I can use this idea to get my friend to back his up for me off his Rogers S3: http://xdaforums.com/showthread.php?t=2374958

I could try the linux option tomorrow, or the JTAG tomorrow if I drive an hour away to a guy that can do it.