Likes: 
Reply With Quoteworks great many thanks bro
nüvi 25x9 Software Version 8.80, UID: 390570xxxx, HWID: 390570xxxx
------------------------------------------------------------------------------
Parsing "del,0:/.System/gupdate.gcd"
Success
Parsing "rrgn,154,2:/154.bin"
Success
Parsing "ergn,14"
Success
Parsing "reboot"
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 121 to 124 of 124
-
7th August 2021, 02:26 PM #121Important User
- Join Date
- Jul 2017
- Location
- CA
- Posts
- 1,466
- Rep Power
- 1059
The device needs to partially boot to load from card, unfortunately many unhealthy devices which cannot enter preboot also cannot read from card. The file Ldr.bin is actually executed by the firmware and quite late in the boot process, after 'Loading Maps' appears on screen in fact. You could try again with text commands. This shouldn't make anything worse however it's entirely your risk to proceed, read on if you want to try:
- Clean the SD card to be sure of correct syntax and extract this directly to the card: [Only registered and activated users can see links. ]
- Ensure the device is fully OFF, not just in standby (if necessary, force it off by holding the power button down until it it goes off);
- Insert the card and power the device on (if battery is low connect an external power source which will power it on but not a computer USB port);
- Hopefully it will read the text command and delete gupdate.gcd from .System if present, dump a copy of the nonvol region 154 into the root of the card and finally erase region 14 forcing it into preboot mode.
If the device just sticks on logo screen without loader message appearing then the card hasn't been read.
-
7th August 2021, 03:20 PM #122Junior Member
- Join Date
- Apr 2013
- Location
- Morocco
- Posts
- 8
- Rep Power
- 0
Last edited by driversat; 7th August 2021 at 03:22 PM.
-
7th August 2021, 11:54 PM #123Important User
- Join Date
- Jul 2017
- Location
- CA
- Posts
- 1,466
- Rep Power
- 1059
@driversat,
You may already know the following however others with similar problems but less experience may also read this thread so to explain a little further:
The GCD file is deleted in case it was corrupt and causing the partial-bricking. Also if left onboard it may try to reverse a subsequent fw flash using RGN in preboot. The 154.bin can be valuable to recover a problematic device in future and you should [Only registered and activated users can see links. ] after each fw flashing then make another [Only registered and activated users can see links. ] once you've finished recovering the device this time. That's because some fw manipulations can cause minor errors in the nonvolatile memory, even a byte or two of bad/corrupt data can lay dormant but return to cause operating problems or even sometimes even irretrievably brick a device in the future.
If you're going to use text commands ongoing (for instance to load patched fw
), the same microSD can be used with altered commands in the "update.txt" file provided you remove "last-id.bin" file from the 1947 folder created from the previous use.
-
10th November 2024, 07:13 AM #124Junior Member
- Join Date
- Sep 2024
- Location
- Tanunda South Australia
- Posts
- 2
- Rep Power
- 0
I used the procedure to successfully unbrick a Garmin DriveAssist 51 (Australia)
Just two notes.
1) I am using windows 11. I had to run GarminCure3.exe in Administrator Mode
2) To get into preboot mode press on the G of Garmin when it starts.
Bookmarks