A couple of nights ago, I accidentally let my phone die. It must have been doing something important, because I kept getting force closes on all stock apps and also apps that required root including superuser. I rebooted to see if that fixed the problem but it didn't boot up after, I figured it wouldn't be a problem and deleted my cache and dalvik and rebooted. The phone booted to the lockscreen saying "Upgrading android, Optimizing x of x applications" but I noticed that when it got to the 33rd app, it would suddenly go very fast and the phone would crash to the boot animation (not the boot logo) on "starting applications". It wouldn't boot back up until I did a hard reboot. After a while, I realized it wasn't going to fix itself and just wiped and re flashed everything. I did restore some user apps in tb and everything was fine. On the next day, i made sure that the battery didn't die but i woke up to the same force closes and bootloop when i rebooted. Tried to delete cache and dalvik again to see if i could reproduce the problem but now it wont boot past the animation at all.
Im using siyah 3.2.7.2 and my second rom (which boots fine) is Pure ics
EDIT: On 3.3.1 now, doesn't make a difference
Related
Hi, I am running the rom Liquid Gingersense and the tb was doing fine until it rebooted once, and so it turned back on and within 3 minutes of turning on again it rebooted again, it turns on and starts up everything and then reboots. Someone called me before it rebooted however, and it worked until the call ended and then rebooted. When I try to reboot into recovery it just reboots normally, and so I tried to download rom manager (because i hadn't done so yet) to get it into recovery and when the app was installing it rebooted. what should i do?
EDIT: LOL nvm, I figured out why, I had accidentally set it to overclock to 1.9 which messed it up, after setting back it is fine
About 3-4 months ago I flashed stock ICS into my Galaxy S2 (I did not wipe the cache, which I discover today was a mistake). I noticed a few weeks later that it was a bit unstable, crashing, restarting, etc. I did not care much and just kept using it.
Today it just would not boot, so after 1 hour trying, I managed to keep it alive (using safe mode) long enough to go to setting and have a factory reset.
Then it would not boot again.
From there, I tried several times the factory reset and wipe cache (using volume up + home + power menu). It would sometimes hang on the "installing applications" until several restarts it would eventually go. Then it would hang randomly on startup "s" video, until I managed to get to the welcome screen - which freezes pretty much on the first or second screen (choosing language and date/time).
I flashed I9100GXXLPY_I9100GDBTLP3_DBT and got the same result.
The phone is not rooted, there is no clockwork and I can't even access the phone to put it into debug mode.
Anyone has any more idea of what can be done besides throwing it on the trash? :/
Hi,
I was using nameless ROM on my TAB. I think it was 4.4.2. I have decided to try ART runtime, so I have removed Xposed Framework, switched to ART and restarted my TAB, it booted fine and showed "Android is upgrading" message so I left the TAB to start.
When I picked it up later I was "black screen only", I thought that battery driained out so I have connected it to charger but nothing happened, so i left if for a few days suspecting I has frozen so I can't unlock it/shut it down.
Right now after a week it's still "black", doesn't respond to connecting charger (I have tried 2).
I also tried to shut it down by pressing power button for 10 seconds but it didn't help either.
What I should try next?
What are the chances that perfectly working tab has died because of ART runtime, I though that bootloop it the worst scenario as system partition can be damaged only while flashing.
Is it possible that the TAB is bricked?
I can also add that I have previously tested ART with Omni ROM but a few apps that I used FC then...
Can you boot into recovery? If so, you can revert back to dalvik using this flashable zip from here: http://forum.xda-developers.com/showthread.php?t=2707841
No, it doesn't power-up at all. Looks like phone with no battery.
Then I have no clue. Never tried ART on my tab before because of Xposed. The one time I tried most of my apps kept FC-ing then I went back to dalvik. But you have to find a way to get your tab into recovery, then you can flash that zip.
The phone is rooted and has a few Xposed modules installed; stock ROM.
I shut the phone down every night. When I wake up and turn it on, every now and again it gets into an infinite boot - not a bootloop (at least not in my understanding). It either stays on the LG logo or the Tmobile logo. Sometimes it boots just fine and quick, sometimes takes a minute longer. Other times I have to hold the Power + Volume Down for a few seconds to reboot it, and it boots fine after that. Yet other times, I have to get into the Factory Reset mode and rebuild the Dalvik cache form within TWRP, after which it boots fine.
The weird thing is that when nothing is changed from the moment it loops to the moment it boots fine; it may only be a reboot away. Granted, I do have (quite) a few things frozen and/or removed in Titanium Backup, but should it affect the boot?
Has anyone experienced anything like that?
Attached are the warnings and errors captured while LiveBoot was running. The lines go really fast, and Nexus 5 shutter isn't capable of going that quick (that's why you can see double lines in certain places). The phone booted after I switched to my swap battery.
Just an update, I restored the earliest Nandroid backup and instead of uninstalling these apps, I froze them in TB. No boot issues so far.
Another update. This morning the problem seems to be back, it was stuck on the T-Mobile logo. Although I can rebuild the cache, it's worse now, because I haven't disabled any LG or system apps since the last restore.
Update to this update: after the T-Mobile logo reboot, it now stuck again on the LG logo and took two 5-minute waits before reboots; it booted fine on the third (essentially, the fourth) reboot upon swapping the battery.
Does anyone else experience this?
i had my phone for about 2 years, it has been rooted ever since i got it and its running custom rom and custom recovery CM 13 on android 5.0.1 and TWRP . about a week ago i was charging my phone, when i unlocked it, i'm unable to go to the home screen because whenever i do that, google app crashed and the phone redirected me to the recently used app tabs, then i tried to reboot my phone and it went to safe mode but then i restarted it and its stuck on bootloop. so i let it be for a while, then it show the "android is starting" tab and "optimizing app number "xxx" out of "xxx" and after it finished, again it is stuck in CM's logo. however, then i put my phone to fastboot an restarted it and i dont know, it turned on again after 2 boot loops. a week after, my phone ran out of battery so i tried to turn it on but it wont , after reading threads on the internet, it suggested me to erase the cache and the dalvik cache. so i did and it turned on. today, i ran out of battery again and i erased both cache and dalvik cache, but it wont turn on.. i have no idea what's going on with my phone, and im a newbie so please go easy on me thank you.