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
Related
Is there anyway to change the second boot screen?
http://forum.xda-developers.com/showpost.php?p=3133153&postcount=91
prolly not talking about splash2, but the Android animation and logo after splash1 & splash2. But i could be wrong.
Theres a folder in framework-res.apk/assets/images that seems to contain the images used in the second boot screen. I haven't had a chance to play with it to see if anything happened. I guess I'll try now and get back to you in 10 minutes. =]
ok so far, I was able to change the second boot screen image without using fastboot, and just modifying the android_320x480.png itself in framework-res/assets/images, but the animation goes out of whack when trying to replace boot_robot.png and boot_robot_glow.png with other images. I'm going to keep at it to see if i can get anywhere.
Hi, i edited the boot_robot_glow.png in PS and it shows up fine when booting
EDIT: I've edited the android_320x480.png but when it boots it shows the original then flicks to the modified one
EDIT: needed to replace boot_robot.png in res/drawable aswell!
Attached images aren'y quite aligned, moves about when booting :S
EDIT: Everything's aligned now
ximonx said:
Hi, i edited the boot_robot_glow.png in PS and it shows up fine when booting
EDIT: I've edited the android_320x480.png but when it boots it shows the original then flicks to the modified one
EDIT: needed to replace boot_robot.png in res/drawable aswell!
Attached images aren'y quite aligned, moves about when booting :S
EDIT: Everything's aligned now
Click to expand...
Click to collapse
would you mind telling us how to replace the files?
adb pull /system/framework/framework-res.apk to your computer,
rename it to framework-res.apk.zip
open framework-res.apk.zip
copy all 3 files into /assets/images
copy boot_robot.png into /res/drawable (in assets/images aswell)
(Uploaded my new boot_robot_glow to use with above files)
ximonx said:
adb pull /system/framework/framework-res.apk to your computer,
rename it to framework-res.apk.zip
open framework-res.apk.zip
copy all 3 files into /assets/images
copy boot_robot.png into /res/drawable (in assets/images aswell)
(Uploaded my new boot_robot_glow to use with above files)
Click to expand...
Click to collapse
Cool... Thanks guys!
Used your images and created a burning Droid for the boot up image.
Adapted the code slightly to run the commands on the phone itself then copied the zip file off the SD card through usb.
Thanks
any pitfalls?
does the image have to be a certain size before 'push' ing it back to the phone?
I like your design so Ill start there, thanks for sharing the work, people have been speculation on how to change this and you did it.
bhang
I'd play it safe and keep everything the size it is, although if you have the dev BL then go for it. It will probably start from the same location on the screen but extend further across and down
This will surround the that icon better than the round glow i made this just now. Looks better just change the hue and make it red if you like.
I can confirm that this work fine on RC30 and ADP1 (there is no reason why it shouldn't but I bet someone will ask...).
So i went ahead and tried to modify the images that make up the animation, got it all repackaged, and pushed it onto the phone. I rebooted and my animation came up like a charm, looking pretty cool, but it got stuck there and the animation kept running. I tried rebooting it several times and then restored it using a backup which fixed it. I am still trying to figure out what i did wrong. Could someone take a look?
Let me preface this statement with the chance that I may have put this in the wrong thread entirely and if the powers to be deem it to be moved, so be it and I apologize for posting improperly.
Ok, that out of the way, I have an issue! I have taken my time to go through and create a "fade in" effect with a logo that I would like to replace my boot animation with. First and foremost, here are my specs:
Rooted nexus one
Locked bootloaded
Stock ROM, FRF91 2.2
I've examined the stock animation and the custom animations that came included with the boot animation changer app. I have no idea what I am doing wrong but I am sure it has to do something with the desc.txt file. If anyone would be so kind as to modify the attached files (probably just the desc.txt), it would be appreciated. Better yet, explain what I am doing wrong and I will do it myself. Attached is bootanimation.zip with a compression type of *store*, including ~100 .png files.
Much thanks
Bump, ~50 views and no reply.
Bump. ~100 views..
Mods / Admins
Please close.
I haven't read your .txt file because I'm at work, but did you compress the .zip? And make sure you're not using transparent images. I heard it causes problems.
Did you try zipping up just the contents? When I unzip the file, it looks like -
/bootanimation/bootanimation/part0/
/bootanimation/bootanimation/desc.txt
Looking at a known, working bootanimation, it looks like this -
/bootanimation/folders
/bootanimation/desc.txt
This is a common problem when devs first start out. I've done it myself when signing a new ROM and trying to flash it.
Not too sure what was wrong other than maybe the "false" line breaks in notepad or something.
Opened a shell in cygwin, nano'd the txt file and made my changes. Wrote it, and dos2unix'd it. Proceeded with a "zip -r -0 part*/*.png desc.txt" and everything is working. Although after I figured it out, I appreciate your responses.
its not working for me D:
It's not much, but I thought everyone should be able to theme their Framework
Requirements: WinZip(or any other zipping program), Android SDK, testsign, some graphics editor...
NOTE: This will work with theme apk's as well !!!
So what you need to start with is your framework files:
framework-res.apk, com.htc.resources.apk ... both are located in SYSTEM:framework/
These files are just renamed zip files, so rename them back to .zip and extract them (you can also edit them inside WINRAR or something, but it is more comfortable if you extract them)
In these, images are usually saved in res/drawable-mdpi or such, but you have to think here, allways modify all files from one resource
Now locate the images you want to edit but I only know how to edit .png files (.9.png files are for a different howto, probably not by me as I've never really mastered it)
Pick those you want to edit, and edit them (I'm not gonna tell you how here, I usually use photoshop to do that )
Once you have edited those images, it is recomended to optimize those png's (Firstly to make them smaller, but more importantly, most of the times the png's from Windows graphics editor didn't work for me...)
To optimize png's you can use:
OptiPNG: DOWNLOAD This one is drag'n'drop batch conversion capable...
Pngcrush: DOWNLOAD Command line utility, but it has more settings
...or something else, but I find these two the best
Once you have these optimized, copy and re-write them to folders you took them from to edit...
Now you need to zip these back, for framework files I was told it is usual to zip them as "store", but correct me someone if I'm wrong.
After you have zipped those, they will have to be re-signed. To do this, use testsign from code.google.com
Then run this in cmd line (or create a .bat file as I did, it's much easier):
Code:
java -classpath testsign.jar testsign [COLOR="DarkRed"]file.zip[/COLOR] [COLOR="DarkRed"]file-signed.zip[/COLOR]
Now that you have signed it, it is recomended to zipalign it:
(zipalign.exe is located in /tools in your SDK)
Run this in cmd line:
Code:
zipalign 4 [COLOR="DarkRed"]infile.zip[/COLOR] [COLOR="DarkRed"]outfile.zip[/COLOR]
(4 is alignment in bytes)
Now that you have aligned the .zip, rename it to the original name and then you just need to push it back to your phone:
Code:
adb shell mount /system
adb push [COLOR="DarkRed"]com.htc.resources.apk[/COLOR] /system/framework/[COLOR="DarkRed"]com.htc.resources.apk[/COLOR]
or
adb push [COLOR="DarkRed"]framework-res.apk[/COLOR] /system/framework/[COLOR="DarkRed"]framework-res.apk[/COLOR]
And you're done
I hope this helps someone! Enjoy!
note: This way you should be able to modify any apk I think
Very good.
Good initiative, thank you.
Lets hope that others will follow your example and contribute in this community,we need it.
Sent from my HTC Desire S using XDA Premium App
One question... can i change the framework if i'm s-on? And if yes how? flash it through recovery or how?
LE: Thx for the info. I found out how to edit themes... i will create a cool one to upload here. I could edit the framework.....but i am s-on so no use for that.
Unfortunately, when you're unrooted, you can't push files to your system...
But this will work for those Theme apk's too... so grab a theme you like and you can edit it as easily as you would your framework It has a limited potential, but it's something for you S-ON users
Hmm, I skipped the push part and copied the file back over the one in the phone. Now my phone is stuck in a continuous loop on the "quietly brilliant" screen.
Any help? Where do I get a stock rom to flash?
rogbese said:
Hmm, I skipped the push part and copied the file back over the one in the phone. Now my phone is stuck in a continuous loop on the "quietly brilliant" screen.
Any help? Where do I get a stock rom to flash?
Click to expand...
Click to collapse
Just enter recovery & factory reset,wipe, then wipe dev cache, then reflash your rom that you were using before the bootloop.
You can even swap icons in the framework of your rom then just flash (if you try to swap framework.apks or dialer.apks using a file manager you will delete or swap the file but this will cause loads or errors & force closes & then result in your bootloop!) Then just swap via a computer within the zip file then just flash in recovery as normal & if done right you wont get bootloops
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:
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