[ROM][RK3188][HD] Malaysk ROMs Lollipop 5.1.1 for any yet known MTCB-Device

[typos1]

Thanks again. It booted fine, but I didn't have any radio audio. I did a factory reset, and tried various radio selections in the factory settings, but couldn't get any audio.

Do you know the correct selections for radio in the US, and the procedure to get it working?

Did you use the "export" button before you updated ? It sounds like you didnt (export saves all your MCU settings and flashes them along with the MCU) your ll have to go into factory settings and reset everything, if you didnt note what radio tuner you had before you updated you ll have to go through each one til you find one that works (after settings radio area to "USA".

 

[undrwater]

Did you use the "export" button before you updated ? It sounds like you didnt (export saves all your MCU settings and flashes them along with the MCU) your ll have to go into factory settings and reset everything, if you didnt note what radio tuner you had before you updated you ll have to go through each one til you find one that works (after settings radio area to "USA".

I reverted to 2.78, got the radio working, went back into factory settings, and hit export. Wipe / Flashed the mcu you provided, it read the mcu.cfg, but no radio regardless of selection (including the one that worked for 2.78). I reverted back to 2.78 again, and was listening to radio.

I can only conclude that some of the later versions of mcu are not compatible with the early units.

Thanks!

 

[typos1]

I reverted to 2.78, got the radio working, went back into factory settings, and hit export. Wipe / Flashed the mcu you provided, it read the mcu.cfg, but no radio regardless of selection (including the one that worked for 2.78). I reverted back to 2.78 again, and was listening to radio.

I can only conclude that some of the later versions of mcu are not compatible with the early units.

Thanks!

So far only some KLD and KLD2 users and all KLD5 users have not been able to upgrade to MTCC with everything functioning, you must be one of the few, unfortunately . . . actually, did you try the others I suggested ? Theyre on the HuieFei server in my signature, they may work.

 

[undrwater]

So far only some KLD and KLD2 users and all KLD5 users have not been able to upgrade to MTCC with everything functioning, you must be one of the few, unfortunately . . . actually, did you try the others I suggested ? Theyre on the HuieFei server in my signature, they may work.

That server is where I got 2.78. I ran out of time to try another, but I will perhaps tomorrow. I finally got TiBu to run a full backup, so getting back up and running will be easier.

 

[typos1]

That server is where I got 2.78. I ran out of time to try another, but I will perhaps tomorrow. I finally got TiBu to run a full backup, so getting back up and running will be easier.

Sorry, but what has Titanium back up got to do with flashing the MCU ?

 

[undrwater]

Sorry, but what has Titanium back up got to do with flashing the MCU ?

Nothing, just typing aloud. Is it true that when flashing a new mcu, best practice is to factory reset?

 

[typos1]

Is it true that when flashing a new mcu, best practice is to factory reset?

Nope, not true at all.

 

[yakupA]

Hi Folks,

i've been attempted to flash Malaysk ROM on my NewsMy NU3001 (2GB version, Screen and android box are 2 separated components) which is supposed to be MTCB.
When i entered TWRP Recovery (in the car android box connected to Head Unit), it didn't propose to flash system partion but it proposed only boot and recovery partitions.
Therefore i've decided to do so with RKBatch Tool v1.8 with PC (android box connected to PC through USB <--->miniUSB), and device recognized...firmware uploaded...firmware checked....flash successful....so far so good.
In the procedure, it says that you need to wipe data and cache partitions....However, when i unplugged and re-plugged the usb cable from pc, the green light indicator switched ON showing the device is ON but no way of getting recogized by PC...So i thought plug-in it to the Head Unit in the car might show Recovery or any options....But Head Unit screen is black as well.
So, i end up by a Hard Bricked device !

I red the procedure of unbricking, bootable SD with stock firmware.... I think i'm gonna go for it but in the meantime if you have any suggestion it will be much appreciated.
So, owners of Newsmy NU3001, you're warned.

Thanks,

KR

 

[yakupA]

I followed the unbrick procedure but saddly nothing happened...the screen stays black.... I don' t know why we choose "Upgrade Firmware" instead of SD Boot option ....My SD does even not boo ... ANy help is much appreciated !

 

[typos1]

Hi Folks,

i've been attempted to flash Malaysk ROM on my NewsMy NU3001 (2GB version, Screen and android box are 2 separated components) which is supposed to be MTCB.
When i entered TWRP Recovery (in the car android box connected to Head Unit), it didn't propose to flash system partion but it proposed only boot and recovery partitions.
Therefore i've decided to do so with RKBatch Tool v1.8 with PC (android box connected to PC through USB <--->miniUSB), and device recognized...firmware uploaded...firmware checked....flash successful....so far so good.
In the procedure, it says that you need to wipe data and cache partitions....However, when i unplugged and re-plugged the usb cable from pc, the green light indicator switched ON showing the device is ON but no way of getting recogized by PC...So i thought plug-in it to the Head Unit in the car might show Recovery or any options....But Head Unit screen is black as well.
So, i end up by a Hard Bricked device !

I red the procedure of unbricking, bootable SD with stock firmware.... I think i'm gonna go for it but in the meantime if you have any suggestion it will be much appreciated.
So, owners of Newsmy NU3001, you're warned.

Thanks,

KR

I followed the unbrick procedure but saddly nothing happened...the screen stays black.... I don' t know why we choose "Upgrade Firmware" instead of SD Boot option ....My SD does even not boo ... ANy help is much appreciated !

Malaysk's ROM is ONLY compatible with MTCB/C units - your Newmay unit definitely is NOT "supposed to be MTCB" - its an ENTIRELY separate device and not compatible in ANY WAY.

So flashing Malaysk's ROM on your entirely different unit will never work, lets hope you havent killed your it completely.

As it is not an MTCB/C unit for help with unbricking it you need the Newsmy NU3001 forum, not this one.

I dont think NU3001 owners need warning that they should not flash software from a totally different device onto their Newsmy - most of them will know that already.

 

[GranRamgo]

¿Does anyone have a blueToothManager.apk that works on Android 5.1 with the BC5M model of the MTCB-KB 2.81 MCU?

 

[Xenomorphys]

Hello, first of all, thank you for your ROM. It's great to have Android Lollipop on my car and the improvements are great!
I write you because I have some problems.
First, my radio car is extremely slow. Yet it worked perfectly before ...
Then, my recovery (recovery stock) is in KitKat, is this normal?
I must:
FullWipe in recovery
Install your Update with clean all
reboot
and it's good?
And finally, is it normal that the boot screen does not take all the screen and it is also slow to start? it is not practical ...
(besides, I will have to change the bootscreen, I find it not top on my e46 xD)

 

[typos1]

Hello, first of all, thank you for your ROM. It's great to have Android Lollipop on my car and the improvements are great!
I write you because I have some problems.
First, my radio car is extremely slow. Yet it worked perfectly before ...
Then, my recovery (recovery stock) is in KitKat, is this normal?
I must:
FullWipe in recovery
Install your Update with clean all
reboot
and it's good?
And finally, is it normal that the boot screen does not take all the screen and it is also slow to start? it is not practical ...
(besides, I will have to change the bootscreen, I find it not top on my e46 xD)

Lollipop is slower than KK because of the way it works and because these units only have 1Gb of RAM, the way round it is to use a ROM with microG apps, like @dsa8310's and @Johny DJ's version of it.

Recovery is KK because most devs feel that the L recovery is not very good.

Not sure what you mean about the boot logo, a picture would help.

 

[thivamero]

Hello,
I use malaysk music player that I find very nice, but I have a problem:
at the first use everything was fine but now the titles are poorly displayed when there are accents
when there is the letter "é" in a title it shows me "ñ", with "ê" it displays "k" .. someone would have a solution to this problem, I emptied the cache, erased the data but the problem persists ??
thank you in advance

 

[klain13]

Hello everyone and thanks for this latest update of the rom, excellent fluency and especially more complete than before [emoji6][emoji106]

 

[thivamero]

Hello,
I use malaysk music player that I find very nice, but I have a problem:
at the first use everything was fine but now the titles are poorly displayed when there are accents
when there is the letter "é" in a title it shows me "ñ", with "ê" it displays "k" .. someone would have a solution to this problem, I emptied the cache, erased the data but the problem persists ??
thank you in advance

hello
I found where the problem comes from.
My problem appears when I activate the xposed mtcmusic module.
When disabled, I have the titles that display correctly even with the special characters, but when I activate it the characters are not taken ( the letter "é" in a title it shows me "ñ", with "ê" it displays "k" .. ) can you help me please.

 

[thintin]

I want to make sure that I'm doing a completely clean install with nothing that could interfere in any way (just to rule out install errors as I'm trying to fix my broken install of this ROM). Does the 'flash ROM and clear all' option followed by the 'format data' option in the recovery completely replace everything except the recovery?

Thanks.

 

[lineyho]

I have and Eonon S07 MTCB KLD2-V2.77 RK3188 800x400 1GB Ram I was Running one of Malaysk's 2016 Versions of KitKat 4.4.4 with no problems. I decided to flash the Feb 2017 4.4.4 version of Malaysk's . The firmware install went fine. I was in the settings and did something to make the screen go dark. The unit would not display anything on the screen, even in recovery. I knew I was in recovery because the lights on the unit flashed. It took me a very long time but I was able to flash the OEM rom back to original by just guessing what was on the screen, knowing what the menu's choices are in recovery and pressing buttons until something happened. Again I flashed the Feb 2017 Malaysk's rom and it loaded properly. This time I had activated Xposed and was reviewing all the icons. I pressed the MTC-Volune App and the screen went dark again just like before. Black screen in recovery. Again I was able to flash another ROM. This time I tried Malaysk's newest version of 5.1.1. It flashed correctly. Two things happened. When I turned the headlights on the screen goes dark then comes back if I turn off the lights. Bizarre. Did not have this before. Some of the previous settings under "Display" in the 4.4.4 version are gone that had fixed the headlight issue previously. There was an " auto Brightness or dimmer" menu that I had set to off and that had fixed this issue. That choice is gone. Now there is a day & night brightness setting. The day is on full and the night is all the way off. The software will not apply the night setting if I try to increase it. While I was playing with the day setting, I turned it down the brightness all the way and accidently took my finger off the slider causing the display to go dark. One again the display is black in all modes including recovery and no way that I know of to get the display functioning again except to reflash again by the recovery guessing mode I have been using. This takes so much time and trial and error. Does anyone has some advice regarding my screen issue and why it is happening ? How to get the display back without a complete reflashing of the firmware ? Very frustrating........

 

[typos1]

I have and Eonon S07 MTCB KLD2-V2.77 RK3188 800x400 1GB Ram I was Running one of Malaysk's 2016 Versions of KitKat 4.4.4 with no problems. I decided to flash the Feb 2017 4.4.4 version of Malaysk's . The firmware install went fine. I was in the settings and did something to make the screen go dark. The unit would not display anything on the screen, even in recovery. I knew I was in recovery because the lights on the unit flashed. It took me a very long time but I was able to flash the OEM rom back to original by just guessing what was on the screen, knowing what the menu's choices are in recovery and pressing buttons until something happened. Again I flashed the Feb 2017 Malaysk's rom and it loaded properly. This time I had activated Xposed and was reviewing all the icons. I pressed the MTC-Volune App and the screen went dark again just like before. Black screen in recovery. Again I was able to flash another ROM. This time I tried Malaysk's newest version of 5.1.1. It flashed correctly. Two things happened. When I turned the headlights on the screen goes dark then comes back if I turn off the lights. Bizarre. Did not have this before. Some of the previous settings under "Display" in the 4.4.4 version are gone that had fixed the headlight issue previously. There was an " auto Brightness or dimmer" menu that I had set to off and that had fixed this issue. That choice is gone. Now there is a day & night brightness setting. The day is on full and the night is all the way off. The software will not apply the night setting if I try to increase it. While I was playing with the day setting, I turned it down the brightness all the way and accidently took my finger off the slider causing the display to go dark. One again the display is black in all modes including recovery and no way that I know of to get the display functioning again except to reflash again by the recovery guessing mode I have been using. This takes so much time and trial and error. Does anyone has some advice regarding my screen issue and why it is happening ? How to get the display back without a complete reflashing of the firmware ? Very frustrating........

Try updating your MCU to a KLD MTCC MCU (on the fileserver in my signature) and see if that sorts your problem. BTW you have a Klyde head unit, Eonon is just a seller.

 

[lineyho]

Try updating your MCU to a KLD MTCC MCU (on the fileserver in my signature) and see if that sorts your problem. BTW you have a Klyde head unit, Eonon is just a seller.

Thank you for your reply. So I see 4 or 5 Klyde MTCC - MCU files on the server. How do I know which one to pic ? My other question is do I need to reflash both the image file and the MCU file, or is there a way to just update the MCU ? By the way, I used my blind recovery method and put 4.4.4 back on the unit, however I want to still pursue 5.1.1 Malaysk. I'm not sure I understand why the "Display" choices and headlight issue change when upgrading to 5.1.1. I can't be the only person who has encounter this, but I can't find any post from members who have the same issue.