[AT&T Samsung Galaxy Note I717] nathanlewan:
Hello again,

Thanks again for the info. I have tried it, and here's the good stuff:

step 1: pulled battery out to make sure phone was completely off.

step 2: put battery back in, and connected to computer.

lsusb reports:

Bus 002 Device 028: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

dmesg reports:

[75649.587078] usb 2-1.7: new high-speed USB device number 28 using ehci_hcd
[75649.679928] usb 2-1.7: New USB device found, idVendor=05c6, idProduct=9008
[75649.679931] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[75649.679933] usb 2-1.7: Product: QHSUSB_DLOAD
[75649.679934] usb 2-1.7: Manufacturer: Qualcomm CDMA Technologies MSM
[75649.680337] qcserial 2-1.7:1.0: Qualcomm USB modem converter detected
[75649.680431] usb 2-1.7: Qualcomm USB modem converter now attached to ttyUSB0

step 3: I git cloned the repo into the same folder where the hex bin files are, and removed the two older versions.

step 4: I ran this:

root@nlewan-deb:/home/nlewan/Videos/msm8960# perl qdload.pl

output was this on the console:

Using TTY: /dev/ttyUSB0
Sending MAGIC...
Got magic response: 03 00 03
Requesting SoftwareVersion...
sent 0c
received something
Version: PBL_DloadVER2.0
Requesting Bootloader..........
Response: 03 00 06
Requesting Param...
requestParam send ok
Param: 08 08 01 06 00 90 00 00
Sent 0x16
got back something
Uploding file...
<edit>Writing 1024 bytes to 0x2a000000; ***** bytes left.</edit>
Executing file...
Unable to receive response
Using TTY: /dev/ttyUSB0
Sending MAGIC2...
Got response: 03 00 03
Sending secureMode...
secureMode send ok
Response: 17 00 40 00 00 00 00 e1 50 6b 00
Sending openMulti ...
openMulti send ok
Response: 03 00 06
<edit>Writing 1024 bytes to 0x00000000; ***** bytes left.</edit>
Writing 1024 bytes to 0x00188000; 0 bytes left.
Got response: 08 08 01 06 00 90 00 00
Got response: 08 08 01 06 00 90 00 00
Sending CloseFlush...
closeFlush send ok
Response: 03 00 06
Requesting Reset...
doReset send ok
Response: 03 00 06

dmesg reports:

[75942.406812] usb 2-1.7: USB disconnect, device number 28
[75942.406959] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[75942.406972] qcserial 2-1.7:1.0: device disconnected
[75942.606390] usb 2-1.7: new high-speed USB device number 29 using ehci_hcd
[75942.699245] usb 2-1.7: New USB device found, idVendor=05c6, idProduct=9008
[75942.699248] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[75942.699250] usb 2-1.7: Product: QHSUSB_DLOAD
[75942.699252] usb 2-1.7: Manufacturer: Qualcomm CDMA Technologies MSM
[75942.699537] qcserial 2-1.7:1.0: Qualcomm USB modem converter detected
[75942.699619] usb 2-1.7: Qualcomm USB modem converter now attached to ttyUSB0

lsusb reports:

Bus 002 Device 029: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

/var/log/messages reports:

Jan 11 13:44:45 nlewan-deb kernel: [75942.606390] usb 2-1.7: new high-speed USB device number 29 using ehci_hcd
Jan 11 13:44:45 nlewan-deb kernel: [75942.699245] usb 2-1.7: New USB device found, idVendor=05c6, idProduct=9008
Jan 11 13:44:45 nlewan-deb kernel: [75942.699248] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 11 13:44:45 nlewan-deb kernel: [75942.699250] usb 2-1.7: Product: QHSUSB_DLOAD
Jan 11 13:44:45 nlewan-deb kernel: [75942.699252] usb 2-1.7: Manufacturer: Qualcomm CDMA Technologies MSM
Jan 11 13:44:45 nlewan-deb kernel: [75942.699537] qcserial 2-1.7:1.0: Qualcomm USB modem converter detected
Jan 11 13:44:45 nlewan-deb kernel: [75942.699619] usb 2-1.7: Qualcomm USB modem converter now attached to ttyUSB0
Jan 11 13:44:45 nlewan-deb mtp-probe: checking bus 2, device 29: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7"
Jan 11 13:44:45 nlewan-deb mtp-probe: bus: 2, device: 29 was not an MTP device

if I cd to /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7:

root@nlewan-deb:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7# ls -l
total 0
drwxr-xr-x 6 root root 0 Jan 11 13:44 2-1.7:1.0
-rw-r--r-- 1 root root 4096 Jan 11 14:00 authorized
-rw-r--r-- 1 root root 4096 Jan 11 14:00 avoid_reset_quirk
-r--r--r-- 1 root root 4096 Jan 11 13:44 bcdDevice
-rw-r--r-- 1 root root 4096 Jan 11 14:00 bConfigurationValue
-r--r--r-- 1 root root 4096 Jan 11 13:44 bDeviceClass
-r--r--r-- 1 root root 4096 Jan 11 13:44 bDeviceProtocol
-r--r--r-- 1 root root 4096 Jan 11 13:44 bDeviceSubClass
-r--r--r-- 1 root root 4096 Jan 11 14:00 bmAttributes
-r--r--r-- 1 root root 4096 Jan 11 14:00 bMaxPacketSize0
-r--r--r-- 1 root root 4096 Jan 11 14:00 bMaxPower
-r--r--r-- 1 root root 4096 Jan 11 13:44 bNumConfigurations
-r--r--r-- 1 root root 4096 Jan 11 14:00 bNumInterfaces
-r--r--r-- 1 root root 4096 Jan 11 13:44 busnum
-r--r--r-- 1 root root 4096 Jan 11 14:00 configuration
-r--r--r-- 1 root root 65553 Jan 11 13:44 descriptors
-r--r--r-- 1 root root 4096 Jan 11 14:00 dev
-r--r--r-- 1 root root 4096 Jan 11 13:44 devnum
-r--r--r-- 1 root root 4096 Jan 11 14:00 devpath
lrwxrwxrwx 1 root root 0 Jan 11 13:44 driver -> ../../../../../../bus/usb/drivers/usb
drwxr-xr-x 3 root root 0 Jan 11 14:00 ep_00
-r--r--r-- 1 root root 4096 Jan 11 13:44 idProduct
-r--r--r-- 1 root root 4096 Jan 11 13:44 idVendor
-r--r--r-- 1 root root 4096 Jan 11 13:44 manufacturer
-r--r--r-- 1 root root 4096 Jan 11 14:00 maxchild
drwxr-xr-x 2 root root 0 Jan 11 14:00 power
-r--r--r-- 1 root root 4096 Jan 11 13:44 product
-r--r--r-- 1 root root 4096 Jan 11 14:00 quirks
--w------- 1 root root 4096 Jan 11 14:00 remove
-r--r--r-- 1 root root 4096 Jan 11 13:44 speed
lrwxrwxrwx 1 root root 0 Jan 11 13:44 subsystem -> ../../../../../../bus/usb
-rw-r--r-- 1 root root 4096 Jan 11 13:44 uevent
-r--r--r-- 1 root root 4096 Jan 11 14:00 urbnum
-r--r--r-- 1 root root 4096 Jan 11 13:44 version

To be honest i'm not sure what i'm looking at in this directory, but I thought it might help.

This has been a very informative process, going through all this. If you wouldn't mind explaining what you think is going on here, I would love to hear your thought process. I realize it's a lot of typing though, so please don't do so just to satisfy my interest.

---------- Post added at 02:20 PM ---------- Previous post was at 02:09 PM ----------

Excellent!

So I need to create the hex2.bin file (which I imagine is an arbitrary name you selected, but not sure) to match the firmware that was on my phone prior to my massive brain-fart/brick? Ok, so I imagine i'm going to need to figure out a way to read the correct efuse to find my version number, and then grab the proper firmware from somewhere else. At least I think that's what I need to do :)

Thank you for your explanation, it's very helpful for me.