therooster

I reached the same conclusion that one would need the whole SD card dumped to continue testing. A simple card swap would confirm if this would work. A dump of the contents would be a bit harder because of the CMD 42 password lock.

I take it there are different passwords on the 4000 series and the 4100 series?

That seems like the most plausible explanation which makes a complete image of the x100 internal SD card that much more important. I just find it a little strange that the "structure" of a map file can change that much. I wonder if they are somehow keyed to a device number or software version to prevent "cross usage" almost like a lock to a particular range of devices or even a specific device. I mean after all, if you attempt a map upgrade it asks you to insert the USB stick so the unit can "prepare" it for an upgrade. Just really thinking out loud here no real evidence to support any t

I believe that there was some work over there regarding the AppRadio2 and it's android OS. Quite honestly if they took a look at this I tend to believe they would come up with a solution. Many times it's not about the talent, but rather the tools. Seeing what the problem is becomes more than half way to solving it. On another note, I tried to update my NEX-8000 to the 3.41 Bluetooth with no luck... Forgive my laziness, but can someone post a step by step on getting the updated Bluetooth firmware into a NEX running 1.08. Thanks.

Just a quick update. I had a little free time and decided to play with the update process. Same results as everyone here regarding the bluetooth issue. What is a bigger concern to me is the Navigation portion having a whitewashed screen with the 1.03 X100 update applied. I'm not sure if this is a map issue. I think the key here is to extract the internal SD card from an X100 series model and try it in corresponding X000 series model. That way we know if it is a firmware issue or if Pioneer has somehow intentionally "tweaked" the new models to purposely break an attempt at updates. Th

Being the new guy here I'm hoping I can add to this discussion on two fronts, first and most importantly, getting the x100 series firmwares to work in our x000 units, and secondly how pioneer sees the whole support of older head units issue. First, From reading the fail overflow blog I think I have a pretty good idea as to why both he Bluetooth and idatalink issues are happening when a x100 series update is applied to a x000 unit. It seems it may be related to the devices being mounted by the android OS. Failoverflow lists the devices of the x000 firmware as follows. /dev/t