I bought a Pumpkin 10.1 inch head unit about 6 months ago, I have enjoyed the head unit but would like to alter the firmware to one called "Malaysk" that a friend uses which I think looks better and has more functionality.
I have contacted Pumpkin who have said that unless something is wrong with the head unit they wouldn't advise updating it. After e-mailing back and forth, I was able to get them to tell me how do get my head unit into recovery mode (searching on Google did not help as there are no physical buttons I was not able to use other methods).
What Pumpkin instructed me to do did not work, so a friend was able to find a method using an app called "terminal emulator". We were able to get the head unit to boot into the recovery menu.
Unfortunately when I try to run MCU update using an dmcu.img file (dmcu(MTCE-KLD-2.94es_by_cs-x)), it just aborts and fails, I have also tried to run the "Malaysk" nupdate.img, which also fails.
Does anyone have any experience with the MCU or firmwares failing to install and aborting? and if so, how did you over come it?
My head unit is:
Pumpkin 10.1 inch
PX3
Android 7.1.2
Current MCU version - MTCE_KLD_V2.80_1
Thanks for any ideas / solutions.
Related
Thought i'd post my experience after a few days of pain in order that it might help someone else. XDA forum was complex in info but couldn't have been more valuable. I'll reference helpful posts below.
Car:Kia Sorento 2010
Head Unit: Pumpkin Android CN10
Android version: 6.01
Processor: quadcore-R16
Model / SKU: CN10-02201b-02A
Model is no longer available on amazon.
After a few weeks of use all the apps stopped launching and just returned to the home screen. Radio (UK) was dropping out every 30 seconds. The time never stayed set and changing it seems to have a bug that affects the system. Thats as much as I got from pumpkin forums. The weird thing was that there was no MCU info on the about screen.
So contacted Pumpkin who provided firmware updates. I would have thought it possible for manufacturers to track products, hardware and firmwares in a version control system but they insist on email 1-1 with firmware upgrades as solutions- but that's another story.
First round of firmware seemed to have bricked it - it was stuck in a boot loop or not booting at all. 3-4 firmware updates via some frosty email exchanges and its still stuck on boot with android logo.
Thats taken 7 days. Ouch
Then managed to find this thread https://forum.xda-developers.com/android-auto/android-head-units/allwinner-r16-astard7-android-6-0-1-t3523906
Since it mentioned the 'Allwinner quad core R16' i assumed it was relevant to this unit due to the chip info above. Since the unit was going back for a refund i didn't worry too much about screwing it up further.
So i took the rar file link from here:
KED1 (MEDEKE?) firmware (thanks):
V7.3.1_20170720.152039_KED1
"V7.3.2_20170826.102252_KED1.rar"
unpacked it on to sdcard:
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
827ba428-9b57-11e6-8dfb-37398ea70e52.2
Instead of doing what pumpkin said installing one file at a time on sdcard i put them all on root of card altogether and ran the upgrade. To my surprise everything installed OK. Rebooted and its working.
I'm pretty sure Pumpkin have no idea what they are doing with firmware as their forum seems littered with apologies for wrong firmware. Maybe they do . Luckily i have flashed a few roms and persevered with some success. The interface is different from factory settings but I now have a fully functioning radio , bluetooth, and installable sat nav app (map.me).
Some questions lingering in my mind.
1. Is this a eonon base unit?
2. Is there any core factory reset available?
3. Should i try and update the MCU to a newer version as listed in the post above?
4. How can I make a back up of my working settings?
5. Can i get any other GUI updates?
Hope this helps someone else with a CN10 R16 unit
Thanks for all the hardwork mods and devs do thru this forum too.
Bought a joying headunit off ebay about a year ago and have been pretty happy with it with the exception of no sleep mode and some minor glitches so I decided to check with joying to see if there were any updates which might fix my issues. Based on photos I sent them they sent me a new MCU file and a new OS file. I had trouble getting the MCU update to start but after popping the SD card in and out a few times it finally started and successfully installed. I ran in to the same issues with the OS file but never could get it to load so I watched their video and went through settings and manually started the OS update. During the update the installation ran in to the error installing the demo file and now all the unit will do is boot up and say "Joying" and then the screen will go black and it will repeat about once every minute. Since I didn't purchase the head unit directly from Joying they say it's not worth shipping back to them and paying for repairs. I've read up on this forum and on the web and tried to get the head unit to go in to recovery mode but have not been able to get anything to work.
Things I've tried so far:
-load OS on to SD card/usb and then reboot, tried in both usb slots and both SD card slots
-use a USB keyboard hitting CTRL+PRT SCR+ E OR I
-push the reset button 3 times
-push and hold the reset button until the lights flash pink and then push it 2 more times
Head unit stats:
Model JY-UO135N4PX5S
MCU version TP6735D 0.39 successfully upgraded to TP6735Dv0.43 using the file in this link drive.google.com/file/d/1OhElZ2d7iI5Lmh9leptIubOzhyoThfPK/view
Android version 8.1.0 prior to upgrade attempt using this file drive.google.com/file/d/1Nj6dpEFgyyXydeS91A0VbdKMPYpARw7d/view
Android security patch level October 5, 2017
Kernel version 4.4.103
Build number OPR5.170623.007 release keys-V4.5
Processor 8 core 64bit CPU [email protected]
Memory 4GB
Resolution 1024x600
From reading here and on the web I am pretty certain this is a QD head unit since it does not have a sleep mode. If anyone has any suggestions on how I might be able to repair this head unit please let me know.
Thanks!
AznDrgn2020 said:
From reading here and on the web I am pretty certain this is a QD head unit since it does not have a sleep mode. If anyone has any suggestions on how I might be able to repair this head unit please let me know.
Click to expand...
Click to collapse
Yes, that's indeed a QD unit.
In this case it is best contact Joying directly: [email protected]
surfer63 said:
Yes, that's indeed a QD unit.
In this case it is best contact Joying directly: [email protected]
Click to expand...
Click to collapse
Yeah unfortunately since I didn't buy it directly from them they have said the only thing I can do is ship it to them and pay the repair fee and pay for return shipping which is cost prohibitive. Figured I would try you guys before I throw in the towel and just junk it.
Hi guys please advice me what I should do.. my brother have Nissan maxima 2016 in the car he has android car unit, we do not know if this is the original head unit, but the system is old and very very slow, we tried to reset factory default but the system still stuck and slow, the only options for me are trying to upgrade for 3Party Android system or original rooted system, I am trying to find a system with the details I took from the system info but still can't find anything regarding that if someone can help me with that ill be very very thankful for that
https://ibb.co/vBknbWc
https://ibb.co/16427Qz
Hi,
I have a Vanku headunit that is stuck in a bootloop, stuck at Android logo. I bought the unit in November, installed it and it never fastbooted, the wiring is correct, I checked it multiple times. The manufacturer sent me a firmware update, followed their instructions for installing which led to the problem. I asked how to get it in to recovery mode, they suggested it needs a new android board. Here is the info for my unit, hopefully someone can help with getting this thing into recovery mode.
PX30
rk3326_nid-userdebug10 QQ2A.200305.004.A1 eng.hct2.20200810.184222 test-keys
Kernel version
4.19.111+
MCU version
MTCE_HT_V3.60_4
dink0617 said:
Hi,
I have a Vanku headunit that is stuck in a bootloop, stuck at Android logo. I bought the unit in November, installed it and it never fastbooted, the wiring is correct, I checked it multiple times. The manufacturer sent me a firmware update, followed their instructions for installing which led to the problem. I asked how to get it in to recovery mode, they suggested it needs a new android board. Here is the info for my unit, hopefully someone can help with getting this thing into recovery mode.
PX30
rk3326_nid-userdebug10 QQ2A.200305.004.A1 eng.hct2.20200810.184222 test-keys
Kernel version
4.19.111+
MCU version
MTCE_HT_V3.60_4
Click to expand...
Click to collapse
hey, can you post the firmware?
Hello, I hope you can help me,
My unit has always had auto touches, it clicks, mutes, exits apps and enters others by itself, it's very annoying.
I did a hard reset, but although it became more fluid, the wifi was damaged and does not turn on.
It is a K2001n, with android 10.1 fake, I would like to change the firmware and have a stable and more efficient one than this.
Can someone give me some recommendation?
Compare with this
Allwinner t3-k2001-nwd
Hi, I am the proud owner of an allwinner Radio. Does anyone know the password for system update? "0000" and "1234" won`t do ... Is there any chance to root it? I hope that is useful: Android 7.1.1 / SDK 25 (Nougat) MCU VER...
forum.xda-developers.com