Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Help with a 760

  1. #1
    Junior Member
    Join Date
    Mar 2016
    Location
    Argentina
    Posts
    6
    Rep Power
    0

    Exclamation Help with a 760

    Hi everyone, i'm trying to unbrick a nüvi 760, but I can't get it to flash the cure firmware.

    With Cure3 I've made the cure firmware out of everyone on the list here:
    MXeLcve

    After making the cure, i put the unit in pre-boot mode
    When it gets detected, open the updater, select the unit and click ok
    Update starts, but depending on wich version I use, gives me an error of memory (4.80 an higher) or finishes ok (anyone lower than 4.80) but still doesn't boot to mass storage mode, just keeps restarting. Shows the garmin logo, powers off, and powers on again. If i run g7towin tells me that software version is 4.70 everytime after updater tells me that finished ok (it should be the one i flash, not always 4.70), thats why i'm guessing that the updater never flashes the unit

    - Tryied in 3 different PC (windows XP and 10)
    - Tryied with 2 different cables
    - Tryied with all the firmwares i could find
    - Tryied with QuickCure file, didn't worked either

    No one worked, any help you can give me it would be great. Thanks in advance!

  2.    Advertissements


  3. #2
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,405
    Rep Power
    1434

    Default

    It seems you've done everything right. First please confirm that the unit has usual US/EU hwid of 0754, it will be shown in G7ToWin without the leading zero as 'ID 754'. Once confirmed please read the rest below but if it's other than 754 post to advise.

    Perhaps the flash is damaged but if you're brave enough there is one more thing you could try, it worked for me with a stubbornly bricked 1350 recently. I'll give more details after we establish that it can accept commands from the SD so firstly you need to check if the unit can still do that. Try to dump both region 41 and region 48. Region 41 is of course the essential 'nonvol' and 48 contains the file system usually visible in Mass Storage Mode. Copy this text command into a new .txt file named Update.txt using NotePad:
    Spoiler:
    rrgn,41,1:/41_backup.bin
    rrgn,48,1:/48_backup.bin
    reboot

    On a CLEAN SD card of minimum 8GB size, create a root folder Garmin. In that create another named Updater and in that one create another named 0754. In that 0754 folder place the Update.txt file along with a copy of boot.bin from the firmware, but name it Ldr.bin [note that V4.70 was withdrawn by Garmin so use V4.60, it may well be that V4.70 is the reason it's bricked]. So you'll have this - SD:\Garmin\Updater\0754 with the two files in there. Ensure the unit is off, if it's not then hold the power slide to the left for up to 30 seconds to force it off. Insert the SD and turn it on, preferably by connecting it to a power source if the battery is weak or not fully charged. If 'Loader' shows on the screen it's copying to the card, let it finish and try to reboot but it won't be able to complete that command and will go back to a bootloop. Force it off and remove the card then check what's on it. Hopefully you will have 41_backup.bin and 48_backup.bin in the root. If not, check the 0754 folder to see if 'update.log' has been created, if so open it in a text reader and report its content. If it doesn't work, try modifying the boot.bin and use this method from Post #38 to run the command by flashing the modded bin file as an RGN in preboot: [Only registered and activated users can see links. ]. Be sure to remove everything else from the 0754 folder except the Update.txt file in that case.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  4. #3
    Junior Member
    Join Date
    Mar 2016
    Location
    Argentina
    Posts
    6
    Rep Power
    0

    Default

    Hi Neal, thank you for your answer.... First of all, HWID is indeed 0754, i forgot to put it on my first message.

    Now, i've followed your instructions with the sd card method and it didn't worked... the unit doesnt show "loader" word, resets right away and the content of the SD card remains untouched, no .bin files, no .log file

    Kunix method seemed to have worked at first but and the end it didn't.
    Extracted the boot.bin from 4.20 firmware, patched it, and made RGN, flashed in preboot with the SD card inserted only with Update.txt in folder Garmin\Updater\0754, and it stayed there for like half hour saying "LOADER" but never rebooted (i assume it should have done it as instructed on the txt), so i turned the unit off and checked the content of the SD card, same as above, no .bin files dumped, no .log file created.

    SD card was on FAT32, but also tryied FAT with same results

  5. #4
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,405
    Rep Power
    1434

    Default

    Unfortunately if neither SD method worked it seems likely the flash is indeed damaged, all the evidence from your previous very capable attempts with Cure fw and now its failure to complete the commands with patched boot.rgn confirms that for me. I'm unsurprised that the usual method with Ldr.bin didn't work as it very often doesn't with bricked devices. However, kunix's patched boot.bin as RGN doesn't rely on firmware initiation at all so it should have allowed the regions to be dumped, provided the flash chip is healthy to my lay understanding. Not 'rebooting' is itself unremarkable [of course it wouldn't 'boot' as such but would instead return to that bootloop state of constant restart attempts had it got to the final command]. The concerning point is that it was stuck on 'Loader' trying to initiate the initial command to dump rgn41 with nothing happening as evidenced by update.log and last_id.bin absence. 7xx series can read/write both FAT16 and FAT32 formatted SD cards.

    Sorry, i'm out of ideas for a soft solution. For a physically damaged flash chip the only solution is its replacement. That's an arduous process requiring unsoldering the chip and resoldering using reballing technique also the new chip requires reprogramming to suit the unit all of which you'd already be aware as i suspect you're not inexperienced in electronics and software and/or IT generally. That is not at all a reasonable solution for fixing such an old device and i would now break it down for parts. Perhaps one of our software experts has another suggestion for a non-invasive fix and if so they'll post. Although i think it's quite unlikely there may be still hope for some type of 'cure'.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  6. #5
    Junior Member
    Join Date
    Mar 2016
    Location
    Argentina
    Posts
    6
    Rep Power
    0

    Default

    Yeah, from the moment it didn't allow to flash the cure firmware I suspected that it will end up as a paperweight due to broken flash... Reballing is never an option for such an old unit, and beeing so cheap to replace with a newer and better one. But I'll keep my eyes open in case that some other idea cames up for testing purposes.

    A curious thing to highlight is when i try to flash any firmare, Updater starts flashing, but the unit goes off and on again really quick. In the cases of normal firmwares then continues normally showing LOADER and SOFTWARE LOADING on screen and Updater says finisihed OK, but not apply any change, but with QuickCure it justs re-enter on pre-boot mode so i'm guessing that's were the problem lyes, It never actually starts flahing, it justs enters again in pre-boot but Updater thinks it finished normally. Could this be possible?

  7. #6
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,405
    Rep Power
    1434

    Default

    Anything is possible with a 'hardware-bricked' unit. QuickCure doesn't rely on using boot.bin and looks for bootloader in the unit's internal memory. If it can't find it then of course it cannot actually do anything. Original fw/Cure3 fw on the other hand is using the boot component of the RGN file to initiate the flashing process and write the individual BIN components' data to the appropriate regions (fw_all.bin to region 14 [hex 0E] for instance), but i don't believe that Updater.exe is 'smart' enough to know if the data has been really flashed at all. It simply knows if it's sending it and will report if it's not or its transmission is interrupted, but doesn't know if the data is then appropriately received and used on the unit itself. That's probably all a bit simplistic and wouldn't satisfy a programmer as a reasonable explanation but as lay person that's my understanding. So, in essence what you've said is correct. QuickCure never actually starts flashing [because it can't find bootloader] and the complete fw RGN although 'sent' by Updater is unused by the unit [so its fw remains as V4.70 regardless of what version is 'flashed'].
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  8. #7
    Junior Member
    Join Date
    Mar 2016
    Location
    Argentina
    Posts
    6
    Rep Power
    0

    Default

    Hi again... I tried Kunix's method againg but with FW Version 4.60, and i got this on Update.log

    nüvi 7 Series Software Version 4.60, UID: HWID:
    ------------------------------------------------------------------------------
    Parsing "rrgn,41,2:/41_backup.bin"
    Error
    Parsing "rrgn,48,2:/48_backup.bin"
    Error
    Parsing "reboot"
    Success


    I read you :P

    Edit: FW version 5.40, same result:

    nüvi 7 Series Software Version 5.40, UID: , HWID:
    ------------------------------------------------------------------------------
    Parsing "rrgn,41,2:/41_backup.bin"
    Error
    Parsing "rrgn,48,2:/48_backup.bin"
    Error
    Parsing "reboot"
    Success



    I think i figured out where the problem lies.... i changed partition from 1 to 2 because i read somewhere that some units take sd card as 2: and not 1:
    After changing it back to 1: again, no luck, frozen on Loader screen and stayed there forever again.


    Well, after various tries it finally worked-ish

    nüvi 7 Series Software Version 5.40, UID:, HWID:
    ------------------------------------------------------------------------------
    Parsing "rrgn,41,1:/41_backup.bin"
    Success
    Parsing "rrgn,48,1:/48_backup.bin"


    And halted there, it was about an hour to get there, a got files

    41_backup.bin of 6.400 KB
    48_backup.bin of 524.038 KB at the moment i turned off the unit a took SD out to check what was on it.

    Im leaving it overnight so it will complete the backup.
    Last edited by TavoTT; 17th March 2016 at 22:50.

  9. #8
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,405
    Rep Power
    1434

    Default

    Yes region 48 will take a long time to backup, probably not overnight though. It will be the full size of the available space for the visible files system, i.e. if your unit has 1GB the 48_backup.bin will be 1GB also. You'll know when it's finished because it'll go back to the bootloop when it tries to execute the 'reboot' command or just freeze. When you get the full 48_backup.bin file open it in PowerISO or similar then you can take a copy to keep as a backup on your PC. If the problem is really that there's something in the visible flash stopping it from booting rather than a hardware problem, writing back 48.bin with just an empty Garmin folder in it might be enough to boot it.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  10. #9
    Junior Member
    Join Date
    Mar 2016
    Location
    Argentina
    Posts
    6
    Rep Power
    0

    Default

    I let it overnight because I was going out office at the time I wrote last message :P

    Now, got today to office and the unit was againt on boot loop. the update.log says

    nüvi 7 Series Software Version 5.40, UID: , HWID:
    ------------------------------------------------------------------------------
    Parsing "rrgn,41,1:/41_backup.bin"
    Success
    Parsing "rrgn,48,1:/48_backup.bin"
    Error
    Parsing "reboot"
    Success

    I don't kwow what happened there, I guess something is wrong with region 48 that didn't let it finish copying. The file was about 947.200 Kb (a little less than 1 gb, 760 has 2 gb of internal memory, so it should be around 1,5-2 gb, give or take some space for the system files and firmware) so i ran it again, same results (i halted it after an hour, 2 gb should copy in no more than 15 minutes, i had a 700 mb file on sd card, i didn´t know copy would be THAT slow)

    So i choose to try to delete the files instead writing the entire region again (plus i was afraid that given the copy was halted and the file is not complete, that could cause the NV size to change and stay in those 950 mb.), that worked fine, i deleted all the map files that oftenly causes the boot loop. After that i tried to flash 4.20 firmware and i went back to boot loop.

    So right now im runing the region 48 backup again and see if it finishes ok, if it does i will open it with PowerISO and delete everything on in, leaving just the Garmin folder, empty, and then try to write it to the unit with xrgn
    Last edited by TavoTT; 18th March 2016 at 21:00.

  11. #10
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,405
    Rep Power
    1434

    Default

    Exactly the way forward from here! It's both good and bad that 48 won't dump properly. It may be an indication of physical damage or there is something very wrong written to it. If it's a severe corruption it might not be possible to even effectively overwrite it and accordingly it may not be possible to remove the corruption with 'xrgn'. If that happens then the only other option that i know will be to attempt to erase region 48 complete with 'ergn'. Doing so successfully should allow it to be seen in Disk Management and then require a reformat with [Only registered and activated users can see links. ]. If neither xrgn or ergn work then it would indicate to me that the flash is damaged rather then just corrupted.

    You appear to know precisely what you're doing .... so good luck Mate.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

 

 
Page 1 of 2 12 LastLast

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