My thoughts too. However, I see/found the routine where it unmounts the large Gracenote DB partition from RAMdisk and deletes it before mounting and copying the GN DB disk image (theoretically freeing up some space).
However no such routine seems to exist for the huge Nuance disk image (which I isolated to be the cause of the infamous "MEM_ERR03" error and bails); looks to be an in-place image copy; almost like a literal
`dd if=/fs/images/voice_new.img of=/fs/foo/bar`

I'd be happy to volunteer. Shall I downgrade back to 2.2, document the APIM test results, and then repeat after a 2.3 upgrade?

Thanks for your contributions!

Edit: Another case of the MEM_ERR03 issue with a Mustang owner: http://www.mustang6g.com/forums/show...postcount=3804

 

Yes it is, I'm downloading it now.

 

I can confirm by file size that it is a 1:1 copy of the voice_new.img from the usb to voice.img on the device. So if there is a memory error, it's likely not clearing the space for the copy. let's continue the discussion on a separate thread! https://www.f150forum.com/f118/sync-...7/#post5544751

Same to you for your input! I say hold off on the the up/down as it seems from your mustang forum link that perhaps people who did not go the 3.0 up/down route also get the mem error.

 

I figure I'll finally chime in and try to help on this one...

@Acool you are correct in that I did not go up to v3.0

The wildcard here is that I am missing my gracenotes version. The move from v2.2_16280 to v2.2_17011 made it disappear and the _16280 fix did not work again in _17011. My thoughts were that the failure is happening when it cannot delete the .img that doesn't exist.

 

I can help you if you'd like. Had the same GN issue but got it working. Head over to https://www.f150forum.com/f118/sync-...ussion-399837/ and ping me if you'd like to see what I did to get GN working.

 

Hi all I have been reading about the upgrades available and just downloaded the 2.3 non-nav. file from Acool (thank you for sharing). is there anything I need to do other than putting the USB in and start the truck (2016 F150 XLT)? is there a procedure or anything? definitely, don't want to brick the system on the 3rd day of owning my truck.... thanks!

 

I'll try to figure out the ping.

I'm waiting on hashes to finish.

 

I've done a bunch using official Ford files and never had an issue bricking so I wouldn't be too worried. I've never had any major issues at all other than what you see below:

My method that has always worked starts with a module that has had no power (because it's not been in the car). If you choose this step you can just unplug/reconnect your battery.
I turn on the car and do a "Master Reset."
I turn off the car, open the door, let it go to sleep, give it about 30 seconds after it's gone to sleep.
I turn on the car, let it boot.
I choose no for auto updates.
I insert the USB and wait for it to say UPDATING up top.
I leave the car for ~20 minutes - This will vary depending on your USB stick speed. Mine is a quality/fast drive.
I return to the car and hope for an installation complete message. If it still says updating I leave for a little while longer and check back frequently.

When I did the 1.0 to 2.3 Non-Nav, when I first returned the unit had rebooted as if it had master reset (auto update message again) but no installation complete message. I then turned the car off, removed USB, opened door, sleep cycled it, turned it back on waited for it to boot completely, and then reinserted USB. This time it installed and gave me an installation complete message! Simple as that

 

Thank you. Downloaded and installed.

 

any idea what the upgrade from 2.2 to 2.3 changes or does?