Thread: Garmin Nuvi 265W dead

Originally Posted by kunix

@ddabcd277
Does Rik need a cure firmware that doesn't read anything from internal flash? Then I can try my patch

@ kunix

No, better. The idea is to flash memory with FTL which would reorganize the information. I know the trick from Alex.

Hi ddabcd277
For 24xx / 25xx Asian (and the same hwid ie 2465 hwid1327 - TH-Sg/My-TWN)
Can FTL change the region ?
(Tested :: No effect if I flashed 2465TH with 2465Sg/My firmware.., Nuvi won't display Sg/My JCV.)

@rik70
@ddabcd277
Hm, I don't understand what is damaged in the device and what is FTL. Also there are no 'boot files' at all. There are two regions in flash memory, one for fw and one for bootloader. I'm not sure whether x-loader is located in flash as I have controversial information. There is also the largest region in flash used to store internal filesystem. If internal filesystem is corrupted we can restore it either by flashing cure firmware and then formatting from Windows or by flashing correct filesystem header (Alexander's method).

@ kunix

That is what I meant - flash filesystem with filesystem header. (Alexander's method) Very cleaver way!!! 99% is fixing rebooting/freezing if the problem is coming from the memory - problematic files, corrupted FTL (I am calling the filesystem - FTL , bad formatting etc. Think it is much better than patching and playing with the main firmware. I see that you also know the method. That's nice.

Have a feeling everything is located in the memory - x-loader, bb, nvm etc in nuvi 265w. What other place can be located?

@ SiamMarine

Don't know never seen an asian unit. But you can experiment.

Originally Posted by kunix

@ddabcd277
Wow! We were talking about same things Personally I don't like flashing filesystem headers. It seems unreliable to me, unless you perfectly understand what those headers contain. Otherwise you have to flash entire filesystem, which will take too long time. Also you have to dump it first which will also take a while. As opposite, patching firmwares is something that I understand And it also helps, at least for old nuvis.

Yes, we are talking about the same thing. Just different approaches. I abbsolutely agree with you - flashing filesystem is unreliable and dumps are too big. But I have noticed that if the so called "cure" firmwares (changing files extensions and 0:/, 1:/ (neadrenalin's method)) don't give access to the memory this is maybe the only way for fixing. (except if you don't know how to jtag a nuvi). Of course nothing to be loosed if patched firmware with disabled Open file function (kunix method) is used. Which is much clever way.

About the x-loader...Sorry I really don't know.

Edited.

Originally Posted by ddabcd277

BTW What is "MMU configuration"?

Here I was talking about configuring Memory Management Unit by firmware. FW remaps some peripheral registers, makes interrupt vectors, bootloader and fw addressess readonly and so on... I didn't investigate deep in this process because lack of time and knowlegde. Have to read ARM Architecture Reference Manual first

aekhong, have you physical access to one SG\MAL 2465? May be, we can dump other regions and enable encrypted jcv on EU and TH devices? I need so Garmin Sync from SG/MAL and Thaiwan devices (I can't find this util in Web, but i know this util is preloaded on some SG and Taiwan devices).

More about 2465Asian here --> [Only registered and activated users can see links. ]