Thread: Bmw navigator V hwid 1982 upgrade

Well, i agree with the above post to a point. It's technically against Garmin's EULA to actively promote and physically modify their firmware/software however it's not a problem to just discuss it here. Venturing into actual piracy is of course generally unlawful everywhere and certainly illegally dealing with maps is against our [Only registered and activated users can see links. ] (#9) ..... but talking about simple mods to make a regional device work like another related regional device is allowable.

@TheOldMan
In general, historically Garmin's method of issuing different area-marketing and/or externally branded versions of the same hardware, was to program them at the factory with different HWIDs and consequently with very similar but slightly modified firmware. For example. nuvi 1690 came in several regional versions all with varying HWIDs, but they can be safely cross-flashed to function as another because of matching PCBs. That may well be the case with your China BMW Motorrad Nav V and the secret lies in the device's PCB P/N. In short, if the HWIDs match then full cross-flashing is usually very safe because the P/Ns will always be the same. If the P/Ns match but the HWIDs don't then hybrid firmware cross-flashing usually works and if it does, then full cross-flashing might also safely work ... but if a hybrid one fails then a full flash would be foolhardy as it might be irreversible and prove fatal. A notable exception to that is nuvi 37x0 > 34x0 where hybrid fails but 34x0's ramloader works on 37x0's hardware even though 37x0's ramloader doesn't work with 34x0's fw due to region size differences ... however as a good rule of thumb it's not wise to attempt a full flash when a hybrid using original boot.bin (ramloader) has failed despite both devices having the same PCB P/Ns.

If you want to go further post again and we'll work thru it for you investigating if P/Ns of European and Chinese versions match. Certainly, Japan and China versions both have HWID of 1982 so their P/Ns would match. Therefore, i'd be surprised if the EU P/N is different to the Asian versions despite its HWID of 1541.

Hi, thanks for your answers. In which section should I create a topic to get help and not violate any rules?

No need to create a new topic/thread, there's no rules violation by such discussion and even posting actual minor fw modification files.

So, to make hybrid firmware to test cross-flashing take the boot.bin component of the China V2.40 GCD and combine it with the remainder of the EU fw then use RGN_Tool's override to 1982, finally save it as ONLY 198201000240.rgn (safe-naming) to flash in preboot. Alternatively, you can use the SD method to flash EU BIN files using China boot.bin as Ldr.bin. Be sure to back up nonvol first. If you don't know how to do any of that then post a request and i'll make a flash kit for you.

Be aware that any flashing carries some risk regardless.

Thank you for your advice. Would you be so kind as to create an update file for me via the SD card? I know the risks and I accept them.

It's been a long time since i've handled a Nav V, so as well as the non-volatile memory i do need you to dump all additional regions so i can check the file and folder structure, file variances like Voice, Text etc., and importantly the region size/layout of it. Should reg_48.bin be empty or return an error in the created update.log then check reg_83.bin instead.

Look behind the spoiler:

Spoiler: Click

• Using a CLEAN card, extract this ZIP file directly to it: [Only registered and activated users can see links. ]. Use a card between 8 and 32GB formatted only FAT32. If you only have a larger card like 64GB you must reformat it from exFAT to FAT32 but avoid using a very large card.
• Ensure the device is fully OFF, not just in standby.
• Insert the SD card while it's powered off. Don't do this on battery power only, especially if its battery is weak or low, connect it to a suitable 5V minimum 2A power source (NOT a computer USB port) which will power it on spontaneously.
• The screen will show a green line with "Loader" or similar wording indicating that the regions are being copied. It will take quite a while, be patient and don't disturb it or disconnect its external power.

When it re-boots you'll know that it's finished the dump, so remove the card and upload the populated large BIN file named reg_48.bin (or 83 as said above) containing the file system. Most BIN files will be empty (region unpopulated) or the rrgn command will return an error (region missing), that's normal. I don't need to inspect any other region BIN file at this stage, including the non-vol backup named reg_41.bin but keep a copy of it in a safe place and just let me know its total size please. The compressed file system BIN will be far too large to upload as an attachment on our server here, so use a trusted host site like MegaNZ to upload a ZIP or RAR of reg_48.bin/reg_83.bin. Along with the big file system BIN file, please include the update.log file that's been created in the 1982 folder.

Hello. Unfortunately, the only files that were saved on the card after the restart are last_id.bin and update.log

Here is all files: [Only registered and activated users can see links. ]

Please post the file "update.log" or its text content.

BMW Motorrad Navigator V Software Version 2.40, UID: 3982548487, HWID: 3982548487
------------------------------------------------------------------------------

Spoiler: long text

Code:

Please Login or Register to see the links