[pinkycz]

Originally Posted by elshanguliyev

Hello, have a good time.
I connected the computer to the monitor but can't access root.
No matter how hard I tried to get root, it was not possible.
Has anyone encountered such a problem?

Hi,
I have similar unit 825X_Pro with Android13 and run into the same dead end.
Mine is


Tried the PX6 way from the start of this thread as suggested by RedErik
Upon connecting via adb attempting to root I get

>adb root
cxj said not suport, 88

that's it.
Trying su in shell gives me "su:not allowed"

will be a bit harder to gain root to these HUs I guess

Any ideas appreciated!

[RedErik]

Originally Posted by pinkycz

Hi,
I have similar unit 825X_Pro with Android13 and run into the same dead end.
Mine is


Tried the PX6 way from the start of this thread as suggested by RedErik
Upon connecting via adb attempting to root I get

>adb root
cxj said not suport, 88

that's it.
Trying su in shell gives me "su:not allowed"

will be a bit harder to gain root to these HUs I guess

Any ideas appreciated!

Your unit is locked down, you would need to root it first. Unfortunately we don't know much about these so can't help you, sorry. Try looking at XDA or 4PDA.ru forums.

[S EyeLand]

Hey guys, I bought this screen for my F90. It's great, resolution is crisp, and the OS is very snappy. Anyway, the default boot animation is the only weak point. The resolution claims to be 2560*720 which seems correct. I'm guessing i would have to create a custom animation. Otherwise, the process would be the same?

[RedErik]

Originally Posted by S EyeLand

Hey guys, I bought this screen for my F90. It's great, resolution is crisp, and the OS is very snappy. Anyway, the default boot animation is the only weak point. The resolution claims to be 2560*720 which seems correct. I'm guessing i would have to create a custom animation. Otherwise, the process would be the same?

That is not a KSW unit. We don't know what the procedure for changing animations is... if there is one at all.

[pinkycz]

Originally Posted by RedErik

Your unit is locked down, you would need to root it first. Unfortunately we don't know much about these so can't help you, sorry. Try looking at XDA or 4PDA.ru forums.

I have now managed to get bootanimation working on my 825X_Pro unit (8259 chipset). I bought it from Ali seller SZ-KIANDA Official Store - Shenzen Kianda Auto Electronic Co., Ltd. The unit runs Android13, mine is 8GB Ram, 128GB SDRAM.
Anyone who would like to give it a try, I suggest to read the RedErik post on the first page of this thread related to PX6 units.
My 8259 unit was only playing "android" glowing logo at the boot start. Confusingly, I did not find this being a dedicated bootanimation, it appears the system has none, so this is Android OS default.
You need to be able to establish adb connection to your HU. Follow the guide to the point where there is

adb root

command. This will probably error as did on my unit, so keep reading.
Enter the following commands:

adb shell

you will now be in HU's shell and enter

su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount

At this point your will be kicked from shell and back to command line.
Insert the USB disk with your bootanimation.zip file and check how is this udentified under your HU (you can use ES Explorer or similar file epxlorer on your HU).
Reconnect back after remount, you should now have RW access to your HU.

adb shell

If you haven't identified how is your USB stick recognised on your system, you can now check in shell too

cd /storage/
ls

My stick is detected as udisk1. As it has two partitions, storage list them as udisk1p1 and udisk1p2. I have stored my boot animation on the primary partition, yours might be different so modify the below to match your input device

 cp /storage/udisk1p1/bootanimation.zip /system/media/bootanimation.zip

That's it. I did not need to adjust permissions using CHMOD so this was the finish for me.
You can now reboot your unit and your effort be rewarded by desired bootanimation playing.



thanks to RedErik for his work, I hope my bit will allow few more guys to enjoy it on their units too now.

[RedErik]

Originally Posted by pinkycz

I have now managed to get bootanimation working on my 825X_Pro unit (8259 chipset). I bought it from Ali seller SZ-KIANDA Official Store - Shenzen Kianda Auto Electronic Co., Ltd. The unit runs Android13, mine is 8GB Ram, 128GB SDRAM.
Anyone who would like to give it a try, I suggest to read the RedErik post on the first page of this thread related to PX6 units.
My 8259 unit was only playing "android" glowing logo at the boot start. Confusingly, I did not find this being a dedicated bootanimation, it appears the system has none, so this is Android OS default.
You need to be able to establish adb connection to your HU. Follow the guide to the point where there is

adb root

command. This will probably error as did on my unit, so keep reading.
Enter the following commands:

adb shell

you will now be in HU's shell and enter

su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount

At this point your will be kicked from shell and back to command line.
Insert the USB disk with your bootanimation.zip file and check how is this udentified under your HU (you can use ES Explorer or similar file epxlorer on your HU).
Reconnect back after remount, you should now have RW access to your HU.

adb shell

If you haven't identified how is your USB stick recognised on your system, you can now check in shell too

cd /storage/
ls

My stick is detected as udisk1. As it has two partitions, storage list them as udisk1p1 and udisk1p2. I have stored my boot animation on the primary partition, yours might be different so modify the below to match your input device

 cp /storage/udisk1p1/bootanimation.zip /system/media/bootanimation.zip

That's it. I did not need to adjust permissions using CHMOD so this was the finish for me.
You can now reboot your unit and your effort be rewarded by desired bootanimation playing.



thanks to RedErik for his work, I hope my bit will allow few more guys to enjoy it on their units too now.

Excellent work! I will include your guide in the post about changing animations. I'm sure it will help a lot of people. Thanks again for sharing that!

[ypolyachenko]

Originally Posted by LuQ

I have Windows 11 Home.
What if I try to change it manually, by factory menu?
I need bootlogo.zip file in OEM folder.
If I make just bootlogo.zip with imagefv.bmp inside, and press "Import", I get information that logo is changed successfully, but really nothing changes, so i think that in bootlogo.zip file should be more specific folders or files (like in bootanimation.zip) to do it right.

I was fighting with bootlogo for some time.
At first, I successfully changed the boot animation part. The rest of the attempts were with a "Success" message, but no real effect.

Then I reset the current boot animation with bootanimation_clear.zip.
Reboot and one more attempt with success for both bootlogo and bootanimation parts.

The content of the OEM folder in my case was
OEM\
imagefv.bmp <-- image created using MaPaint
bootanimation.zip <-- archive created using BootAnimator tool

voila

you can check my bootlogo and bootanimation here

[ypolyachenko]

Originally Posted by elshanguliyev

PX6 guide can you write to me?
Thank you for your help.

Possibly this recent guide will help in your case

[petrutaursu]

I couldn't find a nice one online so I made my own. Link here: https://youtu.be/bjXrH2QU0o8

[Meg_the_Face]

Hi, I'm sorry if this has already been asked, but I couldn't find it. Is it possible to install ID8 Theme on my Android 10 SD 625? Thanks in advance

[RedErik]

Originally Posted by Meg_the_Face

Hi, I'm sorry if this has already been asked, but I couldn't find it. Is it possible to install ID8 Theme on my Android 10 SD 625? Thanks in advance

If you have a native Android 10 unit (i.e. not updated from Android 9), then you can update to the latest A10 version and use the fully unlocked factory config file to enable all UIs. Everything is explained in the first few posts of Android 10 thread.

[Meg_the_Face]

Originally Posted by RedErik

If you have a native Android 10 unit (i.e. not updated from Android 9), then you can update to the latest A10 version and use the fully unlocked factory config file to enable all UIs. Everything is explained in the first few posts of Android 10 thread.

Hi RedRrik, thank you for the info. I didnt see it sorry, i will have a look. And it is defintive a native android 10 head unit.

[Meg_the_Face]

Originally Posted by RedErik

If you have a native Android 10 unit (i.e. not updated from Android 9), then you can update to the latest A10 version and use the fully unlocked factory config file to enable all UIs. Everything is explained in the first few posts of Android 10 thread.

Thanks, i have install it

[beatbop78]

Hi all,

I'm new to this so wondering if anyone could help. I have an ksw-T-M700 OS v1.1.8 running A13 unit in my F87 and managed to change my bootup animation last week following this thread's guides. I'm now wanting to change a few tiles in the ID8 OS which I have done using KswLauncher and kswOverlay-master to repackage the apk after changing the images I wanted to modify locally on my mac.

What I would like to know is weather KswOverlay or the Reworked overlay package installers can work in pushing the apk to the unit as it says they are for versions up to Android 12?

Many thanks in advance.

[RedErik]

Originally Posted by beatbop78

Hi all,

I'm new to this so wondering if anyone could help. I have an ksw-T-M700 OS v1.1.8 running A13 unit in my F87 and managed to change my bootup animation last week following this thread's guides. I'm now wanting to change a few tiles in the ID8 OS which I have done using KswLauncher and kswOverlay-master to repackage the apk after changing the images I wanted to modify locally on my mac.

What I would like to know is weather KswOverlay or the Reworked overlay package installers can work in pushing the apk to the unit as it says they are for versions up to Android 12?

Many thanks in advance.

In theory it will work although I'm not sure how long it will last. In the past there were some issues with overlay sticking for longer than a week. They only worked without any issues on Android 9 and 10. That reworked package is supposed to address that, but I've seen some people reporting that it didn't work for them, the overlays were still disappearing after some time.

[beatbop78]

Originally Posted by RedErik

In theory it will work although I'm not sure how long it will last. In the past there were some issues with overlay sticking for longer than a week. They only worked without any issues on Android 9 and 10. That reworked package is supposed to address that, but I've seen some people reporting that it didn't work for them, the overlays were still disappearing after some time.

Thanks ReErik, I'll give this a go and see what happens!

[vuche]

Hello to all and thanks a lot to you pinkycz!

I'm new to this forum and you were very helpfull with your information, especialy for my "new" 825X_Pro unit bought, not for a BMW, but for a Chrysler PT Cruiser. It has two USB cables (only the 6pins is actually working) and 2 micoSD slots. Fake android 13 on real android 9. 4GB RAM and 64 ROM. Small 5" screen with physical bottons on both sides (very usefull to me).

It was not very clear, and still is not, if my unit has a resolution of 800x480, 1280x720 (what Device Info app tells me) or 1024x600 as seller was pretending... I think once booted it's emulated 1280x720.

Nevertheless, I found out that boot logo has to be 800x480 .bmp or .png to be used. I can confirm that putting the boot logo(s) with whatever name and the extensions .bmp or .png, made with MSPaint on Windows 11, in the root of the USB stick or microSD will make them recognised by the system and added to the list of boot logos. In my unit, it's under Settings / Onboardtainement / Common / Boot Logo - PIN: 5678
hit the "search" icon and you'll find the new usable logo(s). Only the ones with the right resolution, for me 800x480, will be displayed.

So that's it for the boot logo, pretty easy stuff once you know the basics (no really usefull info from the seller, beside the PIN code... / But very usefull info here!)

Now to the boot animation. I have made a few for my car for another unit (AC8227L JCAC10003, 9" screen, 2GB + 64GB, 4 cores, 1024x600) and adapted it with less images, as the 825X_Pro boots faster (8 cores, more RAM), and resolution of 800x480.

Since it's on android 9, no way to switch to wireless adb debugging as the option is not even listed in the developers options. So I thought I'll try with a cable. USB_A (unit) to USB_C (Windows) didn't work -> laptop was displaying "Not enough power to recharge" ;-)
I had a spare USB_A male to USB_A male from an Android TV Box, used to update it, and "taa-daaaa": when plugged the right way - laptop side vs unit side - the radio was recognised as an Android device on the laptop!

That made my day and I could use all your adb commands starting from

adb shell

su @#zxcvbnmasdfghjklqwertyuiop1234567890,.

remount

adb shell

cd /storage/

ls

I had already copied my bootanimation.zip to the root of the microSD card.
My SD card was detected as ext_sdcard1.

"As it has two partitions, storage list them as udisk1p1 and udisk1p2. I have stored my boot animation on the primary partition, yours might be different so modify the below to match your input device" -> wasn't working for me with ext_sdcard1p1 -> ext_sdcard1 was enough.


cp /storage/ext_sdcard1/bootanimation.zip /system/media/bootanimation.zip

That did it! After rebooting my unit I could enjoy my bootanimation playing!

It's smaller than the screen size though, so I'll try with 1024x600 and 1280x720. That's why I'm guessing once the unit has booted, it is emulating another resolution than the native 800x480.

I'll edit this post if I find out anything more.

So again, thanks a lot pinkycz and the others that posted here for your help!
Hopefully my little add-on will help some people.


I can't imagine why it has to be so complicated to do so simple things like making these units fit our cars and likings...!


Edit1:
USB_A male to USB_A male has to be made specially to update via USB_A. I think the data wires are switched. You'll find those cables for sure on Al....ress, e..y, Am..on and others ;-)

Edit2:
Resolution for my bootanimation has definitly to be 1280x720 pixels to fully fill the screen size. I made it last for about 10 seconds as the boot logo stays on for about 15 seconds and then less than 10 sec. left for animation.

My 2nd USB cable (4pins) actualy works fine, I just saw that I set it in USB debug mode in the Factory settings of the unit (Settings - Car Infotainement - About Device - Settings icon PIN 8878 - Others - USB2 Debug Enable). This must make it usable for USB debugging through ADB!

Originally Posted by pinkycz

I have now managed to get bootanimation working on my 825X_Pro unit (8259 chipset). I bought it from Ali seller SZ-KIANDA Official Store - Shenzen Kianda Auto Electronic Co., Ltd. The unit runs Android13, mine is 8GB Ram, 128GB SDRAM.
Anyone who would like to give it a try, I suggest to read the RedErik post on the first page of this thread related to PX6 units.
My 8259 unit was only playing "android" glowing logo at the boot start. Confusingly, I did not find this being a dedicated bootanimation, it appears the system has none, so this is Android OS default.
You need to be able to establish adb connection to your HU. Follow the guide to the point where there is

adb root

command. This will probably error as did on my unit, so keep reading.
Enter the following commands:

adb shell

you will now be in HU's shell and enter

su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount

At this point your will be kicked from shell and back to command line.
Insert the USB disk with your bootanimation.zip file and check how is this udentified under your HU (you can use ES Explorer or similar file epxlorer on your HU).
Reconnect back after remount, you should now have RW access to your HU.

adb shell

If you haven't identified how is your USB stick recognised on your system, you can now check in shell too

cd /storage/
ls

My stick is detected as udisk1. As it has two partitions, storage list them as udisk1p1 and udisk1p2. I have stored my boot animation on the primary partition, yours might be different so modify the below to match your input device

 cp /storage/udisk1p1/bootanimation.zip /system/media/bootanimation.zip

That's it. I did not need to adjust permissions using CHMOD so this was the finish for me.
You can now reboot your unit and your effort be rewarded by desired bootanimation playing.



thanks to RedErik for his work, I hope my bit will allow few more guys to enjoy it on their units too now.

[TonyB]

I would really like to get the stock Android BT instead of the KSW one mainly to connect a OBD dongle and, why not, to connect wireless earphones as if it were a normal tablet.

From what I understand it is not enough to change the KSW BT apk with the Android stock one, would other system changes be necessary?

[RedErik]

Originally Posted by TonyB

I would really like to get the stock Android BT instead of the KSW one mainly to connect a OBD dongle and, why not, to connect wireless earphones as if it were a normal tablet.

From what I understand it is not enough to change the KSW BT apk with the Android stock one, would other system changes be necessary?

As far as I'm aware the stock BT app is still there (at least it was on A9 and A10 KSW systems). It's the system that's heavily modified to disable the stock BT and many other things.

[TonyB]

Originally Posted by RedErik

As far as I'm aware the stock BT app is still there (at least it was on A9 and A10 KSW systems). It's the system that's heavily modified to disable the stock BT and many other things.

Yes, also in A13. There are two bt apps:

/system/app/Bluetooth/Bluetooth.apk=com.android.bluetooth
/system/priv-app/KswBt/KswBt.apk=com.wits.ksw.bt

Do you think if we create a shortcut to com.android.bluetooth it would work Android stock app?

[RedErik]

Originally Posted by TonyB

Yes, also in A13. There are two bt apps:

/system/app/Bluetooth/Bluetooth.apk=com.android.bluetooth
/system/priv-app/KswBt/KswBt.apk=com.wits.ksw.bt

Do you think if we create a shortcut to com.android.bluetooth it would work Android stock app?

It's not that simple, as I said these systems are heavily modified and the stock app is disabled. We never worked on a way to restore it.

[Chilled]

RedErik Are the KWS style unit the better ones to get, or are there better units out there?

Was looking at this unit
https://www.aliexpress.com/item/1005006398499536.html

Is this one of those , or should I be looking at something else.

Also for the EVO, they mention and AUX -USB. Do you know how that works, as in does it show up as a USB thumb drive on my iDrive? or is that the amp/dac like soundkeys Cyrus/ Fiio?