iOS 8.3 is introducing wireless CarPlay.  I'm hoping the 4000NEX will allow for that.

iOS 8.3 is introducing wireless CarPlay.  I'm hoping the 4000NEX will allow for that.

My guess is that they have to issue an updated firmware.  I am afraid, we are in the dark.  Someone said (think Covert_Death) they heard somewhere we will get one more.

My guess is that they have to issue an updated firmware.  I am afraid, we are in the dark.  Someone said (think Covert_Death) they heard somewhere we will get one more.

I suspect it won't.  The wireless CarPlay seems to be way more integrated into a car than an aftermarket headunit can provide.  I may be wrong, but the screenshot of the iOS 8.3 beta has you initiating the setup of wireless CarPlay by pressing the "talk" button on the steering wheel of your car.

Although I will try (again) the "Siri Hands Free" (or whatever it is called) button on my 4000NEX and see if that works instead.  I think I tried that already and nothing happened but I can't remember.

 I am currently running the newest iOS beta.

 

and with new CarPlay settings in iOS 8.3 you can allow CarPlay without unlocking device, plug and play like android auto.

Does this work with the official 4000nex 1.08 firmware? That's really the only thing i'd like to have with CarPlay other than more compatible apps.

I loaded the the 8100 firmware on my 8000, loaded up fine and booted up fine, i did notice the slight differences here an there, I couldn`t to get my Bluetooth work with my Lg G3, so I reloaded the 8000 firmware and it started to work again, I will reloaded the 8100 tomorrow and try again, I did notice it changed the device number and I have this in a 2011 f150 and I use the Idatalink maestroRR for my steering wheel controls and once I updated to the 8100 I lost the use of my steering controls and that could be that i need to flash the module as I have 8100 instead of the 8000, I will do more testing tomorrow

iOS 8.3 is introducing wireless CarPlay.  I'm hoping the 4000NEX will allow for that.

Someone else suggested this will require Wifi which is probably correct. I haven't see mapping or other apps working over bluetooth before.

damn, well since everyone is having problems, even on identical models (8100 = 8000 part for part right????) im not sure what to take away from that. I'll try a few more things out but we may be SOL unless pioneer releases another FW for the X100 series that plays nicer. 

unless of course someone far more talented than I can open the .prj files, but I assume these are just packages for compiled code and won't make any sense regardless of how it is opened.

I don't know how long some of you have been on this forum, but there may be interesting info here

http://avic411.com/index.php?/topic/38859-nex-runs-android-and-other-useless-info/?hl=+5000nex%20+firmware

and here

https://fail0verflow.com/blog/2014/enhancing-the-avic-5000nex.html

and part 2 of that

https://fail0verflow.com/blog/2014/enhancing-the-avic-5000nex-pt2.html

Maybe someone smarter than me can put all this together...

 

Hey guys, so I have been working on flashing my NEX4000 to a NEX4100 and so far have had a lot of luck (images below) It seems everything is working except for the Pandora app. I want to do this the right way and not harm anyones devices. I am working very hard on understanding the 4000/4100 FW and as soon as I do I will also migrate to the 8000 and 6000 devices if I have people willing to test for me.

 

Below i have a donate button. This is not required but is certainly appreciated as my wife is pregnant and we are both starting out our careers so things are a little tight and spending time on this, while fun, does take away from other productive things I could be doing. Anything you feel comfortable with is more than appreciated to help!

 

Please Donate Via PayPal!

 

Known Issues:

 

1. All BT audio (in and out) seems to not work.

2. Must reset SXM data after FW update to get SXM to work.

 

DOWNLOAD LINKS:

 

4000 (1.08) to 4100 (1.03)

http://www.filedropp...om/4000to4100_1

4100 (1.03) to 4000 (1.08)

http://www.filedropp...4100to4000test1

 

6000 (1.08) to 6100 (1.03)

http://www.filedropper.com/6000to6100

6100 (1.03) to 6000 (1.08)

http://www.filedropper.com/6100to6000

 

8000 (1.08) to 8100 (1.03)

http://www.filedropper.com/8000to8100

8100 (1.03) to 8000 (1.08)

http://www.filedropper.com/8100to8000

 

 

 

 

 

 

 

 

 

 

Let me know what you guys think!

 

hi covert_death, one question? are you sell your firm on eBay?, becouse i found in $40 bucks:

http://www.ebay.com/itm/271816740040?rmvSB=true

I'll try a few more things out but we may be SOL unless pioneer releases another FW for the X100 series that plays nicer. 

I tried to find any evidence of people having BT problems with their new x100 units, but came up empty. I think BT works fine on the x100 units, so unfortunately I am not hopeful that the next x100 update would help us x000 owners

I tried to find any evidence of people having BT problems with their new x100 units, but came up empty. I think BT works fine on the x100 units, so unfortunately I am not hopeful that the next x100 update would help us x000 owners

I think there is hope to modify still (I can't, but I am sure someone can) - there is no upgrade in the bluetooth version, both have: Bluetooth 3.0+EDR certi- fied

I checked the manual on both for the information.

while the versions may be the same, they may use a different bluetooth chip that would require a different driver... or of course, it could just be a firmware flash difference. Has anyone inspected to see if the BT chips are the same?

If its new chip, wouldn't flashing old BT firmware do the trick? The new Bluetooth folder I think is about 2mb bigger.

If its new chip, wouldn't flashing old BT firmware do the trick? The new Bluetooth folder I think is about 2mb bigger.

how would you flash the BT firmware?  and is that reversible?  sorry, I am not a programer.  databases are my things lol

how would you flash the BT firmware?  and is that reversible?  sorry, I am not a programer.  databases are my things lol

With each firmware there is a folder called "bluetooth" the one for the new 4100 is about 2mb bigger than the bluetooth folder for the 4000nex.  For some reason when you flash the new 4100 firmware the option in "A/V output" for "Bluetooth Audio" is stuck to off. Even if you flash the new firmware with the old bluetooth folder it gets the same result.  That seems to be the problem. The stereo still reads the song titles or whatever your trying to play but the Audio does not work. 

The 2014 NEX bluetooth firmware is: HW01-SW03.21.30

The 2015 NEX bluetooth firmware is: HW01-SW03.41.10

DOes anyone have access to the actual BT firmware for the 2015 NEX's?  

The 2014 NEX bluetooth firmware is: HW01-SW03.21.30

 

The 2015 NEX bluetooth firmware is: HW01-SW03.41.10

 

DOes anyone have access to the actual BT firmware for the 2015 NEX's?  

Im confused on what you're asking? We have the files for both versions. 

Im confused on what you're asking? We have the files for both versions. 

The x100's 1.03 firmware is only 1 part of what's needed.

We need the BT firmware from the x100nex so the radio and BT communicate.  This is of course, assuming that the x000nex will accept it.

X100 BT firmware:

x000 BT firmware:

 

The x100's 1.03 firmware is only 1 part of what's needed.

 

We need the BT firmware from the x100nex so the radio and BT communicate.  This is of course, assuming that the x000nex will accept it.

 

X100 BT firmware:

 

x000 BT firmware:

what he is saying is that the nex x100 1.03 firmware files do not upgrade the bluetooth because the stock bluetooth on the headunits is already 31.41.30. So when we update our headunits we have the wrong bluetooth firmware and the unit stops working correctly. 

Hmm interesting. So whats the bluetooth folder thats included in the firmware?

So the bluetooth folder on the x000 series has PJ140BTHSAF.PRG while the X100 series has PJ150BTHSAF.PRG , one number difference. Has anyone tried renaming the 150 series to 140, and flashing the bluetooth on the older x000 series OS first, then if it takes, upgrade to the x100 OS?

The sizes of each corresponding file in the bluetooth folder is very close, the BTL file is the SAME size, so is the UDP file. The SAF is the only one with a difference in size, and its .2 megs.

So the bluetooth folder on the x000 series has PJ140BTHSAF.PRG while the X100 series has PJ150BTHSAF.PRG , one number difference. Has anyone tried renaming the 150 series to 140, and flashing the bluetooth on the older x000 series OS first, then if it takes, upgrade to the x100 OS?

 

The sizes of each corresponding file in the bluetooth folder is very close, the BTL file is the SAME size, so is the UDP file. The SAF is the only one with a difference in size, and its .2 megs.

I've tried that, didn't help unfortunately.

This is so awesome. Cant wait for this to work!

I have tried several combinations of the bluetooth files now to no avail :/

I have an idea, but it's insanity. The NEX has a recovery system for if the radio has a catastrophic failure during the update like if lets say you turned off the car during. My guess is that it would be a full wipe of the system to return to stock, vs an update only changes the files that need changing. If I were to do this hacked update and then force restart the radio while it's going it might force it to do a full fresh install which could install the missing parts of the firmware that is causing it to act up. 

I'm not crazy enough to do this, but I'm tempted.