Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 13 of 13 FirstFirst ... 3111213
Results 121 to 127 of 127
  1. #121
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    933
    Rep Power
    141

    Default

    I certainly didn't understood perfectly what you were asking for, also i simply wanted to make it clear about 'patching' so that his thread doesn't end up as a 'de facto' place for users to get help with that because of their difficulty getting protected devices into preboot to load a patched RGN. If you wish to load a higher version ORIGINAL firmware you can do that quite easily with a GCD file even if your device has USB hardware problems, regardless of whether the lower version is patched or not: Simply name the downloaded file from "nuvi25x9_880.gcd" to "gupdate.gcd" and place it in a folder named Garmin in the root of the microSD card, insert the card and turn the nuvi on. However if that present version of fw loaded (original or patched) is already V8.80 you may as well just load individual BIN files via txt commands. If you're wanting to know specific commands, or how to obtain the BIN files from a GCD, how to use Ldr.bin (boot.bin) etc. then please ask precisely what you need to know.

  2.    Advertissements


  3. #122
    Member +
    Join Date
    Jul 2012
    Location
    Bosnia, Republic of Srpska
    Age
    42
    Posts
    49
    Rep Power
    10

    Default

    We finally understood each other. I try to be brief and clear, but I become incomprehensible. My bad English only makes things worse.

    My nuvi 2559 has the latest 8.80 software version, but it doesn't work properly. I would like to reinstall the software. I have tried gpupdate.gcd several time before and failed. I need help reinstalling with a SD card.

    I know how to open the firmware using the RGN_Tool.exe program, but I don't know what to do next. Also, I don't know which text commands I should enter. My only experience with Ldr.bin is backing up Region 41/154.
    Last edited by Boki_Srb; 18th September 2020 at 10:49 AM. Reason: removed unnecessary quote

  4. #123
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    933
    Rep Power
    141

    Default

    Ok, i'll just make an SD kit for you to flash using original V8.80 fw. You'll have to be a little patient though, as i have other things to attend to but will do it in the next day then post a link for you. Standby please.

    EDIT: Here is the kit for HWID 1758 device V8.80, behind spoiler. Please read the warning and instructions particularly regarding checking the device's HWID before using:
    Spoiler:
    It's essential to confirm the HWID before using SD to flash. That's particularly so when Garmin has made more than one device with the same MODEL NUMBER but with different HWIDs as is the case with US/EU nuvi 25x9 which can be either 1758, or 1947 in the case of devices with the C4 chip. If unsure please read this thread: [Only registered and activated users can see links. ]. Once you've confirmed the HWID is 1758 you can proceed as below.
    • Extract this RAR file directly to a CLEAN microSD card: [Only registered and activated users can see links. ];
    • Ensure the device is fully OFF, not just in standby;
    • Insert the card and turn on, preferably by connecting to a 5V power source such as the supplied Garmin card charger unless the battery is know to be fully charged (DO NOT use a computer USB port to power it on for this);
    • "Loader"/"Software Loading" or similar words will appear on the screen as the text commands are initiated, wait patiently for the flash to finish indicated by the device booting normally;
    • Remove the card and keep a copy of the new file "154.bin" which will now be present in the root.

    The commands will do this in order (i) Delete any existing gupdate.gcd from the device if present; (ii) Make a copy of ("dump") the content of the NV region 154; (iii) Flash regions 14, 127 & 158 in turn with fresh V8.60 fw data; (iv) Boot the device.

    WARNING: Note that any flashing carries risk and that use of this kit is beyond my control. I've taken every possible care in making it but you assume all risk in its use. Flashing the content to a device with a different HWID may result in it being permanently disabled, i.e. "hard-bricked". Do not modify the supplied kit in any way unless you know exactly what you are doing. I accept no responsibility whatsoever - so do not use it if you don't accept this warning.
    Last edited by Butters; 23rd September 2020 at 01:43 PM.

  5. #124
    Garmin Expert Running programs from SD on nuviRunning programs from SD on nuvi babj615's Avatar
    Join Date
    Sep 2010
    Location
    USA
    Posts
    82
    Rep Power
    27

    Default

    Butters, is there a tutorial or list somewhere of all the commands that can be used this way? Does this work with all Garmin GPSr?

    Thank you!

  6. #125
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    933
    Rep Power
    141

    Default

    @baja615
    Initial post lists all possible commands.

    Modern MTP devices with RWFS write to the card with path "2:/" (in that case "1" is for the hidden RWFS partition of the device), older MSM devices use "1" for the card. The most commonly used commands are "rrgn" to copy a region's contents to card and "xrgn" to write the contents of a BIN file from the card to a region. Less commonly used is "ergn" which permanently erases a region's contents so must be used very carefully. Other commonly used and handy commands are "copy" and "del" to write or delete specific files and "copydir" to dump a directory/folder, eg. "0:/.System", "0:/Garmin" etc. or just "0:/" for the entire file system usually visible in MSM and in that familiar form. The latter can also be done by dumping rgn48 or rgn83 depending on if older or newer device, such a dumped file system BIN file can be opened (with 7-zip or PowerISO for example) to yield individual files and folders either for examination, modification for flashing back, or to decide on its possible deletion.

    A command will only work if it's written in the device's firmware by Garmin. None of the old 'region-only' devices without a visible file system have any commands in their fw, e.g. StreetPilot 2xxx, 3xx. Some modern device fw may lack certain commands, e.g. nuvi 13xx/14xx don't have "if_error" and some Asian versions of common US/EU devices may lack some commands. To check presence open a firmware BIN or RGN file (don't use a GCD as that can be unreliable) and, for example, search for r.r.g.n in a hex reader where "." is a wildcard character. Some regions are protected against copying/writing. Some regions are encrypted ... NV regions 41 or 154 for example usually show only all "FF" content but that's because the hex reader cannot interpret the encrypted content.

    Ldr.bin is simply the boot.bin renamed. Because there's no 'fail-safe' check matching the device's HWID against that of the fw as done with Updater.exe flashing of XXXX01000xxx.RGN (where XXXX is the firmware's HWID), this method can be dangerous if the incorrect Ldr.bin is used in the correctly named HWID folder as the only check is of the folder name, not the actual HWID in the Ldr.bin file itself. Flashing foreign data to the device's virtual region 12 (0x0C) which in-turn writes to physical regions 5 & 43 on next boot attempt. As rgn5 is the bootloader the device may then be permanently hard-bricked which is why it's better that anyone who doesn't fully understand the process does not make these kits or alter any existing kits. A lot of dead units have resulted from early experimentation when we were learning how to safely use these commands.

    Note that after a card has been used correctly, in the HWID folder along with Ldr.bin & update.txt there should now also be created the files named "last_id.bin" and "update.log". Some devices require an empty "update.log" file to be present for any cmd to be successfully initiated (e.g. some early devices like nuvi 2xx i think). The file "last_id.bin" is created after a flash and it must be removed before the card can be used again to flash the same or identical device.

  7. #126
    VIP Master Running programs from SD on nuvi
    Running programs from SD on nuviRunning programs from SD on nuvi
    isg's Avatar
    Join Date
    Jun 2009
    Location
    Europe
    Posts
    198
    Rep Power
    87

    Default

    Quote Originally Posted by Butters View Post
    ..........
    EDIT: Here is the kit for HWID 1758 device V8.80, behind spoiler......
    Butters, short question:
    in zip file, update.txt is written:
    del,0:/.System/gupdate.gcd
    rrgn,154,2:/154.bin
    xrgn,14,2:/14.bin
    xrgn,127,2:127.bin
    xrgn,158,2:158.bin
    In last 2 rows you missed "/" after "2:" or it is correct like that?

  8. #127
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    933
    Rep Power
    141

    Default

    @isg
    No, it's not correct. I've fixed it now and re-uploaded the kit so thanks for checking and advising. I'm unsure how that happened as i copy/pasted the commands from previous file templates i keep. Curiously in this case it probably wouldn't matter that those 2 commands would fail as any problem he was having would be very likely due to corruption in the main system software in region 14 and that would have been overwritten successfully by 14.bin cmd which had correct syntax. Thanks again for that.

 

 

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
  •