Thread: Convert 3790/3760/3750 to 3490

Originally Posted by bpb

@voyager56
I just realize the dump region 43 from same unit with different firmware is much different.

Yes, but during modifications I didn't change firmware for different units.

What size is region 76? On my nuvi i get error when trying to read 76.

region 76 has a size of 2,486,272 bytes on my 3750, but does not exist on the 3450.

@kunix
Can you share some hints on this matter (how to recover from 34xx) ?
I know - Спасение утопающих - дело самих утопающих.
But still ...

Finally I solved my problem very simple way - replace my region 41 with the same region dump from other unit. Now I have clone unit with LMT subscription. Funny, isn't.
Now I have unit with duplicated UnitID. This is no problem for me, but I was curious is it possible easy way to change UnitID. I discovered that it's possible. Even in a different ways. But at the moment I don't know how to retain HWID after this change.

sound good ...

I have my original backup before make any trial but once flashback the UnitID is recovered but not the model number.
Anyway in the last_id.bin still FF FF FF FF

Originally Posted by bpb

sound good ...
I have my original backup before make any trial but once flashback the UnitID is recovered but not the model number.
Anyway in the last_id.bin still FF FF FF FF

I never had FFFFFFF in the last_id.bin, I had some "funny" situations, when in 34 region was different UnitID than in region 41. Then last_id.bin had number from 34 region, and each time I reloaded my unit, each time unit executed update.txt. I must remove micro SD to stop execution.

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.

Originally Posted by turboccc

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.

I know, but this is not very important for me. I can live with it.

Originally Posted by turboccc

Why don't you flash the "last_id.bin"?

There is a command for that in update.txt.

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.