fiat qubo locked after update

Hi, I have brought a ecu mjet QUBO 1.3 MJET 51832295_3546H780 you ? locked during the update, now I have found two files that have kindly posted here on the site, one specific for SPANSION S29CL016J and another not ? indicated, editandoli are not the same, on my ecu as the c memory'? a 58bw016 then not ? spansion(the difference I think is only in memory, but if someone clears your head I f? a pleasure), with both the file remains on, the light on the lock while the engine will not turn over not even.I wanted to try a full backup and eeprom riverginata, however, also place the file read and file that I tried to use.

the idea and simple, if your spansion then the file from the build must be spansion.
if you can build the file in the exact nn you need to do a virgin nothing/

But recognize you ? spansion see it from the flash?

the open and ec written ... so you have to retrieve bdm

what you read is not ? h780,but 354BH794

the flash it seems to me ok,second me you have to put a e2p virgin or you ? corrupted micro
on these when you do an update writes to the flash, and then a micro area

but the flash if the load with ecm titanium does not recognize it and does not find the driver this to me ? seemed weird.

I said a stupid flash recognizes it and with the chk exact even then I e2p or micro, someone has the micro to pass me since tomorrow I bring the car with the wagon?

note that the exact data are these
MJD6F3HW04P
Num SW: 354BH794
Dis FIAT: 51832295
Cod OMO: 6F3.H731

if you want to put a back up to try if all goes well,in the database of the forum fiat 500 c'? a back up
always hw04p,surely it should start,always 75hp and management turbo equal(instead of g.the point is not okay)
to see if in addition to the errors on the dpf ? everything is ok
the only thing if it is successful, you then have to defappare the file as your qubo has not...

probably ? managed to program the flash Num SW: 354BH794 replacing the 3546H780 with the update, but probably not ? worked fine with the micro.

Solved the problem by reprogramming the flash and micro software version before the attempted update, place in the files section of the original backup.