Ok, I've been trying to upgrade cm 7.0.2.1 and for some reason everytime I go into Clockwork Mod, it says there is an update for it and I'll do the usual update process, then when it boots up again, it is still CM 7.0.2. I even tried a full wipe of everything and a battery pull and still it brings up the "update available" for CM 7.0.2.1. Not to mention it didn't even update and I'm still at CM 7.0.2. Has anyone else experienced this problem and is there anyone that can help me with this?? Thanks.
It's because the latest update (Nightly 57) did nothing more than correct the version number for all the CMs. So, while it may appear there is an update because they came out with a nightly after 7.0.2.1..it is still called 7.0.2.1 (nothing changed except a label)...if you catch my meaning.
I suspect a big update (7.1) will be coming out in the next day or so based on the change logs.
(And you really should post in the correct section. If you have a question...it goes under questions.)
Okay, sorry about posting in the wrong area. I was just reading around and decided to post it here and didn't even see the questions area. But when I go into Rom Manager, it still says that there is an update available which is CM 7.0.2.1 I did the update but it doesn't say 7.0.2.1, it only says 7.0.2. Which I find it kinda weird. So you're saying that it is updated but it will only read as 7.0.2? Cuz that's what it says, nothing else has changed except for the fact that it keeps reminding me that there is an available update which is CM 7.0.2.1. So I dunno.
Related
Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.
As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.
of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.
flashed to 7.2 RC2;
please lock.
vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.
Just like people in this thread: http://forum.cyanogenmod.org/topic/70506-freezes-and-re-boots/
I've looked everywhere. but cannot find any answers.
I've been having trouble with constant reboots ever since any ROM released after cm-10.1-20130316-NIGHTLY-d2spr
Today I saw that there is RC2 available so I decided to try it.
I did my best and got rid of all the 0\0\0\0\ folders (only 1 left it seems), updated Clockworkmod (to the newest I think), then installed the newest RC. (clean install).
Everything was going well until about an hour ago the phone began rebooting again.
Does anyone know what the issue is?
OR if anyone else has a suggestion for a non cm-based rom that is good, let me know.
Did you verify md5sum? Try flashing another kernel right after the ROM flash.
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.
Hey all,
At this point I'm under the impression that it's the CM Nightly that's giving me issue, but here's the rundown in case anybody has any ideas before I revert to a past CM nightly, or a full rollback to VenomROM.
I had the latest build of VenomROM, and yesterday decided to give the new CM 12.1 Nightly builds a shot as my buddy told me it was looking super slick and seemed to be pretty good.
I do the usual when switching custom ROMs, and while everything else is working just fine, my mobile data seems to not work. I can make phone calls and get text messages just fine. But anything related to data I currently have to be connected to WiFi to access.
As far as I know, my phone/carrier firmware is up to date, as the issue with "non-Lollipop firmware + VenomROM = no Wi-Fi" was a non-issue for me.
For the record, my carrier is Rogers. It looks like my APN list and settings are what they should be (according to Rogers), and I've tried some things their tech support asked me to earlier today "Restore Default Settings" for APN's, taking out and reseating the SIM card, turning off my phone while they reset things with my account/SIM from their end, and all to no avail, even a wipe and re-install of the CM Rom produced a no-go.
Anybody got anything else I can try before I revert back to VenomROM? As much as I liked it, I'm really digging the look and feel of the CM nightlies.
Cheers,
shutuppat
For the last 2.5 weeks I have been unable to update to any of the newer Nightlies for Cyanogenmod 13 on my Asus Zenfone 2. After the update is finished my phone claims I am using the wrong password to try to access my phone. I am not using the wrong password, updating seems to change it for some reason. Because I am unable to access my phone I am forced to boot into TWRP and revert to the last build that was stable for me. So far I have only tried two newer builds, the most recent one as of this post (August 3rd) and another one last week (July 27th). Neither work, the build I currently run that works with my current lock screen password is July 17th.
Nightlies for my specific device.
I have done a bunch of forum and google searching and nobody else seems to have ever had a problem like this. I would try to report this as a bug to the CM team but bug reports aren't allowed for Nightlies.
Any help is greatly appreciated.
Edit: Fixed
I fixed the issue by disabling the lock screen, updating to the latest nightly, and re-enabling the lock screen.
Have you tried clean flash?