[RajaXXX]

Hi All,

Currently having issues with the 'No Signal' on display.

Car is a 2014 F30 originally equipped with the NBT professional Media.

This has now been retrofitted with an iDrive 4 NBT EVO Unit which has been flashed to iDrive 5 with Full Screen CarPlay.

I specifically went this route to retain the original GPS port on the rear of the HU.

The unit itself appears to work fine as the music and sat nav can still be heard playing using the voice commands etc.

Now unfortunately the issue is with the display - 'No Signal' which generally sorts itself out after multiple reboots using the rotary volume dial and this can vary between 3 to multiple attempts before the screen responds and comes back to life. This however only generally lasts up until the vehicle is switched off and modules go to sleep before I have to repeat the process.

Has anyone else had this issue?

I've tried multiple screens including the original NBT, NBT EVO iDrive 4, and also the NBT Evo Touch all of which produce the same issue.

I've tried all the usual screen coding options and multiple screen cables from the original to the Evo Cable -

CID_APIX_MODE -> apix2
CID_COLOR_DEPTH -> 24
CID_COM_MODE -> mii
CID_RESOLUTION -> 1280 x 480

Played around with the above coding and still repeat issues.

Is the HU at failure here?

[Ibo24]

Try EVO ID5/6 screen cable.

[RuleNormaliai]

Which screen are you using right now? Id4(apix1) or id5/6(apix2) ?

Cables has nothing to do, they are all the same.

Which istep is your HU is flashed with?

[ahmedmph]

Originally Posted by RajaXXX

Hi All,

Currently having issues with the 'No Signal' on display.

Car is a 2014 F30 originally equipped with the NBT professional Media.

This has now been retrofitted with an iDrive 4 NBT EVO Unit which has been flashed to iDrive 5 with Full Screen CarPlay.

I specifically went this route to retain the original GPS port on the rear of the HU.

The unit itself appears to work fine as the music and sat nav can still be heard playing using the voice commands etc.

Now unfortunately the issue is with the display - 'No Signal' which generally sorts itself out after multiple reboots using the rotary volume dial and this can vary between 3 to multiple attempts before the screen responds and comes back to life. This however only generally lasts up until the vehicle is switched off and modules go to sleep before I have to repeat the process.

Has anyone else had this issue?

I've tried multiple screens including the original NBT, NBT EVO iDrive 4, and also the NBT Evo Touch all of which produce the same issue.

I've tried all the usual screen coding options and multiple screen cables from the original to the Evo Cable -

CID_APIX_MODE -> apix2
CID_COLOR_DEPTH -> 24
CID_COM_MODE -> mii
CID_RESOLUTION -> 1280 x 480

Played around with the above coding and still repeat issues.

Is the HU at failure here?

Hi, were you able to fix the no signal issue, i am facing exact same problem

[klepic]

Sorry for bumping this thread again.

I am facing the same issue. I had CIC but I retrofitted NBT fully to 8,8" screen, professional navigation.

Few months ago I installed MMI CarPlay box retrofit and everything works great. However sometimes when I enter the car (especially if it was idle for a hour or so), I got "No Signal" message. I always reset the HU by pressing volume rotor for 30 sec., and after that it works as expected. This does not occur all the time, only sometimes when I leave the car for few hours. Like once a week.

Does anyone know what might be the issue? This was not happening before I installed MMI box, however I am not sure if the box is causing the issue at all. Any tips? I know that for the instance my battery is bad and it needs to be replaced (factory one, 10 years).

[SK223]

Originally Posted by klepic

Sorry for bumping this thread again.

I am facing the same issue. I had CIC but I retrofitted NBT fully to 8,8" screen, professional navigation.

Few months ago I installed MMI CarPlay box retrofit and everything works great. However sometimes when I enter the car (especially if it was idle for a hour or so), I got "No Signal" message. I always reset the HU by pressing volume rotor for 30 sec., and after that it works as expected. This does not occur all the time, only sometimes when I leave the car for few hours. Like once a week.

Does anyone know what might be the issue? This was not happening before I installed MMI box, however I am not sure if the box is causing the issue at all. Any tips? I know that for the instance my battery is bad and it needs to be replaced (factory one, 10 years).

I know that this is actually an issue with the MMI box as it's happened to me as well, specifically the andream MMI box. This is resolved with a firmware update to the MMI box but you will need to contact the manufacturer of the MMI box explaining the issue and they'll send you a specific firmware file to update that should resolve it

[klepic]

Originally Posted by SK223

I know that this is actually an issue with the MMI box as it's happened to me as well, specifically the andream MMI box. This is resolved with a firmware update to the MMI box but you will need to contact the manufacturer of the MMI box explaining the issue and they'll send you a specific firmware file to update that should resolve it

Thanks for the reply! I am not sure if I have exactly that MMI box, however I ordered it from Ali Express. I already contacted them for an potential update so we will see.
For the refference, this is the package box of the MMI:

[fe7565]

Originally Posted by RajaXXX

Hi All,

Currently having issues with the 'No Signal' on display.

Car is a 2014 F30 originally equipped with the NBT professional Media.

This has now been retrofitted with an iDrive 4 NBT EVO Unit which has been flashed to iDrive 5 with Full Screen CarPlay.

I specifically went this route to retain the original GPS port on the rear of the HU.

The unit itself appears to work fine as the music and sat nav can still be heard playing using the voice commands etc.

Now unfortunately the issue is with the display - 'No Signal' which generally sorts itself out after multiple reboots using the rotary volume dial and this can vary between 3 to multiple attempts before the screen responds and comes back to life. This however only generally lasts up until the vehicle is switched off and modules go to sleep before I have to repeat the process.

Has anyone else had this issue?

I've tried multiple screens including the original NBT, NBT EVO iDrive 4, and also the NBT Evo Touch all of which produce the same issue.

I've tried all the usual screen coding options and multiple screen cables from the original to the Evo Cable -

CID_APIX_MODE -> apix2
CID_COLOR_DEPTH -> 24
CID_COM_MODE -> mii
CID_RESOLUTION -> 1280 x 480

Played around with the above coding and still repeat issues.

Is the HU at failure here?

My understanding is that if your EVO is 2GB then flashing it to ID6, which is 4GB, will cause intermittent reboots and errors in navigation and other CPU intense applications.