Unity's splash screen logo removal, removal, and hiding, on the VR all-in-one machine of the Android platform

First link to the final solution. Friends who want to learn by themselves can go directly to learn. My blog is mainly aimed at Android VR all-in-one machines, but the original text describes the removal of Logos for each platform:

GitHub - kiraio-moe/remove-unity-splash-screen : A full but dirty way to remove Unity splash screen for free

( Good news, I succeeded in my research, and I will post the successful method when I have free time )

( If you want to study, go to the link above. My blog post below has been tested and does not work, but it brings new problems )

If you choose to continue to read my blog, let me first inform you that my blog is a full-process description of the removal of Logo from the Unity program for Android VR all-in-one machines.

I am Unity version 2020.3.30, packaged GSXR (NoloVR) glasses, this glasses is a VR all-in-one machine on the Android platform.

1. Let me talk about the most formal way to remove Unity’s splash screen logo, which is to buy a Unity license to support the official, there is nothing to say.

Second, let’s talk about the traditional and common ways to remove Unity’s splash screen Logo (these methods do not apply to me):

1. How to remove the startup Logo_unity and remove the startup screen without cracking Unity_AlianBlank's Blog-CSDN Blog

Comment: This blog is not written clearly, I am not very good at using it, and if I directly skip the splash screen stage, it will also cause my VR all-in-one machine to fail to initialize. All solutions that skip the splash screen stage will basically cause the VR all-in-one machine to fail to initialize.

2. [Unity] Skip the Unity startup screen/Logo in one step, applicable to all platforms, Unity official API support_unity remove startup logo_TopGames Blog-CSDN Blog Comments: This blog is easy to use, and it really works. But it still directly skips the splash screen stage, which will cause my VR all-in-one machine to fail to initialize. All solutions that skip the splash screen stage will basically cause the VR all-in-one machine to fail to initialize.

3.

Unity Clear Start Logo Video Tutorial - CSDN Programmer Training Institute

Unity3D hides the startup logo_unity removes the startup logo

[Unity Ultimate Profound Meaning] Unity packs and removes the logo on the startup screen, no need to crack it, you will learn it once you learn it

Comments: Handwritten Android arr package, custom startup screen, cover the splash screen of Unity, I provide three blogs for everyone to appreciate, I don’t guarantee that they can be used, anyway, I don’t know much about these things.

4. I have used the PicoVR all-in-one machine, which directly provides the setting option of customizing the startup splash screen. After setting, the VR program will not display the Unity Logo, but the Logo picture you set. If you are capable, you can take a look How is it handled at the bottom.

3. The ultimate solution I newly found (the actual machine test effect has not yet been carried out)

1. First, you need to decompile, re-sign and package the packaged APK file (this process has nothing to do with the Unity editor, and these two steps will be referred to as decompilation and packaging later). It's easy if you can do that. If not, I also have a blog for you to learn from.

Manifest file modification (Android)_Modify androidmanifest_Chu Jiang_wog1st's Blog-CSDN Blog

Note that there are three places to pay attention to when studying this blog:

    First, it is not necessary to modify the Mainfest file. If you don’t have this requirement, you don’t need to change it, just go through the process of decompiling and packaging;

    The second is about the keystore file when packaging. If you know this file and know its function, then naturally there is no problem. But if you don’t know this file, then listen to me, this file is necessary for Android packaging, whether it is packaging in the Unity editor or decompiling and packaging, this file is required. If you usually package without setting this file in Unity, it is because the Unity system automatically sets the default keystore file for you.

    Now the operation of decompiling and packaging is about to be performed. If your current APK file is packaged with Unity's default keystore file, then you have two options before decompiling and packaging:

    One is to go to the Internet to search for keystore file tutorials to learn it, then create your own keystore file, use the Unity editor to package a new APK file, and finally use the new APK file and the keystore file you created to decompile and package;

    The second is that for some reason, the newly created keystore file cannot be used to package a new APK file in the Unity editor, and only the current existing APK file can be used for decompilation and packaging. Then you need to find the keystore file when packaging the current APK file. The default keystore file used by the Unity editor.

   The storage path of Unity's default keystore file: C:\User\Administrator\.android\debug.keystore

    Unity default keystore file key name: androiddebugkey key password: android (very important)

    Third, the command line format of the re-signature step after decompilation is completed: jarsigner -verbose -keystore debug.keystore -signedjar new.apk old.apk androiddebugkey

    ! ! ! ! ! It should be noted that the re-signature command cannot copy the command of the blog in the link above, and needs to be modified according to my command format. Red is the fixed format, green is the name of the keystore file, blue is the name of the re-signed APK you want, yellow is the name of the APK that has been decompiled but has not been re-signed, and purple is the name of the key in the keystore file.

    If you use Unity’s default keystore file to sign and you haven’t changed the name of the keystore file, you only need to modify the names of the old and new apk files in the command, and I’ve filled in the rest. If you are using a keystore file created by yourself to sign, you need to change the green and purple parts to your own.

2. After the baptism of the above blog, you must have learned the process of decompiling and packaging, and now you are officially entering the link of modifying the Logo. Before that, delete the folders and files left over from the decompilation and packaging you learned above.

(1) Let me declare a few names first: APK files packaged from Unity, I will collectively call them Unity.APK; decompiled APK files, I will become decompiled.APK; re-signed APK files, I will Will be collectively referred to as re-signature.APK

(2) The next thing to do is to make sure that you package the APK with the Unity editor.

The packaging settings are as follows:

In the place where the red line is drawn in the picture, you must ensure that the settings are consistent with mine, because this blog only talks about how to modify the Logo in this case. If your settings are inconsistent with mine, please go to learn the article on GitHub by yourself. It talks about other settings How to operate in the situation.

The splash screen settings are as follows:

 Because mine is VR, I don't want to customize the logo, so I set a black background and a black logo. I guess even if you customize the Logo, it will still be presented with both eyes in VR, so it is not recommended that you customize the Logo.

(3) To start this step, download the Unity Resource Bundle Extractor (UABE). I downloaded the 64-bit program of version 3.0. After downloading, you can use it after decompression. The download link is as follows: Publish·Serious Cache/UABE (github . com)

(4) Use apktool to decompile and decompress Unity.APK into a folder (if not, learn the decompilation and packaging process above), find the following files in the path of the folder, and use Unity Resource Bundle Extractor (UABE) Open:

 (5) Find this data and select it:

 (6) Then click the "ViewData" button on the right side of the software to open the data:

(7) Click the plus sign on the left to expand it, and find these two variables:

 

(8) Set both variables to 0: 

 (9) Select this file:

(10) Then save it to another path as follows:

 

 (11) Copy the "unity default resources" file of "other path" to the original path in the decompression folder, and replace the original file: (Before copying, remember to close UABE)

(12) Use apktool to compress the decompressed folder into a decompiled .APK

(13) Use the keystore file to re-sign the decompiled .APK

(14) Finally, the re-signed .APK is obtained, and this APK is the APK that can be used normally. If there is no accident, this APK is installed and run on VR glasses, and the Unity Logo should not be visible. And it will not affect the initialization of VR glasses, because the splash screen stage is still there in essence.

Guess you like

Origin blog.csdn.net/qq_37760273/article/details/129707365