Did it eventually stop showing 'Loader' and try to boot itself to the logo screen, or, how long did you leave it with 'Loader' showing before giving up? Also check in the card's 1541 folder to see if there's any new files named last_id.bin and/or update.log because if those files have been created we're maybe not totally done yet.
No it won't work without also reprogramming the replacement chip. It's quite above my 'pay-grade' but that because i'm not a programmer or coder. The ID codes are stored on the chip somehow and it would recognize that the hardware has changed without reprogramming, i guess that'd need to be done by a true expert with special JTAG equipment - certainly the factory can do it as that's often what's done with replacement 'refurb' units which were returned with failed chips. *See below for the other unit's charging issue.General question Though, I've another (another other) NAV V that i bought for spares a while ago. But it has a power off issue while charging -apart from that it's okay.... Whatever, not my point :D
So, theorically, if i ask a skilled tech to swap the eMMC (memory module) between the two units, would it work? I mean, do you know what actually gives the Serial number etc to the NAV V?
No, even if you flashed all the information in the dedicated regions from the old chip to the new one with conventional means, i.e. simple memory swap, (flashing BINs as an RGN file with Updater.exe in preboot, or BIN files via SD card TXT commands) it wouldn't be enough (see previous answer about JTAG). Regardless, in your case you don't have a previous dump of all individual relevant regions anyway and seemingly read/write of/to the card fails so there's no way to get them now.Would a "simple" memory swap could solve the issue, according to your knowledge of garmin devices?
*Personally, i'd be looking at trying to repair the other device. It maybe as simple as one or two cracked solder connections on the USB socket causing it not to charge properly and power off. Re-flowing the solder connections to the board is fairly simple and a common Garmin failure point (see post #157 in this thread). Of course it may be due to a component failure on the board itself, not so easy to find and fix however i'd be re-flowing the usb socket connections or you can even swap sockets between the units if you suspect the socket's internal pins are damaged.I can ask garmin for a replacement, but I think they're gonna charge stealer price aka BMW price aka 450 euros ... Almost twice tue value of a used one. I'd rather make a working device out of two non usable one...



Likes: 




. I'd rather make a working device out of two non usable one...
Reply With Quote

Bookmarks