Running programs from SD on nuvi

Yes you can make changes to it by adding, replacing and/or deleting files or even entire folders and then recompile it all back into a BIN file to re-flash to region 48 using xrgn. It was intentional that i didn't mention that possibility in my previous post because of the very real risk of bricking if somehow the process isn't perfect. Even if you make the new BIN too big the flash may fail badly. Because you already cannot access preboot there is no way to fix anything if it also cannot use SD card. It's highly likely you would lose that function because a bricked device likely won't enter far enough into the boot process to read the SD if it's been bricked by corrupt files onboard. If the data connection problem's caused by a PCB component failure then re-flowing won't fix it.

Safest way is to use ergn command to remove from the internal memory any map, poi or other files which can easily be used on the card. That way if there's a problem you can just remove the card and the device will still boot. Most brickings are actually due to corrupt IMG and GPI files. You're better to not copy new poi's to the device from the card when prompted because of that reason. Some files such as Voice need to remain on the devices itself of course but updating them isn't crucial.

You really should try to reflow the USB socket solder connections and reinforce its attachment points to the board. If you can re-enable the PC data connection all this goes away. Better to find out now for a couple of reasons if reflowing will work.

Hi there.
Maybe you can help.
I have a BMW Navigator V that keeps booting when connected to a PC or Mac via an USB cable or to the motorbike cradle.
When powered via its own battery, it is working like a charme
It looks that this an USB chipset problem but wonder if a corrupted file may prevent the management of the USB link to be done properly.
I have done a back-up of the internal memory and it looks OK.
Any thoughts ?

It's a hardware problem, has nothing to do with this forum and topics.

Yes, it's certainly a hardware problem. Those symptoms cannot be caused by a software problem, faulty files or even a corrupt region. Had you not added that it also reboots when in the bike cradle i'd have suggested to check the USB socket's external pins and the solder connections internally to the PCB. The only good news is that the combined saleable value of it's strip-able parts and the cradle itself will not be inconsiderable.

Hello butter

I have read the whole thread.
Also the description of the commands in the update.txt file.
Also the following description Since my Nuvi is also not recognized by the PC, this could be a solution.
Am a beginner and although I understood how to determine the HWID my 1772 nuvi 2936. I can also generate the LDR.bin and have also already saved the file 154 with it.
But how do I create the files:
158.bin
127.bin
14.bin
for a nuvi 2639 HWID 1772
or are they always the same ? And does the upate text so also fit on a nuvi with HWID 1772.

These are the questions of a learning beginner

@Raupe
Please state more clearly why you wish to flash standard firmware in this way before i make an SD card kit. I'm very aware that it is difficult to attain preboot in 2xx9 series and it's a very short time to start a flash when the device is in preboot. However Mass Storage Mode should still be available unless the device is bricked or has a faulty USB connection. If it's bricked then it's unlikely to be getting far enough into the boot process for a microSD card to be recognized. If it's not bricked and has a USB hardware problem then placing the higher version of firmware on a card will update the device anyway, to do that the GCD file must be named only GUPDATE.GCD and placed in a Garmin folder on an otherwise empty card.

Hello and thank you for the quick reply. Right the reason I had not described. Sorry.

The 2639 is about 7 years old. He was little used over the time. In the car that I use now is a Navi, whose map is no longer updated.
The day before yesterday I used the 2639 in the car and was satisfied. In the evening to the PC , Garmin Express reported countless updates.
After completion of the updates ran the Nuvi perfectly.Einzige exception no connection to the PC.
Mass Storage Mode is set in the nuvi.
GUPDATE.GCD does not work.new SD card Samsung. BTW is the filename case sensitive? should the filename be in capital letters? Backup from Nuvi to the card 154.bin works.

Addition

The Nuvi is a 2669 not as I wrote, a 2639. This may explain what happened during the update via Garmin (Garmin Express).
The device was recognized as 2439 by Garmin and registered as such and therefore provided with appropriate wrong firmware.

If you didn't hard-reset the device after the numerous updates, you should do so now. Better still to clear the non-volatile memory: [Only registered and activated users can see links. Click Here To Register...]. If you have data you wish to save then back up before resetting or clearing NV. Try after that to see if PC connection works and if not read on below.

There have been rare instances of GarminExpress mis-reporting the device model, going from memory it's been 26x9 showing as 25x9 or similar but at least the error involved another common and closely related model. However it did not involve placing the incorrect fw in the device and even if it did the device would ignore a GCD file which was not applicable to the device. I've not heard of a "nuvi 2439" but maybe there is such a model, a limited regional release perhaps.

Please confirm the HWID of the device by the 'battery symbol' hidden inventory as described here in Method 2: [Only registered and activated users can see links. Click Here To Register...]. Also state the reported firmware version which will show as x.xx (e.g. 8.80) behind the HWID (Bxxxx-00) on the first 3 lines. Advise if the version for 'System' differs from that of Boot BLK and X-Loader or confirm they are the same.

Upload to a host site (MegaNZ or Google Drive will do) a copy of the GUPDATE.CGD you are trying to use (that file name is not usually case sensitive btw) and also upload the folders/files you used to dump 154.bin (you can remove that BIN file as i don't need it, just the Garmin folder and it's subfolders and, importantly, the Ldr.bin file you used and all files other than 154.bin created during the dump). To minimize upload size you can compress everything into a single ZIP/RAR/7-ZIP archive file. Post the link here or PM it to me if you prefer.
..........................
EDIT:
@Raupe
I received your PM with the link for the files and this pic:

Spoiler:

[Only registered and activated users can see links. Click Here To Register...]

Clearly the device already has latest V8.80 firmware loaded. Hence why it ignored the gupdate.gcd on the card. Therefore there's no benefit to be gained by flashing BIN files extracted from V8.80 because you would simply be re-flashing the same version of fw.

If you are still unable to get Mass Storage Mode working after a reset/clear nonvol, examine the USB socket connections to the PCB as it's not uncommon for the solder traces to fail. If the socket is loose or traces are visibly cracked, carefully reflowing them with lots of flux usually fixes the PC connection problem.

Thank you for your effort and support. You are the best.


Following the advice, I disassembled the device and checked the USB port.

The pictures in the attachment. It looks good to me. Nothing is loose, the socket is soldered rock solid to the PCB.

Btw have seen worse solder joints. If no one has any more ideas, no idea how to proceed.
Is there a way to delete the firmware and reload it ?
Happy weekend to all

Spoiler: two large images

[Only registered and activated users can see links. Click Here To Register...]

[Only registered and activated users can see links. Click Here To Register...]

Yes you can delete and reload the firmware by SD method. Use RGN Tool to save the individual BIN files: [Only registered and activated users can see links. Click Here To Register...]