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
Related
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
Solved by restoring KK4 stock used corn kernel then installed CM 7.1, CM 9.1, CM 10.1.3, and 10.2. Works great now with IMEI intact.
I install KK4 stock Gingerbread installed recovery then proceeded to install CM it updated recovery rebooted then tried to flash again it said successful then rebooted only to see it return to recovery. By the Cyanogenmod logo did come up but that's all got then reboot into recovery.
did you wipe data and do a factory reset?
sent from one of my two SGH-I897 Captivates
dracinn said:
... then installed CM 7.1, CM 9.1, CM 10.1.3, and 10.2.
Click to expand...
Click to collapse
Wow! :laugh:
On this Omnirom 4.4 for N7000. Am I supposed to have to flash CMW every time I update the nightly. Currently on 1Dec build. Also these night lies unrooted me and I can not figure out how to root again. I am kind of a noob. So that leads to my last question. Since you were working on the CM 11 builds you know what's going on and when I had beta 6 flashed it didn't unrooted me or uninstall CWM. So is there a way to get those codes from CM 11 into the new Omniroms so we don't have to constantly reflash CWM and reroot. Thanks
-Omni rom comes with twrp recovery. You can flash the update using this recovery itself.
-For rooting you will need to flash supersu after you flash the ROM. This zip can be downloaded from the ROM thread.
-CM 11 for n7000 stopped at beta 6 for now till may be if cm team publishes a nightly.
Thanks
nokiamodeln91 said:
-Omni rom comes with twrp recovery. You can flash the update using this recovery itself.
-For rooting you will need to flash supersu after you flash the ROM. This zip can be downloaded from the ROM thread.
-CM 11 for n7000 stopped at beta 6 for now till may be if cm team publishes a nightly.
Click to expand...
Click to collapse
I have flashed CWM but every time I flash a new nightly it overwrites CWM and I have t reflash before I can flash a new nightly. Thanks about supersu. But what I meant about CM features. Herna was working on the beta 6 so why can't those CWM and root features be moved to Omnirom?
I don't think cwm will be used in omni as they have gone with twrp recovery. Most of the features will be integrated slowly
You font need to flash cwm every time. You can flash the zip file using the twrp recovery also.
nokiamodeln91 said:
I don't think cwm will be used in omni as they have gone with twrp recovery. Most of the features will be integrated slowly
You font need to flash cwm every time. You can flash the zip file using the twrp recovery also.
Click to expand...
Click to collapse
Cool thanks I thought the thread said you couldn't flash the Omnirom zip with twrp.
You cannot flash omni rom with a cwm version lower than 6.0.43. I guess. Twrp is fine.
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?
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