Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Likes Likes:  0
Results 1 to 2 of 2
  1. #1
    Junior Member
    Join Date
    Apr 2017
    Location
    Brasil
    Posts
    4
    Rep Power
    0

    Default Map 62S Sytem Software missing

    Hi!
    My Map62S stuck on the "System Software Missing" screen and also won´t go into pre-boot mode so that I can flash an RGN file. I´ve tried g7towin app to force an usb connection but nothing. I´ve already fixed another 62S with this problem using an RGN file and garmin updater app and it worked but this one won´t even go into pre-boot mode. Any solution?
    thanks
    Last edited by reimorei; 17th June 2019 at 08:46 PM.

  2.    Advertissements


  3. #2
    Important User Map 62S Sytem Software missing
    Map 62S Sytem Software missingMap 62S Sytem Software missing
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,449
    Rep Power
    1033

    Default

    That message can have two different reasons:
    1. Soft-bricked. The most common and innocuous is software-based in that there has been some corruption in region 14 of flash memory where the main system software (firmware) is stored. That usually happens when the firmware is being upgraded and a glitch occurs leaving region 14 either empty or incomplete. In such a case an otherwise healthy device usually defaults to preboot mode and it's easily fixed by flashing a 'known-good' version of the fw as an RGN file via Updater.exe.
    2. Hard-bricked. The less common but more lethal is hardware-based and cannot be fixed using software solutions. If it's because of physical damage to the flash memory of the device then the device cannot enter preboot mode anyway. Replacement of the flash chip is generally not feasible unfortunately.

    If it's only a soft-bricking even though the device won't go into preboot there is a very slight chance to recover it via sd card provided the xrgn command exists in the firmware and the device is entering far enough into the boot cycle to read from the card. Unfortunately the latter's unlikely because Ldr.bin (boot.bin) is loaded late and by fw_all.bin from rgn14 which in your case it seems is corrupt or empty. You can read here: [Only registered and activated users can see links. ].

 

 

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
  •