Thread: Windows cannot detect internal and SD memory for Zumo 390LM

I have some more questions:
1) Does RGN Tool takes information from RGN original GCD file from latest fw from Garmin site?
2) Considering my question (#1) is correct I got two options as save boot.bin and also fw_all.bin from RGN Tool. I assumed to use only boot.bin renamed to LDR.bin.
3) At the field "RGN Region" I can see fixed values as "OC "for boot.bin and "0E" for fw_all.bin and nothing related to regions 41 and 154 as I saw in the post you mentioned above.
4) How does the complete ERGN text command set (rrgn,<rgn #>,<output path>) will be written on update.txt file? (rrgn,41,1:/41.bin) ... considering using boot.bin as LDR and also 1 as my Zumo has SD as #1
5) Using only boot.bin and all set as shown above we got the "green progress bar" during the boot saving files to SD card.


6) Using boot.bin as LDR and using SD as #2 and using 41 I got the following update.log file:
===============================================
zumo xx0 Software Version 4.20, UID: xxxxxxxxx, HWID: yyyyyyy
------------------------------------------------------------------------------
Parsing "rrgn,41,1:/41.bin"
Success
Parsing "reboot"
===============================================

41.bin was generated .... I assume that is the Backup of Nonvol and my concern is about 41 or 154 regions that can invalidate 41.bin as a good backup


7) What kind of features can be lost with completely nonvol clean up?

8) I have already decided to Erase NonVol and it was done... see the result:
==============================================
Parsing "ergn,41"
Success
Parsing "reboot"
==============================================

The device still not recognized by the Windows up to now!