[FYT Android Head Units] iamrance.asa:
The specific unit that I have is by Navitech and for 2004-2008 Acura TL models. However, this will work for other units as well and not only for this unit.

Now there is a lot of debate to if you really need root on these UniSoc/Spreadtrum FYT units. There is also a good list of modifications that can be found here that doesn't require root, thanks to @surfer63 . However, I like root functionality as well as being able to actually pass SafetyNet to download apps like Netflix, HBO Max, Hulu, Etc. (though, these are not really functional for me as of now). I'm also one who likes to block system-wide ads with Adaway, use Viper4Android, etc. So it's really up for you to decide if you really want it.

As always, modifying a device in such a way is never completely safe and can result in a bricked unit. SO DO THIS AT YOUR OWN PERIL! Only you are responsible for anything bad that happens by doing this. It's a risk that all of us take individually.

View attachment 6082121

[RECOMMENDED] Optimized Magisk Kernel by @surfer63

Modified Version of Maria Dantas' Kernel with Magisk and other modifications.

This is by far the easiest method. It's updated frequently and it keeps your data intact.

>Follow the link in the title to the official XDA thread and follow the instructions.

FYT Kernel Workbench (Available in Optimized Kernel thread)

This is the method I mainly use due to Magisk Kernel not being a thing when I started then it used Magisk v23 up until March 2024. I will most likely be using Optimized Magisk Kernels from now on instead. THIS WILL MOST LIKELY RESULT IN LOSING YOUR DATA!​

Download FYT Kernel Workbench from the link in the title.

Unzip on a Linux system

Edit the Config.ini to fit your file locations (don't select root if it has this option)

Place 6315/6316.zip in the location you specified in step 3

Open Linux terminal in main folder of FYT Workbench

Type "sudo su" then input your password

Unpack the 6315/6316.zip with "./01_unpack.sh" in terminal (use ./00_import.sh first if you have the files setup where you need to import)

When unpacked, go into _tmp/_firmware folder (or whatever you named them in the config.ini) and pull the boot.img (might need to use explorer as root to do this)

Push boot.img to device with Magisk apk installed and patch the boot.img with the version you're trying to install.

Pull patched boot.img back on linux system, rename to just "boot.img" before replacing the original boot.img in _tmp/_firmware folder.

Now you can repack with the repack.sh then flash to the unit like usual.

This barely scratches the surface of the things you can achieve with this tool. I highly recommend you play around with the other features.

Universal Root Method by @gordgelin )(pulled from here and translated to English):

**Works with newer builds. Big thanks for the work by @gordgelin !**​

💾 INSTALLATION :​

PS Just in case, your original boot was copied to a flash drive under the name stock_boot.img.​

Universal_ROOT​

​

MD Kernel by @mariodantas )

**This method uses SuperSu instead of Magisk but has integrated tweaks and helpful tools/features. Great work by @mariodantas **​

You can find everything about it here and also here

Flash the same a normal 6315_1.zip

Clean FAT32 flash drive

The downloaded MD Edition 6315_1.zip

lsec6315update file

lsec_updatesh folder

updatecfg.txt (check it make sure it doesn't have any twipe active except twipe_cache or you will lose your data)

Optional: Bootanimation.zip (you can replace this with the one you want but make sure the resolution/orientation is compatible)

Plug into head unit. Press reset then press reset again when the car logo appears -OR- plug it in with your unit on and it should detect it and ask if you want to update

Warning: (Thanks @mariodantas for this info)

Root method (OLD Method)(pulled from here and here):

**This method is old and I will try to update it soon. Don't use if your firmware is after jun 2022**

Grab this zip: developer.zip and a copy of your device's firmware (You can typically ask the seller you bought your unit from for it. They have always provided them to me when I've asked)

Unzip the your firmware which is in a 6315_1.zip (if you have a different name on it then you'll need to modify the zip to fit yours - not recommended if you're not very familiar with these devices)

Grab the boot.img from the firmware and patch it in magisk manager.

Pull the patched_boot img from your device

Unzip the developer.zip and add this 6315_1.zip in the folder. Unzip and add your patched boot img in the root of this folder like in this img (rename it to just boot.img)

View attachment 5723441

Now compress this folder and name it 6315_1_input.zip

Now it's time to sign it. You'll need Java Runtime installed.

Other java versions gave me issues so I downloaded Java jre7 and just linked the folder with the command. It was giving me sign errors with the new version I have installed

View attachment 5723443

You'll need to open command prompt in the developer folder's root with the testkey files in it.

Just put the location of where you have the java.exe for jre7 in parenthesis at the first. then add this after it

-jar signapkv2.jar -w -v testkey.x509.pem testkey.pk8 6315_1_input.zip 6315_1.zip

or if you have in the same place as mine then you can use my modified start.bat (or the default one if you have jre7 as your default java)

If everything went correctly, you will now have a signed zip :D

View attachment 6082126

Flashing Firmware/Files

**6315 for UIS7862/s, 6316 for UIS8581a, 6318 for UIS7870 -- packages should match this numbering scheme for the processor that your unit has. The x in the following should be the number that corresponds to your processor (DO NOT CHANGE A FILE'S NUMBER TO FIT YOUR NUMBER IF THE ONE YOU DOWNLOADED DOESN'T MATCH THE SCHEME FOR YOUR UNIT'S PROCESSOR!!!)**​

On formatted FAT32 Flashdrive:

Firmware

631x_1.zip

lsec631xupdate file

config.txt (PULL THIS FROM YOUR UNIT BEFORE FLASHING ANYTHING)

updatecfg.txt (sometimes optional)

lsec_updatesh folder (if package comes with it)

Extras/Files/Modifications

(required) lsec631xupdate file

bootanimation.zip -- if you want to add a different bootanimation

logo.bmp -- if you want a different boot splash

lsec_updatesh folder (if package comes with it)

apks, other files, etc.

Make sure to follow the instructions for whatever mod/package you're trying to install. Usually, you just have to unzip the package and place all the files within as is inside the root of the flash drive

After adding appropriate files, add to the usb slot of your unit.

Pop-up should appear saying it has detected an update and if you want to restart

select the update/yes option or wait 5s for it to automatically restart

if it doesn't pop-up, you can hold the reset button with a pin until then release it when unit restarts -- press the reset again right before splash pops up. It should then reboot into update.

It will now start to flash everything. When it is done it will tell you to unplug your flash drive.

If everything was done correctly, your unit should reboot with the changes taken place.

View attachment 6082127

Files

6315_1.zip (Modified and provided by @surfer63 )

Developer.zip (provided by @prrlhkr)

patched_boot.zip (ONLY USE IF YOU HAVE THE EXACT SAME UNIT AS ME!) - Rename it to 6315_1.zip for flashing

Factory Firmware (Firmware provided by the seller)

Mekede Firmware (Current one used on my unit with DRM support)

MODS/Software Tweaks

FullScreen/Remove AC Controls

View attachment 5728857View attachment 5728879

Rename or delete apk in "oem\app\190000000_com.syu.air" **

[Recommended] Alternatively, you can flash the @surfer63 's disable_aircolayout.zip

Launcher59_Acura

View attachment 5985981

repackaged Mekede launcher59 with Acura TL 3G (Anthracite Gray) - edited by me. If you need another color or model car, let me know.

*the empty space is an integration space you can edit in settings. You can use Maps and some other apps I just didn't have it set in the screenshot**

VolumeBar_green

finally found the assets for the volume pop-up bar. The original yellow with the dot was too unaesthetic.

currently based on Seb21's MS mod (build 2123051715) -- if you can call it that since it's just a few visual asset changes. I mean, it's just the MS mod APK with a different color volume bar.

If you have the MS mod already of the same build or earlier, then you can just install it like a regular apk (which is what I did on mine). If you don't have @seb21 's mod or you have a newer version, then install it how @seb21 has it outlined in the linked post.

View attachment 6044160

A/C Controls_green

if you haven't noticed a trend by now, I like editing my UI's to green.

this is a repackage of the canbus apk which should install like a regular apk update unless you happen to have a newer version. mine is from the Mekede firmware I have on my unit (mkd-7862_UI21_1024x768_20220913_lzp)

View attachment 6043323

Bluetooth Discovery Fix(for RGB/LED Strips, other unrecognized bluetooth devices)

add the following lines to your devices config.txt then flash it

sys.fyt.systemobd=true

persist.lsec.enable_a2dp=true

ro.lsec.btname=Bluetooth 2

Recommendations:

Vivid Launcher - they finally added a portrait layout. I think it is the most aesthetically pleasing car launcher currently available.

**Note: I am not affiliated with anyone/any software mentioned. It is all just what I use.**

DRM L3 (if you have no DRM currently)

**Most of this, again, is taken from this post because it is the best amount of literature on the subject. I have just streamlined and abridged it for this specific use since it is a broad, all-encompassing post.**

BEFORE ANYTHING! Make sure you have a working firmware for your device AND a configuration backup! Also, back up your data . You can find out how to do this here in the linked post right under this section with @surfer63 flash_any_AllAppUpdate.zip (their link, not mine)

Grab a firmware with DRM support such as Mekede/Navifly, which I will use (the one I used is added here since Mekede removed it from their site) . I have not tested other resellers. Teyes most likely won't work if you don't have a Teyes. You'll want one with the same CPU (UIS7862 and UIS7862s are fine to interchange). You'll also want the same screen resolutions in the same orientation. If you have a 768x1024 Tesla Screen like me, grab this one like me (password: 3368). Can also be found here on Mekede's official software site, I just did the direct link so you grab the TS3/TS5/TS6 Vertical firmware instead of the wrong one.

After you have your software downloaded, unzip it and then use an archiver such as 7zip to open archive (not extract) the AllAppUpdate.bin (password: 048a02243bb74474b25233bda3cd02f8)

Navigate to \app and open the fyt.prop with a notepad application

Replace the number for "ro.build.fytmanufacturer=" with the one from the pre-flash configuration fyt.prop (which is the one for your devices reseller)

Do the same for "ro.fyt.uiid= "

Save the fyt.prop, close it, then click yes when 7zip asks if you want to update the file with changes

Now add these to a freshly formatted fat32 flash drive (or microSD if that's what your device has)

Modified AllAppUpdate.bin,

6315_1.zip

Use the one from the downloaded firmware or you can use MD Edition here which is confirmed working with my install.

lsec6315update

File and folder

config.txt

From YOUR DEVICE'S configurations backup!

updatecfg.txt

if you want to keep your data, then make sure it doesn't have twipe_data or twipe_all. It should only have test and maybe twipe_cache. It is recommended that you do twipe_data but you can try without it if you really want.

Now add this flash drive to the usb port on your device and it should have a popup that will restart it and start installing. You can also push the reset button on your unit then press it again when the boot logo shows while you have this drive plugged into the usb to get it to start on bootup.

If everything installs without error, you should now have DRM L3. and you can finally watch DRM content!

**SafetyNet isn't passing on mine currently so I'm currently testing**

View attachment 5929555 - CONFIRMED!

View attachment 5929557 - CONFIRMED!

View attachment 5929559

- CONFIRMED!

View attachment 5929561 - CONFIRMED!

**Even if they're confirmed working now, it doesn't mean they will stay working. These are currently working for me with SafetyNet failing, sideloaded them since a number of them won't show up for a failed SafetyNet device in the Play Store. Mileage may vary**

In-Car Sim Cards:

Mint Mobile - USA ✓

SafetyNet Passing/GooglePlay Certified:

View attachment 5985983View attachment 5985977View attachment 5985979

Safetynet & Play Store Certification is working as of now for my unit with Magisk installed. Mine has Pixel 6 Pro fingerprints right now but it's not necessary for them to pass. I will update how I achieved this soon. :)

Passing Safetynet/Certified Play Store:

I'm using a combination of the Play Integrity module, Shamiko module, and a depreciated MagiskHide Props Config module set to Pixel 6 Pro configuration for both 1 & 2 options. Currently play store is certified and I'm able to update apps such as Hulu directly (one of the main reasons for me).

Another option could potentially be using Play Integrity Next instead but I haven't verified. I will be going that route if anything breaks again. You won't need MagiskHide Prop Config and probably won't need Shamiko if you do :)