stuydub
Full Member
Karma: +25/-12
 Offline
Posts: 230
|
 |
« Reply #870 on: May 31, 2021, 11:23:34 PM »
|
|
|
A week or two ago i was messing about trying to write an immo file to my backup ECU, no luck.
I got a clean read, and i know how to bootmode an ECU. I am also positive i got it in boot mode, though i just could not get it to write. Tried different baud modes and versions of the program but no luck. I think the error code was 0x07. Any advice? I have probably tried for over a few hours differnt things, settings etc.
I have only tried over OBD, if anyone has some tips please do enlighten me. Otherwise i'm probably going to try a bench setup and flash it that way.
trying to bootmode on the car i guess and then using obd ? . This has never worked for me i just bench it or parcel shelf it depending where i am lol |
|
|
|
|
Logged
|
|
|
|
|
Sandstorm3k
|
|
« Reply #871 on: May 31, 2021, 11:27:44 PM »
|
|
|
trying to bootmode on the car i guess and then using obd ? . This has never worked for me i just bench it or parcel shelf it depending where i am lol
Yes exactly, I figured why wouldn't it work as it seems others have got it to work. Thanks for your input, i'll give it a go on the bench soon. |
|
|
|
|
Logged
|
|
|
|
Home Built by Jeff
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #872 on: June 08, 2021, 10:00:06 PM »
|
|
|
Hi,
I am attempting to put a 4.2 V8 in my Boxster. I have managed to setup a bench flashing cable and the Nefmoto flasher can read the basic info but I need to remove the immobiliser before I can go any further.
I am currently getting the following error on me7eeprom.exe
C:\Users\LENOVO\Downloads>me7eeprom.exe --OBD -r -p 3 read.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM3
I have comfirmed that my cable is going through COM3. The cable that I am using is a blue KKL VAG-COM for 409.1
Any help with what I am doing wrong would be greatly appreciated. I will be posting the whole process on my YouTube channel in detail so hopefully it will be able to help out others as well.
Jeff
|
|
|
|
|
Logged
|
|
|
|
|
Blazius
|
|
« Reply #873 on: June 09, 2021, 05:35:16 AM »
|
|
|
Hi,
I am attempting to put a 4.2 V8 in my Boxster. I have managed to setup a bench flashing cable and the Nefmoto flasher can read the basic info but I need to remove the immobiliser before I can go any further.
I am currently getting the following error on me7eeprom.exe
C:\Users\LENOVO\Downloads>me7eeprom.exe --OBD -r -p 3 read.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM3
I have comfirmed that my cable is going through COM3. The cable that I am using is a blue KKL VAG-COM for 409.1
Any help with what I am doing wrong would be greatly appreciated. I will be posting the whole process on my YouTube channel in detail so hopefully it will be able to help out others as well.
Jeff
Take the cable apart, this program will NOT work with ch340 chip. And if it has FTDI , you probably have to bootmode. EDIT: CH340 works absolutely fine with 1.31. Confirmed. |
|
|
|
« Last Edit: August 09, 2021, 07:28:06 PM by Blazius »
|
Logged
|
|
|
|
Auriaka
Full Member
Karma: +17/-2
Offline
Posts: 113
|
|
« Reply #874 on: June 09, 2021, 09:58:27 AM »
|
|
|
Hi,
I am attempting to put a 4.2 V8 in my Boxster. I have managed to setup a bench flashing cable and the Nefmoto flasher can read the basic info but I need to remove the immobiliser before I can go any further.
I am currently getting the following error on me7eeprom.exe
C:\Users\LENOVO\Downloads>me7eeprom.exe --OBD -r -p 3 read.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM3
I have comfirmed that my cable is going through COM3. The cable that I am using is a blue KKL VAG-COM for 409.1
Any help with what I am doing wrong would be greatly appreciated. I will be posting the whole process on my YouTube channel in detail so hopefully it will be able to help out others as well.
Jeff
On 24v vr6 ecus and some 4.2 ecus I have had to remove a resistor band on bottom of the ecu to allow bootmode. There is a thread on here in regards to me7.1.1 ecus and have to rem ove the 010 band. I fought a 24v vr6 ecu for hours before I found that and did it... 5 min later, its happy as a clam and I can do whatever |
|
|
|
|
Logged
|
|
|
|
Home Built by Jeff
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #875 on: June 10, 2021, 12:57:13 AM »
|
|
|
I didn't realise I could remove the chip from my cable. I will give that a go and I will have a look at the 010 resistor band as well and let you know how I go.
|
|
|
|
|
Logged
|
|
|
|
Briandutch
Newbie
Karma: +0/-1
Offline
Posts: 5
|
|
« Reply #876 on: June 23, 2021, 12:14:17 PM »
|
|
|
Please help me further..
I don't know what this error is...
C:\ecu immo>me7rw --bootmode -wp2 immoOFF.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x01)
Closing COM2
|
|
|
|
|
Logged
|
|
|
|
fredgilb
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #877 on: July 11, 2021, 06:47:33 PM »
|
|
|
I was able to Immo off and vin add. When I attempt to write the file I get these responses.
I'm going thru ODB plug. First is with no ground on pin 24 \. second with ground on pin 24
Am I correct that grounding pin 24 & using obd plug is workable?
PS C:\Users\fredg\Downloads> .\me7_95040.exe --bootmode -wp3 9542.BIN
Ver: 1.31
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3
PS C:\Users\fredg\Downloads> .\me7_95040.exe --bootmode -wp3 9542.BIN
Ver: 1.31
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... uC identification response = 0xE5. Unknown ID. (error=0x01)
If it's any help, me7.5 2001 beetle
|
|
|
|
|
Logged
|
|
|
|
|
Blazius
|
|
« Reply #878 on: August 09, 2021, 07:34:32 PM »
|
|
|
I would like to say and absolutely confirm that CH340 based cable will work with 1.31 on bench harness on ME7.5. This week I added another genuine FTDI "dumb" cable to the collection for eeprom stuff.. well it turns out it has all kinds of issues, not even ME7Logger wants to work properly... so I am like right, I know for a fact ch340 works with ME7Logger, and sure enough it connects and works every single time and speed any init. In a span of 3 hours I got the genuine FTDI chip working like 3 times and never again, all kinds of combinations - latency, buffer sizes it just buggy as hell( Windows XP SP3 32bit with latest FTDI VCP drivers for windows xp)
So I am like right, lets give the ch340 a go, like I did 2 years ago but that was in car OBD/bootmode and with 1.4. Sure enough using 1.31 it read eeprom just fine thru OBD bench and wrote it thru bootmode bench.
Wanna mention that you will have to set the baud to 57600 or it will fail on initializing registers. CH340 to the rescue.
|
|
|
|
|
Logged
|
|
|
|
TeknoFi
Full Member
Karma: +1/-3
Offline
Posts: 85
|
|
« Reply #879 on: August 20, 2021, 09:14:02 AM »
|
|
|
The solution for removing immo from 06A906032HJ / ME7.5 with infineon processor:
You need only VAG-KKL blue cable, take the ecu out of the car and put it to the boot mode. Since there was an Infineon cpu in there its trickier, a 10k resistor had to be placed between the bootpin and the ground. Otherwise it may go to boot mode but it does not respond to anything.
With ME7EEPROM I read the eeprom out, then with eepromtool_04 I removed the immo from the binary. I wrote the eeprom back with ME7EEPROM and the car started, the immobilizer was permanently removed. Here's the information if anyone is looking for help ...The engine was an AUM.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #880 on: August 20, 2021, 11:12:28 AM »
|
|
|
You only need the 10k resistor if you are keeping the pin grounded all the time. If you remove the ground as soon as it's in bootstrap mode, then you don't need the resistor.
|
|
|
|
|
Logged
|
|
|
|
bazgreener
Newbie
Karma: +0/-0
Offline
Posts: 10
|
|
« Reply #881 on: November 20, 2021, 07:05:50 AM »
|
|
|
Hi all, looking for some help in reading/writing my me7.5. I originally read the eeprom with vag commander, i then used eepromtool_04 to set the vin and switch the immo off which appeared successful-
C:\Users\shelg>eepromtool_04 --in ecu_off.bin
Read in 512bytes
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo2
- VIN: TRUZZZ8NZ11042596 (Audi Hungary 2001 - TT 99-06, Gyor, Hungary)
- SKC: 01392
- Immobiliser: Off
- Checksum: OK
- Size: 512bytes
- Cluster Code: 11 20 3B 59 77 94 BC
- P0601 DTC: set to 00 01
- Immo ID: e
- Softcoding ID: 65408
- Tuner Tag:
- Flash Programming (successful): 0
- Flash Programming (attempts): 0
But now i am having trouble writing back the file. I tried using commander again but it won't talk to the ecu in boot mode so i then tried ME7_eeprom but get the following error when i try to read-
C:\Users\shelg>ME7EEPROM --OBD -r -p 3 95040.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM3
I am using a newer vag com lead HEX-V2 which i have set in VCDS to not use intelligent mode. I have also tried using the vag commander lead but get the same error. I can still talk to the ecu via k-line with both commander and with vcds so i assume my bench connections are all ok. This is my first time doing anything like this and i have spent many hours trying to find the answer.
Any advice greatly appreciated.
|
|
|
|
|
Logged
|
|
|
|
R32Dude
Full Member
Karma: +45/-10
Offline
Posts: 248
|
|
« Reply #882 on: November 20, 2021, 06:07:50 PM »
|
|
|
The ecu needs to be in boot mode to write to the eeprom. The fact that vcds still talks to it means that it is not in boot mode.
|
|
|
|
« Last Edit: November 20, 2021, 06:10:04 PM by R32Dude »
|
Logged
|
|
|
|
bazgreener
Newbie
Karma: +0/-0
Offline
Posts: 10
|
|
« Reply #883 on: November 21, 2021, 01:29:30 PM »
|
|
|
The ecu needs to be in boot mode to write to the eeprom. The fact that vcds still talks to it means that it is not in boot mode.
Thanks r32dude, I'm pretty sure I had it in boot when I tried to write the file but I'll give it another go. It wasn't in boot when I tried vcds. |
|
|
|
|
Logged
|
|
|
|
R32Dude
Full Member
Karma: +45/-10
Offline
Posts: 248
|
|
« Reply #884 on: November 21, 2021, 05:44:17 PM »
|
|
|
Its best to use a resistor for bootmode. 4.7k to 10k. The resistor allows you to no longer worry about removing the ground from the pin at the correct time. This avoids a false bootmode
|
|
|
|
|
Logged
|
|
|
|
|
