I've got my Optimus T flashed with the void ROM now and I'm loving it. I've been playing around now with the boot animation and I notice that now there is an animated version of the LG logo that comes after the static logo and before the bootanimation.zip. I've got the bootanimation.zip figured out, but I'd prefer to go straight from the static LG logo to the beautifully simple "void."
Does anyone know where this animated logo is located and how it can be changed or removed? Thanks in advance.
Answering my own question.
The images are in /bootimages named opening_0[1-8].rle. These are rle encoded raw RGB files. See to565.c in the android git tree for some details on that RLE format.
Trying now to see if getting rid of those files gets rid of the boot animation...
Looks like these files are written anew every time from the boot.img. I have found how to unpack the boot image from /dev/mtd/mtd0, but I'm working right now on how to make a new one...
the boot images are in ramdisk you need to unpack boot.img modify ramdisk and repack boot.img
the command to unpack on linux is "./unpack-bootimg.pl boot.img" you need perl libraries installed
Yep, I can unpack the boot image and change the images but once I repack it, how can I flash it to the appropriate place?
take commands what you need from an update-script of a custom rom and flash it trough recovery
Any updates on this? I would also like to know an easy way to remove this animation.
irondevil said:
take commands what you need from an update-script of a custom rom and flash it trough recovery
Click to expand...
Click to collapse
This sounds like the easy answer. Anyone with more knowledge willing to do this for me? I guess we're just talking about a zip to flash to remove boot/shutdown animations and nothing else.
Related
I need to have a Ramdisk with modified init.rc to support BT. I found this url about how to extract Ramdisk from system, modify files within it and repack it
http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
I did exactly the same step there, generate a new ramdisk with modified init.rc, repack it to be new boot.img, go to fastboot mode and use
fastboot boot new-boot.img
The the screen keep staying on displaying "Android" and never go further.
Then, I find a third party ROM which is MoDaCo ROM, use my new-boot.img to replace the original boot.img, then execute this update.zip in fastboot mode, other steps are exactly the same as instructions. But I got this error:
verification failed
Seems like the original boot.img has related signature or whatever which my newly generated boot.img doesn't have.
Anyone met this problem or know the solution? Thanks a lot.
I think it has to do with signing the update.zip so the recovery rom can flash it right. I'm guessing when you put your boot.img into the update.zip it phases out the signature that modaco applied.
http://forum.xda-developers.com/showthread.php?t=551711
Try that thread, it should help you out.
HI robertosandros:
Thanks a lot! I just saw your reply yesterday and have done with it. Your information helps a lot!
lk_517 said:
HI robertosandros:
Thanks a lot! I just saw your reply yesterday and have done with it. Your information helps a lot!
Click to expand...
Click to collapse
this will help you too! http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I am working on a custom boot.img for hero so we can have cyanogen Donut builds on our hero's hopefully I get a boot.img that boots here soon!
will keep you all updated!
If you manage that, you wouldn't believe how happy that would make me xD
First , i want to completely debrand my phone ..i.e. remove boot-animation as well as that LG logo (which i think comes from /boot partition and can we change that??)
Second, is it possible to have Debian-like kernel log(bootlog) displayed when the phone boots up ??? Is there a workaround for that???
yes you can change bootanimation but you need to extract boot.img and modify ramdisk then repack boot.img
irondevil said:
yes you can change bootanimation but you need to extract boot.img and modify ramdisk then repack boot.img
Click to expand...
Click to collapse
He doesn't want to change the bootanimation, he wants to remove it and have android to boot in "verbose" mode instead, like linux does. To my knowledge, nobody has been able to do it yet.
rotorto said:
He doesn't want to change the bootanimation, he wants to remove it and have android to boot in "verbose" mode instead, like linux does. To my knowledge, nobody has been able to do it yet.
Click to expand...
Click to collapse
To boot in Verbose Mode is needed to enter into the Bootloader. It Lg Optimus One how, we, can enter into bootloader? Maybe it is blocked, as Nexus ONE?
the_best_hacker said:
To boot in Verbose Mode is needed to enter into the Bootloader. It Lg Optimus One how, we, can enter into bootloader? Maybe it is blocked, as Nexus ONE?
Click to expand...
Click to collapse
There is no need to get into bootloader mode: what you need is to compile a new kernel with fbcon enabled.
If anyone is interested, here is explained how to enable verbose booting on the Galaxy S. Adapting those instructions for the LGP500 shouldn't be difficult.
rotorto said:
There is no need to get into bootloader mode: what you need is to compile a new kernel with fbcon enabled.
If anyone is interested, here is explained how to enable verbose booting on the Galaxy S. Adapting those instructions for the LGP500 shouldn't be difficult.
Click to expand...
Click to collapse
thnx..but how do i go about editing the .config of the mik_os's kernel that i m using......Will just editing the .config of the present kernel without the need to recompile it and zip it???
You have to edit the config file, recompile the kernel and flash it on your phone.
Hi.
I need the Boot animation for an avatar i'm making.
I haven't been able to find it.
My first try was to extract it from the Nexus 5 image, but i can't seem to read the system.img filesystem.
Can anyone help?
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for ZTE Axon 7 Only..
(For Axon 7 Mini or other devices, send me your splash.img so that I can see if this tool can work in your devices)
Requirements:
1. Rooted ZTE Axon 7 (any ROM)
2. Terminal Emulator app
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Make sure you have a 1440x2560 picture in PNG format.
(If it's not exactly 1440x2560, there might arise problems with fastboot mode. So double check the resolution)
2. Download & Extract this: Axon7_Splash_Maker.zip
3. Now rename your picture as logo.png & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder.
STEPS to flash splash.img:
0. First, backup your original stock splash.img by the command:
Code:
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash_backup.img
(And transfer to computer, might be needed in future)
1. Transfer the splash.img that you created to your device's Internal Storage.
2. Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
(You can also flash from fastboot as given below)
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from fastboot like:
Code:
fastboot flash splash splash.img
This is created based on A2017G's firmware, but should work with all variants..
Please report if any issues..
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
This is awesome , i was wondering about this when I came across that particular image file.
is this static only? or can be animated? (At least 15 frames hehehe).
DrakenFX said:
This is awesome , i was wondering about this when I came across that particular image file.
is this static only? or can be animated? (At least 15 frames hehehe).
Click to expand...
Click to collapse
Lol, just one image..
The one that can be animated and have multiple framee is known as "bootanimation"
Just kidding
GokulNC said:
Lol, just one image..
The one that can be animated and have multiple framee is known as "bootanimation"
Click to expand...
Click to collapse
Yeah, i know i have my own collection...for some reason i thought splash screens can be animated too.
This are my animations for Axon 7 and working in few more.
http://forum.xda-developers.com/axon-7/themes/bootanimation-t3442646
Zte axon Bootlogo
flash in TWRP
Unlock Bootloader and custom rom
Here's mine.
Flashable zip.
Picture found in the official ZTE forum.
Thanx for your information :good:
hi I would like to know if this procedure can be applied to a ZTE axon mini
Thank you so much for this. Made my own
https://ibb.co/kQAfvV
Made a basic AOKP one. Thanks for the guide GokulNC!
the splash.img does not work on A2017G Oreo B02. On Nougat no problems. gives a chance to change this?
I unpacked my boot.img file and changed something, but after I repacked it my phone goes straight into a bootloop/soft brick.
Even without changes to the boot.img (only unpacking and repacking) my phone still wont boot up.
It doesnt matter which ROM/boot.img I use or which tool I use for unpacking/repacking.
My phone is A5 2017 with Stock ROM.
Is someone of you having an idea of how to fix this?
simon151102 said:
I unpacked my boot.img file and changed something, but after I repacked it my phone goes straight into a bootloop/soft brick.
Even without changes to the boot.img (only unpacking and repacking) my phone still wont boot up.
It doesnt matter which ROM/boot.img I use or which tool I use for unpacking/repacking.
My phone is A5 2017 with Stock ROM.
Is someone of you having an idea of how to fix this?
Click to expand...
Click to collapse
Flash stock boot.img that is taken from firmware...
Unpacking and repacking may tamper the hash and remove signature..
Ask here https://forum.xda-developers.com/t/...kernel-ramdisk-win-android-linux-mac.2073775/ with a copy of your boot.img, so that someone can answer you.