That's great news, because no matter what I had tried, my pb would download fine. So the issue was with the rooting of the phone? I am not real familiar with the rooting of phones that I have read about people doing and sometimes think about trying it but I'm more worried about messing something up and damaging the phone.
Glad that you got it working though.

 

Matthew, I have heard that about the dealers over there. I had helped another guy in Australia last year with an issue the dealers couldn't help with.
I double checked on the PN's that I had given you. Both numbers are still correct PN's. However the module does have a new PN for the 2014 vehicles (5091961AA), but you don't have to go out to 2014. The SW is the same in 2012 - 2014, there have only been changes in the PN for the year changes. In 2013, there was a verbal change made for the Chrysler website and also telling you that the "vehicle should be parked while pairing a phone" instead of saying "have your vehicle in Park, while pairing a phone". People seemed to be confused with how to put a manual trans vehicle into "park".
Here's a link for proof of the part:
http://www.partswebsite.com/moparonl...8104911AC.html

http://www.partswebsite.com/moparonl...82212503-.html

 

In the upper glove box, the one above the normal one, there is the pigtail 30 pin connector. So that kinda sucks that I can't get BTSA without getting a new system. Im asked the talked with someone on the mopar owners website that told me there is no update for the radio. Where would I find if there is an update for the unconnect system.

 

Unfortunately, there isn't any updates for the module that you have. SW updates weren't really needed until the constant advancing of the phone mfgs Android & SW. Phones used to be rather basic prior to the Android invasion.

 

Thanks for that. I contacted that company and they said that the part is no longer available? Would the 2013/14 model still be compatible with my vehicle? what is the model number for that? What is the difference between the US model and the Euro/Australia model? would a US model work in my vehicle?

Thanks

 

Matthew, sorry for just getting to the forum and seeing this. The PN for the 2013 & 14 modules is: 05091961AA, did they try that # or did they only check on the 2011 - 2012 unit?
The difference between the USA part and the ROW part is the country codes and tone of the Uconnect speech (yours sounds somewhat British, correct). The country code is responsible for setting the emergency and towing assistance phone numbers.
Also the radio frequency section in the voice command section is different. Because of this, I wouldn't suggest replacing yours with the USA module.
If you continue having issues getting the part, as I have mentioned before, I'm sure that I can help you out.

 

I have ordered this part
http://www.wermopar.com/oem-part/dod...dule/5091961aa
Just noticed it is missing the zero at the start of the part number? will that make a difference, is it the same part? I sincerely hope it all works.

Thanks

 

correct, they are missing the "0" in the front of the PN. This will work for you. Glad that you were able to get it.

 

Hi, I know this is a Dodge forum but saw several posts related to Uconnect RHB model here. Please let me know if this is the wrong forum for this question.

I just bought a brand new Jeep Compass 2013 that has the 430N/RHB dashboard panel with Uconnect bluetooth. I also have an Iphone 5 IoS version 6.1.3 (the latest as of today).

While pairing and phone works, I am unable to download my phonebook to it. Have tried many times through setup but it doesn't seem to work. I have about 200 names in my contact on Iphone.

So my question is: 1. how to download the phonebook to my Uconnect and 2. Is there a firmware upgrade available for my system? If yes, where do I go to get the update file and also, how to update it? I figured it would involve copying the update file on an USB drive but would like a step by step instructions.

Again, I am sorry if I am in the wrong forum. I have checked the Jeep forum and haven't been able to find any solution.

Thanks for any help.

 

Well, the issue really isn't in "rooting" the phone, it is more when one uses custom ROMs that tweak the phone's kernel to "optimize" things for their specific ROM or need. In case there are those that read this and don't know.....kernels control very low level things like drivers for the screen, mic, GPS, radios, etc. that the phone software needs to interact with.

So if you just root your phone and don't do anything else to the kernel, the phonebook and whatnot will work just fine. If you install a custom kernel to the phone, then you might have issues.

I tested quite a few other ROMs and some kernel tweaks work okay and others do not. Overall though, I have found from all my testing, that running the phone stock as Samsung and Sprint would like you to, yields the best battery results and the most consistent usage of features. More importantly, features like All Share Play where you can mirror the phone to your Samsung Smart TVs, doesn't work at all on rooted ROMs to this point. So stock is fine.

The main reason folks root their phone is to get around some limitations like carrier restricted data-tethering (like data to a laptop through your cellular connection). Since Sprint's service is absolutely abysmal here, there's no way that would be beneficial to me. Some other uses of rooting are less nefarious like installing newer features from a future Android build like Photospheres, etc.

Sorry for the largely off topic response, but it might help others in some futuristic time.