Thread: Approach S60 software summary

Not include it now.
Dump Required.
But I don't know how to do that.

Originally Posted by Butters

You can extract boot.bin yourself from firmware with RGN_Tool ([Only registered and activated users can see links. ]) or use [Only registered and activated users can see links. ] command line tool.

Well, nadias is asking because there is no boot.bin in the Approach S60 GCD. I know because I checked myself. She's trying to use the APAC software on the US model. I would have expected to see a boot.bin in there and just swap the fw_all.bin and changing the HWID. Well, no boot.bin so we just changed the HWID. I had to make a RGN_Tool v0.80 to modify the HWID strings as well. I am still waiting for Nadias to try it. She was getting a System Software Missing. I hope that modifying the HWID strings will help.

Anybody have more clues for me to help Nadias? Thanks.

Sorry, i didn't check before but now see it only has one component, the first field in RGN_Tool is fw_all.bin in usual rgn14 [0x0E]. That's not exactly common.

So is it relying on bootloader in RAM or what, how does it work Turbo?

What's being asked in post no. 12, is she wanting to dump regions 5, 12 or something? Region 12 is virtual and region 5 is protected in devices as far as I'm aware. Maybe kunix can help with this ....

Ooooh! Dumping regions. That brings memory from the past. In order to do that, one would need the boot.bin from the device which is the missing piece. When upgrading, the watch must use the boot.bin already stored on the watch. Hopefully, the last fix I made for her will work.

Yes, it's a blast from the past. Although doesn't really seem so long ago that having a way to dump and write regions was so, so exciting. Ooooh, indeed! ... I only just now saw your conversation with nadias on your wiki. Why are we now seeing devices without boot.bin in their firmware ... Why G? For G's sake, why????? [that's rhetorical, i don't expect either 'G' will give any answer ]. BTW, welcome back Pascal, you've been missed ... I only just now saw your conversation with nadias on your wiki.

Approach S60 software version 2.97 Beta
as of October 9, 2017

Code:

Please Login or Register to see the links

Download (5.76 MB)

Code:

Please Login or Register to see the links

Changes made from version 2.95 to 2.97:
• Temporarily disables the separate activity file that is saved during a round of golf.

Approach S60 software version 2.99 Beta
as of November 10, 2017

Code:

Please Login or Register to see the links

Download (5.76 MB)

Code:

Please Login or Register to see the links

Changes made from version 2.97 to 2.99:

• Added back the separate activity file that is saved during a round of golf.
• Fixed issue with saving scorecards at the end of a round.

Approach S60 software version 3.00
as of November 14, 2017

Code:

Please Login or Register to see the links

(4.44 MB)

Code:

Please Login or Register to see the links

Changes made from version 2.90 to 3.00:

• Fixed possible issue with device getting into a bad state and not saving the scorecard at the end of a round.
• Fixed potential memory issues when playing a course with dual greens.
• Fixed possible unit restart if Alerts are set to trigger for a fitness activity.
• Fixed possible issue with smart notifications that don't contain a title or sub-title.

Approach S60 software version 3.71 Beta
as of December 11, 2017

Code:

Please Login or Register to see the links

Download (5.92 MB)

Code:

Please Login or Register to see the links

Changes made from version 3.00 to 3.71:
• Added support for CIQ 2.4.1.