[UPDATE] For the lazy people: You do not have to follow the whole tutorial. Simply download the attached bootanimation.zip and copy it to your /system/media as you are used to. If you want to know what I modified, read the tutorial.
Hey people!
I have a Motorola Razr (Germany/EU Retail with Android 4.0.4), already rooted with EternityProject's EasyRootICS.
The standard bootanimation on EU-Razr ist boring, so I downloaded the Verizon Droid Razr animation und put it into /system/media
Problem: The sound file starts half a second after the animation and one can see that! And that is annoying the **** out of me!
My solution to that is as follows:
1. Extract bootanimation.zip to your computer.
2. Open desc.txt, this is the standard content on Droid Razr:
Code:
# 540 wide, 960 tall 15 frames per second
540 960 15
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, leave blank
# droid
p 1 7 01_droid
# mobility
p 1 0 02_mobility
s droidhd.ogg
# loop
p 0 0 03_loop
As you can see, the audio file is linked after 7 frames (at 15 frames per second that is almost half a second) have already been shown and that is why it starts that late.
3. Move up the line that begins with "s", so that the specific part at the end looks like this:
Code:
# droid
p 1 7 01_droid
s droidhd.ogg
# mobility
p 1 0 02_mobility
# loop
p 0 0 03_loop
4. Use 7-zip to create an uncompressed ZIP-file, name it bootanimation.zip. It is very important that it is uncompressed, because android cannot open compressed files as bootanimations. You can do this with 7-zip by changing the compression-level from "Normal" to "Store".
5. Copy the new bootanimation.zip to /system/media
6. Reboot and enjoy!
I uploaded my modified bootanimation.zip (as above) - the other filenames are selfexplanatory. Of course you have to unpack one of the audio-files from droidhd.zip to use it for the bootanimation.
For everyone who is interested in modding or creating bootanimations, I recommend this how to: http://www.addictivetips.com/mobile/how-to-change-customize-create-android-boot-animation-guide/
Hello, do you know why after this mod, I end up with a black screen? I just replaced my original verizon boot animation with yours
Hello Olao99,
as you perhaps can see, as a German I just own a Razr Maxx XT910 (EU/GSM) and do not know which differences there are in comparison to an XT912 (Verizon/CDMA). So far: I just followed my own instructions on this page again and it works fine for me.
Does your phone boot up and only does not show any boot animation? Or is it bricked and does not boot up at all?
Greetings
derLichtschalter
I rebooted it again, and it worked, thanks for the workaround.....
The audio is now at sync, however when booting, the animation lags a bit, making it look choppy until the end is reached. I guess is too much for it to display? I don't know, probably the fps?
In desc.txt you can see in the first line "15 frames per second". For a smooth animation there should be at least 24 frames per second, so it is normal that it looks a little bit choppy as you say.
Thanx soooooo much for this...
Related
hi all, i'm having problem creating my custom boot animation. i think i got stuck on the desc.txt file. Already tried changed the EOL conversion to UNIX using Notpad++. Will email the zip file upond request. Thanks in advance
Details:
Part0 = 35 files (0.png - 34.png)
Part1 = 8 files (35.png-42.png)
desc.txt
480 480 30
p 1 0 part0
p 0 34 part1
Feel free to send me the zip and I can take a look if you'd like. We have a bunch of people working on boot animations that can help. Check signature.
Sent from my Green Rom Project HTC Glacier on Tap a Talk
http://www.greenromproject.com/forum
helmi666 said:
hi all, i'm having problem creating my custom boot animation. i think i got stuck on the desc.txt file. Already tried changed the EOL conversion to UNIX using Notpad++. Will email the zip file upond request. Thanks in advance
Details:
Part0 = 35 files (0.png - 34.png)
Part1 = 8 files (35.png-42.png)
desc.txt
480 480 30
p 1 0 part0
p 0 34 part1
Click to expand...
Click to collapse
try changing the 34 to 0
also try setting the desired resolution to your phones resolution...for example:
desc.txt
480 800 30
p 1 0 part0
p 0 0 part1
explained:
'480' is the width of the animation
'800' is the height of the animation
'30' is the desired fps of the animation
'p' defines an animation part
'1' how many times this animation part loops
'0' defines a pause (max 10)
'part0' is the folder name where the animation images are
'p' defines another animation part
'0' defines that it loops forever (until android starts)
'0' defines a pause
more info here
stoute said:
Feel free to send me the zip and I can take a look if you'd like. We have a bunch of people working on boot animations that can help. Check signature.
Sent from my Green Rom Project HTC Glacier on Tap a Talk
Click to expand...
Click to collapse
Sent you the zip file
Rodderik said:
try changing the 34 to 0
also try setting the desired resolution to your phones resolution...for example:
desc.txt
480 800 30
p 1 0 part0
p 0 0 part1
explained:
'480' is the width of the animation
'800' is the height of the animation
'30' is the desired fps of the animation
'p' defines an animation part
'1' how many times this animation part loops
'0' defines a pause (max 10)
'part0' is the folder name where the animation images are
'p' defines another animation part
'0' defines that it loops forever (until android starts)
'0' defines a pause
Click to expand...
Click to collapse
Thanks mate. i'll let you know the result
Edit:
Finally, managed to get it work. The ZIP file need to be compressed as Stored otherwise it wont work xD
okay, on other phones ive done this in the past with ease... but its been a while!
NOTE: i am using Resurrection Remix 1.3 with siyahkernal 3.1rc4
I have extracted the bootanimation.zip to see its structure.
i successfully replaced it HOWEVER, when it comes to the part that loops (p 0 0 part1) it just shows up black. i have 35 images in there is there some sort of limit or file size limit? (fiiles are all under 20KB)
so it plays 'p 1 0 part0' but does not play the 'p 0 0 part1'
i even tried making it a loop only with 'p 0 0 part0'
it is in the same layout as the original boot zip with a few more/less images...
i have even cleared dalvik cache to give it enough time to display!
check to make sure you put in the right folder names for each loop:
part0
part1
and then your desc.txt should have some reading for it like this:
480 800 24
p 1 0 part0
p 0 0 part1
PS
are the image files all named properly? and are they png format?
Thanks for your reply,
it was in exactly the same format that the original bootanimation zip was:
desc.txt
480 800 30
p 1 0 part0
p 0 0 part1
File Layout
part0 --> (0000.png - 0100.png) - WORKING
part1 --> (0001.png - 0050.png) - NOT WORKING
the only odd thing i can see is that it starts with 0001.png in part1, but it shouldnt make a difference...
i noticed when i have this setup
480 800 30
p 1 0 part0
it works fine but if i were to do this:
480 800 30
p 0 0 part0
with the same images it just shows a black screen (or stuck on first image coz its black)
Hi, ive created a few bootanimations myself so am all too familiar with problems you can have, naming files wrong, wrong file formats, aspect ratios etc.
Try this program from one of the xda developers, works like a charm for me, it'll create the desc.txt file, lets you specify the boot loop folder, and creates the bootanimation.zip for you (you'll have to name it that yourself when prompted).
http://forum.xda-developers.com/showthread.php?t=1234611
If it helps, let me know, by hitting thanks, and be sure to thank the original dev
Thanks mate, i was looking at that yesterday but i was at work... and it blocks the download as hacking =[! i will try when i get home tonight!
EDIT: for some reason it is working now, (the download) =D after i upgrade to resurrection remix 1.4 and siyahkernel 3.1rc5 i will update here see if it works
To be honest, any of the images or other files not named properly or starting with wrong numbers can cause issue.
Your part0 folder should start with:
0001.png as should your part1 folder.
See if that helps (don't forget to rename the rest of them too (so it isn't skipping number order).
cyberboob said:
To be honest, any of the images or other files not named properly or starting with wrong numbers can cause issue.
Your part0 folder should start with:
0001.png as should your part1 folder.
See if that helps (don't forget to rename the rest of them too (so it isn't skipping number order).
Click to expand...
Click to collapse
To share some experience: I've created boot animations, the program i used creates them with numbers start for example as 10001, 10002, 10003 etc, not 00001, and they always worked.
On occasion, i've deleted images from the animation sequence, from the begining of the sequence, mid way, from the end, so now, for example, the numbers start at 10065, 10066, with perhaps numbers 10070, 71, 72 missing and resuming at 10080 etc, again the boot animations have always worked.
I've also created animations using jpeg, and again, they have always worked.
Wezi said:
To share some experience: I've created boot animations, the program i used creates them with numbers start for example as 10001, 10002, 10003 etc, not 00001, and they always worked.
On occasion, i've deleted images from the animation sequence, from the begining of the sequence, mid way, from the end, so now, for example, the numbers start at 10065, 10066, with perhaps numbers 10070, 71, 72 missing and resuming at 10080 etc, again the boot animations have always worked.
I've also created animations using jpeg, and again, they have always worked.
Click to expand...
Click to collapse
Sounds like good info i may give it a try, either way in my testings for boot animations, i decided to build a tool, which can automatically create multiple png's generating a fade out effect on the selected layer! at the moment its only in alpha but please give it a try feedback is welcome!!
http://forum.xda-developers.com/showthread.php?p=25000616#post25000616
The point is... both folders need to start same numbers. Ok, do as you guys please.
(*you also don't have to split them up - all 1 folder)
I'm trying to get this bootanimation http://forum.xda-developers.com/showthread.php?t=1592942 to work with sound.
I've tried converting the wav file to ogg, adding "s PowerOn.ogg" to desc.txt but still no luck.
Any suggestions?
I think that it doesn't work on CM10, but on AOKP yes.
Wait till Kayant fixes bootanimation speeds in his source built AOKP, then try w/o modding
Here is the content of desc.txt from stock t-mobile android 2.2.2 http://forum.xda-developers.com/showthread.php?t=1178243
# 540 wide, 960 high, 15 frames a second
480 854 15
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, say nothing
# motorola generic intro
p 5 0 part0
# carrier
p 1 0 part1
# freeze frame
p 0 0 part2
# must have newline at end of each part
Click to expand...
Click to collapse
so, s in front of a filename should trigger bootsound. But the s line is missing although there is a boot_att.ogg in /system/media.
I"ve tried the solutions from http://forum.xda-developers.com/showthread.php?t=1771089
and http://forum.xda-developers.com/showthread.php?t=1420991
but didn"t work
This is out of my understandig http://forum.cyanogenmod.com/topic/3434-cm6-startup-and-shutdown-sound/
I deffinetly remember that there was a stock sbf 2.2, maybe from orange france, that had a bootsound.
so... the easy way by adding s in front of the file name didn't work
I've created a flashable zip file for CM7, tested with latest built by: FuZZ_ cm7.2.0-20120909.0101-Defy
Credits to
[Bootanimation] StarWars // Great Bootanimation! NOW With Sound! [ALL ROMS!]
[TRICK/CWM3/EDIFY] Output to recovery UI from shell script
[TUTORIAL]How to make your own boot animations (with sound if you want)
I just put it all together
The zip file can be used with any bootanimation and sound, just replace android_audio.mp3 and bootanimation.zip from system/media inside the zip file attached to this post or from here http://www.freefilehosting.net/starwarsdefy
I used the starwarsdefy.zip and I get the animation but no audio on Quarx's CM10 02.11 build with custom kernel. Any ideas? I sure love the animation, but it would be so much cooler with the audio!
androidtester80 said:
I just put it all together
The zip file can be used with any bootanimation and sound, just replace android_audio.mp3 and bootanimation.zip from system/media inside the zip file attached to this post or from here http://www.freefilehosting.net/starwarsdefy
Click to expand...
Click to collapse
Thanks! I've tried a few things for this myself before and did not succeed...I even thought that this was not possible on the Defy...
I used your zip and it worked fine on a recent cm7 build from maniac103.
Although, I'd like to add that it is not possible to adjust the volume level before the bootup is complete so it is important to set the audio level properly on the mp3 file...yours is/was a little high for my taste and I almost woke up the two kids almost pulled the battery out also....
Finally, since this is a nice tweak and this thread seems to get little response, I will add a link to your post #4 on my [] AL's [] CM7 Tweaks and Mods List Roundup thread - with all due credits to you :highfive:
I hope that we will see more great bootanimations with sound done by Defy owners...
Cheers
/AL
Hi guys, I've made a boot animation for my Z3, I read a few tutorials and followed each to the letter.
I used ffmpeg to grab the frames from a video and put them in two folders, named; part0 and part1.
Part0, I want to play once. Part1 I want to play once and then loop until the phone boots fully.
my desc.txt file looks like this:
Code:
1080 1920 30
p 1 0 part0
c 1 0 part1
p 0 0 part1
I tried it without the line "c 1 0 part1" and it still didn't work.
I previewd the file with depotovski01's boot animation factory and it played perfect, but when I installed it on my phone using ROM toolbox pro and rebooted, the first part played fine then the screen went white and I was in a bootloop.
Had to change it through recovery to boot again.
Any ideas what's causing this?
Thanks in advance!
Hey folks, thanks to @iElvis sharing his or her logo 'data' from the OP6. I have adapted my previous OnePlus programs that let you change the splash screen to work with the OP6. This means that the encoding of the data structure and the encoding of the image data are done. I do not have a OP6 and can not test certain things like where to put the modified file. In the past, flashing was always easy (and always has been especially with the OnePlus models).
My holdup and why I need the XDA/OP6 community support is to find out where to exactly put this modified file. In the past I haphazardly made a super fast in-memory program for altering the splash screen for the Nexus 6p that was (and is currently) at a roadblock for one reason. That reason was Google used ELFs to populate partitions (not short people with pointy ears and green clothing), and at that time utilized separate partitions that the ELFs populate. Not all were ELF generated, but that is outside of the scope of what I do because to a certain point the ones that I wanted to change were generated that way.
This concept of splitting partitions, back then, was just trying to grab a footing on seamless upgrades initially from what I have read up until this newer style. I have put some research into some things involving this, but Google is kind of bland in it's description of what this all means. This is different than the Nexus 6P that I mentioned previously, and if you read that last link, it may be just as easy as flashing it to both partitions logo_a & logo_b. One partition is always active and has two different statuses, which make the device 'ideally' always bootable after an OS update.
Most of my research was done through reading a lot of the open source code put out by the AOSP for "fastboot". You can learn more than you can ever derive from documentation in this realm. I hope to hear some feedback of attempts so that I can delete all of this up above
Please read below so you can better understand this type of encoding being used:
What Is A Raw Image?
A raw image, whether it be a file or an image in memory, is simply pixel data. There is no extra information like width, height, name, end of line... Absolutely nothing, just pixel data. If you have an image that is raw and the resolution is 1080x1920 and you are using a typical RGB24 or BGR24 (like the ones used here), then your exact filesize or size in memory will be 1080x1920x3! We use 3 here because there is one byte for the R or red component, one for the G (green), and one for the B(blue).
What Is A Run Length Encoded Image?
A run length image encoding uses a count ;usually a single byte (char), 2 bytes (short int), or 4 bytes (long int); and then the pixel components. So instead of writing out 300 bytes of '0's to make a line of 100 black pixels. Black is RGB(0,0,0). You could encode this as 100, 0, 0, 0. And only use 4 bytes of data to get the exact same image as the 300 byte raw image. All the run length encoding I've found, except the Motorola style which is a little different, use a run length encoding that is pixel-oriented like this.
Now I've found this new one and it is a byte-oriented run length encoding. This is for runs of bytes, not pixels. You may think, well whats the big deal? When you add a little area of color, you increase the run length encoded image in you logo.bin immensely! You use 6 bytes per pixel if there aren't any runs of color data. If you had an image that was a 1080x1920 black image with a 25 pixel horizontal line in the middle. The encoder would be doing runs of black data efficiently until it reached the red area.
.....0 255 0 255 0 255 0 255 0 255 0 133 /// we've reached the top left corner of the red line /// 13 1 30 1 255 1 // << that was just one red pixel!! in bgr color order (13, 30, 255) <<// And it keeps going through the rest of the red pixels on that line using 6 bytes per pixel, which is the opposite of compression. Before reaching the red line the encoding was decoding to 255 zeros over and over, until finally 133 zeros. 255 zeros is 85 black pixels stored in just 2 bytes!
This type of encoding is ONLY good for grey scale images. It is not good with color, but it still will handle color of course. In grey scale, the Red, Blue, and Green data components are always the same values. All the way from black (0,0,0) to white (255, 255, 255); including every shade of grey in between>>>(1,1,1) (2,2,2) (3,3,3)....(243, 243, 243) (254, 254, 254)<<<
One other difference in this method of run length encoding is that the color byte is before the count, which is backwards from all of the other methods.
The attachment contains the executable that was compiled using mingw32 on a 64 bit Windows 10 PC. The awesome PNG library that I used for generating the pngs is LodePng, the source can be found here.
To use the OnePlus 6 Logo Injector:
Decode your logo.bin:
Code:
OP6Logo -i logo.bin -d
All the PNG 's will be extracted from logo.bin. Edit the PNG(s) that you want to change...
Note:
Your original "logo.bin" file is never changed, it is just read. If the file you try to load isn't a logo file, or a different style, then the program will tell you and exit.
Inject the image(s) back in to the logo.bin:
Code:
OP6Logo -i logo.bin -j fhd_oppo fhd_at
To list whats in your logo file:
Code:
OP6Logo -i logo.bin -l
For a more detailed list:
Code:
OP6Logo -i logo.bin -L
If the colors are messed up use the "-s" switch while decoding.
Code:
OP6tLogo -i logo.bin -d -s
If you had to use the "-s" switch to decode properly, you'll have to use it to inject also:
Code:
OP6Logo -i logo.bin -j image_name -s
Note:
You can put as many names after "-j" as you want, and it's not case sensitive. You also don't have to put the whole name. If you just put "-j fhd" every image in the logo.bin that starts with "fhd" will be injected. There has to be a PNG with the name in the directory though
The size of your modified.logo.bin will displayed along with the original size, if everything went good. The 'splash' partition is 16 MB on the OP6. If you use too much color on too many of the images you will easily go over 16 MB. The program will tell you and delete the "modified.logo.bin" that was created. If for some strange reason you would like to keep it, use the "-B" flag on the command.
The last step is to flash the modified logo file via fastboot with the command
Code:
fastboot flash LOGO modified.logo.bin
Use this at your own risk.
Always make backups.
Always.
Source
Source:
I haven't had a chance to work up a custom splash and flash it just yet, in part because I realized that on this phone, the splash screen only shows up for a split second before it's replaced by the "Your phone is unlocked and insecure, don't put sensitive files on it blah blah" warning. So I'm not sure this is going to do a whole lot for us. I'm going to try later tonight or this weekend and report back. Pretty sure "flash logo" should work fine, but it will flash only to the active partition. We may need to "flash logo_a" and "flash logo_b" to get it on both partitions.
Also, thanks for posting the source. I'm going to see if I can get this to compile in Xcode so we have an OSX version.
Edit 6/10: I can't get it to compile in Xcode, but I'm sure it's something I'm doing wrong.
Anyone tested it splash screen
Okay, welp, I'm throwing in the towel on this one. The bootloader warning is not in text like it was on the HTC phones I've modded to remove it. On those phones, the text showed up in the bootloader file in a hex editor, and could be replaced with empty spaces to remove it.
I pulled the boot file from /dev/block/bootdevice/by-name/ and searched through it. None of the text in the warning can be found with a simple search. As I suspected, that warning screen looks like it's a function coded into the boot process, which means removing it is probably impossible.
work Fine !
file :
lodepng.h
lodepng.c
OP6Logo.c
# gcc lodepng.c -c
# gcc OP6Logo.c -c
# gcc *.o -o OP6_prog OR # gcc lodepng.o OP6Logo.o -o OP6_prog
# ./adb shell
# su
# cd /dev/block/bootdevice/by-name
# ls --color --all
lrwxrwxrwx 1 root root 16 1970-01-06 04:29:20.549999999 +0100 LOGO_a -> /dev/block/sde20
# dd if=LOGO_a of=/sdcard/LOGO_a
exit
# ./adb pull /sdcar/LOGO_a ./
# OP6_prog -i LOGO_a -d
MODIFY YOUR PICTURE .....
# ./OP6logo -i LOGO_a -j fhd_
you have modified.logo.bin
Just dd if of and work fine !
And for the Real Splash :
./adb pull /system/media/bootanimation.zip ../
God bless
gao0309 said:
file :
lodepng.h
lodepng.c
OP6Logo.c
# gcc lodepng.c -c
# gcc OP6Logo.c -c
# gcc *.o -o OP6_prog OR # gcc lodepng.o OP6Logo.o -o OP6_prog
# ./adb shell
# su
# cd /dev/block/bootdevice/by-name
# ls --color --all
lrwxrwxrwx 1 root root 16 1970-01-06 04:29:20.549999999 +0100 LOGO_a -> /dev/block/sde20
# dd if=LOGO_a of=/sdcard/LOGO_a
exit
# ./adb pull /sdcar/LOGO_a ./
# OP6_prog -i LOGO_a -d
MODIFY YOUR PICTURE .....
# ./OP6logo -i LOGO_a -j fhd_
you have modified.logo.bin
Just dd if of and work fine !
And for the Real Splash :
./adb pull /system/media/bootanimation.zip ../
God bless
Click to expand...
Click to collapse
Way to remove bootloader unlocked warning?
NO
Please create flashable zip. Of splash screen
I'm trying this on linux on a 6T boot splash screen but I get a segmentation fault:
Code:
__________________________________________________________-_-
OP6 Logo Injector v1
Written By Makers_Mark @ XDA-DEVELOPERS.COM
_____________________________________________________________
FILE: logo.bin
_____________________________________________________________
RGB is the color order. Use "-s" switch to change it to BGR.
#01: Offset:0
Header=SPLASH!!
Width=1080
Height=1920
Data Length=81798
Special=1
Name=
Metadata=
Segmentation fault
Any idea why?
foobar66 said:
I'm trying this on linux on a 6T boot splash screen but I get a segmentation fault:
Any idea why?
Click to expand...
Click to collapse
For 6T, maybe you need look at this thread
https://forum.xda-developers.com/oneplus-6t/development/tool-splash-screen-modification-t3874158
Sent from my ONEPLUS A6000 using XDA Labs
I tried to report that the error memory could not be read under Windows 10 and wimdows7. Then I executed the following instructions under Linux and still reported the error. What can I do, oneplus 6, Android 9.0?
gcc lodepng.c -c
gcc OP6Logo.c -c
gcc *.o -o a.out
./a.out -i logo.bin -d
The following are the results of implementation：
__________________________________________________________-_-
OP6 Logo Injector v1
Written By Makers_Mark @ XDA-DEVELOPERS.COM _____________________________________________________________
FILE: logo.bin _____________________________________________________________
BGR is the color order. Use "-s" switch to change it to RGB.
#01: Offset:0
Header=SPLASH!!
Width=1080
Height=1920
Data Length=77716
Special=1
Name=
Metadata=
Segmentation fault
Code:
C:\Users\denie\Documents\logo>OP6Logo -i logo.bin -d
__________________________________________________________-_-
OP6 Logo Injector v1
Written By Makers_Mark @ XDA-DEVELOPERS.COM
_____________________________________________________________
FILE: logo.bin
_____________________________________________________________
BGR is the color order. Use "-s" switch to change it to RGB.
#01: Offset:0
Header=SPLASH!!
Width=1080
Height=1920
Data Length=81798
Special=1
Name=
Metadata=
C:\Users\denie\Documents\logo>
Any ideas?
Does this work?
Prakyy said:
Does this work?
Click to expand...
Click to collapse
There's no way to hide the Google warning about unlocked bootloaders, if that's what you mean.
iElvis said:
There's no way to hide the Google warning about unlocked bootloaders, if that's what you mean.
Click to expand...
Click to collapse
Really... This is what I've been searching all over for for my 6t... Get rid of the stupid bootloader unlock warning. On all my other devices we always used a custom made boot-logo.bin and installed it on slot a and slot b using fastboot.. I guess if it could be covered up it definitely would have by now. ?
Edit added: I just read the thread. From what I've gathered basically this device (6&6t) is designed different and that's why we can't tamper with/cover up the bootloader warning message.
flash713 said:
Really... This is what I've been searching all over for for my 6t... Get rid of the stupid bootloader unlock warning. On all my other devices we always used a custom made boot-logo.bin and installed it on slot a and slot b using fastboot.. I guess if it could be covered up it definitely would have by now. ?
Edit added: I just read the thread. From what I've gathered basically this device (6&6t) is designed different and that's why we can't tamper with/cover up the bootloader warning message.
Click to expand...
Click to collapse
I gave up after a lot of experimenting. I'm not aware of anyone managing it.
iElvis said:
I gave up after a lot of experimenting. I'm not aware of anyone managing it.
Click to expand...
Click to collapse
You should get an award for your XDA signature. ?? It's funny because it's real and oh so true! The way some people comment on things never ceases to blow me away. I see some posts and I think to myself, "what the hell?" "Who raised this person!?" There are definitely many different types of humans out there in the world that's a fact. I try and stay out of it as much as possible. ? lol.
It sucks we can't just make a ton of boot logos and cover that up. Oh well the 6 & 6t are awesome devices!! Usually whenever I end up on down the road selling my phone and purchasing another one from eBay or swappa things similar to this begin to be solved and then 15 custom roms all drop outa nowhere all at once. ? Happens every...single...time...haha!! Thanks for giving it a shot! :good: