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!
Related
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
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.
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.
Hi all,
I decided to make 3, very beginner-friendly guides on how to fully backup your Android Head Units and how to restore those backups. These guides are made primarily for the SuperMOD packages in my signature but will generally apply to any Mediatek-based device.
Video Guide - How to full backup your Android Head Unit
This guide will help you:
Backup your whole flash drive with SP Flash Tool
Create your own Scatter and Preloader file
Create your own shareable firmware
PDF Guide - How to restore your backup with SP Flash Tool
This guide will help you restore your backup on a working Android head unit, type MediaTek YT921xxx, with available flash dump
Video Guide - Test Point recovery of a bricked head unit
This guide will help you restore your non-working Android head unit, type MediaTek YT921xxx, with available backup
If you encounter errors during these procedures, like DRAM failures etc, here are the main reasons as to why this might be happening:
Your Preloader and/or Scatter file is incompatible - extract your native scatter and preloader from your backup file
Incompatible SP Flash Tool version
Try to insert the USB cable within 2 seconds of pushing 'WRITE' or 'DOWNLOAD'
Use USB 2.0 ports if available rather than USB 3.0
Make sure your USB port does not go into sleep mode
Your Mediatek drivers are not properly installed on your PC
Faulty or incompatible USB cable - make sure it's shorter than 1m.
Refer to this guide on information about all the errors
------------------------------------------
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!
iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
Click to expand...
Click to collapse
You know it. We know it. That you are the best!!! Thanks a lot!
Flashtool version is VERY critical, as I found out the hard way. Please remember to follow each author's instructions to the point.
iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
**ONLY UPLOAD 'BOOT1' IF YOUR UNIT IS BRICKED, OTHERWISE JUST UPLOAD THE 'ROM_USER" FILE.
Click to expand...
Click to collapse
Hello. Pdf file is not available for download.
raionshinzo said:
Hello. Pdf file is not available for download.
Click to expand...
Click to collapse
Thanks, please try again. The link has been updated.
iceblue1980 said:
Thanks, please try again. The link has been updated.
Click to expand...
Click to collapse
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.
raionshinzo said:
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.
Click to expand...
Click to collapse
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.
iceblue1980 said:
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.
Click to expand...
Click to collapse
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.
raionshinzo said:
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.
Click to expand...
Click to collapse
Try this guide.
iceblue1980 said:
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools.
Click to expand...
Click to collapse
That could be very helpful.
Is it available ?
oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse
iceblue1980 said:
oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html
oferyuval said:
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html
Click to expand...
Click to collapse
Isn't this a guide for WwR tool rather than Flash Tool?
iceblue1980 said:
Isn't this a guide for WwR tool rather than Flash Tool?
Click to expand...
Click to collapse
It uses WwR to make a scatter file and than SP Flash Tool
Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.
iceblue1980 said:
Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.
Click to expand...
Click to collapse
Great, many thanks !!! I'll try to follow it.
The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?
oferyuval said:
The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?
Click to expand...
Click to collapse
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
No, as you are instructed to disconnect the USB cable in step 15.
iceblue1980 said:
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
Click to expand...
Click to collapse
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
iceblue1980 said:
2. No, as you are instructed to disconnect the USB cable in step 15.
Click to expand...
Click to collapse
Sorry, I missed this one
oferyuval said:
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
Sorry, I missed this one
Click to expand...
Click to collapse
You can make your own scatter file using a tool like WwR MTK.
Having said that, I'd be very surprised if the scatter file in the software package didn't work for your device, providing your head unit is compatible.
Hi,
I have the same well-known issue that exists with most Android head units and Peugeot JBL amplifiers.
The amplifier only works until volume knob is adjusted, the issue is technically the same as in this video for example:
Of course, "Amplifier" is enabled in factory settings menu.
MY head unit looks the same as in the video but with PX6 and Android 11.
MCU ver: MTCH_MX_V3.81_1
When I ordered this unit, I asked 3 times the distributor if the head unit is complatible with JBL amplifier and he assured about compatibility.
Till then I discussed with the distributor many times but it seems they are lost and I afraid they won't provide any working solution...
Since all ingoing and outgoing CAN communication works otherwise (ie. remote control buttons, car menu controlling, parking radar, car diagnostics reading, VOLUME ADJUSTMENT, etc.) I'm quite sure this issue is realted to firmware not to hardware (CAN decoder). I read some posts on the internet where MCU update solved this issue.
So I'm looking for any suggestions or perhaps a newer MCU file to test with, or any older MCU files to downgrade (if downgrading is possible).
Thank you in advance,
best regards
Adrian
ps.: my car's model code is: 12372UY, Peugeot RCZ 1.6THP with factory JBL amplifier
nhadrian said:
Hi,
I have the same well-known issue that exists with most Android head units and Peugeot JBL amplifiers.
The amplifier only works until volume knob is adjusted, the issue is technically the same as in this video for example:
Of course, "Amplifier" is enabled in factory settings menu.
MY head unit looks the same as in the video but with PX6 and Android 11.
MCU ver: MTCH_MX_V3.81_1
When I ordered this unit, I asked 3 times the distributor if the head unit is complatible with JBL amplifier and he assured about compatibility.
Till then I discussed with the distributor many times but it seems they are lost and I afraid they won't provide any working solution...
Since all ingoing and outgoing CAN communication works otherwise (ie. remote control buttons, car menu controlling, parking radar, car diagnostics reading, VOLUME ADJUSTMENT, etc.) I'm quite sure this issue is realted to firmware not to hardware (CAN decoder). I read some posts on the internet where MCU update solved this issue.
So I'm looking for any suggestions or perhaps a newer MCU file to test with, or any older MCU files to downgrade (if downgrading is possible).
Thank you in advance,
best regards
Adrian
ps.: my car's model code is: 12372UY, Peugeot RCZ 1.6THP with factory JBL amplifier
Click to expand...
Click to collapse
Hi...
Try with CHS based software for your device, it is android 10, do a backup of your software first just in case, then update from USB, test and see if works
SOFTWARE : https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
If not working, try with EXTRON softwares. Find it on this forum , there is a link for it somewhere in posts.
If issue is not with firmware (if it is the same problem) try leveling audio input (hidden/factory menu/admin menu - asks pin code) to a correct one in menu other or audio or what else is in admin menu.
Anton TNT said:
If issue is not with firmware (if it is the same problem) try leveling audio input (hidden/factory menu/admin menu - asks pin code) to a correct one in menu other or audio or what else is in admin menu.
Click to expand...
Click to collapse
I tried this first but didn't help.
Anton TNT said:
Hi...
Try with CHS based software for your device, it is android 10, do a backup of your software first just in case, then update from USB, test and see if works
SOFTWARE : https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
If not working, try with EXTRON softwares. Find it on this forum , there is a link for it somewhere in posts.
Click to expand...
Click to collapse
Can you please tell me in a few words what is the easiest way of backing up my compete system fw? I only found how to upgrade, but not a complete system backup. Thank you in advance.
nhadrian said:
Can you please tell me in a few words what is the easiest way of backing up my compete system fw? I only found how to upgrade, but not a complete system backup. Thank you in advance.
Click to expand...
Click to collapse
There is a backup option in admin/hidden menu (pin 8888 or 0000 or what ever it is). Just plug nUSB and transfer all files, including system image (xxxx.img etc.).
If not there I do not no where it is. Every device is different. If not found, prior to update, ask seller to give you original software if need to install again. (NOTE: softwqare is as is, and seller or other like myself that are giving you this update are not responsible for any misconduct or defected softwares after updates, so watch what you are doing)
Thank you for your kind reply. I made a short video about the model and build details as well as the Factory menu. Unfortunatelly there aren't any backup option. I was asking the supplier for the factory firmware, I hope they'll send it to have a backup.
Otherwise it looks like this is a PX6 "A-Media Auto" head unit. Does the fw you sent just fit for this taking into account the details in my video?
Refer MTCD forums, unit is a MTCD variant.
You will also find Yandisk based MCU and Android firmware. Stay with same MCU type (MX).
marchnz said:
Refer MTCD forums, unit is a MTCD variant.
You will also find Yandisk based MCU and Android firmware. Stay with same MCU type (MX).
Click to expand...
Click to collapse
Thank you for the information. Do you know what is the safest way of downgrading to A10? Most of the firmwares are A10 or earlier, and it is noted that only for up to A10.
nhadrian said:
Thank you for your kind reply. I made a short video about the model and build details as well as the Factory menu. Unfortunatelly there aren't any backup option. I was asking the supplier for the factory firmware, I hope they'll send it to have a backup.
Otherwise it looks like this is a PX6 "A-Media Auto" head unit. Does the fw you sent just fit for this taking into account the details in my video?
Click to expand...
Click to collapse
What kind of Peugeot is it ? What model ?
If 301-308 version use different PSA canbus settings untill all commands and apps work.
Will look for my psa settings f canbus and took picture of it.
Anton TNT said:
What kind of Peugeot is it ? What model ?
If 301-308 version use different PSA canbus settings untill all commands and apps work.
Will look for my psa settings f canbus and took picture of it.
Click to expand...
Click to collapse
It is a 2010 Peugeot RCZ with factory JBL amp.
My current canbus adapter is a Simple Soft PSA one (PA-SS-05) and canbus setting is Nr.61 - as shown on the video. I have everything working like reverse radar, steering wheel remote buttons, A/C feedback, etc. The only thing is the JBL that do not remain on.
UPDATE: I got an update.zip from the seller. It was a downgrade to Android 10. After installing the update, device stuck at boot logo (peugeot animation). Sometimes reset itself, like in 10 minutes or so. Can it be recovered somehow?
nhadrian said:
UPDATE: I got an update.zip from the seller. It was a downgrade to Android 10. After installing the update, device stuck at boot logo (peugeot animation). Sometimes reset itself, like in 10 minutes or so. Can it be recovered somehow?
Click to expand...
Click to collapse
You must update again a let it finish update till inside android system, then remove usb or sdcard wich contains image for system and reboot with pin code, enter 4 or justbtake off ignirion key. As soon as gets inside android system, purge memory from factory menu, with pin 8888 or what is yours to get in. Go to setting for memory if you have it and it must not write to any sd card or usb attached in system. As soon system is recognozed it will take settings from internal memory not from usb or cards.
Hi, did you manage to update successfuly?
Anton TNT said:
Hi, did you manage to update successfuly?
Click to expand...
Click to collapse
Unfortunatelly not. Still waiting for the seller to provide me a firmware in img. Or a flash tool.
I can't install the update.zip by RKTools, not recognized file format.
But at least I know how to enter recovery mode and drivers are installed on my PC, RKTools recognize it.
I tried to flash the firmware you posted here earlier but the tool quitsas soon as I try to load it.
nhadrian said:
Unfortunatelly not. Still waiting for the seller to provide me a firmware in img. Or a flash tool.
I can't install the update.zip by RKTools, not recognized file format.
But at least I know how to enter recovery mode and drivers are installed on my PC, RKTools recognize it.
I tried to flash the firmware you posted here earlier but the tool quitsas soon as I try to load it.
Click to expand...
Click to collapse
Your device is an MTCD variant. Refer mtcd forums and my recovery threads. If SDCARD recovery does not work, use OTG recovery per my posts
Here is the OTA update.zip I got from that idiot chinese seller:
1.01 GB file on MEGA
mega.nz
He said it is a complete firmware, this is the folder content (zip is 1 Gig):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anybody help me converting to an .img for OTG flashing, or an SD-card image (which I can write to an SD-card with balena etcher)? I'd be really thankful (donate on paypal if succeed), I'd still remain on "official" firmware for my device, for a possible warrantee dispute...
Thank you guys in advance!!!
I still don't know how to install any firmwares in .zip container (either my factory one, hal9k or malysik).
My device has black screen during recovery boot, so the only chance is using the rockchip tools or SD card method. I was trying to find topics on how to convert the .zip package to img but can't find any information.
Please someone help!
nhadrian said:
I still don't know how to install any firmwares in .zip container (either my factory one, hal9k or malysik).
My device has black screen during recovery boot, so the only chance is using the rockchip tools or SD card method. I was trying to find topics on how to convert the .zip package to img but can't find any information.
Please someone help!
Click to expand...
Click to collapse
Use .zip file in usb, if not readable prior to startup of unit, press and hold Reset button - a litlle hole on device - and keep holding while usb with update is in port. Release reset button and system will boot up and read usb files and update device. If not read, unzip files inside .zip and place them in usb , just two files .img and .upd and try again same procedure with reset button.
Anton TNT said:
Use .zip file in usb, if not readable prior to startup of unit, press and hold Reset button - a litlle hole on device - and keep holding while usb with update is in port. Release reset button and system will boot up and read usb files and update device. If not read, unzip files inside .zip and place them in usb , just two files .img and .upd and try again same procedure with reset button.
Click to expand...
Click to collapse
Neither of this method works. Every time it boots into the main system (and the infinite Peugeot logo).