Pages: 1 ... 11 12 [13] 14 15
Author Topic: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc  (Read 230210 times)
mdccode5150
Full Member
***

Karma: +13/-4
Offline Offline

Posts: 122


« Reply #180 on: November 05, 2020, 11:36:56 PM »

Did I miss something? or this program only does 512 EEPROM Files?

This is what I get:

C:\>eepromtool_04.exe ecu.bin
Read in 1024bytes
Found 1024b bin - parsing as a R32 bin - experimental
ERROR: 1024byte file detected, but the last 512bytes are not all padded with 0xFF, this file is may be a corupt dump, a cluster dump or something other than an eeprom dump, open it with a hex editor - if this is a valid eeprom please post the file and vehicle info on the thread for this tool
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo3
- VIN: WVGBC67L74D009484
- SKC: 05166
- Immobiliser: On
- Checksum: Invalid Checksum
- Size: 1024bytes - 512bytes expected, check this is a eeprom bin
- Cluster Code: EE 7A 20 4B 57 1C 1B
- P0601 DTC: not set
- Immo ID: VWZ3Z0C5075067
- Softcoding ID: 0133
- Tuner Tag: Not Set
- Flash Programming (successful): 2
- Flash Programming (attempts): 2


C:\>


Logged
mdccode5150
Full Member
***

Karma: +13/-4
Offline Offline

Posts: 122


« Reply #181 on: November 05, 2020, 11:38:07 PM »

Sorry here is the file
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #182 on: November 12, 2020, 06:16:53 PM »

Sorry here is the file
what should i do including eeprom
Logged
mdccode5150
Full Member
***

Karma: +13/-4
Offline Offline

Posts: 122


« Reply #183 on: November 22, 2020, 11:17:50 PM »

I just wanted to know (at the time) if the EEPROM dump would work...But I found that it changed a lot more than the immo due to it being a 1024 size. I ended up just taking the immo, and checksum values from the generated dump and manually edited the original file.

Thanks
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #184 on: November 23, 2020, 10:25:23 AM »

I just wanted to know (at the time) if the EEPROM dump would work...But I found that it changed a lot more than the immo due to it being a 1024 size. I ended up just taking the immo, and checksum values from the generated dump and manually edited the original file.

Thanks
that is, I understand
that you did it yourself
and you don't need any help anymore
Logged
Micaaacek
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 9


« Reply #185 on: December 08, 2020, 01:33:44 PM »

Hello All,

can I use this program to change VIN, SKC, Cluster code and Immo ID in ECU bin file ? I have similar problem as user "stranger_in_distress". I want to use AUQ ECU with AUM engine with Immo ON. I read that stranger_in_distress solved it, but its almost 6 years ago.

I succesfully changed VIN in eeprom file via this program but change of SKC, Cluster code and Immo ID is not possible  Undecided

Do I something wrong ? Because command line shows "Not Yet Supported for ECU Bins".


C:\>e2t.exe
usage: e2t.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO]
               [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR]
               [--fixcs] [--nofixcs] [--cluster] [--force]
e2t.exe: error: argument --in is required

C:\>e2t.exe --in HN.bin --vin TMBBL21U838684718 --out HN_VIN.bin
Read in 512bytes
Setting VIN to TMBBL21U838684718
- Setting backup pages
- Correcting checksums

- Write Successful

C:\>e2t.exe --in HN_VIN.bin --skc 00679 --out HN_VIN_SKC.bin
Read in 512bytes
Not Yet Supported for ECU Bins
Traceback (most recent call last):
  File "eepromtool_04.py", line 794, in <module>
  File "eepromtool_04.py", line 769, in main
AttributeError: ecueeprom instance has no attribute 'setSKC'
[4452] Failed to execute script eepromtool_04







Thanks.
« Last Edit: December 08, 2020, 02:49:12 PM by Micaaacek » Logged
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420


« Reply #186 on: December 09, 2020, 09:09:15 AM »

Hello All,

can I use this program to change VIN, SKC, Cluster code and Immo ID in ECU bin file ? I have similar problem as user "stranger_in_distress". I want to use AUQ ECU with AUM engine with Immo ON. I read that stranger_in_distress solved it, but its almost 6 years ago.

I succesfully changed VIN in eeprom file via this program but change of SKC, Cluster code and Immo ID is not possible  Undecided

Do I something wrong ? Because command line shows "Not Yet Supported for ECU Bins".


C:\>e2t.exe
usage: e2t.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO]
               [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR]
               [--fixcs] [--nofixcs] [--cluster] [--force]
e2t.exe: error: argument --in is required

C:\>e2t.exe --in HN.bin --vin TMBBL21U838684718 --out HN_VIN.bin
Read in 512bytes
Setting VIN to TMBBL21U838684718
- Setting backup pages
- Correcting checksums

- Write Successful

C:\>e2t.exe --in HN_VIN.bin --skc 00679 --out HN_VIN_SKC.bin
Read in 512bytes
Not Yet Supported for ECU Bins
Traceback (most recent call last):
  File "eepromtool_04.py", line 794, in <module>
  File "eepromtool_04.py", line 769, in main
AttributeError: ecueeprom instance has no attribute 'setSKC'
[4452] Failed to execute script eepromtool_04







Thanks.

You can or PM me and ill update it for you!
Logged
Micaaacek
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 9


« Reply #187 on: December 09, 2020, 01:27:25 PM »

You can or PM me and ill update it for you!

Thank you for offer, but fortunately it has been fixed. I found program "VisualME7Logger" and this cool software did what i needed to do.

After that ECU works fine in car without any problem and I hope so.
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12270


WWW
« Reply #188 on: December 09, 2020, 01:28:45 PM »

Thank you for offer, but fortunately it has been fixed. I found program "VisualME7Logger" and this cool software did what i needed to do.

After that ECU works fine in car without any problem and I hope so.

? how did that fix immo?
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
Micaaacek
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 9


« Reply #189 on: December 09, 2020, 02:19:10 PM »

? how did that fix immo?

Immo is ON and works.

Here is what I did:

1) Downloaded E2prom from HJ ECU (AUM) and from HN ECU (AUQ)

2) Opened HJ E2prom in VisualME7Logger and copy VIN, SKZ, Immo PIN and Cluster code to notepad

3) Opened HN E2prom in VisualME7Logger and replace VIN, SKZ, Immo PIN and Cluster code by data from HJ (notepad)

4) Saved updated E2prom with checksum routine

5) Flashed to ECU and installed ECU to car


I dont know if this is correct procedure, but it works without any DTCs and I have tried more than 20 starts of engine, I drove more than 50 km and its still OK.




 
 


Logged
d3irb
Full Member
***

Karma: +134/-1
Offline Offline

Posts: 195


« Reply #190 on: December 09, 2020, 02:42:58 PM »

? how did that fix immo?

visualme7logger actually has an EEPROM tool in it, blew my mind too: https://github.com/sbloom82/VisualME7Logger/blob/master/VisualME7Logger.Output/EEPROM.cs
Logged
Micaaacek
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 9


« Reply #191 on: December 12, 2020, 02:34:00 PM »

During testing I found small bug. When I tried to pair Skoda's cluster and ECU bin I found that this SW only accept Immo ID with 13 characters. Skoda uses IMMO ID with 14 characters.

Can anyone confirm this ?

C:\>e2.exe --in cluster.bin --out cluster_paired.bin --pair ecu.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
Read in 512bytes
Setting VIN to TMBUR41U038686255
Setting Immo ID to SKZ7Z0B1704024
Setting SKC to 00648

Cluster updated to:
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402

Writing 2048kb cluster eeprom bin to: cluster_paired.bin
- Write Successful

This tool cannot set checksum for cluster bins, so you must force the cluster to reset the checksum by using VCDS to update the cluster softcoding (setting it to the same value will force the update)

C:\>e2.exe --in cluster_paired.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #192 on: December 12, 2020, 06:40:05 PM »

During testing I found small bug. When I tried to pair Skoda's cluster and ECU bin I found that this SW only accept Immo ID with 13 characters. Skoda uses IMMO ID with 14 characters.

Can anyone confirm this ?

C:\>e2.exe --in cluster.bin --out cluster_paired.bin --pair ecu.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
Read in 512bytes
Setting VIN to TMBUR41U038686255
Setting Immo ID to SKZ7Z0B1704024
Setting SKC to 00648

Cluster updated to:
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402

Writing 2048kb cluster eeprom bin to: cluster_paired.bin
- Write Successful

This tool cannot set checksum for cluster bins, so you must force the cluster to reset the checksum by using VCDS to update the cluster softcoding (setting it to the same value will force the update)

C:\>e2.exe --in cluster_paired.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402
I think of the VW group always uses the ID of 14 characters
Logged
Micaaacek
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 9


« Reply #193 on: December 13, 2020, 03:22:17 AM »

I think of the VW group always uses the ID of 14 characters

On the first page of this topic are some examples with Audi and there is only 13 characters in Immo ID. However I have tried to open updated bin of cluster in another SW and it seems that Immo ID has 14 characters.

It looks like its only display bug.
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #194 on: December 13, 2020, 03:54:20 PM »

On the first page of this topic are some examples with Audi and there is only 13 characters in Immo ID. However I have tried to open updated bin of cluster in another SW and it seems that Immo ID has 14 characters.

It looks like its only display bug.
Yes
when it comes to ECU EEPROM 95040
This program has a bug
Logged
Pages: 1 ... 11 12 [13] 14 15
  Print  
 
Jump to:  

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