Log in

View Full Version : VVDI2 IMMO 4 service mode



sjc1
4th August, 2022, 06:04 PM
After using vvdi2 and pogo pin to put Polo 2011 dash into service mode and making two new transponders i have the mileag flashing any ideas why?

Is this the fix?

VDO cluster with NEC processor and 24C64 eeprom the solution is to read the eeprom, replace with FF all values including between 0x10C0 and 0x1173, and finally rewrite the eeprom

sjc1
8th August, 2022, 11:02 AM
Has any one experienced this?

Supas
8th August, 2022, 04:16 PM
Do you have the original eprom?

wuza
8th August, 2022, 09:32 PM
Was that job direct on the car or you have only has it been remote job (with dashboard on the bench)?
As far as I know the super VAG has an option with pogo PIN...
But I can’t remember that VVDI2 has also this option as well...
Maybe I am wrong, since I have been using VVDI2 on VAG directly on the car...

Supas
8th August, 2022, 09:48 PM
Was that job direct on the car or you have only has it been remote job (with dashboard on the bench)?
As far as I know the super VAG has an option with pogo PIN...
But I can’t remember that VVDI2 has also this option as well...
Maybe I am wrong, since I have been using VVDI2 on VAG directly on the car...


The Pogo pin boot function can be used by anyone on the bench... it's nothing more than sending controlled ground to one leg of the mic to leave it in a service mode state. After that you can use the programmer you like the most.

sjc1
9th August, 2022, 06:58 AM
yes pogo pin on bench with vvdi2 . original eeprom wrote back but still a fault code left for internal module fault. iv never had this before but iv spoke to a few other people and theyve had same issue, one even when original eeprom wrote back mileage still flashing

Supas
9th August, 2022, 10:30 AM
If you have a problem with pogo, you must put it into service manually... you have to put in FF from line 0x1290 to 0x1500.

- Connect with vvdi2
- read inmodata (will be wrong data)
- Write original eprom
- Re read inmodata (real inmodata)

That way you shouldn't have any problem with making keys and km

Manta1600
9th August, 2022, 11:25 AM
yes pogo pin on bench with vvdi2 . original eeprom wrote back but still a fault code left for internal module fault. iv never had this before but iv spoke to a few other people and theyve had same issue, one even when original eeprom wrote back mileage still flashing

I had simmilar situation - I used Xtool tool to change the mileage and after that was OK

I think that every tool that can do mileage on this car will be ok

brobble
9th August, 2022, 04:13 PM
Mileage blinking on this type of cluster I know, if lock bit is set to unlocked. Take VCDS, go into cluster (17), adaption and search for lock bit setting. Dont know the exactly name, but you will find it. You can set unlocked to lock with vcds. But not locked to unlocked. With this bit some special adaptions are locked, like numbers of fuel sensors etc. Unlocking this I only know by eeprom dump, but in your case maybe accidently by pogo. I dont like this method, because you are not the first, who messed up dashboard by this method...

Greets MR...

Supas
9th August, 2022, 04:27 PM
Do you have the original eprom?

I'm back to the same thing... do you have the original file?
Your solution is that... save original file and if you already save inmodata when you enter with vvdi2 you can make the 2 keys that are already in the system... without entering programming.
If you want to make two transponders with a new id it's easy too and you don't have to have problems with KM.
At no time did you mention that you wanted to modify the km, only that when writing 2 new keys that problem arose.
He sends me a message and I help him.

brobble
9th August, 2022, 04:37 PM
I think he doesnt have eeprom dump before pogo method. If the made keys are working, he doesnt need to do service mode. He can change mileage, read/write eeprom now with obd without service mode. But changing mileage wont solve his problem I think. He messed eeprom data by pogo method. But read eeprom now and post it could help.

Greets MR...

sjc1
9th August, 2022, 05:15 PM
I wrote original eeprom back and mileage stop flashing now but still have a faut for internal fault. i want to know what this has happened so i can avoid it in the future

Supas
9th August, 2022, 05:45 PM
In my opinion it was the Pogo that happened... although it is a practical procedure... it has its risks, the ideal is to impose mass through resistance and not directly.
Much more we can not help without having your reading.

ovidiumarin
22nd June, 2023, 08:53 PM
Hi all,

Sorry to revive this thread but I'm facing the same issue. Basically, I've upgraded the cluster on a T5.1 from basic one to highline. I've just transfered the immo data from old dash to new dash then recalibrated mileage. Now mileage is flashing. Any ideas where to start ?

Thanks!

brobble
26th June, 2023, 01:30 PM
Yes, start by reading this threat. :-) Post 9 should be the solution.

Greets MR...