Re
That’s a very brief statement, with no explanation, What do you mean by “you need to fix this”
Fix what exactly? Do you have a more detailed explanation for what you have written here?
If you read the threads you’ll see that a full partition there is the result of the 3.4.22251 bug and it needs to be cleared to avoid upgrade and numerous other issues.
You can create just an RW data partition cleanup USB with Cyanlabs or hand build one that has just in the autoinstall once you populate the files properly.
[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
that is a good observation, as a matter of fact I have done the RW wipe disk a few times so far.
I do the RW data wipe and then do a log file disk to check and verify the wipe. Then I go back to trying to get something to install…
by creating an install disk…im still stuck…
What settings do you have on synupdater?
Do this:
- Master Rest the unit if you can. If you cannot, go into FORScan and find the Module Reset menus under the Tools icon. Reset the APIM 2 times in a row. Let it fully reboot each time.
- Run the RWData cleaner.
- Run the Interrogator Utility and see if you have more memory now in the RWData partition.
Soft Reset
There is a reset procedure for Sync of performing 2 reboots in a row, one right after the other, that can clear errors and free memory being used by temporary files. This is effective for the BGMAP and other errors also. Using the Soft Reset option will free up some storage/memory for the short term in perform a reformat and/or upgrades/downgrades. This procedure does not normally clear any user settings, stored phones, nav destinations, etc.
- If possible, perform a Master Reset under Settings > General > Reset. This may not be possible, and the unit will hang. If the unit hangs while trying to perform a Master Reset, try performing a key cycle first to see if that helps completing the Master Reset. Continue with the steps below.
- Once the unit has fully rebooted, perform two soft reboots in a row.
- Hold the power button and next track (seek >) button on the center console interface at the same time for about 5 seconds or until the screen goes black. The APIM will reboot, and the system will restart.
- Once the first soft reboot is done, perform the second soft reboot as above.
- Once the system is back up after the second soft reboot, try to run the update, etc.
There is another method of this using FORScan to reset the APIM a couple of times. This is effectively the same as above. Be aware that this procedure will not completely clear the /fs/rwdata logs but will usually make enough free space to be able to run the reformat tool or upgrades. The upgrade (or downgrade) process will not clear the /fs/rwdata partition. It is recommended that you perform a reformat or run the scripting to clear the left-over logs and data from the rwdata partition.
Thank you for your response,
Please clarify your question with more details and information.
I don’t understand it the way it’s worded,
Regards,
Thank you for this response,
I just dropped the truck off for it’s quarterly service at the dealership.
When I get it back in my driveway I’m going to go over this list you provided.
Thank you so much,
You clearly have not read any of the information on the updater software, the documentation is here in the forum, go to the settings button in the updater and tick all boxes as your specific system demands for the procedure you’re trying to achieve…
My take on this if you go back to day one of the thread is that he has either:
- a bad APIM
- loaded in a firmware which isn’t compatible or he’s mixed pieces of various firmware iterations
- an APIM somebody refurbed at the board level
After a while this comes down to which is cheaper, picking up another APIM or continuing to throw time at it.
- If possible, perform a Master Reset under Settings > General > Reset. This may not be possible, and the unit will hang. If the unit hangs while trying to perform a Master Reset, try performing a key cycle first to see if that helps completing the Master Reset. Continue with the steps below.
The master reset function is what put me into this situation, everything was at least functional before I did that.
There is another method of this using FORScan to reset the APIM a couple of times. This is effectively the same as above. Be aware that this procedure will not completely clear the /fs/rwdata logs but will usually make enough free space to be able to run the reformat tool or upgrades. The upgrade (or downgrade) process will not clear the /fs/rwdata partition. It is recommended that you perform a reformat or run the scripting to clear the left-over logs and data from the rwdata partition.
I have done many many soft resets with the power and forward track button. I have pulled the battery cable for 1 hour, I have used Forscan for APIM reboots several times.
I am finding now that getting the rw data to clear is not as fluid as before. Now that folder is full and the rw data wipe tool doesn’t seem to work.
I can get a successful interrogator file to review, so I am wondering why the rw data wipe tool will not work.
I would have no problem doing a reformat considering it seems I have nothing to lose at this point. But if the rw data folder needs to be empty before I try a forced reformat, then I am hitting a brick wall.
Thanks,
My take on this if you go back to day one of the thread is that he has either:
- a bad APIM (seems like this is the case but I am not 100% sure yet)
- loaded in a firmware which isn’t compatible or he’s mixed pieces of various firmware iterations—(I have only updated the sync system from the head unit OTA wirelessly while at home, using my wifi system in the driveway) they have all been OEM updates allowed/provided by the head unit.
- an APIM somebody refurbed at the board level (This is the OEM factory original head unit and components, the same since I purchased it in 2019 with 5 miles on the odometer)
After a while this comes down to which is cheaper, picking up another APIM or continuing to throw time at it. (I am ending up with those thoughts too)
are there aftermarket head units that will fully work with Sync?
will I lose the cell phone based ford app remote start function, with an aftermarket head unit?
is there an upgrade I should consider in your opinion, If I am going to throw money at it to get my radio back, maybe I should look at other options?
thanks,
First the ForScan reboot/reset is not the same as a master reset.
A master reset clears all user settings and puts the unit back to factory defaults, it clears paired phones, sound settings, NAV settings while the ForScan reset is the equivalent of cycling power on the APIM.
Sync is built into the APIM OS, using a 3rd party instead of it means you lose Sync and all of its functions. Getting a used APIM off eBay from a salvage yard is going to be more cost effective than trying to get something like one of the Android screen kits working correctly and a lot cheaper.
Thanks for the tip!
the rw data wipe tool seems to no longer work, I can get the interrogator to work, it shows rw data completely full.
I have one question which I believe someone already answered indirectly;
with a full rw data folder nothing else will work right? not even a reformat using synupdater tools?
thanks,
It “should” work.
That said there have been numerous reports of not being able to update builds with it full since this is basically where the logs are held.
Hence my statement that you more than likely have a bad APIM.
Thanks for the tip!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.