Urgent: USDM EVO8 Doesn't Start anymore, help needed please

[nabilsx]

Hello guys,

yesterday I was tunning my friends EVO7 european spec using tactrix 1.3U cable and ECUflash 1.38, everything went well, after we were done, another friend asked to tune his USDM import EVO8, so I read the stock rom off his car, modified some fuel, timing, boost tables and then flashed back, everything was going as normal so far, till we tried to start the car and it didnt start, so I went into ECUEdit and tried to access logger and it said "ECU no response", I flashed back stock rom and still pbm was not solved, the stock ECU ID#MN132874 RomID # 94170014

so I said ok, I have an ECU that I bought off ebay, ECU # MN132874 and RomID: 94170008 so I swapped ECUs, and went into logger and the ebay ECU worked fine, tried to start car it did not start, I said ok since it has different Immo code, so I copied the immo code from stock ECU to ebay ECU and flashed. and the same problem happened, logger can't access ECU anymore, diagnostic tool cant find ECU, and car doesnt start. I can read rom and write rom, but nothing else does work? what should I do?
I tried flashing stock file over both ECUs and pbm was not solved
anyway this is what I got when I flashed the stock rom back to ECU and asked to compare file with ECU

-- New session started at 10/2/2008 9:45:02 PM : Compare process with template Evo 7,8 16-bit --

[0.000] loading kernel from file C:\Program Files\ecuEdit\kernels\m7052_v103.bin
[0.015] 3588 byte kernel read
[0.016] 262144 byte image read
[0.063] found OpenPort 1.3U cable
[8.562] sending init sequence 1 (0001)
[1.063] read 0x05 response
[0.015] sending init sequence 2
[0.047] read 0x1B response
[0.016] sending init sequence 3
[0.484] writing kernel area addr: FFFF8800 len: 0E04
[1.906] kernel get version
[0.047] kernel version is : OpenECU Mitsubishi SH7052 Kernel V1.03
[0.016] reading kernel comm buffer size
[0.047] comm buffer size set to 512
[0.015] reading kernel flash buffer size
[0.032] flash buffer size set to 4096
[0.312] comparing ECU flash memory pages to image file
[0.047] page 0 from 000000 to 000FFF crc32 E42003A6 file_crc32 E42003A6 :: YES
[0.062] page 1 from 001000 to 001FFF crc32 B7E7F5C3 file_crc32 B7E7F5C3 :: YES
[0.063] page 2 from 002000 to 002FFF crc32 9EBEFC12 file_crc32 9EBEFC12 :: YES
[0.062] page 3 from 003000 to 003FFF crc32 7A4B5594 file_crc32 7A4B5594 :: YES
[0.063] page 4 from 004000 to 004FFF crc32 37A6E576 file_crc32 37A6E576 :: YES
[0.062] page 5 from 005000 to 005FFF crc32 77EF67BE file_crc32 77EF67BE :: YES
[0.063] page 6 from 006000 to 006FFF crc32 B9D2C2FB file_crc32 B9D2C2FB :: YES
[0.047] page 7 from 007000 to 007FFF crc32 2A8CF5E9 file_crc32 2A8CF5E9 :: YES
[0.156] page 8 from 008000 to 00FFFF crc32 8B6B957F file_crc32 8B6B957F :: YES
[0.297] page 9 from 010000 to 01FFFF crc32 4BCDC4EA file_crc32 4BCDC4EA :: YES
[0.281] page 10 from 020000 to 02FFFF crc32 3EB5B1CF file_crc32 3EB5B1CF :: YES
[0.297] page 11 from 030000 to 03FFFF crc32 AB9A8EC1 file_crc32 AB9A8EC1 :: YES
[0.016] readed image is identical with ECU
[0.078] The operation completed successfully

Basically all what I did was tunned the fuel and ignition tables and flashed back, then with the Ebay ECU I only changed Immo code and flashed back, but in both cases car doesnt work now

Kind Regards
Billy

[MalibuJack]

Did you use the same rom from the old Ecu? Are you certain it wasn't somehow corrupted?

Anyway, I've come across a problem that a few people had recently when copying the Immob code over.. They just typed the number in and didn't use the hex formatting, so the code was basically translated from decimal to hex, instead of left as hex.

Whats odd is you said you had a working rom, saved it, then saved it back onto the ECU, and it won't start..

I would get a virgin 94170014 or 94170008 rom from another car/ecu, and put the known good immobilizer code on (verify its correct by looking at it a second time to see its the same)..

There are other possibilities why it won't start.. a bad definition for your rom could have allowed you to overwrite portions of the programming, but again, you said you put the stock rom back on.. If you put it back the same way you found it, its extremely unlikely the car won't run. But at the least, get it back to that state.

[MalibuJack]

BTW It honestly sounds like you might have used a non-USDM rom instead of the proper USDM rom.. I was experimenting with different periphery bits and was able to enable/disable OBD-II on a USDM rom that basically caused the same thing you are describing (reflashing worked, but OBD-II logging no longer functioned, and I recall I was also able to toggle a bit that disabled MUT-II logging also) Its part of the same group of bits that you would fiddle with to disable the immobilizer.

Hopefully that helps.