Related
On my G2x i have CM7 and the boot goes as follows.
1.) Bland LG logo
2.) Flashy colorful LG boot animation logo
3.) CM7 boot animation with spinning arrow.
I want to change either step one or two to something different, preferably step 1, its super ugly. I despise two different LG logos in a row. Some dev please help. I cant get it right. Nobody has posted an easy solution yet.
Thanks
to do that is risky business.. you have to modify the primary and secondary bootloaders... (correct me if i'm wrong) there is a higher risk of rendering your phone unusable.. (BRICK) i will research it and see what i come up with.. if you flash eb the second bootlogo is awesome but the LG is there and you can always search bootanimation and download.... out it in system/media and reboot easy peasy....
web_ninja said:
to do that is risky business.. you have to modify the primary and secondary bootloaders... (correct me if i'm wrong) there is a higher risk of rendering your phone unusable.. (BRICK) i will research it and see what i come up with.. if you flash eb the second bootlogo is awesome but the LG is there and you can always search bootanimation and download.... out it in system/media and reboot easy peasy....
Click to expand...
Click to collapse
Nope! It's a pain to do, but as far as I know it's not dangerous. The splash screen (one or both? unsure) are contained in the boot.img file that can be rewritten via flashing a zip from Clockworkmod. For instance, if you flash the Trinity kernel, it will change your splash screen (to a really, really ugly one, but that's beside the point). It involves "cpio" archives and a little bit of Linux acumen.
See this thread for instructions: http://forum.xda-developers.com/showthread.php?p=15626524#post15626524
I don't know Linux. No apk that does it for you?
Sent from my LG-P999 using Tapatalk
No there is no apk. You are editing the initrd.gz, apk's don't have access to that part of the system.
As for the first logo, when you first turn on your phone, that's really not editable without hacking the hardware, I'd highly suggest living with it.
First logo - part of the hardware on the phone, coded in.
Second log - part of the initrd.gz (logo.rle file inside it)
Third (boot animation) is in /system/media/. It's called bootanimation.zip. (Easy one to replace.)
You'll never be able to do this without linux, windows doesn't have any kind of support for cpio archives. Plus with the way linux file permissions work, it's way too easy for you to break them when you copy them to a windows partition. The number one reason for bootloops on android is improper file permissions. (For the logo when the linux kernel is loading, logo 2 i call it.)
The first LG Logo is not part of the hardware... It's in the boot.img file. It was easily changeable on HTC Phones.
No, it was. On the hd2, for example, if you wanted to change that logo (when you first turn it on, it was the tmobile logo if you had tmobile us version) you had to flash a ruu to update that image. (Yes, it was easily done, but not so much on this phone.)
I think you're confusing the second image, (before the boot animation), which is the logo.rle file. It's in the boot.img, inside the initrd.gz. (This can be easy to confuse, especially if you're running cm7 or anything based off it, because the logo is the same, and it just flashes real quick.) If you look at the 2.3.3 based ones, there is a blank screen between logo one and the boot animation. For some reason, that logo doesn't load, and that's where the second logo would be, the one I'm referring to. (On 2.2 it was the lg logo with the semi-animated loading bar underneath it.)
mstrk242 said:
No there is no apk. You are editing the initrd.gz, apk's don't have access to that part of the system.
Click to expand...
Click to collapse
Hmmm, time to throw together a shell script to make this easier for those not command-line friendly.
And if you have a Mac, this should work there as well (I assume there's cpio support, there must be). Anything Linux/UNIX.
Yup. It works on mac as well, from what I've heard. (I don't use macs much myself, I can't stand macOS. But the procedure should be quite similar.)
mstrk242 said:
No, it was. On the hd2, for example, if you wanted to change that logo (when you first turn it on, it was the tmobile logo if you had tmobile us version) you had to flash a ruu to update that image. (Yes, it was easily done, but not so much on this phone.)
I think you're confusing the second image, (before the boot animation), which is the logo.rle file. It's in the boot.img, inside the initrd.gz. (This can be easy to confuse, especially if you're running cm7 or anything based off it, because the logo is the same, and it just flashes real quick.) If you look at the 2.3.3 based ones, there is a blank screen between logo one and the boot animation. For some reason, that logo doesn't load, and that's where the second logo would be, the one I'm referring to. (On 2.2 it was the lg logo with the semi-animated loading bar underneath it.)
Click to expand...
Click to collapse
It's still Software-Based.
thanks i didnt know that....when i was on a vibrant messing with the sbl and the like was risky.... soft bricked many times... so sweet i will have to look into it and try it...
Ok well I will try to change LG logo #2 so if someone would be so kind to tell me exactly how and ill go for it.
Sent from my LG-P999 using Tapatalk
I'm also interested in learning how to do this... =^]
Sent from my LG-P999 using XDA App
Well, if we can extract the boot.img using a program such as unyaffs or something like that, we can swap the images.
And there's an app in the Market called BootFlash, but it currently only works on HTC Devices. It allows HTC Users to changed their splash screens. Let's hope they add support for the G2X!
britishtq said:
Ok well I will try to change LG logo #2 so if someone would be so kind to tell me exactly how and ill go for it.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Instructions from mstrk242: http://forum.xda-developers.com/showpost.php?p=15627311&postcount=1025
The instructions from that thread assume you already know how to unpack the boot.img file and can see the initrd.gz within it. If you don't, I'd suggest starting here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
*edit*
The important parts are under the section Unpacking, Editing, and Re-Packing the images, however I'd suggest reading it all. It really gives good info, and an explanation of how it works.
Ok, I figured I'd make a super detailed howto on how to do this, so here it is:
First off, download the following file:
http://jamezelle.com/myfiles/split_bootimg.zip
Now, unzip that, it's a pearl script. (split_bootimg.pl) Copy that, and your boot.img to a directory. Type the following:
./split_bootimg.pl boot.img
This will create 2 new files in the directory, boot.img-kernel, and boot.img-ramdisk.gz. The ramdisk is what you want. Now, inside the directory you created and split the boot image, make yet another directory (I'll call it temp for the purposes of this howto)
cd temp
now, type the following:
gunzip -c ../boot.img-ramdisk.gz | cpio -i
Now, inside the directory you have successfully decompressed the ram image. (Which on my other post I refered to as initrd.gz, same thing, different phone in this case )
You'll see a bunch of files there, the one you are interested in for the init boot logo is called initlogo.rle. THIS is the file you need to edit to change the boot image to whatever you want. (If you are unsure how to do this, google rle editing, or something similar, not going to go into that here.)
After making all the changes that you want (also a useful tip, the init.rc is a very useful file as far as android booting, if you take the time to learn android's init script language you can do some cool things.), go up one directory. (cd ..)
now you should be back in the directory that has the following:
boot.img, boot.img-kernel, boot.img-ramdisk.gz, and split-bootimg.pl. I'd highly suggest copying your boot.img-ramdisk.gz that's in that directory (which is the original) to another folder, then delete it. (Otherwise you're going to overwrite it anyways). After you have done this, go back into the temp directory that has all the files you changed.
Type the following;
find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz
This will create the boot.img-ramdisk.gz in one directory level up (It's important to do it this way, otherwise you'll end up packing a ramdisk file inside another ramdisk file).
Ok, almost there, now you just need to repack the boot.img file
To do this, you'll need mkbootimg, which i highly suggest compiling from the android repo. (Google it, again, not going into that here.)
Copy the boot.img-kernel file and the boot.img-ramdisk.gz file to another directory, so you don't pack uneeded files into the boot image. Go to that directory, and do the following:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz -o boot.img
If you have done it correctly, you'll see a boot.img file in there. You're done. Replace this in the cwm zip, and flash.
Ok, one more little helper (because I'm in a good mood today ), here are the files you'll need. I have included bootsplit file and the mkbootimg file, so you don't have to bother compiling them (the bootsplit is the same as the link I gave in the post above, but I figured to be nice I'd pack them both into one easy zip file.) With this, no mkbootimg compiling required. (Keep in mind this is compiled for x86, since that's what I use. For x64 you'll have to compile it yourself.)
Good luck everyone.
Oh man, thank you. Ill let you know how it goes tonight.
Sent from my LG-P999 using Tapatalk
i found a thread here
http://www.g2xforums.com/t-mobileg2x-rooting/(splashscreens)-by-maco-designs/
has ready to flash splash screens look into the zips to help you replace the files you will need for splash screen
How do I remove the boot logo or splash screen? I am not sure the proper term for it.
When I turn my phone on I see the standard logo followed by another lg logo which came with the rom I installed. These two logos seem to be delaying my custom boot animation. The boot animation only gets half way before going to the lock screen.
tldr; How do I remove the splash screens that come before the boot animation?
Love you xda you are are amazing.
http://forum.xda-developers.com/showthread.php?t=753788 Go to this link
I would like to completely remove the splash screens not change them. The splash screens seem to be delaying the start of my bootanimation.
Yes ofcourse! System is preparing to extract bootanimation.zip!!
If you change the 'splash' to the first frame of your bootanim it will be the best thing for you!
Greets
____________
mDroid - Tapatalk
Phone: LG-P500
ROM: Ciaox' openOptimus
Kernel: franco .35
Theme: /
Tweaks: /
Wishlist: Galaxy Nexus
I am referring to an image that is appearing which is separate from the boot animation. I want to disable that image.
mDroidd said:
Yes ofcourse! System is preparing to extract bootanimation.zip!!
If you change the 'splash' to the first frame of your bootanim it will be the best thing for you!
Greets
____________
mDroid - Tapatalk
Phone: LG-P500
ROM: Ciaox' openOptimus
Kernel: franco .35
Theme: /
Tweaks: /
Wishlist: Galaxy Nexus
Click to expand...
Click to collapse
Ya, that makes sense. But I'm referring to the second splash screen which seems to be ROM specific.
Sent from my LG-VM670
you'll have to split the boot.img, remove the file initlogo.rle from the ramdisk (that's the second splash,) and recombine the boot.img
not for the faint of heart.
Open framework-res.apk. Look in assets\images. Those are the bootscreen images. If you wish to turn off the animation you'll have to edit the corresponding .xml (I don't remember off hand what or where it is). This will require you to decompile framework-res.apk edit and recompile.
Or like others have said use a bootanimation.zip with a static image, like in devoid froyo.
Turducken said:
Open framework-res.apk. Look in assets\images. Those are the bootscreen images. If you wish to turn off the animation you'll have to edit the corresponding .xml (I don't remember off hand what or where it is). This will require you to decompile framework-res.apk edit and recompile.
Or like others have said use a bootanimation.zip with a static image, like in devoid froyo.
Click to expand...
Click to collapse
Even if i use a bootanimation with a static image the other splash screen will appear. Thanks for the info it should help point me in the right direction. I was looking at init.rc, initimage.rle or something along those lines.
The first bootscreen is in boot.img the second is in framework-res.apk.
Would boot.img be the location of the ROM specific splash screen?
I technically have 3 boot type things.
lg boot logo
rom specific boot logo
bootanimation
The bootanimation is easy enough to change. Where is the first one located? You said the second is in boot.img correct?
post #7 above.
bigsupersquid said:
you'll have to split the boot.img, remove the file initlogo.rle from the ramdisk (that's the second splash,) and recombine the boot.img
not for the faint of heart.
Click to expand...
Click to collapse
the first silver lg is supposed to be in the 'splash' MTD partition (mtd3 on the Optimus V,) but I couldn't ever get it to flash anything different with fastboot, or get its contents with dump_image either.
There is another one after that they came with my ROM is that on boot.img and how do I disable it?
Sent from my LG-VM670
you're talking about the second splash.
see post #7 in this thread.
bigsupersquid said:
you're talking about the second splash.
see post #7 in this thread.
Click to expand...
Click to collapse
Can this be done from with in windows? The guides I have found on messing with boot.img use linux commands for messing with the ramdisk.
I've read you can use cygwin to do linux stuff on windows without a virtual machine.
It's fun to set up, though. I used it some years ago for something or another.
Only use windoze for phone PSTs anymore... can't help you much.
plzzz help meee
guys i have micromax a115 canvas 3d with me .and i changed my boot animation of google
and now my problem is that when i change my bootanimation to any other. it is first shows google and then the new animation ....
plzzz help anyone .
i think xda will help me :crying: :crying: :crying:
This DOES NOT work on the i9300/note 2 and never will, please stop asking about it.
Thanks to the work of invisiblek and some Google searching I was able to come up with the following tool:
This tool takes a 720x1280 .PNG image and converts it to a recovery-flashable splash screen in a single click.
A video so you can see what this changes: http://youtu.be/XXaBJTVQ2Sw
How to use:
Making your own splash screen:
0) Download and extract the .zip file
1) Make a 720x1280 .png image you want to be your splash screen (this comes in-between the boot animation and the quick Samsung logo flash)
2) Name it "initlogo.png" without the quotes
3) Place it in the PNGtoConvert folder
4) Run the "PNG-2-RLE.bat" file
5) You are finished! A "flashthisinrecovery.zip" will appear in the same directory as the batch files. Just flash it in recovery and enjoy your new splash screen!
Note: If you want the .RLE and not the whole flashable, it can be found as "initlogo.rle" in the "kernel" folder or you can pull it from the kernel folder inside the "flashmeinrecovery.zip"
Converting an .RLE that you made back to a .PNG for editing:
0) Download an extract the .zip file
1) Copy the "initlogo.rle" you want to convert to a .PNG to the RLEtoConvert folder. It must be named "initlogo.rle"
2) Run the "RLE-2-PNG.bat"
3) PNG will be in the PNGtoConvert folder named "initlogoOUTPUT.png"
Other notes:
I have included the stock initlogo as a .PNG named "initlogoSTOCKBACKUP.png" for your reference/backup purposes. If you want to test the tool with it, remember to rename it to initlogo.png
If you flash a new kernel/rom the splash will revert to stock. To get it back, just flash the "flashmeinrecovery.zip" again. You don't need to reconvert it or anything.
This has only been tested with the d2_vzw but will work with all USA (S4 CPU) variants!
Credits:
invisiblek for the recovery zip scripting
Yagya Gaire @ http://yagyagaire.blogspot.com for the original conversion tools
Download Here: http://d-h.st/F2A
As always, even though this tool has been tested, nobody is responsible to damage to your phone except yourself!
Linux version coming?
wera750 said:
Linux version coming?
Click to expand...
Click to collapse
No... there are too many windows binaries lol.
Sounds interesting, I just downloaded it and will play around with this tonight. I don't know why I never thought about personalizing my phone by just changing out my splash image with one of my own, but this sounds cool and will give me something to play around with tonight at work. Thanks, I will let you know how it works out for me. I appreciate your efforts and willingness to share your work.
jlangleyrn said:
Sounds interesting, I just downloaded it and will play around with this tonight. I don't know why I never thought about personalizing my phone by just changing out my splash image with one of my own, but this sounds cool and will give me something to play around with tonight at work. Thanks, I will let you know how it works out for me. I appreciate your efforts and willingness to share your work.
Click to expand...
Click to collapse
I mean lets be honest it is really a minor thing and it shows for all of 5 seconds but it is still fun to change.
The Samsung thing is getting kind of old...just sayin.
Thanks Con
Sent from my SCH-I535 using Tapatalk 2
I think this is also good.
Works great, thanks man!
omgi0wn said:
Works great, thanks man!
Click to expand...
Click to collapse
Glad to hear it works. It is always nice to know when it works for someone else and my instructions are good
Sent from d2_vzw
I didn't even know I could have a custom splash screen with Samsung! Thanks Con
Sent from my SCH-I535 using xda app-developers app
Will this work with AOSP ROMs, or just TW?
Sent from my BAKED SIII
VikingoRMCF said:
Will this work with AOSP ROMs, or just TW?
Sent from my BAKED SIII
Click to expand...
Click to collapse
Both
Didn't work
Sent from my BAKED SIII
Note: the image I used wasn't 720x1280, does it have to be?
Sent from my BAKED SIII
This is pretty cool. we were doing this with the thunderbolt and i changed my all the time to the flavor of the moment.
thanks for getting this done...it is not necessary, but it sure is cool...
VikingoRMCF said:
Note: the image I used wasn't 720x1280, does it have to be?
Sent from my BAKED SIII
Click to expand...
Click to collapse
It must be 720x1280. If you don't follow the directions (read Step #1) you shouldn't expect it to work!
i thanked you in the other post so i'll do it here too. thanks!
I love changing my splash screens and boot animations. when I came over from a long line of Evos everyone was looking at my like if I was crazy when I was wondering why we couldn't change our splash.
anyways, have you looked into changing the Samsung splash that comes before? I would like to replace both so that the image I created shows longer. don't need that Samsung logo flashing around
Max_Pain said:
i thanked you in the other post so i'll do it here too. thanks!
I love changing my splash screens and boot animations. when I came over from a long line of Evos everyone was looking at my like if I was crazy when I was wondering why we couldn't change our splash.
anyways, have you looked into changing the Samsung splash that comes before? I would like to replace both so that the image I created shows longer. don't need that Samsung logo flashing around
Click to expand...
Click to collapse
I don't think we can because it is a part of the bootloader which is signed so we can't modify it. On the gnex the app logome can change it but we can't due to the security. I am not sure if the other carrier models are signed but for Verizon I am pretty sure it's impossible.
Sent from d2_vzw
Worked great. Here is my (extremely dumb) first splash haha.
Here is mine! We should make a thread with all of these btw. Maybe I'll go over to the theme section in a little bit and make one.
So i've tried to use the bootbox app to change my boot animation, i've used itvon my old phones bu t this is 1st Samsung, what's the proper way to change it?
I'm also interested in this.
You might want to read this thread my friends ...
http://forum.xda-developers.com/showthread.php?t=2073775
So yea, the reason I rooted my phone in the first place was to hopefully be shed of that obnoxious boot animation, but it seems our phones are "unique". I've done the bootanimation.zip replacement and permissions, I've done the individual files (my media directory has both, as well as one in the bin). And I STILL get the obnoxious virgin mobile animation. I followed the link above.. and uh..whaaaaa??
I'd like to hear from anyone that has successfully changed their boot up animation to something cool on their SM-J700P.
Would going to a custom ROM work? I have hesitated since I have marshmellow at present.
I have boot animation support. Depending on the response I get back I might write a "how to" thread. Plus I have a BUNCH of boot animations. I can post the directions and Samsungani files needed.. right now my phone boots up like PlayStation
timmetal6669 said:
I have boot animation support. Depending on the response I get back I might write a "how to" thread. Plus I have a BUNCH of boot animations. I can post the directions and Samsungani files needed.. right now my phone boots up like PlayStation
Click to expand...
Click to collapse
Awesome. I have one that I like, the zip containing the three qmg files. I've replaced the files manually and followed step by step on YouTube, so I hope you have what I'm missing.
timmetal6669 said:
I have boot animation support. Depending on the response I get back I might write a "how to" thread. Plus I have a BUNCH of boot animations. I can post the directions and Samsungani files needed.. right now my phone boots up like PlayStation
Click to expand...
Click to collapse
Do you have the Android default boot animation system working, or just support for the qmg system?
Got it working. Look up bootanimation4U... Flash it. If you can't find it lemme know and I'll post it
Then, manually change out your boot animations or make a flashbable zip
Help here
I accidentally deleted bootanimation.qmg file in my Galaxy j7 and after that the samsung boot up screen is not showing... I tried flashing and manual methods to fix it but nothing seems to help.
Devs please provide different boot animation flashable zips..
Thanks in advance
Read this guys
https://forum.xda-developers.com/showthread.php?t=2063280
Hello I'm building my first rom(grapheneos & cynogenmod) from source code using ubuntu 16. I've followed few tutorials from this forum an so far its been a positive experience for me. I want to know two things:
1. How to change the boot screen animation logo, or is it even possible to do so from source while building?
2. How to change features to make cynogenmod into "secure boot or verified boot feature"?
Can anyone help me please or point me in the right direction. I've search everywhere but cant find a proper answer. they always say like do it afterwards from app or get root access and all. All I wanna know is there a proper way to do it via commands while I'm building the ROM?
the boot animation is basically a gif inside a zip file and the splash is just a png. when i was changing my boot animations on my old S3 and Evo, it was merely a matter of renaming the existing png and zip files to something else and put the ones you want in their place. I think theyre telling you to do it afterwards because the bootloader is suuuuuuper picky about the size of the png's and the images inside the zip in height/width, file size itself and the DPI. Maybe theyre less picky these days, but those were the 3 main issues building boot animations in the past. While building the ROM, do you not have to get the media from whatever mfg youre building it for anyways? I honestly have no idea, not being a smart ass at all. if thats the case, then just get the stock one and replicate those values on the files you want to use and inject them into your ROM