General HowTo: Root Joying SC9853i Head Unit

Search This thread

surfer63

Senior Member
May 4, 2010
4,758
2,271
Zwolle
github.com
So at this point I tried following the instructions in developer.zip in this post and made a patched boot.img
When installing this however It unfortunately results in a soft boot loop.
I can exit the boot loop by placing the unmodified update back onto the usb.

<snip>

If it helps the error I got in magisk on the headunit was "Cannot unzip zip, installation failed"
Attach your zip or give us a link to it, so we can look what's wrong.
 

homer.ali

Senior Member
Jan 17, 2011
59
28
OnePlus 7 Pro
Attach your zip or give us a link to it, so we can look what's wrong.
This is the original, unmodified firmware that joying sent me.
Now that I know I can modify this to get root, +/- just use the excellent process outlined in your modding without root thread, I can really get started.

I assume that since this is a different firmware date than the ones you have for your 190000000_com.syu.ms.apk Main server mod, that I won't be able to use that solution to blanket disable killing all apps on sleep. Instead I have to add apps to the skipkillapp.prop file manually. is this correct?
Is there a way to make my own nokillall app that would work on this firmware?

Thanks again for all of your help. Just looking through this forum it's clear you've been an MVP with these joying headunits for a while so I really appreciate it!
 

Attachments

  • 1920 1080 横竖屏.rar
    1.1 GB · Views: 39

Odt123

New member
Aug 24, 2021
1
0
Hey all I'm interested in rooting my joying 10. 1 in head unit. I have the 1280x800 version and haven't seen any info on here as of yet. So far I've followed this video
Which eventually lead me here after I couldn't get adb to connect to my HU. joying sent me this for the updated firmware
Android 10.0 1280X800 2021.7.5.zip - Google Drive

As ridiculous as this sounds I really just want to get rid of the default Nokia ringtone that blasts thru my speakers when my phone rings. Any and all help would be greatly appreciated. Thanks in advance!
 

DMon04

Senior Member
Feb 16, 2017
116
20
Dalton,Ohio,USA
LG Velvet
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.
How about taking a laptop with Android SDK loaded on it straight to the head unit,or out to your vehicle and do the commands on a laptop to the device?
 

surfer63

Senior Member
May 4, 2010
4,758
2,271
Zwolle
github.com
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.
No. The build is a release build, not a user or debug build. That's why adb over wifi does not work (plus a couple of other safety related things coupled to release builds). That is Android design.

Sorry. This was a post over a year ago. Didn't look at the date.
 

DMon04

Senior Member
Feb 16, 2017
116
20
Dalton,Ohio,USA
LG Velvet
Hey all I'm interested in rooting my joying 10. 1 in head unit. I have the 1280x800 version and haven't seen any info on here as of yet. So far I've followed this video
Which eventually lead me here after I couldn't get adb to connect to my HU. joying sent me this for the updated firmware
Android 10.0 1280X800 2021.7.5.zip - Google Drive

As ridiculous as this sounds I really just want to get rid of the default Nokia ringtone that blasts thru my speakers when my phone rings. Any and all help would be greatly appreciated. Thanks in advance!
Its not MY method but I'll copy the links I followed in this post. Was pretty simple. Hope you guys enjoy the freedom of root!! The first link is not in english so use Google Translate and you should be able to understand it easier.



 

highkick05

Member
Aug 30, 2020
21
2
This thread is so confusing. Might I suggest a better HOW TO be made.

The flashing process is relatively easy once you figure out the premade boot images posted on here can be used with all Joying Head Units, regardless of resolutions. (28 pages)

Going through the readme.rtf to make your own seems stupid, albeit, painful because the Magisk apk's no longer work installed onto the Joying head units. We're lucky these patched_boot.img's have been posted.

I also had an annoying watermark or chinese red text "3595AL" on my home screen that wouldn't go away. But after reflashing original then the latest firmware that has gone now.

Pretty happy though, I now have root with the latest boot image, latest firmware & applications. Changed my new UI 10.25" to the older UI which spans the entire screen and gets rid of the clock (pissing me off). Updated Magisk a few times and now have no popup messages annoying me about installing additional software. 100% rooted, and just waiting for me to install all my apps lol. Awesome work guys.
 

DMon04

Senior Member
Feb 16, 2017
116
20
Dalton,Ohio,USA
LG Velvet
This thread is so confusing. Might I suggest a better HOW TO be made.

The flashing process is relatively easy once you figure out the premade boot images posted on here can be used with all Joying Head Units, regardless of resolutions. (28 pages)

Going through the readme.rtf to make your own seems stupid, albeit, painful because the Magisk apk's no longer work installed onto the Joying head units. We're lucky these patched_boot.img's have been posted.

I also had an annoying watermark or chinese red text "3595AL" on my home screen that wouldn't go away. But after reflashing original then the latest firmware that has gone now.

Pretty happy though, I now have root with the latest boot image, latest firmware & applications. Changed my new UI 10.25" to the older UI which spans the entire screen and gets rid of the clock (pissing me off). Updated Magisk a few times and now have no popup messages annoying me about installing additional software. 100% rooted, and just waiting for me to install all my apps lol. Awesome work guys.

This thread is so confusing. Might I suggest a better HOW TO be made.

The flashing process is relatively easy once you figure out the premade boot images posted on here can be used with all Joying Head Units, regardless of resolutions. (28 pages)

Going through the readme.rtf to make your own seems stupid, albeit, painful because the Magisk apk's no longer work installed onto the Joying head units. We're lucky these patched_boot.img's have been posted.

I also had an annoying watermark or chinese red text "3595AL" on my home screen that wouldn't go away. But after reflashing original then the latest firmware that has gone now.

Pretty happy though, I now have root with the latest boot image, latest firmware & applications. Changed my new UI 10.25" to the older UI which spans the entire screen and gets rid of the clock (pissing me off). Updated Magisk a few times and now have no popup messages annoying me about installing additional software. 100% rooted, and just waiting for me to install all my apps lol. Awesome work guys.
I posted that how to with the instructions. I have Magisk installed and somewhat working on my 7" double din Android 10 unit. I used it to make the patched boot image from my device. It worked for me. I love having root access to do whatever. Did you happen to lose your normal radio after rooting? I lost my normal radio and have been trying to figure it out.
 

highkick05

Member
Aug 30, 2020
21
2
I posted that how to with the instructions. I have Magisk installed and somewhat working on my 7" double din Android 10 unit. I used it to make the patched boot image from my device. It worked for me. I love having root access to do whatever. Did you happen to lose your normal radio after rooting? I lost my normal radio and have been trying to figure it out.
yeah works , maybe try the unroot method and reflash the correct radio apk.
 

surfer63

Senior Member
May 4, 2010
4,758
2,271
Zwolle
github.com
This thread is so confusing. Might I suggest a better HOW TO be made.
Of course this thread is confusing because so many questions get asked. However, which HowTo do you mean? The one from the very first post from @prrlhkr ? I don't consider that one confusing, but that might be me. If you think that one is confusing, please tell us what is confusing because in that case we can better update the first post instead of creating a new one as two HowTO's will be more confusing than one for any new user wanting to root his/her unit.

I posted that how to with the instructions.
Yes, you posted that one. If it worked for you: Great! But why did you copy & pasted a HowTo from a Howto from a HowTo with a pre-created boot image that might or might no work?

To both: That is exactly why this thread's first post tells you to create your own boot image and not simply copy one. You might be lucky, or you might get errors, warnings, yellow bars, etcetera.
If a thread starts with "HowTo: ...", then please start reading from the first post.

I know that a lot of users are eager to root their unit, but it is not necessary and has negative influences (and did you already find out that Google voice feedback does not work on a rooted unit?)
 

highkick05

Member
Aug 30, 2020
21
2
Of course this thread is confusing because so many questions get asked. However, which HowTo do you mean? The one from the very first post from @prrlhkr ? I don't consider that one confusing, but that might be me. If you think that one is confusing, please tell us what is confusing because in that case we can better update the first post instead of creating a new one as two HowTO's will be more confusing than one for any new user wanting to root his/her unit.
Magisk doesn't patch the boot.img on Joying units anymore by the looks as it wants to update to latest stable branch always. As boot.img works on all resolutions, better to list patch-rooted.zip & original-boot.zip under release dates. Some users make even more confusing in the thread talking out of topic, mentioning non-Joying , newer android 10 & Sofia and PX5 & 6 Head Units. Further confusing topic
 

highkick05

Member
Aug 30, 2020
21
2
Strange. I will test tomorrow.
I don't use rooting anymore as it only reduces functionality of the unit, and and with the partial custom flashing almost all "root things" can be achieved as well.
Yeah, I ended up trying to patch boot.img on my Android mobile phone because it appears to work well on that. Only thing is, the resultant patched_boot.img then soft bricks the Joying. That was using the readme.rtf with the correct files for my Joying version. Lucky that reset pin 3x allowed me to flash an entire system back to the unit. So, I have a better understanding of what's involved now. People who have uploaded the root-img.zip's have basically saved all of us. It will never work again with the latest Magisk's :/ Anyway, love your work. Cheers for the help
 
  • Like
Reactions: DMon04

Vinyvince

New member
Jul 19, 2009
4
0
Hello everybody.
I read again and again thoses 28 (interesting) pages but I think I need help.
I'm French and I buy a Joying 8.8 in May 2020 (EU-JY-HOS01N4GS-1) and I try many tips to resize screen (for a good use behind my Corvette C5 radio bezel).

-I try "direct" root method with file on post #33 of ojuniour but I've the red chinese message, the joying seems rooted but can't resize screen (and very slow).
-I try adb method with pc or special app with an other android phone but impossible to find the joying device.
-I try the developer.zip method but the installation of Magisk failed and I can't obtain a pached boot image.

Can you help me ?

(the only good thing is I can always do the update with original joying firmware and have a fully functional device)
 

DMon04

Senior Member
Feb 16, 2017
116
20
Dalton,Ohio,USA
LG Velvet
Yeah, I ended up trying to patch boot.img on my Android mobile phone because it appears to work well on that. Only thing is, the resultant patched_boot.img then soft bricks the Joying. That was using the readme.rtf with the correct files for my Joying version. Lucky that reset pin 3x allowed me to flash an entire system back to the unit. So, I have a better understanding of what's involved now. People who have uploaded the root-img.zip's have basically saved all of us. It will never work again with the latest Magisk's :/ Anyway, love your work. Cheers for the help
I was able to use the latest Magisk on my newer unit to patch my boot image. The newest Magisk doesnt seem to do much and I had to search through Magisk a bit to find the patching function but was able to patch my boot image. As far a signing the patched boot image,I thought I had it done correctly but upon trying to flash the signed boot image,the unit failed to flash it. I then used one of the pre-made patched images and it worked for me. Pretty sad when Magisk does absolutely nothing anymore lol.
 
  • Like
Reactions: highkick05

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    First off a big thanks to the guys at {Mod edit} for doing all the hard work, I'm just writing this post as a guide for those who don't speak Russian - like myself :)
    Second thanks to all those on the Original Thread (https://forum.xda-developers.com/an...ying-android-8-1-intel-airmont-eight-t3897206) for helping me finally find an android head unit worth buying.

    Compatible Firmware Versions:
    • 9853i 800X480 2019.3.20
    • 9853i 1024X600 2019.3.29
    • "New" 9853i 1280X480 新UI 2019.3.18
    • "Old" 9853i 1280X480 旧UI 2019.3.18

    Legacy Support


    Changelog:
    • April 10 2019:
      • Added new files for several units

    Previous Changelogs:

    • April 4 2019:
      • Fixed typo in Developer instructions
      • Added "Ultra Wide" version
    • March 28 2019:
      • Simplified Installation Process
      • Reformatted instructions


    Warnings
    • I am not responsible for bricked devices. Proceed through this rooting process at your own risk.
    • Rooting your device will void Joying's waranty. (Even though it can be uninstalled in Magisk Manager).

    Prereqs

    Rooting Your Device
    1. Plug your Flash Drive or MicroSD into your computer. Make sure there's nothing on it.
    2. Extract the contents of the device-appropriate archive to your flash drive. You should have 2 files: "lsec6521update" and "6521_1.zip".
    3. Go to your head unit. Moment of truth; no turning back once you begin this next step! Plug your flash drive into the head unit. The update will be detected and the update will automatically begin.
    4. Your head unit will reboot into recovery and install the update containg root. DO NOT POWER OFF YOUR DEVICE OR UNPLUG THE FLASH DRIVE DURING THIS PROCESS!!! If you do, you may permanantly brick your device! Once prompted by the update process, remove your Flash Drive and let it boot back up into Android.

    If you would like the more in depth "developer" tutorial, attached is Developer.zip.
    Inside I included "Readme.rtf" - a copy of the developer instructions with screenshots.
    6
    Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
    Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
    Please see attached update file.
    Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
    **FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
    5
    I got emailed the update link to this morning also for the new firmware, just flashed it and it fixed all my problems (voice, notification bar etc)
    Im stoked. :) Joying has been super good and responding to emails and fixing stuff. One of the reasons I bought a Joying over some of the other crap out there.

    Here is the patched boot.img with magisk file: Magisk 9853i 1024X600 or 800X480 Google 2019.5.15

    Cant upload the firmware at work unfortunately but was able to patch the boot.img while driving to work :p
    4
    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.
    3
    Previous terminal command apk wasn't fully compatible with magisk and not to ask superuser grants. I found a new one and tried to generate other files, hope it is good enough but it is not so easily from an average garage...

    This is exactly what I need. Thanks.
    I will start extending the JET apk