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

@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.

Originally Posted by georgedobre

.............
I backed up rgn154 to check if the device can still read from a card but can't read and write to the SD card.

Note that your device has 2:/ not 1:/ as the path to the card, i.e. it's "rrgn,154,2:/154.bin" to dump nonvol. Also the HWID folder needs to be "2826" and the Ldr.bin taken from dezl 580 firmware. Ensure the card is formatted in FAT32 only and there is no file named "last_id.bin" in the 2826 folder if the card was used for any previous flashing attempt.

In conclusion it is only good for parts.

If you used correct path and syntax etc. as above, there's no other way to reflash it therefore a software solution is impossible so strip it now. It's beyond the skill and tools of a normal user to handle replacement/reprogramming of the flash chip unfortunately.