Solution for ECUFlash 1.35 freezing with 100% cpu when reading/writing rom.
#1
Evolving Member
Thread Starter
Solution for ECUFlash 1.35 freezing with 100% cpu when reading/writing rom.
Hey guys, im at it again with another program. I was so tired of having to use the nice features of ECUFlash 1.35 (graph view), but not being able to use my cable with it. I have an older Openport 1.3M (with a 8 digit serial number). The new ones have a 48 digit serial number. As you can see in the pictures, it just filled the rest of my serial with 0's, i blurred out my actual serial. So I used OllyDbg and some other tools to track down the code responsible for maxing out my cpu and stalling the thread.
Here it is.
This makes the function always return true. I have NO idea what the function is or what it does. All i know is with 1.35 it works now. I have flashed and read my rom with out bricking my ecu, so i guess it works just fine. Here are some screen shots.
So to use it, OpenECU flash 1.35. Then run the app. It will modifiy the ram for ecuflash so change the code. I dont know if this is breaking any ELUA or user agreements, so use at your own risk. The you can quit the program. The memory will stay modified for the entire instance of ECUFlash. If you close ECUFlash and re-open it, you will have to patch it again. The program is not a TSR-style program, it will not use any system resources or memory (except for when it is running). For vista users, you may need to use run as administrator. I dont have my UAC enabled, so i cant check if it needs admin rights. Im sure it does because it modifies another programs memory. This program only works with ECUFlash 1.35!! Any other versions will fail the Memory check. I would've just modified the ECUFlash.exe, but it is a compressed exe and ive never been able to actually pull code from a compressed/encoded executable. One last thing, im still using the Tactrix drivers from 1.29a. The drivers included in 1.35 make Tactrix cable not work at all. So Stick with the 1.29a drivers and install the ECUFlash 1.35 and cancel the driver install part. Maybe if enough people use it, ill write a loader to load and patch ECUFlash in just one click, instead if it being a seperate app.
*** Update *** New link with the static linked version (removes the need for the visual c++ runtime dll's)
Download : https://www.evolutionm.net/forums/at...1&d=1218646159
Here it is.
Code:
004091BF 3BD9 CMP EBX,ECX was changed to 004091BF 3BDB CMP EBX,EBX
So to use it, OpenECU flash 1.35. Then run the app. It will modifiy the ram for ecuflash so change the code. I dont know if this is breaking any ELUA or user agreements, so use at your own risk. The you can quit the program. The memory will stay modified for the entire instance of ECUFlash. If you close ECUFlash and re-open it, you will have to patch it again. The program is not a TSR-style program, it will not use any system resources or memory (except for when it is running). For vista users, you may need to use run as administrator. I dont have my UAC enabled, so i cant check if it needs admin rights. Im sure it does because it modifies another programs memory. This program only works with ECUFlash 1.35!! Any other versions will fail the Memory check. I would've just modified the ECUFlash.exe, but it is a compressed exe and ive never been able to actually pull code from a compressed/encoded executable. One last thing, im still using the Tactrix drivers from 1.29a. The drivers included in 1.35 make Tactrix cable not work at all. So Stick with the 1.29a drivers and install the ECUFlash 1.35 and cancel the driver install part. Maybe if enough people use it, ill write a loader to load and patch ECUFlash in just one click, instead if it being a seperate app.
*** Update *** New link with the static linked version (removes the need for the visual c++ runtime dll's)
Download : https://www.evolutionm.net/forums/at...1&d=1218646159
Last edited by silver_evo; Aug 13, 2008 at 09:51 AM.
#2
Evolved Member
iTrader: (2)
Join Date: Aug 2006
Location: Ohio
Posts: 526
Likes: 0
Received 0 Likes
on
0 Posts
This might be what I've been looking for.
Is that a known issue? What about the drivers from 1.34? Neither have been working for me. (Made a thread about it today, actually)
The drivers included in 1.35 make Tactrix cable not work at all. So Stick with the 1.29a drivers and install the ECUFlash 1.35 and cancel the driver install part
#3
I don't have this problem as I have a 1.3 cable, but thought I would post to say nice 1, as i've read a few people have had this issue, so fail play for solving the issue
#11
Evolving Member
Thread Starter
I know enough about assembly to get around a program. I have looked into the evo rom using sh2d. I didnt really dig around the source, it was like a million lines long. Id like to get into the rom program and look around. Maybe ill try again looking at it. Ive got like the next 2 weeks off work. All my programming work is shifting gears from evo to my physx/xna game engine im trying to piece together. I had last week off also, so that was evo week... But if i need to, ill look at some asm
#12
Evolved Member
iTrader: (2)
Join Date: Aug 2006
Location: Ohio
Posts: 526
Likes: 0
Received 0 Likes
on
0 Posts
I tried this out yesterday and couldn't get it to work for me.
The hack always quit with the following error:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
That was with 1.35.1650, the same version you were using in the screenshots.
I'm not sure what is different between my laptop and yours, but I ended up having to go back to 1.29a to actually read/write from my ECU.
My Tactrix cable has an 8 digit serial like yours as well, if that matters.
The hack always quit with the following error:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
That was with 1.35.1650, the same version you were using in the screenshots.
I'm not sure what is different between my laptop and yours, but I ended up having to go back to 1.29a to actually read/write from my ECU.
My Tactrix cable has an 8 digit serial like yours as well, if that matters.
#13
Evolving Member
Thread Starter
Sorry guys, i noob'd everyone, When i set the compilier options, i specified Dynamic linking ---> which means you NEED the visual c++ runtime dll's in your windows folder. I re-compilied with static linking, so it include the required functions in the EXE. Size went from 9.8k to 58k, so should have no more errors. Here is the new file.
Download : https://www.evolutionm.net/forums/at...1&d=1218646159
Download : https://www.evolutionm.net/forums/at...1&d=1218646159