Locked out! Neither phone as a key nor key card worked.

[Atlrivian]

Thanks for the update, that is good information to keep in mind. Would be nice to know if just unplugging the 12 volt batteries and waiting a few minutes was the extent or if more steps were required.

I'm not sure what exactly the screen runs off, but for me the problem was getting to all the wiring in the frunk. With frunk access I could repeat the procedure for disconnecting everything in ~10 min with just hand tools.

Sponsored

 

[R1TFTW]

Thanks a lot for the information and follow-up on the experience

 

[Aardvark]

He had to take apart most of the front driver's side wheel well, in order to manually release the frunk. Once the frunk was released, he disconnected the main and 12v batteries to do a hard reset of the computer.

This seems like a complicated, but valuable procedure to learn. I haven't looked to see if it's in the owners' manual. The simple pop-out cover on Teslas for frunk access has the advantage of simplicity, but always worried me from a security standpoint. The R1x procedure certainly sounds more secure, but fairly complicated if trying to do this on a road trip.
@Atlrivian thank you very much for taking the time to report your issue and follow up.

 

[SANZC02]

This seems like a complicated, but valuable procedure to learn. I haven't looked to see if it's in the owners' manual. The simple pop-out cover on Teslas for frunk access has the advantage of simplicity, but always worried me from a security standpoint. The R1x procedure certainly sounds more secure, but fairly complicated if trying to do this on a road trip.
@Atlrivian thank you very much for taking the time to report your issue and follow up.

Opening the frunk manually is covered in the owners manual.

 

[Mark’s RT-1]

Had the same issue. Fix was actually to un-install all of my other BT devices from my IPhone 13 Pro. Then follow the “set up phone as key” from the dashboard. Worked like a charm.

Rivian phone support person was no help at all. Someone on these forums clued me in. And it works! Pain in the butt to reinstall all of your other BT goodies but oh well.

Earpod Pros we’re the culprit.

 

[Riviot]

Did the gear guard record the whole "popping the front trunk" experience? And if so, did the alarm ever sound?
If it doesn't unlock or read a key, I would hope the alarm would sound if manually opened.

 

[shrink]

Had the same issue. Fix was actually to un-install all of my other BT devices from my IPhone 13 Pro.

Earpod Pros we’re the culprit.

Wait, what? I’m guessing you meant AirPods Pro, but how did you determine those were causing the issue? Were you able to pair them again once the Rivian was happy?

 

[Mark’s RT-1]

AirPods Pro; sorry.

Another forum member suggested it and it worked.

Paired them back up and no issues. Has been about a month since the issue. Give it a try.

 

[PoorDick]

For me it was to simply turn off bluetooth on my phone (Pixel 5), wait a minute, turn it back on and, voila, the truck unlocked using the phone key. It's happened twice now...

 

[RexRemus]

I hate having to go over the entire story multiple times like that, but it seems inevitable in these situations. Glad they got it figured out for you!

Probably the only good thing about waiting for my truck is the hope they will have some of these bugs worked out by next year when I finally get mine.

yeah, I have become more and more comfortable waiting for my next-year delivery. I am confident I'll be receiving a much better vehicle and user experience than I would be getting it "now" - one more year-ish of software/hardware/manufacturing/process updates I am just fine waiting for that end result

 

[Atlrivian]

Did the gear guard record the whole "popping the front trunk" experience? And if so, did the alarm ever sound?
If it doesn't unlock or read a key, I would hope the alarm would sound if manually opened.

Millions of videos from GearGuard. No alarm activation.

I'm assuming manual disengagement doesn't cause an alarm on purpose because it's just so annoying to open the frunk this way. If I was trying to break in I'd want a much quicker / dirtier method.

 

[Atlrivian]

For me it was to simply turn off bluetooth on my phone (Pixel 5), wait a minute, turn it back on and, voila, the truck unlocked using the phone key. It's happened twice now...

I tried all these tricks within thr first 5 min of my first call to the service center. None of them fixed my issue.

 

[Khaneric]

FYI, I had this same issue today except my keyfob didn't work either. Tried the fob, card key and nothing. I opened the app and was able to unlock it ONE time but it failed everytime after that.

I was unable to drive the truck as it kept asking for the key even though I tired all three. Had to hard reset it from inside before anything worked again.

 

[cbuckley]

Had the same issue. Fix was actually to un-install all of my other BT devices from my IPhone 13 Pro. Then follow the “set up phone as key” from the dashboard. Worked like a charm.

Rivian phone support person was no help at all. Someone on these forums clued me in. And it works! Pain in the butt to reinstall all of your other BT goodies but oh well.

Earpod Pros we’re the culprit.

I had the exact same issue early in ownership and also linked the failure to my AirPod pros.

Glad you were able to get it sorted out.

 

[cbuckley]

Wait, what? I’m guessing you meant AirPods Pro, but how did you determine those were causing the issue? Were you able to pair them again once the Rivian was happy?

After spending hours on the phone with Rivian and trying every other troubleshooting tip to no avail, it was a bit of a process of elimination. I happened to notice that the only time my PAAK worked was when I was listening to my AirPods. It wouldn’t work while using other BT devices so I figured it might be related. I unpaired/forgot all of the BT devices on my phone, repaired phone with Rivian, and then PAAK has been working flawlessly ever since (April). After pairing the Rivian, I added all my other devices back - including the AirPods - and everything is in working order.

Sponsored