There is interesting info on. There is description of how to remove demo mode from Nuvi 1690. Since nuvi is not accessible from PC, Garmin offered package 1690_demoremove.zip, which should be unpacked to SD. When SD is inserted into nuvi, demo will be disabled.Code:Please Login or Register to see the links
Package consist of 2 files:
\Garmin\Updater\1132\LDR.bin
\Garmin\Updater\1132\update.txt
update.txt contains commands:
del,0:/Garmin/demo/demo.srf
reboot
LDR.bin seems to be a program, that is executed by nuvi. Inside LDR.bin there is some kind of help text with possible commands:
Program seems to be specific to nuvi 1690, number 1132 is HID of nuvi 1690.Code:Please Login or Register to see the links
Some more information about general usage of SD text commands can be found in this [Only registered and activated users can see links. ].
Last edited by catymag; 18th March 2015 at 03:35 AM.
You are right, I have looked at boot.bin form several firmwares and found the same commands there. I'm able to run boot.bin on 37xx, just need to save it on SD as \Garmin\Updater\1101\Ldr.bin
I have made some tests. Ldr.bin runs just after booting, probably is executed by real boot.bin. Ldr.bin parse Update.txt and execute all commands written there. At the end it write 2 files in its directory: last_id.bin and Update.log. When these files are present, Ldr.bin is not executed again.
There are usable commands for Ldr.bin. We can read and delete files. For example command "del,0:/.System/gmapsupp.img" can remove damaged map from nuvi. We don't need cure firmware anymore
We can copy backup files from SD to nuvi and restore it after formatting
I think commands like fftl or copy_image can even restore damaged file system. This needs more investigation.
I found that commands are present in 3 years old firmware. It is unbelievable that nobody reported this feature before. Just imagine how many problems could be solved that way...
This is very interesting
I would expect that ergn is erase region, probably needed before writing to flash memory.
On 1300 is boot.bin in region 5
Region 5 is the boot block.
@Kanopus
Most times removing gmapsupp.img is very far from being enough to cure a device. In cases it helps simple cure firmware helps also.
And ldr.bin is loaded into memory by fw_all.bin, and quite late actually, so you can't cure with this method at all, firmware would already crash by that time.
For some reason there is "ldr.bin" string in bootloader inside boot.bin but it is fw_all.bin who initiates execution of ldr.bin. You can see it yourself of course.
A lot of people prefer to keep their secrets with them.
I definitely know that some Garmin resellers have been aware of update.txt for a long time.
Last edited by kunix; 18th November 2011 at 03:25 PM.
Yes.,you can see "Loader" will appear after "Loading map".![]()
Yes, there is Ldr.bin in firmware. Could be too late to remove damaged map. But I think boot.bin can execute this too, for example when "system software missing". We just need more experiments.
This method works on old devices too. Today I tried it on Nuvi 350 and Nuvi 765T. It worked but folder name where ldr.bin and update.txt are placed must consist of for digits. Because HWID for these devices consists of three digits (476 and 870) we must add 0 at the begining of HWID. For HWID 476 folder name must be 0476.
For me doesn't work memory dump. When I tried to execute command rrgn (few versions) I got an error.
Parsing "rrgn,5,"
Error
Parsing "rrgn,16,"
Error
Parsing "rrgn,5"
Error: invalid command format
Command format: rrgn,<rgn #>,<output path>
Error
Parsing "rrgn,16"
Error: invalid command format
Command format: rrgn,<rgn #>,<output path>
Error
Parsing "rrgn"
Error: invalid command format
Command format: rrgn,<rgn #>,<output path>
Error
Parsing "reboot"
Success
Where is my fault? Why dump doesn't work? Some of these commands have invalid command format, but why other ones gave me an error?
Bookmarks