Pages: 1 [2]
Author Topic: 2007 AUDI A3 - 8P0907115P  (Read 13856 times)
SB_GLI
Hero Member
*****

Karma: +115/-10
Offline Offline

Posts: 1022


« Reply #15 on: July 25, 2016, 12:52:51 PM »

There's data in the flash (6C00-6FFF) that is some sort of representation of the data in the e2p.  if these two do not match, then no start.

So, once I give you my flash and e2p bdm read, if you want to continue to use your file, you will need to copy the data from 6C00-6FFF from then flash that I give you to your flash... optionally, you can just transfer the map changes from your file to my file.  It might actually be better to do the later as I ran across a bug in ols that will make ghost changes in your bin if you modify 6C00-6FFF.   Just understand that there's a dependency on the e2p data in the flash.
Logged
SB_GLI
Hero Member
*****

Karma: +115/-10
Offline Offline

Posts: 1022


« Reply #16 on: July 25, 2016, 12:54:36 PM »

But you BDM'd the e2p and bin correct?  But you are saying you don't have a backup?
Logged
ktm733
Hero Member
*****

Karma: +18/-8
Offline Offline

Posts: 660



« Reply #17 on: July 25, 2016, 01:24:32 PM »

I only have my bin, I crashed the Ecu by flashing a file with med9.1 layout instead of med9.5 which flash in different areas apparently. Well I tried everything and the car wouldn't start. So I pulled an e2p and bin from an auto 115p file and flashed it. Car started up and ran okay. Of cource I deleted the Immo. So that's why I asked for a manual file so I could see the difference. Also have a proper map for this car, with the auto file the rpms hang.
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #18 on: July 26, 2016, 04:17:38 AM »

I only have my bin, I crashed the Ecu by flashing a file with med9.1 layout instead of med9.5 which flash in different areas apparently. Well I tried everything and the car wouldn't start. So I pulled an e2p and bin from an auto 115p file and flashed it. Car started up and ran okay. Of cource I deleted the Immo. So that's why I asked for a manual file so I could see the difference. Also have a proper map for this car, with the auto file the rpms hang.

TFSI is MED9.1. MED9.5 is N/A
Logged
ktm733
Hero Member
*****

Karma: +18/-8
Offline Offline

Posts: 660



« Reply #19 on: July 26, 2016, 06:00:26 AM »

Are there any tools out there that will read 2010> ? That doesn't cost an arm and a leg?
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #20 on: July 26, 2016, 06:41:55 AM »

Are there any tools out there that will read 2010> ? That doesn't cost an arm and a leg?

2010 what? MED9? MPPS v13 does all MED9 apart from A4s.
Logged
SB_GLI
Hero Member
*****

Karma: +115/-10
Offline Offline

Posts: 1022


« Reply #21 on: July 26, 2016, 08:44:32 AM »

MPPS (v16) bricked a 2007 A3 that I worked on.  I tried reading a 2006 A3 with mpps v13 with no luck.  Luckily I had a BDM backup.

It is my opinion that you should take MPPS clones and toss them in the garbage, unless bricking ecus is a favorite past time of yours.
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #22 on: July 26, 2016, 09:02:31 AM »

MPPS (v16) bricked a 2007 A3 that I worked on.  I tried reading a 2006 A3 with mpps v13 with no luck.  Luckily I had a BDM backup.

It is my opinion that you should take MPPS clones and toss them in the garbage, unless bricking ecus is a favorite past time of yours.

I've not used v16 on anything other than my 2012 Golf R, but my v13 has been tarted around A/S3s from 05-2010. Also MED9 can be recovered up the port very easily. Yet to have a "bricked" MED9 with any version of MPPS.
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

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