From February 29, 2016 - https://mega.nz/#!d1IUgLLD!Ehyxraj5wQuFo3kLCq2a2HoKHl87yyy6eZjk82P6EXE
On March 3, 2016 - https://mega.nz/#!o4Yy1ZIA!IYv9As4_lxPxM2dYAyD2G9OG4rOHTWyfxJr_8NKtHZA
From March 30, 2016 - https://mega.nz/#!ApRx3DrJ!nE-YJYqJuFHENVl8LSzB9VesGhkImO9wSJYYZ2o3Yhg
From April 28th, 2016 - KD - https://mega.nz/#!ZtpyVSqb!r5XhoMLEjKC_qHrVpXpK6LUJWPM0Et4eEmmf-vmxAoI
From April 29th, 2016 - KD - https://mega.nz/#!stB2lBRB!PpbVI4-IgX6cRIDd_UXWQ91xjs6W5oZ_pe4gPH0Erb8
On May 4, 2016 - KD - https://mega.nz/#!UoQDlSqL!YO2qimQXxxsGHg_spUoIG-38uhBJ4rvjMxvPK2e2iCo
Please, if you have sellers sent firmware, put it here !!
Joying MTCD android lollipop firmware MCU and ROM:
https://www.carjoying.com/Joying-blog/42.html
August 10 mtcD Joying
https://drive.google.com/file/d/0BwwSNuJlVkAZZ21hcXFnLWk0dlE/view
----
JOYING mtcD
Jun 21 2016
dmcu
https://mega.nz/#!9w5nyZ6K!Xjk2hheDq-B8IP3xriHiqMBjLUyXfOlxQy_Qf1YYAd8
ROM mtcD
https://mega.nz/#!dwJVzIgb!bHhsDLkQQf0Hp0sKuOqtXh3IWxlLCZwgabQ1f5K1UuU
MCU version：
MTCD_JY_V1.63_2
Jun 12 2016 10:48:32
Android version：
5.1.1
Kernel version：
3.0.101+
[email protected] #38
Mon Jun 13 17:39:59 CST 2016
Build number：
rk3188-userdebug 17062016.14:58:40
==================
dMCU https://mega.nz/#!R5QGFAgS!6SzIIdkxX194wIHhkyJZ3SCZ-11DiFRdnOTeu4q_y2k
ROM : https://mega.nz/#!JsIDkYAQ!5yAF3keXv4f66ZG2hWjMQVtUdjX9kGwSlSQWDxwO7mc
April 30 2016 ROM and dMCU
MCU version：
MTCD_JY_V1.49_2
Apr 28 2016 09:54:26
Android version：
5.1.1
Kernel version：
3.0.101+
[email protected] #35
Fri Apr 29 13:12:26 CST 2016
Build number：
rk3188-userdebug 29042016.14:11:54
===========
https://mega.nz/#!MhwiSaZb!KZho1jz8hgn1vGqqQ6QSjpVW9TjFFDvlE891xD0mNFs
https://mega.nz/#!dtQQyRjK!GjWNKtoQBcldpXIGdbQarS8HHdrxdK8PwDIXe5tNIwc
Do not install on Non Joying Headunit.
MCU version：
MTCD_JY_V1.28_2
Mar 7 2016
Android version： 5.1.1
Kernel version：3.0.101+
Mar 11 2016
Build number：
rk3188-userdebug 19032016.11:29:20
Do you have a later firmware with bug fixes? I have 28032016.11:22:37 but have a few bugs.
Redline10000 said:
Do you have a later firmware with bug fixes? I have 28032016.11:22:37 but have a few bugs.
Click to expand...
Click to collapse
it will be posted when released
Redline10000 said:
Do you have a later firmware with bug fixes? I have 28032016.11:22:37 but have a few bugs.
Click to expand...
Click to collapse
Official JY lollipop upgrade page link: https://www.carjoying.com/Joyincg-blog/41.html
popeye70 said:
Official JY lollipop upgrade page link: https://www.carjoying.com/Joyincg-blog/41.html
Click to expand...
Click to collapse
Thanks! I will give this a shot now.
i just made a 2nd $20 donation towards the 5.1.1 ROM. $40 total. Come on people, DONATE!
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
The update link is bad, it is https://www.carjoying.com/Joying-blog/41.html
FYI, the April 28th "UI Update" brings the ROM version up to 18042016.19:43:10 and from what I can tell there is no newer DMCU update newer than the one posted March 7th.
http://forum.carjoying.com/thread-16-post-278.html#pid278
Don't do this update. If you minimize the radio app it quits and the radio widget does not work. Also the app for steering wheel control is missing .
Redline10000 said:
Don't do this update. If you minimize the radio app it quits and the radio widget does not work. Also the app for steering wheel control is missing .
Click to expand...
Click to collapse
This is not completely correct. If you hit BACK the radio app closes, if you hit HOME it minimizes and runs in the background, this behaviour is unchanged from the March 28th build. The radio widget does not work for me either, that is true. The app for steering wheel control is not missing on mine. It is called "Wheel Key Study" and if you cant find it in the app drawer, just go to the Android settings screen and its there as well near the other driving menus.
Ah I managed to fix the radio issue. It was a problem with my radio key mappings. However I still can't find "wheel key study". I might need to reflash.
Sent from my Nexus 6P using XDA-Developers mobile app
Added firmware of 28 April 2016 - KD
Added firmware of 29 April 2016 - KD
Does the wheel key app do anything for you guys?
@Malaysk does the model number or the car the unit is made for matter when installing new Roms or firmware? For example will the firmware for a erisin generic double din unit work for the erisin bmw e46 es 3062 unit?
Do I need to rename the files to dupdate.img and dmcu.img ?
Sent from my SM-N920C using Tapatalk
elhamy said:
Do I need to rename the files to dupdate.img and dmcu.img ?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
No they will be detected properly as is. What I did notice however is that if you have both files in the same directory when you check for updates it will always only pick up the MCU file first. So what I had to do was move the MCU image out of the directory after it was updated so that it would see the ROM dupdate image and offer to upgrade that.
hadeone said:
Does the wheel key app do anything for you guys?
@Malaysk does the model number or the car the unit is made for matter when installing new Roms or firmware? For example will the firmware for a erisin generic double din unit work for the erisin bmw e46 es 3062 unit?
Click to expand...
Click to collapse
No my wheel keys work on stock app only. Are you using a canbus box? I read you on VW and BMW the wheel buttons can not be remapped...someone correct me if I am wrong.
sterod said:
No they will be detected properly as is. What I did notice however is that if you have both files in the same directory when you check for updates it will always only pick up the MCU file first. So what I had to do was move the MCU image out of the directory after it was updated so that it would see the ROM dupdate image and offer to upgrade that.
Click to expand...
Click to collapse
Thanks for your reply , let me confirm that I understood correctly, first time to update these devices
I will keep the files names update.img and mcu.img
And will keep mcu.img in the root directory to be updated first then I replace it with update.img to be updated after
Please correct if I'm wrong, thanks again
Sent from my SM-N920C using XDA-Developers mobile app
elhamy said:
Thanks for your reply , let me confirm that I understood correctly, first time to update these devices
I will keep the files names update.img and mcu.img
And will keep update.img in the root directory to be updates first then I replace it with mcu.img to be updated after
Please correct if I'm wrong, thanks again
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
I think you meant keep the filenames dmcu.img and dupdate.img
I typically do the dmcu.img first then when that is done, I move the dmcu.img file out of the root folder and place the dupdate.img inside.
I don't know if the order of flashing is relevant, but this is how I've done it and have not had an issue.
I wanna live wallpaper from factoryROM...
Added firmware on May 4, 2016 - KD
Malaysk said:
Added firmware on May 4, 2016 - KD
Click to expand...
Click to collapse
Thanks a lot what's the version of this update ?
Sent from my SM-N920C using XDA-Developers mobile app
Related
Does anyone know who makes the LM MCU units? My Erisin is an LM, but it appears to be less supported with regards to MCU and firmware updates compared to other "brands". I've got 1.63_1 MCU. Any newer?
edit
If you browse the forum you will find v1.82 for these units, but this version makes unable to eject cd unit as in my case, so I don't recomend you to update. Surely that version is for another unit, not mine: es3015
By the way.... does any body have MCU v1.63 firmware ready to install? I would like to eject my CD from the unit...
version 1.90 for LM units
http://forum.xda-developers.com/showpost.php?p=69756399&postcount=402
It seems to be a complete system update, not only the MCU firmware update. That update has 800MB, not the few MB that the MCU firmware updates used to have.
---------- Post added at 12:37 AM ---------- Previous post was at 12:03 AM ----------
In this post you will find the MCU update 1.90 for erisin units:
http://forum.xda-developers.com/showpost.php?p=69926813&postcount=84
i�am on Malaysk.
Possible to update mcu only?
Is it correct to flash these three files from sd/usb?
Done and working faster and more stable than before.
makes2068 said:
Done and working faster and more stable than before.
Click to expand...
Click to collapse
i will try mcu 1.90 with latest malaysk rom too. if update works in your 3015, i supposed it will work on mine
It will definitely work.
Only station presets are gone and the canbus setting. Personal Hardkey mapping too. But thats done in minutes.
Maybe you should look for it before the update and reset it after.
Does this work on all Erisin LM Units?
A stupid question but how can I see if my unit is LM, if I have already updated it with another MCU ?
Settings - about unit - version
Getapped and getalked with 6603
Greetings!
This is the official link of the update zip file straight from Google/HMD's servers :
Official Oct. 2017 Update ZIP (664MB)
Additional Info
Android Version : 7.1.2
Build Number : 00WW_3_700
Linux Kernel Version : 3.18.31_perf
Patch Level : October 1, 2017
Don't use ADB Sideload, put it in a SD card and update it from there by going to "Recovery Mode > update from sd card".
Update only if you already have the September 2017 update installed. This is not guaranteed to run on older updates. Also, this is only tested for Southeast Asian region. probably it might work on other regions but don't take my word on it.
DISCLAIMER : I'm not responsible in case you brick your phone by doing this procedure. This device doesn't have so much support from here yet so tread the waters carefully.
Thanks. Can you see any other nokia 6 models on the download servers? ie TA-1033
Unfortunately I can't since i don't own those variants
Thanks a lot for sharing! Android 7.1.2? Which build number precisely?
Thanks for the reminder! I updated the post!
i update my nokia alrdy , feels a bit lag when i scrolling up to open the menu . feels bad . its kinda freezing for awhile . i tryng restarting and deleting some cache using ccleaner also same . does anyone know what happen with this os ?
Hi bro are you have ta1021 this build number 00ww_3_700 full firmware version 7.1.1....?
Hey bro, do you have a link to Nov update for TA-1021?
qwertysmerty said:
Hey bro, do you have a link to Nov update for TA-1021?
Click to expand...
Click to collapse
Nevermind. Found a way how to get URLs. If someone is interested, this is the link to November 2017 OTA update for TA-1025,
_https://android.googleapis.com/packages/ota-api/nokia_ple_ta102500ww/d42ae64c084e5f25096aef085cb28f4ab6a01bc5.zip_
Android version: 7.1.2
Build number: 00WW_3_700_SP01
Linux kernel version: 3.18.31-perf
Patch level: 6 November 2017
qwertysmerty said:
Nevermind. Found a way how to get URLs.
Click to expand...
Click to collapse
Please share how?
Intercepted checkin request with mitmproxy, modified carrier MCC/MNC in the request's body, and replayed forged request. Better to use big European carriers like O2.
Another November update for Nokia-6. Build number bumped up though security patch level is the same 6 Nov 2017. Direct download link for TA-1021
https://android.googleapis.com/pack.../59350de39b10745525f69545efa7c60c1d73f9a2.zip
Android version: 7.1.2
Build number: 00WW_3_72A
Linux kernel version: 3.18.31-perf
Patch level: 6 November 2017
@Querty
That update broke the phone I will have to go to the service center again to get the software updated
Updates are not cumulative. You have to install one by one. 00WW_3_72A should be installed on top of 00WW_3_700_SP01 released in the beginning of Nov. What's your Nokia 6 model?
qwertysmerty said:
Another November update for Nokia-6. Build number bumped up though security patch level is the same 6 Nov 2017. Direct download link for TA-1021
Click to expand...
Click to collapse
Qwerty, can you please post ddl for the second Nov update for the TA-1025 model? :fingers-crossed:
DeathStar1982 said:
@Querty
That update broke the phone I will have to go to the service center again to get the software updated
Click to expand...
Click to collapse
Btw you can fix the phone yourself, just follow instructions in https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441. This topic contains links to OST tool and firmware images. Reflashing your phone will roll it back to Android 7.1.1 and June patch, after that you can download and install OTA updates one by one.
---------- Post added at 06:19 AM ---------- Previous post was at 05:37 AM ----------
c0ldzer0 said:
Qwerty, can you please post ddl for the second Nov update for the TA-1025 model? :fingers-crossed:
Click to expand...
Click to collapse
Sorry I've already updated my phone. Next time I'll get ddl for the both models. You can install TA-1021 update on TA-1025 and vice verse, they are compatible. I installed the latest TA-1021 on my TA-1025 because did not want to wait until it's approved for TA-1025.
Sweet as, thanks for the heads up @qwertysmerty
So good so far, TA-1021 update working on TA-1025 for the past 8 hours without problem. :victory:
I'm still in the patch of December 2018 I find something unfortunate, I think they do not have the desire to fix this failure of the ota's, so they take 3 devices if two can not update and I'm going g5, g6 and g7, just regrettable
GDATOS_MX said:
I'm still in the patch of December 2018 I find something unfortunate, I think they do not have the desire to fix this failure of the ota's, so they take 3 devices if two can not update and I'm going g5, g6 and g7, just regrettable
Click to expand...
Click to collapse
What is you software channel?
EmiAndroid said:
What is you software channel?
Click to expand...
Click to collapse
Is AMXMX
My G7 Power Update sticks also on December 2018.
Software channel RETEU2
People have complained about this to Motorola on Twitter but they ignore it and give nonsense form replies.
I'm also stuck on December 2018 patch for the xt1955-2...Retla version. Bought the phone on Amazon.
Sent from my moto g(7) power using Tapatalk
Same here.
Retla Software Channel.
Model: XT1955-2.
Build number: PPO29.80-27
Kernel version: 4.9.112-perf+ #1 Mon Dec 10 12:04:01 CST 2018
Security patch level: Dec 1 2018
I bought this phone on eBay with the understanding that it was compatible with AT&T / cricket wireless. The lack of LTE bands for these carriers has been difficult. I am hopeful that progress will be made on unlocking the needed bands!
jlsatt4 said:
Same here.
Retla Software Channel.
Model: XT1955-2.
Build number: PPO29.80-27
Kernel version: 4.9.112-perf+ #1 Mon Dec 10 12:04:01 CST 2018
Security patch level: Dec 1 2018
I bought this phone on eBay with the understanding that it was compatible with AT&T / cricket wireless. The lack of LTE bands for these carriers has been difficult. I am hopeful that progress will be made on unlocking the needed bands!
Click to expand...
Click to collapse
the only way I see is to flash a stock ROM more updated as the openmx that is 1 March 2019 is the most current I see
What about "retus"? I would guess that flashing a different stock ROM to this hardware will alter or prevent future OTA since it is rooted, etc?
jlsatt4 said:
What about "retus"? I would guess that flashing a different stock ROM to this hardware will alter or prevent future OTA since it is rooted, etc?
Click to expand...
Click to collapse
I did it and if the otes arrive I did it with a moto g 5 in its time and if it updates like any other since it is official it has nothing to do with the channel.
same for me, RETEU2 channel and still on december 2018 patch
im just waiting for a TWRP port at this point, im not expecting garbage Motorola to fix this
Is there a way to switch to a different update channel?
My phone stucks on RETEU2 channel, too.
hello ,
sorry to my english but i'm french .
i recently buy a head unit but some problems with GPS position and other i want to reinstall stock firmware but i don't know where to find it
modèle : PX30
SERIAL NUMBER : D33158C380F5709A
BUILD VERSION : rk3326_mid-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20201205.100632 test-keys
version noyau : 4.19.111+
version MCU : MTCE_CHS_V3.67_1
anyone can tell me where find firmware without mod just stock firmware to reinstall my head unit
glashow said:
hello ,
sorry to my english but i'm french .
i recently buy a head unit but some problems with GPS position and other i want to reinstall stock firmware but i don't know where to find it
modèle : PX30
SERIAL NUMBER : D33158C380F5709A
BUILD VERSION : rk3326_mid-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20201205.100632 test-keys
version noyau : 4.19.111+
version MCU : MTCE_CHS_V3.67_1
anyone can tell me where find firmware without mod just stock firmware to reinstall my head unit
Click to expand...
Click to collapse
Yandex
Finds everything
yadi.sk
sandpita said:
Yandex
Finds everything
yadi.sk
Click to expand...
Click to collapse
Thank you to ask me
but i don't see my version of mcu in "ROCKCHIP PX30 ANDROID 10 "
which folder should I choose ? idk...
glashow said:
Thank you to ask me
but i don't see my version of mcu in "ROCKCHIP PX30 ANDROID 10 "
which folder should I choose ? idk...
Click to expand...
Click to collapse
glashow said:
Thank you to ask me
but i don't see my version of mcu in "ROCKCHIP PX30 ANDROID 10 "
which folder should I choose ? idk...
Click to expand...
Click to collapse
stock firmware and MCU are totally two different things, which one are you after?
sandpita said:
stock firmware and MCU are totally two different things, which one are you after?
Click to expand...
Click to collapse
I just want to réinstall stock Android 10 on my px30 but I don't what I need to choose can you just telle which files I need to download I'm little lost about MCU and firmware..
Яндекс
Найдётся всё
docviewer.yandex.ru
Hello all
i need help with my A media Auto
MCU_Version: MTCD_LM_V1.63_1
Jun 12 2016
Android Version 5.1.1
Kernel-Version
3.0.101+
[email protected] #28
Wed Jun 22
Build-Nummer
rk3188_userdebug 24062016
Prozessor
ARM Cortex-A9 @1.6GHz (x4)
RAM
1024mb
i would like make update to android version 10 it is possible ?? and how i can make it ??
thanks all for help
Kakacs said:
Hello all
i need help with my A media Auto
MCU_Version: MTCD_LM_V1.63_1
Jun 12 2016
Android Version 5.1.1
Kernel-Version
3.0.101+
[email protected] #28
Wed Jun 22
Build-Nummer
rk3188_userdebug 24062016
Prozessor
ARM Cortex-A9 @1.6GHz (x4)
RAM
1024mb
i would like make update to android version 10 it is possible ?? and how i can make it ??
thanks all for help
Click to expand...
Click to collapse
I cant find any kind of updates for your model number, there is nothing for your device.
Droidriven said:
I cant find any kind of updates for your model number, there is nothing for your device.
Click to expand...
Click to collapse
He want's to upgrade, not to update.
@Kakacs
to upgrade from Android 5.1.1 to Android 10 you as 1st things of all things have to find a
1. Custom Recovery
2. Custom ROM
both suitable to your device.
jwoegerbauer said:
He want's to upgrade, not to update.
Click to expand...
Click to collapse
An upgrade is a type of update because it uses an updater process to install the upgrade. Some devices upgrade via OTA "update", which makes it an "update" and an "upgrade" at the same time. An upgrade is just a special type of update instead of a separate thing. Any software released for a device other than its initially installed or created software is an update, whether it be a full system upgrade or an incremental update.
Because I can see you - and OP - don't really know the difference between update & upgrade I'll explain it to you herewith:
A software update, also called a software patch sometimes, is an enhancement to the current version of the software or program. It provides fixes for features or adds minor improvements and compatibility.
A software upgrade is a whole new version of the software / application. It provides a significant change or large improvement based on the last version.
jwoegerbauer said:
@Kakacs
to upgrade from Android 5.1.1 to Android 10 you as 1st things of all things have to find a
1. Custom Recovery
Click to expand...
Click to collapse
Incorrect, a custom recovery is not needed and would prevent updating the MCU.
Flashing can be achieved by OTG, SDCard or third party app. OTG and SDcard are factory methods.
There are a great many posts about this suggest OP and jwoegerbauer takes a little more time reading the MTCD forums.
jwoegerbauer said:
2. Custom ROM
Click to expand...
Click to collapse
Incorrect, a custom ROM is not needed. There are no 'custom ROMs' only modified ROMs for these head units.
The factory ROM us sufficient.
OP what is your SOM and onboard RAM capacity. To upgrade you may need to replace the Coreboard with a new unit, even a PX6.
jwoegerbauer said:
both suitable to your device.
Click to expand...
Click to collapse