MG-Rover.org Forums - View Single Post - TOAF worry ye not!
View Single Post
post #6 of (permalink) Old 29-03-2016, 21:18
marinabrian
Registered User
 
Join Date: Jan 2009
Location: People's Republic of North Tyneside
Car: Far too many!
Posts: 630
Yes Shawn, that quote confirms what I suspected that you can change the VIN in SRS BCU and LSM.

What cannot be done is to change the VIN in the IPK or the DDE4, as these are in secured areas in the internal eeprom fitted to the IPK and DDE, and not accessible via KKL programming protocols.

Remember all that TOAF does, is the same things you can do with BMW Scan 1.4, copying ZCS coding from EWS to IPK, and DDE4 etc etc etc.

What is interesting, and at the same time worrying is the ability to override the safety in the BCU in relation to one shot up windows.

So what I hear you say? well if you look at the drivers window seal on a car with one shot up enabled, you will see it is different to the other three window seals.

The reason for this is because the drivers window seal contains a pressure switch to stop the motor if an obstruction is encountered.

So using TOAF once it is released to hack the firmware in the BCU is not a particularly good idea.....imagine this scenario you have your grandson, or a child in any of the passenger seats, they operate the window switch while holding the glass, and up it goes and guillotines off there fingers, or worse they're hanging out of the window and operate the switch

Still sound like a sensible option to you? certainly doesn't to me

Brian

Oh and no you can't even if you have the password from the parent EWS module, use secondhand transponders.

Why not I hear you say, well yes you can copy the fixed code of the used transponder into another EWS, and even if the cyclic redundancy check is the same, the VIN number most certainly won't be, and for that reason alone the EWS will reject the transponder.
marinabrian is offline  
 
 
For the best viewing experience please update your browser to Google Chrome