Here is the latest log, I just ran it again. I’m not opposed to trying to disconnect the APIM, however before I started down this rabbit hole, I disconnected the battery on the truck and left it disconnected overnight (8+ hours). Wouldn’t this have the same effect as unplugging the APIM?
There are no DTC’s for the APIM.
The APIM is original to the vehicle and no asbuilt data has not been modified.
This is what is installed on the unit…
4U5T-14G422-CBC
4U5T-14G421-CHD
4U5T-14G421-CBD
4U5T-14G422-CAJ
4U5T-14G421-CCD
4U5T-14G421-CGD
4U5T-14G421-CDD
4U5T-14G421-CAD
4U5T-14G422-CCC
5U5T-14G391-CS
4U5T-14G421-CFD
4U5T-14G421-CJD
4U5T-14G421-CED
4U5T-14G424-CD
rwdata…is completely full
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1.2G” available=“0”/>
Storage is fine…
<d2p1:PartitionHealth type=“/fs/images/” total=“25G” available=“5.2G”/>
This is the APIM parameters…
7D0
F10A>GB5T-14G379-AA
F110>DS1U5T-14G371-DA
F111>GU5T-14G380-ED
F113>KU5T-14G371-CDF
F124>1U5T-14G375-DA
F141>VY5X000F
F16B>JB5T-14G379-BA
F188>1U5T-14G374-DA
F18C>??? Not reading ECU Serial Number, not really an issue.
F1D0>B07E11D1FA5A
F1D1>B07E11D1FA5B
This matches production release firmware…
3.2/3.3 APIM NAV & NON-NAV Unit Firmware (Production Release, 2018.5, Late J thru K Series)
Secondary Boot Loader: GB5T-14G376-AA
Strategy (F188): 1U5T-14G374-DA (6/27/2018)
Calibration (F124): 1U5T-14G375-DA (NAV) / 1U5T-14G375-CA (NON-NAV)
ECU Configuration/Sound Profiles (F10A): GB5T-14G379-AA
ECU Configuration/Illumination Strategy (F16B): JB5T-14G379-BA (6/7/2018)
Based on the above information, there is no reason the unit should not respond to the recovery efforts of running the RW Cleaner tool or soft resets.
I do see however, that the storage has increased due to the deletion of Gracenotes. This unfortunately didn’t help the rwdata issue. Also the /fs/rwdata/quip/ folders are now full also.
Hi, i already saw an issue like that, but the weird thing is that in this case it’s happening on build 23188.
We have few possibilities here:
The partition is fucked up (and there no way to fix that from the OS). You need to USB Boot it and flash the universal reformat (or the OEM reformat) directly from the Board. If the eMMC sectors are damaged, the reformat will not fix the problem, and you need a new APIM.
The partition is somehow full, but not due to logs, and that’s why the cleanup utility does nothing, and also this explain why it’s happening on build 3.4.23188 and you have only one thing you can try. Jailbreak it and then debug it / fix it by running some custom shell scripts. If jailbreak keep failing (and it’s a possibility due to rwdata being full but sometimes keep trying make it works) then the fix is again the direct flash of the universal reformat (or the oem reformat)
How do I go about executing the suggested solutions? I’m comfortable doing almost anything but I’m by no means a tech expert, is there a guide similar to the other guides found on this site?