I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?
I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?
iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!
lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.
Related
Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo
OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.
Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......
What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...
I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.
bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.
I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.
I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk
No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.
movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
rvenes said:
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
Click to expand...
Click to collapse
Yes, that can be the reason.
_that said:
Yes, that can be the reason.
Click to expand...
Click to collapse
LOL
Yes, that and wrong recovery, no or insufficient wipes before flashing the new rom - lots of possibilities.
Before you fire into the trash send it to me! I could use a tablet to recklessly experiment on
rvenes said:
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
Click to expand...
Click to collapse
No trash! The TF700 is an awesome tablet.
I would start over. Go to the Zombi-X thread and install that rom, *after* making sure you've got the boot loader mentioned in the first posting in that thread. Then, install TWRP (the latest version rather than the 2.6 one mentoined in the thread -- I think it is up to 2.8.01 or so). Then install Zombi-X. If you have an external micro-sd card, go for the ROM2SD install as well. If not, no worries. You'll be so glad you did. But again, the Zombi-X thread will step you through the entire process. They've done a fantastic job. And your tablet will impress.
I haven't had time to look at it yet! So many other gadgets to use.
Will find time sometime this xmas.
If you were on CleanROM, you're bootloader is probably way too old.
Also you HAVE to do a clean install = wipe of cache, Dalvik and data before installing a new rom.
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?
I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..
I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.