Originally Posted by
motoltd
is there a command to copy everything to the SD so i can check every file and it's size?
Yes. You can dump the entire visible file system from the internal memory with this:
Code:
Please Login or Register to see the links
Its ok for me to grab the boot.bin to rename in ldr.bin using the firmware and getting the boot.bin from there? or i have to use the update in the device?, i can see it's the 4.0 but cant extract anything from the device.
If it's running V4.00 that's the latest version for nuvi x2 so just extract the boot.bin from "nuvix2andx4_GCDFile__400.gcd" using RGN_Tool and rename it to Ldr.bin. It's not possible to dump a boot.bin from the device itself because it's flashed to a virtual region 12 which in turn flashes physical regions 4 and 43. Using a boot.bin/Ldr.bin that's from later version usually isn't problematic anyway unless there's a huge difference from the version number already loaded. The GCD loaded to the device's .System folder by GarminExpress should still be there, named gupdate.gcd. It will be in the files dumped with the above command.
Because i checked and the map file i have in the SD is gmapsupp, and not gmapprom (dont remember which one was the base garmin map, and dont know if i can grab it from other device (i have a 200W and a 2495)
The correct naming for a detail map in the Garmin folder of microSD card is indeed gmapsupp.img. However nuvi x2 can support <any_name>.img in Map folder of the card or internal memory. Basemap is in internal .System folder named gmapbmap.img. In addition to gmapprom.img, .System will also support other secondary detail map naming. I can't recall for sure but probably gmapprom1.img & gmapoem.img, and maybe gmapsupp.img as well. Regardless Map folder can read the "<any_name>" for detail map IMGs therefore it's not so important for later devices what the naming convention is in .System.
Once you dump the files you can decide what you want to retain or delete. It's likely that there's only one detail map IMG onboard and that will be it's LM entitlement named gmapprom.
If you can repair the USB socket then all this becomes moot anyway.
Bookmarks