Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 6 of 6 FirstFirst ... 456
Results 51 to 53 of 53
  1. #51
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    988
    Rep Power
    170

    Default

    @kopca
    The second method is far more risky if the first method results were unsatisfactory. The second method, used successfully, will completely convert the nuvi 27x7 to dezl by remapping the region layout of the flash chip, loading new boot.bin (it's actually the ramloader) to a virtual region 12 which in turn flashes the physical regions 5 and 43 with dezl boot data. It also alters the HWID of the device. If the result is a bricked device which cannot boot at all then you may not be able to flash the original nuvi boot.bin back and re-convert to 2757. If you don't understand that or don't accept the risk of an unusable device then it's best not to attempt the full conversion imo.

    Clear NV (non-volatile memory) basically resets the device completely so all user-entered data and more is deleted and the device in all practical respects is returned to factory settings. How to do it is [Only registered and activated users can see links. ].

    Using anything other than the safe-naming convention of XXXX01000xxx.RGN (where XXXX is the device's present HWID and xxx is the firmware version) will force the flash in Updater.exe because there is no check made of Updater of the device's HWID before the flash is initiated. Using safe-naming the flash is rejected if the first 4 numerals don't match the device's HWID. Even if one zero is left out of the middle digits RGN's file name (i.e XXXX100xxx instead of XXXX01000xxx) that precaution is skipped. Using "OUT.RGN" is just a common custom to easily and quickly identify an RGN file intended to flash different firmware in a complete conversion attempt. Again, if you don't understand this don't do it.

  2.    Advertissements


  3. #52
    Member
    Join Date
    Oct 2015
    Location
    Brcko
    Posts
    10
    Rep Power
    0

    Default

    I made it. Full conversion is ok so far.
    Only Bluetooth microphone doesn't work but I didn't check in original 2757 too.

    I understand risk in future that new transformed Dezl 2757 might stop eventually...

    1 st method went well too but first loading maps were too long and setting a language ect. (maybe 3-5 minutes). This way I asked for clearing NV, maybe this is reason for delaying and I should restart 2 more times to see result but I didn't.

    2 nd method had the same problem with first loading maps and setting language but after restart everything going well.
    (By the way, I didn't clear NV before and after)

    Sent from my M2007J20CG using Tapatalk

  4. #53
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    988
    Rep Power
    170

    Default

    @kopca
    In my uncertain recollection, your nuvi 2757 doesn't have a BT module nor a microphone so ASR isn't available to it either. A mic could be retrofitted as there would likely be an empty socket for it's connection or at least solder pads on the board. The related senior model 2797, one of which i own, does however have both a BT module and mic. I've previously partly-converted my 2797 to 760 using nuvi boot.bin and retaining original HWID without issues but cleared NV before and after each flash. It's presently properly functioning as a 2797 and has been for some time.

    You should always clear NV before and after loading a non-standard firmware. That's not optional for me, it's essential imo. A byte or two of incompatible data remaining in the non-volatile region may eventually cause an irreversible bricking later. Certainly clearing NV doesn't guarantee against that possibility, but does greatly reduce the risk for sure.

 

 

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
  •