Hello,
I am running Slim Bean 4.1.1 on my Galaxy S2 for almost one year now. I never had any bigger issues with this rom until yesterday. My battery died so I plugged the charging device in and re-started the phone but the booting animation won't go away. I am caught...I can still get into the recovery but that's it.
Any ideas how to solve this issue?
Thanks in advance
travisbotello said:
Hello,
I am running Slim Bean 4.1.1 on my Galaxy S2 for almost one year now. I never had any bigger issues with this rom until yesterday. My battery died so I plugged the charging device in and re-started the phone but the booting animation won't go away. I am caught...I can still get into the recovery but that's it.
Any ideas how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
Let the battery charge a bit until you boot it up, then see if you can boot into the rom. If you can't, boot into recovery and wipe regular cache and dalvik.
Best practice is to never let your battery die - these older devices (and some new ones as well) sometimes don't respond well to a complete discharge.
SteveMurphy said:
Let the battery charge a bit until you boot it up, then see if you can boot into the rom. If you can't, boot into recovery and wipe regular cache and dalvik.
Best practice is to never let your battery die - these older devices (and some new ones as well) sometimes don't respond well to a complete discharge.
Click to expand...
Click to collapse
Thanks!! I tried wipe cache and dalvik. Now I was stuck in the "android is upgrading starting apps" loop. So I just decided to do a full wipe and re-install everything...
travisbotello said:
Thanks!! I tried wipe cache and dalvik. Now I was stuck in the "android is upgrading starting apps" loop. So I just decided to do a full wipe and re-install everything...
Click to expand...
Click to collapse
If you're going to do a full wipe why not just upgrade to KK? The JB Slim isn't supported anymore, but @cyril279 has a few options for you, should you chose that route:
SlimSaber: http://forum.xda-developers.com/showthread.php?t=2772468
SlimKat: http://forum.xda-developers.com/showthread.php?t=2760074
SteveMurphy said:
If you're going to do a full wipe why not just upgrade to KK? The JB Slim isn't supported anymore, but @cyril279 has a few options for you, should you chose that route:
SlimSaber: http://forum.xda-developers.com/showthread.php?t=2772468
SlimKat: http://forum.xda-developers.com/showthread.php?t=2760074
Click to expand...
Click to collapse
That makes sense. I just upgrade to SlimSaber...and I love it. :victory: This morning I was soo p*ssed because of this whole thing but sometimes it just needs an event like this to try out new things
Thanks again!
Related
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
Hey guys,
I've just instelled cm10 a few days ago,
and it's making me crazy, hope you can help!
Most of the time it works great. BUT when I
play some games or use Facebook, it just
Shuts-down the phone, and when I turn it on
it says it got 1-5% Battery left. (it's not true)
When I plug the charger, the battery level
get's back to where it was.
I've tried updating to CM10.1 and the problem
presists.
so,
1. What's cousing those shutdowns?
2. How can I fix the battery problem after the shutdown?
Thanks!
You installed it with a full wipe?
Sent from the Matrix
Doorman404 said:
Hey guys,
I've just instelled cm10 a few days ago,
and it's making me crazy, hope you can help!
Most of the time it works great. BUT when I
play some games or use Facebook, it just
Shuts-down the phone, and when I turn it on
it says it got 1-5% Battery left. (it's not true)
When I plug the charger, the battery level
get's back to where it was.
I've tried updating to CM10.1 and the problem
presists.
so,
1. What's cousing those shutdowns?
2. How can I fix the battery problem after the shutdown?
Thanks!
Click to expand...
Click to collapse
Have you checked to see if this also happens with non-CM roms?
The first thing you should be doing is counting out a hardware problem so install a non-CM rom like a Samsung stock or based rom.
Also do a clean install or your roms to avoid issues. (Wipe data/factory reset in recovery, ONLY USE IF YOU HAVE A CUSTOM KERNEL/RECOVERY FLASHED).
Donnie Sins said:
You installed it with a full wipe?
Sent from the Matrix
Click to expand...
Click to collapse
I came to cm10 from stock, so yes.
CC10.1 - was updated from the ABOUT
menu (OTA update), So I couldn't wipe,
I just did "Factory reset" from Settings
after the update.
TheATHEiST said:
Have you checked to see if this also happens with non-CM roms?
The first thing you should be doing is counting out a hardware problem so install a non-CM rom like a Samsung stock or based rom.
Also do a clean install or your roms to avoid issues. (Wipe data/factory reset in recovery, ONLY USE IF YOU HAVE A CUSTOM KERNEL/RECOVERY FLASHED).
Click to expand...
Click to collapse
There was no Problems at all on 2.3 stock,
So I don't believe it's an hardware issue.
factory reset from the OS is the same as
Full Wipe, right?
calibration might help. Hardly hardware issue.
a korean guy told me so, they are from the future you know; already got the JB and all.
sent, and now this app cra.........
HAHA I know
but What do you mean by Calibration ?
battery calibration, or kernel stweaks.
sent, and now this app cra.........
Battery calibration - yes.
Kernel stweaks - How can it help?
It seems like a problem with the cm10 rom,
Anyone here using the CM10 nightlies?
Can you tell me if yours is stable or
has such isues ?
I think it's the battery info picked up by the ROM. Wipe bat stats to force it start from scratch.
sent, and now this app cra.........
Double post- Sorry
gastonw said:
I think it's the battery info picked up by the ROM. Wipe bat stats to force it start from scratch.
sent, and now this app cra.........
Click to expand...
Click to collapse
Hey, I've tried battery cal. again - it didn't help.
The main issue though is the random shutdowns not the battery stat.
It mainly happens with the Facebook app, Is it a known bug in CM10 ?
Just an update: I've flashed 2 other Stock based roms and the problem is worse Now!
It shuts down like 10 times a day now, on every screen even on Lockscreen sometimes.
The phone was 100% good before I flashed cm10! Did i do something wrong ???
What do you think's wrong with it?
Help! Please?
Does the screen flicker issues on cm 10.1 effect the phone in long term..Wil it damage the screen ?
I've been running 10.1.2, but this morning was notified of update. So I installed the update.
However, the update killed my Wi-Fi, in that I was getting signal, but no internet connection.
So I tried to roll back to 10.1.2, but now have the constant CyanogenMod loading animation and it's been like it for an hour. So I held down the power and volume button and it does exactly the same thing, reboots and get's stuck with the animation?
I can't turn if off or anything?
Can someone please help?
WannabeMKII said:
I've been running 10.1.2, but this morning was notified of update. So I installed the update.
However, the update killed my Wi-Fi, in that I was getting signal, but no internet connection.
So I tried to roll back to 10.1.2, but now have the constant CyanogenMod loading animaition and it's been like it for an hour. So I held down the power and volume button and it does exactly the same thing, reboots and get's stuck with the animation?
I can't turn if off or anything?
Can someone please help?
Click to expand...
Click to collapse
Have had similar problems would love a dev input here,think it has something to do with having to separately flashing a compatible kernel? Or a bug in cm recovery when whipe? Anyways flash meow kernel and ROM, then in twmp recovery wipe all under advanced, then reinstall cm, that should fix it for you.
cantenna said:
Have had similar problems would love a dev input here,think it has something to do with having to separately flashing a compatible kernel? Or a bug in cm recovery when whipe?
Click to expand...
Click to collapse
Frustrating, whatever it is...
cantenna said:
Anyways flash meow kernel and ROM, then in twmp recovery wipe all under advanced, then reinstall cm, that should fix it for you.
Click to expand...
Click to collapse
Sorry, but how do I do that?
Can anyone assist please, as I'm pretty stuck at the moment. Thanks.
WannabeMKII said:
Can anyone assist please, as I'm pretty stuck at the moment. Thanks.
Click to expand...
Click to collapse
Download cm-10.2-20131029-UNOFFICIAL-pollux_windy.zip from here
http://www.windowsxlive.net/xperia-ztablet-z-cyanogenmod-10-2-fidelity-edition-build-20131029/
wipe factory reset in cwm recovery and install rom
once booted into new rom reset into twmp recovery
wipe and advanced wipe all check boxes except last and iinstall cm rom
should boot now. let me know if it works for you. Did for me.
also see
http://forum.xda-developers.com/showthread.php?t=2383800
also side note, i upgraded to sony stock 4.2.2 befire goingbto custom
Perfect. I managed to get into CWM, cleared all the old data and re-installed 10.1 that was still on the SD card. I then installed Gapps and updated CM, but not to the latest this time!
Thanks for the help, I can relax now and the Mrs can now go on Facebook again
WannabeMKII said:
Perfect. I managed to get into CWM, cleared all the old data and re-installed 10.1 that was still on the SD card. I then installed Gapps and updated CM, but not to the latest this time!
Thanks for the help, I can relax now and the Mrs can now go on Facebook again
Click to expand...
Click to collapse
Anytime, happy wife, happy life!
cantenna said:
Anytime, happy wife, happy life!
Click to expand...
Click to collapse
Lol, so true! :laugh:
Need a quick advise.
I've been running with SLIM stable 4.2.2 for many weeks now without any issues.
Yesterday the battery was drained accidentally after a radio app was left running for many hours.
After recharging with the phone off, I turned it on, and the SLIM logo stayed on forever.
Re-booted into recovery and wiped caches, re-booted and still stuck on slim logo.
Re-flashed rom and gapps, wiped caches, and it went past the slim logo, did the upgrading android process, then got stuck on starting apps.
any ideas how to fix this ?
kalda01 said:
Need a quick advise.
I've been running with SLIM stable 4.2.2 for many weeks now without any issues.
Yesterday the battery was drained accidentally after a radio app was left running for many hours.
After recharging with the phone off, I turned it on, and the SLIM logo stayed on forever.
Re-booted into recovery and wiped caches, re-booted and still stuck on slim logo.
Re-flashed rom and gapps, wiped caches, and it went past the slim logo, did the upgrading android process, then got stuck on starting apps.
any ideas how to fix this ?
Click to expand...
Click to collapse
This is my reply to your post in Slim's post:
Did you do a FULL wipe with /system formatted? If you did, try to flash another the ROM to see if you can get through, then re-flash Slim. Good luck.
wolftou said:
This is my reply to your post in Slim's post:
Did you do a FULL wipe with /system formatted? If you did, try to flash another the ROM to see if you can get through, then re-flash Slim. Good luck.
Click to expand...
Click to collapse
I'll try. thanks. was hoping I could avoid a full wipe. not sure why draining the battery would screw up the rom
kalda01 said:
I'll try. thanks. was hoping I could avoid a full wipe. not sure why draining the battery would screw up the rom
Click to expand...
Click to collapse
Are you using AJK Kernel? If so try to reset STweaks Profiles and fix permissions.
Hey XDA
This all started when I didn't put my phone on charge one night, and the morning after I got a text then I went to read it, my screen flickered and my phone crashed, this was usual when my phone dies.
However this time, when I put my phone on charge, it wouldn't boot up, it would stay at the boot animation screen.
I was running AOKP 4.2.2.
I then thought it was just a corrupt ROM so I went to re-install the ROM.
First, when I went to wipe the dalvik cache it said it had failed, this immediately showed warning signs, then when I went to install the ROM from my SD card it said that had failed also.
This left me only 1 option, to restore back to the stock ROM through Odin.
This seemed to go fine until I got to the end went instead of booting into an "android is updating" type thing, it was stuck on a boot loop.
This now leaves me stumped for ideas, so I turn to you, how do I fix my phone?
I hope I can fix this phone as it is my only phone.
Thanks, Jem
jem.graham said:
Hey XDA
This all started when I didn't put my phone on charge one night, and the morning after I got a text then I went to read it, my screen flickered and my phone crashed, this was usual when my phone dies.
However this time, when I put my phone on charge, it wouldn't boot up, it would stay at the boot animation screen.
I was running AOKP 4.2.2.
I then thought it was just a corrupt ROM so I went to re-install the ROM.
First, when I went to wipe the dalvik cache it said it had failed, this immediately showed warning signs, then when I went to install the ROM from my SD card it said that had failed also.
This left me only 1 option, to restore back to the stock ROM through Odin.
This seemed to go fine until I got to the end went instead of booting into an "android is updating" type thing, it was stuck on a boot loop.
This now leaves me stumped for ideas, so I turn to you, how do I fix my phone?
I hope I can fix this phone as it is my only phone.
Thanks, Jem
Click to expand...
Click to collapse
after you install the stock rom via Odin boot into the stock recovery and do a factory reset and wipe the cache. should boot up after that.
one thing i notice after installing 5 different OTA though odin last night they dont wipe user data you have to do it your self. so i would give that i try im sure that should fix your problem
dray_jr said:
after you install the stock rom via Odin boot into the stock recovery and do a factory reset and wipe the cache. should boot up after that.
one thing i notice after installing 5 different OTA though odin last night they dont wipe user data you have to do it your self. so i would give that i try im sure that should fix your problem
Click to expand...
Click to collapse
Thank you very very much, I didnt see the factory reset option in the stock recovery.
You're a true life saver, thanks
jem.graham said:
Thank you very very much, I didnt see the factory reset option in the stock recovery.
You're a true life saver, thanks
Click to expand...
Click to collapse
no problem at all now if i can just figure out my clients gt-i9300 issue my life would be great hahaha