PDA

View Full Version : PIN from Audi A3 93C86 dump please



fogducker
12th January, 2017, 09:27 PM
PIN from Audi A3 93C86 dump please420923

fogducker
13th January, 2017, 09:02 AM
Can anyone help please? This dump is from 2005 Audi A3 with VDO dash 8P0980950P

mihai99
13th January, 2017, 09:30 AM
Try 65535 .

fogducker
13th January, 2017, 10:32 AM
Thank you so much! I will try at some stage today and let you know the results.

does the dump look ok too?

fogducker
13th January, 2017, 10:48 AM
Just a thought, aren't the pins actually 4 digit? I know they are entered as 5 digit in vcds but we just add a zero to the start.

vlaki electric
13th January, 2017, 11:06 AM
pin is 3713 from your dump. 65535 in hex is FF so that is not the pin

fogducker
13th January, 2017, 11:12 AM
Ahhhhhh, brilliant. I will try that.

fogducker
13th January, 2017, 11:13 AM
Can I also ask the memory address of the PIN?

fogducker
13th January, 2017, 12:02 PM
PIN did not work sadly

fogducker
13th January, 2017, 12:50 PM
here are two dumps, original dump plus 8bit dump if that makes any difference?

421045

fogducker
13th January, 2017, 04:43 PM
Can anyone help? I am told by carprog that this dash is not crypto??

vlaki electric
13th January, 2017, 05:05 PM
if that pin not work try 19654. realy not sure. now i am confused

fogducker
13th January, 2017, 05:24 PM
Thank you for taking the time to look again, I will try that. Do the dumps look ok?

3311
14th January, 2017, 03:08 PM
Thank you for taking the time to look again, I will try that. Do the dumps look ok?

did you try login in dash (ecu 17) oder immobilizer (ecu 25)??

fogducker
14th January, 2017, 04:17 PM
I tried immobiliser and made sure the lock time was at zero

RedNix
14th January, 2017, 04:28 PM
pin should be 19654

fogducker
14th January, 2017, 05:02 PM
I thought they had to be 4 digit with a zero added at the start?

fogducker
14th January, 2017, 05:17 PM
Could I read the dump from my old cluster and write to this one? Would that put the old IMMO pin in to the new cluster? If I knew the memory address I could simply change it to the same as my old cluster.

3311
14th January, 2017, 05:33 PM
my old pin from 8P0920930G was 32111 without zero. when you copy your old cluster into your new one pin stays the same.
what partnumber has your old dash?

copy eeprom from old dash to new dash is possible but not good.
What equipment do you have?

Carprog is good for dash with fujitsu or avdi/fvdi

fogducker
14th January, 2017, 06:12 PM
The new cluster is 8P0920981B (2005 8P model) and I believe it has Fujitsu MCU. I tried the dump from my old cluster which did not work, different cluster though. I put original dump back in to new cluster and it is back to normal. Still no pin however!

i have latest genuine Carprog and latest genuine VCDS Hex v2

fogducker
14th January, 2017, 06:14 PM
Both 03713 and 19654 do not work in this cluster. I am entering the pin at the (25) immobiliser section of genuine VCDS.

fogducker
14th January, 2017, 06:46 PM
If I got a cluster from a donor car along with it's matched key, surely I can then read the IMMO pin with carprog via OBD?

3311
14th January, 2017, 07:04 PM
@fogducker
send me both eeprom by pm read fresh and in 8bit format
i will try next week until now i have stress with examination till monday

fogducker
14th January, 2017, 07:06 PM
I will, thank you!

fogducker
16th January, 2017, 09:26 PM
looks like I cant send files via PM?

3311
18th January, 2017, 10:33 AM
looks like I cant send files via PM?

load it up here secured with pass and send me pass by pm

fogducker
18th January, 2017, 08:02 PM
422370

Here you go. Pass in pm

keyzex
19th January, 2017, 10:19 PM
Try pin 1009


422662

fogducker
19th January, 2017, 11:12 PM
Thank you. That's carprog, mine gives exactly the same reading but sadly it's wrong. It gives the same reading with nothing connected too.

However, I did get the correct pin today which is 21579. I've successfully logged in with it too. My next problem is that adaptation channel 50 in vcds is not available

3311
20th January, 2017, 03:18 PM
422370

Here you go. Pass in pm

hello.

i flashed both eeprom you uploaded but without any success.
avdi displayed only "ffff..." for everythind and all led lighning with DEF error and 0km
i would say eeprom is corrupted

keyzex
20th January, 2017, 04:10 PM
I've never seen that PIN is in the five-digit format your code is. It has always been (0) XXXX.
How did you get out pin 21579?

exe123
20th January, 2017, 04:31 PM
I've never seen that PIN is in the five-digit format your code is. It has always been (0) XXXX.
How did you get out pin 21579?

Login is always 5-digits.
leading 0 is normal for IMMO3. IMMO4 can be full 5-digits.

keyzex
20th January, 2017, 04:44 PM
Login is always 5-digits.
leading 0 is normal for IMMO3. IMMO4 can be full 5-digits.
Okay then, I've learned something new.
Thanks always good to be updated

fogducker
20th January, 2017, 11:45 PM
I've never seen that PIN is in the five-digit format your code is. It has always been (0) XXXX.
How did you get out pin 21579?

I also thought that they were all 4 digit too with a preceding zero. Every day is a school day!

I got the pin using Carprog

fogducker
20th January, 2017, 11:49 PM
hello.

i flashed both eeprom you uploaded but without any success.
avdi displayed only "ffff..." for everythind and all led lighning with DEF error and 0km
i would say eeprom is corrupted

It works totally fine in my cluster and I got the code as posted earlier. I even flashed it with my other cluster eeprom dump and back again to those ones I posted and it still works perfectly. From what I've learned recently, this cluster is immo4c and is very difficult to adapt to a new vehicle due to component security. Do you know anything about that?