Develop Bugs

[Q] Boot Animation

Hey guys hopefully someone can help me with this issue. I odin'd tp the stock ext4 plus rom in the development forum which works fine however then i flashed genocide 1.0 rom over the top if that to get the OC/UV features and when i booted i got the word "android" in the middle of the sprint boot animation then i flash a custom boot animation now the sprint and custom boot animations are mixed together when booting any suggestions to get rid of sprint animation?

Whenever you have android flashing in the middle, that means you had a bad flash. Just pull the battery and reflash the ROM/kernel in CWM and you should be fine.

acer1096xxx said:
Whenever you have android flashing in the middle, that means you had a bad flash. Just pull the battery and reflash the ROM/kernel in CWM and you should be fine.
Click to expand...
Click to collapse
Not true when u have the android name flashing it means it supports custom boot animation. Best bet is to get root explore go into system/ media. Look for bootanimation.zip and delete it then flash the new one
Sent from my SPH-D700 using XDA Premium App

Estewa_619 said:
Not true when u have the android name flashing it means it supports custom boot animation. Best bet is to get root explore go into system/ media. Look for bootanimation.zip and delete it then flash the new one
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
No go brother any other ideas besides reflashing?

justinglock40 said:
No go brother any other ideas besides reflashing?
Click to expand...
Click to collapse
Try taking a bootanimation from a rom that u like and push it to system/media. For example download a rom extract it go into the system/media folder look for the bootanimation.zip copy that put it on ur sd card then with root explore take it and copy it to ur system/media then reboot see if that works
Sent from my SPH-D700 using XDA Premium App

Estewa_619 said:
Not true when u have the android name flashing it means it supports custom boot animation. Best bet is to get root explore go into system/ media. Look for bootanimation.zip and delete it then flash the new one
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Really?? Then I'm confused because the first time I flashed SRF it flashed the android name while trying to boot. Just re-flashing the ROM fixed it. I thought this was the same situation.

acer1096xxx said:
Really?? Then I'm confused because the first time I flashed SRF it flashed the android name while trying to boot. Just re-flashing the ROM fixed it. I thought this was the same situation.
Click to expand...
Click to collapse
Na it just means it custom bootanimation compatible
Sent from my SPH-D700 using XDA Premium App

just flash this stock boot animation cleaner which deletes the stock animation files so you dont have an overlap...
http://chris41g.users.foss-net.org/epic_stock_boot_cleaner.zip
then flash any bootanimation.zip you want, lots in the theme section.. here is the stock animation in bootanimation.aip form.. or as close as can be to the stock animation anyway...
http://forum.xda-developers.com/attachment.php?attachmentid=516330&stc=1&d=1297556826 (made by nubecoder)

Boot animation

Noob here looking for some help, I flashed a new boot animation in recovery which went fine with no problems. The problem I've got is I now can't change it to a different boot animation, I've tried
1 - flashing another boot zip in recovery. No luck
2 - tried rom toolbox pro to flash 1 of their boots. No luck
3 - I've tried doing it manually by deleting boot animation zip in system/media and replacing it with a new bootanimation.zip. no luck
Every time I reboot Im back to the 1 I'm trying to get rid off.
If anyone could help I'd appreciate it.
If I've posted this in the wrong place I'm sorry but go easy on a noob
sent from my Nokia 3210

Which rom do you have installed? Sometimes it is in a different location
Sent from my Inspire 4G using xda premium

I'm using absolution 3.7
If I reflash the rom will that put it back to the boot animation that comes with the rom?
sent from my Nokia 3310

There is a guide on this page/3rd post.
http://forum.xda-developers.com/showthread.php?t=1364835&page=152

ketanmatrix said:
YES!!
still a bit curious, what rom are u using?
Click to expand...
Click to collapse
Thanks. reflashed, problem solved
I'm using absolution 3.7 rom by The Collective (flappjaxxx)
sent from my Nokia 3310

Boot animation chamged after Installing CWM.

I just installed CWM through SFHub's Autoroot package, and my boot animation changed upon the automatic reboot to the animation that just says "Android". Is that normal, and is it something i should be worried about if its not normal?
Sent from my SPH-D710 using xda app-developers app

You're fine. As long as it booted, you're fine.
That's a fallback bootanimation when no other one is detected. The same thing would happen if you were using a kernel that used the qmg format over 'bootanimation' but you had a bootanimation zip in /system/media.

The only time you should be worried is when your boot animation is static
That almost never occurs on our phone so your good
Sent from my SPH-D710 using xda premium

Alright. Thanks.
If i wanted to change my boot animation how would I go about doing so? Is there a thread you can point me to?
Sent from my SPH-D710 using xda app-developers app

naryric Kant's
yup normal, same thing I got until I flashed Blu Kuban

Can't name any threads off the top of my head. Just search 'how to install bootanimation' With Samsung, the type will matter (qmg vs bootanimation) depending on the kernel. As far as I know, most custom kernels support bootanimation zips. just read the OP to check.
Now, most will have a CWM flashable package but if you find one in a ROM you want or it's not wrapped in a nice package:
It goes in /system/media and must be named 'bootanimation.zip' the permissions are rw-r-r (though I'm sure r-r-r works too).

[MOD] Google Wallet Fix for ODEXED ROMs

[THIS SHOULD WORK ON ALL VARIANTS (VERIZON AND ATT), HOWEVER ITS TESTED FOR SURE ON TMOBILE]--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WARNING: This Fix Only works for ODEXED MDB Build ROMS, MDL ROMS will boot loop.
INSTRUCTIONS.. (MUST BE ON A ODEXED MDB Build. stock MDB Build odexed roms will work with this fix!)
1. Mod build.prop file to sprints.. (Make sure you save the Build.prop file with the same file permissions that it originally had)
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
2. download the attachement below
3. REBOOT into recovery
4. FLASH the file, fix permissions
5. REBOOT
6. download the wallet app from the playstore..
7 download and install xposed framework installer
. http://db.tt/hEC5CNzz
8 download and install xposed wallet patch
http://db.tt/NutI92ic
9. Open xposed installer, in framework tab, click update then reboot
10 open xposed installer, under modules check the wallet patcher, reboot
PROFIT.. you can now change your build back to tmobile and wallet will stay working
-------------------------------------------------------------------------------
HUGE THANKS TO OGDOBBER, Xeonox,romracer, joemagistro and everyone who helped get this working!

I'm running M919UVUAMDL stock rooted. Followed instructions and ended up in a boot loop.

glensta said:
I'm running M919UVUAMDL stock rooted. Followed instructions and ended up in a boot loop.
Click to expand...
Click to collapse
Same.

glensta said:
I'm running M919UVUAMDL stock rooted. Followed instructions and ended up in a boot loop.
Click to expand...
Click to collapse
Is that an ODEXed ROM?
Sent from my SGH-M919 using xda premium

djgromit said:
Is that an ODEXed ROM?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Yes it is.
Edit: I am also running the Faux kernel, not sure if that makes a difference or not

I just wiped my phone and restored to stock, Downloaded the zip from this page just to make sure I'm testing the same file. Flashed the zip and had no problems.
It may be something to do with the Kernel your using.

Im on rooted stock mdl and it boot looped for me.
Sent from my SGH-M919 using XDA Premium HD app

sounds like a Build.prop issue if you dont save build.prop with the proper permissions.
Root explorer should set the permissions for you if you are editing the build.prop with root explorer. That would be the only reason I can see for a boot loop.

I did use root explorer. Ill try again.
Sent from my SGH-M919 using XDA Premium HD app

MikesTooLz said:
sounds like a Build.prop issue if you dont save build.prop with the proper permissions.
Root explorer should set the permissions for you if you are editing the build.prop with root explorer. That would be the only reason I can see for a boot loop.
Click to expand...
Click to collapse
Can you edit the build.prop after the fact and then have it work?
Here's where I think I went wrong:
1) I already had Wallet installed, but it would just tell me I had an invalid device (probably should have uninstalled it)
2) Like an idiot, I didn't do the build.prop steps first
3) Flashed the file in CWM and Fix Permissions (Stuck on 4G LTE screen)
4) In an effort to recover from this, flashed TWRP and reflashed zip and fixed permissions (no luck)
5) Pulled build.prop with adb, edited it, pushed it back and set perms to rw-r-r
6) Retried flash/fix perms with TWRP
Still no go...anyone have any thoughts on what I can do to recover without a reflash of a ROM?
Am I lost if I didn't do the build.prop first?
Thanks,
Jason

if u get stuck on set up screen!i i made sure the build prop said sprint and then i wiped the data of google wallet and cache, then i rebooted. Then after the reboot i turned on google wallet and now i have a fully functional google wallet!
I dont know if this will work for u, but this method did get me past the set up screen ....

movieaddict said:
if u get stuck on set up screen!i i made sure the build prop said sprint and then i wiped the data of google wallet and cache, then i rebooted. Then after the reboot i turned on google wallet and now i have a fully functional google wallet!
I dont know if this will work for u, but this method did get me past the set up screen ....
Click to expand...
Click to collapse
I appreciate the response. I ended up reflashing stock OTA, and after I root again, I'll give it another try.

I follow the instructions and ended up boot looping ... ended up having to wipe and reflash new rom to get back running. Was running stock rooted odexed rom with mdl base.
Sent from my SGH-M919 using xda app-developers app

dominante58 said:
I follow the instructions and ended up boot looping ... ended up having to wipe and reflash new rom to get back running. Was running stock rooted odexed rom with mdl base.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same here. Rooted on Stock Odexed MDL. Good thing I had made a backup prior though... Please fix when you can . More people than not are experiencing boot loops/soft bricks and having to reflash. Not a one-off case here. As always, keep doing your thing, DEVS!

rainynight88 said:
Same here. Rooted on Stock Odexed MDL. Good thing I had made a backup prior though... Please fix when you can . More people than not are experiencing boot loops/soft bricks and having to reflash. Not a one-off case here. As always, keep doing your thing, DEVS!
Click to expand...
Click to collapse
when is it bootlooping for you guys? at what step??
after editing build.prop
or
after flashing zip
or
after installing the exposed and/or module?

I don't know how people are boot looping? Weird! It's work exactly as it says it does.
Sent from my SGH-M919 using xda premium

Mine bootloops after fixing permissions.
Sent from my SGH-M919 using xda app-developers app

I renamed the build prop ( had write permissions set for the system folder). And then rebooted into recovery. Flashed the file and then restarted and thats where it bootlooped. And by bootloop for me it was just stuck on the white tmobile 4g lte screen. Didnt make a backup either so had to wipe and reflash. Not a huge deal for me but just wanted to report back to try n figure out where the issue might be.
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 10:28 PM ---------- Previous post was at 10:27 PM ----------
AGunz82 said:
Mine bootloops after fixing permissions.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
When I flash anything I always wipe caches and fix permissions as good practice so i also fixed permissions before restarting.
Sent from my SGH-M919 using xda app-developers app

Bootlooping after flashing zip & fixing file permissions and then trying to reboot back to system.
Tried refixing permissions. Tried wiping both caches. No go.
Then I tried reflashing my ROM, but now I get stuck at the Samsung Galaxy S4 screen...
Odd. Never ran into a situation that I couldn't do a full wipe and flash to get out of.

kevinbear said:
Bootlooping after flashing zip & fixing file permissions and then trying to reboot back to system.
Tried refixing permissions. Tried wiping both caches. No go.
Then I tried reflashing my ROM, but now I get stuck at the Samsung Galaxy S4 screen...
Odd. Never ran into a situation that I couldn't do a full wipe and flash to get out of.
Click to expand...
Click to collapse
Same here.
Sent from my SGH-M919 using xda app-developers app

Can't get past the boot animation when flashing aosp roms

So I've done the whole rom flashing thing a bunch. Hd2, infuse, note 2, mytouch and I've never had this happen.
I can flash any tw rom I want amd no problems at all. But no matter what aosp or non tw rom, I can never pass the bootanimation.
I've tried PA, carbon, liquid, and beanstalk. All of them with gaps and without gaps, Tried multiple downloads of each.
Let the boot animation run for 15 minutes. I did download straight to my phone as I don't have access to a computer.
To be honest I was just wanting to play around with 4.2.2 but when I couldn't get it to run it pissed me off and now I'm on a mission.
Don't know what else to try and amy help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

What steps are you taking when trying to flash. I have never had that problem and have flashed all of the aosp Roms and have also gone back and forth between them and tw roms
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

csandman1977 said:
So I've done the whole rom flashing thing a bunch. Hd2, infuse, note 2, mytouch and I've never had this happen.
I can flash any tw rom I want amd no problems at all. But no matter what aosp or non tw rom, I can never pass the bootanimation.
I've tried PA, carbon, liquid, and beanstalk. All of them with gaps and without gaps, Tried multiple downloads of each.
Let the boot animation run for 15 minutes. I did download straight to my phone as I don't have access to a computer.
To be honest I was just wanting to play around with 4.2.2 but when I couldn't get it to run it pissed me off and now I'm on a mission.
Don't know what else to try and amy help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Please provide more information so we can better help you as the post above said. I've not had a problem switching back and forth either.
Sent from my CLEAN Note ll

brandonarev said:
Please provide more information so we can better help you as the post above said. I've not had a problem switching back and forth either.
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
I download the roms and the gaps. Boot into twrp and do all my wipes 3 times. System, dalvik, cache. Install rom. Install gaps. Reboot.
I've tried without the gaps. I've wiped dalvik after that also like some roms suggest.
I chalked it up to bad download at first but all of them? I may try again with a different browser.
Tried boat browser and Firefox. Both hang at boot animation
I'm on cleanrom 4.7 now. Glad I made a backup!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

I figured it out. I had grabbed the new beanstalk build before it was pulled. For some reason when I tried to flash it, it added a seperate folder in my internal sdcard and moved every file into it. For some reason trying to flash from that new folder wouldn't work. Twrp wouldn't see anything in the old folder.
I moved the ROM and gapps to the external card and everything flashed perfectly.
Weird.
Sent from my GT-N7105 using xda app-developers app

That hidden folder is a legacy folder. .
It's placed as a safeguard during the flash process. ..in the event that data/media...or other important files get deleted. .
The TWRP recovery will prevent deletion of the media files. ..but CWM does not. .
You can still delete your EFS and other critical partitions with TWRP..but they warn you first where CWM does not. .
The legacy folder can be used to restore deleted data later if a problem occurs. ..And should be left there when using roms with modified file structures like CM....g

Thank you for the info. Was just weird that I can't flash from that folder anymore.
Sent from my GT-N7105 using xda app-developers app