We have Garmin Montana 600 now. It was updated from ver.4.70 to new ver.7.10 unsuccessfully. It had stuck on map loading. It was not problem. Device was loaded in forced mass storage mode and broken map was renamed. The defect of gmapprom.img was found after verifying checksum and after comparing of context it was found a part of outside code in map file. Device is fully functional after renaming of broken img file. And it is beginning of problem:
The first, it was not connecting to PC. All attempts for reload SW was failed including gcd, rgn and cure.
The second, there weren't any changes in system and data files. There weren't last position info, new waypoint and track. Even GarminDevice.xml was not changed.
The third, any changes on disk were disappearing. The files were successful copying to device and the files were successful deleting to device. But after reloading of device there were not any changes in file system.
The fourth, chkdsk was implemented. It had gave error: All OK but Cannot write boot sector.
The fifth, even RMPrepUSB had done his work well but Montana stuck on old file system after reloading. No changes was after date when device was unsuccessful updated.
Flash was checked for physical condition with proprietary tools. No errors took place.
Any suggestion?
The first, it was not connecting to PC. All attempts for reload SW was failed including gcd, rgn and cure.
The second, there weren't any changes in system and data files. There weren't last position info, new waypoint and track. Even GarminDevice.xml was not changed.
The third, any changes on disk were disappearing. The files were successful copying to device and the files were successful deleting to device. But after reloading of device there were not any changes in file system.
The fourth, chkdsk was implemented. It had gave error: All OK but Cannot write boot sector.
The fifth, even RMPrepUSB had done his work well but Montana stuck on old file system after reloading. No changes was after date when device was unsuccessful updated.
Flash was checked for physical condition with proprietary tools. No errors took place.
Any suggestion?