Activity Stream
245,732 MEMBERS
1476 ONLINE
GPSurl On YouTube Subscribe to our Newsletter GPSurl On Twitter GPSurl On Facebook GPSurl On Google+
Curing DriveSmart 50 boot loop

Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1.     
    #1

    Question Curing DriveSmart 50 boot loop

    Hi,

    Curing DriveSmart 50 boot loop

    [Login or Register to remove this advertisement]


    I have a DriveSmart 50 LMTHD stuck in boot loop that I'm about to attempt to "Cure". Is firmware on these the same as DriveSmart 40/50 v5.90 available from Garmin download pages? I just like a yes/no from the experts before I attempt a re-flash as I don't see a firmware variation specific to the LMTHD model. Thank You
    roadrage Reviewed by roadrage on . Curing DriveSmart 50 boot loop Hi, I have a DriveSmart 50 LMTHD stuck in boot loop that I'm about to attempt to "Cure". Is firmware on these the same as DriveSmart 40/50 v5.90 available from Garmin download pages? I just like a yes/no from the experts before I attempt a re-flash as I don't see a firmware variation specific to the LMTHD model. Thank You Rating: 5
    Last edited by Garmin_Nuvi; 31st July 2021 at 03:44 AM. Reason: More specific title

  2.   Advertisements

    Curing DriveSmart 50 boot loop
  3.     
    #2
    Garmin Mod
    Supporter
    Garmin_Nuvi's Avatar
    Curing DriveSmart 50 boot loop
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    Yes only if your HWID is 2267

    https://download.garmin.com/software/DriveandDriveSmart40_50_590.gcd

    Last edited by Garmin_Nuvi; 23rd July 2021 at 09:24 AM.
    Unless you are a "New" member, having used the Thanks button regularly is the quickest way to get help.

  4. The Following 2 Users Say Thank You to Garmin_Nuvi For This Useful Post:
    [ Click To Expand ]

    gajevi53 (16th October 2023), roadrage (23rd July 2021)

  5.     
    #3
    After flashing Cure RGN, I am now able to access the device and it is 2267 however simply re-flashing original firmware does not eliminate the boot loop.

    Generally, I would just format the unit with RMPrepUSB prior to loading the original fw back. In this case and with Cure fw loaded, PC detects the device and I can access it however it is not being assigned a drive letter (not seen as a disk in Disk Manager) so RMPrepUSB does not see it as writable drive either.

    Is there a way to force it into pure mass storage mode without being physically able to do it from the device itself?

  6.     
    #4
    I appreciate the offer but I'm afraid SD card method may not work as I've already tried Firefoxe's SD for the 2267 from UFP thread.

  7.     
    #5
    spoon1's Avatar
    STRANGE, because sd will works on every device ...forever if it's made well ...but you must remove the file gupdate into your garmin ...look inside .system folder if there if the file GUPDATE, then remove it ...and then you can do software patch using micro sd card !

  8.     
    #6
    For me to access the .System directory, device has to be into Mass Storage mode I believe? Since it does not boot pass Garmin logo, I cannot switch off default MTP mode hence .System directory is not accessible. If there is another way or anything else I should try, I'd love to know. Thank You.

    Also, a bit of an update: after flashing original firmware for the third time with Cure, device now boots up to Loading Maps screen then reboots. It used to just boot to Garmin logo, go dimmer and reboot then. So perhaps a bit of a progress
    Last edited by roadrage; 27th July 2021 at 09:38 AM.

  9.     
    #7
    spoon1's Avatar
    @ roadrage ... try with Garmin Cure ! , try with garmin web updater to reflash software ...
    @ ion_vasile ... OK but to do the sd FLASH for you i need to know your garmindevice.xml .. so open it and see if it is 2826 OR WHICH OTHER NUMBER ?
    i mean look at this string on your Garmin (garmindevice.xml file)


    -<Model>

    <PartNumber>006-B2826-00</PartNumber>
    <SoftwareVersion>380</SoftwareVersion>
    <Description>dēzl 580</Description>


    Moderator Note
    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.
    confirmed the HWID is 2267 in Post #3
    Last edited by Garmin_Nuvi; 29th July 2021 at 09:32 AM. Reason: added note

  10.     
    #8
    Ok, so I think I'm back in business. Since it now halted at Loading Maps screen rather than on first Garmin logo, I flashed Cure RGN back in it then attempted an update with Garmin Express. I was lucky enough that maps on the device were older so Express installed current version, ultimately fixing what may have been wrong with mapset on the device. I then flashed original firmware and it booted right up. I appreciate the help and suggestions. Thank you.

  11. The Following 2 Users Say Thank You to roadrage For This Useful Post:
    [ Click To Expand ]

    Garmin_Nuvi (29th July 2021), spoon1 (29th July 2021)

  12.     
    #9
    hello I have the same problem with my drivesmart 50 probe the sd and did not work has loaded a partNumber 2826 pro should carry partNumber 2267 softwareVersion 5.90 can be flashed from an sd thanks

  13.     
    #10
    B1ng0's Avatar
    @gajevi41
    Probably you've had no response due to lack of clarity of the situation. It seems to me that this might be the case:
    You used an SD kit which had dezl 580's ramloader (Ldr.bin) of HWID 2825 rather than DS50's HWID 2267. Is that much correct?

    If so, what was the result? For example:
    Does the device turn on at all?
    If it does turn on, how far into the boot process does it get?
    The above info is essential to give and also supply any other info which might be relevant, such as does it freeze on splash screen ( Garmin logo); does it bootloop or does it turn off after showing the splash screen.

    Additionally, please supply the following:
    A copy of the SD kit used, with all folders and files including Update.log (i.e. after flashing)
    Screenshots or video of how the device is now performing (if it isn't completely dead)
    Complete details of corrective action, if any, that you've attempted since the flashing.

  14. The Following 1 Users Say Thank You to B1ng0 For This Useful Post:
    [ Click To Expand ]

    gajevi41 (22nd October 2023)

Page 1 of 2 12 LastLast

  Suggested Articles:

Curing DriveSmart 50 boot loop

Tags for this Thread

Amount:

Enter a message for the receiver:
BE SOCIAL
Curing DriveSmart 50 boot loop Curing DriveSmart 50 boot loop Curing DriveSmart 50 boot loop GPSurl On Facebook Curing DriveSmart 50 boot loop