Quote Originally Posted by xclaudio View Post
I´ve solved others equipment with cure 3, thats is the reason why I went direct to this way.
A device which is 'bricked' by a corrupt file like a map or voice or gpx file is certainly fixable by loading it with cure fw, removing the offending file/s or reformatting then loading original firmware. However, I don't believe your problem of 'system software missing' was likely due to files at all, indeed it was in fact not due to corrupt file/s.

Do you think there is how to solve it?
As I wrote in Post #2 above, 'system software missing' message indicates a different type of 'bricking' which (usually) involves the main system software aka firmware contained in region 14 either being corrupt or empty, i.e. even missing entirely. Therefore there is no need in such a case to use cure firmware to enter MSM with the object of deleting files or formatting. Mostly when that message shows on attempted boot, it's quite sufficient to load original firmware to properly restore region 14 and that's usually immediately possible in preboot as an RGN file via Updater.exe because the device should have defaulted to preboot, which means no MSM available until region 14 is reflashed anyway.

Although it was probably not necessary for cure fw to be used, when you loaded the cure fw you did reflash region 14 however although MSM was then enabled the device still cannot start because that's the purpose of cure fw, to stall the boot by not loading the files required for a complete boot. Now you are reporting that you're unable to attain preboot and that may be for one or two sinister reasons, either your flash of cure fw was not good or the device has damage to the flash chip. There's another possibility that you're simply not doing it right to attain preboot. So I have to ask again "How are you trying to get into preboot?". By that I mean what method, i.e. are you holding the LOWER left corner of the screen?