Ajzride
Well-known member
I still fail to see the logic behind locking the procedure out based on the VIN. The TSB calls it a cybersecurity measure, but that seems like a reach to me.
Sponsored
Yes. Or at least there is a real risk of it. Get the parts you need to finish the job pronto or get it to a dealer. You probably do not want to wait to find out.I started the process but aborted it, will this start the 20 day clock?
So what are options, take it to the dealer or get a USB cable and try it myself? What about running other updates in FDRS? Waste of time or forge ahead?Yes.
I would get as many "SW Updates" done that you can.So what are options, take it to the dealer or get a USB cable and try it myself? What about running other updates in FDRS? Waste of time or forge ahead?
I'm sorry, man. We both learned something today.So what are options, take it to the dealer or get a USB cable and try it myself? What about running other updates in FDRS? Waste of time or forge ahead?
Is there any way to find out if my clock is ticking? I aborted it right at the beginning.Yes. Or at least there is a real risk of it. Get the parts you need to finish the job pronto or get it to a dealer. You probably do not want to wait to find out.
No worries, It's a learning process for sure. I hate wasting time/money though. Too busy for this b/s. Just want my new truck to work as advertised. Where can I find info on the cables/procedure?I'm sorry, man. We both learned something today.
You can perform other updates, but your APIM is so out of date that the updates you need won't even pop up until you do that one. It is the most important one based on your truck's current status. If you feel comfortable following the process, then get the cables and try it. Read the entire document thoroughly before doing anything. In one section it tells you to get certain cables, and right after, it tells you techs reported some of those cables not working and to avoid them. I don't know why they just take the non-functioning cables out of the list instead of adding an addendum, but whatever.
I don’t know. I’m not aware of one.Is there any way to find out if my clock is ticking? I aborted it right at the beginning.
He tried several times yesterday and today. It failed every time. The most recent attempt says:I don’t know. I’m not aware of one.
If I’m reading the chronology correctly, when you started you initially went straight to the PMI. Did you ever run the standard APIM update found under the SW Updates tab? If you haven’t, I’d start with that. I am not optimistic it will work on a 20301 Sync version but you might get lucky. If it does work to update your APIM, the recovery procedure (and the ticking clock) become irrelevant.
I've been having issues with my battery running down to 12V, not sure why since I have a Noco Genius 10 on it. I'm wondering if this is causing my issue. I'm topping off the battery and will try again. Anyone else see this issue?He tried several times yesterday and today. It failed every time. The most recent attempt says:
Downloading USB software has failed: Manifest not found in FENIX reponses
Procedure Unsuccesful - UpdateSoftwareOverUSB Unable to program module, process aborted
Ok. So that’s out and the clock is probably ticking on the recovery procedure.He tried several times yesterday and today. It failed every time. The most recent attempt says:
Downloading USB software has failed: Manifest not found in FENIX reponses
Procedure Unsuccesful - UpdateSoftwareOverUSB Unable to program module, process aborted
10 amps is not as much as you might think. A 20A charger that you can lock into power supply mode during programming is preferred. But you should be ok for most of the shorter procedures IF you are starting with a fully charged battery—one that you have left on the charger overnight so that the charger completes its charging cycle and steps down to maintenance mode.I've been having issues with my battery running down to 12V, not sure why since I have a Noco Genius 10 on it. I'm wondering if this is causing my issue. I'm topping off the battery and will try again. Anyone else see this issue?
When the update fails due to low SOC, FDRS will clearly tell you that is the reason the update process failed. I updated my truck for 13 hours straight using the same charger you are using.I've been having issues with my battery running down to 12V, not sure why since I have a Noco Genius 10 on it. I'm wondering if this is causing my issue. I'm topping off the battery and will try again. Anyone else see this issue?