Is it easy or possible to change the boot animation?
Yes magisk module called ressurection remix oreo
yes you must be rooted, easiest way is to do it via magisk module
here is mine as a template
theOneOSboot
it is already resized for OP7Pro
you can get the file from the zip go to system/media and u will see bootanimation.zip
extract that file and u will see tons of images you can create your own.
when done make sure to re-zip it and it has to be re-compressed as store (no compression)
then move the file back to system/media and you can change info on module.prop to what ever u want to name it.
Move to phone and install module through Magisk
Bradl79 said:
yes you must be rooted, easiest way is to do it via magisk module
here is mine as a template
theOneOSboot
it is already resized for OP7Pro
you can get the file from the zip go to system/media and u will see bootanimation.zip
extract that file and u will see tons of images you can create your own.
when done make sure to re-zip it and it has to be re-compressed as store (no compression)
then move the file back to system/media and you can change info on module.prop to what ever u want to name it.
Move to phone and install module through Magisk
Click to expand...
Click to collapse
I love this one without changing it.
Related
Can I modify an existing one by simply dropping in updated bootscreen files, rosie.apk, etc.. and signing the existing rom zip?
Any good guides on how to do one if not, and/or how to use Flipz kitchen tool to create a rom?
Ceger
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Kcarpenter said:
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Click to expand...
Click to collapse
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Ceger said:
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Click to expand...
Click to collapse
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
wtphoto said:
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
Click to expand...
Click to collapse
Oh well, was trying to have a one step zip. I guess I can make at least have a 2 step process which is better than 4-5.
Thanks,
Ceger
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
zippy-man said:
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
Click to expand...
Click to collapse
Perfect, just what I was looking for.
Thank you, just made my day!
Ceger
I have been trying to follow dubsx guide for installing his awesome custom boot animations but the PB31IMG.zip file keeps coming up with wrong image during HBOOT.
iowabowtech suggested a different method that works.
Using Root Explorer, make a backup file on your sdcard. Go to system/customize/resource and move the VZW_Bootanimation.zip and the VZW_Droid.mp3 to the backup folder (just so you can return it to the stock boot animation if you want)
Go to the custom boot animation zip you want and move it to system/customize/resource You can also use a custom mp3 file (up to 30-40 seconds long I believe) and place it in the resource file too.
Long press your animation file and rename it to VZW_Bootanimation.zip If you are changing the mp3 file rename it to VZW_Droid.mp3
It worked for me running the rooted Inc_Gingerbread_Official.zip found here on XDA.
Please correct me if I am wrong somewhere with this method.
I never install boot animations thru hboot. You sure he's not talking about installing splash screens because that's how you install those. I just rename the animation and throw them into the folder containing the old bootanimation.zip. So yes, that's the method I use, and yes it works, and what you have written is correct.
Hey, I'd like to know how to change the bootanimation in Kyrillo's ROM as ive already tried BootAni and some other apps and even tried manually changing the Bootanimation in "data" and "system/media"...didnt work.... it'd be great if i could get some help and if possible in a step by step manner...
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
ak700 said:
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
Click to expand...
Click to collapse
I did ..
On an extra note:
If you want to avoid having white flashes in your bootanimations on any rom with openFIMG you should look for one with less than 75 frames in the part1 folder. Any frames past that turn white...
Tried didnt work!!....
Ava.tar said:
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
Click to expand...
Click to collapse
i tried it .... didnt work .... idk why.... just to change the bootanimation i bymistake flashed a motorola Xoom bootanimation please help...plzplzplzplz.... im stuck here with nothing but "A)" out of the whole bootanimation plz help im tired of trying to change my bootanimation!!!!!
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
here is log cat along with used vrtheme script.
dr.ketan said:
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
Click to expand...
Click to collapse
doc, am not a linux expert, but i tried to inject your black aosp vrtheme files into the apk and flash them from cwm, it kills the wifi and have to wipe and reflash the whole rom. so, perhaps you want to put more attention to it.
waiting for your aosp theme and thanks a lot.
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
dr.ketan said:
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
Click to expand...
Click to collapse
sorry doc, but i cannot understand what you mean.
do you mean i should change the flashing path (in the script)? or do you mean i should copy the apks manually into the system/app by root explorer? if you mean the later, i can do, but the first one i don't.
i can see all the icons, just the wifi would not start after i flashed the modified apks through cwm flash. what do you mean by reflashing recovery?
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
dr.ketan said:
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
Click to expand...
Click to collapse
will just wait for your file then. dont want to mess my setup again. spent too much time experimenting with it today. lucky it's saturday in my country...
ok then wait 10 min.
EDIT : AOSP theme for MJ2 ROM Posted to MJ2 thread post#2
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
wesamothman said:
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
Click to expand...
Click to collapse
Already fixed that (at least in my MJ2 rom)
vrtheme works perfect on framework-res.apk and secsettings.apk
Hi,
I have tried all methods mentioned here to change the boot animation but it did not work , please help
Hi there and welcome to Assist,
Your device must be rooted for this change. Try this:
You will need a file manager app with Root access. Use Root Browser app or any other file manager.
Download a custom boot animation you want to use by choosing the animation you want to use and downloading the associated bootanimation.zip file.
Open Root Browser (or your file manager) app and once inside, locate your original boot animation file (bootanimation.zip) in /system/media.
Long-press the file, choose Rename and name it to bootanimation.zip1.
Browse to the custom boot animation that you want to switch to, copy the zip file to /system/media. Long-press, choose Permission.
Tick the boxes as shown in the screenshot below, and press OK. After that, rename the file to bootanimation.zip, if the zip file name is different.
You have to make sure that the file name is correct (bootanimation.zip) for the system to recognize your boot animation, and boot properly.
Now you should be able to see two zip files, one, bootanimation.zip (new file) and the other is bootanimation.zip1 (original).
Note: If you ever want to switch back to your original boot animation, delete the current bootanimation.zip and rename the original file back to bootanimation.zip (from bootanimation.zip1).
Reboot the device and you will be able to see your new custom boot animation!
You'll have to create an account to post in the main forums if you have any other questions.
Good luck