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

Originally Posted by catymag

If you want HELP in case of a bricked device please follow this:
..............
Write please in your HELP request:

1) Bricked device MODEL, Firmware version, HWID.

2) Why and how the device got bricked.

3) Symptoms: what's wrong in your device?

4) Does your pc sees your device ?

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.

6) Do you have Garmin USB Drivers installed ? [Only registered and activated users can see links. ]

7) If you don't know HWID get it by [Only registered and activated users can see links. ]

8) Write down if you already read or tried [Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]

9) Can you reach preboot mode? If no ,have you followed this? [Only registered and activated users can see links. ]

10) Probably no , but do you have NV backup?

11) Once you get a reply and a procedure to follow from our experts, please give an accurate reply about what you did and obtained results.

I'm writing this because sometimes it needs a lot of posts before understanding what has been already tried and what is needed. Being precise will help you and us in saving a lot of time and curing it
Thanks

Hi,
I have a problem with an older Alpha 100 with TT10, manufactured for the US territory, but used in Europe.
Below are answers to your questions.

1. Alpha 100 with TT10, Current Firmware version 7.8 (updated by mistake), HWID: 006-B1562-00
The device is made for USA, but has been used in Europe for some time. To do that, the firmware was cracked and probably downgraded to Firmware 3._

2. Tried to copy some satellite maps (via BirdsEye), and by mistake allowed PC to update the Firmware to the latest firmware (via Garmin Express), BEFORE doing Backup. I did backup after the fact.
The Alpha 100 would NOT connect to BirdsEye because its license had expired (and it would not accept a new one, before de-registering from the previous owner, which is not important for the story, anyway).
Unfortunately, because of the update, the Radio Function was OFF now, because it reverted to its “original” format – for use within USA, only.
After browsing through forums, I found out about GarminCure3 and Updater. Again, I jumped my gun, and went directly to Firmware 3.0, instead of step-by-step downgrade. I did enter the device into PREBOOT state, and the Updater showed that it copied the file 100%.

3. And then – everything went wrong. The Alpha 100 is now constantly in “Connect Mode” and does not enter the User Interface at all (except for the time that I forced it into Preboot Mode). The Updater intermittently recognizes it, but then drops the link. Sometimes, the “Connect Mode” forces itself over the “Preboot Mode”, but even without it, Updater wouldn’t work anymore.

4. The PC recognizes the device, and I can see the contents of its drive. There is a lot of “trash” piled up during time.

5. Mistakenly updated via Garmin Express, and then mistakenly tried downgrading directly to Firmware 3.0 via Updater. When none of that worked, I formatted the unit using RMPrepUSB and then tried Updater again (after having GarminCure create ORIGINAL firmware). This is what I get – now, the Updater manages to connect to the device, but fails to read it.
See image below

Spoiler: pic

[Only registered and activated users can see links. ]

6. Garmin Drivers are up to date and functioning on other devices
7. HWID: 006-B1562-00 (GarminDevice.xml accessible freely through Windows File Explorer)
8. Tried GarminCure3, bricked the device
9. Yes, Preboot Mode is possible, but the Memory can be accessed through Windows File Explorer also
This is the content of the Garmin Drive, from the backup (see image below)

Spoiler: pic

[Only registered and activated users can see links. ]

10. I don’t know about NV backup
11. Please help!