Thread: Convert Nuvi 2460 to Dezl 560 Truckies Nav.

Originally Posted by Neil

..
Method 1:
You can safely convert your 2460 using this method of combining fw. Because it uses the original 2460 boot.bin with original HWID of 1273..

Method 2:
This will load the full dezl fw and your unit will have HWID of 1269. Worked fine for me and flashed back to 2460 ok..

Hello Neil! Great to know about these possibilities. It would be interesting to have some information about the accuracy of gps in the 2 conversion methods. By chance you came to compare them? If we make an analogy with the 3790 converted with full 3490 fw, which resulted in considerable inacuracy, we can assume the same with 2460 to 560? If the precision of the first method is higher, appear to be a strong indicator that the boot drivers are crucial in precision and that the same principle must be valid for the 3790 converted to 3490. Would miss only get operationalize the process with these firwmares ..

Nice idea Angelo! Unfortunately i only have one 2460/560 to play with so i can't do side-by-side tests as i did with 3790>3490 convert and original 3790.
But i'll see what results i can get with rough testing. Stand by, might be a little while as i'll have to convert back and forth several times.

@kunix
Is it also possible to modify the boot.bin of 37x0 so that it will boot 34x0 converted from 37? Angelo has been looking at that as a possible way to overcome the unacceptable accuracy of some of those converted units. Feasible? Sorry, it's a bit ot here.

I'm pretty sure it's feasible, but we need to patch the bootloader (bootloader is not boot.bin). And the question is how many devices would have to be bricked (if bootloader crashes there are no pre-boot) before it finally works. Also I think bootloader has nothing to do with GPS chip initialization. Why does angelozip think the opposite?

UPD:
Well, in theory we could try running the patched bootloader by sending it with a special boot.bin, which could unpack it and execute.
Also I think it should be possible to use the original 37xx bootloader with ported 34xx firmware and as far as I remember Alviora has reported some success here.

Dunno, it's way above my miserable pay-level. He mentioned it in context of boot drivers in this [Only registered and activated users can see links. ] but i don't know the significance or otherwise of it of course.
I'm sure he'll elaborate on it but it will be for you to consider as it's above my head. If this goes too much further, maybe we should move some of these posts to [Only registered and activated users can see links. ] ??

EDIT: All 37>34 specific posts moved, and Posts from #12 to here copied to above thread.

Rough individual tests with original 2460, hybrid fw 2460/560, and with full 560 fw all showed unwavering 3m accuracy in good clear conditions, no tall buildings. Suburban and rural running on same day.

@kunix
Your comment about bootloader for 34/37, could you elaborate more in small words how that works and could it be applicable with 2460/560 at all [i.e do 2640 and 560 have identical bootloader]?

Sorry, i probably wasn't clear what i was asking. But it seems you have divined and answered my questions: (i) You can patch 37 bootloader using a custom boot.bin (if you are willing to move further with that and how to do it, we can continue in the other thread); and (ii) 2460 & 560 bootloaders are different but it's of no consequence as the original works with 560 fw_all.bin anyway.

I converts 2460 to 560, but do not view POI in card, using standart card - CNE_NT_2013.41
How to enable them to see?
[Only registered and activated users can see links. ][Only registered and activated users can see links. ]
First image in 765, next in 560 (ex2460)
Thanks in advance for your reply

Don't think you'd have seen them in 2460 either, and i think that's common across 23x0/37x0 as well.