Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 46
  1. #21
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,038
    Rep Power
    601

    Default

    Quote Originally Posted by smokefree View Post
    The screen of the unit then shows the text "LOADER" for about 10 more seconds and then repetitively briefly shows "SYSTEM SOFTWARE MISSING" until I disconnect the unit from the PC.
    So the 827's boot.bin works fine. This is some good news actually. If nothing else helps, we can use 827's boot.bin, I think.
    Quote Originally Posted by smokefree View Post
    I get the message "No updates are available for your product":
    I guess you renamed RGN taken from 082701000620-org.rar from 082701000620.bin to 097201000620.rgn before flashing.
    Please try again without renaming, and check if it shows "LOADER" after flashing.
    Renaming was needed only for the healthy device.

  2.    Advertissements


  3. #22
    Navigation software expert

    lolypop000's Avatar
    Join Date
    May 2010
    Location
    EU
    Posts
    2,925
    Rep Power
    849

    Default

    Quote Originally Posted by smokefree View Post
    loly, just to get the instructions in step 1 right: do I just add the microSD in the GPS but not switch it on until pre-boot in step 2?
    Or do I flash the software from the microSD first and then proceed with step 2?
    1.) Turn nuvi off
    2.) Add SD in nuvi
    3.) Turn nuvi on and flash in pre boot

    Here you have all that you need:

    Spoiler: This extract on SD
    http://www20.zippyshare.com/v/37395781/file.html



    Spoiler: With this flash in pre boot
    http://www24.zippyshare.com/v/11561638/file.html



    This pack is created in this way that when you flash in preboot with rgn this will start command from SD and if all go OK you will have 14xx boot.bin on your unit.

    p.s.

    do I just add the microSD in the GPS but not switch it on until pre-boot in step 2?
    Yes, correct
    Last edited by lolypop000; 9th February 2014 at 23:20.
    If you wish, you can [Only registered and activated users can see links. ]

  4. #23
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,316
    Rep Power
    717

    Default

    Quote Originally Posted by kunix View Post
    I guess you renamed RGN taken from 082701000620-org.rar from 082701000620.bin to 097201000620.rgn before flashing.
    Please try again without renaming, and check if it shows "LOADER" after flashing.
    Renaming was needed only for the healthy device.
    Tried again. Here's the sequence of computer screens observed:

    c58k

    I clicked "Yes" and then for about half a second I saw "LOADER LOADING..." on the GPS screen.

    c3k4

    After this computer screen, it took about 10 seconds for the next computer screen to appear:

    lbox

    From the moment LOADER LOADING... had disappeared from the unit's screen, the screen stayed on, but nothing showed up anymore.

    Will now continue with loly's suggestion in post #22.

  5. #24
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,316
    Rep Power
    717

    Default

    Followed loly's instructions from post #22:
    1. I unpacked the first download and placed the Garmin folder with all contents in the root of an empty microSD.
    2. I made sure the bricked unit was switched off and placed the microSD in the unit.
    3. I unpacked the second download and dragged & dropped it onto the Updater.exe file that came with the download.
    4. In the Updater.exe window, I selected "USB Device".
    5. Brought the bricked unit into pre-boot mode and then clicked "OK" in the Updater.exe window.

    From there on the sequence of events was identical to what I described in post #23 (the post above this one). Therefore the same screen shots:

    c58k

    I clicked "Yes" and then for about half a second I saw "LOADER LOADING..." on the GPS screen.

    c3k4

    After this computer screen, it took about 10 seconds for the next computer screen to appear:

    lbox

    From the moment LOADER LOADING... had disappeared from the unit's screen, the screen stayed on faintly, but nothing showed up anymore.
    There's no 41.bin file in the root of the microSD. Also there is no confirmation of successful flashing in either update.log file on the microSD.

    Asked before, but can you please confirm if the presence of the (empty) update.log files could cause the flash from microSD to be ignored? I thought there should be no update.log file on the microSD before flashing, as it will be created automatically as part of the flash.


    Edit:
    Small detail, but maybe relevant and important to know: Besides the notification in Updater.exe, I also hear by the "dong-ding" from the PC speakers that pre-boot mode is active. When I set the flash in motion by clicking "OK" in the Updater.exe window, almost immediately I hear "ding-dong", signalling the termination of pre-boot mode. Yet, my finger is still on the top left hand corner of the screen. Also, the progress bar in the "Updating Software In Progress" window is not gradual, but jumps from 0 to 100% immediately. Around the same time I hear the "ding-dong", signalling the termination of pre-boot mode. Still, about 10 seconds later, the window confirming the successful update shows up...
    Last edited by smokefree; 10th February 2014 at 00:06.

  6. #25
    Navigation software expert

    lolypop000's Avatar
    Join Date
    May 2010
    Location
    EU
    Posts
    2,925
    Rep Power
    849

    Default

    updater.log is no problem, you can delete it and try again but will be the same.
    I don't know why sd command is not executed.

    Try add this on SD:

    Spoiler:
    http://www41.zippyshare.com/v/83487263/file.html


    and flash with rgn from post #22
    If you wish, you can [Only registered and activated users can see links. ]

  7. #26
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,316
    Rep Power
    717

    Default

    Will continue tomorrow. It's after midnight and I have to get up at 4.00 AM.

    Thanks everyone for all the help so far. To be continued...

  8. #27
    Navigation software expert

    lolypop000's Avatar
    Join Date
    May 2010
    Location
    EU
    Posts
    2,925
    Rep Power
    849

    Default

    Here is another pack for try:

    Spoiler: Extract on SD
    http://www67.zippyshare.com/v/55431529/file.html



    Spoiler: With this flash in pre boot
    http://www39.zippyshare.com/v/81348758/file.html


    After procedure is over and if you stuck on black screen, then flash with this original 14xx FW in pre boot


    Spoiler:
    http://www5.zippyshare.com/v/6949524/file.html
    If you wish, you can [Only registered and activated users can see links. ]

  9. #28
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,038
    Rep Power
    601

    Default

    Now we know that 972's boot.bin always crashes, even if we [Only registered and activated users can see links. ] it to load update.txt (tests in posts #22 and #16 have failed).

    But we do know that 827's boot.bin doesn't crash (test in post #16).
    So we could use 827's boot.bin to execute update.txt with something like this:
    Code:
    Please Login or Register to see the links
    Where 1:/5.bin and 1:/43.bin are the 972's bootloader and the 972's x-loader respectively.
    We can extract them from boot.bin or dump them from a healthy device (I prefer the latter way).
    But the problem is, flashing regions 5 and 43 is disabled in the xrgn command handler. So we have to patch boot.bin to remove this limitation.

    smokefree, please dump regions 5 and 43 from a healthy 14xx using [Only registered and activated users can see links. ] and post them here.
    It's a normal region dump procedure, not dangerous if you use the right ldr.bin

    lolypop000, I predict that "xrgn,12,1:/Garmin/12.bin" won't work. Guess why? It's because you're requesting to rewrite boot.bin in the RAM, while it's being executed. It will fail for sure.
    Last edited by kunix; 10th February 2014 at 08:42.

  10. #29
    Navigation software expert

    lolypop000's Avatar
    Join Date
    May 2010
    Location
    EU
    Posts
    2,925
    Rep Power
    849

    Default

    In post #27 i add in rgn 827 boot and patch to execute update.txt

    You ar right i forget about 12.bin, It was late and i was sleepy.
    If you wish, you can [Only registered and activated users can see links. ]

  11. #30
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,316
    Rep Power
    717

    Default

    Based on information in post #28 and #29, I did not perform the instructions from post #25 and #27. If at a later stage you'd like me to try anyway, let me know.

    Quote Originally Posted by kunix View Post
    smokefree, please dump regions 5 and 43 from a healthy 14xx using [Only registered and activated users can see links. ] and post them here.
    It's a normal region dump procedure, not dangerous if you use the right ldr.bin
    Here they are, taken from the healthy 1490T: [Only registered and activated users can see links. ]
    Awaiting further instructions.

 

 
Page 3 of 5 FirstFirst 12345 LastLast

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
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.