I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
jamesclay89 said:
I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
Click to expand...
Click to collapse
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
sagirfahmid3 said:
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
Click to expand...
Click to collapse
Actually, I am running 2.4.4. Whats still odd about it though is that it ran fine for at least a month and had been on all day. The problem didn't start with a reboot, I had been on it for a while and everything forced closed on me. I am about to try to update TWRP to 2.6.1 and try that. I haven't tried any other roms yet either, I would really like to stay on CM though if I can get it to flash back.
Related
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0
So I have CM12 installed, but when I go to flash the latest nightlys I keep getting System UI crashing. When I acknowledge it, the error will not go away. I have HBOOT 3.18 and radio 1.19 with TWRP 2.8.4.0. I've wiped everything I can think of save the internal and external SDCARDs. What am I doing wrong to not be able to flash the latest nightlys? Ive tried flashing on top of my current CM12, which was upgraded from CM11, and wiping clean. When I wiped clean everything was working great till the phone went to sleep. When I woke it up, same issues.
Yeah, I was having that issue as well. CM12 just isn't stable right now, at least for me. Everything lagged after having the phone on for about a half hour, took 4-5 seconds to do anything after selecting it... it was just a mess. Went back to stock.
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Tobb555 said:
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Click to expand...
Click to collapse
Okay, I have cleared off a bunch of crap off my phone and am willing to give CM12 a try just to see if you have the issue. Which CM12 version are you referring to?
Thanks for the help. Right now Im running version 12-20150128-NIGHTLY-m8. When I try to update to any of the latest versions Im getting the System UI crashes. It doesnt matter how many times I acknowledge it, it wont go away.
I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Vipery said:
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Click to expand...
Click to collapse
try the KDZ. if it continues then it must be a hardware problem..
raptorddd said:
try the KDZ. if it continues then it must be a hardware problem..
Click to expand...
Click to collapse
Thanks for reply, i have fixed the problem. Just pull out and put in the battery, idk what happen it seems to be solved now.
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
AnotherStupidUser said:
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
Click to expand...
Click to collapse
You already lost apps by wiping data, but you still have your photos.
If you had GApps installed before android version upgrade, you now need to flash android 11 GApps. Wiki.lineageos.org tells you what and how.
Thank you for your help. Surprisingly for some reason I found a work around as the unofficial GApps didn't work as well. I wiped data again, so the apps were gone (it took me 3 hours to restore that), but all files were still there and I flashed back to 17.1 with GApps and it worked. Phone is working same way as before. Guess I will wait a LOOOOOOOONG time now until I will try 18.1 again. But again thank you