Convert dezl 770 to any other model

[timstring]

Is there a way to convert a dezl 770 to a Camper 770 or any Nuvi model?

[Butters]

It is only possible if the PCB P/Ns of the two devices match. You can check the PCB on the device itself or in the firmware. Read this thread (not just initial post) to understand how to do that: [Only registered and activated users can see links. ]. Search for "1.0.5.-." in text (31 00 30 00 35 00 2D 00 in hex) using either either the complete fw only as an RGN file or search in fw_all.bin, don't search a GCD firmware file as that might not work due to inclusion of special headers in GCDs. Matching PCB P/Ns doesn't guarantee a smooth conversion however, there are other factors also at play. On the other hand, if the PCB P/Ns don't match a conversion is not possible at all.

[Bushwalker8]

If you have it in your hands the easiest way is to go to the volume screen, hold the top rhs, go to developer settings then PCB info.

I'm guessing you will find it's 105-02500-00, and the hardware ID appears to be 2002 - but check this before doing anything radical!

It's definitely different to the RV770, mine is PCB 105-03101-00 and hardware ID 2684. This is same as the localised RV775 here in Australia (essentially same PCB with more memory for the included onboard maps.)

I just had a quick look at some firmware for the following devices and at first pass all appear to be different hardware to yours; RV660, Nuvi 67/68, 25x9, 26x9, 27x9, 34xx, 35x7/35x8

You can sniff out more firmware samples here: [Only registered and activated users can see links. ]

Happy hunting

[wlodekwbw]

Dezl 770 PCB 105-02500-00
Nuvi 27x9 PCB 105-02500-00

Camper 770 PCB = DriveSmart 61
Camper 660 PCB = Nuvi 26x9

[Bushwalker8]

Be careful
Dezl 770 Hardware ID 2002
Nuvi 27x9 Hardware ID 1932

[wlodekwbw]

Hardware ID will always be different, it is important that the motherboard (PCB) is the same.

[Butters]

@wlodekwbw
I'd think that Bushwalker8 simply means for the OP to be careful with cross-flashing because of the differing HWIDs. For any degree of success, matching PCBs is of course essential. You'd be aware, as he is, that a PCB match alone doesn't for certain guarantee a safe successful cross-flash particularly if there's region layout/size differences.
@timstring
Safest way to do it initially is to use the original device's boot.bin combined with the donor firmware's other components and retain the original device's HWID however that sometimes doesn't work because of region differences. eg: converting 37x0>34x0 needs either a full flash or for a hybrid flash one of the fw's BIN files needed to be compressed (fw_all.bin or boot.bin, can't recall). Likely a hybrid flash retaining HWID will work and even if it doesn't it's easy to revert back in most cases.

[wlodekwbw]

@Butters
And here you are right, everything we do we do at our own risk, it doesn't hurt .
I have carried out many full conversions and always successfully but I am brave. This does not mean that there must always be success. YOU NEED TO HAVE THIS AWARENESS!

[boll]

There are some models that have the same firmware and HWID, but different functionality.
The best examples I can give is the Drive Smart 60 and Drive Track 70. How can a Drive Smart be converted to a Drive Track?

[Butters]

@boll
Some devices using the same firmware have hardware differences. An old example, nuvi 13/1450 and 14/1390 where the latter has a bluetooth module, that's of course missing on the former albeit same HWID. Also in the 1xxx series, some devices had different features enabled via the splash, contained in region 16. Flashing a senior model logo to a junior model can enable JCV for instance, even in a base 1300. Indeed, as a run-out of the model, 1300 was released with a logo flashed which enabled LA & JCV in some markets. There were other earlier instances too, EU nuvi 710 flashed with AU 7xx logo enable TTS on that device. Second generation HWID 0827 nuvi 2xx/W (2009) lacked traffic but when flashed with nuvi 2x5/W logo the traffic feature was enabled. Maybe Garmin is still using region 16 to enable/disable features in Drive series?