Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 31

Hybrid View

  1. #1
    Important User Alpha 100 US in EU, problems after fw downgrade & cure used
    Alpha 100 US in EU, problems after fw downgrade & cure usedAlpha 100 US in EU, problems after fw downgrade & cure used
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Our server directly accepts files with extensions apk; bmp; cab; deb; doc; jar; jpeg; jpg; pdf; png; sis; sisx; and txt. Any other type of file or a folder must be compressed to an archive in rar or zip format as those 2 types are also accepted.

    I've downloaded your XML file, the first thing of note is this:
    Model>
    <PartNumber>006-B1562-00</PartNumber>
    <SoftwareVersion>770</SoftwareVersion>
    <Description>Alpha 100</Description>
    </Model>


    Of course there's been a lot of flashing attempts since you made that backup, so it's unlikely V7.70 is onboard now, almost certainly it's V3.00 cure fw but i'd have liked to know for sure. What's noteworthy is that you firstly updated with GE to V7.80 and since then have flashed with V3.00 as cure fw so i do wonder why 7.70 shows on the XML from the backup. It would be better knowing 100% what's loaded now which is why i was hoping that the XML file had been recreated on a recent boot attempt however i'm going with it's V3 as a likely bet and used the boot.bin componenent of it to make Ldr.bin for this attempt.

    So let's see what we can get off it now with a media card. Please read the disclaimer below before you go ahead, this isn't without risk but is normally quite safe to do. Behind a spoiler below i've attached a file for you to use, in it are text commands to dump copies of the device's various regions. Extract "Copy_To_Card.zip" directly onto a clean microSD of at least 4GB size formatted FAT32 then follow this:
    • Ensure the battery is fully charged
    • When charged, ensure it's FULLY OFF, even if you have to force it off by holding the power button down for a while
    • Place the card in the Alpha
    • Power it back on and wait
    • "Loader" or "Software Loading" or a similar message should show on the screen
    • Don't touch any buttons or interfere with it until it finishes, you'll know it has when it tries to re-boot but sticks on the start screen
    • Turn it off again and remove the card

    Spoiler:
    [Only registered and activated users can see links. ]

    Connect the card to your PC and examine the contents, hopefully there'll be numerous BIN files in the root alongside the Garmin folder, many will have 0 bytes however. In Garmin\Updater\1562 folder there should be 2 new files named "last_id.bin" and "update.log". Please compress them into a RAR or ZIP and post the archive file here.

    Disclaimer: All flashing carries some risk. Although a certain procedure may be quite safe in a healthy device, it can have adverse effects in some devices which are affected by previous failed or inappropriate software flashings. All possible care has been taken in compiling the flash files however all and any risk is carried by you, the end-user.

  2.    Advertissements


  3. #2
    Member
    Join Date
    Jun 2020
    Location
    Pristina
    Posts
    17
    Rep Power
    0

    Default

    Hi Butters,

    I did as you instructed.
    Formatted the SD Card to FAT32 (it was exFat), and it has enough space (56GB).
    Then, I extracted the "Copy_To_Card.zip" to SD Card, and started the device.
    The start "logo" appears and then, the device again goes to "Connect" mode, and after 3-4 seconds, turns off by itself.
    Nothing appears on the screen, no word "Loader", which usually appears in other devices (and even on this device, sometimes, with the Updater.exe), or anything else (word or image).
    However, everything is still accessible via Windows Explorer from the PC.
    The files you mention are there, and I have compressed them into a zip archive, hereto attached.

    Spoiler: attached
    [Only registered and activated users can see links. ]


    I hope you can find something there, which will help.

    Regarding the GarminDevice.xml, and the fw v7.7 - that might also be my doing. I checked when was the fw v7.8 published on Garmin website, and it says 16th of June 2020. I had the device BEFORE that, so, I suspect that at the beginning, when I was trying to be a "know-it-all" screw-up, the initial update must've been to v7.7, and later on to v7.8
    Since I only noticed v7.8 Update before it bricked, I never suspected that there have been two updates, one after another.

    I don't know if this can be of any help, but, I think that is why the GarminDevice.xml shows v7.7

    Yesterday, I was using the fw v7.8 with the Updater.exe, and maybe that was wrong. But, the message was saying that "The Current Version is the SAME as the update version", so, that was confirming what I thought.
    Last edited by Boki; 26th June 2020 at 05:36 PM. Reason: approved

 

 

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
  •