Related
***I have recently switched to the Nexus One but I will continue to do these Magic ports as long as there is a desire (and I have time).***
This is a thread for the port files required to use the 32B Cyanogenmod ROM on 32a/EBI1 phones. Please see the following link for details on the ROM:
http://forum.xda-developers.com/showthread.php?t=567610
Note: Rogers users - if you find yourself without data upon flashing this ROM, use the settings found here to restore your APN.
Credit Radix for the following instructions - they are copy/pasted from his thread. Also thanks to all of devs who have contributed to the ROM scene - impossible to mention all of you, specifically Amon_RA, stericson, prash, cyanogen, riku, Radix, koush, TigerTael, haykuro, pershoot, zinx and more I am forgetting I am sure.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
***Please note that the following steps require that you have a recovery with the option to flash any .zip file. I recommend Amon_RAs recovery, Clockwork Recovery, or ROM Manager
***
NOTE: All new ports will be based on Koush's Universal update.zip. This lets you flash just a kernel and matching libs to a phone without the need for a ramdisk. Basically, it takes the ramdisk currently installed and repacks with it the new kernel.
Basically, the port packages provided from now on will port ANY ROM from 32B --> 32A/EBI1.
CM5.x (Eclair base)
Upgrade from 4.2.x Cyanogenmod ROM
http://wiki.cyanogenmod.com/index.p...or_other_rooted_ROMS_to_5.0.x(Dream/Sapphire))
Gapps Mirror: http://briancrook.ca/android/gapps/gapps-ds-ERE36B-signed.zip
CM4.2.x (Donut Base)
NEW INSTALL (ie. never installed CM 4.1.99 or greater before):
Magic Users
Rogers Dream EBI1 Users
UPGRADE INSTALL (ie. already installed 4.1.99 or greater):
Cyanogenmod Wiki
ROM Manager
1. Download ROM Manager from the market
2. Flash the ClockWork Recovery
3. Go to Download ROM > CyanogenMOD > Choose the version you want to flash.
4. Select Gapps addon (if you want Google Apps)
5. This will reboot to recovery, make a backup if requested, flash all the components and reboot.
6. Win.
Theme Support
Themes CAN be applied overtop of this ROM/Port combo. Just make sure to reboot in between the Defanged Base/update-cm-/port file step and pick a theme that corresponds to the Cyanogenmod version you are running. Keep in mind that some themes include a boot.img (no idea why...), so just keep an eye out. If you apply a theme with a 32B boot.img, just reapply the port file afterwards. If you apply a theme with a 32B boot.img, the phone will not boot past your carrier lockscreen...you can easily restart and reflash the port file. Always backup before flashing anything!!
==================================================================================================
If you would like to donate, please use the following link. Any donations are greatly appreciated
==================================================================================================
Port Files:
CM-6.1.0
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-ebi1-signed.zip
md5sum
CM-6.1.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-RC1-ebi1-signed.zip
md5sum
ROM Manager Web Connect
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
CM-6.0.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.0.0-RC1-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-5.0.8
Download: http://briancrook.ca/android/cm-ports/bc-5.0.8-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-4.2.15.1
Download: http://briancrook.ca/android/cm-ports/bc-4.2.15.1-ebi1-signed.zip
md5sum
Iptables was left out by mistake. Tether issues should be gone.
For other port versions, go to: www.briancrook.ca/android/cm-ports/old
Thank you
cheer
Worked great, thanks a ton!
Does anyone else have signal problems with this rom?
I have had lost signal, many many times today
bunny0007 said:
Does anyone else have signal problems with this rom?
I have had lost signal, many many times today
Click to expand...
Click to collapse
no problem
very nice！
i like this rom, but now i cant have Google navigation
elite_is3 said:
i like this rom, but now i cant have Google navigation
Click to expand...
Click to collapse
did you have it before you did the new rom? i had to go to a like 4.2.4 or 4.2.3.1 and then download the gmaps off the market and then took it back to the 4.2.5. I havent did the 4.2.6
can this be installed using the one click method from the unlockr.com
i have the amon ra recovery
also im on a perfect spl - do i need to change that- rookie questions i know-
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
Do you mean the dialpad, that you drag up while on a call? it works for me.
KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
I can access it just fine. Have you tried doing a wipe?
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I cant confirm, I dont have the proper bluetooth stuff. have you checked the cyanogen bugtracker?
I have a few issues after updating from 4.2.5 without wiping.
1. GPS kept losing signal during navigation.
2. Lost three 888 xxxxxxx call receptions today.
3. My wife complained she heard horrible static noises each time when I changed locations. For example, when I moved from outside to inside my building or I stepped out of my truck.
4. I couldn't listen to my voicemail through GV. FC every time.
The rest work great. The rebooting time is super fast.
Thank you so much, guys.
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I believe I suffer from this issue as well, or at least something related. This was also happening on 4.2.5, but was perfect on my previous ROM, MyHero.
In my case I use a mini USB Y-Splitter adapter in the car: one end goes to the mini-USB cigarette lighter charger, the other to a 3.5mm jack for the AUX-IN in my car stereo. This way I can listen to Pandora or whatever over the stereo. If I answer a call in this setup the other party cannot hear me. Similarly I cannot speak any Google searches, or use Shazam, or anything that requires my microphone to work. I was hoping this release would fix it. Evidently not.
As stated, worked great with MyHero. *sigh*
No one else could confirm this as an issue before, so I thought I was alone... maybe still am...
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I listen to music in my car audio which is connected to my phone via BT (music from my phone). When someone calls i just pick up call and talk through built in car system. After the call, music just continues playing.
sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
they 'adapt' to the roms for which they are written, allowing 32a owners to flash 32b roms on their devices.
you dont really have a choice on which port file to install. there is only one (generally) for each version of a rom.
sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
Pick the one that corresponds to the version of CM you are running. Assuming you want to use the newest cm (version 4.2.6), use the 4.2.6 port file
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21
Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!
Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.
Reserved2
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!
jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.
Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!
shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.
silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Would you be open to posting your sources for these builds?
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol
jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk
silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM
Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z
Lollipop
piotr_waw said:
Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z
Click to expand...
Click to collapse
I have read that if you upgrade your android system to the newer version; something about the GPS maps will no longer work. Not sure but you might want to look for that.
I have the same system A-Media Auto, MTCD-KGL_v1.53a_1
I found a newer version KGL_10-20-2016_1.92a_4_dmcu.img but I can't get the Head to find the .img file
I tried the SD card in the slot, GPS slot and a USB cable. Still System Update cannot find the .img file. Frustrated I gave up.
I did find that the SYGIC maps works good with the unit. I didn't like the IGO that came with it and wiped the map SD.
I also loaded Car Launcher v2.4.074 which is more appealing.
The backup camera is kind of squirrelly, works when it wants to.
Thinking about getting a new head unit with a flat screen, no buttons and knobs, but not sure if I want to go with a name brand or pure android version.
Will try to insert an image of my unit but I am new at this. The image wants me to put in a http url
/home/pok1/Downloads/20190316_134105.jpg
Hi all you clever people
I just bought this unit, https://www.aliexpress.com/item/7-I...igation-Sat-Nav-Radio-Player/32772807019.html, and installed in my car.
I have set up a bluetooth connection with my phone and using a hotspot from the phone to give Internet access.
I have a lot of questions, and I have searched this site, but haven't really found clear answers.
First the facts. here are the data from my settings:
Model: px5(1024x600)
Android version: 8.0
Android security patch level: October 5. 2017
Kernel: 4.4.93+
[email protected] #336
px5-userdebug 8.0.0 OPR5.170623.007 eng.htc.20180804
MCU version: MTCE_MX_V2.92.1
Aug 21 2018 20:10:21
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Memory: 3891 MB
I know I'm asking a lot of questions, it's just a bit confusing to get started in this new world. I have numbered my questions, so it's easier to reference
1) I would like to get hands free phone calls and texting and navigation. I tried Android Auto, and that was very stable, but I couldn't get the phone to work. I assume thats because it's meant to be run on a phone and then mirrored to the head unit. Now I'm trying with Google Assistent, but it's not really stable. At first it worked pretty well, but now it just works as Google Now, so it won't make phone calls for instance. Any advice on what to choose, and how to get it to work?
2) I found this thread about a custom ROM, https://forum.xda-developers.com/an...t/rom-hal9k-rom-3-mtcd-e-head-units-t3847477/, my unit should be compatible for that, right?
3) As far as I understand, I can not go back to the stock ROM, if I install the new ROM. Then I should flash it with my old ROM. But how do I find out the name of my existing ROM? Is it risky to flash a new ROM, or will I always be able to flash back, if something goes wrong?
4) It's a requirement for the Hal9k ROM, that my MCU is upgraded to at least 2.93. I found this thread, https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155, but how do I find out if this MCU upgrade is compatible with my MCU?
5) Finally, I installed Tidal app, so I could download playlist for my head unit, but when I start the app and enter my credentials (and they are correct, because I get an error if I enter a wrong password) it just starts up with a black screen with a play icon in the middle, and previous and next symbols, but no menu, except for a hifi menu in the top left corner, where I can choose streaming quality. I will post a picture tomorrow. Does anyone know how to fix that?
Can someone please help me or at least point me in the right direction? I have spent multiple hours searching this site, but right now I'm a bit confused
Kind regards
Allan
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
millab said:
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
Click to expand...
Click to collapse
Thank you very much, it sound like it should be pretty safe to try the Hal9K ROM. I just have a couple of extra questions:
3a) My seller on AliExpress seems to have no clue, when I'm asking for stock ROM. But I should be able to find something close to my Stock ROM, if I don't succeed with Hal9K, right? Something like the Original Android 8.0 MX ROM mentioned in this thread: http://www.androidiani.com/forum/au...ndroid-rockchip-px5-2-4-gb-ram-32-gb-rom.html
4) I found this thread, https://forum.xda-developers.com/an...evelopment/update-media-auto-mtcd-mx-t3828177, with a link to yadi.sk, where I can find a MTCE_MX_V3.00.rar. That should be compatible with my device, right?
I hope you will bare with my ignorance, I'm really trying to get into this
Kr
Allan
Did you manage to get Tidal working ?
for Android Auto. I'm running the app called `Head Unit Reload` that would turn the Android system as host. essentially it's helper app for `DHU` (Desktop HeadUnit by Google for android auto debugging).
with HUR you can do either wireless Android Auto or USB tethered. This would handle SMS and phone call hands free.
I'm running Hal9K 3.1.1 ROM on my MCUE HK + Car launcher pro as launcher.
Hi
I have a Chinese Auto Media and need to update its firmware to something newer easily done.
Attached photos for my car media
Thanks in advance