Pages: 1 [2]
Author Topic: Audi B5 dash and ECU swap fail Immo2 to immo2 ( i think)  (Read 22338 times)
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #15 on: October 17, 2014, 02:56:45 AM »

sadly failed, Eprom reader says it's immo3 despite it being set to immo2. So ecu is defeated currently.

Can i just change a bit to stop the flashing light for now, has to be easier than dropping the dash out and disassembling the damn thing again?
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #16 on: October 19, 2014, 08:11:59 AM »

I have the dash Eprom if anyone can point me in the correct direction to lose the flashing key symbol please
 I can't open the dash as I'll invalidate my warranty from the new screen
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #17 on: June 14, 2015, 02:58:15 PM »

Still not working so am running the ecu in IMMO off mode with a flashing key symbol. I'd like to get it working, is anyone perhaps able to look at my dumps and tell me if they can be made to talk. I have virgin RFID chips for the keys to adapt

I am so hoping to re activate it if possible
Logged
tjwasiak
Sr. Member
****

Karma: +26/-0
Offline Offline

Posts: 420


« Reply #18 on: June 14, 2015, 04:42:52 PM »

To be able to adapt anything you need switch immobilizer to on in ECU EEPROM first.
It should not matter if your instrument cluster is IMMO2 or IMMO3 as long as your ECU is IMMO2 as IMMO3 clusters are backwards compatible (at least Volkswagen ones Cheesy).
Main issue I see is you are trying to pair TT (BAM) ECU with A4 cluster which might just not communicate properly. Perhaps it will work if you use different ECU EEPROM (but be sure to backup yours first) (one from APU or AWT engine) but it may also require to use flash from such ECU and tune it according to your setup.
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #19 on: June 21, 2015, 12:57:25 PM »

ok cheers. so i need a virgin eeprom for the ecu in order to set the adaption?
Logged
tjwasiak
Sr. Member
****

Karma: +26/-0
Offline Offline

Posts: 420


« Reply #20 on: June 21, 2015, 03:43:55 PM »

It does not need to be virgin. It just needs to have immobilizer on.
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #21 on: July 04, 2015, 03:39:51 PM »

Ok cheers, will try it later when i get my netbook back
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #22 on: August 15, 2015, 10:21:41 AM »

I give in, It won't let me adapt keys even, on adaptation block 21 it states 2 keys are coded but will not allow me to zero it to wipe them out. Also noticed on measuring block 22 or was it 23? it stated immo status as 6, which i think is adapted/locked?

Can't even get to the ecu adt stage yet.

PPS I have skc's for cluster and ECU
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #23 on: August 16, 2015, 08:18:47 AM »

A slight update, I used a virgin eeprom in ecu and went straight away for a key adaption, it allowed me to extinguish the light and recognise the keys. The ECU however will not adapt, I guess the ECU is immo3 and the dash immo2. The dash can be set as immo3 but then wants canbus for speedo/revs and the like which i cannot provide.

I was hoping 7.5 was immo2 compat, it would seem not.
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #24 on: August 19, 2015, 01:35:19 PM »

 if i post my adapted to key dash eeprom and my ecu eprom could someone make them match on the ecu eeprom please?

I'd like a working immo if possible as a backup against aftermarket security employed, it seems daft to not use it if possible and i learn by seeing, I have read page after page and sadly cannot get further than keys adapted to cluster to shut light off.

I am now using the virgin immo on file.

cluster  SKC is 7394
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

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