Search Archive

F900BT (EW) - Either Bluetooth OR TMC (or: downgrade of BT?)

By Boby · Jun 24, 2009in Problems/Troubleshooting💬 3 posts👁️ 2,164 views
Posted Jun 24, 2009 · 18:25 UTC#1

Hi folks,

a few days ago (unfortunately bevor I found this great forum), I updated my European F900BT the following way:

- Firmware: 2.05 => 2.07

- Bluetooth: 2.90 => 3.30

 

The next day, I noticed my Bluetooth didn't work anymore. The software upgrade page told me "not found" - and the button for updating the BT-software was disabled.

 

On my search for a solution, I stumbled over this forum - and successfully downgraded the WINCE-Image like described in some other topics here.

 

After this downgrade, the BT-upgrade-page didn't even show me "not found" - everything was disabled now and BT still not working, of course.

 

On my search I started to fool the device by changing the SYS.TXT in the IGO8 folder. Result of my tests:

- if I put "UC" (=US version) in the SYS.TXT, then my Bluetooth works as it should. If I put "EW" at the end of the model type in the SYS.TXT, bluetooth isnt's working like described above.

- BUT: If I fool my device by using a "UC" in the SYS.TXT, then my TMC doesn't work anymore!

 

That means:

EW = TMC works, Bluetooth doesn't work

UC = TMC doesn't work, Bluetooth works

 

Have you guys any ideas? I would be glad, if I could downgrade from BT3.30 to BT2.90, because I think the problem is caused by the BT3.30 version. But I didn't find a hint here, how to downgrade the Bluetooth software...

 

Thanks,

Robert

Posted Jun 24, 2009 · 22:51 UTC#2

Hi,

at least I managed to downgrade the BT-Software from 3.30 to 2.90.

I also loaded the WinCE-Image which was delivered by Firmware 2.05, but the rest still stays at 2.07.

 

Though, I still have the same problem...I can either use Bluetooth (when I change the SYS.TXT to US-version) or I can use TMC (when I change the SYS.TXT to EW-version). But I can't use both at the same time.

 

Before the update took place, both worked fine...ARGH

Seems to me like the 2.07 update changed something in the system, which lead into this problem.

If I won't get a useful hint, I have to show up at my Pioneer shop, I'm afraid.

 

Thx,

Robert

Posted Jul 05, 2009 · 13:11 UTC#3

Since I didn't find a solution, I put my device back to Pioneer. They formatted everything and set the device up from the scratch. The technician said, the best way to get it back working is to start with the very first version of firmware, doing the update with the next which was released and so on. Took him over two hours, but finally the problems were gone. He said, that was the hint he got from the European central. Seem strange to me that e.g. 2.05 just can be put on an "empty" device, but however...

 

Bye,

Boby