Why don't you flash the "last_id.bin"?
There is a command for that in update.txt. Search for unicode "last_id" in your boot.bin and you will find the syntax. I have to go and no time to search. Still add "reboot" after.
All copies of UnitID in region 41 are protected by CRC or some kind of other protection. But at this moment for me it's not important.
First of all I modified UnitID in region 34 and uploaded to device.
Then I modified first instance of UnitID id region 41 and got nothing. Then I modified two instances of UnitID. All the time I don't care about CRC.
After modification of two UnitID copies I got new UnitID and 34xx. Region 41 completely updated.
Looks like software discovered modification in region 41 and cleared NVRAM (region 41).
Know in region 41 is new UnitID with correct (IMHO) CRC or other protection.
First instance of UnitID is at offset AA08 and group of bytes from offset AA00 looks:
36 05 3B C5 87 C4 3A C5 YY YY YY YY C5 3A where YY is an old UnitID
36 05 3B C5 36 C5 3A C5 XX XX XX XX C5 3A where XX is a new UnitID
As you can see some bytes also changed. In different places these CRC bytes are different.
According to this I modified all 24 instances in original region 41 and uploaded to device.
Sadly, but i got the same as before - new UnitID but 34xx.
I'm not sure it's the right way, but maybe we need more investigation.
EDIT:
Probably there are some other protections from modifying. For example some kind of CRC for area of region 41 or even CRC for the whole region 41.
Interesting why NVRAM wasn't cleared when I modified only the one instance of UnitID in region 41.
BTW I have a dump just after first attempt to modify UnitID. Probably there is some important information about updated CRC.
Last edited by voyager56; 25th November 2011 at 11:46 AM.
Why don't you flash the "last_id.bin"?
There is a command for that in update.txt. Search for unicode "last_id" in your boot.bin and you will find the syntax. I have to go and no time to search. Still add "reboot" after.
There is command "write_last_id,[0|1]".
In my opinion this is for writing [1] or disable writing [0] last_id.bin on SD.
If there is last_id.bin on SD and number is the same as unit ID, then Ldr.bin won't run, it assumes that commands have already been executed for this ID.
I'd like to be able to use the GTM-60 Traffic receiver with it's supposed advanced traffic features on a 3790.
Anyone tried it yet ?
Anybody know how to setup EcoRoute if you dont have OBD II?
On nuvi 3790 work normal but after flashing to 34xx now EcoRoute say for OBD II and if you dont have it you cant setup EcoRoute.
How to bypass this?
DeviceConfig_ecoRouteHDReq_Disabled then DeviceConfig_ecoRouteStandard_Enabled
O,i forget this command
Last edited by lolypop000; 27th November 2011 at 11:33 AM.
Hi, all.
After reading this forum, I've flashed my garmin 3790T USA with 3490 3.60 firmware. First flashed with 34xx firmware with modified HWID, then with original 34xx firmware. Both times I did it through updater.exe and .rng
Two questions.
1) Is there are easy way to get logo on loading?
2) Is it possible to delete unnecessary files from internal memory. I'm plaining to full format Garmin in FAT32 and then upload firmware again. Will WebUpdater upload everything necessary?
Thanks.
Bookmarks