yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] focusedcoder:
New Joying Unit came in month ago can I root using this?

I just picked this JY UO135N4GS unit fast. now I am up finally got it installed and looking at root and roms. I never got the OBDII to work yet still hunting and waiting on feedback from Joying.

NOTE:

I was able to sideload TV Launcher II and set as default home launcher and it stayed, also the settings link in TV Launcher displays settings that are not avaible in the native settings app I can manipulate some but the screen stays dark kinda odd no backlight in what looks like native android Oreo settings...? I still maintain the pic in pic of the front camera app called Traffic Safety. wheel controls work still and even programmed one button to be home on the wheel.

here are the specs of this one

BaseBand Version

FM_Base_18A_RLS2_ISHARKL2_W18.37.1 SC9853_modem 09-10-2019 02:22:12

Marlin2_17b_oit_W19.05.2 marlin2_cm4 01-29-19 14:49:31

Build number

OPM2.171019.0012 release-keys

system info

app 1024X600 2019-03-04 10:41:36

CPU info

Intel Airmont eight-core 1.8 4+32 GB SC9853

MCU Version

2019.01.18 13:52 JY_53_C63L_G32P48F64_Ver: 1.0

BT Version

BLINK_8761ATV_RELEASE2/2019:03:15:11:29:00_blink
[FYT Android Head Units] julien_blanche:
Hi, I have rooted my joying sp9853i head unit and installed magisk 19.2 but can not download any module from the download section. Also i could not install the xposed framework (gave an error regarding unable the extract zip file every time) Does anybody know how to do this ?
[FYT Android Head Units] olegfusion:
Thank you, these files roots device normally.
[FYT Android Head Units] Mixa84:
I have installed 2019.05.15 firmware and did not do the root and TPMS is broken. "TPMS device error". Probably FW problem...
[FYT Android Head Units] thomasorr:
You're correct, I did some more testing and after flashing the non root firmware the TPMS breaks as soon as you reboot for the first time. I have reported to Joying and they are working on a fix.
[FYT Android Head Units] x111:
does new update fixed Bluetooth issue when you cannot hear anything while on Bluetooth calls ?

I'm pretty sure that in my case "jeep jku" has very small speakers on the dashboard and it does not have a proper connection or any.
[FYT Android Head Units] Wiebenor:
Ok, guys, stupid questions here... First some background on my Android experience. I have rooted and replaced rooms on a few phones, so I'm not an idiot as far as that goes, but however, I am new to the discussion of an Android based head unit, in general, although I have seen a few reviews on YouTube for several devices from varying companies...

On to question 1: I see you talking about Joying devices, but have any of you used headunits from XTrons, and if so, how does the build quality compare???

Question 2: is there a such a thing as doing custom roms on a headunit, not just on a certain brand unit, but in general?? I only ask, because if that was the case, then we as a community, could build something, possibly a resurrection remix fork,(my favorite phone rom) but with a custom launcher and setup, just for cars... I don't know how easy that would be to do, if custom roms were possible, and haven't seen any custom roms for any devices, so I'm assuming that we can't do custom, but what if we could??? (Not to mention, what if those companies made their code public, for that purpose)

Question 3: what is this stuff I hear about steering wheel controls??? Does it require 3rd party signal interpreters, like a normal radio might, depending on brand and model, or would you hook it up direct, without the extra hardware???

**Edit**

Another quick question... what do you guys prefer: newer, or older models, spec-wise, and what features are a must for said headunit???

As for model age, I mean Android version and production date, as well as the 2gb/3gb/4gb ram 16gb/32gb/64gb rom question... As for features, I mean how many USB ports, 4g/3g/none, SD card or not, what connections are required, and so on..
[FYT Android Head Units] kpitao:
New Head Unit

Hi all,

I just got this unit Android Car Radio - JOYING Android 8.1 4GB + 64GB 8“ (details are below) I want to know if I can use this method and files from the first post to root my radio.

Thanks
[FYT Android Head Units] surfer63:
The method: yes.

The files from the first post: probably not, but you can try that at your own risk.

Your firmware version is of 04 April.

It would be better to first upgrade to the May firmware and then make your own rooted system from there, using the method. Or search this thread if others already made it for the 15 May version.
[FYT Android Head Units] kpitao:
Thanks.... I got the may update from Joying, I'm trying to update my head unit but some hoe is not working.

I use the same method use on post #2, put the May update and the other file on the root of my flash drive, then i connected to usb of the radio; system says "update found" it looks like it goes thru, system reboots but the update does not complete; no messages (error message or completed) am I missing something?

Thanks
[FYT Android Head Units] bambapin:
I was able to root the May update using the patched boot image of post 81, my headunit is a not exactly the same as yours but it is still a Joying SC9853i.

Basically i did the update 2 times, the first time putting on the SD (or USB in your case) only the original May firmware, finished the update and rebooted.

Then on PC i wiped the SD card, unpacked the zip of the post 81 and at the end i inserted the SD in the headunit and restarted the update which actually replaced the boot image with the patched one for the root.
[FYT Android Head Units] kpitao:
My issue is that I tried 3 times update my radio to May update, again after I press start the update the radio reboots but the update never completes.

When you did update yours, did you get a message saying was completed?

Going to try the sd card instead the usb.

Thanks

SD Card did the trick..... just update to May.... now time to root!!
[FYT Android Head Units] nvstelmach:
Xposed not (yet) possible on SC9853i

Hi,

I have my Joying JY-UO134N4 rooted already on 15.05.20019 firmware and I have been following xda forum for a long time (but this is my first post).

-I have to ask why no-one is talking about the fact that installing Xposed on this chipset is not possible? -A previous member tried to raise the issue in this thread some pages back, but seemed to be ignored.

I know some things will be possible to do some things on the head unit once rooted, but without Xposed the point of rooting seems a little mute IMO. -I was especially looking forward to using XFYTtweaker as I need some way to start an app on ACC_ON and this seems to be the only tool to make this possible (MTCDTool is no longer maintained and does not work on SC9853i).

I have tried al possibilities installing Xposed from both Magisk Manager and the Xposed Installer 3.1.5 but it's clear from the installer that no Xposed SDK supports this chipset as of yet.

Am I the only one keen on getting Xposed on this unit or is it simply because so few of us have bought a SC9853i until now? -I was really hoping surfer63 would take an interest as he develops all the cool joying tools available;)
[FYT Android Head Units] surfer63:
Nobody said it is not possible to install Xposed. I'm fairly sure that one of the rooters also mentioned that he installed Xposed. And another mentioned indeed he was not successful. It took me also some time to get the right install for the Sofia (still buggy) and for the PX5.

W.r.t. XFytTweaker: In the new 15 May firmware they used some tool to obfuscate the jars. Instead of methods (functions) being called "KillAllButSome()" in the "ToolKitApp" class (java file), methods are now called some random names like "o()" in the "ad" class. (for the NoKill function. I did find that one).

It means that XFytTweaker will no longer work as it takes over the method (function) in the class (java file). Those names were always the same going from Sofia to PX5 to the 9853i, but they are different(=obfuscated) now in the 15 May firmware. I did not even find the ACC_ON and ACC_OFF function yet (only relative quick scan though) in the new code. So far FYT is successful in stopping hacking their code apart from the NoKill and "move BT app in the background during call" (see my Jet apk thread).

This obfuscating means a total rebuild of XFytTweaker, which is only copy&paste, but also a terrible search to find everything back. And that searching is really a pain in the back side and wil ltake extremely long.

And if their obfuscating/encryption tool is doing it randomly, then the new (not yet published) firmware, after this 15 May firmware, will again be totally different. Which means you have to start all over again.

My other "project" FytHWOneKey does it differently and without root and Xposed (but is currently on stand-still as I'm working on another desktop project). It detects ACC_OFF, but it can't detect ACC_ON as all apps are killed upon ACC_OFF. So the unit needs to have the NoKill mod and then might work with ACC_ON.
[FYT Android Head Units] nvstelmach:
Thx for the reply surfer63. Sorry to about XFYTtweaker and the newer firmwares for sc9853i. FYI. I have read and re-read all threads and post regarding sc9853i and no-one mentioned having xposed installed, only one that could not like me. I'll give it one more try later today as I've found that systemless exposed should be compatible across all hardware for 8.1 Oreo. Just need to figure out how to flash it with TWPR on my unit as the devise is not officially supported by TWPR either....the cost of being first movers I guess.

Also thx for pointing out FytHWOneKey, I had already looked at that one too but thought it needed a hardware key binding, which I don't want. I'm not using sleep mode at all and don't want the Nokill either, so I don't think it will work as the app is not alive on boot.

-I find it extremely frustrating that it can be so difficult to have a user option for installed apps which should be launched on boot for these head unit android devices:(
[FYT Android Head Units] surfer63:
When rooting with Magisk you can also install xposed via Magisk.

Tried anything like tasker already?
[FYT Android Head Units] julien_blanche:
Installing any app through magisk gives zip extract error every time for the intel 9853 head unit, for the moment it is impossible to install any module through magisk not even normal apps like youtube vanced etc..so magisk works for root only it doesn't do anything beside that..
[FYT Android Head Units] merdok:
I tried at installing xposed but was unsuccessful. I believe my last thought was that was not built for correct Arch. Everything listed as x86, and unit showed x86-64 iirc

Long chain with email support confirmed 2 bugs with default volume and back light control breaking car illustration control of buttons. On 5-15 firmware
[FYT Android Head Units] bambapin:
Hi, to fix the zip extract error you could try to replace the /system/bin/unzip executable with the one in the [MENTION=2550900]surfer63[/MENTION] repository (you can use root explorer to automatically mount the fs rw when copying) https://github.com/hvdwolf/JoyingBinRepo/blob/master/tools/unzip-x86.

It should fix the unzip error and allow to install "some" modules, indeed i still couldn't be able to install the xposed one :(
[FYT Android Head Units] nvstelmach:
I agree to some extend. I can actually get magisk to process this SDK27 systemless file when xposed magisk installer is installed: xposed-sdk27-topjohnwu.zip

-However the process fails after extract with "wrong platform: arm64" or something similar. -This confused me as Topjohnwu's file supposed to be systemless, so I started digging into xposed repos and we have version for arm, arm64 & x86....but it turns out intel sc9853i is actually 64 bit = x86_64...and after hours of digging it turns out that xposed has never been successfully ported to this hardware. Some claim that x86 would work, but I doubt it as Topjohnwu files should install then (unless the installer get's confused because of the 64 bit part in device info).

Anyway only way to really try is via TWRP recovery (to flash zips), but that another challenge as you need a specific device recovery img file for sc9853i. I found this but have not tried it yet (its another sc9853i device): google "LEAGOO T5c 3.2.1.rar" and find article from feb 2019 - I cant post links yet!

I have chased the rabbit for more than 40 hours the past 2 weeks and give up for now, but will be happy if anyone gets it done:)

Re. Tasker: I would actually prefer this or something similar as its my only objective for rooting the unit, but seems Tasker does not launch on boot on 8.1 Oreo, so that one is ruled out too. I will now be reading up on RECEIVE_BOOT_COMPLETED options.
[FYT Android Head Units] surfer63:
Systemless does not mean cross-platform.

Systemless means that your system partition is not "touched". You still need the version for your platform being x86 (or x86-64). The package comes with arm, arm64 and x86.

The Sofia was also 64-bits and used the x86 32bits version. That is not an issue whatsoever. Theoretically 64-bits should be faster and be able to address memory more efficiently and address more memory, but that is not important here.

Your error "wrong platform: arm64" means that the configuration detects the wrong platform.

When Magisk is installed it has utility scripts in /data/adb/magisk (MAGISKBIN). I assume something goes wrong there.
[FYT Android Head Units] nvstelmach:
Thx for clarifyin the "systemless" part.

So both installer and module is directly from topjohnwu's thread: https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268

It's the only module I can get to even extract in Magisk.

If I try the one from Magisk "download" it just says "unable to extract zip file" - "Installation failed". Now this one should have worked 100%, but can't explain it.

Anyway the one from topjohnwu's site extracts correctly when using the Modules - "+" installation, and the EXACT error message is this:

-Extracting module files

-Xposed version:

-Device platform: x64

!Wrong Android version:

!This file is for: SDK

!Please download the correct package

!for your android version!

!Installation failed

Since topjohnwu's only have 1 single file across all hardware and android version I can't really go anywhere from that. -The official x86 SDK27 xposed wont install in Magisk (extract error).
[FYT Android Head Units] nvstelmach:
Starting any user app on boot

So with the risk of looking like an idiot I want to share something for others in my situation on this Joying head unit:

I originally only rooted and struggled for the past 2 weeks unsuccessfully with xposed, because I wanted a way to start a "tasker app" on boot.

For some unknown reason (to me at least) neither Tasker, Automate or Macrodroid are allowed to start on boot. Don't know if it's Joying firmware or Oreo in general as google comes up with this issue in general for Oreo.

So today I played around in Setting and in there are both "Start Navi app on launch" & an option to set the Navi app of choice. I never took much notice about this earlier, and I just assumed you could only choose installed Navi apps in there. But to my surprise you can choose any installed app.

-So I have now solved my objective by simply setting Tasker in this setting and Tasker now starts on boot, and from Tasker I can start all other apps or tasks (like a Navi app so you dont loose that option). This is a perfect workaround and does not require root at all.

Tasker can still only survive Sleep mode if you install the NoKill mod, but I dont use sleep mode anyway as boot is rather fast and ensure my 4g/wifi hotspot is already live when unit is done booting.

I don't know if this has been there always in previous Android versions/units so please bare with me if this is the case.
[FYT Android Head Units] surfer63:
Nice work around!!

I just replied on your post in the other 9853 thread and your analysis here and now is correct. I had not thought of this navi app work-around. It opens new perspective. At least for users without hardware buttons on their unit.
[FYT Android Head Units] bambapin:
If anyone is interested, this is the patched boot for the latest version 06.12
[FYT Android Head Units] Thorsteenster:
Once it's rooted, is it possible to install a clean/pure Android? I hate the software on it, mainly the music player and I tried installing Player Pro but it doesn't see any music. Joying support said it can't support it right now and to fix built in player issue wipe HU and update. Thinking I might as well root at same time.
[FYT Android Head Units] rigattoni:
No!

You need to choose the folder. Automatic searching may don´t find your music on SD card.
[FYT Android Head Units] kpitao:
OK guys, I'm back with another question:

When I press the "Power Button" on the radio itself, instead bring the power menu, it "mute" the radio, I want to be able to bring the power menu back?

Is there a way to change it? The car settings "Panel Key Learning" is set to power not to mute....

Also, found on the root of the internal card a file named "MuteSwitch" but I cannot open...

Thanks
[FYT Android Head Units] Thorsteenster:
I went through all the settings in HU and adjusted any that looked related, permissions etc. When Player Pro looks for music there is none found, and when I try to give Player Pro folder permission from in the app, it says "Unable to open directory selector". Maybe root can fix this? I do have Player Pro as default so if I open a song from file explorer it opens in it.

Thanks for the reply.
[FYT Android Head Units] rigattoni:
That has nothing to do with root and should not be handled in this thread.

You need to use the player correctly.... or choose another player which is able to set a folder as source where you stored your music.
[FYT Android Head Units] surfer63:
This is/was standard behavior and it is actually never a power on/off button. On the previous models a push meant mute/unmute, a 3 seconds push meant "black screen" but simply continue. It never switched off the radio as that is done via the contact.

Can you check the "3 seconds push" on the 9853i?

and rooting should not change your "bring the power menu back". Rooting has nothing to do with how a function reacts on a button press.
[FYT Android Head Units] Thorsteenster:
You could have just said no, I'm asking because I didn't know the root might fix this or not.

How do you use the player "correctly", you play music with it. The default player doesn't function correctly.

Thanks anyway.
[FYT Android Head Units] rigattoni:
Yes, I could have just said no...

You never wrote where you stored your music and in which format.

The standard player works on my same unit as expected with music stored on a SD card in a folder named Musik as MP3.

If you try to use other formats, you need to choose another player as OGG, FLAC, ALAC... as these are not supported by the original player.

You could try MortPlayer or Poweramp, but with Poweramp there are some issues with activating the pro license.

But once again, this has nothing to do with rooting your device.
[FYT Android Head Units] Thorsteenster:
This neither has anything to do with rooting device.

Music is on SD, 7.5GB of MP3's. The issue I have with default player, even in staright play mode, after playing 3 or 4 songs from an album it starts playing random. I have to hit back button, press file icon and press the next track to play. Very frustrating trying to listen to an entire album straight through, and distracting while driving. Awesome for when I'm in the mood for random music.

Have a nice day :silly:
[FYT Android Head Units] kpitao:
Ok.... yes the "3 seconds push" blacks the screen....

I wanted the power menu so I can get the "android bug report".... since there's no option under developer settings to "take bug report" however there's a option to add the "take bug report" to the power menu.

is there another way to get it? or does anyone knows the file location for the report?

Thanks
[FYT Android Head Units] dirk_:
Hi,

I have the problem that when I rooke my Joying, that e.g. on Google Maps the voice output stops working. Everything is ok before that. I have tried it several times and always with the same result. I tried it with the version of Joying from the 15.5 and 12.6 Can one help me there?

I have find my solution here:

https://xdaforums.com/android-auto/...droid-8-1-intel-airmont-eight-t3897206/page68

Kind regards

Dirk
[FYT Android Head Units] merdok:
Is there a specific root for the 6.21, or can the 6.12 file be used?
[FYT Android Head Units] surfer63:
Only after you have compared the boot images for 6.21 and 6.12 and they turn out to be equal in config. But in that case it is faster to simply create a new rooted boot image.

If FYT changed the boot image you might end up with a bricked unit.

The risk is not so big, especially not when the 6.21 is only a small bug fix over the 6.12, but then again: you never know whether the bug fix is boot image related.

But you can try: the proof of the pudding is in the eating :)

And as a side note: The fact that you can use unsigned zip images (the 6521_1 zip for the rooting) and modify the Allap.pkg yourself (@julien_blanche mentioned that) without needing the Joying signing, might also mean that this is the first Joying unit where it is easily possible to create a custom rom for, without needing a custom recovery.
[FYT Android Head Units] TechnoJaguar:
Questions

joying-10-1-inch-double-din-android-8-1-0-big-screen-car-navigation-system-with-4g-module

Running this unit (10.1" 1024x768 4GBx64GB)

First question: Can anybody get bluetooth working for general devices?

bbfly-BB77102 Bluetooth modified Android OBD Scan Tool FORScan

Can't get this to connect, and can't get my Valentine 1 Connection dongle to even prompt for PIN.

I saw someone post a mod somewhere that changed all device names to ODB but Joying insists they aren't blocking any devices.

Is there a way to re-enable the android native bluetooth stack (or maybe need to replace a file?)

Second Question: Is there any way to access the AUX In or Reverse video feeds via a 'camera'? The streams are always garbled when I try to use stuff like autoblackbox.

Third question: Will rooting and Joying Extra Tools allow me to fix the menus where the text is all black? So many hard to read places :(

Thanks and have a great week!
[FYT Android Head Units] merdok:
Thanks for the info.

In my profession I have built firmware updates for embedded busybox. I should just set time and learn this process. I have been flashing android too long to not fully understand the process.

I guess would need to get a stable release from joying to start from.
[FYT Android Head Units] MIndrunner:
Hi!

Any idea if this root schema will work on other Intel Airmont units? I own a different brand HU built on same cpu core (9853i ). Thank you.
[FYT Android Head Units] bambapin:
Does anybody have any ideas on why rooting breaks the voice output in Google apps? It would be nice to find a solution that does not require to uninstall Magisk ...

Inviato dal mio SM-G965F utilizzando Tapatalk
[FYT Android Head Units] PsychoMcSatan:
For those that have rooted the newest June 21 ROM, is anyone willing to upload/share their patched files?
[FYT Android Head Units] merdok:
I did have success using the file in post #108 on the 6.21 build. I forgot to reply.
[FYT Android Head Units] bambapin:
I noticed that the original boot.img are not exactly the same in 6.21 and 6.12.

Even if the file in post #108 works, i think it would be better to create a new one starting from the last 6.21.

I can do it but not before next week.
[FYT Android Head Units] bersercci:
Great idea! How do you run a task = how to set up a profile to run immediately on Tasker start?

It doesn't show Tasker in the list of apps to run profiles on start...

If I can run a profile with this workaround on every time HU wakes from deep-sleep, many of my problems are solved!