Perhaps erasing region 41 would fix it, but that will lose its registration and unlock codes. I regard it as 'last resort' and wouldn't do it solely because of slow boot.
Printable View
Perhaps erasing region 41 would fix it, but that will lose its registration and unlock codes. I regard it as 'last resort' and wouldn't do it solely because of slow boot.
Better back it up first.
Lol, thanks. 'Cos maybe San Francisco is greener than he seems ..... ;))
That did you keep in mind under restoring of factory default? Due to a huge time of Reset on the screen I think you did not reset device properly. Did you perform to return to default settings in menu only? Or did you make master reset with finger holding on lower left corner when turn on device?Quote:
Originally Posted by SanFrancisco [Only registered and activated users can see links. Click Here To Register...]
Sorry for the long absence, guys. Have been buried under work, both professionally as well as privately.
Have not tried that yet. Obviously, will backup rgn 41 first before erasing it, as suggested by o4i.Quote:
Originally Posted by Butters [Only registered and activated users can see links. Click Here To Register...]
The device was reset to factory default by pressing and holding the lower right hand corner of the screen while switching on power.Quote:
Originally Posted by Grizzzly [Only registered and activated users can see links. Click Here To Register...]
Unfortunately, erasing rgn 41 did not speed up the boot process. When connected to Garmin Express, its entitlement to Lifetime Mapupdates is still recognised though.
Apart having to go through screen calibration, entering the locale and waiting for first satellite fix at first boot after erasing rgn 41, I notice no difference in behaviour at all. Do I need to restore the original rgn 41 from backup?
Did you use RMPrepUSB to reformat after applying Cure3 fw, or only remove some dodgy files once you had Mass Storage Mode back? If there was no format done I'd suggest make a backup of the file system and reformat it then restore the folder and files. You may as well restore region 41 too seeing it didn't alter the boot time.
Make sure your backup of 41 was successful and file is not empty. Restoring an empty 41 is bad.
Not questioning your knowledge there but can you explain how restoring an empty bin file to region 41 is different to erasing with ergn command? The device rewrites most information to 41 on every boot anyway.
If 41 is "regenerated" then no big deal. But in general, you backup something so you can restored it later (I mean why backed it up in the first place) Engineers (good ones) often "clear" memory area before "restoring". Just like in programming if you allocate memory, you should "zeroed" it before using. So if your 41 is empty and you restored it, what you get is zeroed memory area.