Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
View
Go to last post
Offline RocketSurgeon  
#1 Posted : 30 June 2019 00:00:04(UTC)
RocketSurgeon


Rank: Advanced Member

Reputation:

Groups: Registered
Joined: 10/01/2019(UTC)
Posts: 52
United States
Location: NC

Was thanked: 44 time(s) in 24 post(s)
I'm having some difficulty with BMW cluster EEPROM and Hexprog. I was working with an F02 cluster with 160DOWQ chip, which I desoldered and placed in the hexprog socket. When attempting to set or erase mileage, I would get a "Failed to unlock Chipset Reference: 2103" at some point in the erasing process. This would result in a random mileage being set in the chip. Trying to backup the original data resulted in the same error. I could not set mileage, erase mileage, or backup original data.
I decided to try the same operations with a spare 080DOWQ and experienced the same issues. It will erase up to a certain position, then fail. I was able to complete these operations using the exact same chips in a different programmer, so the EEPROM appears to be fine.
Sponsor
HexTag/HexProg tool is the ultimate tool for Ecu Cloning/Ecu Tuning ,BDM Read/write, Key renew and EEPROM Reset

Click here on HexTag for more info about HexProg Software

Offline Findlaybum  
#2 Posted : 30 June 2019 01:21:34(UTC)
Findlaybum


Rank: Advanced Member

Reputation:

Groups: Registered
Joined: 04/10/2015(UTC)
Posts: 93
Location: Here

Thanks: 715 times
Was thanked: 90 time(s) in 57 post(s)
Try using the clip provided .. see if that works ...
OFFICIAL FRIEND OF OFFICIAL AUTOHEX II PARTNER .. AND OFFICIAL FRIEND OF THE BOSS .:)
Offline Autohex_II_BMW  
#3 Posted : 30 June 2019 01:55:20(UTC)
Autohex_II_BMW


Rank: Advanced Member

Reputation:

Groups: Moderator
Joined: 22/08/2015(UTC)
Posts: 1,057
United Arab Emirates
Location: Dubai

Thanks: 469 times
Was thanked: 1097 time(s) in 556 post(s)
Originally Posted by: RocketSurgeon Go to Quoted Post
I'm having some difficulty with BMW cluster EEPROM and Hexprog. I was working with an F02 cluster with 160DOWQ chip, which I desoldered and placed in the hexprog socket. When attempting to set or erase mileage, I would get a "Failed to unlock Chipset Reference: 2103" at some point in the erasing process. This would result in a random mileage being set in the chip. Trying to backup the original data resulted in the same error. I could not set mileage, erase mileage, or backup original data.
I decided to try the same operations with a spare 080DOWQ and experienced the same issues. It will erase up to a certain position, then fail. I was able to complete these operations using the exact same chips in a different programmer, so the EEPROM appears to be fine.


please send us the original eeprom and damaged one's.your eeprom is getting corrupted in mileage part that's why showing some random numbers.
Offline RocketSurgeon  
#4 Posted : 30 June 2019 11:52:20(UTC)
RocketSurgeon


Rank: Advanced Member

Reputation:

Groups: Registered
Joined: 10/01/2019(UTC)
Posts: 52
United States
Location: NC

Was thanked: 44 time(s) in 24 post(s)
160D0WQ_original.bin.txt (2kb) downloaded 9 time(s). 160D0WQ modified.bin.txt (2kb) downloaded 4 time(s). 160D0WQ revert.bin.txt (2kb) downloaded 1 time(s).

I think I got the 3 files attached. The original has a mileage of something like 147572km on it. The modified file is the result of trying to reset back to zero, and the third file is what happened when I tried to write the original file back to the chip. I tried with both the chip clip, and putting the chip in socket.
Offline Autohex_II_BMW  
#5 Posted : 01 July 2019 06:20:40(UTC)
Autohex_II_BMW


Rank: Advanced Member

Reputation:

Groups: Moderator
Joined: 22/08/2015(UTC)
Posts: 1,057
United Arab Emirates
Location: Dubai

Thanks: 469 times
Was thanked: 1097 time(s) in 556 post(s)
Originally Posted by: RocketSurgeon Go to Quoted Post
160D0WQ_original.bin.txt (2kb) downloaded 9 time(s). 160D0WQ modified.bin.txt (2kb) downloaded 4 time(s). 160D0WQ revert.bin.txt (2kb) downloaded 1 time(s).

I think I got the 3 files attached. The original has a mileage of something like 147572km on it. The modified file is the result of trying to reset back to zero, and the third file is what happened when I tried to write the original file back to the chip. I tried with both the chip clip, and putting the chip in socket.


your eeprom file we tested with our 160dw IC and it is working.so i guess problem from your IC itself.
WhatsApp Image 2019-07-01 at 5.17.55 PM.png (852kb) downloaded 47 time(s).

try to read in this way and make first 2 lines all 00 00 and write
Offline RocketSurgeon  
#6 Posted : 01 July 2019 22:55:35(UTC)
RocketSurgeon


Rank: Advanced Member

Reputation:

Groups: Registered
Joined: 10/01/2019(UTC)
Posts: 52
United States
Location: NC

Was thanked: 44 time(s) in 24 post(s)
I did one 160DOWQ previously, and it worked perfectly on the first try. I used the clip and it worked in-circuit, didn't even need to take it off the kombi. After that first cluster, I've been having problems where I get the "Failed to unlock Chipset Reference: 2103" message. It always fails erasing the same memory block. With the 160DOWQ, it failed on block 14. Now I have been testing with a different 080DOWQ chip and it is failing on block 4. I have experienced this issue on 2 different chips, and both are functioning with a different programmer. Should I try clean install or something?
Here are files from an additional attempt with 080DOWQ. Hexprog managed to erase the first several blocks, but gave the 2103 message after working on byte 4 for some time. 080D0WQ_original.bin.txt (1kb) downloaded 6 time(s). 080D0WQ_modified.bin.txt (1kb) downloaded 2 time(s).
Offline Autohex_II_BMW  
#7 Posted : 02 July 2019 04:15:37(UTC)
Autohex_II_BMW


Rank: Advanced Member

Reputation:

Groups: Moderator
Joined: 22/08/2015(UTC)
Posts: 1,057
United Arab Emirates
Location: Dubai

Thanks: 469 times
Was thanked: 1097 time(s) in 556 post(s)
Originally Posted by: RocketSurgeon Go to Quoted Post
I did one 160DOWQ previously, and it worked perfectly on the first try. I used the clip and it worked in-circuit, didn't even need to take it off the kombi. After that first cluster, I've been having problems where I get the "Failed to unlock Chipset Reference: 2103" message. It always fails erasing the same memory block. With the 160DOWQ, it failed on block 14. Now I have been testing with a different 080DOWQ chip and it is failing on block 4. I have experienced this issue on 2 different chips, and both are functioning with a different programmer. Should I try clean install or something?
Here are files from an additional attempt with 080DOWQ. Hexprog managed to erase the first several blocks, but gave the 2103 message after working on byte 4 for some time. 080D0WQ_original.bin.txt (1kb) downloaded 6 time(s). 080D0WQ_modified.bin.txt (1kb) downloaded 2 time(s).


contact support in skype
Offline robert  
#8 Posted : 22 October 2019 13:50:55(UTC)
robert


Rank: Newbie

Reputation:

Groups: Registered
Joined: 05/10/2019(UTC)
Posts: 4
United Kingdom

Was thanked: 1 time(s) in 1 post(s)
I also have problems with 160d0wq eeproms. I did try to erase first and set mileage to 120 000. When read it again mileage was not correct 112500. Tried different values but mileage was incorrect and always much lower. Obviously chip was removed from cluster. Cheap r270 did the job with no issues so it is not a eeprom fault. This is the second time I tried 160 eeprom and it failed in both cases using hexprog
Offline RocketSurgeon  
#9 Posted : 22 October 2019 21:47:17(UTC)
RocketSurgeon


Rank: Advanced Member

Reputation:

Groups: Registered
Joined: 10/01/2019(UTC)
Posts: 52
United States
Location: NC

Was thanked: 44 time(s) in 24 post(s)
As an update to my original post, it turned out to be bad EEPROM. I got new chips that functioned fine with Hextag.
Here's the interesting thing: even the EEPROM that didn't get along with Hextag could still be erased with CG Pro. Certain chips had certain bytes that Hextag couldn't erase. I suppose CG Pro hit them harder and managed to erase them.
Offline Autohex_II_BMW  
#10 Posted : 22 October 2019 23:00:31(UTC)
Autohex_II_BMW


Rank: Advanced Member

Reputation:

Groups: Moderator
Joined: 22/08/2015(UTC)
Posts: 1,057
United Arab Emirates
Location: Dubai

Thanks: 469 times
Was thanked: 1097 time(s) in 556 post(s)
Originally Posted by: RocketSurgeon Go to Quoted Post
As an update to my original post, it turned out to be bad EEPROM. I got new chips that functioned fine with Hextag.
Here's the interesting thing: even the EEPROM that didn't get along with Hextag could still be erased with CG Pro. Certain chips had certain bytes that Hextag couldn't erase. I suppose CG Pro hit them harder and managed to erase them.


yes we have small software bugs in mileage reset in some cluster eeproms.we are working on it and will be resolved real soon.
thanks 2 users thanked Autohex_II_BMW for this useful post.
Users browsing this topic
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.