Thread: Alpha 100 US in EU, problems after fw downgrade & cure used

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.

Originally Posted by Butters

Ok, the problem could have started right there, forcing a downgrade to such a low version in one step. Please confirm if you did that downgrade by using Cure3 fw V3 with V7.8 original onboard which is what i think has happened.

Yes, that is right.

Originally Posted by Butters

Persistence is paramount when a device is not sticking on the logo screen but either 'bootlooping' or turning off spontaneously. In your case it's entering preboot as evidenced by the fact it's being recognized by Update.exe but because a flash isn't initiated quickly enough it's then exiting preboot and attempting to boot normally. To explain, when Updater detects the device in preboot (it only detects devices in preboot, or 'boot-block' as Garmin sometimes calls it for outdoor devices), if a flash isn't started in a short set period then the device exits preboot. For some modern devices that's a matter of mere seconds, many older devices had lots of preboot idle time like 30 seconds. However once a flash is initiated the device will remain in preboot provided the connection isn't broken or the flash's transmission of data packets interrupted.

The device now, does remain in preboot, until I release the button. But, the Updater stucks as in the picture I sent in the original post.

Originally Posted by Butters

So you still see it in Mass Storage Mode which is a good thing, regardless of whether it's been enabled by cure fw or not. See my final question below, no "trash" should be there after a complete successful reformat.

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. ]

Originally Posted by Butters

Well, i'm unsure if you mean you used V3 only initially and then 7.8 as asked above. It's important we know what it's running as it changes how we proceed whether it's got cure V3 or V7.8 or indeed even original of either version. Also it's contradictory to say "Updater manages to connect to the device, but fails to read it" because when it connects it is "reading it" by checking the device's ID info evidenced by displaying the info in the window next to 'USB Device'.

Sorry. What I meant is that it Updater stucks as in the picture from the original post.
I now, don't know what was the original fw version of the device, as I didn't pay attention, when I connected the device to Garmin Express. The first thing that happened was the update to v7.8 (for no reason except that I was careless). When it updated, the device still DID work - it showed the maps and everything, but, couldn't connect to collars, because the Radio Function was off.
Then, I went with GarminCure3 and Updater. And although it appeared that the process went all the way, the changes were negative - the device "bricked".

Originally Posted by Butters

What isn't clear to me is whether you have Mass Storage Mode (MSM) available because of Cure3 fw though.

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.

Originally Posted by Butters

So again, i'm not sure of the timeline here. Is this still the state of the internal memory right now? You said that you re-formatted using RMPrepUSB however the dates of folders and files raise questions. GarminDevice.xml shows as 29/5/2020 for instance.

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.

Below is a screenshot of the RMPrepUSB window and related values

Spoiler: image

[Only registered and activated users can see links. ]

Originally Posted by jupigarmin

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.

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.

Originally Posted by jupigarmin

..........
This is the content of the Garmin Drive, from the backup (see image below)

Spoiler: pic

[Only registered and activated users can see links. ]

Originally Posted by jupigarmin

....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.

Originally Posted by Butters

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