MSM is simply Mass Storage Mode, the normal way that the nuvi connects to the PC and communicates like any other USB device.
That's method 4, using the modded boot.bin made as an rgn to flash from microSD. I modified the boot.bin as per kunix's method described in P#33 here: [Only registered and activated users can see links. ]. BTW, reading your comment in P#19 [i.e. 'drag the 113201000390.rgn (downloaded from Neil) over the Webupdater.exe'], that makes me think that you've used my modded boot.bin RGN file that way. It's only meant for use with the Garmin folder on sd card, so did you do method 4 correctly as i said in P#16? That rgn file contains only the boot.bin [ramloader] modified so that it doesn't load the unit firmware, so if you've used it with WU or Updater.exe it will only update the unit's 'Boot BLK' and 'X-Loader'. The 'System' component of fw remains unchanged therefore you would receive the message that the update's been successful but subsequently the device again reports 'system software missing' [because the system software hasn't been touched, only the other parts of fw were]. If you've used the modded boot.bin rgn that way without the sd card with Garmin folder on it inserted in the nuvi, then please try it exactly as i said in P#16.
It's workable if that is indeed the problem and if you can do the r & r work described here: [Only registered and activated users can see links. ]. Assuming the symptom 'system software missing' is showing a physical problem with the flash chip, then for practical purposes the device is effectively toast quite frankly. What Alex describes in that thread is for very advanced users with specialist equipment and ability.The idea is dismantling the device and get the internal storage device out, connect it to a pc and format it.
Do you think it's workable?
Unfortunately as more and more efforts to resurrect your nuvi fail, the chances of a damaged flash being the cause are becoming greater. Let's not give up yet though. The majority of units displaying that message are the result of an imperfect fw update and that's increased by the circumstances where it happened immediately following a power-down as you said while updating. So we should continue trying to fix this unit as non-invasively as possible until kunix has time to intervene, the more things we tick off the less he has to do. It does concern me that you had MSM access when you were in contact with Garmin support and subsequently lost it before posting here. That means one of two things of course, (i) the unit was 'bricked' further during or subsequent to Garmin's phone efforts and prior to you posting here by something you've attempted, or, (ii) most concernedly, the flash chip quite co-incidentally failed while updating with GarminExpress [it wasn't a case of 'power-down' as you said, rather a communication failure because the flash memory failed mid-update] and that there has been further deterioration of the chip which resulted in MSM also being lost. In that case all this is for naught i'm afraid, but we should regard it as a software problem until all possibilities are exhausted. So let's bat on:
Did you try [Only registered and activated users can see links. ] from the cure3 thread? If no, give it a go but it's quite unlikely it'll work to gain MSM. If it doesn't, try the version of QuickCure with flasher from P#36 here: [Only registered and activated users can see links. ].
Another thing to try is to make an rgn file containing only fw_all.bin & fw1_resources.bin and try flashing that with updater.exe in pre-boot. Make it with RGN_Tool as per the pic below, save it as 113201000390.rgn then drag onto Updater.exe as usual.
[Only registered and activated users can see links. ]
You should also read the 'Running programs from SD on nuvi' thread from P#35 by the user nuvi1100; and this thread too: [Only registered and activated users can see links. ].
Note: All above posts moved to new thread from [Only registered and activated users can see links. ].
Bookmarks