astrorob
Well-Known Member
- First Name
- rob
- Joined
- Aug 26, 2022
- Threads
- 22
- Messages
- 873
- Reaction score
- 388
- Location
- bay area
- Vehicles
- 24GT, plug-in prius, 99 MBZ C43
- Thread starter
- #1
tl;dr deleting the FordPass app and reinstalling seems to have unstuck everything in the app/cloud, including PAAK.
i've posted here before about this problem - when i picked up my 23 GTPE in late december, PAAK would not configure. the dealer immediately took it to the service bay and declared that the TCU was bad. they ordered and installed a new TCU which did not resolve the problem, and i think they put my old TCU back since i assume ford would not pay them for the new TCU under warranty. they left the service ticket open and contacted ford for help. 2+ weeks later, they have no new info from ford.
today i decided to try to log my issue with the BEV group. predictably they wanted me to go thru the PAAK setup again, and somehow we got it wedged in a new way - the cryptographic key got stuck in such a way that the setup could not be repeated after the inevitable BLE connection failure. the app asked me to delete the key and despite doing this the key persisted in the list of keys despite multiple attempts. at that point the BEV person just gave up on me and opened a case, but wasn't interested in trying anything else. just about the only thing i learned from her is that the dealer does indeed have a case open with ford. in the end i told her i was going to delete the FP app in an effort to purge the key, and ended the call.
after deleting and reinstalling the app, the old key was still there. it wouldn't proceed if i tried to use the same name, however, this time it did not complain when i gave it a different name. to my great surprise the pairing dialog box popped up and i was able to complete the process. the car then offered me to create a backup start code and a custom door code. i put my fob in the house and indeed the car unlocked and started with my phone. success!
not sure if this has anything to do with it, but yesterday i pulled fuses 11 and 19 in an effort to reset the TCU and RFA. obviously that was not sufficient to solve this problem, but perhaps it was necessary.
i think one clue about all this is that somewhere along the line i stopped getting the in-app blue status messages at the bottom of the screen, but i'm not sure when that started. this could all have its origin in the fact that i downloaded FP and tried to attach the VIN to the app while the car was still in transit to the dealer. someone at the dealer definitely clicked the OK button in the car, because i could see the charges they were doing to prep the car for me. so it could be that when the car was marked "sold" by the dealer that things got wonky on ford's back-end. or, this could be because the car temporarily had a different TCU. but somehow completing the PAAK setup with a fresh app install caused all those things to start working again.
the car/app/backend was in some partially provisioned state, because all this time i could still see the battery level, odometer, unlock doors, etc. but was unable to change any charge settings from the app, nor see any trips or charging data. this is now all working after setting up PAAK. i also note that the "connected vehicle services" dropdown in the car's settings (in SYNC) was completely empty until finishing PAAK. i believe they were all there before the dealer did the TCU shuffle though.
at this point the only issue is that the phantom key is still in the app, and it still can not be deleted. i suppose if i went thru the whole fordpass reset in the car i might be able to get rid of it but now that its working i don't want to mess with anything.
thanks for reading, and i hope this helps someone who finds themselves in the same situation.
i've posted here before about this problem - when i picked up my 23 GTPE in late december, PAAK would not configure. the dealer immediately took it to the service bay and declared that the TCU was bad. they ordered and installed a new TCU which did not resolve the problem, and i think they put my old TCU back since i assume ford would not pay them for the new TCU under warranty. they left the service ticket open and contacted ford for help. 2+ weeks later, they have no new info from ford.
today i decided to try to log my issue with the BEV group. predictably they wanted me to go thru the PAAK setup again, and somehow we got it wedged in a new way - the cryptographic key got stuck in such a way that the setup could not be repeated after the inevitable BLE connection failure. the app asked me to delete the key and despite doing this the key persisted in the list of keys despite multiple attempts. at that point the BEV person just gave up on me and opened a case, but wasn't interested in trying anything else. just about the only thing i learned from her is that the dealer does indeed have a case open with ford. in the end i told her i was going to delete the FP app in an effort to purge the key, and ended the call.
after deleting and reinstalling the app, the old key was still there. it wouldn't proceed if i tried to use the same name, however, this time it did not complain when i gave it a different name. to my great surprise the pairing dialog box popped up and i was able to complete the process. the car then offered me to create a backup start code and a custom door code. i put my fob in the house and indeed the car unlocked and started with my phone. success!
not sure if this has anything to do with it, but yesterday i pulled fuses 11 and 19 in an effort to reset the TCU and RFA. obviously that was not sufficient to solve this problem, but perhaps it was necessary.
i think one clue about all this is that somewhere along the line i stopped getting the in-app blue status messages at the bottom of the screen, but i'm not sure when that started. this could all have its origin in the fact that i downloaded FP and tried to attach the VIN to the app while the car was still in transit to the dealer. someone at the dealer definitely clicked the OK button in the car, because i could see the charges they were doing to prep the car for me. so it could be that when the car was marked "sold" by the dealer that things got wonky on ford's back-end. or, this could be because the car temporarily had a different TCU. but somehow completing the PAAK setup with a fresh app install caused all those things to start working again.
the car/app/backend was in some partially provisioned state, because all this time i could still see the battery level, odometer, unlock doors, etc. but was unable to change any charge settings from the app, nor see any trips or charging data. this is now all working after setting up PAAK. i also note that the "connected vehicle services" dropdown in the car's settings (in SYNC) was completely empty until finishing PAAK. i believe they were all there before the dealer did the TCU shuffle though.
at this point the only issue is that the phantom key is still in the app, and it still can not be deleted. i suppose if i went thru the whole fordpass reset in the car i might be able to get rid of it but now that its working i don't want to mess with anything.
thanks for reading, and i hope this helps someone who finds themselves in the same situation.
Sponsored
