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

    Quote Originally Posted by jupigarmin View Post
    Hi Butters, first of all, thank you very much for your reply. Being a sort of novice with the device, I beg your patience, even though I might sound silly.
    It's ok, i'm patient by nature and enjoy solving problems and anyway you do not sound silly..... however, i do think you've quite compounded the original problem by trying to solve one that didn't exist so we need to unwind a little and get things back to where the Alpha at least boots.

    So here's what i think has happened in order:
    • You had an unknown version of older fw onboard ( V3.x?) which doesn't disable US frequencies in EU.
    • Using GarminExpress, you accidentally updated to V7.8 and disabled US frequencies.
    • You then tried to solve the problem the wrong way by using Cure fw to downgrade to V3.
    • The device then stuck during startup and you thought it was bricked. (*see below)
    • So now unfortunately the device is not accepting ORIGINAL V3 fw via Updater.exe.

    ^^Correct?

    *Now here's the thing: In fact it's meant to not fully boot with cure fw loaded, it's intentional that it doesn't load files so that MSM can be used to remove corrupt or incompatible files and/or reformat internal memory - but you didn't have that problem at all anyway. The sudden downgrade to V3 using either original or cure fw would also very likely caused another problem regardless of course and that may be the reason Updater.exe is now being a b*tch.

    I have formatted the drive with the RMPrepUSB, and then copied the files from the backup again. Now, I did reformat the drive again. The device also has a flash drive (SD Card). After the formatting, I removed the SD Card, and pressed the start button - the device started, and even without the USB cable, it comes to the same (see picture below).
    [Only registered and activated users can see links. ]
    Your pic was not successfully attached so post it again if it's important info ongoing, but if it's only a shot of the device's screen stuck mid-boot don't bother.

    As I said, the device does have an SD Card. At this point, nothing works, so, I don't know if the SD Card initiates or not. Anyway, it DOES show on Windows Explorer, so, I can see its contents, and it is even recognized by RMPrepUSB.
    Another point, please remove the card from the device for the time being. We might have to use it later on to try something else if Updater.exe still doesn't work in the usual way to flash V3 original fw, but it's better it's not in the device while attempting recovery with Updater.

    The picture of the Garmin Folder, was what I re-copied to drive after reformating. Today, I did another wipe with RMPrepUSB, so, now, the drive is empty. The device remains in "Connect" mode (as in the picture above), and it turns off after only few seconds when not connect with USB cable.
    But, I do have the backup, although, it is made AFTER the fw was updated to 7.8 - so, even if I do copy it back on the drive, it does NOT work, and the device does NOT initiate, which probably means that I screwed up badly.............
    For the moment please don't do anything other than what i suggest. In particular, don't re-format again (it won't help and never did) and don't copy files back to the empty internal memory, we probably will need to do that later though.

    So working on the assumption that it's got cure fw V3 still onboard, please continue trying to flash ORIGINAL fw. If it won't accept V3 then flash V7.8. Also try other USB cables, use a desktop PC if possible and only a REAR USB2 port without a hub (not USB3). Be persistent. Sometimes it takes dozens of attempts to complete a flash using Updater with a stubborn device. Now if it still won't complete the flash don't panic or be tempted to try other things without referring back here because we do have other things to try but it gets riskier trying other methods when we can't be sure what's causing Updater to abort the flash now.

    Please continue trying to get a complete flash and meantime post a copy of the GarminDevice.xml for me to examine but first open the copy in a text editor (Notepad is fine to use for this), Look for "<Id>" near the start, you'll see <Id>1234567890</Id> and remove or disguise the 10 digits before compressing into a ZIP or RAR and attaching to your post.

  2.    Advertissements


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

    Default

    Quote Originally Posted by Butters View Post
    So here's what i think has happened in order:
    • You had an unknown version of older fw onboard ( V3.x?) which doesn't disable US frequencies in EU.
    • Using GarminExpress, you accidentally updated to V7.8 and disabled US frequencies.
    • You then tried to solve the problem the wrong way by using Cure fw to downgrade to V3.
    • The device then stuck during startup and you thought it was bricked. (*see below)
    • So now unfortunately the device is not accepting ORIGINAL V3 fw via Updater.exe.

    ^^Correct?
    I guess you are right! Now, there is NO Garmin folder on the drive of the device, and no SD card.


    Quote Originally Posted by Butters View Post
    Your pic was not successfully attached so post it again if it's important info ongoing, but if it's only a shot of the device's screen stuck mid-boot don't bother.
    Here's the picture that shows on the screen, when not in preboot (regardless if it is connected to USB or "freestanding")
    Spoiler: pic 1
    [Only registered and activated users can see links. ]



    Quote Originally Posted by Butters View Post
    Another point, please remove the card from the device for the time being. We might have to use it later on to try something else if Updater.exe still doesn't work in the usual way to flash V3 original fw, but it's better it's not in the device while attempting recovery with Updater.
    I did

    Quote Originally Posted by Butters View Post
    So working on the assumption that it's got cure fw V3 still onboard, please continue trying to flash ORIGINAL fw. If it won't accept V3 then flash V7.8. Also try other USB cables, use a desktop PC if possible and only a REAR USB2 port without a hub (not USB3). Be persistent. Sometimes it takes dozens of attempts to complete a flash using Updater with a stubborn device. Now if it still won't complete the flash don't panic or be tempted to try other things without referring back here because we do have other things to try but it gets riskier trying other methods when we can't be sure what's causing Updater to abort the flash now.

    Please continue trying to get a complete flash and meantime post a copy of the GarminDevice.xml for me to examine but first open the copy in a text editor (Notepad is fine to use for this), Look for "<Id>" near the start, you'll see <Id>1234567890</Id> and remove or disguise the 10 digits before compressing into a ZIP or RAR and attaching to your post.
    So, I followed the instructions, and here's what happens.
    I have the Updater.exe and the fw v7.8 in the same folder.
    I can enter the preboot mode without any problem. The Updater recognizes the device. For couple of times, it shows this error message, and then, falsely shows that it is updating the software.
    I changed the USB slot from the front to the rear of the PC – same thing.
    Spoiler: pic 2
    [Only registered and activated users can see links. ]


    As you can see, the software version shows to be 3.2, although the version in the folder is 7.8.
    If I hold this window for longer than 10 seconds, the device’s screen goes black (NOT OFF), and the Updater loses the connection again.

    After a couple of times, it shows another error message (below).
    Spoiler: pic 3
    [Only registered and activated users can see links. ]


    After several more times, the following message came up (below). Now, it shows the version 7.8 and asks if I want to replace it with the same version. I pressed Yes. A Runtime Error message appeared, and disappeared in a second. Along with it, the Updater crashed and “disappeared” also. I though it could be because I left the device for a dozen seconds, before pressing the OK button on the Updater.exe window, but the same thing repeats itself every time, if I persist long enough.
    Spoiler: pic 4
    [Only registered and activated users can see links. ]


    I went again at it, and I pressed yes, and as the bar started to move, the screen went black again, and the connection was lost.
    Spoiler: pic 5
    [Only registered and activated users can see links. ]


    I repeated the cycle several times. By the time I reach the step where it shows fw version 7.8, the screen goes black, and the connection is lost, or, the Runtime Error appears, and the Updater.exe crashes.
    This is where I stopped, and made this post.
    With a risk of sounding redundant - I hope there's still hope.
    Last edited by Boki; 25th June 2020 at 05:02 PM. Reason: spoilers!, approved

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

    Default

    The results you're getting from Updater attempts are typical of one of two things: (i) a physically damaged flash (unlikely i think); or (ii) a poisoned non-volatile region that's so corrupt it's preventing proper flashing from Updater (most likely, considering the recent history). The former is not repairable by software means and is economically not feasible to fix, the latter is likely recoverable provided we can fix the problem via SD card txt commands.

    Quote Originally Posted by jupigarmin View Post
    ..........
    This is the content of the Garmin Drive, from the backup (see image below)
    Spoiler: pic
    [Only registered and activated users can see links. ]
    Quote Originally Posted by jupigarmin View Post
    ....l. Now, there is NO Garmin folder on the drive of the device, and no SD card.
    I'd rather not press ahead with this without seeing the device's GarminDevice.xml as i asked for in my previous post, you'll find the older copy in the Garmin folder of the back-up you have shown in that pic quoted above but also please check again that there's no Garmin folder presently on the device. If it's disappeared that isn't the most troubling but if it's there i mostly need a copy of the XML from it too. Give me both in that case for comparison, just remember to remove the Unit ID.

    With a risk of sounding redundant - I hope there's still hope.
    There's more to try still and next i want to see if it can still both read commands from and write to the SD card as mentioned.... but before we try that it's ideal to know exactly what's in that XML file, the back-up one AND most importantly, the current one from the device.

  5. #4
    Member
    Join Date
    Jun 2020
    Location
    Pristina
    Posts
    17
    Rep Power
    0

    Default

    Quote Originally Posted by Butters View Post
    I'd rather not press ahead with this without seeing the device's GarminDevice.xml as i asked for in my previous post, you'll find the older copy in the Garmin folder of the back-up you have shown in that pic quoted above but also please check again that there's no Garmin folder presently on the device. If it's disappeared that isn't the most troubling but if it's there i mostly need a copy of the XML from it too. Give me both in that case for comparison, just remember to remove the Unit ID.

    There's more to try still and next i want to see if it can still both read commands from and write to the SD card as mentioned.... but before we try that it's ideal to know exactly what's in that XML file, the back-up one AND most importantly, the current one from the device.
    The GarminDevice.xml file has "disappeared" when I formatted the drive with RMPrepUSB. I didn't find a way to upload the file here (it only accepts .png files), so, I am hereto sending the hyperlink from Wetransfer, so you could download the file.

    [Only registered and activated users can see links. ] The link is good for 24 hours

    I hope the problem is "soft", because the device didn't suffer any physical damage since I got it, and also, since I can manage to read-write the drive
    Thanks

 

 

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
  •