My great thanks to Neil for all his care and help in solving this issue
The device is back alive working with no problem ..
"lolypop000" has solved it and I really want to thank thank you very much
I guess the explanation of solving the problem with her
4th April 2016, 07:15 PM
catymag
Loly is a magician :)
I will mark thread as solved
4th April 2016, 07:29 PM
lolypop000
I like to thank you to have courage ;)
If i explain here what i do, a lot of user will do this in wrong way and they will brick device to point with no return.
If someone will have the same problem, i will create files and step by step tutorial like i do it for you :)
I am happy for you that your device is now back in normal condition.
4th April 2016, 07:38 PM
catymag
@Loly
magician and wise :) :1:
4th April 2016, 08:53 PM
Neil
Great work Loly! As Caty said 'magician and wise', i agree.
A warning here for others from this unfortunate experience which has ended happily only because of lolypop000's knowledge and experience dealing with Garmin firmwares. When flashing firmware whether original or modded by RGN file, unless you know exactly what you're doing, you must always use the 'fail-safe' naming convention of XXXX01000xxx.rgn where 'XXXX' is the HWID of the FIRMWARE being used which should also match the HWID of the DEVICE. See here to find them: [Only registered and activated users can see links. Click Here To Register...]. Also 'xxx' is the firmware [unit software] version without decimal [i.e. V8.30 is shown '830']. Even though the OP used the25x9 firmware in error, if the naming convention of 194701000830.rgn had been used for that firmware then Updater.exe would not have flashed it and reported there are no updates for the device. So when the HWID of the device doesn't match the first 4 numerals in the rgn file name you will get that message and the process is stalled. Change that naming convention [OUT.RGN is most commonly used by experienced modders] and the flash is forced. Even removing one zero from XXXX0100xxx will tell Updater.exe to ignore HWID mismatch and force the flash. Another 'trap' is when using SD card flashes, if the Ldr.bin [boot.bin] is not correct for the device then incorrect information is written to the boot sectors of the unit and it may become irreversibly bricked. Thankfully Loly was able to recover this unit, he'd be one of the few ppl in the world outside of Garmin who could do so using firmware mods.