JOYING JY-UQ139N4G-H 1280x720 Update firmware dated 8-12-2022 - Android Head-Units

Just received this update from 'Mandy' of Joying Support. It's for model JY-UQ139N4G-H 1280X720
MIPI SCREEN UIS7852 4GB 64GB and dated 8-12-2022. Since I could not find this on their site, I'm posted the location
on this thread. I also don't know how long it's going to be available where she posted it. If you need it or if someone
is collecting firmware for these units, it's located here:
Google Drive - Virus scan warning
drive.google.com
This unit on their web site:
https://www.joyingauto.com/joying-9-inch-double-din-android-10-0-car-stereo-upgrade-with-bluetooth-5-1-4gb-64gb.html
Might want to backup your apps before installing in case it does a wipe without notice!!!

Related

Joying JY-JM001N2 - MCU Update Message

Hi, I searched around but was unable to locate a member with a similar problem.
Issue:
- I applied the Joying 01 March, 2018 firmware to my JY-JM001N2. MCU version is 5.25 800*480
- All seemed to go fine, head unit rebooted
- When the unit started I get an MCU update screen. The top is green with a MCU and some Chinese writing which I do not understand
Has anyone experienced this and have tips or tricks they can pass along?
Many thanks,
Dan
if everything work, and u just need to hide this message u can use the sofia xposed module
danomite01 said:
Hi, I searched around but was unable to locate a member with a similar problem.
Issue:
- I applied the Joying 01 March, 2018 firmware to my JY-JM001N2. MCU version is 5.25 800*480
- All seemed to go fine, head unit rebooted
- When the unit started I get an MCU update screen. The top is green with a MCU and some Chinese writing which I do not understand
Has anyone experienced this and have tips or tricks they can pass along?
Click to expand...
Click to collapse
As you are on the stock joying ROM, you probably downloaded the wrong firmware. Did you download the 1024x600 version or the 800x480 version?
surfer63 said:
As you are on the stock joying ROM, you probably downloaded the wrong firmware. Did you download the 1024x600 version or the 800x480 version?
Click to expand...
Click to collapse
Yeah, initially I thought I applied the wrong one. I downloaded it from Joying again and applied with the same issue.
Firmware - 01 March, 2018
MCU: 5.25
Resolution: 800*480
drive.google.com/file/d/1SiHcRPihrfQzxrkRy5qe0EEAjegQJ-0M/view
Interesting, I have two Joying head units, one JY-JL001N2 and a JY-JM001N2. Both use the same firmware and the JL took fine whereas the JM has the issue. I sent an email to Joying because I just got the JM and the Zlink wasn't working right. I wanted to reapply the latest firmware to see if it'll help but just caused the MCU issue. They replied asking for the download link, I suspect they're checking if I applied the wrong one.
I successfully applied an older firmware from around August 2017, no more message but the radio and sound is all messed up. I then reapplied the latest firmware with the same MCU message.
Thanks!
RoNeReR said:
if everything work, and u just need to hide this message u can use the sofia xposed module
Click to expand...
Click to collapse
Thanks, I'll give it a shot!
Well, I ended up using an old firmware from around August 2017 and the MCU message went away. I then installed the latest March 2018 update and it finally took. I’m posting this follow up so if someone else has a similar issue they can give this a go.
Joying support wasn’t very helpful although they do reply quickly. I think they should just have an auto reply email saying “do a factory reset” as this is basically all the advice they seem to give.
Hi,
Having same problem with you. Can I have link to download 2017 firmware.

Mekede Head unit

Hi guys, i've purchased the android unit with this firmware (below in the photo) but how i recognize the exact update for my head unit?
Hi mate, after a deep research i found that this device is the same as "Ownice c500". The firmware for this - https://forum.xda-developers.com/an...d-units/ownice-c500-firmware-updates-t3560984 . My "Mekede" comes with Android 8.0, so i`m not update yet /didn`t find firmware for 8.1/. So to be sure you have to ask for compatible in link thread, just to be 100% you won`t brick your device.
Download an Android version checker.
I just installed my mekede unit which is supposed to be android 8.1. On checking I find it's actually android 6.0
The seller on aliexpress is not answering my messages and I'm beyond the buyer protection time limit.

Is my generic brand H.U. compatible with Joying (rooting)/JET-apk

Hi all,
of course the typical question which is " Is my generic brand H.U. compatible with Joying (rooting)/JET-apk? kindly help me find out. I just got this new 8.1 inch Head unit for my Mazda 6 2019 i want to root if possible so i would like to know if it's joying rooting enabled. "
attached hwgetinfo zip file Named Mazda62019 in the below link. Thanks.
unfortunately i can' t post links here as this is my first post. any advice would be appreciated.
faisaljed18 said:
Hi all,
of course the typical question which is " Is my generic brand H.U. compatible with Joying (rooting)/JET-apk? kindly help me find out. I just got this new 8.1 inch Head unit for my Mazda 6 2019 i want to root if possible so i would like to know if it's joying rooting enabled. "
attached hwgetinfo zip file Named Mazda62019 in the below link. Thanks.
unfortunately i can' t post links here as this is my first post. any advice would be appreciated.
Click to expand...
Click to collapse
I updated the HWGetinfo.apk this morning. See this post (#1528) for extra screenshots.
You can send me a PM. As far as I know that will allow you to attach a zip and otherwise you can post a link to your google drive, mega download, yandex or so, if you upload the zip there.
I got your PM.
Your unit is a FYT unit. It can be rooted according the mentioned "howto root Joying SC9853i".
The vendor/manufacturer id is 1 ([ro.build.fytmanufacturer]: [1]).
You cannot use the JET apk at this moment.
I will also see if I can think of something smart to apply to all vendors.
All FYT apks (on the FYT SC9853i units) start with 1900, then 2 digits for the manufacturer id, then a set of digits for the version.
And they start with 1800 on the FYT PX5 units.
surfer63 said:
I got your PM.
Your unit is a FYT unit. It can be rooted according the mentioned "howto root Joying SC9853i".
The vendor/manufacturer id is 1 ([ro.build.fytmanufacturer]: [1]).
You cannot use the JET apk at this moment.
I will also see if I can think of something smart to apply to all vendors.
All FYT apks (on the FYT SC9853i units) start with 1900, then 2 digits for the manufacturer id, then a set of digits for the version.
And they start with 1800 on the FYT PX5 units.
Click to expand...
Click to collapse
thank alot ..you're a life saver .. one more question i have different firmeware than the one posted on the thread you shared where they specified firmware 9853i 800X480 2019.3.20 while i have 9853i 800X480 2019.01.10 , any advice ..
faisaljed18 said:
thank alot ..you're a life saver .. one more question i have different firmeware than the one posted on the thread you shared where they specified firmware 9853i 800X480 2019.3.20 while i have 9853i 800X480 2019.01.10 , any advice ..
Click to expand...
Click to collapse
Try to make a new boot image based on your unit and firmware. Boot images can contain dependencies with the rest of the firmware. That's why you always should create a boot image for your firmware release.
And as further info: The FYT units can use each others firmware as long as the MCU binary/firmware is updated at the same time. Some firmware releases come without MCU binaries. That will give conflicts as the MCU firmware also contains the manufacturer id and checks whether that id is also in the Android properties. If not, it will still work in most cases but you can run into issues/instabilities and you will always see a yellow banner on top of your screen giving some MCU error.
Not only that: sometimes new Android firmware comes with new MCU firmware because new functionality is built in, or the MCU firmware contains a bug (like in the last 14 August 2019 Joying firmware).
So if you want to flash an updated Joying firmware onto your unit, make sure you have a firmware release with MCU firrmware/binaries.
And when you do that make sure you have a firmware version really belonging to your unit, so that you can reflash when necessary.
surfer63 said:
Try to make a new boot image based on your unit and firmware. Boot images can contain dependencies with the rest of the firmware. That's why you always should create a boot image for your firmware release.
And as further info: The FYT units can use each others firmware as long as the MCU binary/firmware is updated at the same time. Some firmware releases come without MCU binaries. That will give conflicts as the MCU firmware also contains the manufacturer id and checks whether that id is also in the Android properties. If not, it will still work in most cases but you can run into issues/instabilities and you will always see a yellow banner on top of your screen giving some MCU error.
Not only that: sometimes new Android firmware comes with new MCU firmware because new functionality is built in, or the MCU firmware contains a bug (like in the last 14 August 2019 Joying firmware).
So if you want to flash an updated Joying firmware onto your unit, make sure you have a firmware release with MCU firrmware/binaries.
And when you do that make sure you have a firmware version really belonging to your unit, so that you can reflash when necessary.
Click to expand...
Click to collapse
Are MCU's interchangeable between manufacturers? Such as can a non-joying Sofia unit use a Joying MCU?
adamlee06 said:
Are MCU's interchangeable between manufacturers? Such as can a non-joying Sofia unit use a Joying MCU?
Click to expand...
Click to collapse
I don't have experience with this so this is a theoretical approach, but in general I would say NO.
There are 3 big motherboard/MCU manufacturers: FYT, STT (QD) and Microntek (MTCB/C/D/E). They make the motherboard and MCU and the MCU firmware. And then you have Atoto and a few others who use a Mediatek chip-based motherboard/MCU and assemble the units around it. I do not know who really manufacturers these motherboards/MCUs.
All the resellers like Joying, Funrover, Dasaita (Hot Audio), Xtrons, Seicane, all the "unnamed", etc., etc., use one of the 3 mentioned motherboard/MCU manufacturers. The resellers only assemble the motherboards into their units.
Theoretically (again) all FYT motherboards/MCUs for a specific chipset (Sofia 3 GR / PX5 / SC9853i) are 100% compatible.
All MTC motherboards/MCUs for a specific chipset (3188/PX3/PX5/PX6) are indeed 100% compatible.
So between motherboard/MCU manufacturers they are certainly NOT interchangeable, also because hardware might differ and that is where the MCU plays its pare.
Between different brand units sharing the same motherboard/MCU manufacturer and the same chipset they should be interchangeable.
And with regard to hardware upgrades: In most cases those resellers offer you an upgrade step from PX3 to PX5, or Joying PX5 to Joying SC9853i.
surfer63 said:
Try to make a new boot image based on your unit and firmware. Boot images can contain dependencies with the rest of the firmware. That's why you always should create a boot image for your firmware release.
And as further info: The FYT units can use each others firmware as long as the MCU binary/firmware is updated at the same time. Some firmware releases come without MCU binaries. That will give conflicts as the MCU firmware also contains the manufacturer id and checks whether that id is also in the Android properties. If not, it will still work in most cases but you can run into issues/instabilities and you will always see a yellow banner on top of your screen giving some MCU error.
Not only that: sometimes new Android firmware comes with new MCU firmware because new functionality is built in, or the MCU firmware contains a bug (like in the last 14 August 2019 Joying firmware).
So if you want to flash an updated Joying firmware onto your unit, make sure you have a firmware release with MCU firrmware/binaries.
And when you do that make sure you have a firmware version really belonging to your unit, so that you can reflash when necessary.
Click to expand...
Click to collapse
Hey surfer63,
Thanks for the info! I recently got a new unbranded unit that I believe is a FYT. I'm going to run your HWinfo apk when I get chance later today but trying to clarify some details. Photo included for reference since I haven't run HWinfo yet.
I've messed with my old MTCB unit a bunch but I'm approaching this one a bit more cautiously. Am I able to follow the steps in the Developer.zip to create the patched boot.img for my unit's firmware? Knowing that the provided files are based on Joying, would I need to get the firmware file from the seller first before proceeding or does the magisk patching process make this unnecessary?
EDIT: HWGetinfo.apk was useful. My unit is apparently not an fyt. Haven't looked at the log yet. I was poking around some files and found some flyaudio references but I've not heard much about those here. Still curious about the boot.img patching though. Thanks.
{
"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"
}
RabbidHampster said:
HWGetinfo.apk was useful. My unit is apparently not an fyt. Haven't looked at the log yet. I was poking around some files and found some flyaudio references but I've not heard much about those here. Still curious about the boot.img patching though.
Click to expand...
Click to collapse
Your firmware is not for an FYT either. It is Android 8 for a PX5.
I don't think you can use the developer zip option. The Magisk way of patching the boot.img will certainly work, but you can't flash that patched boot image the way it is described in the 9853i thread.

Root and custom Firmware Android Pie VW Unit

I'm looking for someone who can root my original volkswagen factory android switch, I could pay for it. I'm sorry if I posted in the wrong place.
SO is Android Pie
i have original firmwares if need investigate.
Post details about the unit.
Post Android system information including MCU version.
upload your firmware. maybe it is possible to root.
I will upload it today
Latest Firmware
Below you see the Version of unit
marchnz said:
Post details about the unit.
Post Android system information including MCU version.
Click to expand...
Click to collapse
I cant see the details about info from unit, maybe the software can show it. i want root and instal 3trd party apps on this units, like youtube and netflix.

4 core allwinner rom 32gb ddr3 1gb 1024x600

Hello everybody
I buy this unit for my car but it's too slow
I think it's a version 10 fake of android
Can you think i can downgrade with an optimized firmware. I have a sd card emplacment
You can see the details of software
Thank you for your help
Open "system" tab in CPU-Z and check API level.
Then compare with this:
Android version history - Wikipedia
en.wikipedia.org
I bet that you got Android 6 or 8.1 already.
It seems be a real android 10, do you than i can find a firmware faster ?
Hi, if you have online update for canbus, MCU and system in factory or developer settings please update softwares there.
If not having this option contact your seller to improve device - ask firware update system.
Thank you for your response
I don't have developper settings and the seller don't respond to my mail.
Search the net I can't help you I do not know exact model and chipset of this device.
Thank you Anton
Hi
I find screenshoots to find model, I contact Eincar to know il they have firmware

Categories

Resources