Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 25 of 42 FirstFirst ... 15232425262735 ... LastLast
Results 241 to 250 of 413
  1. #241
    Junior Member
    Join Date
    Oct 2021
    Location
    Germany
    Posts
    3
    Rep Power
    0

    Default

    Please help !
    one question please:
    what name I have to put in step 8 , insted of
    (QuickCure3.rgn)
    I have a fenix5x plus and I need to enter mass storage to delete a folder with maps .
    After I put that folder my clock bricked.
    It loads maps forever.
    My problem is that I can no longer see the folder Garmin in my PC so I ca not delete the folder.


    1) Bricked device fenix 5x plus, Firmware version, 15.40 , HWID 2900

    2) Why and how the device got bricked.: I tried to upload some custom maps

    3) Symptoms: what's wrong in your device?:after power-on, i get the Garmin logo and the copyright notice text then it loads maps forever

    4) Does your pc sees your device ?:
    No

    5) List all the procedures you already :
    Forced Usb conect : Not working
    Forced reebot: Not working
    Master Reset: Not working

    6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads: yes

    7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID

    8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    How to unbrick a nüvi - step by step guide

    I have Garmincure3 but It says
    I put QuickCure3.rgn in the input folder ,
    I select Cure,
    I select Make firmware
    result:
    ramloader has invalid format
    Procesing FAILED


    9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode: Yes but Not working

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

    Thank You
    Spoiler: images
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    Last edited by ciprigfh; 26th October 2021 at 04:54 PM.

  2.    Advertissements


  3. #242
    Junior Member
    Join Date
    Mar 2016
    Location
    Lithuania
    Posts
    4
    Rep Power
    0

    Default

    1) Bricked device MODEL, Firmware version, HWID.
    dezl 580LMT-D, Software version 4.00, HWID 2826

    2) Why and how the device got bricked.
    I don't know, got it like that.

    3) Symptoms: what's wrong in your device?
    When power-on, it shows Garmin logo and restarts itself, and again the same.

    4) Does your pc sees your device?
    As normal no, only when keeping finger on the top left screen.

    5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
    Tried to reach preboot keeping finger on the top left screen, device several seconds shows note SYSTEM then note Loading... and restarts. In those seconds computers sees the device.

    6) Do you have Garmin USB Drivers installed?
    Yes, Garmin USB Drivers 2.3.1.0

    7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
    From G7ToWin HWID 2826

    8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    How to unbrick a nüvi - step by step guide
    Readed and tried, but I can't found .GCD file for my HWID.

    9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode
    Probably yes, but don't know whether the device needs to reboot so quickly in this mode if nothing is done on computer.

    10) Probably no , but do you have NV backup?
    Sorry, but no.
    Last edited by Boki; 25th October 2021 at 06:26 AM. Reason: approved

  4. #243
    VIP Master IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Garman_Nuvi's Avatar
    Join Date
    Apr 2015
    Location
    On the move
    Posts
    233
    Rep Power
    1030

    Default

    Quote Originally Posted by Maldonis View Post
    8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    How to unbrick a nüvi - step by step guide
    Readed and tried, but I can't found .GCD file for my HWID.
    Original
    Code:
    Please Login or Register to see the links

  5. #244
    Junior Member
    Join Date
    Oct 2021
    Location
    Germany
    Posts
    3
    Rep Power
    0

    Default

    one question please:
    what name I have to put in step 8 , insted of (QuickCure3.rgn)
    I have a fenix5x plus and I need to enter mass storage to delete a folder with maps .
    After I put that folder my clock bricked.
    It loads maps forever.
    My problem is that I can no longer see the folder Garmin in my PC so I ca not delete the folder.
    Last edited by Boki; 26th October 2021 at 06:17 PM. Reason: approved

  6. #245
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1058

    Default

    @ciprigfh
    I think you may have confused the instructions. EITHER you directly use the supplied QuickCure3.rgn (unchanged, just safely renamed appropriately as XXXX01000xxx.rgn - see below) OR you use the device's actual firmware to make the Cure3 RGN. It seems like you're trying to make the Cure3 fw from QuickCure3.rgn. QC3 is ready to use after renaming, "XXXX" being your device's HWID and "xxx" being the current fw version loaded to the device, e.g. 290001000154.rgn. Whether you use QC3 or Q3 the RGN's safe-naming convention is the same. Best try with QuickCure3 first as it usually works, but Cure3 always works to re-enable Mass Storage Mode in compatible devices.

  7. #246
    Junior Member
    Join Date
    Oct 2021
    Location
    Germany
    Posts
    3
    Rep Power
    0

    Default

    Processing C:\Users\No One\Desktop\290001000154.gcd
    This is a GCD file.
    No patchable HWIDs detected
    Processing FAILED

    Spoiler: image
    [Only registered and activated users can see links. ]
    Last edited by Boki; 27th October 2021 at 08:06 PM. Reason: unnecessary quote removed, merged two posts, spoiler, approved

  8. #247
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1058

    Default

    It seems the Fenix 5x plus firmware may not be in traditional Garmin format therefore it's not recognized by GarminCure3.exe for patching of file names. Check if it's encrypted because if so there's no help for that as far as i'm aware.

    Have you tried using QuickCure3.rgn? If not and you want to try it, [Only registered and activated users can see links. ]. Rename it to 290001000154.rgn and flash in preboot (at your sole risk of course, i don't know the outcome).

    Another way if it's not encrypted firmware is to try the old original method we used before kunix made his cure3 app. Done by using a hex editor to rename IMG to MIG for example in the firmware RGN to make a cure firmware specifically for by-passing loading map image files on boot. See post #4 here: [Only registered and activated users can see links. ] Also this thread: [Only registered and activated users can see links. ].

  9. #248
    Junior Member
    Join Date
    Nov 2021
    Location
    USA
    Posts
    2
    Rep Power
    0

    Default

    1) Bricked device MODEL, Firmware version, HWID.
    GARMIN NUVI 1340, Software version 6.30, HWID 972

    2) Why and how the device got bricked.

    I tried to install some maps via BaseCamp v4.3.4 witch prompted me to update and i let it, i got a message that a substantial amount of data will be installed.
    I think the map was this "Garmin City Navigator Europe NTU 2020.20 UN FID 8219"
    Near the end installing something happened, witch said that the installation was completed but "not successful"
    The device sat there some time with the PC connected logo and after that it went into "GARMIN LOGO" loop

    3) Symptoms: what's wrong in your device?
    When power-on, it shows Garmin logo and restarts itself, and again the same.

    4) Does your pc sees your device?
    As normal no, only when keeping finger on the top left screen to access preboot mode.

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

    Tried QuickCure3 and it gives me "Update successful" but my PC still can't recognize the device after this operation.


    6) Do you have Garmin USB Drivers installed?

    Yes, Garmin USB Drivers 2.3.1.0

    7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID

    Spoiler: image

    nuvi1340


    8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    How to unbrick a nüvi - step by step guide

    Readed and tried, used nuvi13xxand14xxseries_GCDFile__630.gcd

    I get error message "The GARMIN device is unable to program the requested memory region.
    This could be due to an incompatibility between this application and the GARMIN device.
    If this error continues to occur, please contact GARMIN Technical Support."


    9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode

    Yes, holding upper left corner before powering on.

    10) Probably no , but do you have NV backup?
    Sorry, but no.
    Last edited by Boki; 9th November 2021 at 01:40 PM. Reason: approved, corrected image link, spoiler...

  10. #249
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1058

    Default

    @heresy
    This reply is not timely sorry, i only just now noticed and read your post. If you still need help to solve you may need to give some more info after trying again as below.

    Some thoughts:
    Firstly, 1xxx devices don't use NTU (Unicode) maps, they are only offered NT maps by GarminExpress.

    Secondly, QuickCure3 usually works with 1xxx devices but not always depending on the problem causing the soft-bricking.

    I get error message "The GARMIN device is unable to program the requested memory region.
    This could be due to an incompatibility between this application and the GARMIN device.
    If this error continues to occur, please contact GARMIN Technical Support."
    That error message may be only due to the device and Updater.exe losing communication, for instance by the device dropping preboot mode, or due to some corruption in the cure RGN file, but it can also be indicative of a damaged flash region that cannot be written to. I suggest you re-make the cure firmware and try again to flash but this time ensure that the RGN is loaded to Updater.exe with it's GUI visible on your desktop and the radio button next to "USB Device" selected. Ensure your device is fully OFF, not just in standby. Hold the top LH corner of the nuvi's screen and connect the device to the PC watching the window next to "USB Device" for it's details to appear. IMMEDIATELY you see the window populated, press OK on the GUI and keep holding the screen firmly.

  11. #250
    Junior Member
    Join Date
    Nov 2021
    Location
    USA
    Posts
    2
    Rep Power
    0

    Default

    Thanks for the input, Butters!

    I think it messed it up with the NTU maps, but i had no idea...

    Here's the step by step:

    1. I improvised a "hack" to enter preboot - just a simple spring clamp and a rubber, it gets the job done so both my hands are free work. The USB cable is plugged in my PC and the micro-USB part I plug after setting the updater.

    Spoiler: image

    0 rubber hack


    2. I prepare the .gcd in "GarminCure3 v0.1 by kunix" using "nuvi13xxand14xxseries_GCDFile__630.gcd". I launch the updater and set the USB connection option. The cure gets discovered and i proceed with the steps

    Spoiler: image

    1 gcd load


    Spoiler: image

    2 Discovered


    3. Once I see it discovered i hit Enter and dash for the "Yes" menu with the mouse that is prompted (it says the current software is the same, and so on...) .Here's why i use the hack from 1. to utilize both hands. It starts doing it's thing updating, gets to the point of "Erasing" and here i hit the brick wall - every time i get the "unable to program in this memory region" error.

    Spoiler: image

    3 Nuvi discovered update



    Spoiler: image

    4 Erasing



    Spoiler: image

    5 garmin memory region error


    4. I also got a random error about the updater, no idea if it will be of any use

    Spoiler: image

    updater error



    I tried like 10 times restarting everything, clearing the temp folder, making new cure, setting up the updater, prebooting, connecting and every time it's the same error message regarding the "memory region".

    Some thoughts:
    Am i using outdated .gcd for the cure? If so where can i get most recent one, or one that is more reliable?
    Am i using an outdated version for the GarminCure? This one says v0.1.
    Am i using a wrong data cable, i tried like 3 different ones and all of them discover the nuvi in preboot but i get to the error about "memory region" and that's it.





    Spoiler: image

    updater error



    [Only registered and activated users can see links. ]
    Last edited by Boki; 14th November 2021 at 10:38 PM. Reason: corrected AALL image links, approved

 

 

Tags for this Thread

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
  •