Flashhack - New LT1 flash tool

**yoheer** · 07-10-2020

Originally Posted by NomakeWan

E/T is for if you're flashing a BIN directly to the chips on the actual PCB, for example if your PCM is bricked and you have the equipment necessary to flash the EEPROM chips themselves.

This is clear. I have a flasher and I've restored my bricked PCM.

And what about RAW?

**NomakeWan** · 07-10-2020

Originally Posted by yoheer

This is clear. I have a flasher and I've restored my bricked PCM.

And what about RAW?

Ah, sorry, now I see what you mean.

Raw E-Side/Raw T-Side are what you would flash directly to the EEPROM chips.

E-Side/T-Side are for flashing over the ALDL (for example, if only one side or the other actually has changes; Flashhack does this automatically).

**yoheer** · 07-10-2020

thank you. now everything is clear.

**Casey96SS** · 08-20-2020

@steveo I am getting an error when writing bins to my PCM. Seems to have something to do with patches. I unapplied any patches I did have and now am only running the BLM locker. I get an error that says cannot install recovery ROM on T side. If I uncheck the setting in Flashhack about Verifying patching regions against reference it writes with no problem.

Is this anything I should be concerned about or need to fix? Thanks!
T side.jpg

**NomakeWan** · 08-20-2020

Are you using the latest XDF from Steveo’s website in TunerPro? If so you shouldn’t get that error.

That said, it’s nothing to be overly concerned about—the recovery patch is just a safeguard against a failed flash, we’re such a thing to occur. Without it your vehicle will run just fine, you just need to make sure the flash sequence completes successfully.

The error stems from Flashhack being unable to guarantee that the Recovery ROM won’t overwrite one of the patches you applied in the XDF. If you’re using the latest XDF from Fbodytech, this problem shouldn’t occur.

**steveo** · 08-20-2020

it's probably nothing, but i would recommend you uncheck 'install recovery rom on tside' rather than 'verify patching regions' until we figure out what's going on. you should post the bin that it's complaining about and i'll try to have a look at it later.

the recovery rom is probably only helpful if you totally lose ECM power during a flash write

if you uncheck 'verify patching regions' what you're doing is forcing the recovery rom patch no matter what. we don't know why it's throwing that error but something is different about your bin. the reason i wrote flashhack to be so picky about it? if we run into a bin that's been altered in a way we don't anticipate, the recovery rom might prevent it from booting, and that would brick it.

**Casey96SS** · 08-21-2020

Thanks for the replies guys. Yes running the XDF last modified on 5/16/20 in TunerPro.

Attached is the most recent bin that I loaded. Thanks for any input!

**steveo** · 08-22-2020

kur4o can you look at this code segment and see what's going on in his t-side? there might be other differences but these ones stick out.

there are differences at 0xB9DB.. the factory bin has:

Code:

8B 85 40 27 03 14 85 08 39 B6 01 9D 81 03 24 08 FE

this guys bin:

Code:

8C 85 40 27 03 BD 3C 89 39 B6 01 9D 81 03 20 0F FE

also at 0x4311. normal bin:

Code:

15 02 40

this guys bin:

Code:

BD FF 85

is this one of your patches or something else? i looked through a few factory bins and don't see any like that.

**kur4o** · 08-24-2020

I checked the bin and it does have some patches. Couldn`t figure which one. It does have some meta data of engine specs.

It looks like the bin have the mini rom patch too. I guess it was flashed with flashhack and than read back.

Only the owner of the bin can shed some light about the mods being done to the bin.

**WASyL** · 08-27-2020

having same issue here, one of my customers bins was read and flashed by EEhack flash tool like year ago (some tuning done and applied patches from EEX def file, now wanted to flash modified one (some spark and trans stuff) and recieved same error.

besr regrds

**NomakeWan** · 08-28-2020

Sounds like some incompatible patches, definitely. Two solutions:

1. Just do as steveo mentions, uncheck 'install recovery ROM' and flash that way. It won't attempt to install the recovery ROM so it won't throw that error. Flashhack is pretty robust even without the recovery ROM--the recovery ROM is really just to be able to recover from a power-off state (as in, you kill power to the PCM mid-flash). So don't do that, and you will be fine.

2. Use the difference tool in TunerPro to compare against a matching stock BIN for that year and type of vehicle, then port over the important changes to the stock BIN and save it as a new BIN. This will bring over what you want, and get rid of whatever erroneous code is throwing off the Recovery ROM.

**steveo** · 08-28-2020

the chance of the recovery rom being required to prevent bricking your ecm? almost none

the chance of something going wrong if we install the recovery rom blindly over unknown code modifications? substantial

that's why the program is paranoid about it

just disable it for that side of the ECM if you're getting that error. it'll still work for the other side.

fyi you are all reading back eehack-flashed bins from the ECM and further modifying them. eehack had warnings all over the place about that kind of thing, that is the reason we modified the bin during flash rather than screwing around with your actual bin on disk. now you're using some spotty eehack-modified bin because you ignored the warnings. why don't you just go get your original bins? you do keep track of them on disk, don't you?

**kur4o** · 08-28-2020

I am absolutely sure that non of the earlier patches interfere with the minirom patch. If the pcm have been flashed with flashhack and later read with eehack you have pre patched bin with minirom. NOt sure how to deal with it but maybe add a check of flashhack if the bin is already patched with minirom, than check if the bin is read with FF in place of 00[the case where eehack fills empty space], and than it can be considered unsafe to patch with minirom.

**steveo** · 08-29-2020

Originally Posted by kur4o

I am absolutely sure that non of the earlier patches interfere with the minirom patch. If the pcm have been flashed with flashhack and later read with eehack you have pre patched bin with minirom. NOt sure how to deal with it but maybe add a check of flashhack if the bin is already patched with minirom, than check if the bin is read with FF in place of 00[the case where eehack fills empty space], and than it can be considered unsafe to patch with minirom.

it does those things, it checks if the mini rom is installed and informs the user and doesn’t care about the extra ffs

**steveo** · 09-07-2020

something to read if your flash write fails and you're panicking

i recently had a user fail during an erase, and for some reason decided to press 'read' next, which is a bad choice, since the read procedure does reboot the ECM when it's done.

http://fbodytech.com/flashhack-lt1-p66-error-recovery/