There you go mate,few days ago i made km for a car like this there are original files....Good LUck!P.S i think your flash is corrupted...
I can usually find the solutions to problems by just browsing here but this time I'm desperate. Tried to add a key and everything seemed to go ok but then CAS comm stopped and it just seemed to drop dead. Tried to connect to it on the bench with VVDI and Zed-Full but got no response. So I read Flash and Eeprom with a Xprog. I'm assuming the eeprom got corrupted and am hoping that someone can help me sort it out. CAS part number is 61.35-9147185-01. Any help would be greatly appreciated. These are the read files:
There you go mate,few days ago i made km for a car like this there are original files....Good LUck!P.S i think your flash is corrupted...
doctore (14th December, 2017), droidwayne65 (14th December, 2017), NogaroB5S4 (12th December, 2023)
why dont make backup before make key?
bersch8688 (14th December, 2017)
Test whit the flash first,because i think your eeprom is OK,and please report back
Thank you. Hopefully this is enough to revive it. Will worry about car-specific details later .
LOL! Just got to the shop, all excited, only to notice that your flash is a quarter the size of mine. Seems the Xprog reads all four blocks of flash while yours is block 3. I assume that's the important block, so what did you use to read your CAS? VVDI usually gives a prompt that the whole flash isn't being read when it's used, so I'm assuming that's the tool I should use for writing?
Yes m8 i used VVDI prog for read
Well this thing is well and truly screwed. Can't write the flash with xprog or vvdi. Took it to a friend with a R270 and got the same result. Crazy thing is that eeprom can be read and written all day long and there's no problem reading the flash.
Can you try whit another cas???Write your eeprom and the flash from my files...
Bookmarks