Thread: How to backup Nuvi NV (region41) with sd

Your 5000 used firmware in the same .exe format as many other contemporary nuvis of the day, but the contents are different as you've found. Up to version 4.10 was supplied as only an *.exe file which can be extracted with winrar or similar de-compressor to then find B074300.update in Nuvi5000_410/Nuvi5000/Garmin/Updater. However RGN_Tool will not open B074300.update even if the file extension is changed to .rgn or .gcd.

With V4.10, it was supplied also as an rgn file, named Nuvi5000_regionfileonly__410.rgn and that can be opened with RGN_Tool but doesn't obtain a boot.bin.

I'm unable to say whether 5000 can have region 41 dumped because of the way this firmware is compiled. Certainly other conventional OS models of that time such as 2x0, 3x0, 6x0 could not have 41 dumped to SD anyway even though they had conventional boot.bin in their fw.

nuvi5000 V4.10.rgn file can be downloaded from the Perry site:

Code:

Please Login or Register to see the links

Using RGN_Tool to obtain a boot.bin proves problematic because it only displays 'virtual_image.bin' in first section where 'boot.bin' would normally be and no other sections are populated. virtual_image.bin is 69,754,880 bytes [~66.5 MiB] which comprises all of the firmware.

Maybe one of the Navigation Software Experts can explain further.

What do you have in Update.txt ?

update.txt

rrgn,41,1:/41.bin
reboot
---------------------------

update.log

nüvi 35x7 Software Version 4.40, UID: 38800xxxxx, HWID: 38800xxxxx
------------------------------------------------------------------------------
Parsing "rrgn,41,1:/41.bin"
Success
Parsing "reboot"

For newer devices like 3597, 2797 etc (2013 & later) you should change the script in update.txt because MicroSD has been changed from 1 to 2

From

rrgn,41,1:/41.bin
reboot

To

rrgn,41,2:/41.bin
reboot

Thanks Ellinas I added it in starting post

Sorry I forgot to add this info in starting post, but it's written in thread by lolypop000 [Only registered and activated users can see links. ]. Always better to read whole thread

Something else worth comment is that old nuvi series 2x0, 3x0 and 6x0 backup 41 empty but they can backup other less-important regions. However, interestingly the card's path for 3x0 and 6x0 is 2:/ as it is with 2013> devices, which in fact write 1:/ to the hidden RWFS ram flash as described [Only registered and activated users can see links. ]. So with 2013> [and only them], it's therefore possible to write regions elsewhere than a card and then move the backups from RWFS to elsewhere using a PC. However, as neither the unit itself or RWFS cannot execute script commands, you still need to have a card to do that but it could be a help if you only have a tiny 32MB microSD and want to dump a lot of regions together. There was an earlier question in here about backing up without a card but from memory the poster had a 2012 unit anyway. In any case the short answer is it's impossible to dump regions from any unit without using a card, as one is required to at least execute the script in update.txt.

Relatedly, Linux OS units like nuvi 5000 and 8xx cannot write 41 or for that matter any other regions that we know as commented on by kunix [Only registered and activated users can see links. ].

It would be worthwhile knowing if any of the Asian Android units are capable, but my guess is if the Linux units can't then neither can they.

A handy tip to try with a unit which refuses to write to the card is to add an empty update.log file in with ldr.bin and update.txt, that will enable some units to then do backups.

Originally Posted by jackmawatan

thanks for this info. took me whole day to finally figure it out. almost broke my sd card during the process.

In your case, the card wasn't getting a look in at all until you changed the path to 2:/ anyway. The previous attempts were all writing and then overwriting 41.bin to RWFS. You'll find it's still there if you look.