js12278

Good luck.. its the longest most viewed thread on the forum

Actually, what they've done is to recall the vehicles and yours isn't among those that have been recalled, even though what they REALLY were recalling are radios in the build range of the recalled vehicles . . . . . and they ignored vehicles with the right radio that are outside of the build range, I suspect that if you had a quiet, patient chat with someone at Customer Service at FCA and explained that they put a radio from the range of defective radios into your vehicle (and explained how you know that it is in the range of 'bad radios') they might relent
If you checked and if the navigator software your radio is running version CTP13, CTP14 or CTP15 then you do have one of the recalled radios.
If you'd like to repair it yourself PM me and we can discuss the procedure and you can decide whether you'd like to save the $100 and spend the time to 'do it'.

Recalls are not only for safety issues - mandated recalls (one's ordered my the NHTSA) are, but the manufacturer can recall vehicles for any reason and they clearly felt that they weren't going to win any popularity contests by ignoring the issue . . . . . though they are still obvious screwing around with situations like MSP1330's

Stuff happens, and this is supposedly due to a software bug. They claim to have found the problem and 'the fix' is to update the firmware.
To this end recall R65 was issued for vehicles with the latest radio and bad software to update that software and/or replace the radio with one that has the updated software should it be that the radio comes in for the recall with issues.
I believe that the issue goes further back (and forward) and I have heard of a couple of owners who suffered the 'can't unlock maps' issue after the recall was supposedly performed (though unless I look at the affected radios I choose to believe that the dealer may not have properly executed the recall.
On the other hand, the radios need not actually be swapped. They can be repaired in the field.
One serious issue in the text of the R65 document is that it implies that the fix is a one-time thing.
If indeed it doesn't correct the situation I'm certain FCA will step up But it may require some coercion.
But there IS a recall. That's what R65 is.

Hey bramfrank, glad to hear you will be willing to share your fix if someone wants to try! While I dont have nav in my DJ, its nice to see that if someone is willing to try it your fix is available. Good work!!

THEY had to change it, but IT didn't have to be changed. I've brought these back from the dead and it is relatively simple to do. If you read what I wrote you'll know that I think it is an FCA policy for some reason, perhaps because the fix requires about 2 hours of someone babysitting the vehicle while it processes the data.

Supposedly they've got it figured out now (finally). The latest software for the radio and navigator have been incorporated into the R65 recall. The only problem is that if they DON'T have it figured out, the recall implies that this is a one-shot affair - they go at it and then you're on your own.
If you have the latest radio, a decent Internet connection, a reasonable 8 gig USB stick and a couple of hours to spend on it I can probably walk you though the repair and you can avoid going back to the dealer. I would need to know what firmware your navigator is running, which you can read as it begins to start up.

Thanks for the information.
So you know; While FCA doesn't include your vehicle in the R65 recall, the radio they installed last time is the recalled version - they replaced the original radio with a post 2013 revision, and that's the one in the recall list. You can tell because it is running CTP15.
As such you OUGHT to be able to get it resolved for free since they installed the recalled version of the radio after the initial failure. Or if they were smart about it the would simply reload the maps and then update the firmware for both the radio and navigator to versions 15.09.D1 and CTP16/6.22 respectively.

FCA *claims* to have resolved the problem with the latest firmware release, which you can download from the uConnect web site and install yourself. They also claim that the R65 recall only impacts on the 2013+ radios, which is why I had asked about MSP1330's history and version number (which would identify his radio version).

For the record, it CAN be addressed by the dealer, but it requires a couple of hours of a tech babysitting the vehicle and it may well be that FCA also does something to perhaps make the unit less prone to glitch electrically, which almost certainly would have involved making component changes or additions which would be beyond the skill set of the shop's techs (not that whatever they did seemed to have helped much, because while only the minority of RB5 owners had problems, those problems seemed to recur - i.e. lots of people complained not of only ONE failure, but that they were having their radios replaced for the second or third time).

If indeed the R65 recall (most recent release of firmware) solves the problem, then great. If it doesn't then at least in my case I know how to resolve the issue. It remains, however something beyond what is reasonable to expect the owner to do and beyond the level of patience and ability of the typical owner; and if improperly executed could brick the device.

This thread wins for most views yikes

No. They don't even try to update the maps because they don't have them to install - if they did, they would have had to buy them, which they didn't. And no, the 'hard drive' has not gone bad, because there IS no hard drive - the thing has Novram and it has either glitched for some reason, or there is/was some errant code that changed something in the map segments of memory, causing the unit to report a CRC error in the map file during the device's power-up self test.
They had no reason whatsoever to spend 2 hours with your vehicle since SOP is to order in a replacement unit when the complaint is 'can't unlock maps'..
They COULD resuscitate them at the dealership, but for some reason they don't seem to want to do that.

The mention of the inop nav system is what the "Can't unlock maps" error addresses.