I installed helix boot screen and shutdown screen on my wifes phone, she is running syndicate 1.0.2 with fuscia theme. Now she is getting a ton of force closes, it pretty much locks her phone up right after the boot up screen! How do I fix this? or how do I get rid of the boot screens and put them back to syndicate boot screen and shutdown screen?
She must have improperly shut the phone. Boot into clockworkmod, fix permissions then try rebooting. If that first work you're going to have to reflash the Rom.
Texted while driving
Related
I've got a strange issues and, unfortunately, I'm not exactly sure when it started. When I do a reboot or a shutdown of my phone it will not power back on after it shuts down. I can't push the power button to make it power back on. I have pull the battery first, then it will power back on without any issues.
I honestly don't reboot or shutdown my phone very often, so I don't really know when this may have started. I'm running Uncommon Sense v1.1 with the stock kernel. I also have a custom Boot Animation and Splash screen. I know I've done successful boot/restarts with the custom splash screen and with Uncommon Sense v1.0. Booting into Bootloader or Clockwork seems to work fine.
Any suggestions on what I should check?
I figured this out. I upgraded to Clockwork 2.5.0.5 a few days ago just prior to me noticing this issue. I downgraded back to 2.5.0.1 and everything seems to be working again. Weird.
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Well the phone will take slightly longer to boot up once you wipe the caches, because they have to rebuild. Do you wipe your cache and dalvik when flashing a boot animation?
WhiteiceDMSTech said:
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Click to expand...
Click to collapse
That's never really happened to me on a consistent basis. I've got stuck at the splash screen a couple of times, but it was my own doing one way or another. How long do you let it hang on the Splash screen before you pull the battery? Sometimes mine will sit on the splash for a good minute or so during a normal reboot. After wiping cache's it can sit there for a good 3 or 4 minutes sometimes. I've caught myself pulling hte back cover off the phone to yank the battery, then I notice that the boot animation was starting, and it booted up. I just wasn't patient enough. Have you tried changing away from that boot animation, temporarily, to see if the problem goes away? I doubt that's the cause, but you never know. And if it started happening right when you changed boot animations, I'd say the first thing to try would be changing out to a different one, and see if the problem persists. Has this been happening on any ROM/Kernel combo you've tried? Perhaps it's the kernel you're on, have you tried another? Do you use SetCPU?
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
I use different kernels to try them out depending on if I am using a sense based or AOSP rom, and it seems to happen no matter what kernel. I do not use SetCPU.
Whiteice
WhiteiceDMSTech said:
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
Whiteice
Click to expand...
Click to collapse
Oh I gotchya, so it was the splash screen you changed to the jordan symbol. Yea, I mean, most of the time it will pass by the splash screen in less than 30 seconds, but for whatever reason, from time to time it will sit in the splash for a little longer than normal. If it goes past 5 minutes then yea, that's too long. It shouldn't take that long. Have you tried a different kernel?
Yes, I try different kernel's all the time and it happens on most of them.
It seems that anytime it freezes up on the splashscreen and I reboot, and it still freezes up on the splashscreen that I have to reboot into recovery (AMON 2.3) and wipe cache and delvik cache each and every time for it to clear whatever is going on. Then usually it reboots fine the next boot after doing that until I reboot again and it locks up. Then repeat above.
Thank you,
Whiteice
So Today I changed my gfs lcd and the digitizer. Installed it fine, I make sure all the ribbons are properly connected and close up the phone. The phone turns on and shows the splash screen, seems like it's booting. I decide to use the latest RUU and see if that helps. A few reboots later i on the newest hboot, thing is it keeps happening, except now i can hear it boot (sprint boot anim). I battery pull a few times and I get it to boot. Touch screen works fine and all, tick Development and keep awake (because once it slept it wouldnt turn on again), mind you adb works while the splash is displayed and after the boot anim, adb also works when the screen is turned off and it wont wake up.
I just want a second opinion on if i should get another lcd screen. The one I installed didnt have the best reviews.
Thanks.
ps: i dont post alot because i know how to search, but i havent found anything on this exact issue.
Im slightly confused... so does it boot? or not? I am trying to make sense of what you wrote...
Try clearing the storage in hboot something may have corrupted during the process...
well it does boot you can hear the sprint boot animation, and i can also adb into it. getting into the bootloader works fine, booting into recovery or regular booting is the problem. Just displays the splash screen, but as I said I think it does boot into recovery/system because I have adb access.
edit: i just turned it on and it booted, but once put it to sleep the screen wont turn back on.
If it's not getting pay the splash something is stalling it... Did you try to run a logcat from adb? Do that and look for errors.
Sent from my PC36100 using xda premium
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
I tried reflashing it another few times and now I actually got into the setup screen and got to the home screen. It charges somewhat normally but it still boot loops when I start it. When I plug the charger in when it's looping it boots fully and I got to the point where I installed an update. Not I'm stuck in a loop on the T-mobile splash
Try a new battery.
Bell-wether said:
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
Click to expand...
Click to collapse
Did you try Samsung Kies' emergency recovery option yet?
Im facing some strange issue here since 1 month. After installing new rom (say phoneix or sultan) and after using for sometime UC brower gets force close error . And when i restart, the phone is stuck on boot animation, sometimes it automatically restarts and stuck on blank screen but notification light remains on. I only found solutions for that is to reinstall system again. Anybody is also facing some kind of this probs or got any other reason why its happening?
Its happening only during clean flash and not during dirty flash