Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Lakilaulea said:
Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Click to expand...
Click to collapse
Try booting recovery and clearing the cache. But I really don't know if that'll work.
Otherwise you can trying factory resetting and restoring from one of your backups.
If that still doesn't work you could download a stock 4.3 image and flash it. Then restore your backup.
Sent from my Nexus 7 using xda app-developers app
theaftermath said:
Try booting recovery and clearing the cache. But I really don't know if that'll work.
Otherwise you can trying factory resetting and restoring from one of your backups.
If that still doesn't work you could download a stock 4.3 image and flash it. Then restore your backup.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i was rooted / open bootloader made a huge mistake re-locking the bootloader without backup lol duh:silly: so it wiped the whole tab went to 4.2.2 locked bootloader and non root. so i just ota updated to 4.3 re-installed any apps that i remember and google didnt automatically download. now i have a fresh system with no crap all over the place in the files and lots of storage ..... i will fill it with crap again lol but yeah now rooted 4.3 smooth as hell and fast as f***
Lakilaulea said:
Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Click to expand...
Click to collapse
try completely wipe your device, make sure you backup everything you need to the emulated /SDCARD and back that up onto your PC. Then do a fresh reinstall. Also check background apps, some malware might be the problem
chismay said:
i was rooted / open bootloader made a huge mistake re-locking the bootloader without backup lol duh:silly: so it wiped the whole tab went to 4.2.2 locked bootloader and non root. so i just ota updated to 4.3 re-installed any apps that i remember and google didnt automatically download. now i have a fresh system with no crap all over the place in the files and lots of storage ..... i will fill it with crap again lol but yeah now rooted 4.3 smooth as hell and fast as f***
Click to expand...
Click to collapse
Well there you go. I also made the mistake of relocking once upon a time.
Sent from my Nexus 7 using xda app-developers app
So I backed up all my stuff through Titanium Backup to Dropbox and did a factory reset. After reinstalling everything, I reboot the device. Now it won't get past the colored X. What do I do now?
Related
Sorry if this is in the wrong place. This is the first time I've posted.
I recently rooted my Epic 4g with the instructions here:
http://forum.xda-developers.com/showthread.php?t=770388
and then used the "update.zip method" to fix Clockwork Recovery found in this thread:
http://forum.xda-developers.com/showthread.php?t=782300
Looking back, I suppose that was somewhat redundant, but there is nothing to indicate major system damage to me yet.
However, I am having a rather annoying issue that's causing me a lot of stress. All of my apps have come unlinked from the app market. Titanium Backup's market doctor finds "no recoverable market link" and even after I relink them myself by re-downloading them in the market, they come unlinked in a matter of minutes. It's pretty annoying and I'm eager for a fix.
What would cause this behavior? Did I **** something up in the rooting process? Is there anyone else out there experiencing this? I will be so greatful to anyone who can help me solve this problem.
I'm beginning to regret that I rooted my phone in the first place, which is kind of pathetic. What did I do wrong?
If you are on any rom try reflashing it after wiping system data through clockwork if that doesn't work then try using odin. If the problem still persists your FINAL option is to take it to the sprint store
Sent from my SPH-D700 using XDA App
I unrooted the phone after I ran into big slowdowns in network speed and overall performance while trying to re-download all my apps for the third time and that fixed both my issues.
Thanks for the response, btw. I'm not running any custom ROM, just Stock 2.1.1, but I assume those options could still work, although It would result in having to download my apps agin, wouldn't it? Also, what would I say if I took it to the Sprint store?
The upshot of all this is that I still have clockwork recovery, so last night I made a backup of my non-root image to revert back to if I have the same problem next time I tempt fate and try the root again. That's how it'd work, right?
I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
JadedRescue said:
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
Click to expand...
Click to collapse
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
slogar25 said:
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
Click to expand...
Click to collapse
I definitely did defrost those apps.
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
If you really want the ota then why don't you try mattlgroff's utility here:
http://forum.xda-developers.com/showthread.php?p=39576818
It will return you back to completely stock with one click and then you should be able to take the ota and reroot unlock if desired
Sent from my XT907 using Xparent BlueTapatalk 2
RSD
vLegend said:
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
Click to expand...
Click to collapse
I tried using Mattlgroff's method (which i'm sure is fine for most) but seems to be geared towards linux users mostly, and I ran into some issues. I have always used RSD to get back to stock and never had an issue. Check it out How To Restore Stock Firmware on Razr M. This will hard restore your phone to the factory image, as well as unroot it, no need to unfreeze or reinstall bloat. It will also obviously erase the internal SD card contents so make sure you back those up.
Yeah looks like slogar25 and cliMAKtic are right. I tried a few more things and its not working. I'll do an rsd in the next couple days and try the ota again.
I'm going to try rsd sometime tonight, I'll let everyone know how it goes. Thanks for all the help!!
I like rsd too. The point is to return too stock.
Sent from my XT907 using Xparent BlueTapatalk 2
Same issue, stops 1/4 of the way through.
Flashing back to stock with the RAZR M utility 1.10 once my phone hits 100% battery (at 93% now). Will let you know if I can take the update after.
Keep in mind
RSD is great to get back to clean stock, but keep in mind that it will remove your root. After taking the OTA update, you will be running firmware v4.1.2. If you used MotoFail2Go exploit to root your phone originally you should note that the exploit apparently does not work for the updated firmware. Instead you should use motochopper, an updated exploit that works on 4.1.2 to root your phone, developed by Drjbliss over at Droidrzr.
I honestly don't care too much about being unrooted at this point anyway, having root wasn't doing too much for me. I managed to get back to the original stock ICS using RSD and everything worked out! Downloaded one update to 4.1.1, then the second update to 4.1.2, and everything went swimmingly.
Thank you so much for all your help everyone!
I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
kabads said:
I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
abaaaabbbb63 said:
Do you have an unlocked bootloader?
Click to expand...
Click to collapse
Yes - why? Can I download the data somehow using adb? What difference does this make?
Got the same problem on my Nexus 4, updated via normal Ota, unlocked bootloader and rooted.
Any solutions apart from a complete factory reset?
Sent from my GT-P3110 using xda app-developers app
kabads said:
Yes - why? Can I download the data somehow using adb? What difference does this make?
Click to expand...
Click to collapse
Well, you could make a nandroid backup. That way, you will have your data saved. After that, install a stock rooted 4.3 ROM and only restore data from recovery.
Or, Adb could work too. It would backup your data to your PC, and you could restore after you reinstalled the ROM.
I don't really know why, but many updates to 4.3 failed. That's why a data wipe is always recommended.
I always use Titanium Backup. It's very simple and easy to use.
I've used Nandroid before - not sure why I didn't think of it - thanks.
kabads said:
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
I had this exact same problam and was able to fix it without losing data, settings or installed apps.
My Solution:
Download factory 4.3 image and extract system.img. You need to untar the gzipped file and then unzip the included zip file to get system.img
Flash only the system.img and reboot. (fastboot flash system system.img)
When the phone is rebooted, root will be gone, but all installed user apps, data and settings should be preserved.
Background:
After the 4.3 OTA, my phone would reach the lock screen and receive notifications. Sometimes a call would make it through and I would be able to answer, but most of the time calls went straight to voicemail. Callmaster might have contributed to this behavior.
However, if I attempted to enter a pattern on the lock screen, the phone would immediately reboot.
I was rooted using SuperSU prior to the OTA. My Nexus was also affected by the issue were attempting to access the 4.2.2 Security Settings resulted in an error. I never got around to fixing that issue, but suspected that the 4.3 and 4.2.2 problem were related.
solution that worked for me: keep failing pattern until prompted to type in google account details to login, it then worked for me after that, no longer rebooting when unlocking
Since Lollipop 5.1, Android optimize the apps at every reboot (359 apps), it takes around 20 minutes each time. My phone is encrypted and it does that with or without SD card. Did anyone notice a similar behavior?
1) Tried to remove SD
2) Tried to clear Dalvik
No changes.
difto said:
Since Lollipop 5.1, Android optimize the apps at every reboot (359 apps), it takes around 20 minutes each time. My phone is encrypted and it does that with or without SD card. Did anyone notice a similar behavior?
1) Tried to remove SD
2) Tried to clear Dalvik
No changes.
Click to expand...
Click to collapse
On my phone a window shows up on a reboot that Android is optimizing apps, but it takes 3 sec. Your seems like you have just upgraded Android OS and it prepares apps for that. It could be that update didn't really go well. I have never encrypted my phone, so that could be something... If nothing helps, factory reset could work, but make sure that your sd card is decrypted before reset(if you have it encrypted too)
Same here, thought that xposed is the cause but it seems that other have this issue without root.
Sent from my D5833 using XDA Free mobile app
smardu said:
Same here, thought that xposed is the cause but it seems that other have this issue without root.
Sent from my D5833 using XDA Free mobile app
Click to expand...
Click to collapse
I did not have xposed when it began... I have root though
Charkatak said:
On my phone a window shows up on a reboot that Android is optimizing apps, but it takes 3 sec. Your seems like you have just upgraded Android OS and it prepares apps for that. It could be that update didn't really go well. I have never encrypted my phone, so that could be something... If nothing helps, factory reset could work, but make sure that your sd card is decrypted before reset(if you have it encrypted too)
Click to expand...
Click to collapse
The issue with encryption is that the recovery cannot access the data partition and so cannot fix file permissions which could be an explanation for the issue.
Though rarely it only optimize 1 app usually it's all of them...
Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony
I had root in 5.0.2 then went to 5.1.1 but had to use flashtool as the over the air update kept failing (because I had root? I undid root and still had the same problem).
So when 5.1.1 loaded I had the same issue you are having, and I found I couldn't get root so I flashed it again 5.1.1, still the apps optimising every boot.
So flashed it to 5.0.2 again, took root again. Rebooted and the apps still had to optimise again (far less apps though, like 170 compared to 350 on 5.1.1).
Do I flashed it back to 5.1.1 and now it seems to all work fine.
No idea what the issue was.
BTW I used the UK firmware for both versions.
Pyres said:
Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony
Click to expand...
Click to collapse
I already have this issue once. I don't reboot often, but I doesn't happen at each reboot...
Pyres said:
Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony
Click to expand...
Click to collapse
Actually this is the same as me, tries to boot ~2 min then reboot and optimize. I will try to reflash the zip pre-rooted.
I have had the same. I was on 5.0.2 with root. Updated to 5.1.1 with flashtool (as OTA no possible due to root). Had extensive battery drain and flashed back to 5.0.2 and then this boot problem. Only when I did a factory reset everything was fine again. I suppose clearing the cache/dalvik cache is not sufficient. Better to save all apps and data (Titanium backup for example), reset the phone and apply the update. Root with pre-rooted 5.1.1, then apply your backup ...
Brgds
omg
omg1010 said:
I have had the same. I was on 5.0.2 with root. Updated to 5.1.1 with flashtool (as OTA no possible due to root). Had extensive battery drain and flashed back to 5.0.2 and then this boot problem. Only when I did a factory reset everything was fine again. I suppose clearing the cache/dalvik cache is not sufficient. Better to save all apps and data (Titanium backup for example), reset the phone and apply the update. Root with pre-rooted 5.1.1, then apply your backup ...
Brgds
omg
Click to expand...
Click to collapse
That's what I did, solved the problem.
I've had this problem for quite a while. my phone is stock, unrooted. I have encryption enabled (required to get work email through Mobile Iron). I observe that this issue (double boot w/ optimize apps) starts after a software update. the only way I have resolved this is by wiping the phone completely and rebuilding my apps and customizations which is quite time-consuming. is there anyway to resolve this without wiping? And for the 1st time, the issue came up just last week but this time there was no software update that preceeded it. is this really just a fact of life when using Android with encryption enabled or is this just an Xperia-specific issue?
I have the same issue on my work issues Xperia Z3. 20 minutes per reboot. It's brutal. Not a good look for Android.