Hey all!
This questions is probably dev only, but since I dont have permission to post on dev thread, I had to pop out my question here. Here is the deal: from mid march I started building my own nightlies from CM 11 source and I use them only on my device. After 27.03, every time I flash a new nightly, my phone boots up but first I get 'Unfortunatelly, has stopped' and after that same message but for systemui process. Somewhere in CM 11 nightly thread I read that CM is now using msm8960 kernel, so I switched my builds to that kernel, but still have the same problems. If I do a full factory reset, phone boots ok with the nightly I flash, but as soon as I reboot it again, same story... I also tried with the recovery that is build with the rom itself (regular clockworkmod, 6.0.4.8, normally I use clockwork touch 6.0.4.6) still the same problem. But, if I flash the M5 release, it works with no problems... Did anyone encountered similar problems?
Related
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Antonnzr said:
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Click to expand...
Click to collapse
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
DFornazari said:
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
Click to expand...
Click to collapse
I have used nightly builds of CM10 from October 15 onwards with a problen
only on the 19th release when I couldn't install anything due to an issue with
the version of Clockworkmod Recovery. Once I found out how to downgrade
that version, it's all fine (touch wood).
Sam
@Antonnzr
Rather just use normal GAPPS. There was a release by tantrums that caused bootloop, but he fixed it now.
Use ADB to go back to recovery.
@DFornazari
CM10 isn't heavy at all. rmcc committed a lot of changes from TI's branch and I think it caused some instability with the some of the newer releases. I based that speculation from a comparison between nightlies before the changes was made and after the changes was made. I didn't look at the code so I can't be 100% certain since I don't know what they changed. rmmc is a great dev and should have all the device specif bugs sorted soon.
Yes its all working fine now with cm10 m2 and regualr gapps but I have a new issue.
Whenever I try to download an app from the Play Market ( nova launcher, for example ) it pops up with an error reading:
"Error: 'Nova launcher' could not be downloaded due to an error (927)"
or alternatively:
"Error: 'Nova launcher' could not be downloaded due to an error ( error retrieving information from the server )"
Tried to install apps via online Play Store both on my phone and my laptop but the download never starts. Help?
Disregard that, fixed after reflash.
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
I think you mean Nightly of CM 10.2 ...
Use the newest nightly ,in one Nightly there was an error about installation.
The warning is because with the nightly beginning from 20130816 the partitioning layout have to be changed because of Out of space on /system...so the massage is only that you know it and you have to confirm it a second time ...
So test a newer nightly an it should work!!!
Here is the link to the thread of CM 10.2 ....http://forum.xda-developers.com/showthread.php?t=2385178 there are some additional infos ...
Let me no if it works ...
unrealbe said:
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
Click to expand...
Click to collapse
Downloaded and attempted to flash the latest (8/30) CM 10.2 nightly on my Captivate SGH-I897. Both times a dead Android showed up in recovery before it rebooted back to the 8/25 nightly which I'm currently running. Downloaded again to see if it was a bad download, but it appears to be a bad zip. Can't post in the development forum, so I'm putting this here. Will also submit a bug report. Didn't see the error message - it flashed by too quickly.
UPDATE: The 8/28 nightly wouldn't flash, either. Tried to flash both from within the CM Updater. So I rebooted into CWM Recovery and flashed from there. The 8/29 nightly flashed with no apparent problems.
So, did the 8/25 nightly break the CM updater? Nightlies downloaded fine, just wouldn't flash.
I recall pawitp stating something about cm updater being broken for a few builds over in the cm 10.2 thread. You may check there for your answer.
Sent from my SGH-I897 using XDA
Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use
Hi guys!
my phone seems to have issues with dirty flashes.
A few days ago i successfully clean installed cm 13 from stock. so far, so good.
I decided to use the nightly updates so i downloaded the latest build from the built in updater(i also tried to install the nightlies manually but still no success)
The installation by itself did not show any errors but when i reboot the phone from the recovery(TWRP) it gets stuck in a bootloop. this happened with every nightly so far but when i clean installed them they worked fine.
Am i doing something wrong and does anybody experience the same issue?
i appriciate every tip on how to solve this problem because i am not going to clean install the nightlies and set up the phone over and over again
thanks in advance
Jurac aka. mynameisnotraphael
Have you tried wiping cache and dalvik?
Sent from my Moto G 2014 using Tapatalk