N1CKY
Jr. Member
Karma: +1/-0
 Offline
Posts: 31
|
 |
« Reply #30 on: September 04, 2014, 04:03:16 AM »
|
|
|
0x12 and 0x22 are supposed to be 02, not 03. Someone ran this file through one of those immo off programs twice and messed it up. Start with the original read, change bytes 0x12 and 0x22 from 01 to 02, correct the checksums, and you're done.
The problem is, I dont have the original read. Below is the most raw one i have (Still not raw, prev owner modded it) buts its only 512bytes can i pack it out to 1024 and correct the checksums? I appreciate your help lads, I really do. |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #31 on: September 04, 2014, 04:54:21 AM »
|
|
|
Just had another look at the dumps N1cky pulled, and extended my eeprom tool to attempt to process R32 bins. Few oddities:
- in DUMP1.BIN, checksum is wrong in pages 1C and 1D - these lines are all FF, am I right in assuming checksum is not calculated for these lines too?
- in nicky.bin, the lines 1C and 1D are not all FF and have a checksum calculated.
- DUMP1.BIN and nicky.bin also differ in pages 0x11 and 0x14, nicky.bin appears to have a date in 0x14
- in DUMP1.BIN and nicky.bin, they start with 5 bytes of 0x30, all other immo3 bins' that I've seen start with 5 bytes of 0x20.
Have a look at the attached bin.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #32 on: September 04, 2014, 05:20:48 AM »
|
|
|
Just had another look at the dumps N1cky pulled, and extended my eeprom tool to attempt to process R32 bins. Few oddities:
- in DUMP1.BIN, checksum is wrong in pages 1C and 1D - these lines are all FF, am I right in assuming checksum is not calculated for these lines too?
- in nicky.bin, the lines 1C and 1D are not all FF and have a checksum calculated.
- DUMP1.BIN and nicky.bin also differ in pages 0x11 and 0x14, nicky.bin appears to have a date in 0x14
- in DUMP1.BIN and nicky.bin, they start with 5 bytes of 0x30, all other immo3 bins' that I've seen start with 5 bytes of 0x20.
Have a look at the attached bin.
Iv just had a look and tried to understand what you mean, But my understanding of the file system layout is slim to none. I see the differences in a hex editor that you pointed out but that's about it. I'm hoping one of the more experienced members can shed some light. |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #33 on: September 04, 2014, 10:57:30 AM »
|
|
|
Most of that is random commentary as I've been trying to figure out what a 1kb bin should look like- although looking at it again, it looks like the bin I attached above has checksums calc'd for 1c and 1d too, which I think is wrong. Try writing the attached eeprom and see if that solves your problems.
Kompressed/f1torrents - any more info on what a 1kb bin should look like, as the ori is unavailable?
|
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #34 on: September 04, 2014, 11:04:29 AM »
|
|
|
heres a gimme. proper 5p08c3 e2p file.
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #35 on: September 04, 2014, 11:12:31 AM »
|
|
|
thanks  |
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #36 on: September 04, 2014, 04:43:47 PM »
|
|
|
I really appreciate your help on this guys, so in theory can i modify evan.bin with my vin/skc immo off etc correct the checksum and everything be okay? I know the vin and skc etc dont need to be changed but it will give me a very similar file to what was stock.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #37 on: September 05, 2014, 09:17:03 AM »
|
|
|
Just a little update guys, For anyone experiencing the same error as me: Sending Loader + MonitorCore ... FAIL. error=
0x40001
I managed to fix it, After ALOT of trial and error with different cables/drivers/computers baudrates etc.
I set both my cable (Device manager/COM4/port settings) and the argument in argdubs tool to 19200. Hoora! 5 consecutive dumps!
Now i just need help with the file, I wouldn't mind spending some money to pay for someones time to help me out?
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #38 on: September 05, 2014, 10:17:10 AM »
|
|
|
I've compared your files (dump1 and nicky) with evan.bin, neither nicky or evan have a block of padding at 1c and 1d, so I've taken dump1, zero'd those pages and checksummed them as normal. Going through evan.bin, it has nochecksum and backup pages as normal for immo3, so I'm cautiously confident that this file is ok. My only question is the 30 30 30 30 30 at the start of dump1 and nicky.bin - std immo3 bins usually start 20 20 20 20 and the evan.bin starts 30 51 31 30 31 - but this may be irrelevant. Give it a try with this version If not, maybe try evan.bin. latest version of the eepromtool script attached too - this is still very hacky until I get enough 1kb bins to properly figure out what they should look like, hopefully getting another couple soon |
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #39 on: September 10, 2014, 09:02:00 AM »
|
|
|
Right, I believe i now have a working file. But a new problem arises! When argdubs tool finally lets me write a file to the eeprom without failing, i read it back to check the file was the same. IT WAS NOT! It didnt even write the file, It says it did in the tool. But reading it back tells me otherwise. Iv almost had enough now, Is there reputable person i can send this to in the UK? I have the file i need to write now (Thanks DDllenger) but i just cant write the thing!
|
|
|
|
|
Logged
|
|
|
|
seishuku
Full Member
Karma: +13/-0
Offline
Posts: 131
|
|
« Reply #40 on: September 11, 2014, 03:21:26 PM »
|
|
|
Writing must be done in boot mode...
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #41 on: September 12, 2014, 02:52:21 AM »
|
|
|
Hello, I was writing in boot mode. The ECU enters bootmode fine, It even says the write is successful. But it does not actually write.
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #42 on: September 12, 2014, 04:39:13 AM »
|
|
|
Assume you've diff'd the file you read back and dump1.bin from above and its the same? Tried a different version of argdubs tool? Any error messages? You could try writing with vag eeprom tool - not sure if that does ECUs but might be worth a look.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #43 on: September 23, 2014, 09:43:59 AM »
|
|
|
Im at my witts end now, I need the car started before Friday and i have no idea what's going on. It will fire on brake cleaner so its sparking, The injectors are getting live and fuel pump is running as it should. Im getting quite a few DTC's ill pop them below for people to look at, The interesting one is the check coding of ECU's. The immo file im using is a donor file ddilenger gave me, I got a friend to write it with a programmer rather than argdubs tool, But when i read the file back with argdubs there was 4 differences, Ill attach them for you to look through. I dont want to give up, But im so damn close! Address 01: Engine Labels:
Control Module Part Number:
Component and/or Version:
Software Coding:
Work Shop Code:
VCID: 55A167DFACF48DB6975
13 Faults Found:
18058 - Powertrain Data Bus
P1650 - 004 - Missing Message from Instrument Cluster No dash in
18055 - Check Coding of ECUs on Powertrain Data Bus No idea?
P1647 - 008 -
16497 - Intake Air Temp. Sensor (G42) probably wasnt plugged in
P0113 - 002 - Signal too High
17834 - EVAP Purge Valve (N80) Dont have one
P1426 - 004 - Open Circuit - Intermittent
19475 - Valve for Exhaust Flap 1 (N321) Dont have one
P3019 - 004 - Open Circuit - Intermittent
17841 - Secondary Air Pump Relay (J299) Dont have one
P1433 - 004 - Open Circuit - Intermittent
17530 - Oxygen (Lambda) Sensor Heating; B2 S2 Wasnt plugged in when i last tried it, Was previously
P1122 - 004 - Open Circuit - Intermittent
17526 - Oxygen (Lambda) Sensor Heating; B1 S2 As above
P1118 - 004 - Open Circuit - Intermittent
17606 - Oxygen (Lambda) Sensor Heater Circuit: B1 S2 As above
P1198 - 004 - Electrical Malfunction - Intermittent
17607 - Oxygen (Lambda) Sensor Heater Circuit: B2 S2 As above
P1199 - 004 - Electrical Malfunction - Intermittent
17951 - Angle Sensor 1 for Throttle Actuator (G187) No idea, Throttle works
P1543 - 002 - Signal too Small
17580 - Angle Sensor 2 for Throttle Actuator (G188) Signal too Low As Above
P1172 - 002 -
16502 - Engine Coolant Temp. Sensor (G62) Probably wasnt plugged in when last cranked
P0118 - 002 - Signal too High |
|
|
|
|
Logged
|
|
|
|
|
f1torrents
|
|
« Reply #44 on: September 23, 2014, 12:18:25 PM »
|
|
|
None of those codes have to do with the immo off file.
|
|
|
|
|
Logged
|
|
|
|
|
