Jump to content
AVIC411.com
Sign in to follow this  
JasonH

Modify Base OS

Recommended Posts

For questions just pm EEGeek.

 

The steps to modify your Base F-series AVIC unit's OS are outlined below. I've also created an app to do this for you so you don't have to do it manually. The link the the avic-modder software is here: http://www.mediafire.com/file/zmzymzgzggy/avic-modder_beta.zip

IF YOU USE THIS SOFTWARE, YOU MUST REMOVE AT LEAST A FEW LINES FROM THE STOCK REGISTRY BEFORE IT WILL REGENERATE!!! This is an annoyance of the dumpromx utility. Don't worry though, there are hundreds of lines in there referencing a bunch of modems we don't need driver support for. You can search for the following lines and delete them if you only need to free up a little bit of registry space:

 

 

[HKEY_LOCAL_MACHINE\Drivers\PCCARD\PCMCIA\PNP\MEGAHERTZ-Megahertz_28.8-73E3\Option1\Unimodem]

 

"DeviceType"=dword:00000003

 

"FriendlyName"=mui_sz:"unimodem.dll,#9005"

 

"Tsp"="Unimodem.dll"

 

 

BUT, all of the similar lines before and after this entry are also expendable, unless somehow you plan on attaching a 28.8 modem to the thing! If you need to add a lot to the registry, I'd recommend removing all references to these modems that you'll never use.

 

The following is an explanation of how to modify your OS or registry manually (without the avic-modder software).

 

 

Basic outline for registry updates:

 

1) copy stock WINCEIMG.BIN and .CKS files from unit's flash disk to PC for editing

 

2) use hex editor to split WINCEIMG.BIN into sub files such as toc.bin, wince42.nb0, eboot.nb0, chain.bin, etc.

 

3) use dumpromx to extract files from eboot.nb0

 

4) use fdf2reg perl script to convert the default.fdf file from eboot.nb0 into a reg file

 

5) update reg file in text editor to make additions/changes

 

6) remove unused sections of reg file to make modified version smaller than original

 

7) use reg2fdf perl script to convert modified default.reg file to default.fdf, match old default.fdf file size via '-s' argument

 

7. use dumpromx to update default.fdf file inside eboot.nb0

 

9) use hex editor to paste new eboot.nb0 into a copy of original WINCEIMG.BIN file

 

10) use hex editor to calculate "checksum 32" of new WINCEIMG.BIN file

 

11) use text editor to update WINCEIMG.CKS with new checksum

 

12) copy WINCEIMG.BIN and WINCEIMG.CKS to sd card

 

13) with sd card in unit, enter service mode (directions below soon)

 

14) update WINCE image via service menu, do NOT select the format option

 

15) reboot unit, voila!

 

 

Basic outline for Windows image updates:

 

1) copy stock WINCEIMG.BIN and .CKS files from unit's flash disk to PC for editing

 

2) use hex editor to split WINCEIMG.BIN into sub files such as toc.bin, wince42.nb0, eboot.nb0, chain.bin, etc.

 

4) use dumpromx to extract files from wince42.nb0 if you need original files to play with

 

5) use dumpromx to add/update files in wince42.nb0 (it's ok if wince42.nb0 file size changes)

 

6) use hex editor to paste new wince42.nb0 into a copy of original WINCEIMG.BIN file

 

7) use hex editor to update expected size of wince42.nb0 in the toc.bin section of WINCEIMG.BIN

 

8. use hex editor to calculate "checksum 32" of new WINCEIMG.BIN file

 

9) use text editor to update WINCEIMG.CKS with new checksum

 

10) copy WINCEIMG.BIN and WINCEIMG.CKS to sd card

 

11) with sd card in unit, enter service mode (directions below soon)

 

12) update WINCE image via service menu, do NOT select the format option

 

13) reboot unit, voila!

 

http://avic411.com/index.php?/topic/27524-modify-your-f-series-base-os-and-registry/

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×