Big BIG problem.
Infotmic FlyTouch 3, temporary root using Z4root.
Replaced boot animation using this tutorial:
http://www.addictivetips.com/mobile/how-to-change-customize-create-android-boot-animation-guide/
Used this bootanimation.zip file - AndroidParticles2:
http://dl.dropbox.com/u/19412696/480x800_AndroidParticles2.zip
Got it from here:
http://forum.xda-developers.com/showthread.php?t=905538
I put the ZIP file in this folder: /system/media/ - that was probably a very stupid ideea.
Now the tablet is not getting past the boot animation.
In the middle of the animation, there's a 1-2 seconds pause, white screen instead of android robot.
Endless bootanimation loop.
Of course, tried hard reset. Of course, it did not help.
Probably, all my apps and bookmakrs are gone.
Probable solution: flash a custom ROM. But that's really scary.
Any other ideas? Please help, I'm desperate.
Hate to ask, but did you flash Clockwork Mod Recovery before doing this? Any chance you made a nandroid backup (or even titanium) of your data? If not, you may have lost your stuff. I'm not at all familiar with your phone though.
If all else fails, you could try a program like android explorer (or similar...just search around XDA). I had luck with this previously recovering from a bootloop. It will sometimes recognize your phone (even while bootlooping) and you can go into the files and replace the boot animation with the original. I once tried flashing CWM from this program while bootlooping...and it worked!
Good luck!
Sent from my DROID2 using XDA Premium App
No backup, no nothing.
Only temporary root using z4root, copy bootanimation.zip to system/media, reboot.
And it's not a phone, it's a tablet.
I dont' care about the apps and data, I already did a hard factory reset and they're gone.
But the system/media folder content is still there.
Fixed it myself.
Flashed Tim ROM
Then fixed 576 resolution. Even tough Elixir and webpage specs say it has 600 resolution !!
Related
A while ago i installed an app called "Boot Animation Lite" and it just swaps the boot animation. I decided i no longer wanted it because it was slowing down my boot time. After deleting it, the animation i installed was still there. I emailed the dev about it and he said to reinstall & put the stock anim back on. I did this, and the mario-bros one i had installed was still there. So i imported a stock one, tried that, with no success. Loaded the "AndroidStock" one from the app menu, and that didnt work.
After becoming furious about it, i applied the stock, then uninstalled the app, used RootExplorer to remove the directory for this app (including the mario-bros boot) and its still F'ING mario!!!!
WTF?
This is irritating as hell, since ive swapped to TelusLite-v4 it takes my phone roughly 20 seconds to complete the boot sequence, but the Mario animation sticks around for about 2-3 minutes. So i want some help removing this, because im bout to pull my hair out over this!
If anyone knows how to restore the stock animation that would be GREAT!
See either /data/local/ or /system/media (look with RootExplorer). There you'll SURELY find a bootanimation.zip, which you can delete
awesome.
deleted both .zip files, then removed the folder as well off the SDcard & it worked.
many thanks!
ROFLMAO you had to see freaking mario for 3 minutes before booting your phone ahahahaha sorry but this made me laugh
i´m glad your problem it´s solved !
Hello.
First sorry for my poor english and my newb-ness ...
My xoom is stuck in boot animation (the honeycomb animation).
It is recognised by my computer, I can access it via adb.
I wish I could unbrick it without having to reset it.
The last thing I did before reboot was to install ADW.launcher.
So I thought I only had to remove the apk/odex from my system/app folder, but the files actually do not exist.
Is there a way to know what is happening, and to repair without having to do a full reset ?
Thanks for your help.
davpitdavpit said:
Hello.
First sorry for my poor english and my newb-ness ...
My xoom is stuck in boot animation (the honeycomb animation).
It is recognised by my computer, I can access it via adb.
I wish I could unbrick it without having to reset it.
The last thing I did before reboot was to install ADW.launcher.
So I thought I only had to remove the apk/odex from my system/app folder, but the files actually do not exist.
Is there a way to know what is happening, and to repair without having to do a full reset ?
Thanks for your help.
Click to expand...
Click to collapse
How are you seeing system/app folder. Try looking in data/app folder instead.
Sent from my Xoom
Thanks for the answer.
The installed apps are in data/apps ? Or is it the data for each app ?
I am rooted. I am seeing files with adm remount, adb shell, and then shell commands.
I tried lots of bizarre stuff yesteday night, removing or pushing files to the system dir, but off course I didn't manage to do anything usefull.
So I decided to flash STOCK MZ604_HW169 root, recovery, system and userdata.
I lost my userdata but kept my apps.
Anyway:
1. I would be pleased to know how could I have been able to know what is wrong ( is there a bootlog ?) and what should I do if and app prevents me to accomplish full boot.
2. My xoom is a french wifi, and stock us wifi works like a charm on it.
(JaymZ37 is asking the question in this thread:
http://forum.xda-developers.com/showthread.php?t=1052644&page=5
and I am not allowed to post the answer)
Before i start i just wanted to let you guys know, i did my best to search around the forum using the search bar and manually, read all of the guides and tut's, read other peoples problems and tried their solutions
nothign seems to be working.
im on a Pantech Sky Vega IM-A650S.
i followed the tutorials located
http://forum.xda-developers.com/showthread.php?t=1702625
http://forum.xda-developers.com/showthread.php?p=27477164#post27477164
but nothing seems to be working. my phone is z4rooted, and now when my phone boots its just black and plays the original boot sounds.
im doing this through the ROOT EXPLORER method,
i was trying to get the alienware boot animation someone created here to work on my phone and it just stays black.
i have stretched the images like in the tutorial, used the "imageresizer/Boot animation Creator"
i place it on my sdcard, then click mount r/w and move it to the media folder where it replaces the original bootanimation.zip
- in an attempt i actually tried renaming it just to "bootanimation" (without the .zip) and placing it in my "bins" folder because i noticed that there was a file there as well. looks like it made my situation worse.
all i really want to do is learn that way i can start making boot animations other people may want to use.
0 i know it was stupid of me not to make a backup of the original bootanimation, but i have the files needed to factory reset this phone.
the resolution is 480 x 800 ( i tried this resolution as well as the others )
Help would be greatly appreciated, i only ever ask a question once and thats when im at a complete loss
Thank You Xda-Developers!
i know its redundant
Up, hope its just something simple im forgetting to do,
this is in the right section right? thanks
try this...
thanks
so it could possibly be due to the program im using? ill go ahead and give it a try right now, thanks for the quick reply
- just installed i see that its kind of a manager for boot animations, but how would i get that specific boot animation to work.?
didnt really like the boot animations on the list, but thanks.
any other suggestions?
would i be making a mistake when stretching the pictures? other than that the program listed in the link above pretty much does everything for you
wonder why it wont work :s
didn't work still displaying black when the phone is booting. even with the program,
Bump, I'm on the same situation. Even the app for the bootanimations wont play the selected animation.
I'm trying via terminal, pushing the zip through the ADB, I've just modified the stock bootanimation images and saved as PNG-8, zipping the folfer with 7-Zip and selecting store instead of compressing...
Thanks for the help!
try flashing another rom, which supposts them
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?
Has anyone figured out a way to replace the stock MetroPCS boot animation?
Although I'm rooted and using the Tried & True method of renaming the stock animation to ".bak" and replacing it with the Nougat (or any other for that matter) animation (as well as setting permissions) does not work.. It's as if MetroPCS has a "fallback" boot animation hidden somewhere..
Even deleting the stock animation does not stop the MetroPCS animation from engaging.
Any Help Would Be Appreciated.
I feel your pain...I have the tmo variant....same issue
RaiderWill said:
Has anyone figured out a way to replace the stock MetroPCS boot animation?
Although I'm rooted and using the Tried & True method of renaming the stock animation to ".bak" and replacing it with the Nougat (or any other for that matter) animation (as well as setting permissions) does not work.. It's as if MetroPCS has a "fallback" boot animation hidden somewhere..
Even deleting the stock animation does not stop the MetroPCS animation from engaging.
Any Help Would Be Appreciated.
Click to expand...
Click to collapse
Yes its in the System/OP folder
A Hero....
xxbabiboi228xx said:
Yes its in the System/OP folder
Click to expand...
Click to collapse
Bless You My Brother..
Thanks Has Been Given.. :good:
And where can you find boot animations to flash for the lg Stylo 3 plus?
Can someone give detailed instructions on how to do this because I've tried myself I went to system/Op but really don't know what to select from there and exactly what to do. I was going to use the Jay rummy app boot animations to change the animation but I keep getting an error. I'm pretty Savvy on most things but this is something I've never done before so I'm definitely a noob to doing this. Thank you and any help would be appreciated.
Sent from my LG-TP450 using Tapatalk
Making Boot Animations
To create a boot animation for yourself, as I have made them in the paste(around the 4.0 era), after extraction seems to be the same.
https://forum.xda-developers.com/showthread.php?t=642851&nocache=1
Please give thanks
I decided to mess around with this a bit tonight on my MetroPCS Stylo 3 Plus (MP450), i assume the t-mobile version will be same/similar
(Root required, obviously)
Now hop into your root browser (any root browser should be fine)
(Optional but recommended)Firstly, get ROM Toolbox Lite, go to the interface tab, tap the bootanimation button. Go to top right 3 dots for options, create backup. This way if you decide not to use custom anymore youll be able to go back stock without having to reflash firmware and losing root ect..
I found that there are 3 locations for boot animations.
The one most know of is the standard /system/media
Delete the bootanimation.zip out of there.
Then we have another in /system/OP/MPCS_US/poweron
Delete that bootanimation.zip also.
Now with that done, on boot it should default to the 3rd i have not seen mentioned yet, /data/local which will simply display an image of the word android.
Now, get yourself back into ROM Toolbox Lite.
Under the interface tab, you will see boot animations. Go ahead on into that. Now you will have access to many different boot animations. I find the ones labeled with tablet seem to come in best resolution. Click one. Youll see an option to resize. Tap that. Resize to 1080x1789.
Now normally when trying to use this app to load a boot animation, it would default to /system/media, which of course would fail on this phone because of the /system/OP/poweron copy we normally would have to go into a root browser and copy/paste our /system/media bootanimation.zip to the OP/poweron. BUT, we deleted both of those. So now the toolbox app defaults to /data/local, our last remaining location.
Tap install on your 1080x1789 resized choice of boot animation, and after toast for super user permission shows, feel free to reboot.
*note* i have found a few of these boot animations simply do not work. Still working on the why, and work arounds for those ones with issues, but for the most-part you should be all set with this.
This method of deleting both /system bootanimation.zip is merely to force it to boot from /data/local on boot, and to make the toolkit to default to that location, this way you save the step of having to go in root browser and copy/paste every time you change your boot animation.
Hope it helps. Thank me if it works out for you
They probably don't work because of resolution. I used to be mad into this