Database Users

Avin Avant 2 - Android 4.1.1 [Currently No Root]

I'm trying to get root on the Avin Avant 2, but unfortunately i've been unsuccessfull despite extensive reading of this fine website. The Specs for the device are as follows:
Android 4.1.1 (Jelly Bean)
Dual Core 1.7Ghz CPU ARMv71
Mali-400MP GPU
Hardware Device Type "Cedric"
My model is the universal unit from avinusa (site down at the time of posting) . Factory options can be accessed with Code "0000" and i've enabled developer options. Allow Unknown Sources is enabled so i can load whatever APK i need via the inernet or flash drive
Things i've tried to get root:
Framaroot, KingRoot, TowelRoot and numerous other Rooting APK Tools - All Failed
RootMyAN21U - Won't install, probably due to signing
Attempting a USB connection - Won't work, i suspect the client mode connection is on the motherboard somewhere.
The unit appears to be vulnerable to all three MasterKey exploits and i've seen other units successfully rooted, so i think it's definitely possible. i've extracted the Settings, SettingsProvider and framework-res Apk's from the device as i've seen these being used as signing sources on other threads.
If someone could rework somthing like RootMyAN21U for me to try with the files i have provided, that would be great! I am open to any other sugestions (or detailed tutorials so i can help myself). A donation is available to whoever provides the solution!
APK'S From Device https://drive.google.com/open?id=0B89NZzCjXoSbWTVwLWVDR0xYU0U
Also, Merry XMAS

it has already root...
For owners of the AVIN Avant-2 unit there is a new software update available. Email tommy for the download link and password.
Software update for the BMW AVIN Avant-2 Update 09-09-2015
Change log:
1. Added ROOT access and SUPERUSER
2. Added EasyConnect app for Mirrorlink support for Android 5.0 phones and AirPlay support without the need of the AirPin app.
3. Removed a lot of apps from the pre_install_apps.zip file making the update process a lot faster. The removed apps are now placed in the optional_app.zip file in the link below.
You can add or remove your choice of app from the pre_install_apps.zip before running the update.
4. Increased userdata partition to 1524MB
And so on...

I not understand
I not Understand

I've emailed support but no reply as of yet. Is this patch uploaded somewhere?

Kaboom22 said:
I've emailed support but no reply as of yet. Is this patch uploaded somewhere?
Click to expand...
Click to collapse
Any luck, or any response, respectively? I am desperately waiting for Root/Superuser-support...

fpingoud said:
Any luck, or any response, respectively? I am desperately waiting for Root/Superuser-support...
Click to expand...
Click to collapse
Do you have a BMW E46?
If so, you got to take a look on the E46fanatics, just google it, there is a huge thread about your device.

Hi All!
I have the same unit in my car.
But the system is laggy and worst of all I'm having a huge BT-echo at the other side of the line which makes it impossible to have a decent call.
Also android 4.1.1 isn't really supported by the newest app-updates like iCoyote.
Smaller problems:
- System does recognize my iPod but it won't play any music from it
- The radio app shuts down every 10-ish minutes of use
- The status bar on top isn't useful at all and only uses up screenspace that i'd rather use for navigation like Waze.
Conclusion:
It "works" but that's about it.
Question:
Would it be possible to install a more recent version of android which uses the hardware more efficiently and makes the system more stable while keeping the most important functions (obviously).
I've contacted Avin Europe (as I live in Belgium) and Tommy from AvinUSA about this problem but sadly they didn't offer a solution. Even worse, they didn't even reply to me since the end of March.

"UI and mcu does not match" plz help me

My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 6.0.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-09-06 17:39:41 KEQ_(NOR)__90_C9_7706_5009_CAN(XianDai)_Newlap
Please help me solve the problem.
Thanks.

no0496 said:
My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 6.0.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-09-06 17:39:41 KEQ_(NOR)__90_C9_7706_5009_CAN(XianDai)_Newlap
Please help me solve the problem.
Thanks.
Click to expand...
Click to collapse
So.if I understood correctly....
You have updated your unit (not joying) with the joying Android 6 firmware. And now you have issues on boot as it appears a message that "ui and mcu dont match"
Do your unit boot?
Apparently joying has been placed a security check to avoid others use their software....
You have to enter into recovery menu to downgrade to your seller Android ROm.
Check on forums how to get into recovery.
Some guy wrote about plugging a keyboard and some key combination resulted into recovery menu.
There you can force to upload a new software (this time use the one supplied by your seller)
Enviado desde mi D6603 mediante Tapatalk

ikerg said:
So.if I understood correctly....
You have updated your unit (not joying) with the joying Android 6 firmware. And now you have issues on boot as it appears a message that "ui and mcu dont match"
Do your unit boot?
Apparently joying has been placed a security check to avoid others use their software....
You have to enter into recovery menu to downgrade to your seller Android ROm.
Check on forums how to get into recovery.
Some guy wrote about plugging a keyboard and some key combination resulted into recovery menu.
There you can force to upload a new software (this time use the one supplied by your seller)
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
The boot is normal. I asked the seller, but I do not know how to get into recovery mode.
I still do not have enough information.
10.1 인치 쿼드 코어 안드로이드 5.1 자동차 DVD 플레이어 기아 스포티지 2011 2012 2013 2014 2015 자동차 라디오 스테레오 gps 네비게이션 시스템
s.aliexpress.com/ruQJ3YRr
(from AliExpress Android)
That's the product I bought.

doitright6 said:
That is *NOT* the product you own. The specifications on that product indicate "RK3188 Cortex A9 Quad Core 1.6GHz CPU"
Yours is clearly an Intel/Sofia x86 CPU, which is so different that if you tried to install intel/sofia firmware on the rk3188 unit, it definitely would not boot.
Now there is something I find extremely interesting about your unit;
the MCU string indicates that it is an FYT5009 unit, just like the Joying, but with a manufacturer of "KEQ". Up until now, we have only seen Joying units with the FYT5009. If you can figure out how to load the Joying MCU firmware on there, then it just might work. This might be accomplished by just re-running the update process. There is a file that you would have to rename though -- 5009_20.zip has to be renamed to 5009_60.zip.
But beware; there is also the possibility that the Joying MCU firmware could brick the thing. I doubt it though, it is likely that yours is built from the same schematics.
Click to expand...
Click to collapse
The product is SOFIA chipset is right. It is written by the seller differently from the actual one.
I will attach an image link before the update.
Blog.naver.com/no0496/221001239611
As doitright6 said, it is not a joying product, but it could be updated in the same way.
I will attach the updated JOYING 6.0 firmware and my unit's 5.1.1 genuine firmware.
Please let me know how to fix it.
[JOING 6.0]
drive.google.com/open?id=0BymwBAxBOI-TU0pMQ2REZmV3djA
[my unit 5.1.1]
drive.google.com/open?id=0BymwBAxBOI-Tb0xLV0pjR2JHcXM
Thanks.

My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 5.1.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-10-19 11:20:27 RUL_(NOR)__90_C9_685x_5009_CAN(DaZhong)_Newlap
Please help me solve the problem.
Thanks.

Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.

Hi
How Can I know which MCU I should use
If my MCU looks like MCU version 5.3.1836-13E50201-160106
Thank you

Did this helped i am also stucked on the same situation

guys
have you solved this issue , please help me too

Omer.afzal said:
Did this helped i am also stucked on the same situation
Click to expand...
Click to collapse
helmi_zr1 said:
guys
have you solved this issue , please help me too
Click to expand...
Click to collapse
Did you both miss post #6? If that doesn't work, what was your result? Failing that - what does the reseller suggest?

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
sir
i have been trying to change the no. but couls not able to do it
kindly let me know whats the easy way

You're not going to be able to do it if you have not rooted your HU.

nic2k said:
You're not going to be able to do it if you have not rooted your HU.
Click to expand...
Click to collapse
thank you i will try to root my device and let you

helmi_zr1 said:
thank you i will try to root my device and let you
Click to expand...
Click to collapse
thank you sir the top message have been removed
thank you so much for your help :good::good::good::good:
now one more thing
how i can downgrade to the old firmware since i saw the file in my HU but when i try to selected the unit is not doing any things
do you have any idea ?

please help!
Hi!
I want to ask for help. I have a radio that the seller has corrupted with an update. the update was not good. i put up joying software and it works properly with it, but in the yellow bar above there is that "UI AND MCU DOEST NOT MATCH".put the latest update on it.2020-04-07.
thank you!
managed to root the device but fyt.prop filet is not included in the System / App folder. what could be the solution
land Mou [email protected] 16:26 4)
-keys
System Info
kernel:#1 SMP PREEMPT Tue Apr 7 12:20:56 CST 2020
platform 12)6313 LFN Full Band carplay
touch:goodix 911_1060 (5a422c2b)E:0
panel:none
radiotype:nxp6xXx_6686(dft)(0)
audiotype:dsp55
APP 1024x600 2020-04-09 09:10:18
System 2020-04-07 12:15:23 Tuesday
03L G23P46F04 veT. 1.U
EO/2020:03:2:16:50:18 blink
HTXY
---------------Device Status
System Application Info
System Application Information
CPU Info
CPU:Intel X86_Octa-Core 1.8GHZ [email protected] GB(Memory) + 64 GB(Storage)
MCU Version
2019.11.18 09:58:08 KEQ_53_C63L_G23P48F64_Ver: 1.0
Bluetooth Version
BLINK 2161_RELEASE0/2020:03:2:16:50:18_blink

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
Do you know the manufacturer number for this MCU?
MCU version: 2020.08.21 17:11:25 YIN_53_L82_G23P48F64_V:1.0
Thank you.

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
how can i enter i no found folder fyt.prop help

Hello friend i have the same problem i had rooted device and did change number 43 to 9 you had written, but screen warning now like written like this
UI AND MCU DOES NOT MATCH! (PCBA)
do you have a solution?
javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
e

I can't find fyt.prop file and I had rooted. I have android 10 , is there another solution?

In the same boat. Found the file in CX file explorer (yes, I'm rooted and CX is in root mode), but it won't save my changes ("Cannot save the file".).
Is there a known way to edit and save the fyt.prop file?
At least I only have $20 and a few evenings invested (I found my unit brand new at a thrift store). Been one of my better behaved ones but I got greedy on updates. Also, I flashed the wrong file because I misread my MCU version number, and what *should* have been the right file loops when I try to flash it (reboots after the "CUSTOMER ID" text of the MCU update, have to reset to end the loop)... Whoops!

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.

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!

podofo android head unit zlink not working after trying to update

I got a podofo head unit radio from ebay at the beginning of the year and just recently tried to update my zlink to the latest version but was unaware that there are a bunch of different zlinks for different radios. After the update my zlink gave me a error code that said "Channel Err! CHANNEL-MISS-MATCH Apk:[zhangxun]". Then I contacted the manufacture who told me to contact the ebay seller and the ebay seller isn't replying. Has anyone else solved this problem? All I want is a functional zlink. I've seen online that apparently I have to update my android radio but I cant find a site to do so.

These are pictures that might help show what Im seeing.

That error message you are getting is giving you some useful information. It's telling you that you need to be have the zhangxun channel version of the software in order to recognize the license that came bundles with the unit. I would advise downloading the version 5.3.31 zhangxun firmware from here and following the instructions in that post. It should update you to Zlink5. If you have an issue with wireless android auto working on first attempt, try disconnecting your phone bluetooth, then reconnecting to the head unit bluetooth again while Zlink is open.

SeaScoot said:
That error message you are getting is giving you some useful information. It's telling you that you need to be have the zhangxun channel version of the software in order to recognize the license that came bundles with the unit. I would advise downloading the version 5.3.31 zhangxun firmware from here and following the instructions in that post. It should update you to Zlink5. If you have an issue with wireless android auto working on first attempt, try disconnecting your phone bluetooth, then reconnecting to the head unit bluetooth again while Zlink is open.
Click to expand...
Click to collapse
I downloaded the 5.3.31 to a usb drive plugged it into my radio and did the android update from the radio settings but now my radio keeps restarting. It starts up to the regular car dashboard for 15 seconds then says shuts down and restarts.

Can you get into Apps and notifications long enough to uninstall Zlink? If not try loading 3.9.44 from a USB thumb drive and working up from there. Make sure the file is on the root of the drive with nothing else on it. You can also try to use the reset button to see if that helps.

I tried the other files by putting them on my usb drive but i cant go the the android update through the settings because the radio keeps restarting. These are pictures showing the process it takes

SeaScoot said:
Can you get into Apps and notifications long enough to uninstall Zlink? If not try loading 3.9.44 from a USB thumb drive and working up from there. Make sure the file is on the root of the drive with nothing else on it. You can also try to use the reset button to see if that helps.
Click to expand...
Click to collapse
Should I try the zlink apk's as well?

Unless you can uninstall any existing newer installed version of Zlink the apk files will not work. On the other hand, he gzipped files can overwrite whatever is already there. Looks like from your screen Zlink5 actually installed. By the way, just use the 4-pin USB connector when attempting updates just to be on the safe side.
It looks like what is happening is a bootloop following a failed system reset. Did this happen following the Zlink install or after pushing the reset button?

SeaScoot said:
Unless you can uninstall any existing newer installed version of Zlink the apk files will not work. On the other hand, he gzipped files can overwrite whatever is already there. Looks like from your screen Zlink5 actually installed. By the way, just use the 4-pin USB connector when attempting updates just to be on the safe side.
It looks like what is happening is a bootloop following a failed system reset. Did this happen following the Zlink install or after pushing the reset button?
Click to expand...
Click to collapse
This happened after I attempted the android update

Loudnewchamp said:
This happened after I attempted the android update
Click to expand...
Click to collapse
I'm sorry you got hit by this. Maybe you should cross-post this to the [APP] Z-LINK Channels thread with the screen pictures in case someone else has seen it happen.