R3 quit receiving alerts after running well for a year

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#1
Somehow my R3 has quit receiving radar alerts. It came with version 1.26 and ran well. I went to 1.30 and 1.31 and it ran very well. I went to 1.46 and did not get a chance to use it at this version and backed down to 1.37 (after reading all the horror stories). With the downgrade to 1.37 it stopped receiving alerts. I then went back to 1.31 and it still did not give me alerts. I went back to 1.46 and I do not get alerts. I've been testing alerts by driving by operational speed traps with multiple radar units in operation and get nothing. I've also been driving by the Walmart doors for K band alerts and get nothing. I did a factory reset after each version change. I bought it in August of 2017 so the warranty is over. Anything I should try before I send it back for an $81.95 repair?
 

OBeerWANKenobi

This is not the car you're looking for.....
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Mar 20, 2018
2,293
5,070
Right Behind You! (Wisconsin)
#2
Yes,
Some users have had this problem when upgrading/downgrading with the wrong version of software being used to do one or the other. I'll see if I can dig up some posts to remedy it.

@Brainstorm69 might know. IIRC, someone came up with a procedure to possibly reverse what you are seeing.

Also, did you have "recovery mode" checked when trying to revert?

--- DOUBLEPOST MERGED ---

This is all I could find at the moment...

www.rdforum.org: 1.46 has really done a number on my R3

I'm sure someone else will be along shortly.

I'd try updating in recovery mode first though, if you haven't done it yet.
 

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Dec 7, 2016
1,620
2,356
#3
Somehow my R3 has quit receiving radar alerts.
Try the suggestions above....however there is a small group of R series owners who have had this happen that has not been related to any software update. Contact Uniden support, after you try above, and I'm sure they will take care of you if it still has failed.
 

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#4
Thanks! I'm reading through the other guys problem and it's given me some ideas to try before sending it off.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Apr 9, 2017
718
1,036
39
NH
#5
I think @OBeerWANKenobi is correct, you need to download the installer for 1.37 off unidens support site and then flash it in recovery mode. Should be good to go from there but not 100% sure.
 

Deadhead1971

Instant-On Survivor
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Dec 7, 2014
2,403
3,204
47
Central NC
#6
This is on the fringe and out there, but check your settings to make sure K band is ON and Ka band is ON.:)

We had one member awhile back come in like yourself and was concerned that he was no longer getting K band alerts; after much probing and inquiry, he discovered to his surprise that somehow K band was turned OFF. It happened.
 
Last edited:

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#7
I think @OBeerWANKenobi is correct, you need to download the installer for 1.37 off unidens support site and then flash it in recovery mode. Should be good to go from there but not 100% sure.
I just tried this with recover mode and tomorrow I'll give it a drive to see if it made a different. What does "recovery mode" mean? What makes it special? I also see that installer 1.22 is included with 1.37 and 1.46.

Update: For clarity I used v1.22 updater to install 1.31 with "recovery". 1.31 was the last good install that I had. If this doesn't work I'll try v1.16, that came with 1.31, with recovery.
 
Last edited:

OBeerWANKenobi

This is not the car you're looking for.....
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Mar 20, 2018
2,293
5,070
Right Behind You! (Wisconsin)
#8
I just tried this with recover mode and tomorrow I'll give it a drive to see if it made a different. What does "recovery mode" mean? What makes it special? I also see that installer 1.22 is included with 1.37 and 1.46.
I don't know for sure but I believe that it forces a reload of the entire firmware instead of just an update. also I believe that without checking recovery mode, if it detects you are already on the firmware you are again trying to load, it won't actually reload it because it figures it's already there.

Maybe @UnidenSupport can shed some more light on the subject.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Apr 9, 2017
718
1,036
39
NH
#9
I just tried this with recover mode and tomorrow I'll give it a drive to see if it made a different. What does "recovery mode" mean? What makes it special? I also see that installer 1.22 is included with 1.37 and 1.46.
Yes first see if that worked. If it does you’re all set.

Though I have a question...When you upgraded from v1.31 to v1.46 did you use the newer v1.22 installer or the same v1.16 installer?

I’m starting to think you should use the older v1.16 installer to go back to previously working v1.31 firmware. Since that was the installer used for that version. Then once you confirm v1.31 is working, use the newer v1.22 installer to get v1.37 firmware loaded. Hopefully it works as v1.37 is a great version.

The key here is using correct installer for the specific firmware and all flashes should have recovery mode checked. If that doesn’t work call Uniden for sure.
 

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#10
I used the V1.22 installer to go from 1.31 to 1.46, and also from 1.46 to 1.37. Somewhere in here it broke. I was thinking that the installer didn't really matter and that using the latest installer was the right thing to do.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Apr 9, 2017
718
1,036
39
NH
#11
I used the V1.22 installer to go from 1.31 to 1.46, and also from 1.46 to 1.37. Somewhere in here it broke. I was thinking that the installer didn't really matter and that using the latest installer was the right thing to do.
I agree, you would think using the latest installer should be fine. But Uniden does specify which installers to use for each version. I can only “assume” if you could simply use the latest installer Uniden would only list it (1.22) for each firmware version and not specify the other installers. Because why else would the say to use older installers if you can you can use the latest. These are just my opinion. But yeah, if 1.37 doesn’t work tomorrow try using 1.16 installer in recovery mode to go back to 1.31 firmware and see what happens. Confirm it’s working. Then from there use 1.22 installer to go to 1.37 firmware.
 

Deadhead1971

Instant-On Survivor
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Dec 7, 2014
2,403
3,204
47
Central NC
#12
I don't know for sure but I believe that it forces a reload of the entire firmware instead of just an update.
Yea that’s my understanding- it wipes the slate clean and reloaded everything rather than what is different between the 2 versions
 

Brainstorm69

TXCTG 2016 MOTY
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 23, 2015
7,663
14,192
Lone Star State
#13
I agree, you would think using the latest installer should be fine. But Uniden does specify which installers to use for each version. I can only “assume” if you could simply use the latest installer Uniden would only list it (1.22) for each firmware version and not specify the other installers. Because why else would the say to use older installers if you can you can use the latest. These are just my opinion. But yeah, if 1.37 doesn’t work tomorrow try using 1.16 installer in recovery mode to go back to 1.31 firmware and see what happens. Confirm it’s working. Then from there use 1.22 installer to go to 1.37 firmware.
Just as another data point, I've used 1.22 to go back and forth between 1.37 and 1.46 without incident.
 

Brainstorm69

TXCTG 2016 MOTY
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 23, 2015
7,663
14,192
Lone Star State
#15
Yes. I used recovery mode.
 

raybo

Learning to Drive
General User
Newly Registered
Nov 13, 2018
9
12
#16
Please post back if you get it to work. Mine stop receiving alerts, but I had it all of 3 days so I returned it.
 

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#17
I do IT work from home and didn't get out today. Hope to tomorrow, to give it a try.
 

UnidenSupport

Learning to Fly
Beginner User
General User
MFG/Vendor
Newly Registered
Oct 16, 2018
102
536
#18
Yup, recovery is a full clear, while updating firmware normally only changes files that have been changed.
 

hlh1

Learning to Drive
General User
Newly Registered
Jul 17, 2017
35
18
#19
Still no joy with 1.22 installing 1.31 with "recovery". Just reinstalled 1.31 with 1.16 and "recovery" is NOT an option with this version download tool. Interesting... I'll get this setup a try.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Apr 9, 2017
718
1,036
39
NH
#20
Still no joy with 1.22 installing 1.31 with "recovery". Just reinstalled 1.31 with 1.16 and "recovery" is NOT an option with this version download tool. Interesting... I'll get this setup a try.
That stinks, what a PITA. Any luck with 1.16 installing 1.31? If not I guess it’s time to call the mothership.