Minor Flashhack Bug

[NomakeWan]

Heya steveo,

While chasing down an issue on my '95 today I noticed a rather odd bug with Flashhack. It could just be me doing something dumb, but I figure I'll share and see what's going on.

So I was noticing that flashhack wasn't doing the fingerprint thing correctly anymore. When I would write it would always write the full memory space. I also noticed that in EEHack, I wasn't getting a read on my VIN or CAL ID. So I tried flashing a known-good tune, then reading the exact same tune back immediately afterward. Oddly, they did not match. The VIN and CAL ID memory locations were wiped to FF, and a random memory location at $1000 was set to 00.

I've attached both BINs to this post. 'write' is the one I tried to write to the car, and 'read' is the one I read from the car after writing.

In Flashhack's settings I had enabled:

Only write side(s) that have changed, Write E-SIDE, Write T-SIDE, Install recovery ROM on E-Side, Install Recovery ROM on T-Side, Verify patching regions against reference., Do not write 0xFF regions, Set unused regions to 0xFF, Read onboard EEPROM, Handle E-Side comms patch, Get vehicle fingerprint.

I assume 'Set unused regions to 0xFF' is probably at fault here, but if so, it shouldn't be nuking VIN and CAL ID. Plus I'm not sure what that $1000 set to 00 is all about.

[steveo]

newer versions of flashhack will, by default, update those values from your bin as part of the flash procedure (so they always match the values stored with your bin, which is what most users would expect, but was never happening before).

if for some reason your bin has been wiped at that area it will not touch it. it requires at least the seed/key (which is stored there) to be sane.

see "EE_WRITE_ONBOARD_EEPROM" and "EE_PROTECT_EEPROM" and "EE_PATCH_EEPROM_UNLOCK"

it's very new code so if it's glitching out on you go ahead and disable those things

i will look into why it failed for you but can you confirm how those options are set

[NomakeWan]

newer versions of flashhack will, by default, update those values from your bin as part of the flash procedure (so they always match the values stored with your bin, which is what most users would expect, but was never happening before).

if for some reason your bin has been wiped at that area it will not touch it. it requires at least the seed/key (which is stored there) to be sane.

see "EE_WRITE_ONBOARD_EEPROM" and "EE_PROTECT_EEPROM" and "EE_PATCH_EEPROM_UNLOCK"

it's very new code so if it's glitching out on you go ahead and disable those things

i will look into why it failed for you but can you confirm how those options are set

I don't see any of those options. This is flashhack 1.2 from your website. Am I missing something?

[steveo]

huh i thought i uploaded the new version

well if you are running 1.2 it shouldn't touch the onboard eeprom as it doesn't even have the code to do that

[NomakeWan]

There was a point where you had shared a 1.3, and I believe I did use it once, but you then said you found a bug with it and took it down and warned me not to flash with it. I had already done so. Maybe that's the root cause here?

I just always assumed that was why 1.2 was the only version you made available to the public. If you have a 'fixed' 1.3 then yeah, would love to test it out to see if that resolves the issue.

[NomakeWan]

Just gonna ping back. It sounds like you've got a newer version that never got released, so I'd love to give it a shot. Especially if it could potentially fix the issue with my '95 EEPROM from the old buggy copy of 1.3.