-
So i'm now assuming that you didn't get that HWID from G7ToWin AFTER it was 'bricked'.
With preboot unavailable your only chance to revive it is if it does recognize an SD card. For that to happen it has to be actually booting at least partially despite the screen remaining black because the device doesn't even look for a card until after essential files such as maps are checked for and loaded. I think the chances of it working are probably slim given the history you reported but let's try:
-
Hey Neil, seems like "she's dead, Jim". On the bright side, I managed to successfully flash a few others among a late Nuvi 260W. In Butter's tutorial is mentioned "Junior models may need to have the 465T Logo flashed as well, in particular that is essential for the 2x0 devices." Does this mean that boot logo flashing is only necessary for junior models, and that it's being emphasized for the 2x0 junior models, or is it implying that it's essential for both junior models AND any 2x0 devices including my 260W. All the help so far is appreciated by the way!
-
You're referring to this post [Only registered and activated users can see links. Click Here To Register...] as Butter's tutorial, i'm sure. What he's saying is that for the senior models (255W & 265W) the original logo data is fine after 456T conversion. Some junior models, particularly regional EU issues, may have had features suppressed by modified data in region 16 - that's where the logo splash is stored therefore the logo data is best updated or there's a good chance of not functioning properly as a 465T. That's essential to be done with the (misnamed) 2x0W models sold in the Northern summer/Southern Winter of 2009. They were a Frankenstein device which had essentially what was a 2x5W HWID 0827 board in a 2x0W case. They acted like the original 2x0W devices without any traffic function and some others like Speed Limit display and maybe TTS too were lacking, i think. That was done by intentionally crippling 0827HWID basic functions via modified logo data to make them "seem" like a 2x0. If one of them was converted to 465T retaining the original logo data it was a mess. It needed to have either the senior 2x5W logo flashed to it first or the 465T logo flashed at the same time as the other data during the conversion. However, some of those later boards didn't take a 465T conversion well at all, even hybrid wasn't successful and then they would white screen brick if fully converted i seem to recall.
Sorry your nuvi is indeed dead as you said. With neither preboot or SD card reading operative it's irrecoverable by software means and a hardware solution is not viable. Keep it for parts, the screen is probably still working fine and some 2x5W screen types even work on early 13x0 nuvi models.
-
Hi,
I had a 265W and a 260W I successfully converted that were working just fine, until I tried to update their maps to 2026.20. All were HWID 0827. They still work fine and boot etc. The map files though, are in a sort of limbo state with deletion where they are corrupted/deleted enough to be unusable by the GPS (no detailed maps that support routing...) and are are seen as 0KB size by Windows, but they are still present enough to the point where I can't load the new gmapprom onto the onboard storage. Not sure whether it was more appropriate to start a new thread for this as though it's a different issue, I'm branching off the conversation from a couple months ago. Thank you for any help in advance.
-
It looks like errors in the file system record (the chances of the chip being damaged are small). The files were too big and the transfer broke, I guess
You will probably have to reset and reformat the memory (storage). Of course, first you must backup all system files.
Be very sure that you know what you are doing
-
Sorry for the late reply and thank you so much for your comment, just a couple questions.
If the files were too big, how come they transferred just fine on my non-converted (unsupported) 265W units?
Could you point me to a general direction on how to reformat the units? What I'm assuming is that I copy the whole file system, format the unit as I would do for a USB drive, and copy all the system files back except for the gmapprom, but I'd rather be safe than sorry and break the unit even more than it already is.
-
@Zakk
I've not quite got my head around the circumstances here, so a couple of clarifying questions from me:
You said the map files are showing as 0 bytes in the internal memory but you aren't able to delete or overwrite them - correct?
What file names do you have for your map IMGs?
-
Correct, they are "taking space" so that I can't add any other files but the computer sees them as 0b and the nuvi can't use them for routing, trying to force delete them or move them yields a message that says something along the lines of "this file is corrupt". The file name is gmapprom, but it's never caused me issues except for these 465 converted devices.
-
Right, thanks got it now. It's as Boki surmised in his reply but i just wanted to be sure.
The only way to remove those corrupt files is to reformat the internal memory. First copy everything else other than the zero size files to a save place on your computer as a backup, then use ONLY [Only registered and activated users can see links. Click Here To Register...] to format the internal memory in FAT32 - Don't use any other method, not even the Windows built-in tool in Disk Management. Garmin devices can be very picky about the format and (to mangle an old saying in rhyme) "There's more than one way to format in fat".
After you've reformatted, copy back your good files and then source known-good IMGs to replace the corrupt ones which will restore functionality.
-
Seems to have worked for one of them, I'll get to formatting the other at another time. Any idea why this only happens on the 465 converted models and how to avoid it? It's only something I'll need to do twice a year but if I can avoid it then I'd like to.
