Yes Loly that's correct, some old ones give results with 31 30 35, for others 31 joker 30 joker 35 works. One or the other works for 300_350 blks 476 & 566, 2x0, 2x5 blk 851, 265W, 465, 1xxx --> for instance. But did you try the ones i suggested: 310 blk 566, 6xx blk 569...?
4th July 2013, 01:01 PM
Neil
@kanopus
Not sure what's wrong. The non-MTK 2x5 is no problem:
What hex editor are you using kanopus? This has got me wet, do you know what i'm doing wrong?
4th July 2013, 01:16 PM
kunix
Guys, you shouldn't search for anything in GCD files, as the content inside those files is stored in split state. In particular, every 0xFF00-byte (~64KB) chunk is prepended with a special header. So, unpack fw_all.bin before searching.
4th July 2013, 02:00 PM
Neil
Hi kunix,
I tried the search again using the fw_all.bin for 310 blk 566, 610 blk 596 and 2x5 blk 1074. No joy for the 310 or 610, but on the fw_all.bin of 2x5 the search 31 00 30 00 35 works. I guess searching the .rgn file would be ok too?
4th July 2013, 02:08 PM
kunix
yes, inside rgn files the contents are not split.
4th July 2013, 02:27 PM
Neil
Any clues as to why i'm not getting any search results on the 310 and 610 fw_all.bin files?
4th July 2013, 02:30 PM
kunix
First of all those devices are not unicode for sure. And also maybe the PCB P/N doesn't start with "105-" in this case?
4th July 2013, 03:09 PM
kunix
I've got nuvi 670.
Here is the XML file generated by the unit: [Only registered and activated users can see links. Click Here To Register...]
As you can see, P/Ns start with "006-".