[Q] 2DIN 'S07' Android 4.4 Using RK3066 - Root? - Android Head-Units

I recently bought a generic android head unit from Ali Express. It actually works well but I really need to connect it to a CAN bus and write some additional software (background: I want to replace the factory unit in a Nissan Leaf, so it needs to display some vehicle info, show the heater settings and set up the charge timer). I have experience in Android app development and embedded Linux, but I'm still a 'noob' when it comes to Android hacking (root access etc).
I'm pretty sure I will need root access to do what I want. It has 'CAN tx / rx' pins on the back, and I am pretty sure they are wired to one of the serial interfaces internally (I will need an adapter to convert UART to CAN as well). I played around with an app to access the serial ports (i.e. ttyxxx) but I didn't have permission to use many of them - probably the ones I wanted!
I don't want to re-write the existing music player, amp control and radio; I just want to add a new app to carry out my vehicle-specific functions.
I tried the root process given here but it didn't work.
Here are the device details:
Model: S07
MCU Version: MTCB-HA-V2.60
Android Version: 4.4.4_01062015
Kernel Version: 3.0.36+ [email protected] #278
CPU: ARM7 1.6G x 2
CPU/SOC is an RK3066 on a modular board. Pictures attached.
It doesn't have any physical buttons except reset - there are touch sensitive buttons for power, back and volume. It has one SD card slot for map data and no USB on the front (several on the back).
I haven't figured out how to get to the recovery console, or connect it to a PC via USB.
Any suggestions for how to root? Or get to recovery console?
Anyone else with a similar device?

Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work

Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
MayfairDROID said:
Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work
Click to expand...
Click to collapse

jcolebaker said:
Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
Click to expand...
Click to collapse
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.

MayfairDROID said:
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.
Click to expand...
Click to collapse
SUCCESS! I just downloaded and installed the latest image from Malaysk (I think?) and it looks like it is working well! Radio, music player and amplifier work, and I have root access. Woo! So far so good... Thanks!

Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank

aribetty7811 said:
Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank
Click to expand...
Click to collapse
Hi, I also didn't know the screen resolution, and it is not mentioned on the "About" screen.
In the settings menus, I found some options for recording a video of the display (I don't know why!) and the maximum resolution there was 1024 x 600. I figured that you wouldn't bother to record at higher res than the screen had, so the resolution must be 1024x600. This seemed to work!
My stereo has absolutely NO branding on it anywhere so I don't know whether it's a clone of Huifei or something else, but it worked with the "Malaysk" firmware, which I downloaded from the Huifie file repository (linked from here), under firmware->Malaysk ROM->Malaysk DualCore RK3066).
I picked the bottom one (12th Jun 15, 1024x600 with different launcher).

jcolebaker said:
Anyone else with a similar device?
Click to expand...
Click to collapse
I just installed the same unit. Only complaints are streaming music via Bluetooth only works if you open up the Bluetooth app (probably because android doesn't act as a Bluetooth sink). The other issue is, I cannot seem to change the brightness of the screen...its a touch too dim for daylight (I have a convertible) and a bit too bright for nighttime.
Glad to see you got a custom rom working.

Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk

vdubskey said:
Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry not sure what the LCD is - I don't want to pull it apart. It has a board on the back which has the following on it:
BL-TFT-V2.2(HCT)
That's soldered to another board that says:
P/N:BL-7inch-7000-KB-V00 20150311

Update question
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
---------- Post added at 11:06 PM ---------- Previous post was at 10:42 PM ----------
dovoto said:
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
Click to expand...
Click to collapse
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?

dovoto said:
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?
Click to expand...
Click to collapse
The file should be "update.zip". I used a new SD card - try formatting one with FAT32.
You just copy it to the card and insert it - I think the stock Android image automatically checks for update files that look like this, and loads them. This process worked OK for me - if not then hopefully someone here knows more about the update process than me.

HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks

Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
I think the file is "update.img" not "update.zip". Anyway I have not figured out how to get to the boot loader on mine, and I never got any recovery console. Sorry I am too much of a beginner myself to suggest anything.

HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Instead of flashing a new image, go to the factory settings and type in *#hct#root#
This should give you root, no need to flash a new image

Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Bonjour.
If you would like more than root and you're still having trouble getting into recovery with your Hot Audio RK3066 1024x600 2 DIN Head Unit, the steps below have worked for me when the system does not automatically detect the mcu or update.img.
*** Prior to flashing any OEM or Custom ROM firmware, I recommend using a backup app like Titanium to save all your existing apps and data to your external micro sd card or usb memory stick.
1) Install Quick Boot or a similar apk from the play store.
2) Attach a wireless usb or usb keyboard and confirm it is working as intended. I use a Lenovo N5902 but most usb or wireless usb keyboards should work for this task.
3) Make sure you have the update and or mcu image file on your gps micro sd card or an attached usb memory stick (not the zip file).
4) Open Quick Boot, select recovery, and the system will shut down and boot into recovery.
5) Use your usb keyboard to scroll or arrow down to the update option with correct img file location, then press enter to execute the mcu or android firmware update or both.
6) After you update the android firmware, it is highly recommended that you go into the Settings > Backup & Reset, and select reset to factory and check the box to delete all data from the internal sd card. This reset to factory and internal sd card wipe should give your updated android system a clean start and help avoid system issues due to left over data from the previous firmware.
7) Delete the mcu and or update image from your external micro sd card. Done.
Hope this helps...
Best to all,
R

wrong thread. sorry

Android dvd s07 update
Hi,
I want update my android car dvd mercedes w203 2006
MCU version: MTCB-KGL-V2.80
Android version:
4.4.4._07012016
3.0.36+
[email protected] #2321
I need files to update, please help

Related

Caska Android 4.4.2 2 din

Has anybody managed to root android caska 4.4.2?
Thanks
Anyone?
It says:
mcu: v3.00h7_ca712_f7e1430
kernel: 3.0.36+
android 4.4.2
Thanks
Also looking for a way to root this HU too.
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
War-Rasta said:
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
Click to expand...
Click to collapse
I've never used Android, I'm a iOS user and very afraid to brick my unit. I just download ROM for 4.4.2 and boot it according to the instructions?
My unit shows:
MCU Version: V3.00F8_CA380_E55B_ECI1455
Build number: D200 Ver2.01 20141228.2309
TCON Version: V6.00_HSD80_EC28e
Many thanks for your help!
War-Rasta said:
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
Click to expand...
Click to collapse
I actually tried a Malaysk's rom and It gave me error in the middle of installation. I had to return the original rom. Not quite sure if I used the correct malaysk's rom. I have a rk3066 android. 4.4.2
Hi Guys,
I also have a similar unit. Did you manage to make a backup of current image? I want to upgrade because I have two issue: sometimes the unit doesn't complete the startup and I can't use sygic navigator.
Build number: D200-20150713.2225-S1
Kernel version:3.0.36+
[email protected] #883
Tue Jul 7 10:43:52 CST 2015
MCU Version:V3.00H7_CA712_F7E1430
TCON Version:V6.00_HSD70_F77Hi
Media Version:89J_0025_000000
SN Number:UNKNOWN
Bluetooth Version:I50E_ADK.HBS.0.20150521.1
Hardware Version:TFT:EC2_EBT
MB:EC2_D1S
MD: DE5GM_R82_TE6K
Best regards,
lmcoelho said:
Hi Guys,
I also have a similar unit. Did you manage to make a backup of current image? I want to upgrade because I have two issue: sometimes the unit doesn't complete the startup and I can't use sygic navigator.
Build number: D200-20150713.2225-S1
Kernel version:3.0.36+
[email protected] #883
Tue Jul 7 10:43:52 CST 2015
MCU Version:V3.00H7_CA712_F7E1430
TCON Version:V6.00_HSD70_F77Hi
Media Version:89J_0025_000000
SN Number:UNKNOWN
Bluetooth Version:I50E_ADK.HBS.0.20150521.1
Hardware Version:TFT:EC2_EBT
MB:EC2_D1S
MD: DE5GM_R82_TE6K
Best regards,
Click to expand...
Click to collapse
By your username I assume you're brazilian, right?
Where did you buy your unit?
This night I've managed to talk to a Caska sales director for LATAM and he said that they cannot give the stock ROM for security reasons. I still have problems with the clock and the startup also (blank screen). They say their engineering team is working on fixing that issue, but China has a holiday that starts today (Oct 1st.) and only ends Oct 7th. So I'll only have an answer after that day.
Maybe you can talk to your seller and see if he gives any support (I bought mine at www.rcmultimidias.com.br).
Sure I am, you are right.
I bought mine from aliexpress. I found a update.img file in some folder, but I'm not sure if it is the full image. I opened that image in a linux box and looks like we have everything, there some ext4 images, boot image and a lot of other files, but I'm not 100% sure about it. May be somebody with experience could verify that.
Another annoying thing is the music and video apps not reading files from sdcard, they only read USB and inand. I've modified the Music app to point it to the correct path, but I couldn't install it back to the unit (It fails to install without any error). At least if I could reassign music and video buttons to another app, that would be ok (VLC is working fine, just need to adjust volume).
purchio said:
By your username I assume you're brazilian, right?
Where did you buy your unit?
This night I've managed to talk to a Caska sales director for LATAM and he said that they cannot give the stock ROM for security reasons. I still have problems with the clock and the startup also (blank screen). They say their engineering team is working on fixing that issue, but China has a holiday that starts today (Oct 1st.) and only ends Oct 7th. So I'll only have an answer after that day.
Maybe you can talk to your seller and see if he gives any sup.
Click to expand...
Click to collapse
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
Normally you have to boot in recovery mode, something that I still don't know how to do for this unit, and then use that update.img to restore. See this thread http://forum.xda-developers.com/showthread.php?t=2660662, there some possible procedures there and may be one of them work for the caska.
How big is the update.img file they sent to you?
lmcoelho said:
Normally you have to boot in recovery mode, something that I still don't know how to do for this unit, and then use that update.img to restore. See this thread http://forum.xda-developers.com/showthread.php?t=2660662, there some possible procedures there and may be one of them work for the caska.
How big is the update.img file they sent to you?
Click to expand...
Click to collapse
Yeah. I have tried everything but could not boot. It is just a blank screen.
Here you go with the update.img.
https://www.sendspace.com/file/mjkgfj
Here I posted a video with all the problems I'm experiencing with this unit. The main problem is that I cannot setup the right time, so all Android apps are useless (they require a secure connection to their servers and this is only allowed with a valid certificate [that needs the correct date]).
I was trying to root my unit so that I could use ClockSync to fix the time every 30 seconds (it resets after 1 minute), but had no success on that.
https://www.youtube.com/watch?v=tWWCP9tAYm4
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
Hi!
So, where did you managed to talk to Caska? I've tried contact with Caska Brasil with no success (they say they do not offer support for Android units), and Caska Global didn't give any answer ([email protected]).
I've downloaded your update.img, but it's for CA712 and my unit is a CA380-XLA, I'm afraid to brick it. Have you tried entering recovery mode pressing reset and power buttons the same time?
lmcoelho said:
Sure I am, you are right.
I bought mine from aliexpress. I found a update.img file in some folder, but I'm not sure if it is the full image. I opened that image in a linux box and looks like we have everything, there some ext4 images, boot image and a lot of other files, but I'm not 100% sure about it. May be somebody with experience could verify that.
Another annoying thing is the music and video apps not reading files from sdcard, they only read USB and inand. I've modified the Music app to point it to the correct path, but I couldn't install it back to the unit (It fails to install without any error). At least if I could reassign music and video buttons to another app, that would be ok (VLC is working fine, just need to adjust volume).
Click to expand...
Click to collapse
I can reassign the screen buttons in my unit. In the settings, go to the last menu: "Shortcuts". Not sure if there's a way to reassign the physical buttons without modifying the original ROM.
danylam said:
Yeah. I have tried everything but could not boot. It is just a blank screen.
Here you go with the update.img.
Click to expand...
Click to collapse
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
lmcoelho said:
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
Click to expand...
Click to collapse
I've tried pluggin a USB to the unit and connecting it to my PC with no success, no devices are recognized. I have developer mode active but no options to enable USB Debugging.
So, I was able to extract all APKs from the file danylam hosted, and it's quite different from my unit: I have only one "Settings" menu, and in my unit some essential apps weren't installed (like HBS_Carkit_ChangeLogoUtil.apk and HBS_Carkit_SyncGPSTime.apk). I've installed them and solved one of my problems: car starting with a GMC logo. But the SyncGPSTime.apk isn't being called by any applications, so it's not starting (and I cannot start from itself).
Then I tried installing the Settings.apk that came with the ROM and ended up with a non functional setup menu, unfortunately. Since in that version most settings are changed from the "Android Settings", and I couldn't install that apk (it shows me an unknown error), I've lost some essential menus.
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
purchio said:
So, I was able to extract all APKs from the file danylam hosted, and it's quite different from my unit: I have only one "Settings" menu, and in my unit some essential apps weren't installed (like HBS_Carkit_ChangeLogoUtil.apk and HBS_Carkit_SyncGPSTime.apk). I've installed them and solved one of my problems: car starting with a GMC logo. But the SyncGPSTime.apk isn't being called by any applications, so it's not starting (and I cannot start from itself).
Then I tried installing the Settings.apk that came with the ROM and ended up with a non functional setup menu, unfortunately. Since in that version most settings are changed from the "Android Settings", and I couldn't install that apk (it shows me an unknown error), I've lost some essential menus.
Click to expand...
Click to collapse
Hi,
The only way to talk to caska global is using skype (coagent,service). Normally they are online at 9pm (Sao Paulo time).
lmcoelho said:
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
Click to expand...
Click to collapse
Can you tell me how to extract this bin file from the image?
Thanks
purchio said:
I've downloaded your update.img, but it's for CA712 and my unit is a CA380-XLA, I'm afraid to brick it. Have you tried entering recovery mode pressing reset and power buttons the same time?
Click to expand...
Click to collapse
I found the update.img in my CA712 with a simple search for update.img. I used the file browser and and did the search from / device.
---------- Post added at 10:59 AM ---------- Previous post was at 10:40 AM ----------
danylam said:
Can you tell me how to extract this bin file from the image?
Thanks
Click to expand...
Click to collapse
This is the linux tool to open the image http://forum.xda-developers.com/showthread.php?t=2257331
command:
Code:
./imgrepackerrk update.img
It creates a update.img.dump folder and the bin file should be in the update.img.dump/Image
Boot.img is compressed and if you want to see content do this:
Code:
mkdir boot
cd boot
gzip -cd ../boot.img | cpio -i -
lmcoelho said:
I found the update.img in my CA712 with a simple search for update.img. I used the file browser and and did the search from / device.
Click to expand...
Click to collapse
Tried searching mine but couldn't find any *.img files. But at least I've managed to uninstall the CA712 settings from my unit and revert to the original one.
Looks like your unit is a little bit different from mine.

Help!! Bricked Seicane H605E t3 k2001m Android 6.0.1 Head unit

Guys I have a huge problem. I searched day and night for the last couple of days, still no solution for my problem.
I bought the cheapest Seicane head unit (model H605E). It's one of those head units that doesn't have any depth. It's very shallow/thin/short however you may wanna call it. It doesn't have an SD CARD SLOT or any PHYSICAL BUTTONS, just a touch panel. Specs showing on their website and in the settings of the device are:
QUAD-CORE T3 K2001M 1.6GHz
16GB ROM
1GB RAM
Rooted my device with kingroot. installed CPU-Z and ES file explorer. Noticed that the actual RAM was 752MB. From which the half was being used all the time. Actual capacity was 1.94GB not 16GB. From this 1.94GB only 1.5 was usable. There was an additional 10GB of space showing on the board as an sd card. Weird thing is that my device doesn't have an sd card slot. CPU clockspeed was 1104MHz.
Anyways I couldn't even run spotify in the background. It was auto killing all processes in the background. Actually pausing not killing. I searched the net and it was supposed to be power saving mode causing this. Funny thing is my head unit also doesn't have a battery. So whatever I did I couldn't solve the problem. I even accessed all the additional settings with settings editor pro. But no luck. So I decided to delete some system files with system app remover. Till finally everything seemed to stop working.
It was time to do a system restore. Oh forgot to mention I did one succesful system restore earlier. Anyways this time, it gave me the option to format my sd card. So Again.. I don't have an sd card slot. So I thought "Yeaaah, why not?" It rebooted and now I'm stuck in an infinite bootloop.
It's giving the following error:
supported api: 3
E: Failed to mount / cache (no such file or directory)
Rebooting..
I contacted Seicane and they're not exactly the most helpful reseller. They ignored my questions about where I can find a stock rom. I did find one on 4pda tho. I think that one should work. So far so good right. I ordered an usb male to male cable. Because the only slots the head unit has are 2 usb slots. I didn't succeed with connecting tho. It's not working. I totally bricked my device and in desperate need of help. And no, there's no one on the internet with the same device and/or problem.
Any help with telling me how I can put this thing in recovery mode (because of the absence of pysical buttons) and how to flash it would be greatly appreciated. I tried with phoenix suit and live suit btw. Maybe I did something wrong I don't know.
usb bridged cable?
My ordinary male to male usb cable doesn't work for the connection. Would a usb bridged cable do the job?
You need a USB SD card reader.
rigattoni said:
You need a USB SD card reader.
Click to expand...
Click to collapse
Will that work for sure?? or is it a hunch?
And how will I get in recovery?
KillinDesire said:
Will that work for sure?? or is it a hunch?
Click to expand...
Click to collapse
If you don´t have an SD card slot there is only this single solution possible...
KillinDesire said:
And how will I get in recovery?
Click to expand...
Click to collapse
You need the correct firmware before you try to get into the recovery. At least the firmware on the SD card would open the recovery itself.
Manually there are at least more than one possible options to get into Recovery:
Long press of the reset button (until your softbuttons are blinking)
Pressing the reset button and volume up or down
Pressing the reset button in combination with any other soft button
...
...at least: You should ask the seller for information and firmware. Without firmware you are not able to get the unit back to life.
Ah... the hardware contains a so called SD Card, called "Internal SD", this is correct so far.
If your uni does not have the RAM and ROM which was written in the shop... send the trach back and use some more money to get a good one.
Thanks a lot man I will try it tomorrow with a usb card reader. I need to buy one. Here’s the thing with sending back. I paid $69.99 for the device and $28 for shipping. So they’re only refunding 69.99. I also have to pay money to send it back to china.
Thus it’s not worth the trouble of sending back and waiting for a louzy 50 dollars. That’s the reason I rather save the thing than waiting another month.
rigattoni said:
If you don´t have an SD card slot there is only this single solution possible...
You need the correct firmware before you try to get into the recovery. At least the firmware on the SD card would open the recovery itself.
Manually there are at least more than one possible options to get into Recovery:
Long press of the reset button (until your softbuttons are blinking)
Pressing the reset button and volume up or down
Pressing the reset button in combination with any other soft button
...
...at least: You should ask the seller for information and firmware. Without firmware you are not able to get the unit back to life.
Ah... the hardware contains a so called SD Card, called "Internal SD", this is correct so far.
If your uni does not have the RAM and ROM which was written in the shop... send the trach back and use some more money to get a good one.
Click to expand...
Click to collapse
The USB sd card reader came in. But still no luck. At this point I'm not sure about anything anymore. I really really really have a giant urge to smash this thing to pieces. Rather on one of the employees head from Seicane. Doesn't matter who. Just anyone from their company will qualify for this ****. So if anyone wants to volunteer feel free to pm me.
anyways, any other ideas?
i have the same problem
Did you have any solutions ?
Had the same issue. The HU (with 2 USB ports) was some unknown brand called Funrover loosely based on Joying firmware. What worked for me was
- Download the suitable firmware
- Extract it on the PC and then copy the firmware files on to a freshly (FAT32) formatted USB drive
- Plug in the USB drive to your HU USB port (1?)
- Since your HU is already bootlooping, plug in a keyboard and use the following key combination> Alt + Print Scr + tapping i (or e, both worked for me) to get in to recover
- Ideally the recovery option will detect the plugged in USB and start reflashing the firmware so that you will be able to use the HU again.
Hi. Was it running fine b4 rooting? Or it went weird after kingroot?
i have same unit and its workin with some problems. if you help me i can backup my unit rom vs whatever and upload than share with who need it.
sorry for language i'm still working on it.
i attached a photo about my device specs
ceyrekoto said:
i have same unit and its workin with some problems. if you help me i can backup my unit rom vs whatever and upload than share with who need it.
sorry for language i'm still working on it.
i attached a photo about my device specs
Click to expand...
Click to collapse
la voz del gps se oye muy poco, como lo habeis solucionado
MADNESSSsss said:
Had the same issue. The HU (with 2 USB ports) was some unknown brand called Funrover loosely based on Joying firmware. What worked for me was
- Download the suitable firmware
- Extract it on the PC and then copy the firmware files on to a freshly (FAT32) formatted USB drive
- Plug in the USB drive to your HU USB port (1?)
- Since your HU is already bootlooping, plug in a keyboard and use the following key combination> Alt + Print Scr + tapping i (or e, both worked for me) to get in to recover
- Ideally the recovery option will detect the plugged in USB and start reflashing the firmware so that you will be able to use the HU again.
Click to expand...
Click to collapse
Do you place firmware files into directory alone, in zip file? what format? Mine doesn't seem to recognize the usb how I have them.
Myseka said:
Do you place firmware files into directory alone, in zip file? what format? Mine doesn't seem to recognize the usb how I have them.
Click to expand...
Click to collapse
Extract the zip file your downloaded on the PC itself and copy the extracted files on to the USB so that all the files are on the root of your USB.
eg: If your USB is F: drive, the content would be (For Sofia 3GR)
Code:
mcu <- folder
oem <- folder
5009_20.zip
5009_60.zip
bootanimation.zip
Allapp.pkg
config.txt
crruptoff
customercfg.txt
logo.bmp
rksofiacfg.fg
SQLSOFIA
I have the same unit but with Android 7 and I fight the same problem with auto-killing apps.
Have you tried putting spotify to sys.keep_app_1 in /system/build.prop?
I'm hoping you recovered your system.
Edit.
Actually chemixzgz's tip helped me solve app-killing issue. Apps need to be added to Whitelist in device settings.
https://forum.xda-developers.com/showpost.php?p=78745173&postcount=4
May be a hardware issue!
KillinDesire said:
Guys I have a huge problem. I searched day and night for the last couple of days, still no solution for my problem.
I bought the cheapest Seicane head unit (model H605E). It's one of those head units that doesn't have any depth. It's very shallow/thin/short however you may wanna call it. It doesn't have an SD CARD SLOT or any PHYSICAL BUTTONS, just a touch panel. Specs showing on their website and in the settings of the device are:
QUAD-CORE T3 K2001M 1.6GHz
16GB ROM
1GB RAM
Rooted my device with kingroot. installed CPU-Z and ES file explorer. Noticed that the actual RAM was 752MB. From which the half was being used all the time. Actual capacity was 1.94GB not 16GB. From this 1.94GB only 1.5 was usable. There was an additional 10GB of space showing on the board as an sd card. Weird thing is that my device doesn't have an sd card slot. CPU clockspeed was 1104MHz.
Anyways I couldn't even run spotify in the background. It was auto killing all processes in the background. Actually pausing not killing. I searched the net and it was supposed to be power saving mode causing this. Funny thing is my head unit also doesn't have a battery. So whatever I did I couldn't solve the problem. I even accessed all the additional settings with settings editor pro. But no luck. So I decided to delete some system files with system app remover. Till finally everything seemed to stop working.
It was time to do a system restore. Oh forgot to mention I did one succesful system restore earlier. Anyways this time, it gave me the option to format my sd card. So Again.. I don't have an sd card slot. So I thought "Yeaaah, why not?" It rebooted and now I'm stuck in an infinite bootloop.
It's giving the following error:
supported api: 3
E: Failed to mount / cache (no such file or directory)
Rebooting..
I contacted Seicane and they're not exactly the most helpful reseller. They ignored my questions about where I can find a stock rom. I did find one on 4pda tho. I think that one should work. So far so good right. I ordered an usb male to male cable. Because the only slots the head unit has are 2 usb slots. I didn't succeed with connecting tho. It's not working. I totally bricked my device and in desperate need of help. And no, there's no one on the internet with the same device and/or problem.
Any help with telling me how I can put this thing in recovery mode (because of the absence of pysical buttons) and how to flash it would be greatly appreciated. I tried with phoenix suit and live suit btw. Maybe I did something wrong I don't know.
Click to expand...
Click to collapse
Followed everyone's suggestions, nothing worked. Followed videos for taking unit apart to reset battery. (find on you -tube) easier than I imagined. Recharged battery and it works. Wasted 2 days trying software fixes.
loisbajor said:
May be a hardware issue!
Followed everyone's suggestions, nothing worked. Followed videos for taking unit apart to reset battery. (find on you -tube) easier than I imagined. Recharged battery and it works. Wasted 2 days trying software fixes.
Click to expand...
Click to collapse
How do you achive this can u explain bit more? Batttery mean HU's battery? Can u send me link of video.

Help identify unit, manufacturer code ZQ?

I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.
mondo1287 said:
I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.
Click to expand...
Click to collapse
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]
Albe Vala said:
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]
Click to expand...
Click to collapse
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
I don't know how is it possible to exctract the MCU file (.bin) by the interface. I could try to find online anything to do it. i try to find softwars and so on, if i'will try i tell you something. I send many mails to producer of the unit, but everytime i do it, he tell me to waiting for response of the engineering department......and i wait. My MCU was TUREG-ZQAND-1.3 but i think your version 1.1 coluld going rigt for mine.
Not (android-auto) requested moderator move to Android head units forum.
mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
Hi Mondo. I've find how could you extract the MCU file from your ZQ android interface. read the thread that i link you now! I wiat for your reply. https://www.androidiani.com/forum/autoradio-android/546699-f-q-px5-autoradio-android.html. At the end of Point "2" you can read how to export your mcu file! Thanks a lot and best regards.

Collection of 8227l firmware (android vers:6-9)

https://m.youtube.com/watch?v=FLe7yx3XJP8https://m.youtube.com/watch?v=FLe7yx3XJP8
click video link and comment. im not a developer i just listened to the amazon sellers directions and then searched 8227l in google and found a bunch of files, then tested them and now i want to pass the info on.
tp the guys asking if itll work?
i dont know you gotta test it like i did. they worked on my unit. and the files i donloaded came from other style stereos with android.
i just generally think they are all same firmware if it look similar to actual stereo design and ui .
This is what I have.
Android : YT9216b_00002_V004_20190728
8227L
MCU 3.1
MODEL NUMBER 8227L_DEMO
Can i install the 9.0? Is is real 9.0 or fake?( you know right now it has 6.0 but says it is 8.1GO)
its the fake 8.1 like always but it works so cant complain.
ighostsgunnaz said:
its the fake 8.1 like always but it works so cant complain.
Click to expand...
Click to collapse
Is this the 8.1go or just 8.1?
Also the android 9.0 has multi screen working?
Can i safely flash my head unit with the firmware listed?
Yes u can ( always do at your own risk like me); but use one of the touch only files. I can't upload pictures yet but i tried to post a screenshot of each firmware look. If its 8227l firmware it should update/flash.
ighostsgunnaz said:
Yes u can ( always do at your own risk like me); but use one of the touch only files. I can't upload pictures yet but i tried to post a screenshot of each firmware look. If its 8227l firmware it should update/flash.
Click to expand...
Click to collapse
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
slayer369 said:
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
Click to expand...
Click to collapse
They both looked very smooth even when running on my stereo. And i have a touch & button stereo it worked flawlessly no lag no glitch.
Only error was for the firmware being for touch screen only
Hello, I would like to know if this type of software has in some menu the option of autosleep to program that it turns off completely and does not remain in standby, in other Android it exists but here I do not see it. Can this Android 9.0 image be flashed even if it now has 8.1? Is it official or is it rooted?
thanks
i have the following head unit in the link attached will android 9 rom support this head unit ? It has touch button such as back,home,volume up/down.
and how does UI2 look like?
https://drive.google.com/open?id=0B-DeZ2cJS-h6UFVKSkswdExXX2NMNnc2akoydS1jcVQxd1hN
Hi guys! I ask for your help, a few days ago I bought an android radio unit on aliexpress, specifically the Junsun brand, with these characteristics:
Model: 8227L
Android version: 8.1.0
Kernel version: 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3.2017.05) [email protected] #57
Comp. Number: alps.mp.o1.mp5
2GB Ram
32Gb Rom
7 inch
With Canbus (ford mondeo 2007)
Its my first time with an android radio unit and I am very lost, I would like to know if I can change the firmware or update it, the one that it brings is very limited and does not let me change the brightness of the device or bluetooth functions.
Thank you for support!
Hi guys!
Is it suitable for me?
'Android 9'
ac960e2134.jpeg[/IMG]
I tryed to update using 8.1 archives, the unit detect the USB files, ask for update with a countdown, but when autorestart and start to update, the unit say fail, check USB and files...
Any solution?
i have 8227L with DSP will it work with this
ighostsgunnaz said:
Above are 2 android 7.1 & 8.1 example. Below is Android 9 example.
This is for those who have a ( 8227l ) android stereo and are looking for the update file zip. Also the mcu in the about phone menu should begin with ts . I have 5 files from jby tech, they are the Amazon seller of my hizpo android 8.1 stereo unit. From lots of research and emails to the company, i found that these Android stereos come in many brand names but run the same 8227l system. Another company with the same unit is joying but the device name is different along with the entire UI. Please do be sure you have a 8227l unit before proceeding. Other updates for other brands can be found on google and xda forum. I will try to remember to put link for xda forum. Below I have listed 2 groups of files. One is for touch screen only android stereo and the other is for touch screen with volume knob. Please choose according to your type of stereo. And follow the steps below exactly.
1. Download proper zip for your device.
2. Extract the 2 files from within the zip folder.
3. Copy & paste the ( .bin ) & other file on to a blank sd card or usb flash drive. Make sure these are the only 2 files on the sd card or flash drive.
4. With stereo unit powered off insert the sd card or usb flash drive and power on stereo. (Note some units will recognize the file immediately during boot, and others will prompt you after loading main screen. If unit does not recognize it, power off for 40sec and when u power on tap the screen in middle repeatedly with finger until the word "detected" shows in green. If it gives a message in red saying failed please check you have good download copy and have followed the instructions exactly. Will answer questions as i am able to.
All links to files and sites mentioned must be copy pasted. Im not able to attach external link yet.
The files below this line are for android6os,7os,8.1os 8227l units with a volume knob
Stock Android 7.1 firmware:
drive.google.com/folderview?id=1_D0IOyzUDNwo83Y4cVv054HPmaYs2JO7
Stock android 8.1 firmware:
drive.google.com/folderview?id=1LJ-FVgn73hxqJ-x7-pSJZuJDkfEV-c-7
Here is another version for this unit that is stock Android 6,7os but felt like it had a low resolution not for certain, but is safe to install in case base version still isnt a match for your unit:
Android7.1 V63
7drive.google.com/file/d/14UTC12nlWutwEqfsfux8spPY6qApw8Nt/view?usp=drivesdk
Android 7.1 v67
drive.google.com/file/d/1QQkQnxYZuO8rZ19KqVKPtVRIIE81sJ5b/view?usp=drivesdk
____________________________________
The files below are for the "TOUCH" only Android 9os 8227l units with touch back, home, vol -/+ buttons.
*** I have installed them on the non-touch unit and it will work but not allow volume knob to work, and will display " Activation code does not match " ***
Stock android 9 touch firmware version 1:
drive.google.com/file/d/19Yn_v6hXMJBObvgS7eqPN2nVgHhoisyX/view?usp=drivesdk
Stock android 9 touch firmware version 2:
drive.google.com/file/d/14gSJXCNqYPpUkgg7M_sd3jim6JvF1R3M/view?usp=drivesdk
Click to expand...
Click to collapse
I have a 8277L with Dsp, will it work with this one.
Hy guys,
I have this android radio with fake android 9.1
Android: YT9216C_AHD_00005_V004_20191017_HIFI
System: Android 9.1 XY AUTO:3.1 (8227L)
CAN pro: 3.0 (8227L)
DDR: 2G FLASH:32G
CPU: A7 1.3 GHz x4
MCU1: 3.1
Kernel Version: [email protected]#5
Build number: android-trunk-m0.AC8227L-V1.0
The unit have hardware buttons for volume up and down.
Can i install android 9 touch or android 8.1 ?
Thanks for the reply and sorry for my bad english.
rohan_agashe said:
I have a 8277L with Dsp, will it work with this one.
Click to expand...
Click to collapse
I have it too... Are there Any New firmware? I changed launcher to agama and each time i start the unit, usb doesnt detect it.
The 8.1 versión is horrible
code
ighostsgunnaz said:
Above are 2 android 7.1 & 8.1 example. Below is Android 9 example.
This is for those who have a ( 8227l ) android stereo and are looking for the update file zip. Also the mcu in the about phone menu should begin with ts . I have 5 files from jby tech, they are the Amazon seller of my hizpo android 8.1 stereo unit. From lots of research and emails to the company, i found that these Android stereos come in many brand names but run the same 8227l system. Another company with the same unit is joying but the device name is different along with the entire UI. Please do be sure you have a 8227l unit before proceeding. Other updates for other brands can be found on google and xda forum. I will try to remember to put link for xda forum. Below I have listed 2 groups of files. One is for touch screen only android stereo and the other is for touch screen with volume knob. Please choose according to your type of stereo. And follow the steps below exactly.
1. Download proper zip for your device.
2. Extract the 2 files from within the zip folder.
3. Copy & paste the ( .bin ) & other file on to a blank sd card or usb flash drive. Make sure these are the only 2 files on the sd card or flash drive.
4. With stereo unit powered off insert the sd card or usb flash drive and power on stereo. (Note some units will recognize the file immediately during boot, and others will prompt you after loading main screen. If unit does not recognize it, power off for 40sec and when u power on tap the screen in middle repeatedly with finger until the word "detected" shows in green. If it gives a message in red saying failed please check you have good download copy and have followed the instructions exactly. Will answer questions as i am able to.
All links to files and sites mentioned must be copy pasted. Im not able to attach external link yet.
The files below this line are for android6os,7os,8.1os 8227l units with a volume knob
Stock Android 7.1 firmware:
drive.google.com/folderview?id=1_D0IOyzUDNwo83Y4cVv054HPmaYs2JO7
Stock android 8.1 firmware:
drive.google.com/folderview?id=1LJ-FVgn73hxqJ-x7-pSJZuJDkfEV-c-7
Here is another version for this unit that is stock Android 6,7os but felt like it had a low resolution not for certain, but is safe to install in case base version still isnt a match for your unit:
Android7.1 V63
7drive.google.com/file/d/14UTC12nlWutwEqfsfux8spPY6qApw8Nt/view?usp=drivesdk
Android 7.1 v67
drive.google.com/file/d/1QQkQnxYZuO8rZ19KqVKPtVRIIE81sJ5b/view?usp=drivesdk
____________________________________
The files below are for the "TOUCH" only Android 9os 8227l units with touch back, home, vol -/+ buttons.
*** I have installed them on the non-touch unit and it will work but not allow volume knob to work, and will display " Activation code does not match " ***
Stock android 9 touch firmware version 1:
drive.google.com/file/d/19Yn_v6hXMJBObvgS7eqPN2nVgHhoisyX/view?usp=drivesdk
Stock android 9 touch firmware version 2:
drive.google.com/file/d/14gSJXCNqYPpUkgg7M_sd3jim6JvF1R3M/view?usp=drivesdk
Click to expand...
Click to collapse
When I give the code 12345678 in the menu, I come in a separate menu in Chinese on my ac8227L Someone confesses to this.
how to upgrad my drive to android 9
noomkhup said:
how to upgrad my drive to android 9
Click to expand...
Click to collapse
I cant choose Android upgrade too, like the previous post shows: it is grayed out...
Soldiaz said:
I cant choose Android upgrade too, like the previous post shows: it is grayed out...
Click to expand...
Click to collapse
i think sell this device and buy new device android9 hahaha
Sorry My English is stupid - -"
i think i have the same unit as yours.how was your after flash result?
slayer369 said:
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
Click to expand...
Click to collapse

MCU version of Erisin ES6292B 9" PX6???

I received an Erisin ES6292B 9" PX6 for Mercedes Benz.
I don't know why but for some reason I was sure it was a MTCD/E version so without prior checking, I immediately went for the upgrade to Hal9K MOD.
The upgrade finished and the unit rebooted. I am not sure if I saw the boot logo (I think not) but as if this was not enough, during first boot, someone in the workshop cut the power to the car and the unit was bricked!
I wrote to Erisin and they sent me the Stock image to try to apply from recovery. However it is impossible to enter recovery with any way I tried. As long as I hold the reset button the unit is dead. When I release it the backlit starts but the screen remains black even after 10 minutes. No recovery, not even boot logo! It seems the MCU firmware is corrupted.
At the moment I have an ST-LINK/V2 programmer in my hands to go for unbricking with Wadzio method but STILL NO ANSWER FROM ERISIN IF MY UNIT IS MTCD/E or different.
Anyone knows?
Also, anyone knows a direct link to download recovery.bin for my unit?
What are the names of the files that were being applied for upgrade? Are you able to share these - assume you had two files, one MCU and the other android.
Also the stock image ersin supplied.
Note the wadzio Unbrick is for MCU unbricking, are you sure that the MCU is bricked? I.e. you are sure you were upgrading the MCU, because from your description, sounds like you were upgrading the SOM/Android.
Details are everything.
marchnz said:
What are the names of the files that were being applied for upgrade? Are you able to share these - assume you had two files, one MCU and the other android.
Also the stock image ersin supplied.
Note the wadzio Unbrick is for MCU unbricking, are you sure that the MCU is bricked? I.e. you are sure you were upgrading the MCU, because from your description, sounds like you were upgrading the SOM/Android.
Details are everything.
Click to expand...
Click to collapse
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery
When there is no boot logo, I guess it is the MCU. Correct?
aphilgr1 said:
When there is no boot logo, I guess it is the MCU. Correct?
Click to expand...
Click to collapse
Not necessarily, no.
aphilgr1 said:
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery
Click to expand...
Click to collapse
The zip doesn't contain an MCU, and is an android OTA zip, therefore if your power outage occurred while applying this file, the SOM emmc/nand is probably corrupt, and you might not be able to enter recovery.
I've had a number of SOMs sent to me exhibiting the same symptom, so not uncommon.
If unable to SDCard boot, SOM recovery via OTG is the likely path to recovery. Refer my threads/signature.
marchnz said:
The zip doesn't contain an MCU, and is an android OTA zip, therefore if your power outage occurred while applying this file, the SOM emmc/nand is probably corrupt, and you might not be able to enter recovery.
I've had a number of SOMs sent to me exhibiting the same symptom, so not uncommon.
If unable to SDCard boot, SOM recovery via OTG is the likely path to recovery. Refer my threads/signature.
Click to expand...
Click to collapse
I still have not managed to find out if my MCU version is MTCD/E or other. Still waiting for Erisin's response. They requested a video with symptoms which I already sent.
Supposedly my MCU's version is an STM32 and I tried to install Hal9k's ROM (specific for MTCD/E) wouldn't that corrupt the MCU? To my thinking, this is the most probable scenario.
aphilgr1 said:
I still have not managed to find out if my MCU version is MTCD/E or other. Still waiting for Erisin's response. They requested a video with symptoms which I already sent.
Supposedly my MCU's version is an STM32 and I tried to install Hal9k's ROM (specific for MTCD/E) wouldn't that corrupt the MCU? To my thinking, this is the most probable scenario.
Click to expand...
Click to collapse
The files you list are not MCU updates.
Its trivial to determine if you have an MTCD MCU using Wadzio's decryption tool, however & once again, the MCU is separate to Android. You cannot flash the "wrong" platform MCU (ie. MTCD vs STM MCU) in recovery.
Once again; the files you list are ANDROID and not MCU. Unless you havent described what you were doing to "upgrade" the unit, which lead to corruption; the SOM is bricked and not MCU.
Again, for clarity, MCU and ANDROID are not the same. They are separate images and cannot be flashed together.
marchnz said:
Once again; the files you list are ANDROID and not MCU. Unless you havent described what you were doing to "upgrade" the unit, which lead to corruption; the SOM is bricked and not MCU.
Click to expand...
Click to collapse
Kind of getting there. Ha ha, my knowledge is very epidermic! Tomorrow I ll try the SOM recovery via OTG as you suggested and report. Thanks for your time
Just a (silly?) question: Could we say MCU is equivalent to bios on a PC and Android is the equivalent to PC OS? If the MCU (=bios) is still untouched, even with Android (=PC OS) corrupted, why is it impossible to boot from SD or simply access recovery?
aphilgr1 said:
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery
Click to expand...
Click to collapse
Hello. | have an Erisin ES6283C 8" Android 9.0 Car Stereo DAB+ 4G WiFi HDMI GPS Sat Nav for Mercedes C/CLK/CLC Class W203 W209.
They (Erisin) provided me the same stock ROM as yours.
For sure your MCU is STM32, as mine.
aphilgr1 said:
Just a (silly?) question: Could we say MCU is equivalent to bios on a PC and Android is the equivalent to PC OS? If the MCU (=bios) is still untouched, even with Android (=PC OS) corrupted, why is it impossible to boot from SD or simply access recovery?
Click to expand...
Click to collapse
The MCU is more like say an auxillary fan and button controller, connected to a serial port, but still controlling the power supply to the computer.
Why impossible to boot or access recovery - corrupt emmc/nand.
Your unit doesnt look like an MTCD/E device.
Unfortunately hardware used in my PX6 implementation is quite different from what shown in SOM recovery over OTG page. I don't have the tools needed to uncover the SOM (75W soldering etc). Judging from the bottom, it seems the SOM is embedded on the mainboard and there may not be any pins accessible. However, rk3399 supports what is called MaskRom mode (a relevant link translated from Chinese) allowing programming of the SOM with the use of a male to male usb cable. But this would be possible only if we access the interior and find that the test points to bridge exist. My last resort if nothing else is possible.
Another issue I am facing is that my firmware is not in update.img format but comes in .zip split in several files. I think I need to repack it in .img format in order to be able to program my unit with existing tools and I don't know how
Just a last (stupid?) question. Accessing the MCU via ST-LINK/V2 programmer is possible. If we new the starting memory address of the SOM firmware or the various parts, would it be possible to flash from there?
florynn2003 said:
Hello. | have an Erisin ES6283C 8" Android 9.0 Car Stereo DAB+ 4G WiFi HDMI GPS Sat Nav for Mercedes C/CLK/CLC Class W203 W209.
They (Erisin) provided me the same stock ROM as yours.
For sure your MCU is STM32, as mine.
Click to expand...
Click to collapse
It is an STM32 eventually. I managed to unbrick it but the MCU was changed. Both firmware and config. I am stuck with an 800X480 desktop on a 1024X600 display.
Can you export your MCU.cfg file and send it to me please? I think you need to go to settings/about then toggle between Kernel Version and OS Version 6 times in total to enter hidden menu. If a password is asked, try 666666 or 123456. From there you can go down and select export config.
Thanks in advance!
aphilgr1 said:
It is an STM32 eventually. I managed to unbrick it but the MCU was changed. Both firmware and config. I am stuck with an 800X480 desktop on a 1024X600 display.
Can you export your MCU.cfg file and send it to me please? I think you need to go to settings/about then toggle between Kernel Version and OS Version 6 times in total to enter hidden menu. If a password is asked, try 666666 or 123456. From there you can go down and select export config.
Thanks in advance!
Click to expand...
Click to collapse
I tried to export config data (is the only export in the menu) and it's only a 1KB file. I think it's the config only for HU startup. I searched all the settings (including the Hidden section) and I have nothing to export the MCU config.
florynn2003 said:
I tried to export config data (is the only export in the menu) and it's only a 1KB file. I think it's the config only for HU startup. I searched all the settings (including the Hidden section) and I have nothing to export the MCU config.
Click to expand...
Click to collapse
This is exactly what I am looking for. Can you share please?
aphilgr1 said:
This is exactly what I am looking for. Can you share please?
Click to expand...
Click to collapse
here you go
Wondering if you managed to fix your HU? Also, what rom did you settle on?
Also, is that blue material on your HU metal or painted plastic?
lachlan102 said:
Wondering if you managed to fix your HU? Also, what rom did you settle on?
Also, is that blue material on your HU metal or painted plastic?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=81930477&postcount=100
Hi! Dumb question: I own an Erisin ES7802B which came with Android 8.0, where can I check or find if I can update my product? Thanks in advance!

Categories

Resources