Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    Junior Member
    Join Date
    Apr 2011
    Location
    Malaysia
    Posts
    8
    Rep Power
    0

    Default 64s to a Different Region

    Currently, I am using RGN_Tool V0.82, with GPSMAP64s SW Version 4.2 and SEA RGN Version 2.30
    I following the instructions as per steps recommended in RGN_TOOL.
    After flashing it to GPSMAP64s, it prompted "System Software missing" and ESN ID: 0

    I have full backup of both units.

    Please help me.
    Thanks.

  2.    Advertissements


  3. #2
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,606
    Rep Power
    5320

    Default

    These two GPSMAP64s firmware(SEA and US/EU)are completely different firmware with different HWID and regions sizes.

    [Only registered and activated users can see links. ]
    IMHO not possible to cross flash them.
    I hope you did a NV backup
    Otherwise you can try to use kunix's cure and see if you can unbrick it, but "ESN ID: 0" is not a good sign
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    You have to navigate to get to the good.
    Nuvi1250/Nuvi 34xx/Nuvi 2200/Nuvi 66/Oregon 600/Galaxy S5 MM 6.0.1/TomTom GO/iGO Nextgen Avic,Basar,Isr.Gift/Navigon
    Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.

  4. #3
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,399
    Rep Power
    1434

    Default

    It seems that PCB P/Ns are not written in either firmware so Caty you may be right about cross-flash not being possible.

    @gpskarakuri
    Cross flashing won't work if PCB P/N aren't matched and such attempts can hard-brick devices in many cases. [Only registered and activated users can see links. ]

    It's worth trying to flash it back with original firmware if you can still get preboot mode. From your info it seems that you used hybrid firmware [US boot.bin and SEA fw_all.bin]. If you retained HWID 1859 then flash the full US fw V4.50 as 18590100450.rgn with no override in RGN_Tool. Name the US/EU firmware OUT.rgn if you didn't use HWID override in RGN_Tool to make the hybrid fw or you used full SEA fw HWID 2123. Naming the RGN other than <hwid>01000<swv> will force the flash in Updater.exe regardless of the HWID presently on the unit so it's never to be used lightly.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  5. #4
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,606
    Rep Power
    5320

    Default

    Quote Originally Posted by gpskarakuri View Post
    Currently, I am using RGN_Tool V0.82, with GPSMAP64s SW Version 4.2 and SEA RGN Version 2.30
    Where did you find "SEA RGN Version 2.30"?
    Code:
    Please Login or Register to see the links
    v.2.20 is the latest.
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    You have to navigate to get to the good.
    Nuvi1250/Nuvi 34xx/Nuvi 2200/Nuvi 66/Oregon 600/Galaxy S5 MM 6.0.1/TomTom GO/iGO Nextgen Avic,Basar,Isr.Gift/Navigon
    Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.

  6. #5
    Junior Member
    Join Date
    Apr 2011
    Location
    Malaysia
    Posts
    8
    Rep Power
    0

    Default

    @catymag
    sorry mistype, it is indeed sw v 2.20

    @neil
    We managed to flash the unit back to its original US ver. 4.50
    although we follow the steps inside the wiki, we are still unable to flash the GPSMAP64s US version to SEA version 2.20
    we still get the software missing error

    since both versions have different Region and size, how can we overcome this problem?
    [Only registered and activated users can see links. ]
    Last edited by gpskarakuri; 13th August 2016 at 04:28.

  7. #6
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,399
    Rep Power
    1434

    Default

    The method you've reproduced above is what i referred to as flashing hybrid firmware i.e. US boot.bin & SEA fw_all.bin with retained HWID 1859. That's a well-know generic method which doesn't always work, often because of differing region layouts, however in the case of the two firmware used the bin sizes are not greatly different and the same regions are populated. [Only registered and activated users can see links. ] to understand what 'system software missing' message might mean.

    You could use SD text command 'rrgn' to dump region 14 [0x0E] from your US device to ensure it's total available size exceeds that of the SEA fw_all.bin [Must be more than 10,918,400 bytes because if less space is available then it can't be flashed]. That will eliminate another possible reason for region 14 not being flashed. If you haven't already [Only registered and activated users can see links. ], then do it before going any further. Dump region 14 via "rrgn,14,1:/14.bin" because that bin file will be the total available size of the region, not just the size of fw_all.bin in the firmware.

    If you are determined to press on with this i would STRONGLY advise against using full SEA firmware to flash initially as it's seemingly not possible to determine by firmware inspection that the PCB P/Ns match. All at your risk of course anyway. BTW, using an incompatible boot.bin can potentially hard-brick a device for the third reason detailed in that linked post.

    If the US boot.bin is incapable of flashing the larger SEA fw_all.bin, then you could try compressing it so it might then be handled successfully by the US boot.bin: [Only registered and activated users can see links. ].
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  8. #7
    Junior Member
    Join Date
    Apr 2011
    Location
    Malaysia
    Posts
    8
    Rep Power
    0

    Default

    @Neil

    We have tried compressing but it is showing Error while compress the fw_all.bin

    [Only registered and activated users can see links. ]

  9. #8
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,399
    Rep Power
    1434

    Default

    Not supported firmware. Maybe kunix can do something about if if you ask him nicely. Still no guarantee it'll work compressed anyway.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  10. #9
    Junior Member
    Join Date
    Apr 2011
    Location
    Malaysia
    Posts
    8
    Rep Power
    0

    Default

    @Neil
    Thanks Neil, I will try asking him

  11. #10
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,038
    Rep Power
    601

    Default

    You called me. Ao I'm here.
    The NAND region layouts on both devices seem to be the same (and there are 13MB for fw_all.bin), so you should not have any problems with not fitted fw_all.bin.
    So your problem is different and gfwpack.exe will not help you.
    I can suggest publishing your cross-flashing firmware so that we can check it.

    Also where do you see ESN:0? In updater.exe device list? This is strange... as bootloader remains the same. You didn't flash SEA's boot.bin, right?

 

 
Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.