Sadly, if some files are corrupted (or even worse, the entire partition is not recognized), fw_all.bin crashes before "rebooting". And no mass storage mode is available.
GarminCure3 patches fw_all.bin and makes it think that it was called with R12=0xC. In this case fw_all.bin enters the mass storage immediately, while not reading any files.
But if NV is severely corrupted, it could still crash. There are other methods which could help in this case, but they also need pre-boot mode.
What happened before you formatted it the first time, why did you format it?
You have to navigate to get to the good.
[Only registered and activated users can see links. ] Password for my files: gpspower.net
Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
The very first indication of a problem was when I turned on the device and it went into the white touchscreen calibration view. At first the device was unresponsive to attempts to calibrate it. After sitting a while it responded to calibration. But then device was caught up in a loop of loading the maps, rebooting, loading maps, etc.
By and by I did countless iterations of resetting, update attempts, screen recalibrations, etc. While attempting to force software updates in pre-boot the device never connected to the PC long enough to do that. When connecting in pre-boot mode the nuvi popped up in the System's Device Manager as a Garmin but then quickly popped out and the device went into the white calibration screen (I've read of others encountering this same issue but none were ever resolved).
Perhaps when loading GarminCure3, the device was in pre-boot just long enough to execute the program to turn it into a mass storage device. But now, because of a touch screen issue, I am no longer able to get into pre-boot to reload the original firmware. The device is too old to justify purchasing a replacement touchscreen to satisfy my curiosity though.
I suspect the same as you, The digitiser on the touchscreen is faulty.
If you relate to keyboard it it has "stuck key".
The difference between stupidity and genius is that genius has its limits.
need help flashing the firmware for 1460, using updater or cure, it pop up the device for sometimes, but when I pressed ok, it said no available update. can you give advice what I've done wrong?
While the device is detected, i can not see any storage device that i can open and delete the file...
i have Asia Unit, my garmin ID is xxxx. Which one is asia unit?
NOTE:Id removed by Mod: Don't post units ID on public forums.