yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Lestat-XDA:
Hi, just received my Joying SC9853 and upgraded to the last firmware.

Please find attached the last patched image for 2020-04-07 version.
[FYT Android Head Units] LunaEros:
What model Joying unit do you have?

It wouldn't happen to be the JY-HOS01N4GS-2 would it?
[FYT Android Head Units] Lestat-XDA:
Nop, that's the : JY-UO128N4GSN
[FYT Android Head Units] LunaEros:
Damn. I'm sick of waiting for them to reply to me about getting the image I have in mine for a "backup" so I can root mine.
[FYT Android Head Units] surfer63:
What is your version anyway? The latest ROM for your model is the 28 Nov 2019 ROM at this moment.
[FYT Android Head Units] LunaEros:
Actually it's not. The latest version which is on mine they haven't put up on their firmware page. I have no idea why. I wish they would because all I'd have to do is download it from there then.

The OS version is 1-10-2020 and the MCU version is 1-09-2020.
[FYT Android Head Units] cepuchin:
hello

What kind of format needs the usb drive?

my unit detects the usb drive but doesn't do anything
[FYT Android Head Units] LunaEros:
I think my Sansdisk 128G drive is formatted as NTFS but I'm not 100% certain. I know the SD cards are supposed to be formatted as FAT32 and need to be 32G or less.
[FYT Android Head Units] tchleb:
1. That does not matter.

2. You need to put the two files on your USB stick / SD Card and the update dialog pops up and the flashing starts.

3. It doesn't metter which file explorer you use (if there is no error dialog during the steps)

Had you the "no command" error durning flashing? If yes press the reset button after Bootlogo appears for 3 seconds, release and press again. Flashing should be forced.

Maybe you made an mistake during the steps e.g. Flashcontainer isn't signed.
[FYT Android Head Units] surfer63:
No.

The boot image (boot.img) is rooted.

Upon a new firmware a new boot.img is also flashed to the unit. So you "loose" your previously rooted boot.img.

Upon every new firmware flash, you need to reroot your boot.img and flash it again to your unit.
[FYT Android Head Units] kpitao:
I had no errors at all ..... everything said was successful..... the 2 files were on the sd card

Don't fell taking my car apart again to reboot, unless if I really need to.

Does anyone knows a reboot app that works without root?

Thanks
[FYT Android Head Units] surfer63:
Sorry. I did not read your question well enough.

You can simply reboot by pulling down the notifciation bar. There is a reboot button.

What is wrong with rebooting? And why do you want to reboot?

You must install Magisk manager again as that is the app that gives root access to apps when they ask for it.
[FYT Android Head Units] kpitao:
ok.... stereo is now on 04/20 .... since the update did not remove my old data (I know it's not supposed to) I want to go back to 11/28 .... but before I want to factory reset the unit.... After i choose backup and reset I enter code 3368 .... now i select erase all data but it keep asking for a device pin, which I don't have it....I tried 3368, 8086, 126, 123, 1234, 123456, 0000, 0000000

Does anyone know the pin?
[FYT Android Head Units] cepuchin:
try 7890
[FYT Android Head Units] kpitao:
yep, that did not work either..... going to email Joying
[FYT Android Head Units] surfer63:
You did not try 5768 yet (Backlight Current Adjustment). Maybe that one works.
[FYT Android Head Units] kpitao:
Did not work either...... just thought about something not sure if it has anything to do with it

I did not use DEV tools to create my boot image file to root myself; I use one from this tread; do you think it could have a different code because that?
[FYT Android Head Units] surfer63:
No. The pin codes always used to be hard-coded in the Settings.apk. I didn't check, but I can't imagine that it has changed. And the pin codes are the same on every unit. Why would that be different in another boot.img?

You want to first do a factory default reset and then reflash. And that now gives you issues.

Why not simply reflash with the 20191128 and afterwards do a reset to factory defaults?
[FYT Android Head Units] kpitao:
I did tried that .... it's just weird.... even after the flash update I'm still unable to factory reset....

My next steps:

I'm on April 2020 update... going to update the updatecfg.txt with some codes to erase all data like you said on: https://xdaforums.com/android-auto/android-head-units/modding-joying-fyt-sc9853i-unit-root-t3974357

I just have to read and try
[FYT Android Head Units] Curro06:
Please, help with my device no joying

Hello everyone!

My name is Curro and I am from Spain. I am new to the forum and I would like to thank you for this thread and for all the explanations. I have followed the instructions to root my device and it has not been successful. Please someone can help me, I can't find how to do it for no-joying devices like mine.

many thanks!
[FYT Android Head Units] tchleb:
From which brand is your unit? Do you have update files?
[FYT Android Head Units] Curro06:
Hoy root no Joying device

Hi! Whats do you mean “update files” ? The original firmware or boot patched and 6521_1.zip.....?

The brand i think is “LiJun” y bought in AliExpress and there say “SinoSmart” brand
[FYT Android Head Units] marcus82:
I'm in the same situation with prelingcar head unit from alixpress. unfortunately my last update was not update.img file

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] Curro06:
Root no Joying device

Kindly, ir you say me one email i coludirse send you the firmware; the forum don let me paste the link of my firmware to my cloud
[FYT Android Head Units] tchleb:
6521_1.zip is the archive with the images.

With this it should not be a problem to root your unit.

What was your fault?

Flashing doesn't start and only a quick error message on the recovery wit "No command"?
[FYT Android Head Units] Curro06:
Root no Joying device

No friend; i have doing ALL proces of this thread explaim for surfer.... al good... bit finally, when i restart device, Magisk don’t have updated..
[FYT Android Head Units] marcus82:
but installing magisk from magisk manager directly?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] Curro06:
ROOT no joyimg device

I have installed Magisk Manager already. When the last phase i into 6521 and isee 6521 .... the device installed update... but when i restart, ir say Magisk dont update
[FYT Android Head Units] tchleb:
Has the unit given the task to remove the USB stick after the flashing?

If no the flashing was not performed.

If yes you made an fault durning the patching / sign process
[FYT Android Head Units] Ejpi16:
Works great!

It first failed but the usb device was not properly formatted (was exfat or something like that)
[FYT Android Head Units] ojuniour:
I have the ultrawide model - version with resoolution 1280x480 . How to you root the system file?

In case anyone wants it, the system version below.

https://drive.google.com/file/d/1VltRfQMEltK-UEuP2ICEeC-kO8lsA27j/view?usp=sharing

Can I just take the patched bootimage , rename it to boot.img, repack it with my 6521_1.zip and just flash?
[FYT Android Head Units] surfer63:
First off: You do not mention which unit you have. Yoying sells several 8.1.0 ultra-wide units, but with different hardware. Is it this one?

Secondly: No, you cannot "Can I just take the patched bootimage , rename it to boot.img, repack it with my 6521_1.zip and just flash".

You should read the first post on how to do it, or use the files from the 2nd post.

But first confirm which model you have. You do not even mention that it is a Joying although that seems logical to assume.

Facts please.

At least the firmware is for a Joying sp9853i.

Edit: It seems to have a new nice gui/launcher.
[FYT Android Head Units] ojuniour:
Thanks for the response.And yes, I do have the newer one (and yes, the one you referenced with the 4G/intel cpu/ built-in DSP).

I tried following the instruction attacked except the part where I need to use the root.zip which obviously contain system files and I'm not sure if that would be compatible with my unit san the different resolution or the root.zip is just thesame untouched firmware from the specific system. That's why I'm asking for clarification.
[FYT Android Head Units] colonel_lp:
You are best of asking joying if the update (that the root method is based on) is for your system.

I don't think it is, unless your boot image is the same, as if you read here: https://www.joyingauto.com/blog/category/updated-files-released/

It says the update is for 1024x600 units: Applicable Car Models: JY-UO135N4G, JY-UO128N4G, JY-UO138N4G, JY-UO134N4G, JY-UOS01N4G, JY-UOS02N4G, JY-UOS03N4G, JY-VO131N4, JY-TO138N4, JY-VO130N4G ,

That's the firmware the root method is based upon.
[FYT Android Head Units] ojuniour:
There is a reason why each system with different resolution has its own system files due to the obvious. so yes, i do believe the root might be specifically for the that specific resolution.

Now if i can find a way to modify my own system files that was done to the "root.zip", that would be great.
[FYT Android Head Units] surfer63:
Please note that root is something completely different than boot.img

I downloaded "your" ROM. The boot.img in your ultra-wide ROM is different from the one in the "normal" firmwares. I can't make a patched boot image for you as it needs to be made on the unit itself. I do not have a 9853i.

You have to do it yourself.

Download the developer.zip from the first post and read the Readme.rtf inside it describing how you should do it.
[FYT Android Head Units] ojuniour:
as I've just mentioned, it requires "A copy of root.zip (attached)" which is nowhere to be found.. Is it talking about the firmware? and if so, can I use mine?
[FYT Android Head Units] colonel_lp:
Developer.zip contains all the files from root.zip, follow the readme
[FYT Android Head Units] ojuniour:
The mystery has been solved.. so the "root.zip" IS the "developer.zip".. Please someone update the instruction to avoid any inducing confusion.

Thank you all for the help. I'll give it a try now.
[FYT Android Head Units] prrlhkr:
On it, sorry for the confusion. I changed the attachment name but forgot to update the readme. On another note, if you could send me the final "lsec6521update" and "6521_1.zip" I can post them for others to use with the wide units.

Interesting, didn't know there was a totally different firmware for the wide units...
[FYT Android Head Units] kouklo:
They just released a new firmware. Do you need to update the root files for it?
[FYT Android Head Units] ojuniour:
File uploaded.. For anyone, this is for the 8.8 and 10.25 ultra wide version.

And also this version retains the old UI because the new one is pretty useless and takes unnecessary screen space (a dummy clock occupying 1/5th of the screen.. and it's not customization..)
[FYT Android Head Units] PsychoMcSatan:
Has anyone with root tried fixing "OK Google" dialing yet? There's an app in the play store called "GVC CallHandler 4 Joying" which, at least for my old Sofia unit, was able to pass Google phone call requests to Joying's Bluetooth Dialer app. As it looks like the same app as the Sofia unit uses, I'm hoping it can work without modification.

The only problem is that default 160 DPI (on the Sofia at least) causes issues, I think because Android thinks you have a tablet and not a phone. Initial attempt on the Airmont result in the expected "I can't make calls yet" response from Google Assistant. On the Sofia, once you change DPI to 161 (or higher) it started working.

So is anyone who is rooted willing to give this a try by altering DPI? I'm hesitant to root and risk warranty as I've only had this unit a couple days. And I might want to update to newest ROM just posted by Joying so waiting for confirmation that this rooting method works on this version. By the way, does rooting reset the unit?
[FYT Android Head Units] ojuniour:
Believe me they won't it's rooted if you root by magisk.. Just revert change and flash back the boot image and of course system files.

Now regarding the OK, goole.. I don't know why you are having problem with yours..but mine works right out of the box. There is now an even can Bus functionality for voice control that I map to my steering wheel button for ok google.
[FYT Android Head Units] PsychoMcSatan:
OK Google works fine. It's specifically the ability to initiate a phone call I'm looking to get working. If you say "OK Google. Call Joe Mobile" does it start dialing Joe's mobile number (if you have a contact named Joe)?

And not clear about what you're saying or referring to in your first sentence.
[FYT Android Head Units] ojuniour:
You need to download and install the "Google contact" from the playstore to enable that functionality.

Give it a try.
[FYT Android Head Units] PsychoMcSatan:
Thanks, installed Google Contacts, but still responds with "I can't make calls yet". Sorry for high-jacking thread, but I think I am going to root anyway.

So can someone confirm whether the quick root method will work for the newest ROM on Joying's website, "9853i 1024X600 2019.3.29.zip"?
[FYT Android Head Units] Sargol.Xanger:
Will this also work on 9853i 1024X600 2019.3.18? I'm a little bit affraid to try :)
[FYT Android Head Units] surfer63:
The boot images between the 4/5 March version and the 4/5 April version are different when you check them bitwise (using md5sum or so), but you can already see it on the size itself. I guess the 2019.03.18 is different as well.

The previous boot images might still work. They are recompiled/rebuild for every firmware, but that does not necessary mean they will not function.

On the other hand: If FYT/Joying really changed "something", the previous patched boot images might "boot-loop" or "soft-brick" your unit. Which means you need to reset your unit and reflash it with a stock rom.

The safest is to build a new patched boot image for every new firmware and use that.
[FYT Android Head Units] marcus82:
oh ok...

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] surfer63:
Your Lijun/Sinosmart unit is indeed a FYT unit, but it's flashed slightly different than the Joyings as it contains config files for the several models they have.

To make sure we understand each other correctly I like to know what you did.

Did you use the develop.zip and the howto that is inside that develop.zip from post #1?

Did you copy the boot.img from the 6521_1.zip to the unit and let Magisk do it's work?

Did you then copy the modified boot.img back to your pc and made a new 6521_1.zip?

Did you flash that new 6521_1.zip?

And to correct one thing: I did not write that first post nor created the readme. That was done by [MENTION=6208347]prrlhkr[/MENTION]
[FYT Android Head Units] Curro06:
Root no Joying device

I answered you in your text, friend
[FYT Android Head Units] surfer63:
You say that Magisk did not update. Did you get a message?

And how did you check whether root is installed or not? Did you try some rooted app?
[FYT Android Head Units] Curro06:
ROot no Joying device

This is my firmware:

https://drive.google.com/open?id=1NInLNpL_IdQ5awDPGWD_lY0wsqPtDHuJ
[FYT Android Head Units] surfer63:
Yes, I have seen that file but that is the complete firmware from your unit.

That is not the rooted image. Can you share that one?
[FYT Android Head Units] Curro06:
ROOT no Joying device

When restart device, Magisk app show the first screen after process:

(Symbol red) Magisk is not installed

(Symbol green) Magisk Manager is un to date

Like first screen; no finally screen like developer guide (readme doc)
[FYT Android Head Units] surfer63:
Again: Can you share your modified boot.img ?
[FYT Android Head Units] Curro06:
ROot no Joying device

Ok friend; I’m Writing from phone. Inma few moment i try share my boot.img... altought i don tu inow hoy i can share files in forum.

Let me some minutes, please

Thanks!

---------- Post added at 08:03 PM ---------- Previous post was at 07:55 PM ----------

there are the link of my boot.img

https://drive.google.com/open?id=1tFm2dx6zgHUA1tkJUniRt6jHKNAxUEZH

---------- Post added at 08:05 PM ---------- Previous post was at 08:03 PM ----------

excuseme friend.

:

there are link of my boot patched created with magisk manager in my car:

https://drive.google.com/open?id=1tFm2dx6zgHUA1tkJUniRt6jHKNAxUEZH
[FYT Android Head Units] tchleb:
Here your rooted Boot.img

https://mega.nz/file/qp0SCaTY#1ceVHW2377iWuBzvLDRcJOqMHrkZRurY3dILnffUfRo

If flashing not work keep the usb stick plugged, restart the unit and press when the bootlogo appears 3seconds the reset button, release and push quickly again. Maybe you need some tries...

I have an Junsun (FYT) and flashing works only with the reset button.
[FYT Android Head Units] surfer63:
This is the patched boot image, but it is called "magisk_patched.img".

The script that flashes the rooted image is looking for a "patched_boot.img".

Did you rename your file before you put it into the 6521_1.zip?

That script is called "updater-script" inside the 6521_1.zip in /META-INF/com/google/android/
[FYT Android Head Units] Curro06:
Root no joying device

I think yes; I think I will can change the name of this file...

I must rename file with “patched boot” name?

---------- Post added at 08:29 PM ---------- Previous post was at 08:27 PM ----------

Hi friend...

You say me that this firmware it’s already root? I only would have into my device with a flash usb?
[FYT Android Head Units] tchleb:
Right, unzip the archive and put both files an the root directory of an usb drive.

At first you can tried flashing over the pop up menu. If that's not working you have to flash with reset button process.

If the flashing was successfull you will get an message that you should remove the USB drive.
[FYT Android Head Units] marcus82:
me too I want help to root my radio ehehrh[emoji7]

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] LunaEros:
Damnit. I'm so jealous of all you. I can't find firmware I can use to root and create a patched firmware to flash mine with. ?
[FYT Android Head Units] marcus82:
me too.. and I'm not able to modify manifest of an apk to force split

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] surfer63:
What do you mean? Another method?

---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------

Well done. You understand the principle of the updater-script
[FYT Android Head Units] marcus82:
I haven't image file unfortunately

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] kpitao:
I'm having the same issue.... followed the instructions to the teeth ..... after the last reboot I check Magisk Manager it it says:

Manager is up to date

Magisk is not installed.....

Here's my patched file

https://drive.google.com/file/d/1VFCfwQPz-objVcn_v4ctRtJi6xHjC3zJ/view?usp=sharing

Are we supposed to rename the file? No were in the instructions said we should rename the file....

By the way I did not renamed....
[FYT Android Head Units] surfer63:
With regard to renaming: The rtf doesn't say to rename it, but it clearly mentions:

The name patched_boot.img is even set in bold font.

So if Magisk creates a file like "magisk_patched.img", you should indeed rename it as the mentioned "updater-script" inside the 6521_1.zip in "/META-INF/com/google/android/" contains

getprop("ro.product.device") == "sp9853i_1h10" || abort("E3004: This package is for \"sp9853i_1h10\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/47522:user/release-keys");
show_progress(0.050000, 5);
package_extract_file("[B]patched_boot.img[/B]", "/dev/block/platform/soc/soc:ap-ahb/c0c00000.sdio/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);

The script wants to flash a "patched_boot.img" and can't find it.

If you still want to use the "magisk_patched.img", you have to change one line in the updater-script

package_extract_file("[B]magisk_patched.img[/B]", "/dev/block/platform/soc/soc:ap-ahb/c0c00000.sdio/by-name/boot");

(And I only used bold font in the code to show you the difference)
[FYT Android Head Units] Lestat-XDA:
Hi,

don't know what file you are using, but on the patched version I uploaded a week ago with the 'April firmware' I used

"magisk_patched.img" on the zip file... but the script was adapted accordingly.

So, if using my provided version, maybe the problem is not the file name.

Have you made any modification on the ZIP file ? (the zip needs to be signed before being flashed)
[FYT Android Head Units] Curro06:
Root no Joying device

Hello everyone!

Finally I was able to root by renaming the .img file that magisk generated for me. Magisk flashed boot.img to me and generated a file called magisk patched.img. I renamed it to "boot.img" and followed the process. It was not successful. I repeated it but this time I named it as it said in the first forum post “patched_boot.img” and with this I was successful.

Thank you very much to all!!! ??????????
[FYT Android Head Units] kpitao:
Did not worked for me..... I did it twice, first I used my file and update the script and the second time I rename the patched the file

I really think that for some reason I need to factory reset my unit first.... but I'm unable because the codes....

Still waiting for Joying reply to me with a solution but I think because I got the radio from Amazon they won't help me.....
[FYT Android Head Units] LunaEros:
Just one note. They don't work on weekends over there. Maybe that's why they haven't responded yet.
[FYT Android Head Units] tchleb:
Have you tried force flashing?

"If flashing not work keep the usb stick plugged, restart the unit and press when the bootlogo appears 3seconds the reset button, release and push quickly again. Maybe you need some tries..."
[FYT Android Head Units] marcus82:
I have a .rar file with 8 compressed file, but not an image file
[FYT Android Head Units] tchleb:
Post the files here, maybe I can help you.
[FYT Android Head Units] marcus82:
I hope this link it works

https://drive.google.com/file/d/1Phdfdg0kc0YsNCmPGnuKBQ0YITbiVKy1/view?usp=drivesdk

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] kpitao:
I did tried that.... like I said somehow mu unit has a lock, it keeps asking for to reenter a pin code to factory reset the unit: I think this is somehow preventing me to flash....

Joying replied to me and ask me to flash the new firmware (April 2020) which I did already; I also flashed the November 2019 .... I need to find a way to reset to factory the unit, before trying something else ...

I flash the unit quite a few times for the past week or so, I'm afraid to brick it.....

For the lock I'm talking about:

I go to settings > User > Backup and Reset (picture 1)

Once I click on Backup and Reset it asks for a code which I enter 3368 (picture 2)

After that I select Erase all Data (Factory Reset (picture 3)

Then I select Restore Factory Settings (picture 4)

After that I get ask to enter the pin again (picture 5)
[FYT Android Head Units] surfer63:
You have a TS9 unit. It is not even FYT compatible.

That firmware of yours is in the kaier encrypted file format. The 4192eb4c-c1fc-11e8-8f83-a7a51df1443b is your encrypted boot image. You need to use the k-support tool to decrypt it and after having rooted it with magisk, encrypt it again to be able to flash it.

There are other threads that describe how to do that (and I am not going to repeat that here as it is not Joying. It would only confuse other users)

Edit: You can start here. It is not a TS9 but the rooting principle is the same.
[FYT Android Head Units] marcus82:
thanks and sorry if I'm writing here but I didn't find any others post on this cpu
[FYT Android Head Units] surfer63:
Don't cross post or I ask the moderator to remove your posts.

First read the sticky post on top of every forum to see what is correct behavior.