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

[25aaj835]

I can't reset to factory settings.

 

[surfer63]

I can't reset to factory settings.

First of all: Create a new thread. You are polluting this uis7862 thread with Sofia 3GR questions. Thoe Sofia 3GR and uis7862 are completely different systems.
Next: you can't update to 6315 as that is for a completely different CPU and architecture.

 

[Robbiemo]

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?

 

[surfer63]

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.

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.

 

[Robbiemo]

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:

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.

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.

 

[surfer63]

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]

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?

 

[surfer63]

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

wm overscan [reset|LEFT,TOP,RIGHT,BOTTOM]

So I assume for you the command would then be

wm overscan 80,0,0,0

 

[mariodantas]

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]

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.

 

[mickchip]

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 !

Here is the Univeral_ROOT_7862_9863_8141_9853 tried it on my 8.8inch Joying uis7862 and it worked fine. unzip to a flash drive, plug in and let it update and reboot then install the included magisk.apk and your done.

 

[Vette00]

I see that this thread is fairly out of date, but curious if anyone found success in getting a newer Joying HQS01N4G-1 (Feb 2023) Rooted? I bought this unit for my C5 Corvette and need to adjust the screen size because of the smaller bezel. I have researched and tried the step by step instructions but keep hitting errors. From reading post #66 above it sounds like the signature process might be my problem. Just curious if a work around has been found. I did see the wm_overscan suggestion, but I see no validation that it worked so I haven't attempted that.

 

[Vette00]

FWIW - I tried the Universal Root offered in post #71, followed the instructions listed in the post and readme file, and it did not work. Got an immediate Android error.

 

[gopro_2027]

Where is the developer.zip everyone has been referring to? I am on a more recent update and I need to sign my own. I have tried downloading some older zip's such as what @Z0siz has mentioned "Android 10.0 1280X480 Old UI 2021.7.5" but there is no developer.zip in any joying update that I can find.
Secondly has anyone managed to get android 11 with usb debugging working OR usb debugging working on the oem android 10?
All I am trying to do is debug my app on the device (it crashes on joying but not my phone) and this joying unit does not seem to support any form of usb/adb connection. It won't even show up as attached to your PC if you connect a dual sided usb a between the unit and a laptop. That combined with weird permission issues often has made this unit such a pain to work with, but I digress, I figure if I can get root for on device adb commands OR android 11 (wireless debugging) I should be able to solve all my problems in one way or another. I have the patched boot.img file from magisk. Please assist, thank you!

 

[gpieper]

I see that this thread is fairly out of date, but curious if anyone found success in getting a newer Joying HQS01N4G-1 (Feb 2023) Rooted? I bought this unit for my C5 Corvette and need to adjust the screen size because of the smaller bezel. I have researched and tried the step by step instructions but keep hitting errors. From reading post #66 above it sounds like the signature process might be my problem. Just curious if a work around has been found. I did see the wm_overscan suggestion, but I see no validation that it worked so I haven't attempted that.

I'm in the same boat as you. I just bought a Joying HQS01N4G-1 and tried to root it with no success. I'm just going to widen the bezel opening and paint the affected area.

 

[surfer63]

Where is the developer.zip everyone has been referring to? I am on a more recent update and I need to sign my own. I have tried downloading some older zip's such as what @Z0siz has mentioned "Android 10.0 1280X480 Old UI 2021.7.5" but there is no developer.zip in any joying update that I can find.
Secondly has anyone managed to get android 11 with usb debugging working OR usb debugging working on the oem android 10?
All I am trying to do is debug my app on the device (it crashes on joying but not my phone) and this joying unit does not seem to support any form of usb/adb connection. It won't even show up as attached to your PC if you connect a dual sided usb a between the unit and a laptop. That combined with weird permission issues often has made this unit such a pain to work with, but I digress, I figure if I can get root for on device adb commands OR android 11 (wireless debugging) I should be able to solve all my problems in one way or another. I have the patched boot.img file from magisk. Please assist, thank you!

I'm in the same boat as you. I just bought a Joying HQS01N4G-1 and tried to root it with no success. I'm just going to widen the bezel opening and paint the affected area.

Android 11 is fake. It is still Android 10. Read/Search the forum.
Rooting via the developer zip does not work on these units. Use @mariodantas's MD-EDITION to root. Read/Search the forum.
USB debugging only works after enabling the developer options. Read/Search the forum.

The default density is 160 for these units (don't know for the 2000x1200 units). Setting the density can be done with an lsec script. It can be done via a property (ro.sf.lcd_density=) or via the (deprecated but still working) "wm" command via "wm density xyz".
Via an lsec script you can also slightly reduce the resolution with something like "wm size 1260x700", and "wm size reset" to undo it.
To change top/bottom/left/right margin, you can use "wm overscan [reset | left, top, right, bottom]. Also from an lsec script.

Edit: Or use @mariodantas's MD-EDITION, install a terminal app, give it root rights, and issue the commands from the terminal.

 

[gopro_2027]

Android 11 is fake. It is still Android 10. Read/Search the forum.
Rooting via the developer zip does not work on these units. Use @mariodantas's MD-EDITION to root. Read/Search the forum.
USB debugging only works after enabling the developer options. Read/Search the forum.

The default density is 160 for these units (don't know for the 2000x1200 units). Setting the density can be done with an lsec script. It can be done via a property (ro.sf.lcd_density=) or via the (deprecated but still working) "wm" command via "wm density xyz".
Via an lsec script you can also slightly reduce the resolution with something like "wm size 1260x700", and "wm size reset" to undo it.
To change top/bottom/left/right margin, you can use "wm overscan [reset | left, top, right, bottom]. Also from an lsec script.

Edit: Or use @mariodantas's MD-EDITION, install a terminal app, give it root rights, and issue the commands from the terminal.

I guess you aren't aware but usb debugging does not work on this device by just enabling dev options. I think it's something to do with it acting as a host device instead of a slave device and or usb OTG. It only wants to accept other slaves like flash drives for example. I tried many different combinations of cables and adapters and devices and settings and none would work. I ended up refactoring my app for android 10 and it fixed my issues, I never got debugging working.
Personally not concerned with root otherwise so I won't be trying MD-EDITION but somebody else should give it a shot. Thanks for the tip on that and the density!

 

[surfer63]

I guess you aren't aware but usb debugging does not work on this device by just enabling dev options. I think it's something to do with it acting as a host device instead of a slave device and or usb OTG. It only wants to accept other slaves like flash drives for example. I tried many different combinations of cables and adapters and devices and settings and none would work. I ended up refactoring my app for android 10 and it fixed my issues, I never got debugging working.
Personally not concerned with root otherwise so I won't be trying MD-EDITION but somebody else should give it a shot. Thanks for the tip on that and the density!

Debugging can be made to work. There are several examples of it on this forum. It is just harder to do, but it can be done.

I always say that rooting should not be done on these units. It is totally unnecessary and comes with other not-working issues as both Google and FYT don't want it (anymore).
But if users want to root, they can go ahead.