Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 12 of 40 FirstFirst ... 2101112131422 ... LastLast
Results 111 to 120 of 392
  1. #111
    Junior Member
    Join Date
    Oct 2014
    Location
    Seoul S. Korea
    Age
    67
    Posts
    7
    Rep Power
    0

    Default

    Quote Originally Posted by Butters View Post
    A couple of questions:
    1. Do you mean you have to terminate Updater.exe because it hangs endlessly with 'Software Loading' on the screen?
    2. Do you mean it will boot with the US firmware loaded? If it does boot then hard reset it and then clear nonvol memory if that's available to your Oregon: [Only registered and activated users can see links. ].

    Usually a drastic change in firmware will cause the device to clear nonvol spontaineously on first boot after the flash finishes successfully, 'Locale' has to be re-selected on first boot afterwards. It seems that doesn't happen because the flash isn't completed. You could also try leaving it with updater running for an extended period to see if it will eventually finish the flash itself.
    Thanks again Butters,

    1. Updater out.rgn gives me error message and stops flashing(attached photo). The difference from previous updater 08901000660.rgn is that "Software Loading" device doesn't turn off automatically. I think updater stopped working due to this error. I let it run more than 1 hour but nothing changed. updater 08901000660.rn gives a quick "software missing" message and turn into a red screen.

    While device is on with "software loading", I tried to run g7towin.exe to find any changes. Then g7towin gave me this original info back. But if I switch off/on again, device stays in korean version.

    2. I don't think US/EU firmware is flashed in a proper way since I turn this device off/on again and this device goes back to previous korean version.

    3. I did a hard reset. This device gives a quick message(I guess "software missing") and gives a red screen in short period, then turn off by itself.
    After hard reset, I turn this oregon 550 in preboot mode and check with g7towin.exe. It is still Korean firmware with serial number 0.



    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    Last edited by shawn_pa; 29th August 2018 at 08:13 AM.

  2.    Advertissements


  3. #112
    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,440
    Rep Power
    1033

    Default

    Yes it's absolutely certain that the full US/EU firmware flash isn't properly finished. Let's try to address the 'System Software Missing' problem firstly. That message means that the fw_all.bin flashed to region 14 (0x0E) is either corrupt or incompatible with the device. In your case it'll be the latter. So if you can flash the correct fw_all to region 14 we may be able to go further in recovery. This will involve flashing a "hybrid" firmware, composed of the APEC boot.bin and the US/EU fw_all.bin. To make it, do this:

    • Open the US/EU fw in RGN_Tool and save the second section (fw_all.bin) somewhere convenient.
    • Open APEC fw in RGN_Tool and press 'Load' on its second section and load the previously saved US/EU fw_all.bin to it.
    • In HWID override put 1209 and in SW Version override put 251.
    • Press RGN button and save the file as 120901000251.rgn.

    You should be seeing this before you save the RGN:

    [Only registered and activated users can see links. ]

    If you want to check to be sure you've done it correctly, the resultant file should be 11,193,419 bytes with an MD5 hash of A4A342D342B1B6430C088FD723E95736. To flash it proceed as before with Updater.exe with the Oregon in preboot mode. Good luck. All this is entirely your risk of course.

  4. #113
    Junior Member
    Join Date
    Oct 2014
    Location
    Seoul S. Korea
    Age
    67
    Posts
    7
    Rep Power
    0

    Default

    Thank you very much Butters.

    Now this oregon 550 back to life :-) fw_all.bin came back to US version. This boots normally.

    I feel like to apply updater OUT.rgn so that I can fix boot.bin back to US.

    How do you think? If updater OUT.rgn flashed successfully, I think I can go back to US firmware.

    Now I am a hybrid with korean boot.bin and US fw_all.bin as you said. Thank you very much for your great helps again.



    Read [Only registered and activated users can see links. ]
    Last edited by Midnight Blues; 30th August 2018 at 05:36 PM. Reason: removed quote

  5. #114
    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,440
    Rep Power
    1033

    Default

    Certainly it shows that the korean boot.bin is compatible enough with the US firmware. First I should explain a little about how the boot components of the firmware work: You will see from RGN_Tool's GUI that the boot.bin is flashed to a region "0C" and that's the decimal number "12" in hex, ie 0x0E. Region 12 seems to be a virtual region and it in turn writes data to 2 other, regions 5 and 43 from memory, which actually boot the device. So now we need to try to overwrite rgn12 again with the US boot.bin so in turn it can write the correct data to the other two physical regions. You'd maybe think, "Well the Korean data overwrote them ok so why wouldn't the US data now write back just the same?". Unfortunately it's not always that simple and many things can go wrong because you're trying to write to regions which are being used in the process. It might work and it might not. It might even kill the device completely. In short, you now have two choices: (i) Try again to flash full US/EU firmware with it's native HWID 0896 and hope it doesn't kill it; or (ii) Leave it as it is and see if it can operate normally with the hybrid firmware in 'real world' operations.

  6. #115
    Junior Member
    Join Date
    Oct 2014
    Location
    Seoul S. Korea
    Age
    67
    Posts
    7
    Rep Power
    0

    Default

    Butters,

    I am testing this hybrid oregon 550(Korean boot.bin and US fw_all.bin). It looks like running OK so far.

    I want to minimize risk of bricking this Oregon again...

    What may be problems of using this hybrid oregon 550? I guess I can't have licensed map since I can't provide proper serial number.

    There can be problems caused by incompatible firmware. I can't upgrade.

    These are the problems caused by a hybrid firmware. Am I missing other problems?

  7. #116
    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,440
    Rep Power
    1033

    Default

    Quote Originally Posted by shawn_pa View Post
    ............
    What may be problems of using this hybrid oregon 550? I guess I can't have licensed map since I can't provide proper serial number.
    Does it have a Lifetime Maps entitlement? If not the lack of a UID may not be a problem. Have you checked the device's GarminDevice.xml file for the UID as well as in G7ToWin? Look at this: [Only registered and activated users can see links. ]. GE uses the UID read from the XML file only I think.

    There can be problems caused by incompatible firmware. I can't upgrade.
    Yes you can but you have to again combine the US and Korean firmwares and flash in preboot as an RGN. If you try to update with GarminExpress or WebUpdater it will read the Korean HWID and supply full Korean firmware.

    These are the problems caused by a hybrid firmware. Am I missing other problems?
    None that i can think of presently. If there is too much problem in 'real world' operation you could take the risk and try the flash to full US native fw, alternately firstly with full US changed HWID from 0896 to 1209, and then [maybe or maybe not] try the native fw unchanged. Only you can reasonably assess the risk vs. benefit aspects I'm sorry.

  8. #117
    Junior Member
    Join Date
    Jun 2015
    Location
    Aus
    Posts
    6
    Rep Power
    0

    Default

    1) Bricked device MODEL, Firmware version, HWID. Astro 320, 4.50, 1339

    2) Why and how the device got bricked. Not sure.

    3) Symptoms: what's wrong in your device? Kept displaying "Memory Full" Now will only load Garmin page. Wont turn off without taking batteries out.

    4) Does your pc sees your device ? No, even after running Cure.

    5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
    Wouldn't Master reset. Garmin Webupdater starts software installation then pops up with corrupted software message. Have installed rgn file made in Garmincure3 tool. It flashed cure firmware, updater said it had updated successfully. Astro turned off then back on like it should but did not go into mass storage mode, can not see on computer to delete files. Just went back to Garmin screen and disconnected from computer. When I put astro into reboot mode I can see its connected to computer in device manager. Have tried this process many times with different cables.

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

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

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

    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.

  9. #118
    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,440
    Rep Power
    1033

    Default

    @JackyATR
    The combined symptoms of (i) WebUpdater failing with that message, (ii) no Mass Storage Mode before or after cure fw loaded and (iii) the device showing 'Memory Full" message could mean there is serious flash corruption and probably it's actually physical damage. Such damage cannot be corrected by regaining Mass Storage Mode regardless because it's not just corrupt files at fault. This device has rrgn/ergn/xrgn commands enabled in it's firmware so you could try to dump some regions via SD card with rrgn command, particularly rgn48 and rgn83 because one of those two regions will contain all the files usually visible in MSM. See here: [Only registered and activated users can see links. ].

  10. #119
    Junior Member
    Join Date
    Jun 2015
    Location
    Aus
    Posts
    6
    Rep Power
    0

    Default

    Thank you for getting back to me.
    Was thinking there was something major wrong with it. Will try what you have suggested.
    Thank you again.

  11. #120
    Member
    Join Date
    May 2015
    Location
    Bahía Blanca
    Posts
    16
    Rep Power
    0

    Default

    Hi all!
    I am in trouble...
    I have a Garmin nuvi 1410 and it is not recognized by the PC, "the USB device is not recognized".

    I wanted to make a CURE with the GarminCure kunix software but it was impossible for the PC to recognize it again even in preboot mode..

    Then I decided to update the firmware through an SD card, the GPS had version 5.80 and I decided to take it to 6.10:
    What I did was download the file nuvi13xxand14xxseries_GCDFile__610.gcd and rename it as gupdate.gcd, place it inside a folder named "Garmin" and paste the folder in the root of the card. When I put it on the gps off and then turn it on it took the update and installed perfectly, but it was still not recognized by the PC, so I decided to install the CURE firmware.

    With the GarminCure3, I created the corresponding CURE .rgn file with the nuvi13xxand14xxseries_GCDFile__620.gcd and then with the RGN_Tool_V094 transform it into .gcd. I placed it renamed as gupdate.gcd (the CURE firmware) and it got stuck forever on the Garmin screen.

    Before doing the CURE I took these photos:

    [Only registered and activated users can see links. ]

    Does anyone have any idea what I can do to solve this problem?
    Thank you!
    Removed Unit ID number from top image and fixed images to display properly. Disclosing your device's UID publicly can be dangerous.
    Last edited by Vasconia; 5th December 2018 at 06:20 PM.

 

 

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
  •