Transform device to another type

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

@kopca that information conflicts with what spoon1 said:

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

are you saying you've done this and your maps were expanded to cover a larger area?

Garmin Drive 50 is HWID 2267, so i never had this device and i never tried patch on this device, but it clould be work !
with Garmin drivesmart 50 or Garmindrivesmart 51 i never had same problems , i tested patch and works ... the difference id that drivesmart 50 will became a dezl 580 without wifi and drivesmart will became a real dezl 5809 with also wifi ...so to update maps on drivesmart 50 you will use as normal only garmin express, with drivesmart 51 you can use garmin express or wifi and this will remain the same after modified on dezl 580
i think your garmin drive 50 could be patched ! bu never tested it

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

It's nuvi 2460 HWID 1273 that will convert to dezl 560.

i told on last postes , read please
i wrote compatible models list
and the list is tested by me , others compatibles model i don't know , because i didn't try to modified !
so if yoiu want try it then do it at your own risk, but it's not a joke , you seriusly can broke yuour Garmin for ever.
about dezl 560 modify, i done it many years ago , compatible models could be nüvi 2575 / 2575 ..but i not sure, i no remember well those !

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

It isn't nuvi 2575 > dezl 560, or for that matter any model other than as I already said, and it's only nuvi 2460 (HWID 1273) which can convert to dezl 560 (because their PCBs match). Certainly nuvi 25x5 (HWID 1371) has no PCBs which match dezl 560.

@spoon1
It seems you suspect it's possible i'd write that without actually knowing that it worked by personally testing! I first did it then wrote about it over 8 years ago after finding the two devices had matching hardware. So, yes it works. Both with (i) *'hybrid' firmware comprising original nuvi ramloader and dezl fw_all.bin retaining HWID 1273; and (ii) by flash of complete dezl fw thus changing HWID to 1269. In both cases:

• All truck/RV functions of dezl 560 are enabled;
• Voice Command hardware is present in the nuvi but it isn't supported in the dezl 560 fw so no ASR which 2460's fw does have;
• Region layout is the same for both firmwares;
• There is no need to re-flash region 16 as the logo/splash is the same for both devices.

Both cross-flash methods result in the device identifying as dezl 2460 on start but dezl 560 in the hidden inventory behind battery symbol.

@All readers
Some important general info that isn't always stressed by ppl giving advice about these conversions:

1. Reset/clear nonvol and backup nonvol - In any cross-flashing attempts, it's very important to hard-reset or if available clear non-volatile memory both before and after a flash. It's even more important to back up the nonvol region (dump rgn41 or rgn154 depending on device) before any cross-flash attempt. Problems occurring (even much later) in nonvol data can be resolved by converting back and re-flashing the backup bin file via sd txt command.
2. Check PCB P/Ns - What's absolutely essential is to first check that the PCB P/Ns have a match in the device and the donor firmware however if devices/firmwares already have matching HWIDs the PCB P/Ns always match too. Without matching PCBs there is no chance of a successful complete conversion. Even when PCBs match some original features may not work because they're missing or differently handled in the donor fw or some features of the donor fw won't work because there's no hardware support in the original device. With a close match of PCBs or even with a proper match the device may boot but be missing essential features, i.e. it may have no sound, no touch etc., and at worst with mismatched PCBs it may not even boot at all which results in it being irrecoverable.
3. If a potential conversion has not already been tested - Doing a *'hybrid' conversion first is good insurance. If problems result then a return to original device is easy and much safer. If a hybrid fw works then almost certainly so will a full conversion with HWID change. Sometimes an original ramloader (boot.bin/ldr.bin) may be unsuitable as in the case of nuvi 37x0 > 34x0 as a hybrid, but a complete conversion is successful due to region size/layout change. In that particular example the 37x0's ramloader does work in a hybrid fw only if the bin file is first compressed.

OK VERY PERFECT and excuse me ..i NO suspect about you and i'm glad that you posted it ... i like your post so much and this is can be an archive about patch/modify .
i repeat you, many thanks to you, i'm glad to know you , GREAT