Thread: Garmin Etrex 32x is not connecting to its database

@cwerty
To get help you need to share all that you have done or you will waste others time.
On the 24th you posted elsewhere:

Hello. I purchased a used Etrex 32x navigator with ID 3445. It has the following problem: it doesn’t accept firmware version 3445, but it does accept 4333 and successfully flashes it. With this firmware installation, GarminDevice.xml looks like this: <PartNumber>006-B4333-00</PartNumber>
<SoftwareVersion>290</SoftwareVersion>
<Description>eTrex 32x</Description>
I tried to cheat and in RGN_Tool, in firmware 4333, I replaced the HWID with 3445. This firmware was installed, and now GarminDevice.xml looks like this:
<PartNumber>006-B3445-00</PartNumber>
<SoftwareVersion>280</SoftwareVersion>
<Description>eTrex 32x</Description>

PartNumber and Id in the file match. But GPSDaemon identified Id 4333.
However, as before, it doesn’t see the databases, maps, or installed languages. I installed all the firmware using Updater.exe. I installed a fake firmware version 280 because I planned to update to 290 via WebUpdater. But it didn’t see any updates.

Please help fix the navigator. Just in case, I’m attaching the GarminDevice.xml file after the latest firmware update. Please take a look and see if there are any errors in it. And if possible, please upload a backup of the folders and files in the internal memory; I’m afraid some files might be missing. I couldn’t find a clean backup after a properly installed firmware anywhere online. I’m not fluent in English and I’m writing with a translator, so I apologize for any possible misunderstanding. Thanks!

Code:

Please Login or Register to see the links

@cwerty
It's far more likely your eTrex is malfunctioning because of firmware or flash damage problems. I very much doubt that changing/adding files will help you to recover it.

I have many questions:

Is your device a "standard" etrex 32x or is it marked as eTrex 32x 2022 Redesign on the ID label?

How did you flash the modified 4333 firmware? i.e. Did you use an RGN file in Updater.exe or individual BIN files using Update.txt in a media card? (a device with a different HWID won't accept a GCD flash with a mis-matched HWID).

Why did you know to try using 4333 fw when it was identifying as 3445? i.e. Did you or someone else change its HWID or "cross-flash" firmware previously?

So, if you know, please say what is the complete modification history of this device BEFORE you obtained it. Without knowing that, any further manipulation of fw might make things worse and even hard-brick it.