View Full Version : audi a4 8K0 959 655B internal checksum B2000
smokinjoe
1st November, 2018, 10:27 PM
Hi could you please help me repair this module with B2000 checksum error which appeared after jump starting the vehicle
568860
thanks
badziewo
1st November, 2018, 10:39 PM
Here you go.
smokinjoe
2nd November, 2018, 05:50 PM
I have tested this file but i am still getting the same B2000 error tested on 2 different modules if anybody could assist,
thanks again.
smokinjoe
8th November, 2018, 06:57 PM
i have purchased a replacement module and have used the above clear file but was still showing internal checksum fault and live data was showing a frontal collision so i gave it a try myself and wrote the attached file which got rid of the frontal collision but i still have a checksum error B2000 any help would be greatly appreciated
570532
thanks
smokinjoe
10th November, 2018, 12:21 PM
Still looking for help with this one,module has been replaced but still getting checksum error once connected to car.
Sent from my E6653 using Tapatalk
badziewo
10th November, 2018, 11:53 PM
Try this one. Same pass
smokinjoe
11th November, 2018, 08:08 PM
Try this one. Same pass
thanks i will try this and report,is this a dump from a different car and if so will I not have a cp problem by using it?
badziewo
11th November, 2018, 10:33 PM
Yes this is from different car. Let see if you get b2000.
smokinjoe
11th November, 2018, 10:52 PM
Ok I will try tomorrow and report, I have tried a different file with same numbers but I was just getting component protection active so couldn't go any further.
Sent from my E6653 using Tapatalk
badziewo
11th November, 2018, 11:13 PM
Last option.This is your file cleared.
Same pass. Good luck
smokinjoe
13th November, 2018, 09:10 PM
no success with this module so i will order a new one but just to say a big thanks to badziewo for your help,much appreciated.
slick_dick
13th November, 2018, 09:19 PM
dont give up
i suspect driver error
look for mcu with bosch logo and number like 41083, if on one of these mcu's you see a pinhole out of the ordinary then grab another mcu similar and stick a new driver on yours!!
see my pics in this post
http://www.digital-kaos.co.uk/forums/showthread.php/701320-AUDI-A4-2017-CHECKSUM-ERROR
we wait for used module to rip drivers out of
smokinjoe
13th November, 2018, 09:56 PM
thanks,i had got a used module already to eliminate any h/w issues but the module still reports the same error so i feel it has to be an eeprom error in my case but i'm unable to confirm this as i can't use a donor file as component protection is active and i don't have any tools to remove this so at the moment the only option i see is to install a new module,
appreciate your input though and thanks.
Meat-Head
13th November, 2018, 10:08 PM
ON TOPIC-
can you cause a shit load if faults, read EEPROM see if you in same area if workings
as for cp verses cost if new module ring dealer can and how much to code used module?
badziewo
14th November, 2018, 02:35 AM
ON TOPIC-
can you cause a shit load if faults, read EEPROM see if you in same area if workings
as for cp verses cost if new module ring dealer can and how much to code used module?
I don't understand why you give negative feedback if you and I had never dealt before and I never advised you on anything. That is a very spiteful action on your behalf and not cool at all. Why did you do it? Please remove it. I help people for free and so far everyone is very happy with my advice.
smokinjoe
14th November, 2018, 08:59 PM
ok today i decided to use a different file from dk and this got rid of my b2000 error and i had faults for passenger deactivation switch and component protection,i was able to use adaptations with vcds to lose the passenger faults and now have just 1 dtc of component protection,is it possible to remove this from enclosed dump or is the only option to use avdi or main dealer.?
572128
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.