yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
With my remarks you could have checked the properties.txt yourself, but anyway: It is a FYT compatible. Your manufacturer id is

[ro.build.fytmanufacturer]: [1]

and your

[sys.fyt.bluetooth_type]: [1]

Which means it is the general purpose model sold to many small resellers.

The Airco software is different though. The CANbus seems different as well and the android and boot image build date is 22 August 2020. This is by far the newest firmware I have seen. This might explain the change in the CANbus and airco software. The MCU firmware is of 17 July 2020, which is also newer than anything I have seen.

The properties also mention:

[ro.build.version.release]: [10]
[ro.build.version.sdk]: [29]

This means that your Android version is indeed 10, and not 8.1 like all the other 9853i's.

This might also mean that Joying and T'eyes "might" come at some time with Android 10.

However, it also means that you should not flash your unit with Joying or T'eyes firmware as these are all 8.1 with older MCU firmare, which might give conflicts.
[FYT Android Head Units] janojj81:
Hello

How can I check if my unit is Joying SC9853i?

i wanted root because ppp widget doesn't work

[sys.fyt.bluetooth_type]: [5]

[ro.build.fytmanufacturer]: [53]

[ro.build.host]: [bsp-04]

[ro.build.id]: [OPM2.171019.012]

[ro.build.product]: [sp9853i_1h10]

[ro.build.version.release]: [9.0]

[ro.build.version.sdk]: [27]
[FYT Android Head Units] bennyasf:
so does that mean I cant root with this method? and is there a way for me to dump the rom for others to use it? I mainly want root to install zlink since my 4gb model didnt come preinstalled with it. how can I move forward with rooting? before I had this info I tried updating to the offical joying software and no update popup ever shows.
[FYT Android Head Units] bennyasf:
I got the rom here https://drive.google.com/file/d/1xf...imconversation.0.0.2f1a3e5fbLFqw5&usp=sharing
[FYT Android Head Units] surfer63:
Yes, you can use that method, but as you will be the first on such a new firmware I absolutely recommend to have firmware ready in case "something" fails. And like mentioned: I would also recommend not to install Joying firmware as it is older (8.1) and not 10.0! And most probably canbus controller and MCU firmware is also different.

Anyway: You don't need root to install Zlink.

Did you use the file manager and did you look in the /oem folder? On all Joyings and T'eyes units the zlink apk is located in there and by double-clicking you can install it. I assume it is the same for all other FYT compatibles.
[FYT Android Head Units] bennyasf:
I got the rom here https://drive.google.com/file/d/1xf...imconversation.0.0.6baa3e5fljS9rp&usp=sharing , and there is no oem folder inside and the rom doesnt have zlink i see the folder for zlink in file manager but the actual app isnt there, and installing the app normally leads to a mismatch error
[FYT Android Head Units] surfer63:
This is a FYT but definitely a new generation. "Our" SC9853i Android 8.1 units are 6521 units. Your Android 10 unit is the next generation 6315 unit.

You can NOT use a Joying or T'eyes firmware to flash your unit.

You first need to check if the Magisk rooting method already supports Android 10.
[FYT Android Head Units] bennyasf:
i believe it does, how would i go about rooting? or installing zlink with no oem folder?

edit: was able to patch the boot.img but now i really dont know where to go from here
[FYT Android Head Units] surfer63:
I ask it again: Why do you want to root your unit? I know perfectly well how to root my unit and the 2 previous ones, but in the last 2 I removed root again. It doesn't add anything extra.

So really ask yourself why you need root before rooting your unit.

And Zlink might simply not be compatible yet with Android 10.
[FYT Android Head Units] bennyasf:
the folder is there just no included app, ive seen reports of it working on android 10 also. and same reason as before to use root explorer to install zlink and remove apps i dont use and install the mods i see people use.

edit: also would make it easier for people in the future with my device who also want to root.

edit 2: would it be possible to make a modified version of the developer.zip to sign a zip file for me to flash the patched boot.img?
[FYT Android Head Units] bennyasf:
i was able to make a root file with the developer zip but have no idea if it will work, is it possible to edit the developer zip to make the root file for my unit?
[FYT Android Head Units] surfer63:
No. It needs to be done on the unit itself. So either on your unit or an identical unit.
[FYT Android Head Units] bennyasf:
How do i do it?
[FYT Android Head Units] surfer63:
That is perfectly described in the Howto.rtf in the developer.zip
[FYT Android Head Units] gamer765:
Your asking too many questions. If you can't follow instructions, perhaps this isn't something you should be attempting in the first place, especially since there's no stock Joying firmware posted yet to recover from. As surfer63 mentioned, there is nothing gained from rooting. You can do all the mods you're describing without root. You can replace files using the lsec.sh method. I rooted my unit, but that's because I'm using it for research purposes in modding libsyujni where I need to replace it multiple times. Other than that, there really is no need to root.
[FYT Android Head Units] bennyasf:
I already followed the directions in the developer.zip and created the root files, but since it’s for the old motherboard would it still work? I tried flashing and it just gives me an error when it tries to flash the patched boot.img

---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------

I know what I’m doing... and i have my rom to recover from that i posted a link to. And my rom doesn’t include an oem folder and if i try changing anything in the actual firmware it gives an error while flashing. That’s where i get stuck since it just says error and nothing else.
[FYT Android Head Units] surfer63:
The developer.zip uses a different lsecupdate and the contents of the updater-script are different. The developer.zip is indeed for the 6521_1 models and you need the 6315_1 version.

Find attached a zip containing the lsecupdate for your unit and inside the 6315_1.zip the correct META-INF structure with the correct updater-script (see inside META-INF/com/google/android/ for the updater-script. Note that the updater-script has unix line-endings, not windows line-endings)

The patched boot image you created needs to be named boot.img, NOT patched_boot.img. Add this boot.img (with name boot.img) to the 6315_1.zip

Signing the zip remaines the same.

Copy the signed 6315_1.zip and the lsec6315update to a usb-stick.

Try to flash it.
[FYT Android Head Units] bennyasf:
Did everything you said but it gives an error still then reboots into the system.

edit: seems i cant even flash the firmware at all anymore leads to an error or no command and just reboots into system
[FYT Android Head Units] cottec:
i just got my 6,2" display replaced with the 7" version

did this in order to upgrade from a wrong described UOS04N4GS with a UOS03N4GS in order to have 1024x600 instead of 800x480 res

when i first booted it, it was showing some coloured lines on the right and bottom (probably the "additional new" pixels)

it asked me to recalibrate the touchscreen which was recognized as the bigger one, however, the resolution was still displayed as 800x480

i reflashed the 2020-04-09 firmware hoping this would solve the issue but it didnt...

going back to an old 2019-11-28 doesnt work as the device runs into an MCU update error before flashing the old firmware

according to the device information its a G23 and hence should be the newest version (compared to the G32)

does anyone know how to convince the unit to put out the higher res?
[FYT Android Head Units] gamer765:
You need to flash a display configuration file for your lcd. Better to ask Joying for the file rather than flashing random ones found online.
[FYT Android Head Units] cottec:
support just sent the files, will these be interesting for anyone around here?
[FYT Android Head Units] gamer765:
Wouldn't hurt to post them. Just add the disclaimer that not to flash unless you know what you're doing.
[FYT Android Head Units] bennyasf:
can I get help with root, I need root for an xposed module for carplay with steering wheel control
[FYT Android Head Units] surfer63:
You are the first doing this on a brand new device on a new Android 10. We do not have expertise here.

Secondly: which Magisk are you using? The version 18.x from the developer.zip? The first Magisk version fully supporting Android 10 is Magisk V20. You might try using a Magisk 20+ version from the Magisk download site.

First discussions now also start on 4pda about the UIS7862 with the 6315 MCU. You might need some patience.

And using Carplay on the latest, fastest Android unit? Why ????

If you simply want to use your phone, why not simply buy a low-level, cheap unit that supports Carplay?

From my point of view this is a complete waste of money and modern, powerful headunit resources.

:confused:
[FYT Android Head Units] bennyasf:
That’s exactly why i bought this android head unit, it was cheap and was meant for CarPlay nothing else, seems weird that you think it’s a waste of resource like the head unit can do that most, it still lags and isn’t as fast as you are making it out to be, and I’ll figure it out on my own then or wait like you said.
[FYT Android Head Units] surfer63:
You say it lags, can you tell us what lags? And compared to what or which other head unit?

I'm not trolling but as this unit should be faster than the previous ones, I am really interested. I guess that users wanting to buy such a new uis7862 unit really would like to know as well.
[FYT Android Head Units] bennyasf:
I had the 2gb android 8.1 version, bought this first for CarPlay but it wasn’t internal so i returned it, had that for about 3 weeks and that one wasn’t too bad with lag but it was slow, now i have the 4gb model with android 10 (was a surprise to me since it’s advertised as android 8.1) this one is faster but still hiccups and lags in random areas, it’s a lot better than the 2gb model but it’s using the old CPU so personally I’d say it’s still slow considering joying just uploaded a video of the new android 10 din they released and it uses a different cpu i believe since they don’t list it, it’s a guess. Anyways overall the system runs fine for the most part but will lag in areas like changing a/c or opening maps, sometimes it just freezes for a good 2 seconds, but better than the 2gb model, this could also be a firmware issue since it’s new and they haven’t released updates yet, like zlink was suppose to be in my firmware but they decided not to include it even though it’s advertised for internal CarPlay but I’m getting the new firmware this upcoming week. I’ll keep you updated but i wouldn’t say it’s worth upgrading your current unit unless you have the 2gb model and want something that stutters and lags less. (Still lags a bit tho)

Edit: also you can’t do adb over wifi i enabled the settings for it but the pop up immediately goes away which i believe has to be a firmware thing they setup because it seems almost intentional, no other ui i can change to to allow the pop up. And i believe they also messed with recovery because with the update they sent me all i get is error or no command when trying to flash.
[FYT Android Head Units] surfer63:
No, that won't work. The latest releases are "release" releases and no longer "debug" releases or "user" releases.

ADB over WiFi simply won't work on "release" releases. That's Android builtin behavior.
[FYT Android Head Units] bennyasf:
i have an android 10 and 11 phone that say different and my old heatunit could also do adb over wifi

---------- Post added at 05:09 PM ---------- Previous post was at 04:40 PM ----------

For the new android 10 models something is very off, tried flashing the Russian firmware and got an error again rebooting to recovery just gives a no command and boots back into the OS
[FYT Android Head Units] surfer63:
It has nothing to do with Android 10 or 11. I meant the lastes releases in head units, like the SC9853i and now the uis7862.

If you look in the system info or directly in the properties.

For the FYT SC9853i models you will see something like:

ro.build.display.id=OPM2.171019.012 release-keys
ro.build.version.release=8.1.0
ro.build.tags=release-keys
ro.build.description=sp9853i_1h10_vmmTos-user 8.1.0 OPM2.171019.012 14212 release-keys
ro.build.fingerprint=SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/14212:user/release-keys
ro.fota.version=OPM2.171019.012 release-keys_20200407-1215

For the FYT uis7862 units you will see:

ro.system.build.fingerprint=SPRD/ums512_1h10_Natv/ums512_1h10:10/QP1A.190711.020/32116:user/release-keys
ro.system.build.tags=release-keys
ro.system.build.version.release=10
ro.build.display.id=QP1A.190711.020 release-keys
ro.build.version.release=10
ro.build.tags=release-keys
ro.build.description=ums512_1h10_Natv-user 10 QP1A.190711.020 32116 release-keys

The "release-keys" makes that the kernel will no longer accept these ADB over WiFi requests.
[FYT Android Head Units] bennyasf:
ahh i see, hmm. I would assume rooting can fix this issue or im i mistaken on that?

by chnace do you know russian digits? im trying to go on the 4pda forum to ask if they get an error when trying to upgrade the firmware. its the the android logo with error thats it.
[FYT Android Head Units] bennyasf:
{Mod edit: Quoted post has been deleted}

was able top guess the captcha, anyways thanks for all the help, ill see if they know why im getting error/no command when trying to flash something

If i dont have allapp.pkg and have allappupdate.bin is there a way to extract that and put apps i want in there? apkapp doesnt see the file
[FYT Android Head Units] gamer765:
This post has information regarding the new format and how to extract it. Packing it would be the reverse. https://xdaforums.com/showpost.php?p=83542227&postcount=1898
[FYT Android Head Units] Rami3073:
Hey I did a quick search of the thread about any

queries regarding Joying’s new Android 10 head units using a new chipset UIS7862, rather than SC9853i, having root but seems to be no clarity on that. So just asking if root is possible or perhaps in the making for the new products?
[FYT Android Head Units] kersian:
Just to check, does signing works for other branded fyt units?
[FYT Android Head Units] dragon-tmd:
Check yourself: https://play.google.com/store/apps/details?id=mark.fakedevicetest&hl=de
[FYT Android Head Units] riz619:
Hey there I'm wondering if you can help me. I'm trying to root my joying head unit.. I placed both the files you listed onto a USB, the head unit picked it up and a message popped up saying its about to update. However, all that happened was the screen went black for 2 seconds then the head unit rebooted back up. Once it rebooted, the update message popped up again and the same thing happened. The device kept rebooting until I removed the USB. The head unit is working fine but there is no root access. Am I doing something wrong? any help will be appreciated. Thank you.
[FYT Android Head Units] surfer63:
Don't troll. The units are real Android 10 units. The firmware has been checked.

This is the new unit, not a SC9853i unit.

Download the firmware yourself and check it yourself (if you even know how to do that).
[FYT Android Head Units] deedeebulldog:
No command

I am having issues with rooting. I am on the latest firmware from April. The process looks normal until i get a message that says "No command". Then it just reboots. I am using the image from post #351. Really the only reason I am trying to get root is because after the last update my screen dimmer no longer works. It is at 100% no matter how low I put it. I am having to use a screen filter at night and I would like to auto launch it at certain times. Maybe I will try re flashing the stock image and it will fix itself.

Never mind. I searched No command and found the answer. It did not fix my screen brightness though.
[FYT Android Head Units] marcus82:
hi guys, we're 3 friends with Prelingcar tesla style head unit with this cpu. We've installed latest android 10 firmware and now 2 of these head unit are withtou reverse camera; moreover, we're without parking sensors and I think it's related to che mcu version. We've carchoose.apk to download it but before first update from this apk, parking sensors were working!! Then, anyone has mcu file for FORD FOCUS MK3?
[FYT Android Head Units] GrubcioPL:
MCU Problem with update, no sound

Hello!

I am having trouble updating my MCU. I've been randomly losing this driver for a while now. After starting the car, the radio has a problem with starting (android works fine, no sound from the radio) when the MCU starts, the version is unknown. After 5 minutes, the device resets, sometimes the MCU will load and everything works until the car is turned off again.

During the update (SD Card FAT32, empty only with the original files from the joying blog - Trying few others), the information that SDCARD cannot be mounted

It goes to the line where the STM32UD was updated correctly, then the line with the description: "2019.09.07 10:40:57 JY_53_C63L_H32P48F64_Ver: 1.0" - the device is locked here, nothing happens - after 5 minutes, restart the device and loop.

How the device works properly MCU Version is:

2019.09.07 10:40:57 JY_53_C63L_H32P48F64_Ver: 1.0

CPU Info:

Intel X86_Octa-Coire 1.8Ghz SC9853i@4.0GB + 32 GB

Android 8.1

What should I do, what file should I use? Radio is:

Joying JY-UO135N4G

//EDIT:

I don't speak perfect English, I use a translator. For thorough help, sending any files, I am able to use a grant. I am asking for help in solving the problem.

I am asking for information which data is still needed to solve the problem. The device is rotated.

After struggling to start the device, I did not have an MCU, I used Joying Extra Tool and the option -Rebot Option - Soft Reboot (Gui only, sufficient for all apk replacements)

After starting the car, the panel LEDs light up for 2 seconds and then they turn off, the device usually starts after a few minutes, the vehicle's logo is displayed with a countdown from 5 to 0, the device stops on the number 0. I have to hold power off and manually reset the device, then Andorid is charging correctly.

Twice after using it, the device started working properly. The MCU showed up in the settings.

System info:

Kernel: #451 SMP PREEMPT FRI MAR 29 2019

Platform: (24)6313 LF Full band carplay

touch: 911_1060(263efcda)E:0

APP 1024x600 2019-11-28 15:50:42

System 2019-11-28 09:40:06 Thursday
[FYT Android Head Units] energy_drink:
I just updated my 8inch 4/64gb headunit to latest (I suppose) firmware ( 2020-04-09).

Is it possible to root this firmware yet? Is any of files from 1st post working with this update?

If not, any other way to root?

Thanks for any help.
[FYT Android Head Units] lucvan:
Hi, I am looking to root my headunit, but the firmware version is dated 2020-06-22 so I do not have a dump of it to modify using the method here. Can I just use the old bootloader and root?

[edit] - the unit is a JY-VO130N4GSN
[FYT Android Head Units] wenefe1:
Hello you experts

I have a Joying 10.25 universal unit Intel 1240 x 480 unfortunately flashed the wrong MCU and now I only have about 30-40% background lighting can help me? I read that you can adjust the brightness in the build.pro

for that you need root right I don't have that and I can't find Boot.img for

9853i OS 1280X480 Old UI 2019.11.28 mcu 32

Pleace Help me

Thanks Werner
[FYT Android Head Units] surfer63:
Why don't you download the correct MCU firmware and flash that one?
[FYT Android Head Units] JMeister234:
I have a Atoto S8 ultra. I wanted root. I compared the patchedboot.img and it was comparable to Atotos boot.img for the same chip, resolution and GPU.

I downloaded the 1024x600 and it didn't brick my head unit.

But the radio stopped working, and the red letters "Need check active. ID 1.Area 2"

- what is that error referring to?

I can revert back to the Atoto firmware, but I'd really like root.
[FYT Android Head Units] surfer63:
The rooting process as described in the first post using Magisk is really a general purpose rooting method. The latest Magisk makes it even more easy. Search for magisk on XDA.

The boot image is for a great deal the same (apart from architecture: ARM, Mips or intel) for all Android systems but can contain few changes that can completely brick your system or make certain hardware/software based options (in your case) not function. Especially those Chinese Android head units contain a lot of hardware normally not available in phones or tablets. Some of that config/drivers/software is included in the firmware (/vendor for example), some in the MCU firmware and some in the boot image.

Please create your own boot image for your system: You can use any "howto" that comes a bit close to your unit. Using Magisk "parts" you can even do that manually: pda has a post about that, but I currently can't find it (I didn't bookmark it as I don't need it ).
[FYT Android Head Units] khoaitaychienvn:
I'm looking for the file to root the version 2020.4.7, can anyone help please?
[FYT Android Head Units] homer.ali:
Hi there!

Apologies if this has already been asked and answered but Joying recently uploaded updated firmware files in April 2021. Included in these files is firmware for the 13.3 inch 1920x1080 resolution headunits!

Instead of 6521_1 it is 6315_zip

Does anyone happen to know if the instructions listed in developer.zip could still apply to this firmware? Would love to actually be able to root my head unit as ADB is not natively available via usb ports or wifi, making any kind of modifications or application development a pain.

Thanks!
[FYT Android Head Units] surfer63:
Don't use it!

6315 is for the uis7862 units, not for the sc9853i units.
[FYT Android Head Units] surfer63:
You can find it on my repository: https://github.com/hvdwolf/SC98531BinRepo/tree/master/boot_images/2020-04-07

Don't use it if you have a 800x480 or 1280x480 unit or a 1600x800 unit.

It will work with 1024x600 and 1280x720
[FYT Android Head Units] khoaitaychienvn:
Thank you a lotttt