Question Joying 8.8 inch Android 10 JY-HQS01N4G-1 how to root

Search This thread

Robbiemo

New member
Aug 17, 2022
4
0
I'm trying to root my head unit, but right now if I backdate my firmware to be compatible with the files in this thread I can no longer use carplay.

I've used magisk to create my own boot image, and I've put it into what I think would be the correct thing to make it work but I have no idea how to sign my file, can anyone chime in on how to do that?
 

Attachments

  • boot.img
    19.8 MB · Views: 5
  • 6315_1.zip
    9.5 MB · Views: 6

surfer63

Senior Member
May 4, 2010
4,367
1,931
Zwolle
hvdwolf.github.io
I'm trying to root my head unit, but right now if I backdate my firmware to be compatible with the files in this thread I can no longer use carplay.

I've used magisk to create my own boot image, and I've put it into what I think would be the correct thing to make it work but I have no idea how to sign my file, can anyone chime in on how to do that?
Actually you do not even mention whether your have a FYT sc9853i. I hope you have that.

You have not done it as described in the post with the developer.zip. Your 6315_1.zip contains the wrong manifest files. It contains the full commands to erase and reflash all partitions! In this case you would have an empty system with only a boot.img. Be very happy that you tried this with an unsiged zip that the system didn't want to flash.
You need to remove the nvmerge files and your updater-script should only contain the following:

Edit: Code removed.

Signing the zip file is very simple, but you obviously didn't read that either.
Code:
java -jar signapkv2.jar -w -v testkey.x509.pem testkey.pk8 6521_1_input.zip 6521_1.zip

You specifiy an input zip which is not signed yet and followed by the name of your to be created zip.

But as mentioned: your manfest in the 6315_1.zip is wrong.

And again, like I have already posted so many times: Why do you want to root your unit? You must have very good reasons to do that as you will also lose functionality.
 
Last edited:

Robbiemo

New member
Aug 17, 2022
4
0
Actually you do not even mention whether your have a FYT sc9853i. I hope you have that.

You have not done it as described in the post with the developer.zip. Your 6315_1.zip contains the wrong manifest files. It contains the full commands to erase and reflash all partitions! In this case you would have an empty system with only a boot.img. Be very happy that you tried this with an unsiged zip that the system didn't want to flash.
You need to remove the nvmerge files and your updater-script should only contain the following:
Code:
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("patched_boot.img", "/dev/block/platform/soc/soc:ap-ahb/c0c00000.sdio/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);

Signing the zip file is very simple, but you obviously didn't read that either.
Code:
java -jar signapkv2.jar -w -v testkey.x509.pem testkey.pk8 6521_1_input.zip 6521_1.zip

You specifiy an input zip which is not signed yet and followed by the name of your to be created zip.

But as mentioned: your manfest in the 6315_1.zip is wrong.

And again, like I have already posted so many times: Why do you want to root your unit? You must have very good reasons to do that as you will also lose functionality.
I have the UIS7862, I haven't even tried to upload the unsigned zip to it, I knew that wouldn't work. I have only tried to use the ones from the beginning of this post but they make the unit get locked on the Google splash screen.

I went through the process again, I downloaded the 6315_1 file that you had posted in post 10, took the zip, added my boot image (the patched one), and tried renaming it to "6521_1_input" to use the .bat in the developer folder to sign it, but it will no longer work with the renamed file. I don't understand the coding aspect of this, I tried going through the JAR/JAVA files in the folder to find any reference of the input files so I could change the name but I haven't found anything

So what I'm left with is the attached file, that is unsigned.

The reason why I want/need to root the unit is like the others in this thread I have a C5 corvette and the left 80 pixels are cut off by the bezel so I need to use a screen resizer app to correct it. (Unless there is a simple way to make a screen resizer work without rooting the device). I don't care about any functionality outside of CarPlay.
 

Attachments

  • 6315_1.zip
    9.3 MB · Views: 3

surfer63

Senior Member
May 4, 2010
4,367
1,931
Zwolle
hvdwolf.github.io
I have the UIS7862, I haven't even tried to upload the unsigned zip to it, I knew that wouldn't work. I have only tried to use the ones from the beginning of this post but they make the unit get locked on the Google splash screen.

I went through the process again, I downloaded the 6315_1 file that you had posted in post 10, took the zip, added my boot image (the patched one), and tried renaming it to "6521_1_input" to use the .bat in the developer folder to sign it, but it will no longer work with the renamed file. I don't understand the coding aspect of this, I tried going through the JAR/JAVA files in the folder to find any reference of the input files so I could change the name but I haven't found anything

So what I'm left with is the attached file, that is unsigned.

The reason why I want/need to root the unit is like the others in this thread I have a C5 corvette and the left 80 pixels are cut off by the bezel so I need to use a screen resizer app to correct it. (Unless there is a simple way to make a screen resizer work without rooting the device). I don't care about any functionality outside of CarPlay.
Sorry, I made errors. I thought you had an sc9853i and the content of my previous post was for a sc9853i. I removed it.

A few posts ago it was mentioned by @mariodantas that the latest firmwares can't be signed anymore with the test keys. The lsec6315update has obviouslty been altered to only allow the real signed zipped file and not a test keys signed zip.
Next to that the lsec6315update also checks on the date of the firmware itself not allowing downgrades.
Thinking this over I think it is no longer possible to root your unit.
 

Robbiemo

New member
Aug 17, 2022
4
0
I have the UIS7862, I haven't even tried to upload the unsigned zip to it, I knew that wouldn't work. I have only tried to use the ones from the beginning of this post but they make the unit get locked on the Google splash screen.

I went through the process again, I downloaded the 6315_1 file that you had posted in post 10, took the zip, added my boot image (the patched one), and tried renaming it to "6521_1_input" to use the .bat in the developer folder to sign it, but it will no longer work with the renamed file. I don't understand the coding aspect of this, I tried going through the JAR/JAVA files in the folder to find any reference of the input files so I could change the name but I haven't found anything

So what I'm left with is the attached file, that is unsigned.

The reason why I want/need to root the unit is like the others in this thread I have a C5 corvette and the left 80 pixels are cut off by the bezel so I need to use a screen resizer app to correct it. (Unless there is a simple way to make a screen resizer work without rooting the device). I don't care about any functionality outside of CarPlay.
I realized what I was doing wrong for the signing, and I got that fixed. Thanks! This is my signed file, can you take a look at it and make sure I didn't mess it up? I apparently don't have the best track record on this.

Edit: just saw the last response, is there any alternate way to resize the screen that you know of, or am I just out of luck for the time being?
 

Attachments

  • 6315_1.zip
    9.3 MB · Views: 6

surfer63

Senior Member
May 4, 2010
4,367
1,931
Zwolle
hvdwolf.github.io
Edit: just saw the last response, is there any alternate way to resize the screen that you know of, or am I just out of luck for the time being?
I am afraid you are out of luck when it comes to interactive changing it as that requires root rights.
Another option might be to try it via an lsec script. That is run on "flashing" the unit and runs with root access, but if the USB stick only contains an lsec script and the lsec6315update you might be able to change the settings with the "wm overscan" command. It is deprecated as of Android 11, but it will still work and the uis7862 is Android 10 (whatever fake version the resellers might want to sell us).
But that approach is not interactive. You have to guess the right setting (-80 ?) and then issue the command. If it is not correct you need to redo it and eflash" your unit.
And I am not sure it will really work.

The complete overscan command is
Code:
wm overscan [reset|LEFT,TOP,RIGHT,BOTTOM]
So I assume for you the command would then be
Code:
wm overscan 80,0,0,0
 
  • Like
Reactions: marchnz
Thinking this over I think it is no longer possible to root your unit.

I think that someone posts in 4PDA an "universal-root-script", and I think that this one run on 7862lsec and 8581lsec, copying a shell script into unit and executing it inside the unit (not the USB key) and patching the boot.img directly, I neder used it

Another way to flash an older version of firmware (I think) is to use an old "lsec6315update" file, but I never tried that !
 

Robbiemo

New member
Aug 17, 2022
4
0
I think that someone posts in 4PDA an "universal-root-script", and I think that this one run on 7862lsec and 8581lsec, copying a shell script into unit and executing it inside the unit (not the USB key) and patching the boot.img directly, I neder used it

Another way to flash an older version of firmware (I think) is to use an old "lsec6315update" file, but I never tried that !
I can flash the older firmware with the lsec6315update file, but it seems like I'm not able to root any version that has the wireless carplay working.

I tried using one of the older lsec6315update files to flash the patched boot on a recent build of the firmware but it complained about signature verification.

It's obviously a long shot that wont work, but I reached out to Joying themselves to see if they can present any ideas on how to get the screen resized. If they have anything useful I'll be sure to post it here.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    attached are the files that I tried it with. Your zip file with my patched boot file (renamed to boot.img) and the lsec6315update file.

    You did not sign the zip. Attached your zip, but now signed.
    2
    Before I got your reply I actually went ahead and installed the latest version of Magisk (version 22) from their website, installed it, and opened it. Then I got the "Screen Shift" app and it worked to resize my screen, so I assume the rooting was successful. And I didn't need to download any special file manager app.

    So I don't think installing/opening Magisk prior to rooting is necessary, but appreciate the help guys!

    I made my screen resolution 1200x480 to fit within my C5 Corvette center console opening, and it fits perfectly. Note: Avoid the "overscan" screen settings because it makes apps appear cutoff.
    2
    My current need is that I can't seem to watch youtube tv from the unit. I like to sit in my car on my lunch break and watch some of my DVR'd stuff, but apparently the joying head units are missing any widevine drm stuff, making youtube tv not work. Installing those libraries via magisk module would typically be impossible without root. If this has changed, I'd love to know how! JY-UQS15N4G, if it matters.
    I wrote a couple of posts about Modding your Joying fyt sc9853i without root
    Again: the principles are exactly the same but the binaries and files have changed. That way you can also install libraries, but please understand that some libraries also require system libraries or "hooks" in system libraries. Also with root that would not be successful.
    For more info about the uis7862 FYT units and modding them, also read 4pda. I don't have a uis7862, so I never dived as deep into the matter as with my Sofia 3GR, PX5 and sc9853i.
    1
    Thanks everyone. Thanks to this and the thread OP linked, I was able to root mine as well (JY-UQ128N4G). Just in case anyone in the future has this model, I used Joying's 2021.1.19 firmware for my model above and created the attached signed zip.
    1
    Hi- is the resizer still working well, and every app has been compatible with it? I've heard some issues with some popular apps not playing nice with resized screens, like Waze and Google Maps.

    Btw, I have the same exact Joying unit in my C5 Corvette.

    To be honest I’m not sure. It works great on the apps I’m using but then again I mostly just listen to music and I use Sygic maps due to it being offline mode and they work great. You can always try using one of the other resizer apps, maybe newer resizer will work better with newer apps.