search

bri3d / VW_Flash

Flashing tools for VW AG control units over UDS. Compression, encryption, RSA bypass, and checksums are supported for Simos18.1/6/10, DQ250-MQB, DQ381-MQB, and Haldex4Motion-Gen5-MQB.
Other
320 stars 82 forks source link

Stucked (bricked) ECU.... #142

Open arell50 opened 1 month ago

arell50 commented 1 month ago

Hello, I have a VW passat B8 1.8 SIMOS18.1 (SC8) original ID is 3G0906264 0004. And so I obtained the correct frf of the same. I have followed the procedure.

  1. UNLOCK ECU (FRF) FL_8V0906259H__0001.frf from unlock folder

    From here it Upgrading to programming session 100 and stops there.

  2. Full Flash Unlocked (BIN/FRF) FL_3G0906264___0004.frf

  3. Calibration Flash Unlocked udsoncan.log

    FL_3G0906264___0004.frf

My VW hardware version shows H13 instead of X13.

Now Flashstock relock also cannot work. ECU is stucked

flash.log flash_details.log udsoncan.log

This far I have not attempted to write any tuned file. just using all the stock files provided.

2nd try: After obtaining a full read backup, I boot wrote it using Magic tool. After that the ecu could not be detected when installed in car. possibly some corruption. but can ID. I then used VWflash flash back to stock and lock using the correct ID frf. AFter that car started and stalled with IMMO active. This car has stock everything, what causes it to immobilize?

arell50 commented 1 month ago

Ok. I suspect this ECU had immo previously deactivated. So, while unlocking, as soon as a stock IMMO active bin got written. It locked up. My next question is: Is there a way to see if the ECU has been previously IMMO offed in the ID screen so that this will not happen to anyone else in future?

arell50 commented 1 month ago

I have read problem faced by others, The only reason you get stucked and cannot write anymore with OBD connection is when immo is activated.

BerkayE010 commented 2 weeks ago

Any updates?