6 Meg's out of 8.
6 Meg's out of 8.
Last edited by Boki; 29th October 2020 at 10:02 PM. Reason: approved
Seeing it takes a flash to region 14 to update the main firmware it seems that there's no corruption in that part of the flash memory at least.
Provided the Rufus format actually leaves the visible memory genuinely empty, I suggest you try this: Set your computer to show all hidden and system files, [Only registered and activated users can see links. ]. Remove everything from the visible file system keeping a backup copy. Manually create a folder named Garmin in the root of the empty memory and then boot the eTrex ignoring and clicking through any warning messages. If it completes the boot, shut it down and connect to computer again to check if there's a newly-created file GarminDevice.xml or GarminDevice.temp in the Garmin folder.
It should write a new copy of the XML file every time it boots. Likely the flash chip is damaged although it could also be due to severe corruption in it's non-volatile region. I can't recall if eTrex 10 has the function to clear non-vol and don't have one to check, perhaps babj615 can help with that info.
Hidden Test Pages eTrex 10
Hardware/Software ID and Display Test:
With the device turned off, press and hold [Power] + [Thumb Stick]
[Power] = Cycles Backlight 50% > 100% > Off
[Back] = Cycles Diagnostic Screens
Error Logs:
Open the Trip Computer page.
[Thumb Stick Up > Right > Down > Left]
[Thumb Stick Up/Down] = Select Desired Shutdown Log
[Enter] = Displays additional information when available
[Thumb Stick Up > Right > Down > Left] = Logging Control
[Back] = Exit Selected Test Mode
@asprin624
So 'Clear nonvol' option isn't available for eTrex10 is what you're stating? It seems not to have 'ergn' written in firmware either so erasing nonvol memory by sd txt cmd isn't an option either unfortunately.
@Butters,
I spend a lot of my time at this site. It has been setup for all Garmin Handleld devices.
There is lots of great info here with direct contact with Garmin.
Spoiler: Garmin Handheld Help
If anyone can give good tips these are the people that can.
Tried the HW test, RAM and ROM get a "Pass", when BMap Chk gets a "Wait".
Tried accessing the error logs - had 2 "Abnormal shutdown" ones. When I tried to access them, device somehow froze and shutdown itself.
I'm sorry, it's almost certainly physical damage in the flash chip. Not economically repairable and even if you wanted to try you need special skills and kit to change the chip and then also need to reprogram it after replacing it.
There is only a small chance it's due to bad corruption in the devices nonvol region but without a way to clear it or erase the region it's still toast.
Forcing a downgrade of firmware to a much lower version might trigger a comprehensive reset to clear some nonvolatile data from region 41 but that process may kill it completely too.
Bookmarks