View The Full Version : Golf 5 2.0 TDI MED9.1 not let you read
cawadany
06-06-2013, 09:54
I have a problem with my car, a Golf 5 GTI 2.0 TFSI fitted with a MED9.1. I've always read and written safely, initially with powergate and then with mpps v5. A few days ago I connect mpps and I to read it: error "invalid key". Since the same mpps in the evening before I had blocked a edc16u31 (then recovery in recovery always with mpps), I think either the cable is defective and I buy a rooster v48. I plug in the cock, I start reading and.... error sk2, silentkey reading... it seems the same error of the mpps. At this point, I think that the problem is not the interface, but my ecu. What is pu? be successful according to you? C'? the way to resolve it? Of course I didn't trust to write......
danny677
06-06-2013, 15:52
with mpps put it in the reading, when you d? the error does not turn off the picture, but restart the mpps, after 2-3 attempts it should unlock and go read.
Also see if you can give a few tenths of a volt in + to the battery with a charger.
cawadany
06-06-2013, 16:07
From how I understand the ecu when the law of an access key is not valid blocks access to a tot of time. In fact, the first time gave me the key is not valid, the subsequent times the required time has not expired. Then the last I see that it functions in this way, danny.
danny677
06-06-2013, 16:21
look up to you and behaves as if the keys you were expenditure in previous inputs for both reading and writing, if mpps is able to enter in recovery read? bypassing, I don't know to explain why? but ? gi? success
cawadany
06-06-2013, 16:25
look up to you and behaves as if the keys you were expenditure in previous inputs for both reading and writing, if mpps is able to enter in recovery read? bypassing, I don't know to explain why? but ? gi? success
Unfortunately mpps for now I don't. But how do you activate this recovery?
write it down in the bdm if you can't by obd, at least you have a backup copy
danny677
06-06-2013, 16:36
Unfortunately mpps for now I don't. But how do you activate this recovery?
there it goes only after the smanetti 2-3 times that you d? the error without shutdown the framework restarts, mpps, and then switch off the panels off and back on without restarting mpps but retrying the read-after-error. 2-3 times that I do so? go into recovery and law and I unlock well as the reading.
cawadany
06-06-2013, 16:45
there it goes only after the smanetti 2-3 times that you d? the error without shutdown the framework restarts, mpps, and then switch off the panels off and back on without restarting mpps but retrying the read-after-error. 2-3 times that I do so? go into recovery and law and I unlock well as the reading.
I did not know, otherwise I would have tried when I was mpps. I should see if c'? way to do it with the cock....
cawadany
06-06-2013, 23:31
Do you think it is worth the try to read it at the counter? Then, by connecting to the output pin?
to make the test that you told danny not harmful, but according to me, get a template of the bdm port with a e xxx bosch, open it and read it from the pitches to the inside with the cock v48 ;) you can find the guide between the documents of your gslletto, under the heading bdm subsequently med9.1
cawadany
07-06-2013, 13:07
Guys, I doubt that the file is encrypted. C'? the way to check if ? "locked" in some way?
cawadany do you know if ? can reset the counter of the scriptures on this ecu?
you how many times have you written ? c? also, a maximum limit ? I have one that ? gi? been written 20 times
cawadany
07-06-2013, 13:53
cawadany do you know if ? can reset the counter of the scriptures on this ecu?
you how many times have you written ? c? also, a maximum limit ? I have one that ? gi? been written 20 times
I don't know if c'? a limit, and I don't even know if you can reset the counter. Perhaps with kess v2 ori. I have written 16 times.
assuming that the counter scriptures has got to a certain number, a kind of block...I think you only have to rewrite the eeprom of the first reading, the bdm and the counter goes down to the number of programmazzioni of the reading
cawadany
07-06-2013, 17:23
I probably understood what'? the problem: ? was inhibited reading from obd by varying the seed key.... this ? been done by those who developed the file that I have on now.... so I guess there are no issues with the rewrite of the file ori or another mod file....
Try to read in bdm maybe ? inhibited only by obd
cawadany
07-06-2013, 17:56
Try to read in bdm maybe ? inhibited only by obd
That surely ? inhibited only by obd. Bdm works 100%. But I do not care to read it, the file I have. It was just to understand if there was a problem that could stop me any scripture. If, instead ? cos?, I would say that the writing is not there are problems.
cawadany
11-09-2013, 18:43
Riesumo the 3d to inform you that I have written the car in question without problems with the Cock 2.
I don't know if c'? a limit, and I don't even know if you can reset the counter. Perhaps with kess v2 ori. I have written 16 times.
not c'? limit writing
I have a problem with my car, a Golf 5 GTI 2.0 TFSI fitted with a MED9.1. I've always read and written safely, initially with powergate and then with mpps v5. A few days ago I connect mpps and I to read it: error "invalid key". Since the same mpps in the evening before I had blocked a edc16u31 (then recovery in recovery always with mpps), I think either the cable is defective and I buy a rooster v48. I plug in the cock, I start reading and.... error sk2, silentkey reading... it seems the same error of the mpps. At this point, I think that the problem is not the interface, but my ecu. What is pu? be successful according to you? C'? the way to resolve it? Of course I didn't trust to write......
pu? be the encrypted file with lock-read.
if it's so? it was a solution c'?:
keep on the framework for an hour after trying to read
of course, put a battery charger...
assuming that the counter scriptures has got to a certain number, a kind of block...I think you only have to rewrite the eeprom of the first reading, the bdm and the counter goes down to the number of programmazzioni of the reading
not c'? block over no limit in writing.
the counter can you? anyway to reset in bdm, of course
cawadany
12-09-2013, 13:53
pu? be the encrypted file with lock-read.
if it's so? it was a solution c'?:
keep on the framework for an hour after trying to read
of course, put a battery charger...
This files ? been protected with ecusafe who made me. I do not think that the method of holding the ignition is switched on functions, given that ecusafe change the seed key, and then the programmer does not succeed? never get to read it.
This files ? been protected with ecusafe who made me. I do not think that the method of holding the ignition is switched on functions, given that ecusafe change the seed key, and then the programmer does not succeed? never get to read it.
test... no ? said that nn funznioni
carmageddon
12-09-2013, 21:01
pu? be the encrypted file with lock-read.
if it's so? it was a solution c'?:
keep on the framework for an hour after trying to read
of course, put a battery charger...
on med9 not c ? the possibility? to encrypt files.
when there are files locked against reading and writing is not c ? way to read them, the procedure to keep the framework on for 45 min serves to enable the writing and not the reading...when a file ? locked against reading c ? so read it from the diagnostic socket.
carmageddon
12-09-2013, 21:02
I left out one thing : all the ecu vag, not only med9
cawadany
13-09-2013, 10:17
My file as a gi? said ? been protected with ecusafe, which only protects the read. In fact, I wrote it without problems and without special processes.
on med9 not c ? the possibility? to encrypt files.
when there are files locked against reading and writing is not c ? way to read them, the procedure to keep the framework on for 45 min serves to enable the writing and not the reading...when a file ? locked against reading c ? so read it from the diagnostic socket.
ecusafe protects you from reading the MED9
carmageddon
14-09-2013, 10:52
ecusafe protects you from reading the MED9
fraintendi-encrypt block the download!
on med9 and sisters do not ? can encrypt...read cos I wrote it!
carmageddon
14-09-2013, 10:53
error : and does not and
I mean the block by reading the obd on MED 9.1
carmageddon
14-09-2013, 16:04
the lock for reading ? well-known, and I have written, encrypt ? a other operation.
the procedure you described is used to write and not read
the lock for reading ? well-known, and I have written, encrypt ? a other operation.
the procedure you described is used to write and not read
there is also to read....
I ? happened on audi S3
after ID gave me error in reading and you ? unlocked after 55 min
carmageddon
15-09-2013, 14:36
e-mail the file read after 55 min, and I tell you now cos they have done
if you inhibit the proper way to download in the ecu there is no way to read it from the obd...obviously they have blocked the download in the wrong way
cawadany
16-09-2013, 08:12
My ? locked with ecusafe, and when you read it to read not even part of and you get error seed key. Write no problem.
e-mail the file read after 55 min, and I tell you now cos they have done
if you inhibit the proper way to download in the ecu there is no way to read it from the obd...obviously they have blocked the download in the wrong way
after reading it I checked to see if it was changed...
for? strangely, after it is rewritten let me? read this now
pu? be that the programmer is crazy but me ? only happened that one time
cawadany
02-08-2014, 10:12
Use this thread to ask for clarification, since we stay in the theme....
I have another Golf 5 GTI 2.0 TFSI Med9.1 mapped. The owner would like to try another map, but would not want to lose the one it has now. The problem ? that probably ? was inhibited the reading in the serial, and so I can not read it. If I do it in the bdm, we should be able to read it, right? The read file and then in the bdm ? can possibly write it to serial?
cinqueturbo
02-08-2014, 18:30
Use this thread to ask for clarification, since we stay in the theme....
I have another Golf 5 GTI 2.0 TFSI Med9.1 mapped. The owner would like to try another map, but would not want to lose the one it has now. The problem ? that probably ? was inhibited the reading in the serial, and so I can not read it. If I do it in the bdm, we should be able to read it, right? The read file and then in the bdm ? can possibly write it to serial?
You should to compare the two readings to see s? you can write..
You begin to read it in the BDM that in addition to read it to you up the ass,
and then you can find the file ori is for comparison and maybe and read on the serial line etc. etc.
Use this thread to ask for clarification, since we stay in the theme....
I have another Golf 5 GTI 2.0 TFSI Med9.1 mapped. The owner would like to try another map, but would not want to lose the one it has now. The problem ? that probably ? was inhibited the reading in the serial, and so I can not read it. If I do it in the bdm, we should be able to read it, right? The read file and then in the bdm ? can possibly write it to serial?
after reading the bdm flash the write quietly from the obd
cawadany
18-08-2014, 11:20
Ok, thanks to all. Tonight I read in the bdm.
Powered by vBulletin® Version 4.2.2 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.