My CAS dump issued or good? Please check and help

[taisukesan3]

Dear friends,

Troubled for BMW E91 / 2010 / N42engine / MSD81.2
CAS 61.35-9226238-01 / MC9S12XDP512CAL 0L15Y


Engine won't start After battery dead and replace new one .
DTC 2F49 Mean --- EWS Manipulation Protection


Place to key slot , Work ESL so unlocked steering wheel.
I think OK for key matching.
Starter Cranking OK.


I thought lost link as CAS and DME.
Synchronize My tool.
FVDI --- failed.
Vedis --- failed.


Next try CAS clone with VVDI and Synchronize once again.
Results same , still won't engine start. 533


Possibly issued Flash data of CAS?
May I request check CAS dump Good or Not?


WBAUS92080A861866
ISN 8C71B21350D248E2BA0A16B15948E635


ISN read with AT-200.
CAS data broken? Or can resynchronize ?


Please your help and things,


Best regards, :tears_of_joy:

[weld88]

Your eeprom dump was in boot mode. CAS 3+ editor that you can find on the forums here will tell you that, and can *sometimes* fix it.

Your flash matches the version listed in your eeprom, 9389115.


Cheers

[taisukesan3]

Hello weld88.

Thank you for your help!
I will test and tell you result.

Best regards, :tears_of_joy:

[PixelsFixed]

But in my experience, if it's stuck in "boot mode", you won't get the car to crank?

Cranking, previous flat battery and "EWS Tamper" errors look like cas/dme resynch to me.

Clear all dme and cas fault codes that you can.
Disconnect the battery for at least 20 minutes. Time it. Be patient.
Reconnect the battery and a battery support unit.
DO NOT try to start the car.
Clear any codes again.
Perform CAS/DME resynch.

If you follow these steps, I'm sure your car will start.

[weld88]

Agreed, boot mode CAS shouldn't work. The dump was in boot mode, maybe the tools OP used took care of that already.

That said, others reporting that same fault code *sometimes* have the engine cranking but not starting.

Of course most of the examples I've read about were because ECU or CAS had been replaced. The root cause was usually because the ISN's did not match.

Assuming the issue isn't solved, maybe someone with access to better tools than I have could verify that the ECU ISN OP posted matches the ISN in the CAS dump ?

The eeprom dump only shows version 9389115, there is no mention of the original version# 9226238.

Normally the original version # repeats 3 times at offset 0xF70 in the eeprom.

[Chriz123]

CAS Editor is crap tool
or this version of Editor is crap and very old

Long ISN does not need to be sync thats why you cant sync. (as far as i know)
From what i can see, the ISN is ok. Hextag can decrypt your file with ISN

The problem really comes after replacing battery, or it was already present before change batt?
Maybe flash it a bit corrupt? Try this one is same (9389115)

Give it a try with a new key, if you can programm one

[weld88]

CAS Editor is crap tool
or this version of Editor is crap and very old

Long ISN does not need to be sync thats why you cant sync. (as far as i know)
From what i can see, the ISN is ok. Hextag can decrypt your file with ISN

The problem really comes after replacing battery, or it was already present before change batt?
Maybe flash it a bit corrupt? Try this one is same (9389115)

Give it a try with a new key, if you can programm one

His flash dump and yours are identical, unless his CAS flash was corrupted after the dump was made, this will not solve the issue.

If ISN's are correctly matched, what does that leave? A checksum error in his eeprom maybe.

[Chriz123]

oh didnt extract the flash file, so didnt see it :rofl:
i dont have an idea...
played a bit with hextag and other tools, and did some manual edits, and transfered to other eep.
hope it will work :D

Try this one, but coding data and VO won't match.
Transfer VO from FRM to CAS, and Code it. clean error and try to start
and/or try new key...