2) both :depends on ext (.img .CGD)
Ok. I already implemented everything a week ago. Now, I am just waiting for the right answers that do not seem to come. I probably do not ask correctly.
1- Should I search only for unicode entensions or plain strings as well?
2- Upper or lower cases?
3- Should I do ".ext" searches or only "ext" searches? Or both?
I am sure that whatever I'll do, a few tweaks will be required, but it would be nice to be on the right track from the start.
I downloaded the latest version of RGN Tool - 74. (till now I was using 44) Unfortunately, AVG warns that version 74 is trojan infected. Any ideas how to run version 74?
BTW wanted to ask you how do you calculate (find) the proper RGN Region in .GCD? In .rgn is easy but I can't find the logic in .GCD.
Just tell AVG that this is a false alarm. You can scan the file using VirusTotal.com if you have doubts.
For the GCD, you have to know that section 0800 is region 0C and section BD02 is resion 0E. No info in the GCD itself.
No, I don't have any doubts about RGN Tool. I am just searching for a way to run it. I know that AVG is very paranoic.
That is very interesting about GCD. I thought...hmmm...I suppose you use special headers for each module then? Am I correct? So for the logo you use "10 05" instead of 0x10 which is for the .rgn. Two questions then.
1. What section identifier are you using for a not known section in GCD?
2. Why in the Bluetooth .gcd RGN Tool is choosing region "01"?
Code:Please Login or Register to see the links
1- XX05 so far, XX is the region.
2- Not sure. Because the GCD section is 0104 and normally the first 2 digit are the region number. I know there are exceptions like for the boot and fw_all.
I have not been working on this for some time. You can read the 44+ page thread and maybe it is there. Right now, I am just following the code itself: when I see 0104, I put it in region 01.
I understand. Thanks. I am asking for the Bluetooth region because the other Bluetooth FWs I have seen are on 0xF5.(in .rgn) Here an example:
BTW I successfully flashed bluetooth FW on region 0xF5 on nuvi 1390. 2. If you see the Bluetooth FW in hex after the strings 0xFF FF FF it can be seen the version. For example "36 01" which is 310.Code:Please Login or Register to see the links
Last edited by ddabcd277; 15th July 2011 at 08:23 AM.
Took me a while to find this post. I just remembered it was posted on page 5 of a thread. The difficult part was to remember which thread... LOL:
Originally posted by PouchX
(some regions does not apply for Nuvi series)
03 BM (you have to determine this region size from memory table)
0A Map area
0D ID, Settings and other factory details
0E Main firmware
31 user/factory IMG (you have to determine this region size from memory table)
4D user/factory IMG (GPSmap 478) (you have to determine this region size from memory table)
F5 (in most cases) MTK chipset firmware
F6 (in most cases) SIRF chipset firmware
New Version 0.77 from Today:
* Set the RGN region to 0x10 for special gir file containing 37xx logo.