While I am planning to rent Toolbox to work on my Model 3, which is now out of warranty, I also would like to use it to check the eMMC health on my Model S during that period.
I don't think Toolbox works on the Model 3 or MCU2.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
While I am planning to rent Toolbox to work on my Model 3, which is now out of warranty, I also would like to use it to check the eMMC health on my Model S during that period.
I understand that. I have an MCU1 Model S.I don't think Toolbox works on the Model 3 or MCU2.
You might be 6 days, 6 weeks, or 6 months for complete failure to boot. Good luck!
Some people have reported that the service centers do a memory check which does look for the number of bad blocks and if it's above some threshold, they will replace it.So is complete failure the official threshold? I mean clearly, they will replace it at that point, but not before? I'm looking for something concrete, like "25% of blocks in the eMMC have failed" or "Only 4096mb remain usable". Something precise that I can run a diagnostic on and have a definitive answer before I even schedule the visit.
So is complete failure the official threshold? I mean clearly, they will replace it at that point, but not before? I'm looking for something concrete, like "25% of blocks in the eMMC have failed" or "Only 4096mb remain usable". Something precise that I can run a diagnostic on and have a definitive answer before I even schedule the visit.
The latest firmware has their checks built in and will warn you when you need to schedule an appointment. (Or if it gets really bad it goes into a "limp" mode that only displays the backup camera, and sets other options to "safe" defaults, like HVAC on auto...)
3. If the eMMC name is “H8G2d”, determine if the filesystem malfunctioned due to wear.
- If alerts “MCU_w088_eMMCNeedsReplacement” or “MCU_w086_eMMCEOL” are actively asserted, recently asserted, or present in vehicle logs, continue to “Provide Rectification”.
- If alert “MCU_w031_cidSquashfsError” is actively asserted, recently asserted, or present in vehicle logs, AND there are fewer than 65 reserve blocks remaining, continue to “Provide Rectification”.
- If neither of the above is true, the eMMC filesystem has not malfunctioned due to wear, continue to “Vehicle Ineligible”.
If the eMMC name is “Hynix”, determine if the filesystem malfunctioned.
- If alert “MCU_w031_cidSquashfsError” is actively asserted, recently asserted, or present in vehicle logs,continue to “Provide Rectification”.
- If alert “MCU_w031_cidSquashfsError” is not present, the eMMC filesystem has not malfunctioned, continue to “Vehicle Ineligible”.
My eMMC was replaced a couple weeks ago under the warranty adjustment. However, it doesn't seem to have helped my problem much. Though the MCU does seem to boot a little faster and is a little more responsive, I keep getting intermittent lockups that require a reboot. Normally what happens is after some time of driving (usually over an hour), I see the LTE resetting and the outside temp going to ---. Then audio effects sometimes don't play (blinkers, etc.). Then the map gets jittery and the interface starts to lag more and more until it doesn't respond at all, and there is no audio and no further updates to the screen. Sometimes the MCU will reboot itself after a couple minutes of that final state, but sometimes I have to reboot it. I was previously on 2020.36.11 and now I'm on 2020.40.9.2 and it's still happening. This never happened before 2020.36.11, not that that means anything though.
You likely need some factory resets, and possibly an additional update. This often happens if some of the corrupted data gets copied to the new eMMC.
Good point - sorry, I forgot to mention that I did a factory reset last week. Still having the issue.
try 5-6. Note the fine print