in update.txt write this and scan will work ;)
rrgn,41,2:/41.bin
reboot
Old nuvi use 1 for SD card but new nuvi have 2 for SD card ;)
Printable View
in update.txt write this and scan will work ;)
rrgn,41,2:/41.bin
reboot
Old nuvi use 1 for SD card but new nuvi have 2 for SD card ;)
Loly, smokefree has a 2xx5. It's the 2013 2xx7 devices which have the RWFS which is written as 1:/ and the microSD as 2:/. The 2012 range 2xx5 definitely still has the path 1:/ for the card.
@smokefree
Try another microSD. Format it freshly first before adding the Garmin/Updater/1371 folders and also remake ldr.bin. A hard reset or clear NV of the unit would also be advisable before you try again. My 2455 and 2595 both HWID 1371 have no problems writing regions to the card.
This initially appeared to be working (SOFTWARE LOADING / LOADER message, green progress bar and reboot) but did not give me a 41.bin file in the root of the microSD and it resulted in a corrupted update.log file (unreadable).Quote:
Originally Posted by lolypop000 [Only registered and activated users can see links. Click Here To Register...]
Used another microSD, cleared NV and tried again (using 1:/). All symptoms look fine, this time I even do have 41.bin in the root, but the update.log file is still corrupt.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Edit:
The 41.bin file on the microSD also seems corrupt as I am unable to copy it from microSD to the HDD of the PC. Will try a third microSD and try again but will not be home until 8 hours from now. Could it be the nüvi 2545 does not write the files properly onto memory card?
How big is the 41 bin file? It should be 4,352 KB and although it is encrypted it should 'copy & paste' normally.
My AU 2595 is identical hardware and sw to your EU 2545 other than addionally having a mic and BT & ASR. Your unit will write and read to and from 1:/. Try the third card and if it's not brand new reformat it correctly to FAT16 or 32 as required using SDFormatter [google it, freeware] or RMPrepUSB which you'd already have. I simply don't trust the built-in Windows tool, occasional bad formats and never use a Mac. There's more than one way to format in FAT [rhymes with more than one way to skin a cat, lol!]. No need to worry with a brand new card as it's factory format will be fine. Remake the whole kit from scratch, don't copy the old one across. You can add an empty update.log if you want but it's not necessary with 2xx5 as it'll be created by it.
I have had problems occasionally with the card slot on some units when the contacts have become 'filmed' and read and/or write function is sporadic or unreliable. I've usually been able to fix that by working the microSD in and out of the slot several times. In stubborn cases, it's necessary to do a very short spray of dedicated electrical contact cleaner [not water dispersant-type cleaner such as WD-40, that's a big no-no] either onto the card contacts or in the slot followed by working the card in and out. If you do that, let it thoroughly air-dry with the card out before powering up.
Yes, the size is 4,352 KB. With your advice of post #16 in mind, refreshed by post #125, I tried a third card. A Kingston 4 GB microSD brand new from a sealed package. The process again froze on the Garmin splash screen with the text "Loading Maps" at the bottom of the screen.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
So I decided to now use another brand and capacity: a 2 GB Transcend microSD. And voilá: the backup was made in seconds without any corrupted files on the microSD! Amazing how particular the combination of a memory card with a specific unit can be.
Yes, it can happen. I recall a Sandisk 2GB card which i used for backup of 41 for numerous units only to have it baulk on backing up a 2 series nuvi [a 255W i think is my recollection, and it wouldn't recognise the SD at all] after it had been used for other very closely related units. Used a different card and it worked fine.
Interesting that the Transcend worked when the new Kingston froze the unit. Sandisk and Kingston are the only two brands endorsed by Garmin for use of additional map data.
Hi!
I have tried to update software on my Garmin nuvi 660 NA. Something has gone wrong and my nuvi is death now.
Can anybody send me 41 region for this device? I want to tray this way to fix my nuvi.
@miroslavbl
Flashing rgn 41 from another 660 would cause you no end of grief even if possible. 6xx cannot retrieve a backup of 41, and anyway it's not what you need. If it can be seen in Windows Explorer/Disk Management as a removable drive, remove GUPDATE.GCD from the Garmin folder. If that doesn't fix it, reformat it with [Only registered and activated users can see links. Click Here To Register...]. If it's not recognised by Windows, try [Only registered and activated users can see links. Click Here To Register...] first, then remove the GCD file and reformat with RMPrepUSB only if necessary. Post in the Cure3 thread if you need more help.
I took your advice and my nuvi 660 works again. Is there a way to do a backup Nuvi NV (region 41)? I followed the instructions, but Update.log says
Parsing "rrgn, 41.2 :/ 41.bin"
Error
Parsing "reboot"
Succes
41.bin file is 0 kb.
When "rrgn, 41.2 :/ 41.bin" Replace with "rrgn, 41.1 :/ 41.bin" nothing happens, no file 41.b5n.
I've tried several different SD cards.
No, unfortunately it's not possible. Read again the first part of my reply above, but perhaps my wording wasn't clear i'm sorry. '6xx cannot retrieve a backup of 41' = 'You cannot do a region 41 backup of a 6xx'. The problem's not to do with the SD card, I think the command is simply not present in firmware of nuvi 2xx/3xx/6xx or earlier SP units either. I recall that rgn41 backup was not possible until nuvi 2x5/7xx series. Backups of other regions can be done though in 6xx nuvis, ie. rgns 5, 14, 15, 16, 24, 34, 45.
In an extreme case as an absolute last resort it is possible to erase 41 in a 2/3/6xx series to restore a unit to semi-working condition if rgn 41 is corrupt. The problem is that all registration and unlock code are removed from the unit in the process and that makes updating with purchased maps impossible unless they are purchased on an SD card to which they are locked. Unlocked maps can still be loaded to internal memory normally.
One of our software experts should be able to write the command into the firmware to allow backup of 41. Who's up for the challenge guys?? ........ [chirp, chirp ...... chirp ....] ........ guys? .... anyone??
:lol: