Thread: Table of nuvis PCB P/N written in FW and possible conversions

This is reason why you can't find PCB number:

Originally Posted by kunix

First of all those devices are not unicode for sure. ......

Yes, i wasn't searching in unicode in those. Search was for 105- [31 30 35 2D], but gets naught for me.

Originally Posted by 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?

Found out why the unicode search works in the fw_all.bin extracted from 2x5 MTK, I had 2 copies of the .gcd file in separate folders. The first copy nuvi2x5_GCDFile-MTK__760.gcd was corrupted. Extracted fw_all.bin worked ok because it was from the good second copy:



nuvi2x5_GCDFile-MTK__760.gcd 2nd copy works fine too:



So one mystery solved [operator error]. Now for the remaining puzzle. I'm sure this will turn out to be my stuff-up too:

Originally Posted by lolypop000

This is reason why you can't find PCB number:

OK, i am just not getting this at all [yet]. Loly, are you saying i should be searching in plain text for XBLKS rather than 105- ? This is what i get for XBLKS, 2 hits only and the second screen [Find Again Down] doesn't look like your 2nd result. My 3rd screen is further attempt for 'Find Again Down' - no result:







Same result in HexCmp with 58 42 4C 4B 53:



Can someone try to replicate my results in XVI32 or HexCmp? Or can you tell me what program you're using in the screenshots shown in your last post Loly?

@All
I seem to have highjacked the thread for what has essentially degenerated into a personal hex tut for me, i didn't intend for that to occur. I really appreciate your patient attempts to help me find my mistakes in this. Apologies for being such a dopey noob ..... Caty, if you want me to spin this off into a Discussions thread let me know, or you just do it. Otherwise i can do some 'cleaning' once the penny drops for me and the light comes on
Probably easier for you guys to train a how to do this. Sorry!

Originally Posted by Neil

Caty, if you want me to spin this off into a Discussions thread let me know, or you just do it. Otherwise i can do some 'cleaning' once the penny drops for me and the light comes on
Probably easier for you guys to train a how to do this. Sorry!

Your questions and our friends' replies are manna from heaven lol , we can learn something

@giomen
Are you talking about this program?:

Code:

Please Login or Register to see the links

Originally Posted by Neil

@giomen
Are you talking about this program?:

Code:

Please Login or Register to see the links

Yes! But I think all viewers or text editors has joker for help to text search (for omission the first h00 in Unicode). It gives a some false result usually but no problem with pair of additional click...

@giomen
These are non-unicode firmwares so I'm searching in plain text. Loly can see XBLKS followed closely by 105-0096800.105-00968.S0.105-XXXXX.XX in his second search imaged in post #30. I get that OK searching the 300-350 fws HWIDS 0476 & 0855, and that's how i found their PCBs in [URL="http://www.gpspower.net/garmin-receivers-firmwares/298003-table-nuvis-pcb-p-n-written-fw-possible-conversions-2.html#post920215"]post #12[URL], by searching for 105- in plain text.

It just beats me why Loly can see the PCBs in 310 hwid 0566 and i can't. What the heck program is that in Post #30????

This is my results searching for XBLKS in nuvi310_360_370_regionfileonly__520.gcd using Total Commander with F3 search, 2 hits again:

Edit>Find>XBLKS




Edit>Find Again



I get the exact same result searching fw_all.bin. I find XBLKS and get no results for 105-. That's the identical garbage results i got with XVI32 & HexCmp. Same result too in nuvi6xx_regionfileonly__480.gcd and it's extracted fw_all.bin, again i can find XBLKS but searching 105- yields nothing.

This is my fw_all.bin extracted from nuvi310_360_370_regionfileonly__520.gcd. [Only registered and activated users can see links. ]. Could someone test it for me please?

@Caty, I don't think you're learning anything from this. Our Queen is being too modest methinks!
I appreciate everyone's patience. [Even G is being nice ]. My head's spinning, i'm going out for some fresh air ......

@kanopus, Thanks. I'll try in HxD when i get back [if i don't hang myself from a tree that is] ......

Caty, i saw you added pics of HexCmp. My results, the first is same as yours, but Find Again is different to your lower result:





I get this garbage in every search. Maybe my 610 fw file is corrupted too?:

XBLKS �!ƒ1B…Rc‡s„‰”
¥‹µÆ�Öç�÷ ‰#›2$F*W6e¿tHŒÁ�Z¯Ó¾lÊåÛ~é÷ø flush_map> flushing %u map pages, lock %u, gen %u to page %u, sver %u ?Ì *s 575- ÿ ÿ ÿ + €  @  @ "  )  -  À   H F ÿ à� ÿ ( ÿ +

Off to find a tree now.....

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

Thanks Caty, but i have no problem with 300 fw [it was me who added the PCB PNs for HWIDs 0476 & 0855 to Post #1 ]. It's 310 fw [HWID 0566] and 610 fw [0596] causing me grief. Your .gcd MD5 hash matches my file and i have the same garbage result as before. I'd already re-downloaded both 310 & 610 fw from Garmin earlier in any case. MD5s match mine too and same search problem. I haven't tried with HxD as recommended by kanopus yet. I'll dl it soon ..... [if i don't smash something first, that is].