Thread: Patched firmwares for JNX files

I manage to get in USB Mass Storage, i delete the false JNX file but when i reboot the Astro 320, it gets only in USB Mass Storage, if i dont plug the usb cable the GPS shut's off.

Originally Posted by alex2917

I manage to get in USB Mass Storage, i delete the false JNX file but when i reboot the Astro 320, it gets only in USB Mass Storage, if i dont plug the usb cable the GPS shut's off.

Oh, people don't enjoy reading too much as usual. It's written [Only registered and activated users can see links. ] (in bold!) that
"Please note that the CURE firmware will never boot, it can only enter the mass storage mode."
So now you should use ORIGINAL option of GarminCure3 and flash the original firmware.

edge 800 v2.50 patched:
[Only registered and activated users can see links. ]

Patcher 2.14 released. In this version, support of Oregon 6x0 firmwares is added, as well as recognition of Edge 810.
The archive is available from its usual [Only registered and activated users can see links. ].
[Only registered and activated users can see links. ] is a direct link to the file.

Hello.
Last week I updated a GPSmap 62S with the V4.60 and Patcher V 2.14.

Everything was fine but I detected a little issue, every time I started the GPS It was created in the menu a new Adventures Icon.

I solved the problem updating again the Firmware V 4.60 version but this time with the FirmwarePatcher213

Thanks for everything.

Barbastro, I've just checked, and patched firmware 4.60 produced with patcher 2.14 is byte-to-byte identical to one made with 2.13.

So, there most likely was some problem with your current profile, which was solved by up- and downgrade you made during the re-flashing.

OK great and thanks for your support.
That is almost an online chat.

Hello again Alex,
That is not a big deal because the problem now for my is solved.
But, I have compared both files the one created with FirmwarePatcher214 and FirmwarePatcher213 and they have six differences.

1) 0x101f=4127 to 0x101f=4127 (1 bytes)
2) 0x242df=148191 to 0x242df=148191 (1 bytes)
3) 0x2c64d=181837 to 0x2c64d=181837 (1 bytes)
4) 0x6faaf5=7318261 to 0x6faaf5=7318261 (1 bytes)
5) 0x84b25a=8696410 to 0x84b25a=8696410 (1 bytes)
6) 0x84b25f=8696415 to 0x84b25f=8696415 (1 bytes)

Maybe that is because in the V2.14 I adjust firmware version number by –50 and in V2.13 I put –1.

Thanks.

Originally Posted by Barbastro

Maybe that is because in the V2.14 I adjust firmware version number by –50 and in V2.13 I put –1.

Yes, that's the reason of the difference.
If you won't adjust the version numbers, the produced files should be the same. And if they are not, there apparently is some problem.