Pages: [1]
Author Topic: MED9.1 Bench flashing - Did a search  (Read 9202 times)
jastr
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 56


« on: December 11, 2017, 02:34:35 PM »

So from what i can see when i search in here. MED9.1 bench flashing is not allowed if the ecu is not immo off. So i got the ECU immo off and i am trying to read it on the bench with a home made bench cable according to the pin out available everywhere. I can communicate with the ECU using VCDS having a lot of errors ofcause however trying with CMD it says key not present. I did a immo off using eeprom tool 2.0 and it has worked a ton of times.

Here is the log from CMD

VOLKSWAGEN
GOLF V
2.0 GTI TFSI EDITION 30 169KW MED9 CAN
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
Identification
++++++++++++++++++++++
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
CANBUS
Voltage: 11,8 V.
Wait...
SW: 1037383925
HW: 0261S02429
VAG: 1K0907115L
INFO: 00102.0l R4/4V TFSI
Total time: 00:00:06 sec.
OK

++++++++++++++++++++++
Read
++++++++++++++++++++++
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
CANBUS
C:\Documents and Settings\CPH Motorsport\Dokumenter\Downloads\Jacob Golf ED30 Virgin
Voltage: 11,8 V.
Wait...
 
Error: 80 F1 10 03 7F 27 35 01
Description: invalidKey
 
Possible Solutions:
-Press HELP button
-Wrong protocol, please check ecu model
 
Total time: 00:00:06 sec.
 
-Dashboard key OFF
-Wait 20 sec.
-Dashboard key ON
-Try again
-In the case of repeated failures, take note of the hex. error codes and contact the technical support
 
FAILED
Send errors report to CMD technical support
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #1 on: December 11, 2017, 07:21:59 PM »

So from what i can see when i search in here. MED9.1 bench flashing is not allowed if the ecu is not immo off. So i got the ECU immo off and i am trying to read it on the bench with a home made bench cable according to the pin out available everywhere. I can communicate with the ECU using VCDS having a lot of errors ofcause however trying with CMD it says key not present. I did a immo off using eeprom tool 2.0 and it has worked a ton of times.

Here is the log from CMD

VOLKSWAGEN
GOLF V
2.0 GTI TFSI EDITION 30 169KW MED9 CAN
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
Identification
++++++++++++++++++++++
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
CANBUS
Voltage: 11,8 V.
Wait...
SW: 1037383925
HW: 0261S02429
VAG: 1K0907115L
INFO: 00102.0l R4/4V TFSI
Total time: 00:00:06 sec.
OK

++++++++++++++++++++++
Read
++++++++++++++++++++++
BOSCH MED9.1 VAG CAN
++++++++++++++++++++++
CANBUS
C:\Documents and Settings\CPH Motorsport\Dokumenter\Downloads\Jacob Golf ED30 Virgin
Voltage: 11,8 V.
Wait...
 
Error: 80 F1 10 03 7F 27 35 01
Description: invalidKey
 
Possible Solutions:
-Press HELP button
-Wrong protocol, please check ecu model
 
Total time: 00:00:06 sec.
 
-Dashboard key OFF
-Wait 20 sec.
-Dashboard key ON
-Try again
-In the case of repeated failures, take note of the hex. error codes and contact the technical support
 
FAILED
Send errors report to CMD technical support


If the ECU is out, why not BDM?
Logged
superglitch
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 45


« Reply #2 on: December 13, 2017, 11:54:47 AM »

ECU more than likely has read protection on it, this is why CMD would get invalid key back.

Flash this SGO on it using CMD tool: http://odise.3110110.com/vw/1K0907115L__0030.sgo

Then you should be able to read out.
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #3 on: December 14, 2017, 03:05:23 AM »

ECU more than likely has read protection on it, this is why CMD would get invalid key back.

Flash this SGO on it using CMD tool: http://odise.3110110.com/vw/1K0907115L__0030.sgo

Then you should be able to read out.

There is no protection via BDM. It's processor level flash access. You can only disable BDM by physically destroying the BDM circuitry.
Logged
superglitch
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 45


« Reply #4 on: December 14, 2017, 12:01:07 PM »

There is no protection via BDM. It's processor level flash access. You can only disable BDM by physically destroying the BDM circuitry.

I meant for OBD read.  It sounds like he is developing a protocol since he was able to write IMMO off.
« Last Edit: December 14, 2017, 12:03:38 PM by superglitch » Logged
jastr
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 56


« Reply #5 on: December 14, 2017, 10:20:29 PM »

Hmm that sgo should be Virgin? Or will it keep immo data if i flash some other ecu with this flash file?
Logged
eliotroyano
Hero Member
*****

Karma: +47/-7
Offline Offline

Posts: 796


« Reply #6 on: December 15, 2017, 06:02:33 PM »

I do not think you can flash an SGO file through OBD port on bench. It will not touch immo data but anyway I think that flash conditions are not met
Logged
jastr
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 56


« Reply #7 on: December 16, 2017, 12:12:36 AM »

I do not think you can flash an SGO file through OBD port on bench. It will not touch immo data but anyway I think that flash conditions are not met

Hmm maybe with vcp. It almost call for a test.
Logged
superglitch
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 45


« Reply #8 on: December 17, 2017, 08:55:50 PM »

You cannot write over IMMO data with OBD flashing.

With MED9 IMMO Off in E2P you can write on bench via OBD, you cannot start programming session if immobilizer is active.
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #9 on: December 17, 2017, 11:22:13 PM »

You cannot write over IMMO data with OBD flashing.

With MED9 IMMO Off in E2P you can write on bench via OBD

Can you say what tool does this?
Logged

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

Karma: +0/-0
Offline Offline

Posts: 56


« Reply #10 on: December 17, 2017, 11:45:52 PM »

Can you say what tool does this?
Eeprom tool 2.1.1
Logged
Pages: [1]
  Print  
 
Jump to:  

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