Thread: Drivesmart 51 stuck on Logo Screen

In the "Sticky" threads at the head of this Section are these 2: [Only registered and activated users can see links. ] and [Only registered and activated users can see links. ]. Try QuickCure first as it's universal and doesn't involve original firmware but if it doesn't work then make specific Cure3 RGN fw from the GCD. The is also an "unbricking" guide which refers to nuvi devices but the procedure is the same: [Only registered and activated users can see links. ].

Post again if you need more assistance after reading the above threads and trying yourself. Most likely it just has a corrupt file (like an IMG, GPI or VPM etc.) in its internal memory which cannot be loaded. If so, it should have defaulted to preboot mode and will recognize Updater.exe and G7ToWin. A failing flash chip can also cause an interrupted boot but that's less common and the device usually doesn't have preboot in that case.

No GCD file can be flashed from a media card when the boot sequence stalls on the logo because the device doesn't check for a card's presence until further into the boot process. Similarly, it can't be seen by File Explorer in MSM by a PC for that same reason. Therefore, any flashing of a device that's been "soft-bricked" by a bad essential file can only be done using an RGN via Updater.exe in preboot.

The Drive series i recall as entering preboot by holding a different spot on the screen. While most automotive devices use the top LH corner, some use the lower LH corner and even some others you need to hold on or over the "G", or on the "RM" in "GARMIN" when it appears. I'd try those 3 alternate methods in that order but have Updater.exe GUI open with the radio button for "USB Device" selected and be ready to click "OK" button, or your PC's Enter key, very quickly when the device's details appear in the GUI. You might only have a very short time of opportunity to start the flash.

Good result and many thanks for reporting back the correct screen hold position.

Just for completeness, does QuickCure work in your DriveSmart or did you need to make Cure3 fw from original?

Neil
I directly applied the dezl 580 firmware using Updater.

For your information, in this case as well the device did not change its name. It remained “drivesmart51”.

There's been no consistency in name-change experienced when various devices are cross-flashed, some don't change model name at all as you've found there. Some will partially change name, an example is nuvi 2450 to delz 560 which identifies as the composite "dezl 2460" on the splash screen after conversion. Whereas others do show correctly the new device naming, such as: nuvi 37xx to nuvi 34xx; nuvi 2x5W to nuvi 465; and (i think, from memory) nuvi 5x0 to zumo 2x0 to name a few. I can't explain why that happens differently.

Would you mind clarifying this for me please?:

Originally Posted by Neil

....... does QuickCure work in your DriveSmart or did you need to make Cure3 fw from original?

Originally Posted by toninolapo

Hi Neil,
I didn’t use either GarminCure or QuickCure, but once I put the device into preboot mode
I directly installed the dezl 580 firmware using Updater, after saving it as an RGN file.

Oh ok. I assumed you'd needed to use cure because you stated in Post #3 that it froze after the Garmin logo screen displayed.

So what had likely caused that freezing do you think? It clearly wasn't 'bricked' in the usual way by a corrupt file onboard if simply loading the full dezl fw recovered it. Had you tried using hybrid fw previously with the DriveSmart boot.bin combined with remainder of dezl fw?