Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26

Hybrid View

  1. #1
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Certainly, but my point was that it indeed boots fully, i.e. it loads firmware then works properly, therefore whatever is holding it up isn't something essential for proper operation or enough to stall or reset the boot. So what's it trying to read/load that's causing the long boot? Not firmware, not maps for sure. Also a corrupt GPI or VPM etc. file should freeze it on loading.

    You can't do an easy 'clear NV' in 2x5W devices, other than with a deep firmware downgrade and if it's got a late board version it's quite possible to brick it with a white screen going beyond a certain version.

  2.    Advertissements


  3. #2
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,877
    Rep Power
    1384

    Default

    There is a field in .rgn that's called "delay." For some .rgn it's set to 0 while others it's not. I have no idea what it's used for. But if I have to guess, it might be a wait time for some area of firmware to get loaded (perhaps unit has slow memory or i/o ports are synching) Who knows, so the question is this. Does one 265WT "behaved" differently from another unit with same hardware AND firmware? Considered the following scenario, the unit was repaired via replacing some bad memory using component that's not up to par with the specs.
    Last edited by osiris4isis; 20th October 2017 at 10:07 PM.
    Do not PM me with questions. That's what a forum is for.

  4. #3
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Perhaps erasing region 41 would fix it, but that will lose its registration and unlock codes. I regard it as 'last resort' and wouldn't do it solely because of slow boot.

  5. #4
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,877
    Rep Power
    1384

    Default

    Better back it up first.
    Do not PM me with questions. That's what a forum is for.

  6. #5
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Lol, thanks. 'Cos maybe San Francisco is greener than he seems .....

  7. #6
    Member + SanFrancisco's Avatar
    Join Date
    Aug 2017
    Location
    CA, USA
    Posts
    36
    Rep Power
    39

    Default

    Unfortunately, erasing rgn 41 did not speed up the boot process. When connected to Garmin Express, its entitlement to Lifetime Mapupdates is still recognised though.

    Apart having to go through screen calibration, entering the locale and waiting for first satellite fix at first boot after erasing rgn 41, I notice no difference in behaviour at all. Do I need to restore the original rgn 41 from backup?

  8. #7
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Quote Originally Posted by SanFrancisco View Post
    Unfortunately, erasing rgn 41 did not speed up the boot process. ........
    See if removing the file mlg_history.db from .System\SQLite helps the boot time. Back it up first of course.

  9. #8
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Did you use RMPrepUSB to reformat after applying Cure3 fw, or only remove some dodgy files once you had Mass Storage Mode back? If there was no format done I'd suggest make a backup of the file system and reformat it then restore the folder and files. You may as well restore region 41 too seeing it didn't alter the boot time.

  10. #9
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,877
    Rep Power
    1384

    Default

    Make sure your backup of 41 was successful and file is not empty. Restoring an empty 41 is bad.
    Do not PM me with questions. That's what a forum is for.

  11. #10
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Not questioning your knowledge there but can you explain how restoring an empty bin file to region 41 is different to erasing with ergn command? The device rewrites most information to 41 on every boot anyway.

 

 

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
  •