[aiwa]

Originally Posted by DRuw

I cannot access anything anymore.
The unit is completely dead except for the light on the background.
No menu nothing.
It did work, its the MCU upgrade that went wrong I think...

Have you attempted to remove the ground from your battery so that the unit doesn't get any power?

EDIT* I just saw Druw's video regarding the no signal issue. Once you get this no signal issue can you press the back button or is the system unresponsive once the no signal issue pops up?

Today after changing the loader i rebooted the system and it loaded and went into a no signal error but a quick press of the back button got me to the main android menu. I restarted and got the same thing. It seems like it was defaulting to DVR or some other app. Once I went to music and restarted it would default back to music upon restart.

[koutsouk]

Originally Posted by DRuw

Super! I just dont know how I can put it on there. is there a hard-reset procedure or something?
Ill PM you my email so you can send it by wetransfer or something?

Your issues happen because you installed MCU file from another car entertainment center. Example your car is NBT and you installed CIC MCU version.
Copy the firmware that the other guy told you about.
Put it in a usb stick and rename the file to force_update.
You might not see anything on screen for maybe 10 minutes but the unit after finishing background install might boot.
I do not want to give you false hopes that for all the mights!
I had similar problem and solved it that way.
It might help you operate the android side of the unit again. If you succeed to operate it you need the correct MCU file for your car version.
Do not play with MCU. There are no updates for it regularly.
Every MCU file is car option specific and also manufacturer specific
Hope this can help you.

[uluvsg]

Originally Posted by koutsouk

Your issues happen because you installed MCU file from another car entertainment center. Example your car is NBT and you installed CIC MCU version.
Copy the firmware that the other guy told you about.
Put it in a usb stick and rename the file to force_update.
You might not see anything on screen for maybe 10 minutes but the unit after finishing background install might boot.
I do not want to give you false hopes that for all the mights!
I had similar problem and solved it that way.
It might help you operate the android side of the unit again. If you succeed to operate it you need the correct MCU file for your car version.
Do not play with MCU. There are no updates for it regularly.
Every MCU file is car option specific and also manufacturer specific
Hope this can help you.

Thanks for the extra info about force update.
That really will help if I brick my unit.

MCU files I posted here was given by UGODE staff and it is the correct version for NBT ugode unit.

I guess MCU updating process was somehow inturrupted by other processes in DRuw's case. I will send firmware file to DRuw so hope it will unbrick his unit ;-)

[uluvsg]

Originally Posted by aiwa

Have you attempted to remove the ground from your battery so that the unit doesn't get any power?

EDIT* I just saw Druw's video regarding the no signal issue. Once you get this no signal issue can you press the back button or is the system unresponsive once the no signal issue pops up?

Today after changing the loader i rebooted the system and it loaded and went into a no signal error but a quick press of the back button got me to the main android menu. I restarted and got the same thing. It seems like it was defaulting to DVR or some other app. Once I went to music and restarted it would default back to music upon restart.

I am having the same issue like DRuw and BACK button does nothing whenever the unit shows "NO SIGNAL".

Also, in multimedia menu on IDRIVE side, it says nothing is connected to aux input so I guess android unit is not booted at all. If it was booted in the background, it should show that AUX is connected even though nothing is playing at android unit.


Can you check your CCC type setting under arm setting(first one on the menu at the left hand side) in the factory setting menu?
Is it set to IDRIVE_A or IDRIVE_B?

Mine is set to IDRIVE_B so it would probably set different key settings for idrive knob I guess? ;-( and that could be the reason why mine is not going back to android menu when it shows no signal message on screen?

[uluvsg]

Originally Posted by DRuw

Super! I just dont know how I can put it on there. is there a hard-reset procedure or something?
Ill PM you my email so you can send it by wetransfer or something?

https://mab.to/uMEMa6ta0


Here is the link for the firmware.

Luckily I found I am running teamviewer on my desktop so I was able to upload it through it.

The firmware is given by Louie and it is for NBT Ugode unit.

[Sea-Tac]

Originally Posted by uluvsg

https://mab.to/uMEMa6ta0


Here is the link for the firmware.

Luckily I found I am running teamviewer on my desktop so I was able to upload it through it.

The firmware is given by Louie and it is for NBT Ugode unit.

Appreciate the link. Thanks for putting that up.

[DRuw]

Originally Posted by koutsouk

Your issues happen because you installed MCU file from another car entertainment center. Example your car is NBT and you installed CIC MCU version.
Copy the firmware that the other guy told you about.
Put it in a usb stick and rename the file to force_update.
You might not see anything on screen for maybe 10 minutes but the unit after finishing background install might boot.
I do not want to give you false hopes that for all the mights!
I had similar problem and solved it that way.
It might help you operate the android side of the unit again. If you succeed to operate it you need the correct MCU file for your car version.
Do not play with MCU. There are no updates for it regularly.
Every MCU file is car option specific and also manufacturer specific
Hope this can help you.

Thanks for the tips!
as indicated, my system, setup (and issue) is identical to uluvsg.
I have downloaded the image and will try to force-install it, no response from Louie yet..
I am not just playing with the MCU files, Im trying to resolve an issue that some people have which makes the unit kinda useless.
Issue now is that it completely f*cked my unit at this time so even Idrive doesnt work anymore.
Probably, it half-updated the MCU file and now it doesnt know what to do.
I hope your tip helps with the force update.
I just need to rename the px3.img file to force_update.img and put it in the USD plug?

Edit: this is what it looks like now... ignition off or on..


edit2:
this is going to be a live report as it looks
Allthough the screen is still the same, I can see the USB stick is being read.
Im letting it run now hoping in 10 mins its loaded or whatever its doing....

[koutsouk]

Originally Posted by DRuw

Thanks for the tips!
as indicated, my system, setup (and issue) is identical to uluvsg.
I have downloaded the image and will try to force-install it, no response from Louie yet..
I am not just playing with the MCU files, Im trying to resolve an issue that some people have which makes the unit kinda useless.
Issue now is that it completely f*cked my unit at this time so even Idrive doesnt work anymore.
Probably, it half-updated the MCU file and now it doesnt know what to do.
I hope your tip helps with the force update.
I just need to rename the px3.img file to force_update.img and put it in the USD plug?

Edit: this is what it looks like now... ignition off or on..


edit2:
this is going to be a live report as it looks
Allthough the screen is still the same, I can see the USB stick is being read.
Im letting it run now hoping in 10 mins its loaded or whatever its doing....

The MCU file cannot be half installed .
It is installed or not .
As you say you have the same specs unit.
NBT yours and NBT the other member . Then everything should go smoothly.
That wasn`t smooth indicates that something is wrong.
Can the other member provide a screenshot of the updated MCU info ?
Is it really updated to a newer version or reinstalled the same one?
I was seeing the same things as you when i installed the wrong MCU file in my AVIN unit.
Also the system did not power off when ignition off. As yours...
No iDrive , no Android , just blank screen .
After i let force update run for 10 minutes or 15 and after a few restarts later the unit booted .
I installed the correct MCU file and everything was partially ok , and i say partially because the wrong MCU file ruined my CCC unit. after the revive the colors in iDrive side were yellowish. The problem solved by replacing the CCC unit.
I was lucky to find a CCC unit for 100 € so that was a cheap one.
In your case NBT is really expensive.
That for i say do not play with MCU files. They are dangerous for your OEM system.

Also the ROM is a different thing than the MCU.The is no different ROM for NBT or CIC or CCC versions. They is one ROM.
The MCU makes the difference between the entertainment versions.

[DRuw]

The MCU file is a android file right? not a BMW-system file or am I wrong?
When I connected the original screen, the factory unit still works fine.
Its just the Ugode...
This is the current status:

[koutsouk]

Originally Posted by DRuw

The MCU file is a android file right? not a BMW-system file or am I wrong?
When I connected the original screen, the factory unit still works fine.
Its just the Ugode...
This is the current status:

Yes MCU is an android file but interferes with can bus lines so can mess up original hardware.
thankfully that isn`t happening in your case !
Have in mind to calculate times for the update process .
You must calculate the boot time of your android system when it was working. So lets say 1 minute
The system recognizes the update file and starts auto install in 30 seconds from full boot
We have 1:30 minutes to start updating.
Update time was in my unit 5-8 minutes for a smaller file though. My files were 720 mb . The new file as i saw is 1gb so it will need some time more.
So lets say in total 12 minutes approximately.
After that you should take out the usb stick because the system reboots and if you have the usb stick hooked up it will start again and you do not want that.
After you complete the new installation try to plug and unplug the plugs behind the screen a few times with ignition on and see what is happening.
But i am almost sure that you have installed a wrong MCU file since the ignition on - off does not work.

[DRuw]

Originally Posted by koutsouk

Yes MCU is an android file but interferes with can bus lines so can mess up original hardware.
thankfully that isn`t happening in your case !
Have in mind to calculate times for the update process .
You must calculate the boot time of your android system when it was working. So lets say 1 minute
The system recognizes the update file and starts auto install in 30 seconds from full boot
We have 1:30 minutes to start updating.
Update time was in my unit 5-8 minutes for a smaller file though. My files were 720 mb . The new file as i saw is 1gb so it will need some time more.
So lets say in total 12 minutes approximately.
After that you should take out the usb stick because the system reboots and if you have the usb stick hooked up it will start again and you do not want that.
After you complete the new installation try to plug and unplug the plugs behind the screen a few times with ignition on and see what is happening.
But i am almost sure that you have installed a wrong MCU file since the ignition on - off does not work.

Is the MCU file also updated via the update process as you described?
If that file is "broken" how do I get that one correct?

[koutsouk]

Originally Posted by DRuw

Is the MCU file also updated via the update process as you described?
If that file is "broken" how do I get that one correct?

No MCU file is different one.
The one you try to update is Android system. MCU is the brain of the system.
If i remember correctly the MCU file is a small file ending with .nbd
Only the manufacturer can provide you the correct file.
Only then the system will work properly .
But installing the android system files will give you a hint that the system is working and not bricked, so to need only the MCU file.
i learned all these the hard way believe me !

Read this explains a lot about MCU

https://forum.xda-developers.com/wik.../MCU_Explained


If these things do not work we have another method to try with sd card update process .
Try the above first and we will see what can we do next.

[DRuw]

Originally Posted by koutsouk

No MCU file is different one.
The one you try to update is Android system. MCU is the brain of the system.
If i remember correctly the MCU file is a small file ending with .nbd
Only the manufacturer can provide you the correct file.
Only then the system will work properly .
But installing the android system files will give you a hint that the system is working and not bricked, so to need only the MCU file.
i learned all these the hard way believe me !

Read this explains a lot about MCU

https://forum.xda-developers.com/wik.../MCU_Explained


If these things do not work we have another method to try with sd card update process .
Try the above first and we will see what can we do next.

Dead as a doornail...
This is what I did:
I have put the file on the USB stick and renamed it.
Plugged the stick in and turned the ignition on.
I can see the unit reads the stick for about a minute since the stick itself flashes.
After that stopped, I waited for 15 minutes.with ignition on.
I then turned ignition off removed the USB stick and the main cable to the screen since all this time it is lit up.
Plugged the main cable back in and turned ignition on.
No difference, still a screen that is powered but no Android boot and no idrive or anything...
pulling the main cable out en putting it back kin a couple of times doesnt do the trick as well...

[koutsouk]

Originally Posted by DRuw

Dead as a doornail...
This is what I did:
I have put the file on the USB stick and renamed it.
Plugged the stick in and turned the ignition on.
I can see the unit reads the stick for about a minute since the stick itself flashes.
After that stopped, I waited for 15 minutes.with ignition on.
I then turned ignition off removed the USB stick and the main cable to the screen since all this time it is lit up.
Plugged the main cable back in and turned ignition on.
No difference, still a screen that is powered but no Android boot and no idrive or anything...
pulling the main cable out en putting it back kin a couple of times doesnt do the trick as well...

Ok then we will try the alternative method with SD card tool.
I am not in front my pc right now but you can search for Amlogic SD card tool , download it , start it put the update file through the Programm,remove plug from the unit, insert SD card and put the plug with ignition on. Wait 8-10 minutes and remove the SD card and see if the unit boots. If not you have a bricked unit.

[DRuw]

Originally Posted by koutsouk

Ok then we will try the alternative method with SD card tool.
I am not in front my pc right now but you can search for Amlogic SD card tool , download it , start it put the update file through the Programm,remove plug from the unit, insert SD card and put the plug with ignition on. Wait 8-10 minutes and remove the SD card and see if the unit boots. If not you have a bricked unit.

this is not going anywhere....

[koutsouk]

Originally Posted by DRuw

this is not going anywhere....

I will send you tomorrow morning the files and instructions. Please pm your mail.

[DRuw]

Originally Posted by koutsouk

I will send you tomorrow morning the files and instructions. Please pm your mail.

Done,

Ive tried several usb sticks and SD as well.
Also created a boot SD with a PX5 rockchip tool (the px3tool hangs every time)
but it does completely nothing like before.
Just a lit screen, thats it.


Edit: after some more fiddling I removed the unit from my car. I really need to drive it tomorrow and I cant have the cables to the AC and emergency lights hanging loose.
goes without saying that allready removed stuff is very attractive to take from the car by the baddies...

I wonder what Louie can do for me tomorrow (damn I hate the time difference...).
Will keep you guys posted.

[Supernova66]

Originally Posted by DRuw

Done,

Ive tried several usb sticks and SD as well.
Also created a boot SD with a PX5 rockchip tool (the px3tool hangs every time)
but it does completely nothing like before.
Just a lit screen, thats it.


Edit: after some more fiddling I removed the unit from my car. I really need to drive it tomorrow and I cant have the cables to the AC and emergency lights hanging loose.
goes without saying that allready removed stuff is very attractive to take from the car by the baddies...

I wonder what Louie can do for me tomorrow (damn I hate the time difference...).
Will keep you guys posted.

Any updates?

[DRuw]

Originally Posted by Supernova66

Any updates?

I have one more option to try but if that doesnt work Louie will send me a new PCBA board next week as soon as they are available.
To be honest, a big A+ for his efforts to help me till now at least
There where AVIN said here is the manual and , Ugode really shows the difference for me.
Going to test the last option in an hour, fingers crossed

[DRuw]

Ok, I dont know if you guys kept your fingers crossed but it worked
I had another MCU file and that uploaded finally.
It turns out the MCU file I tried to upload failed the previous time and got it half-done.
This resulted in unable to boot.
Having only the MCU file on a usb stick and boot with that automatically uploaded it and suddenly it shutted down and rebooted with the connected drive and then the menu in chinese
By accident, I selected the correct menu setting and all is back in english.
The no signal issue is not resolved since the next time I booted it turned to no signal but at least I can select the Idrive again!
Somehow, the unit is wiped so need to install everything again but at least its alive again!

[koutsouk]

Originally Posted by DRuw

Ok, I dont know if you guys kept your fingers crossed but it worked
I had another MCU file and that uploaded finally.
It turns out the MCU file I tried to upload failed the previous time and got it half-done.
This resulted in unable to boot.
Having only the MCU file on a usb stick and boot with that automatically uploaded it and suddenly it shutted down and rebooted with the connected drive and then the menu in chinese
By accident, I selected the correct menu setting and all is back in english.
The no signal issue is not resolved since the next time I booted it turned to no signal but at least I can select the Idrive again!
Somehow, the unit is wiped so need to install everything again but at least its alive again!

Nice having good news !
MCU cannot auto update. It updates only from the settings menu. You can try to boot again with the usb stick hooked up and see that it will not happen. Probably you reinstalled firmware , that for everything is wiped!
Anyway very good news !!!
No signal issue is something that happens only to your unit so it might be something connected the wrong way. I remember in my unit always appeared no signal if I had sd card hooked in. If I removed it and boot again everything was ok.
I would like to mention that this no signal issue in my case started to happen when I accidentally installed the wrong MCU file , so maybe the file was not originally good.
I never managed to resolve the issue till I return the unit back.

[Supernova66]

Originally Posted by DRuw

Ok, I dont know if you guys kept your fingers crossed but it worked
I had another MCU file and that uploaded finally.
It turns out the MCU file I tried to upload failed the previous time and got it half-done.
This resulted in unable to boot.
Having only the MCU file on a usb stick and boot with that automatically uploaded it and suddenly it shutted down and rebooted with the connected drive and then the menu in chinese
By accident, I selected the correct menu setting and all is back in english.
The no signal issue is not resolved since the next time I booted it turned to no signal but at least I can select the Idrive again!
Somehow, the unit is wiped so need to install everything again but at least its alive again!

Right on! Super glad to hear WE have a vendor that will respond to our issues. Hang in there buddy..