This may be overkill of too much info, but you might be able to create a good bin by using the tunerpro bin stacker to take the first 32kb saved from tunerpro (calibration) and the 96kb above that (code) from a matching bin downloaded from a release thread on this site. I havnt tried this, I normally use linux for this. Any tool that can achieve the following will work.
Code: Select all
[antus@antus ~]$ ls -lh c*.bin
-rw-rw-r--. 1 antus antus 128K Apr 14 13:16 calibration.bin # contains a good calibration (0->32kb)
-rw-rw-r--. 1 antus antus 128K Apr 14 13:16 code.bin # complete bin, contains good code, wrong calibration (32->128kb)
[antus@antus ~]$ dd if=calibration.bin of=1.bin bs=1k count=32 # if=infile=calibration.bin of=outfile=1.bin bs=blocksize=1k, count=32 of them. Total 32kb.
32+0 records in
32+0 records out
32768 bytes (33 kB) copied, 0.000218337 s, 150 MB/s # dont worry that this says 33kB.
[antus@antus ~]$ dd if=code.bin of=2.bin bs=1k count=96 skip=32 # from code.bin to 2.bin. skip 32 1k block, then copy 96 1k blocks
96+0 records in
96+0 records out
98304 bytes (98 kB) copied, 0.000704095 s, 140 MB/s
[antus@antus ~]$ (cat 1.bin ; cat 2.bin ) > fixed.bin # create a stream from the contents of 1.bin then 2.bin and save it to fixed.bin. This concatenates the chunks.
[antus@antus ~]$ ls -lh fixed.bin
-rw-rw-r--. 1 antus antus 32K Apr 14 13:17 1.bin
-rw-rw-r--. 1 antus antus 96K Apr 14 13:17 2.bin
-rw-rw-r--. 1 antus antus 128K Apr 14 13:16 calibration.bin
-rw-rw-r--. 1 antus antus 128K Apr 14 13:16 code.bin
-rw-rw-r--. 1 antus antus 128K Apr 14 13:17 fixed.bin