[AT&T Samsung Galaxy Note I717] darkspr1te:
The Tainted data is because the first time i was able to access the emmc was by using QPST/emmswdownload to write a new boot sector + boot chain to the emmc (8660_msimage.mbn) from there i dd'ed the entire emmc to a file on my nas drive. i then copied that file locally to work on so there was never a chance to corrupt the original, I have worked on the copy since.

On the windows/drivers side of things.

1. USB = PDA / UART = MODEM - windows driver pid/vid is 04e8:6860, One USB Samsug Modem and one samsung USB serial port, samsung CDC driver and SHV-E160 MTP

2. USB = MODEM / UART = MODEM - windows driver pid/vid is 04e8:685e, Two USB Samsung modems, Two USB Serial Ports, Samsung CDC driver and SHV-E160 MTP

RMNET driver loads fine then has yellow exclamation mark after a minute in all configs.

Kies installed first, for ODIN, then QPST. I have not swapped drivers out for the ones you provided on your Anyway link as non of the PID/VID's have matched, Kies will not see the device as the SHV-E160L is listed in it's incompatible.ini list which i found just now.

I also have not tried adding the VID/PID to current .inf files for diagnostics.

The actual pid vid reported by windows :-

USB = MODEM / UART = PDA

USB\VID_04E8&PID_685E&DIAGSERD\6&36A5EDB5&0&0006

USB = PDA / UART = MODEM

USB\VID_04E8&PID_6860&MODEM\6&3759C3D4&0&0001

I've attached a screen shot for you.

None of the programs connect in any of the above configurations, once i reflash the bootloaders and boot into android i can no longer use QPST tools or simlar( that i am aware of)

The machine is virtual running on Ubuntu, tests on a windows desktop ad random points have produced no comms. Only com ports listed are USB pass-through from ubuntu, i have not yet had a reason to distrust this as all prior work (QPST etc) has worked in this configuration.

Currently working on some scripts/bat files to make it easier for the users. i am assuming most will not want to download a ubuntu live CD just to run my scripts so I will do a windows based batch file first and test via my device before i put it out. It does delay me getting my hands on info but i want to also make this a form of backup for the user and not brick their device either. So it will be double/triple check my commands, :D

my original script and bootloaders used RPM/SBL3 from shv-e120l, it was my assumption that the fact it was also L model from same telecom provider that the certs would be the same, using all i717 files and my original aboot.mbn how ever makes the odin counter work and also all my soft touch button light up and vibrate works which it does not do using the files from the E120.

I happy to test any theories out you may have on mix/matching the boot loaders as i can reset back any time if i brick.

Right now i get the feeling that i am not talking to the CP, either the CP has a chain of trust I have broken , damaged configuration or failure to fully boot.

Why am i thinking this?

1. All the dialer codes related to gsm either do not produce feedback or dont work but all LTE based ones do.

2. none of the diagnostics pathways that talk to the CP seem to produce any feedback

3. OS reports baseband unknown in every tool i've tried.

What disproves the above:

1. Bluetooth works

2. WLAN works

3. NFC diag works, i dont have a nfc device to test but i do have a arduino i could repurpose

I still also suspect that my partition table is still not correct hence I have not extracted real copies of the various partitons in a raw format. I will sit down at my windows desktop tonight and start on reconfirming that

only machine with enough ram for the 16GB dump and it's fast for searching for the hex bytes.

The current partition table is based on a ODIN re-partition which is the partition0.mbn file contained in my first brixfix post.

I have just discovered that fdisk on ubuntu accept -H Heads -C Cylinder -S Sectors , so now i can take a copy of the original dump and fix the partition table within the dump, cross check that with my hex editor on windows , for the first few partitions is easy (except the smd_hdr parition ) as i have similar files and the have headers that are exactly the same between devices. Footers are different, the i717 .mbn files have what looks like a samsung Cert on the end, the extracted E160 .mbn and E120 mbn files do not have this addition.

but i can boot i717, 160l, e120l aboot.mbn using i717 primary chain. the only effect of swapping the aboot is :-

1. i717 aboot.mbn wont accept any files apart from a pda file with recovery partition of main firmware, all produce errors. non of the vibe based operations occur, lower soft touch lights remain off, baseband unknown, pit file produce a error : Secure Check Fail PIT

2. odin says passed OK flashing bootloaders but aboot.mbn will remain e160l version. will accept almost any version of PDA flash i do.

3.E120L bootloader is setup for a different screen so it's messed up on this device, booting gingerbread already insatlled works but odin will fail in any attempts to reflash anything.

Some sniffing around i found this, i am itching to try vanilla surf bootloaders, what do you advise?

The structure is larger than below, i posted only link i wanted to highlight.

http://files.epos-ps.com/noamd/Qualcomm/Releases/022/

http://files.epos-ps.com/noamd/Qualcomm/Releases/M8960AAAAANLGD172025.1/

http://files.epos-ps.com/noamd/Qualcomm/Releases/usb_drivers/host/windows/prebuilt/

Finally, Sorry if i am bouncing around a bit, there is method to my madness, only i can see it thought :p

2. e160