Thread: No pre-boot mode possible on DriveSmart 50 LMT-D 5 ?

Nor should you use it unless as an absolute desperate last resort when nothing else has worked to restore a malfunctioning device. I meant "usual" only in the sense of how we run SD txt commands.

Ok, I am desperate

@kopca
I'm assuming you don't have a backup of its nonvol region 154 made before you did the previous flashings or you'd already have tried restoring it. So it seems you're at the point where you may as well erase 154. Make a copy of it first anyway before you do. Suggested commands:

Code:

Please Login or Register to see the links

The first command will stall the process before erasing if it's unable to dump region 154 successfully in the second one. If you already have a very recent copy of nonvol made after the cross-flashings then just run the last two commands. Good luck. Be sure to read again my comments in Posts 38 & 40 before attempting this. It may just die completely if it has a failing flash chip.

Inside Garmin/Updater/1947 I need to make Ldr.bin and update text?
And Ldr.bin need to make from original firmware?

You must take the boot.bin from the firmware version that's currently loaded to the device, renamed Ldr.bin and make update.txt file as per post #44 for inclusion in "Garmin/Updater/xxxx" where xxxx is appropriate HWID number. But i don't understand why you mention the proposed HWID folder name as "1947". That's for C4 chip version of nuvi 25x9 series. DriveSmart 40/50 is HWID 2267 therefore "Garmin/Updater/2267". You need to be absolutely sure which fw is currently flashed to the device as well as its actual HWID.

Yes, that is correct, Hwid is 2267, (I have an other 25x9 C4 also in this state, so I make confusion)

@georgedobre
I guess you're "george77ro" in the other forum you mentioned. The user kopca who posted before you here has also come from there. I warned users in that external thread about this kind of 'gung ho' flashing and suggested not to do things the way that's being promoted over there: See Post #49 there by "B1ng0" and read carefully below "@All Readers", although it's too late for you to heed that advice now because you've force-flashed the complete dezl 580 firmware to this DS50 device and it now has HWID of 2826 and the ramloader is changed as well. Also preboot is now unattainable because of the lack of touch, leaving using SD commands as the only other means of recovering it.

I need to know some more info before going further:

• Do you have a backup of the nonvol region 154 made before you flashed the dezl fw?
• Did this device have a functioning touchscreen at first after the flash, or was it non-responsive immediately?

If you don't have a backup of rgn154 you should do one now, if only to check that the device can still read from a card. If it can't read from and write to SD card then it's toast.