[AT&T Samsung Galaxy Note I717] nitus_77:
Hi. Hopefully not too late for some advice. The situation with my phone is similar, so perhaps some advice may be useful.

SGH-T989D, the Koodo Galaxy SII X. Identical to the Telus version (koodo is owned by Telus, their 'value' carrier) and the T-Mobile Hercules. Started with stock Koodo rom and though I am on Mobilicity (AWS band) I didn't have any issues while using stock. Later I flashed to CM 10.2, which I liked, but noticed network issues - slow to connect, low bandwidth, etc. Still livable once it was on the network, but of course I had to play with it.

Found the default AOSP "4636" menu and played with radio settings. Lost the network. Couldn't get it back. I then realized that CM wipes out all the samsung debug menus that allow you to fine tune your radio band, and couldn't get the samsung apks to run properly. It had not altered the settings that were there in stock until I did it myself, but it couldn't set it back.

I had noticed while on stock that the T-Mobile, Telus, and Koodo firmwares were interchangeable - I had tried all of the radio firmwares at one time or another. I reasoned that since T-Mobile uses AWS and Telus doesn't, I might get some improvement if I flashed to the stock T-Mobile rom, latest radio, tweaked the radio settings, then flashed back to CM. I think it probably would have worked.

Except: the odin version I downloaded came with a PIT file. I assumed it was the one for T989, as I had downloaded an odin zip specifically labelled as such. It wasn't. I knew right away that something was wrong, but all was not yet lost - the phone was still in download mode, still responding to odin. I spent the next hour growing increasing frustrated as I couldn't find the proper PIT and if it didn't need it before it sure did then. Then I made a fatal mistake - I said, "ah, screw it. I'll give my brain a rest and try later." Unplugged the usb cable.

All she wrote. Hard brick. identified as QHUSB_DLOAD in windows, and Qualcomm Gobi in lubuntu.

After a lot of searching, I discovered that the Miflash tool was able to flash the phone. Only problem was, couldn't find the images to flash with.

I feel that there is a solution, if only I knew what to flash with what, but I am a newb to this sort of thing (although in the last two weeks I have learned more than I ever thought I would). I have bookmarked all of the related threads to this subject, and there is a wealth of information to pore over, in the hopes that I might be able to adapt some of your methods or steps.

Qualcomm APQ8060 Snapdragon, Dual-core 1.5 GHz Scorpion, 16 gb internal SD. Still a very solid phone, and would love to recover it, but it retails for only $150 new from Koodo (less elsewhere) and the local jtag guy wants $80. I was going to pick up a 16 gb external sd and see if the clone-sd recovery method used for the s3s would work, but any advice at all would be very helpful.

I think it's awesome the amount of effort you guys put in pro-bono, and I hope you don't burn out on all the thoughtless, thankless, or witless begging and demands from those of us who are completely ignorant on the subject. It's encouraging that you were able to find solutions to a broadly similar situation, and it confirms in my mind that there is one without jtag, if I only knew what it was.