Hello everyone,
My cm auto updater hasn't been working for about the last week. It used to work fine, but just randomly stopped.
Basically what happens is I download a nightly, and then hit reboot and install like usual, but then it just boots to twrp and doesn't actually run the update. I tried putting the downloaded file on the root and flashing it manually through twrp, but when I swipe to flash the screen goes black and reboots twrp.
I tried wiping and clean installing cm, which worked fine, but the next nightly still did the same thing.
I also tried upgrading to the latest twrp, which also didn't fix it....
Any ideas? Thanks
known bug/issue. their G+ is flooded with the same reports, most users state they just flash the zip in twrp from the cmupdater folder.
Look into using Cyandelta for updates, this results in smaller downloads and less problems in my experience.
Awesome, I tried cyan delta and it worked perfect. Thanks!
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.
I currently am on CM 10.2, which installed fine and is working nicely. I decided to try out CM11 and ran into a bunch of problems.
First off, following the instructions, I booted into recovery, wiped/reset, and attempted to flash the current cm11 zip file. I tried this several times because each time I got an error message saying some changes failed. Dead in the water. I restored 10.2 and tried again, this time following a suggestion to first extract boot.img and flash that with UKF, then flash CM11 and the KK apps from recovery. I was able to do those steps, but when it came to rebooting to system, the whole thing hung up for about 10 minutes, then rebooted. At that point I thought all was good, and I was up and running on CM11. I noticed the camera was FCing, so I thought I'd better reboot. But when I try to shut down or reboot, the phone gets stuck (in either process). The only way to close the phone is to pull the battery. So, now I don't know what to do to get this phone running on CM11. Any suggestions?
http://forum.xda-developers.com/showthread.php?t=2582060 use this to install cm11
shadytarek_97 said:
http://forum.xda-developers.com/showthread.php?t=2582060 use this to install cm11
Click to expand...
Click to collapse
This is true!
This description must be used and all will work if you follow this sequence to!
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
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
BEDickey said:
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
Click to expand...
Click to collapse
I haven't flashed this rom for my turbo yet and this may not be the issue but in the past, dealing with other phones on CM, when you would 1st flash the rom, (& before rebooting the 1st time) you would then need to flash the gapps immediately after for everything to work properly. Try flashing the rom and gapps before rebooting.
I didn't see if the CM op instructions recommended this, just personal experiences from previous rom flashing.
I have had this happen twice after installing any CM13 on top of the March 31 nightly. I have not found a way around it yet besides doing a factory wipe after installing CM13, Open GApps and the latest radio code in this thread.