Konica Firmware Imaging Toolkit SUCKS

[mrwho]

Re: Konica Firmware Imaging Toolkit SUCKS

I just ordered a SanDisk Ultra II 256mb card, should be here tomorrow.
Im hoping it's just the cards i've been using. We have a c352 high mileage machine with a busted fuser drive that I'm using as a test machine so i dont brick my customers machine if something goes wrong.

There shouldn't be a bricked machine by experimenting on CF cards, but it's good to be on the safe side anyway.

[b3p0]

Re: Konica Firmware Imaging Toolkit SUCKS

Welp, card arrived. Loaded up the firmware and stuck it in the machine. Machine actually took it! However. ... after turning the machine on i see that the firmware version shown in tech mode doesnt match, but the checksum does. Thought maybe i got the wrong file, so i wrote zeros and used FIU again to write the firmware. Machine took it (downloading ....) powered it up and it shows the same thing.
So I thought maybe I have a bad file. I have another firmware that is actually more recent that I wanted to try. Wrote zeros, FIU the firmware onto the card all checks out good. Popped it in the machine and "Card error, please make sure the card." - Re-did this process about 15 different ways using FIU, cygwin, different card reader, different PC, it always is able to format and write the firmware, but the machine just wont take the card.
I'm ordering another card as of now.
At least it doesn't say "PC load-Letter"

[Darren King]

Re: Konica Firmware Imaging Toolkit SUCKS

The card should only be formatted with the Firmware Imaging Toolkit, not by right clicking and formatting it that way.
As long as the checksum is correct the firmware has been written properly.
Darren

[Mr Spock]

Re: Konica Firmware Imaging Toolkit SUCKS

On most firmware there is an adobe file that will tell you which files have been updated or list all with what you will see in service mode.
I have seen a few updates that only update one or two files and did not look like it updated correctly until I compared to the pdf file.
I do not think that the c352 was one of the affected machines by the disaster that hit japan a couple of years ago. They changed a few processors and not all the firmware worked on all machines. If it was then that is why the newer firmware failed. It was written for the new processor and not the older one. Try writing the first one again and see if it takes.

[TheOwl]

Re: Konica Firmware Imaging Toolkit SUCKS

Also, depending on how old the original firmware was can also give funny results.

You should always make sure that you load the machine from Phase 1 to Phase 2 and then to Phase 3. Never Phase 1 to Phase 3 as the Phase 3 firmware assumes that you have already loaded Phase 2 which contains fixes that Phase 3 doesn't but remain with the machine once the firmware been installed once.

Remember to also do your HDD Version Up procedures.