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.
Related
So I decided to try one of the ICS roms earlier today. I nandroid backup'd my current config, flashed the ROM, played around, ran calkulin's format all, and proceeded to nandroid restore. Booted back into what was my original config only to find it's constantly locking up and random apps keep FCing. I did fix permissions, I wiped dalvik and cache multiple times. What the hell is the point of nandroid if it doesn't ****ing work right anyway?
I'm on RA 2.3 recovery. I backup the normal stuff including .android_secure and wimax.
Do you still have the rom handy?,if so,do your nandroid backup,then without wiping anything,install the rom over the top of the backup you just restored,it should help with the FC's,it worked for me,but if you installed a theme,it will convert back to stock as far as the framework goes.
Try manually wiping all options except sdcard and battery stats 3x or more and then restoring your nandroid then wipe cache and dalvik after the restore and before rebooting, sounds like you may have an errant piece of data that got left behind during the wipe
It seems that the 18 or so reboots I was forced to do have fixed something. No problems now. Strange for sure.
G+ was locking my phone up causing me to have to pull the battery, it was working fine then there was an update in the market but I was using an inverted version and didn't want to update the the bright white one and after a week of not updating it it started randomly freezing up when I would try to upload a pic or post a long message I updated and it stopped :-/ which was weird in itself maybe an app got updated and fixed your issue or maybe something uninstalled itself if your using dta2sd, sometimes when I have FCs, random reboots or have to do a battery pull some of my a2sd apps disappear when I reboot
firstly, am i the only one having searching issues? i would search for an answer, but i'm getting these errors no matter what i search:
"Sorry - no matches. Please try some different terms."
or "Search is temporarily unavailable. We apologize for the inconvenience."
so long story short- my phone would constantly random reboot on 4.3 based ROMs.
long story long- i was originally on CM10.1.3, but it started acting weird over the last few days. when leaving a wifi area, the phone would not switch over to data correctly. i tried to disable/enable data, but that wouldn't work, i would instead have to enable/disable airplane mode for data to start working. and also, i would get random app crashes when i first launch any app. but on a second try, the app launches just fine. so i took this opportunity to change things up.
i've been reading lots of praise for SlimBean, so i flashed the "Slim-d2att-4.3.build.2-OFFICIAL-1349" version with the "Slim_AIO_gapps.4.3.build.2" gapps file. flash steps were as follows (using CWM 6.0.3.1):
* factory reset
* wipe cache
* wipe dalvik
* flash ROM
* flash gapps
* reboot
i get the phone setup, installed Titanium Backup, and started restoring my apps. somewhere along the line, my phone rebooted. i figured it was going thru strain or something so i didn't think anything of it. finished restoring my apps and i left my phone alone. then it rebooted again. after this time, i wiped cache and dalvik to see if that would fix anything. but it happened another time while i was configuring the phone settings. another time when it was doing nothing, and one last time while i was listening to music. all of this within a 3-hour span.
so i decided to go back to CM, but this time 10.2 RC1. to flash this, i instead used these steps:
* factory reset
* wipe cache
* wipe dalvik
** format system
* flash ROM
* flash gapps
* reboot
got it all setup, restored all apps just fine. then as it was doing nothing, it rebooted. then rebooted again while i was in Chrome. and another time while i was trying to text.
i was tired of all these reboots, so i went back to my nandroid backup of CM10.1.3.
was i missing a step or configuration somewhere to get 4.3 working correctly?
EDIT: i just stumbled upon this post, could this be the step i was missing?
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23
*bump*
so from the edit i did on the original post, i was reading about the new bootloader and modem. that once you switch over, you can never downgrade from 4.3. but they all sound like this is only for 4.3 TouchWiz. is that the case with 4.3 AOSP?
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
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
try going back to 100% stock by flashing stock firmware on ODIN. Next root and twrp.
sarreq said:
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
Click to expand...
Click to collapse
I have a t700 and had the same problems you have installing marshmallow. What worked for me was advanced wipe in twrp, everything except internal storage and sd card. From there hit the home key, and flash the marshmallow rom, then reboot into recovery, next flash su 2.5x, then reboot into recovery. Lastly, flash the benzo gapps, and reboot system. My play store started working after i installed in that sequence on t700. Ive heard a few others have had to do that process 2 or 3x before it works, and some, it doesnt work at all. Worth a try though. Good luck.
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.