[AT&T Samsung Galaxy Note I717] darkspr1te:
Shared Memory Device , I wish hearing that would trigger some kind of solution in my head but i am non the wiser on what kind of data would be in there. I will fire up the hex reader and go through the corrupt data i have as no one has yet posted a copy of mmcblk0p1 (SMD_HDR)

On the USB/UART question i've done more reading and i am more confused but let me try and clarify.

When you use a Jig resistor of 301K on id pin the USB pins from the device communicate using the USB protocol and USB voltages.

If i use a Jig value of 150K then the USB Pins (D+ D-) now become TX/RX having being switched from the USB connections by the FSA9280A IC onboard, So now i would connect a TLL Serial adapter (FTDI, Arduino ) to the device on the USB pins, Now TX/RX.

REF: http://xdaforums.com/showpost.php?p=25532839&postcount=2

Your post, Thanks.

Is there a mode available that switches to the modem side of the system either using a USB based protocol (Windows picks up Samsung Modem Diagnostics COMx )

or using the TLL logic levels of the serial protocol?

REF:http://xdaforums.com/showpost.php?p=28047426&postcount=50

I Have tried 255K,301K,523K on my device, 255K boots to Factory mode( I got as low as 229K to trigger FM) and 301K also provides factory mode.

Both modes use USB via D+ D- of the micro-usb

523K powers up, no difference in operation, My Oscilloscope does not show any activity on the USB lines until it's connected to the USB port of a PC and 615K activates car mode.

I have avoided the values of resistors that clash, HDMI modes for example where +5V on the charge line could damage the device.

I am looking forward to your Anyway jig setup, in the meantime i will continue to research the header section of the device, i dont think it's coincidence that both tyler and my self loose IMEI and modem control on the loss of the SMD_HDR partition, i suspect it's possible the modem settings could sit there, a lot of other devices (A820 for example) write a file called NON-HLOS.BIN there but this seems to be the amss.mbn file that our devices require on mmcblk0p13.

I also found a file on the asian sites that is ment to be a complete Resurrection for a SH?-E120 device using a blank emmc, it does not contain smd_hdr file sadly but many others including the mmcblk0p21 partiton that our devices mount as EFS, i could share this if anyone thinks it may help. sadly i dont have the link to the original post, but should not be hard to find.

It also worth noting that this E120 file uses the MIUI phones flash program and NOT QPST?

One last things i want to just bring back to the thread i mentioned before,

This mentions a secondary flash, and early on in my research i did find another mention of the on a asian site that also mentioned a resistor connected on the ID pin allows you to flash (wire brush as it was translated ) this memory region but only once the device was in factory mode, i will look for that post again in the hope that my better understanding now will bring to light a solution, it concerns me that i may have erased this flash in my experiments, but i dont think Tyller has, the common factor of Tyller and I is that we both wrote data to mmcblk0p1, and we both had flashing failures.

Regards

darkspr1te

P.S Tyller , i am glad your device is alive, it's proof that we can fix these devices up to a certain point. Do you have the backup stiil? Can i post some scripts for you that will split your backup into it's components for me to scan for usable information ? I dont need data partitons or the like but i would like to try your rpm.mbn and sbl3.mbn on my device ( my script is just the opposite of the brixfix.sh script) in the hope i could compile a set of original files.