Remove or replace Khadas boot logo

[Electr1]

@gar1234

1: Does this require a Linux PC to this work with the logo? I do not have a Linux PC

No, you can do the same procedures from a Windows PC as well.

@gar1234

Am I to presume from your response that means Khadas will not be able to do this for me?

We encourage you to try this by yourself

@gar1234

What about replacing the Animation?

That will involve replacing the bootanimation.zip file, This is a thing that is same among all Android devices, you can check it has been discussed in another forum topic:

Khadas VIM1S Android11 Kernel Customization

You can refer to format of bootanimation.zip from google source: bootanimation format For VIMs Android, the boot animation is in /system/media/bootanimation.zip It’s the same format used among all android bootanimation, you can try to fetch the boot animation currently on the device: adb pull /system/media/bootanimation.zip /some/destination/in/your/computer to push the boot animation from your computer to override the one on the device adb push /some/destination/in/your/computer/bootanima…

Regards.

[gar1234]

Hi -I created/packed the boot up image.
Now I want to use adb and fastboot.
I connected successfully using adb over Wi-Fi (e.g. adb 192.168.1.120).
When I enter this command:

fastboot reboot

I get this response:

< waiting for any device >

[Electr1]

Fastboot can not be used with wifi like adb, it’s a bootloader interface. You need to connect your device with a USB cable for that to work.

For this you can connect your device to your laptop with only the USB cable and have nothing else connected to the VIM, this will ensure it has enough power to work with the device for this operation alone.

[gar1234]

@gar1234

fastboot reboot

I can’t do that - the PC does not supply enough power via USB-C.

I am going around in circles with this issue - all solutions eventually assume you can communicate to the VIM3L via USB-C, but the VIM3L needs to much power

[gar1234]

I will disconnect everything and try again

[Electr1]

Most laptop/PC ports equipped with a USB3.0 port can supply 900mA of current enough to power VIM for testing application. You can even run Android completely off the adb with scrcpy and use your laptop screen as your main display

[gar1234]

I managed to communicate via USB, by using an external booster, so the device appears when I type

adb devices

But when I type

fastboot reboot

I still get the response

< waiting for any device >

[xiong.zhang]

@gar1234

Q3: If I needed the source, where would I get the source code for this specific image?

https://docs.khadas.com/products/sbc/vim3/development/android/download-android-source-code

[Electr1]

Sorry, have you rebooted into flashboot before running the fastboot commands ?

adb reboot fastboot

[gar1234]

Originally, no, I wasn’t rebooting into flashboot, because the original instructions I was given didn’t specify that.
However, this time I did.

adb connect 192.168.1.120
adb devices
adb reboot fastboot
fastboot reboot

When I entered

adb reboot fastboot

The VIM3L reboots, and stays on the Khadas logo page

When I then entered

fastboot reboot

I still get

< waiting for any device >

and it stays there forever

[Electr1]

@gar1234 ensure you run the command in an terminal with administrator privileges otherwise it may not detect the device.

[gar1234]

HI, yes I am running a command window with Admin privileges.
My last post implied I was using adb over Wi-Fi.
I am not.
I have a direct USB-C connection.
These are my commands, with the appropriate responses:

adb devices

Response is 12-digit number and “device”
e.g.

123456789012 device

Next:

adb reboot fastboot

I waited 30 seconds before next command:

fastboot reboot

• < waiting for any device >

[Electr1]

Check device manager of windows to see if devices is being detected or not you might be missing the Android fastboot/adb drivers.

Get the Google USB Driver  |  Android Studio  |  Android...

[gar1234]

Hi
I think the fastboot drivers were missing.
I installed these and got further.
Using these commands I tried to replace the logo:

adb devices
adb reboot fastboot
fastboot flashing unlock
fastboot flash logo logo.img
fastboot flashing lock
fastboot reboot

Here is the full operation:

C:\dev\android adb\platform-tools>adb devices
List of devices attached
123456789012 device

C:\dev\android adb\platform-tools>adb reboot fastboot

C:\dev\android adb\platform-tools>fastboot flashing unlock
OKAY [ 0.047s]
Finished. Total time: 0.047s

C:\dev\android adb\platform-tools>fastboot flash logo logo.img
Sending ‘logo’ (4050 KB) OKAY [ 0.216s]
Writing ‘logo’ OKAY [ 0.200s]
Finished. Total time: 0.564s

C:\dev\android adb\platform-tools>fastboot flashing unlock
OKAY [ 0.053s]
Finished. Total time: 0.053s

C:\dev\android adb\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s

When the VIM3L is now re-booted, there is no boot logo - just a blank/black screen for a few seconds, and then the boot animation starts.

I have tried re-creating the boot logo/img three times - as specified earlier in this post - each time an image size 1920 x 1080px.
I export the image as 16bit BMP file (using GIMP: Export Image as BMP: 16 bits / R5 G6 B5)
I use the aml-imgpack-master to pack the image.

SO all I have succeeding in doing so far is “deleting” the boot logo

[Electr1]

Is the bmp file name “bootup.bmp” ?

[gar1234]

Yes it is - and I have tried this three times

[gar1234]

Also, I am really running out of time to get a solution for my customer

[Electr1]

@gar1234 there must be some error in your steps, I have perfectly described every step necessary to do so and can replicate from my side as well.

@xiong.zhang do you have any additional ideas ?

[xiong.zhang]

This post may be helpful to you

Android Boot Logo on MIPI-DSI failed to change

Which Khadas SBC do you use? VIM3 Which system do you use? Android, Ubuntu, OOWOW or others? Android 9 Pie Which version of system do you use? Khadas official images, self built images, or others? Khadas official images (vim3-android-9-64bit-v230408.img) & self built images Please describe your issue below: Android boot logo failed to change on the MIPI-DSI LCD. But it changed on an HDMI display successfully. Do they operate separately like that? I followed instructions from the link…

[gar1234]

Here, again, are the entire steps that I perform to try and replace the boot logo on the VIM3L

Step 1 - create the logo
I used Microsoft Paint to create a simple logo
Create bootup1.bmp, size is 1920 x 1080 px - size is 5.93 mB
Step 2 - convert the logo
In GIMP, export this image 1920 x 1080px size, 16bit BMP file
The exported file is named bootup.bmp - size is 3.95 MB
Step 3 - pack the logo
Use the aml-imgpack Python2 script to pack the image, as follows:
c:\Python27\python.exe aml-imgpack.py --pack logo.img bootup.bmp
Result is: logo.img - size is 3.95 MB
Step 4 - load the image to the Khadas device
open a command window (run as Administrator)

adb devices
c8631473ccca device
adb reboot fastboot
fastboot flashing unlock
OKAY [ 0.038s]
Finished. Total time: 0.053s
fastboot flash logo logo.img
Sending ‘logo’ (4050 KB) OKAY [ 0.231s]
Writing ‘logo’ OKAY [ 0.200s]
Finished. Total time: 0.563s
fastboot flashing lock
OKAY [ 0.047s]
Finished. Total time: 0.047s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s

When the VIM3L reboots, I get nothing - just a blank screen, instead of the original boot logo. And then maybe 10 seconds later, the boot animation starts.

Your link to this post, seems to imply that I also need to replace the following two files:

bootup_rotate.bmp
bootup_rotate_secondary.bmp
in this directory:

device/khadas/kvim3/logo_img_files/

I cannot find these files:

Here is what I tried:

adb pull device/khadas/kvim3/logo_img_files/bootup_rotate.bmp
adb: error: failed to stat remote object ‘device/khadas/kvim3/logo_img_files/bootup_rotate.bmp’: No such file or directory
adb pull /device/khadas/kvim3/logo_img_files/bootup_rotate.bmp
adb: error: failed to stat remote object ‘/device/khadas/kvim3/logo_img_files/bootup_rotate.bmp’: No such file or directory
adb pull device/khadas/kvim3/logo_img_files/bootup_rotate_secondary.bmp
adb: error: failed to stat remote object ‘device/khadas/kvim3/logo_img_files/bootup_rotate_secondary.bmp’: No such file or directory
adb pull /device/khadas/kvim3/logo_img_files/bootup_rotate_secondary.bmp
adb: error: failed to stat remote object ‘/device/khadas/kvim3/logo_img_files/bootup_rotate_secondary.bmp’: No such file or directory

I did ‘adb shell’, to see what directory / files were on the VIM3L:

kvim3l:/ $ ls
acct cache data init init.usb.configfs.rc lost+found oem sdcard ueventd.rc
bin charger default.prop init.environ.rc init.usb.rc metadata proc storage vendor
boot config dev init.rc init.zygote32.rc mnt product sys
bugreports d etc init.recovery.amlogic.rc init.zygote64_32.rc odm sbin system

SO my questions:

Q1: Can you see anything that I am doing wrong when I am creating, converting and sending the boot logo image?
Q2: Do I have to replace the bootup_rotate.bmp and bootup_rotate_secondary.bmp?
Q3: If so, where are these images located in the VIM3L - I cannot find them?
Q4: How do I replace these images? Do I just the the push command?
Q5: Do I just copy/rename the bootup.bmp file that I created to these two files (bootup_rotate.bmp and bootup_rotate_secondary.bmp) or do I have to do something else?

Please answer all my questions and answer them clearly / precisely.
My customer is getting very frustrated because I cannot deliver a solution

Thank you