Quote:
Originally Posted by Jagaer
Ajomad
I've updated your 1B, and it looks correct, but it still may not work.
If you used the USB script to download the 1B file, it may not "grab" the right part of the hex file (which means the keys in the file are not correct)
|
Hello Jagaer,
a) It seems to be that the file you sent me for download is exactly the same as I modified
(just changing at offset x1A the VIM data), that I had already tested and didn't work.
In fact your 1b file genereates the same code as my previous test.
What I realised seeing the 1b file you interchanged with Axlbmw is:
original one: ...... 123456. 1234567.x.1234567............200
the modified: ...... 773487. 2873863.x.C096398............200
bytes changed: at offsets x'08' x'10' and x'1A'
At the same way, the files interchanged with me were:
original one: ...... 123456. 1234567.x.1234567............200
the modified: ...... 123456. 1234567.x.E457511............200
bytes changed: at offset x'1A' only
I thought offsets x'08' and x'10' were also to be modified and the reason to ask your for help.
b) also you says:
"If you used the USB script to download the 1B file, it may not "grab" the right part of the hex file..."
YES, I used the USB script created by 'portalseo' to extract the 1b from the car.
At a previous Post, your also wrote:
"The USB stick method has failed in the past, as it cuts the 319 byte file out of the
VIN_generalPersistencyData_DiagnosticSWTController file.
If there is more than one section in the file which matches the header bytes, it will return the first
one (which may not be correct).
At this point you would need to follow one of the other methods to retrieve the full file above,
and "cut out" the right part of the file to make the correct 1B file for your car. "
Sorry, Do you have a way to download the full file from the car in order too 'cut out' properly ?
Many thanks