I need some help here... I probably in error, attempted to install 1 of the Android 9 mods, the MALAYSK, and now I have zilch... The mod would not install, I can force the unit into the recovery screen, but I have nothing to go back to and can not go forward as to installing the 9 version... Does someone have the actual firmware that I could reinstall? What ids the actual MCU for the unit? I put the MTCE_KGL 3.10 on it and I am not sure if that will work...
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.
It’s been about a week and half and I haven’t been able to get my radio back up and working, I have an Android Unbranded head unit running 4.2.2. I tried to post a picture of my info from my settings screen but couldn’t get the url link to go thru. But it pretty much looks like this: CPU INFORMATION
CORTEX-A9 DUAL CORE
RAM INFORMATION
DDR3 1 GB
ANDROID VERISON
4.2.2
MCU VERISON:
4.3.16-7-01-650201-151022
SYSTEM VERSION:
2.9.4_20150316
I installed what I thought was the right update but I may have gotten the files mixed up and updated the wrong file via my mini SD card and now it’s stuck on the opening screen which is the Chevy logo and won’t go any further, PLEASE help me unbrick my radio so I can get my tunes back, haven’t had any music in my truck for over a week now and I’m going crazy!
Find the correct factory firmware and flash it through the factory recovery.. or try flashing one of the custom rom. 4.2.2 version.
Mtcb firmware is what you need.
Nsx93 said:
Find the correct factory firmware and flash it through the factory recovery.. or try flashing one of the custom rom. 4.2.2 version.
Mtcb firmware is what you need.
Click to expand...
Click to collapse
Ok I’ll do that but My head unit doesn’t have any physical buttons just a reset button and I’ve tried to get it into recovery mode so many times and I can’t seem to do it, I e tried every combination of buttons and nothing’s worked...any suggestions?
Nsx93 said:
Find the correct factory firmware and flash it through the factory recovery.. or try flashing one of the custom rom. 4.2.2 version.
Mtcb firmware is what you need.
Click to expand...
Click to collapse
Still can’t get my head unit to read anything, I uploaded the right firmware to my SD card and it’s still stuck on the opening screen, and still can’t get it to go into recovery mode... I feel like I’ve tired everything and NOTHINGS working, I’m about to throw in the towel....ANYONE HAVE ANY SUGGESTIONS OR SHOULD I TAKE A LOST N BUY A NEW DECK?
graverober138 said:
Still can’t get my head unit to read anything, I uploaded the right firmware to my SD card and it’s still stuck on the opening screen, and still can’t get it to go into recovery mode... I feel like I’ve tired everything and NOTHINGS working, I’m about to throw in the towel....ANYONE HAVE ANY SUGGESTIONS OR SHOULD I TAKE A LOST N BUY A NEW DECK?
Click to expand...
Click to collapse
from what I understand, you can use Phoenixcard, and flash an image to a USB or SD card. Then insert into the GPS or USB cable, power on the unit, and allow it to boot from that to correct a incorrect flash....just what I have been reading. I would start along those lines....I am in the same boat, but I don't have my original firmware to test
Att: Still nothing....someone w/ experience
My head unit is still stuck on the opening screen, I’ve downloaded so many different file and tried soooo many techniques that I’m seriously beat, I’ve never had a device that I couldn’t figure out, especially after almost a month of reading and tried different approaches. So if someone could take a look at my Info in the opening forum and give me some tips or advice I’d REALLY APPRECIATE!!!!
Still bricked and haven’t had music in car in over a month...
Ive tried everything and havent gotten anywhere so
im about to throw this radio into the trash if no one
else has any othetr suggestions ....
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.
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?
I know, the unit model is a mess...
My screen barely shows anything because of a messy MCU flash.
I could go blind, but I would need someone to film them going to recovery and showing me how it looks.
I also flashed the android 9 custom ROM from Hal9k and am rooted, it case it changes something