Grabbing life by the horns.
My man! Lol

Nefmoto is officially installed. Working on the driver for the cable

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 'B0907551AL 2.71 V6/5VT
G 000104A
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Sending start communication request.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
Reading ECU identification option: calibrationEquipmentSoftwareNumber
Read ECU identification option with unknown scaling record.
Successfully read CU identification information
ECU reports programming session preconditions have not been met.
Reasons preconditions failed:
-Immobilizer not authenticated
Continuing despite programming session preconditions not being met.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Start diagnostic session failed, ECU reports conditions not correct or sequence error. This can oc 100% complete.
Reading ECU flash memory failed.
Too many consecutive unsolicited messages from CU, disconnecting.
Disconnecting...
Disconnected
Restoring Windows sleep mode.

You are getting your information mixxed up, the info that you are reading is about a command line program and is not directly related to nefmoto flasher. Nefmoto flasher has known bugs immo authentication is one of them and  I'm about 90% sure that disabling the immo will only make the problem worse for port flashing. Your best bet in my opinion is to fork up more then like $15 bucks and get a decent cable like mpps v16 as that has bootmode flash built in. You CAN use your blue cable for boot mode but it involves reflashing the cable with mprog to change the serial number to use with galletto, or patch galletto software with the serial number that's in your current cable. Flashing the calibration file (eprom) is not the same as flashing the 95040 immo (eeprom). Argdub made a command line tool to flash the eeprom and really has nothing to do with the calibration file. Flashing the calibration file can be done thru the port or on the bench in bootmode. While grounding a pin on the ecu it will boot up in programming mode, it requires specific software and nefmoto does not support bootmode. Also, I just want to point out that you may want to get yourself familiar with bootmode flashing as you are 1 incomplete read, one dead battery, one crashed program, one mistakenly unplugged cable away from being stuck in program mode or with a bricked ecu.        

Forgive this post. I’ll Be surprised if my image comes up. Smh

this is a gui for eeprom flasher


http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1168.0;attach=32744

can someone walk me thru how to post my screenshot.... i am using the Gimp app, downloaded from the thread "how to take a screenshot".

i tried clicking the insert image button above and then copying my image and pasting it , but nothing.

Update....
TBH all of this is overwhelming... i gave up on the immobilizer ecu for now... the command terminal is way over my head..... also that ecu came from an auto car, so im sure ill have to mess with that... and im not totally sure which maf it has.... so ill come back to it....

I decided grab my ecu out of my car, and hooked it up to the bench, flashed it and saved the original file to my desktop... it took me a few hours but finally did a checksums on it!!!!! ( i was so fuckin  pumped)

 now more researching

I deeply appreciate the help guys!



 

ok so i back to the ecu with the immobilizer....
this was my attept in bootmode... this is the first step correct? where am i going wrong?
did i not get into bootmode? how are my entries into the command? you can see my adjustment in the second attempt. under my device manager it says my cable is set to port 3.... but also when i go to the advanced setting and try to set it to port 1 and hit ok... i dont see any changes?

    --bootmode MEM_TYPE   Use this option to program the EEPROM in boot mode.
                           Allowed memory types: [95040 | 95080 | 95160 | 95P08].
 -r, --read                Read EEPROM contents and save it to file.
 -w, --write               Write a file to EEPROM.
 -s, --screen              Displays EEPROM contents on the screen.
     --CSpin               Set the CPU chip select (CS) output. eg: P4.7
                           The following table shows all available ports with
                           its corresponding physical address.
                              Port   PortReg   DirControlReg
                              P2     0xFFC0    0xFFC2
                              P3     0xFFC4    0xFFC6
                              P4     0xFFC8    0xFFCA
                              P6     0xFFCC    0xFFCE
                              P7     0xFFD0    0xFFD2
                              P8     0xFFD4    0xFFD6
     --help                Display this help and exit.

Usage example:
   Read EEPROM over OBD port:         $ ME7_EEPROM --OBD -r -p 1 95040.bin
   Print EEPROM contents to srcreen:  $ ME7_EEPROM --OBD -p1 --screen
   Write file to EEPROM in bootmode:  $ ME7_EEPROM --bootmode 95040 -wp1 95040.bin

It's free for hobby use.
This software is provided "as is", with NO WARRANTY.
email: agv.tuning@gmail.com

C:\Users\Matt\Desktop> ME7_EEPROM --bootmode -r -p 3  95040.bin
'ME7_EEPROM' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Matt\Desktop>ME7_EEPROM --OBD --bootmode -r -p 1  95040.bin
'ME7_EEPROM' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Matt\Desktop>