Pages: [1] 2
Author Topic: ECU keeps undoing immo defeat r32 7.1.1  (Read 9428 times)
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« on: April 21, 2018, 12:27:06 AM »

So i have been lurking and using the search function for a week now. I have flashed 30 or so different immo off bins to my 022906032eg with a 1024b 95080. Every time i flash it immo of with the hex edited at 12 and 22 set to 02 from 01 it will come back either 00 or 01 and the car will not start. I cannot figure out what i am doing wrong. Attached is the file i started with and what i thought was a good immo off from what i have read. Any help would be much appreciated.
Logged
prj
Hero Member
*****

Karma: +1072/-483
Offline Offline

Posts: 6039


« Reply #1 on: April 21, 2018, 01:08:48 AM »

Saturday morning blues Tongue
« Last Edit: April 21, 2018, 02:12:32 AM by prj » Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #2 on: April 21, 2018, 01:31:23 AM »

How come all the stickies say set them from one to two?

Look at your examples.

12 and 22 on the ON file are 01.
12 and 22 on the OFF file are 02.

That's the immobilizer. ON is 01. OFF is 02. Then, just correct the checksums. If you ADD to the page, SUBTRACT the number you added from the checksum of that page.

The checksums for those pages are at 2E and 3E.

So, say this is your setup:

        0   1   2   3   4   5   6   7   8    9   A   B   C   D   E   F
10 : XX XX 01 XX XX XX XX XX XX XX XX XX XX XX FE XX
20 : XX XX 01 XX XX XX XX XX XX XX XX XX XX XX FD XX

Is IMMO ON

You would change it to:

       0   1    2   3   4   5   6   7   8    9   A   B   C   D   E   F
10 : XX XX 02 XX XX XX XX XX XX XX XX XX XX XX FD XX
20 : XX XX 02 XX XX XX XX XX XX XX XX XX XX XX FC XX

which is IMMO OFF.
Logged
prj
Hero Member
*****

Karma: +1072/-483
Offline Offline

Posts: 6039


« Reply #3 on: April 21, 2018, 02:14:03 AM »

Sorry, wasn't fully awake yet.

The sticky is right.
But look at the files you posted, your 2nd file has a whole page replaced from some other file. Why would you do that?
You are supposed to edit your file...

Usually it means incrementing 12 and 22 by 1 and decrementing 1E and 2E by 1.
In this case you can set 12 and 22 to 2 and decrement 1E and 2E by 2 (as it's 0 stock).

You should not be changing anything else.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #4 on: April 21, 2018, 07:55:08 AM »

After I flash it to the ecu, it comes out different. If I start with xyz bin it comes out with values changed. I flashed a 1k file where the second half is all ff and it came out full of numbers. Im lost unless the files are not actually flashing but just saying that they did. One thing I didn't do was compare the read bins entirely, I just looked that the immo was always 1 and not 2 when I pulled them back off. So my problem is, I set immo from 1 to 2, fix checksum, flash, read the ecu after flash, immo is still set to 1. Could this be because there is a tune on the ecu?
Logged
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #5 on: April 21, 2018, 07:59:38 AM »

Sorry, wasn't fully awake yet.

The sticky is right.
But look at the files you posted, your 2nd file has a whole page replaced from some other file. Why would you do that?
You are supposed to edit your file...

Usually it means incrementing 12 and 22 by 1 and decrementing 1E and 2E by 1.
In this case you can set 12 and 22 to 2 and decrement 1E and 2E by 2 (as it's 0 stock).

You should not be changing anything else.

Also to address why the whole page is changed is because I worked on this from 4pm to 3am lol. I was trying anything at that point to see if it would stay changed. Flashing other 1k bins, editing mine, editing others absolutely nothing worked. But I still have my original bin which is what posted! I really appreciate your help with this by the way.
Logged
prj
Hero Member
*****

Karma: +1072/-483
Offline Offline

Posts: 6039


« Reply #6 on: April 21, 2018, 08:04:13 AM »

So flash the stock eeprom and read it back...
If that comes out the same, then flash one with only the modifications I said.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #7 on: April 21, 2018, 09:29:12 AM »

Ok, so i am attaching 3 files

File 1, this was in the ecu when i woke up this morning for a comparison of what comes out.

File 2, this is my original bin read that i first took and made the edits you said to at 12, 22, 1e and 2e, i flashed this today. This should have turned the immo off.

File 3, this is a read taken right after i flashed file 2, no changes were made to this after reading and no files were flashed between 2 and 3. Here you can see the immo reset back to 00 when i read it
Logged
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #8 on: April 21, 2018, 02:22:08 PM »

Cant use nefmoto either.

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have not been met.
Reasons preconditions failed:
-Immobilizer not authenticated
Continuing despite programming session preconditions not being met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Starting diagnostic session.
Unable to properly start diagnostic session, attempting to continue with current undefined session.
This can occur if the security lockout is running, or the engine is running. Please turn off the ignition and retry if this continues to fail.
Negotiating communication timings.
Too many consecutive unsolicited messages from ECU, disconnecting.
Disconnecting...
Reading ECU flash memory failed.
Disconnecting because no response was received for the Stop Communication message.
Disconnected
100% complete.
Restoring Windows sleep mode.
Logged
prj
Hero Member
*****

Karma: +1072/-483
Offline Offline

Posts: 6039


« Reply #9 on: April 21, 2018, 04:07:05 PM »

Post exact command line you are using to read and write, just looked at your files and they don't look right.
It's double stacked, I think you have the wrong memory type selected in boot, and you just overwrite the memory twice with the same.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #10 on: April 21, 2018, 09:44:33 PM »

First looks stacked 4x
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #11 on: April 21, 2018, 09:54:20 PM »

I use

--bootmode 95080 -b 9600 -p 3 -r xx.bin

--bootmode 95080 -b 9600 -wp3 xx.bin

I drove 4.5 hours round trip today to have the UM tune removed and immo defeated with no such luck, i emailed my tuner and hope he has some advice in the morning. I have deathcode 33 in the same line as the immo off. All i did was pull him eeprom to take a look, i dont want to mess it up but if you have any advice i would gladly accept it! 

Attached is the bin i pulled after getting home with the P0601

Logged
prj
Hero Member
*****

Karma: +1072/-483
Offline Offline

Posts: 6039


« Reply #12 on: April 22, 2018, 01:01:21 AM »

Are you sure it's a 95080? Smiley
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
aleckerchner
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #13 on: April 22, 2018, 01:01:43 AM »

I revisited the mem type i was using and you are in fact right. It was wrong, i needed to be using 95P08 and i was not. Thank you for helping me get in the right direction! I was able to flash an immo off file i had worked on the other night and it worked. Im not sure if my tuner getting a stock tune on the ecu helped me be able to flash it but i am able to flash EEPROMS that matter now, i flashed an immo on file and it died after starting, i flashed an immo off following that and it worked as well!
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #14 on: April 22, 2018, 07:57:31 PM »

So i have been lurking and using the search function for a week now. I have flashed 30 or so different immo off bins to my 022906032eg with a 1024b 95080. Every time i flash it immo of with the hex edited at 12 and 22 set to 02 from 01 it will come back either 00 or 01 and the car will not start. I cannot figure out what i am doing wrong. Attached is the file i started with and what i thought was a good immo off from what i have read. Any help would be much appreciated.
read eeprom dump is faulty repeat the eeprom reading
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 17 queries. (Pretty URLs adds 0s, 0q)