Search results

how many people have had USB drives "broken" from doing these updates? i've had two: one failed internally which enabled the write protect feature. it failed in the middle of a GWM update being written to it from FDRS the second failed when the truck rebooted with the USB drive in it. it...

i didnt have activation issues, but mine was opened (the seal on the box was no good) but everything else looked/felt new.

yeah, get the mongoose. my stuff has been gravy since i ditched the nano...

the big update for APIM is around 2-3GB. I have done 2GB updates in <10minutes with no issue. There's something 'stuck' that causes it, but trust me, it will work eventually. just forget about it, drive around, use the truck, and it will eventually just show up :)

@Snakebitten , my USB update for 1.7.1 after failed OTA took 30 days. 18FEB to 18MAR (to the day). then it just randomly started.

got it, thanks y’all. haven’t had any 2100s yet (or 2400) so i’ll keep my fingers and continue updating!

oh, and i’m afraid to ask at this point, but what is a PMI

good luck man. i’m rolling nearly every update since before 1.7.1 today haha

another recommendation for general use is to install the app Caffeine so your laptop doesn’t go to sleep on long programming sessions. while FDRS recovery from sleep is good, it’s not perfect.

if you use FDRS you can actually see the history of what the technician at the stealership did.

had this issue a few times. usually this happens either 1) if you haven't let it hang long enough before restarting (leave it off, lock the doors, walk away, etc.) or 2) if SYNC hasn't told you to remove the USB yet

so it seems it was an "order of operation" issue. i had to do things in a specific order, and it seems that some modules that have prerequisites would not proceed without those prereqs being met. oh well, all is well.

i ran the test routines at the beginning of the evening (yeah, long day with all the modules on this baby haha). CCM and PSCM show healthy on network scan. i think there may be a mandatory order as SOBDM C took an update, and then pushed a bunch more through.

So... I've done APIM a few times and GWM now, but when trying to do CCM and PSCM, the entire truck shuts off except the sync screen, FDRS establishes comms, then it tells me that it can't communicate. After around 60seconds the truck will "come alive" again, but it won't work with any other...

i'm down south in Manchaca, so if Lodans is closer south, happy to help here.

nothing wrong with PWM, it's better than a lot of analog chargers as it's more efficient with the charging curves required for various batteries. however, as you noticed, sometimes in digital systems it can be a bit weird depending on how the respective circuits are designed to isolate from ground.

re: battery, i use the schumacher INC100. used it when doing DME flashes on BMWs and it works perfect for this. the problem with the Noco and others is it only puts out 1, 2, or 5 amps (some do 10 i think?). my schumacher will do 10+ regularly even without programming. it does up to 100a in...

i think i'm in the same boat as @speedracercjr ... no dice on it catching the APIM upgrade from USB. i've done module resets (GWM and APIM) and the GWM and TCU are both up to date, so looks like i'm in a waiting game :)

I did a full delete with parts from BFN Truck Shop. The guy over there communicates very well and is a general pleasure to work with. The painted parts are a good paint; I didn't find any issues or defects when prepping for ceramic coat of the parts. Would definitely buy from them again.

So normally the sounds play through the normal speaker/stereo system. When there's a condition that may cause issues with that (such as low battery) there's a fallback speaker in the dash/cluster that's used, and it's a single, loud volume. Hope that helps :)