Make your spica "look" more i5800 stock by matching your touchwiz launcher with the i5800 shutdown screen converted as a boot animation for the spica. Two recovery update zip files are included in the package (SDM_i5800boot-package):
SDM_i5800bootanimation is a recovery zip file containing the modified boot animation.
SDM_i5800bootlogo contains the stock boot logo of the i5800 to make the boot process look more seamless from logo to animation.
Apply both or any of the zips under recovery.
Preview: i5800 boot animation mod
WARNING: see all warnings about flashing boot logos. Applicable with samdroidmod, other systems have not been tested at all.
BIG FAT WARNING IN USE WITH SAMDROID KITCHEN V2
With release of Samdroid Kitchen V2, be warned that the attached files include the old Superuser.apk from kitchen v1, and the update zip themselves are for ktichenv1 format. So don't flash directly to kitchen v2. Use them in the newer kitchenv2 format, and delete the older Superuse.apk.
WARNING ENDS
Download:
Code:
[URL="http://www.megaupload.com/?d=M8BCEJFM"]Mirror 1 (3.84MB)[/URL]
thanks a lot man.
Related
15 Android Boot Animations with Aroma Installer.
»»»»» All-in-one bootanimation installer with aroma installer support. «««««
Click to expand...
Click to collapse
Things you will need:
1. A rooted phone.
2. Custom Recovery (TWRP, CWM)
Note: If you are on Cyanogen Mod rom or any theme related rom, just change your bootanimation to systems one.
If you are using cm rom change your boot animation to android pack.
Click to expand...
Click to collapse
How to use:
1. Boot to recovery (TWRP OR CWM)
2. Select Install.
3. Choose IND_TechNitiUm Boot Animation Pack.
4. The Aroma Installer will start, so just choose the preferred boot animation and hit next.
5. Your Bootanimation will be installled.
6. ENJOY
Well these boot animation are tested and they are awesome but i dont hold any guarantee for them to work on your device. And i am not responible for Bricked phones. Also my phone is a Lenovo A536 with a 5 inch screen so they work perfectly on it , but they may not be scaled on your device.
Click to expand...
Click to collapse
DOWNLOADS:
IND_TechNitiUm Boot Animation Pack
It seems to be quite problematic to implant compression formats into SuperSU systemless install other than gzip.
Here is a method i used for lz4 compression on my lg k8 (mt6753) http://www.chinaphonearena.com/forum/Thread-root-lg-k8 and https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807.
I guess it must work on other devices and also with other compression methods.
1. Unlock your bootloader
2. Boot to TWRP
3. Backup your boot image
4. Tweak your boot image with Carliv Image Kitchen (http://forum.xda-developers.com/and...-cika-carliv-image-kitchen-android-t3013658):
-Unpack it, open "boot.img-ramdisk-compress" file with a text editor (notepad++) and change the first (and only) line from "lz4" (or whatever you have here) to "gz"
-Repack image
5. Flash the tweaked boot image in TWRP - from now on you must not leave TWRP but use a microsd card to put files from phone to PC and back. You have to stay in TWRP until last step otherwise you might get bricked...!
6. Install SuperSU - do not restart or boot up your phone!
7. Backup boot image again
8. Tweak boot image in Carliv
-Unpack it, open "boot.img-ramdisk-compress" file and change the first line from "gz" to "lz4" (or whatever you had there)
-Repack image
9. Flash boot image in TWRP
10. Restart (this will take a bit longer and also expect bootloop a few times)
Before you proceed you have to check if your boot partition has enough space to accept a bit bigger boot image than the stock one.
In my case the boot partition is 16Mb and my boot image is only 12Mb so after the patching it's still safe to flash it. (After you backed up the boot image try unpack and repack first to see its reel size - sometimes backup takes the whole partition not only the boot.img)
Lz4 is about 1Mb bigger (in my case) than gzip, however other compression methods might differ...
No promises... and no responsibility i take...
Working devices so far:
LG K8 k350n
LG K10 k430Y
The whole story got developed a bit farther by now:
https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327
Why can you upload the two boot.imgs
rickwyatt said:
Why can you upload the two boot.imgs
Click to expand...
Click to collapse
What do you mean?
How do you install twrp on the lg k8?
ahmdaini said:
How do you install twrp on the lg k8?
Click to expand...
Click to collapse
You cant install it but you can boot into it. Read the related threads in the k8 and the k10 sections regarding the 2016 models. However there is no twrp for the 2017 models yet.
I was having major issues with my system going into a perpetual boot screen, which I isolated to be caused by the modified boot image I was flashing from here: https://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
I simply performed the following:
Extracted the n4f26j factory image and isolated the boot.img file
Used Android Image Kitchen to unpack it
Navigated to the new ramdisk folder in the Android Image Kitchen directory
Modified the fstab.angler file slightly to remove the ",verify" bit from two strings
Saved the fstab.angler file
Repacked the boot.img using the script from Android Image Kitchen
adb reboot bootloader
fastboot flash boot angler-n4f26j-modifiedboot-20170228.img
fastboot flash recovery twrp-3.0.3-0-angler.img
Rebooted to recovery
Flashed SuperSU
Wiped cache & Dalvik
Rebooted the phone
Great success
I'm a happy camper, and wanted to share this with anyone who may be in a similar boat. I've also attached the modified boot.img for anyone who may want to save a little sweat. I make no claims that this will not cause problems for you, but it worked beautifully on my phone. I hope this helps someone!
Edited to Add: I just updated my phone to n4f26o and performed the same process outlined above. The n4f26o file is now attached for convenience.
As you may know, it's the time of the year when new phones get released and everyone is eager to grab the new boot animation!
Following this post is the Boot Animation grabbed directly from the system dump of the Google Pixel 2.
I will post the boot animation of the Pixel 2 XL at a later date.
Warning: I am not liable for any damage caused by the content in this forum. You agree to use my content at your own risk!
Instructions:
1. Download the file :
HTML:
https://goo.gl/KQ9ei7
2. Open your preferred Root Browser (ES, FX etc.) and give it root access. Then, navigate to system/media/.
3. Copy and paste the new boot animation exactly the way you download it into this folder (Change the permissions to rw-r-r).
4. Last but not least, rename the old boot animation to "bootanimation.zip.b" to retain the old boot animation if you want to go back.
5. Finally, reboot your phone and Voila! You have successfully changed the boot animation.
Note: This has been tested on a Nexus 5X.
Comment below for any questions!
The resolution of the animation is 1080x1920
Here simple Windows tool (x64 only) to unpack existing or create your own logo.img
Based on Python script by penn5, I only created "wrapper" for comfortable using.
Guide, all simple:
1. Unpack attached archive
2. Edit images logo-*.bmp, keep 24bit color
3. Run "2 Repack.bat"
4. In folder appear done.zip, flash it via recovery
To edit existing logos replace logo.img in folder, run "1 Unpack.bat" and process as above.
Most likely app will work with other modern Xiaomi models.
If you want to try – use your own logo.img, because screen resolution may be different.
File can be copied from fastboot / recovery stock ROM or firmware.
UPD: fixed, file was not created if 7-Zip not installed.
I would like to bring to your attention that this post is currently marked as a question.
While running 2 repack.bat, it ends with error "Can't load module: 7z.dll"
HUe1998 said:
While running 2 repack.bat, it ends with error "Can't load module: 7z.dll"
Click to expand...
Click to collapse
Sorry for long answer.
Oops, my fault, file was not created if 7-Zip not installed.
Re-download ZIP, this problem fixed.