Thread: Bmw navigator V hwid 1982 upgrade

Originally Posted by zorang

........ Maybe it is because of the firmware?

Almost certainly it's due to China firmware restriction to only 2 languages.

Which level of protection is on that devices? MSV? GSV?

The Asian firmwares have this:

Code:

Please Login or Register to see the links

However, the Western firmware has this (no MSV):

Code:

Please Login or Register to see the links

The solution may be to cross-flash your Asian device with the Western firmware. The China and Japan version devices have the same HWID of 1982. They have 2 possible PCB P/Ns of 105-02052-01 and 105-02052-00 which they also share with the US/EU version which differs only in having HWID 1541. That means that a CN device can be safely fully cross-flashed with JN fw and vice versa because they are the exact same hardware, however it's likely the only change will be in language selections i.e. CH/EN and JN/EN - of course that's only a guess on my part because i haven't looked further.

There'll certainly be far more languages and associated text /keyboard selections available if you cross-flash to the Western firmware. Changing the HWID to 1541 by fully flashing the Western fw might be safe due to matching PCB P/Ns in the Asian and Western firmwares ... however that could result in some unwelcome adverse result, perhaps even a hard-bricking which at worst is irreversible.

What would be much safer and almost certainly reversible, would be to do a hybrid-flashing using the original Asian boot.bin combined with the Western fw_all bin & resources.bin and the HWID of the latter two BINs changed to 1982. Thay way if the device either fails to boot or boots with weird behavior making it unusable it should almost certainly be able to be re-flashed back using original full CH fw. The hybrid-flash is what i suggested to the OP in Post #5 with information of how to make and flash that hybrid fw.

Generally speaking, if a hybrid-flash is completely successful, i.e. the device operates as the converted device exactly like it should, then a full conversion using the complete fw with HWID change is possible and almost certainly safe as well as reversible. Regardless, any firmware flashing carries some risk.

You should always [Only registered and activated users can see links. ] memory region (41) and the visible file system before attempting any cross-flash and also [Only registered and activated users can see links. ] on the device both before and after the flash, especially after. That can prevent unwelcome results due to non-compatible data held in the non-vol region.

@zorang

Spoiler: Click

[Only registered and activated users can see links. ]

It's the latest to which i have access, from 20th July 2020. I don't know if there have indeed been any later updates by the patcher's author, big-bang.

Update on region conversion...
I have done a hybrid-flashing using SD card method. I have used the original hwid 1982 boot.bin (renamed to Ldr.bin) combined with the hwid 1541 (Europe version) fw_all bin (renamed to 0E.bin and copied to region 14) & resources.bin (renamed to 7F.bin and copied to region 127) and the HWID of the latter two BINs changed to 1982.
Everything is working fine, in Device info it says that Software version is 350 which match the European software version but still, only text options I have is English and Chinese although there are other languages in Text folder in the root of navigation.

@Neil
How do you propose I should do the full conversion using the complete Europian FW?

and here is the backup of region 48

Spoiler: Click

[Only registered and activated users can see links. ]

@zorang
It should now be a trouble-free conversion to full US/EU firmware. If you decide to do so, proceed as before using HWID folder still named "1982" but with the unmodified US/EU firmware components as Ldr.bin, 0E.bin & 7F.bin (i.e., still with their original HWID as 1541 and SWV as 350). Provided that flash is successful the device will be fully converted to a Western device with HWID 1451 and its associated region layout. I can't guarantee that you won't have problems however the vast majority of devices which function ok following a hybrid-conversion can be successfully fully converted in turn. I have to say again that any flashing carries risk and that i haven't attempted this conversion myself nor have i even read any reports of others doing it so it's all at your risk if you proceed.

The file "006B082300.bin" in the Garmin folder is used to overcome the 600m Chaina map offset. I don't think leaving it onboard will cause problems navigating in Europe but it's best removed for safety. Please be sure to clear nonvol immediately before and after flashing. Also backup region 41 again after full conversion.

Regarding the limited text selection you've noted: That's due to not having other languages' KBD files in the device's Keyboards folder. Many additional files may be available via GarminExpress following a full conversion because it picks which updates to offer depending on the HWID it reads in the GarminDevice.xml file and that XML also shows which files it already has onboard. Remember to delete the device from GE before connecting it physically to then re-add it after full conversion. As far as GE is concerned, with a hybrid conversion only, your device is still an Asian version because of its HWID regardless that its running US/EU fw. Look behind Spoiler for more info on Keyboards:

Spoiler:

Most recent EU devices would have something like these keyboard styles to select from:

Code:

Please Login or Register to see the links

Your Asian device has only these:

Code:

Please Login or Register to see the links

The current keyboards you have will probably be compatible with the US/EU firmware but you may find they differ slightly from the KBD files of the same name supplied to Western devices. If you have any doubt, remove the Asian ones then reboot to rewrite the XML before updating with GE.

Originally Posted by zorang

...... ended up with device stuck on logo with message above logo "System Software Missing".

It doesn't always happen but certainly it isn't a totally unknown occurrence to get "System Software Missing" on the very first startup after full fw conversion with HWID change. In that case it just needed to be forced completely off by holding the power button down, then when re-booted it would have started normally. Sorry, i do try to cover the most likely outcomes in my posts but giving all possible scenarios in advance can just confuse and frighten many users. There's also some chance of an an error when you made the SD kit for the full conversion - e.g. an incorrect TXT "xrgn" command or wrongly placed BIN file resulting in a mis-match of fw files written. The file "update.log" will disclose all errors there, if any.

As it is, i'm often told my posts tend to be overly wordy ... like this one .

Even when I pulled out the SD card, problem stayed the same.

The card is ignored anyway if left in the device when "last_id.bin" file remains in the HWID folder.

I think that was the case because in update.txt, on SD card, first line was "del,0:/.System/gupdate.gcd" so it probably deleted old FW but for some reason couldnt load the one from the SD card.

No, that's got nothing to do with it. The GUPDATE.GCD file (if present) is only read and initialized by the device if it's deemed appropriate fw and then only used if it's a higher version than is already in the device's fw regions (i.e. 14 [0x0E] & 127 [0x7F]). If so, it will it be extracted and flashed to those regions (a bit like a self-extracting EXE file does on a computer). The DEL command is therefore usually included as the first line of update.txt to remove it just in case it otherwise does somehow get initialized on the next reboot cycle, but if the GCD file's not present then the update.log will show an error for that one command and update.txt will simply continue on with the remaining commands.

Please post the content of the update.log file so we can confirm the above.

... In that moment I thought that I bricked the device and that it will be the same case our colleague @gigidel had with his Motorrad VI, but either way I wanted to try loading FW using WebUpdater.

Again, sorry if that brief concern was due to any info i omitted to give.

Regarding gigidel, i don't recall any posts of his about bricking a Nav VI. Can you point me to that please? It's ok if it's in another forum.

So, loaded EU FW in RGN tool, saved it as .rgn file, used webupdater to load it in pre-boot mode and everything went well.

You simply repeated what was previously done with BIN files via SD card, if that was done properly nothing actually changed there subsequently. The flash in fact works exactly the same whether using SD card method, or by Updater.exe/WebUpdater in preboot. SD just is easier because you don't have to find preboot which can be difficult for some users, particularly with modern devices.

After restart, I selected "Other" region among many other offered (not just US, China and Taiwan as was previously) and I was able to select my language in text option of the device. In Device info and GarminDevice.xml, software version was 350 (correct EU version) and HWID was 1541 (correct EU hwid). Garmin Express recognized the device and offered me an update of text files and also, interestingly, Chinese map that was previously on the device. Maybe because the Device ID was still the same, I dont know...

The device's Unit ID remains the same with this conversion. It's not possible in fact to change it's regional map entitlement which is tied to that UID which is why you got offered CN maps. Although the Garmin servers will use UID to satisfy map entitlement, they use HWID to allocate other files, firmware upgrades and all other software. For all intents and purposes as far as its ongoing interactions with Garmin is concerned your Nav V is now a Western device HWID 1541 but with factory-allocated (OEM) CN mapping.

Nevertheless, after putting the EU maps, I can confirm that everything is working fine.
Couldnt do it without you @Neil.

Great result of course and thanks so much for acknowledging my help. Surprisingly few users do that even when they get a trouble-free smooth outcome, without any hiccups like you had. I'll help me if you follow up with answers to the bits in blue above. Cheers.