Related
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Did you try to wipe cache and dalvic cache in CWM?
Dizzyrul3z said:
Did you try to wipe cache and dalvic cache in CWM?
Click to expand...
Click to collapse
No. I just make a dirty flash over the Cyanogemod-Updater under Settings.
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Volkan66 said:
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Click to expand...
Click to collapse
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Volkan66 said:
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Click to expand...
Click to collapse
What recovery do you have installed?
january waower
kieranc said:
What recovery do you have installed?
Click to expand...
Click to collapse
I have installed ClockworkMod-Recovery (CWM): cwm-6.0.4.6
I don't have any problems with the recovery but with the Nightly Update from 27th February.
I can't understand how the cm-11-20140227-NIGHTLY-falcon can get official, when a lots of people have the same problem: bootloops.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I totally agree with you. I won't do a full format of the internal card. Just waiting for the next Nightly in the hope that dhacker improves this issue.
Do you have also problems with GMAIL. After each restart GMAIL is lost. I must install it each time new.
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
kieranc said:
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
Click to expand...
Click to collapse
So, I installed by mfastboot for now the newest stock rom 4.4.2 DE, updated to the latest release and rooted.
Maybe I'll flash also kernel to faux's release. Very strange issue. I flashed CM several times and today's issue was the first time.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I've just wiped /data/media ("sdcard") and have successfully installed and booted feb 27th build. Strange problem but that looks like the solution....
I was at the 0224 build and flawlessly updated to the 0227 build... no issue so far. i am using twrp...
Hey guys,
i have flashed the newest Nightly cm-11-20140228-NIGHTLY-falcon.zip today and everything was solved. No bootloops or lost of apps.
With pink kernel the system rocks. This is awesome. Thanks to dhacker29, pinkflozd, faux123, razrqcom-dev-team :good::good::good:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
hydromän said:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
Click to expand...
Click to collapse
I can confirm your sound problem.
I am using the nightly version 0228 and pink kernel 0228 and would recommend you to use the pink kernel because you will feel the boost in performance.
Yes the battery will drain a little bit more than on stock-cm but it is worth it. I can use my phone with pink kernel two days long without charging it.
So I will try Again Pink Kernel =).. I hope the Sound in Call Problem get fixed soon
Android-CM11
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
hydromän said:
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
Click to expand...
Click to collapse
Yeah this version of pink kernel is great. I hope this kernel will leave soon the beta-stadium and will get official.
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
tohigh said:
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
Please flash the TWRP 2.6.3.3 recovery first then flash the newest nightly cm-11-20140304-NIGHTLY-falcon.zip .
I am using 0303-NIGHTLY with TWRP 2.6.3.3 and don't have such issues like bootloop again.
But it is very important to flash the recovery first, then flash cm-11-20140304-NIGHTLY-falcon.zip with Cyanogenmod-Updater under settings.
If you do otherwise flash cm first you will encounter the same problem.
So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.
still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery
but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???
so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
anybody?????
THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk
Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..
THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk
THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.
gonna try Philz Touch CWM and if that doesn't work then TWRP
I have a 6045I
Originally I ran the Chinese ROM with no problems. Wanted to check out the CM beta so I did the standard procedure and followed in instructions on flashing. Found out I was constantly in a boot loop (phone would go through boot animation and load up the OS, then freeze, reboot, and repeat)
I tried going back to back to stock by using TWRP to restore my personal backup but it always went to bootloops. Same with the other backups on the forum.
As a last resort I tried using Mobile Upgrade Q 4.9.2 but the device wouldn't read my device (doesn't detect it).
Any suggestion on how to save this device? All that is working is TWRP so far.
seahavens said:
I have a 6045I
Originally I ran the Chinese ROM with no problems. Wanted to check out the CM beta so I did the standard procedure and followed in instructions on flashing. Found out I was constantly in a boot loop (phone would go through boot animation and load up the OS, then freeze, reboot, and repeat)
I tried going back to back to stock by using TWRP to restore my personal backup but it always went to bootloops. Same with the other backups on the forum.
As a last resort I tried using Mobile Upgrade Q 4.9.2 but the device wouldn't read my device (doesn't detect it).
Any suggestion on how to save this device? All that is working is TWRP so far.
Click to expand...
Click to collapse
The Chinese ROM screwed up your partitions, you have to flash the stock partitions (like I did) provided by @famewolf
fubugang said:
The Chinese ROM screwed up your partitions, you have to flash the stock partitions (like I did) provided by @famewolf
Click to expand...
Click to collapse
Yes, this fixed it!
Here's the post if anyone has the same issues http://forum.xda-developers.com/showpost.php?p=63272682&postcount=178
seahavens said:
Yes, this fixed it!
Here's the post if anyone has the same issues http://forum.xda-developers.com/showpost.php?p=63272682&postcount=178
Click to expand...
Click to collapse
Glad it worked for you. Now you can see just how fast your idol3 can fly under cm 12.1.
Hi guys, i have a completly stock OPO with CM13.1,
I never changed anything because personally I really like the CM roms, but now after learning that OPO will not be updated to Android nougat would like to install a new rom.
Browsing the forum I found the rom Tuga Power (http://forum.xda-developers.com/oneplus-one/development/rom-tugapower-0-2rc-t3463157) who seems to have a few bugs, is already updated to 7.1 and has all the features i love about CM (such as themes).
Now since I have never done anything like that (except the flash of some recovery of stock updates), I need a hand for backing up (a good app that makes me put EVERYTHING safe), for installation of custom recovery (TWRP?) and flash the new rom and related Gapps.
Thanks in advance
The backup you're looking for a is nandroid backup which can be made in your custom recovery. If you have TWRP, just boot into recovery, select backup, select all the partitions, then start the backup. It'll take a couple of minutes and the backup will be about 5-7~ GBs so make sure you haven't enough space. Another type of backup can be made with the app Titanium backup and it's available on the play store. Your phone needs to be rooted and you need to have busybox installed, but the app will make a backup of all your apps and their data.
After you install the ROM, do a factory reset in recovery, wiping all partitions except internal storage. After that, follow these steps:
1. Flash your preferred firmware (241 is generally the recommended one)
2. Reboot into recovery.
3. Flash your ROM, then immediately flash your GApps package.
4. Do a regular reboot. The first time will take a couple of extra minutes.
5. After it's done turning on, reboot regularly one more time.
And done!
I recommend draining your battery to 0 and then charging it to 100 ASAP to recalibrate your battery, as this will usually give you better SOT.
DurRice said:
The backup you're looking for a is nandroid backup which can be made in your custom recovery. If you have TWRP, just boot into recovery, select backup, select all the partitions, then start the backup. It'll take a couple of minutes and the backup will be about 5-7~ GBs so make sure you haven't enough space. Another type of backup can be made with the app Titanium backup and it's available on the play store. Your phone needs to be rooted and you need to have busybox installed, but the app will make a backup of all your apps and their data.
After you install the ROM, do a factory reset in recovery, wiping all partitions except internal storage. After that, follow these steps:
1. Flash your preferred firmware (241 is generally the recommended one)
2. Reboot into recovery.
3. Flash your ROM, then immediately flash your GApps package.
4. Do a regular reboot. The first time will take a couple of extra minutes.
5. After it's done turning on, reboot regularly one more time.
And done!
I recommend draining your battery to 0 and then charging it to 100 ASAP to recalibrate your battery, as this will usually give you better SOT.
Click to expand...
Click to collapse
I thank you for reply
I've just found this tool : http://forum.xda-developers.com/showthread.php?t=2499926 wich i think can be good for me, i can use this for install TRWP and back up ?
sgronkia said:
Hi guys, i have a completly stock OPO with CM13.1,
I never changed anything because personally I really like the CM roms, but now after learning that OPO will not be updated to Android nougat would like to install a new rom.
Browsing the forum I found the rom Tuga Power (http://forum.xda-developers.com/oneplus-one/development/rom-tugapower-0-2rc-t3463157) who seems to have a few bugs, is already updated to 7.1 and has all the features i love about CM (such as themes).
Now since I have never done anything like that (except the flash of some recovery of stock updates), I need a hand for backing up (a good app that makes me put EVERYTHING safe), for installation of custom recovery (TWRP?) and flash the new rom and related Gapps.
Thanks in advance
Click to expand...
Click to collapse
CM 14.1 is coming to OnePlus One (bacon) any day now!
Sent from my A0001 using Tapatalk
Elius2676 said:
CM 14.1 is coming to OnePlus One (bacon) any day now!
Click to expand...
Click to collapse
The Official COS, or CM branch ?
CM
Sent from my A0001 using Tapatalk
Elius2676 said:
CM
Click to expand...
Click to collapse
You think that will be better then Tuga ? Reading on forum i think Tuga is One of the best in terms of Battery/bugs/usability
I've not had a lot of experience with Tuga, so not totally sure. CM 13 has treated me well (except for this time last year when there was a pretty serious spontaneous rebooting issue due to a modern change). Other than that, this has been my exclusive daily driver for a year now.
I don't expect CM 14 to be daily driver material out the gate, but I wouldn't mind being wrong about that ?. We'll see.
Sent from my A0001 using Tapatalk
sgronkia said:
I thank you for reply
I've just found this tool : http://forum.xda-developers.com/showthread.php?t=2499926 wich i think can be good for me, i can use this for install TRWP and back up ?
Click to expand...
Click to collapse
Yes, this tool will work to flash TWRP. But you will have to do the backup yourself, as I don't believe that tool supports that function.
But personally, I will recommend you do these steps yourself, as you will learn more about your device and will be able to pin point any errors or to familiarize your self with the process in case a tool is not available in the future.
DurRice said:
Yes, this tool will work to flash TWRP. But you will have to do the backup yourself, as I don't believe that tool supports that function.
But personally, I will recommend you do these steps yourself, as you will learn more about your device and will be able to pin point any errors or to familiarize your self with the process in case a tool is not available in the future.
Click to expand...
Click to collapse
+1
Someone gave me that same advice about a year ago. It pays to learn how to use things like ADB from your computer terminal.
Sent from my A0001 using Tapatalk
Yeha i'm looking on YouTube for videoguides, seems not too hard, at least not harder than Kali wich i'm familiarizing righ now, my only fear is the backup, i Have no root and Titanium works with root , but for having root i need too go with Twrp wich needa to unlock bootloader that need wipe ...
Hello!
I could not find any other threads related to this issue, so my apologies if this is a "duplicate" thread
So I found my old Samsung Galaxy Tab 2 10.1 (Model GT-P5113 in Samsung ROM, identified as Galaxy Tab 2 in CyanogenMod) in a cabinet doing nothing, so I thought I would flash CyanogenMod on it and get some use out of it. And so I did; I flashed the nightly build of CM 13 in the "espresso wifi" image. Now, that worked just fine, but when I tried to flash open gapps (open_gapps-arm-6.0-nano-20161217.zip to be exact), I got some sort of boot loop; the device starts and gets into the App Preparer thing (pardon my ignorance) and begins preparing the google apps, and once it does all 16 apps, it starts preparing some other cyanogen mod apps, or at least I believe they are cyanogen mod apps, and then the app preparer just closes, and the boot animation restarts. If I wait long enough, it will once again get to the app preparer and begin flashing 2 apps, I could not see the first one, and the 2nd was the Google app. It would then begin flashing the cyanogen mod apps and then it would close, and the cycle would restart. I flashed Gapps right after flashing cyanogenmod; I did NOT boot into the rom upon installing open gapps. Does anyone know how to resolve this issue? I will provide more information if it is needed. All help is appreciated.
You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Sent from my espresso3g using XDA Labs
Lightracer said:
You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Click to expand...
Click to collapse
Hi, Lightracer, thanks for the reply! I did not boot up the tablet after installing CyanogenMod; however the same result occurs whether I flash it with or without a boot up in between (I needed to reflash CM multiple times)
What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Sent from my espresso3g using XDA Labs
Lightracer said:
What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Click to expand...
Click to collapse
Yes, I am using the right package; arm 6.0 nano with TWRP recovery
What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs
chompy33 said:
Yes, I am using the right package; arm 6.0 nano with TWRP recovery
Click to expand...
Click to collapse
which version of twrp??
smart-t78 said:
which version of twrp??
Click to expand...
Click to collapse
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)
Lightracer said:
What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
I think I wiped it, however, I may have not wiped everything that was required. I will try this and post back.
chompy33 said:
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)
Click to expand...
Click to collapse
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.
smart-t78 said:
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.
Click to expand...
Click to collapse
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!
chompy33 said:
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!
Click to expand...
Click to collapse
You could download the common twrp which works for every samsung galaxy tab 2 model. The newest version is 3.0.2-8 which is found on andi34.github.io under recoveries. This could be useful if you want to flash newer roms.
Sent from my espresso3g using XDA Labs