Pages: 1 [2] 3 4
Author Topic: Me7.1.1 Immo problem  (Read 33493 times)
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #15 on: September 02, 2014, 01:55:51 PM »

Iv just got my file back from the tuner who modified it.. And that seems to be 512bytes with IMMO off, I used that python script i seen above. It looks like he messed it up, So was the immo good to go in the fist place? The car kept cutting out after a conversion, And i took the previous owners words with a pinch of salt when he said the IMMO was removed (It wasnt even wired up at the time )

Code:
EEPROM Status:
- VIN: WVWZZZ1JZ4D010174 (VW 2004 - Golf and Bora 4, Bratislave, Slovakia)
- SKC: 06050
- Immobiliser: Off
- Checksum: OK
- Size: 512bytes
- Cluster Code: BA DD 32 C5 E2 C8
- P0601 DTC: not set
- Immo ID: WZ7Z0C8204091

Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #16 on: September 02, 2014, 02:54:19 PM »

It might be ok, kompresseds post suggests your EEPROM is meant to be 1024bytes and padded with FFs, so it may still be wrong. (Your tuner may be like me, too lazy to look at a data sheet and just assumed it was a bad read, truncated the file a 512bytes and fixed the checksum...then again kompresseds may be wrong about 1024 being correct).

I would try and get a bit more info on your EEPROM before flashing the new bin on.
Logged
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #17 on: September 02, 2014, 03:01:56 PM »

See im unaware, the original one that was pulled off is 512 with correct checksums. (When i say origional, I mean modified by previous owner)
Then i sent it away and received it back at 1024 with bad checksums.

So do i just need to padd out the first file to 1024? Or am i meant to flash another 512?

Im confused.
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #18 on: September 02, 2014, 03:06:40 PM »

The file must be 1024 with the last 512 being all FF
Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #19 on: September 02, 2014, 03:26:03 PM »

Is it litterally a normal EEPROM, but padded, or is the structure different too?
Logged
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655


« Reply #20 on: September 02, 2014, 06:45:53 PM »

this whole thread is 2 pages of nonsense when fixing and correcting whatever idiot touched that file before would take about 10 seconds.
btw, i may be wrong? use your fucking brain and stop being "lazy" and you would know 100% that im correct.
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #21 on: September 02, 2014, 09:51:55 PM »

this whole thread is 2 pages of nonsense when fixing and correcting whatever idiot touched that file before would take about 10 seconds.
btw, i may be wrong? use your fucking brain and stop being "lazy" and you would know 100% that im correct.

Thanks for clearing that up, K0m. I thought I was loosing my mind Smiley
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #22 on: September 03, 2014, 02:31:49 AM »

this whole thread is 2 pages of nonsense when fixing and correcting whatever idiot touched that file before would take about 10 seconds.
btw, i may be wrong? use your fucking brain and stop being "lazy" and you would know 100% that im correct.

I hope your not referring to me with that comment? I'm very new to this, and I'm learning.

So can i just pack a good 512 file out to 1024 (The other 512 all being FF ) and flash it to the eeprom?

 I really appreciate the help guys.

Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #23 on: September 03, 2014, 02:36:19 AM »

It's ok, he's referring to me Wink
Logged
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #24 on: September 03, 2014, 08:57:49 AM »

Oh okay, I literally have no idea why i keep getting this error trying to read this eeprom! i dont want to write to it incase it messes something up.

Reading EEPROM ... FAIL. (error=0x40B01)

Cheers.
Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #25 on: September 03, 2014, 09:05:07 AM »

Have you snipped off the resistor mentioned in the r32 thread linked above?
Logged
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #26 on: September 03, 2014, 09:33:42 AM »

Yeah, it was just a 000 surface mount resistor, So a link basically.
Logged
N1CKY
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #27 on: September 03, 2014, 10:02:27 AM »

Okay so iv had a go at fixing the checksums etc, Can someone check it over please?
Logged
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655


« Reply #28 on: September 03, 2014, 10:45:31 PM »

Okay so iv had a go at fixing the checksums etc, Can someone check it over please?

chksums are not the issue.
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #29 on: September 03, 2014, 11:03:57 PM »

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.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.024 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)