Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Solved ✔ 160DOWT cluster issue (F25)
01-11-2023, 15:04 PM,
Post: #11
|
|||
|
|||
RE: 160DOWT cluster issue (F25)
(01-11-2023, 13:57 PM)Bavarian Wrote:(01-11-2023, 13:19 PM)Node Wrote: Long ID is a secret number in the special area of a 160DOWT chip. AFAIK it's burnt into the chip in the factory and CAN'T be changed. It's NOT in your dump. If long ID does not match, you will NEVER get rid of a red dot (unless with cracked firmware). Yes. But I don't know if any tool other than VVDI can write ID into it. |
|||
01-11-2023, 15:34 PM,
Post: #12
|
|||
|
|||
RE: 160DOWT cluster issue (F25)
Okay. Understand what you said. The only chance to rescue the part is buying the Xhorse 35160DW eeprom an write the dump on it. If my cg prog can’t do it, is there anybody who can support with vvdi prog? Is this chip flashable more than once?
Regards Bavarian |
|||
01-11-2023, 15:46 PM,
Post: #13
|
|||
|
|||
RE: 160DOWT cluster issue (F25)
Get VVDI, read ID from your current chip. Get xhorse emulator 35160DW, write id to it, write your dump and solder it back.
Have no idea if any other tool can be used for this. |
|||
02-11-2023, 10:00 AM,
Post: #14
|
|||
|
|||
RE: 160DOWT cluster issue (F25)
Hi,
today I powered the cluster up on my desk and it shows 000000KM. I have read the actual dump file of the Eeprom 160DOWT. Can anybody tell me if CG Pro can read the chip ID or not? Regards Bavarian |