thank you

Well everything finally arrived a couple of days ago and I got my cable built and was able to successfully communicate with the new ecu on the bench. Reads are not successful as immo is enabled, but that's fine, I know it is working at least. I started working on cloning my existing immo to the new ecu, still learning about that.

Because I was comparing EEPROM images between the ecus, I was taking a closer look at them with a hex editor and noticed my car's ecu eeprom says REVO right in it near the bottom. Guess that answers the question why I am not able to read the flash via OBD2. Unfortunately REVO maps cannot be changed without the REVO SPS device from what I can find (unless someone knows a way to do this with nefmoto? ). I am planning to dump the REVO software using bootmode, would anyone be interested in seeing that if I am allowed to post it here?

Edit: interesting note, according to 95040tool.exe my car's ecu eeprom has invalid checksum(s). I guess the REVO software does not care about checksums and does not check them. Kind of scary.

So I got a better power source today and Galletto was still unable to write the flash in bootmode. Strangely it would instantly fail write after erasing the flash. On a whim I tried a different .bin (both files I got from here in original ECU file section and both are 032LP files) and it worked! Also it worked on my ATX PSU which I switched back to after it still failed with the new power source. So the problem is the file all along.

revo stores boost/timing settings in eeprom so you can manually adjust them without sps
but if there is an attempt to read flash via obd (not bootmode), this eeprom section probably overwrited with flasher and after that you got default timing/boost

i was playin a few years ago with revo tune. any protection can be easily cracked but there is no reason to do that cos no interesting stuff