Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.
dissonance01 said:
Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.
Click to expand...
Click to collapse
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?
audit13 said:
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?
Click to expand...
Click to collapse
Thanks for the reply, sadly yes I've wiped pretty much everything but the sdcard in between installs. ROM's like OH!NO!'s v20 work fine.
Thing is I used to have CM10 installed before (and even had 10.1 but it was a bit unstable), until one day the phone had a random reboot and then would not stop boot looping. I stayed with v20 for a while before trying at CM10/10.1 again, and now here I am
EDIT: I just tried OH!NO!'s CM10 hypersonic which works great... until I reboot, and from that point on it just boot loops. I wiped data, cache and dalvik after that and now it's just like the others, reboots on pressing start >_<
Maybe there is something wrong with the hardware?
Related
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.
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
Hi,
I was running AICP android 4.4 fine for weeks.
Then it kept hanging at boot screen , well just after when screen went black
Only way I could get to boot was clearing cache and re-boot. Worked OK then same thing any re-boot. This got worse and worse until nothing would boot.
I have found this isnt an ACIP issue all kitkat roms do this now on my phone (has now become they never boot). If I put 4.2.2 back on works perfectly
Im flashing the boot.img and reseting factory, dalvik and cache before flashing
Any ideas - really dont understand why 4.4 worked for a fortnight before becoming problematic and then being impossible to work
m60kaf said:
Hi,
I was running AICP android 4.4 fine for weeks.
Then it kept hanging at boot screen , well just after when screen went black
Only way I could get to boot was clearing cache and re-boot. Worked OK then same thing any re-boot. This got worse and worse until nothing would boot.
I have found this isnt an ACIP issue all kitkat roms do this now on my phone (has now become they never boot). If I put 4.2.2 back on works perfectly
Im flashing the boot.img and reseting factory, dalvik and cache before flashing
Any ideas - really dont understand why 4.4 worked for a fortnight before becoming problematic and then being impossible to work
Click to expand...
Click to collapse
You don't need to reset to factory you need to format data,system, cache and dalvik cache this is full wipe. Don't format your SD
First, for shortening and simplicity let's use cm versions only last numbers (cm-12.1-20151230-NIGHTLY-nicki will be 30 etc.).
I will arrange my short story in points for better understanding, let's begin here:
- I installed CM 23 (it's 12.1 but the number is for nightly like shown higher) and updated to 26, everything was fine
- quick install of Open Gapps, my apps and doing settings stuff, everything fine
- wild update to 30 appeared, i updated it and it was not very effective
- device rebooted, flashed update automatically, optimized apps aaaaand it got stuck on finishing boot. it was fully ok and responding cause a sound played when i plugged it to charging, it was showing touches ( i set it to show em before update), but it was stuck. So i took battery out and it started to boot, after couple of seconds screen brightness turned down as in every normal booting, boot animation slowed and lagged a few times but then continued to bootloop. Here is a list of things i tried:
- rebooting of course
- clearing cache and dalvik in twrp, then it just optimized apps again and got stuck on starting apps
- wiping data, still bootloop
- wiping everything and installing fresh CM 30
Only the last worked but i lost everything i installed etc. I made a backup of data partition but it restored only some apps ( not even gapps) and settings for some reason.
so after installing everything again i lived it for a while, but because it is a nightly a new update was posted! CM 104
- i downloaded it in cm updater as every other update (btw flashing cm 26 and then 30 from .zip gave the same result), installed it, and it worked soo...
- two days later another update appeared(cm 106), i check every update changelog and this one was big.
- happy of last successful update i just updated it but this time it didn't worked so well
everything is the same as updating 26 to 30, and here we are it got stuck on finishing boot, i took battery out, bootloop, clearing cache and dalvik, optimizing apps, got stuck on starting apps, system fully responding to the same things. i turned the phone down and started this thread.
I have a full backup of everything on another sd with cm 30 and installed apps, but because system is responding i think you guys can help me. i don't want to do a clean install every time a not working update appears. I could stay on last working version, but i'm a type of a person who wants everything updated even if won't give me anything new so staying on last working version from backup is only accepted if you guys won't have any solution or at least idea.
Big thanks for everyone that will bring anything here and probably save some time another happy cm user
EDIT: also, i can restore that backup i have and install version 104, and then figure out how to install it properly
my own idea
so, now i have restored my backup and when i have some free time i'll try to install fresh cm without gapps and update it a few versions, if it'll work problem solved. i will have to just clear cache and dalvik after every update and flash gapps. I only want to ask, if it will work, will flashing gapps with the old ones installed make any issues?
Try to re install rom after full wipe
rohitnegi44 said:
Try to re install rom after full wipe
Click to expand...
Click to collapse
i specially wrote this thread with extra simplicity, but you didn't read that it's working after full wipe, i'm trying to install update AND save my data. read before you post and try to get some easy thank points or whatever this forum has somewhere else.
FIXED IT!!
So for everyone who's looking for answer to this problem here's the fix: after cm flashes and turns off, hold VOL+ button to go to recovery instantly then wipe cache and dalvik, flash gapps, again wipe cache and dalvik reboot. For me it worked.
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.