My understanding is that too many BMW Navigator VIs will have screen touch ghosting after a long time.
Garmin has replaced a new hardware module, so there is a new HWID and V10.00 version.
1. So when you tried to dump the regions you used HWID 2842's ldr.bin in folder named 4044? That 2842 ramloader is from Nav VI Japan fw.
=> Yes, I have another Nav Vi I borrowed from a friend, it's HWID is 2842, I got the GCD file from Garmin Express with the 2842.
2. You didn't get successful dumps?
=>Yes, I got 5.bin and 154.bin, but I'm not sure if I got it with 2842 or 4044 HWID and update.log
From the update.log file, we can see that there are two successful messages, one is HWID 3375696611 (4044), and the second is HWID 3952386425 (2842).
It can be seen that although 4044 uses the wrong Ldr.bin, Nv data can still be obtained.
Contents of update.log:
BMW Motorrad Navigator VI Software Version 2.60, UID: 3375696611, HWID: 3375696611
------------------------------------------------------------------------------
Parsing "rrgn,5,1:/5.bin"
Success
Parsing "rrgn,154,1:/154.bin"
Success
Parsing "reboot"
BMW Motorrad Navigator VI Software Version 2.60, UID: 3952386425, HWID: 3952386425
------------------------------------------------------------------------------
Parsing "rrgn,5,1:/5.bin"
Success
Parsing "rrgn,154,1:/154.bin"
Success
Parsing "reboot"
3. Also, why did you want to dump the bootloader rgn5? It's usually protected against writing/flashing in most devices anyway.
=>I just want to dump from a learning example.
I don't yet understand what any rgn block does.
4. Do you have the full firmware for 2842 JN?
=>Yes, I have the full 2842 GCD file from Garmin Express and extracted Boot.bin from this GCD file via Rgn_Tool.
Right now I'm trying every possible way to find the full firmware file for the HWID 4044,
get the correct 4044 (Boot.bon/Ldr.bin) and maybe simply reboot the machine normally
Bookmarks