Related
However ironic the title may be, I updated my fiance's non-rooted N1 to the official release froyo and from the very beginning, it will work for a few seconds, then it will just freeze for a few minutes. I have patiently gone through and stopped almost every process, and nothing will fix it. It still just freezes constantly and usually requires a battery pull to get it to work at all. I told her she could try a factory reset, but she would rather just go back to 2.1-update1. I'm going to try renaming 22607-ERD79-update-nexusone-stock-signed.zip (or PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip) to update.zip and reflashing it in the stock bootloader on her phone, but I feel like that won't work because it is a previous version and not really an update. Does anyone have any advice on how to just bring her back, or perhaps how to fix her freezing problems on froyo?
Thanks
Try a fresh flash with no apps installed and see how its doing.... if it doesn't freeze then its a app probably ...
I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.
dnoggle said:
I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.
Click to expand...
Click to collapse
Just do a factory reset in settings and security ... no reflash. Just cause a app didn't freeze 2?1 doesn't mean it wont freeze 2.2. And even if the apps currently not running or closed, it'll still wack ya phone. I had a freeze every hour yesterday with my chosen apps installed, flashed 3 different times to no avail. Now I factory reset with only 4 definitely needed apps installed and haven't gotten a freeze yet. So my conclusion is 2.2 doesn't like something I've installed so I'm adding a few apps every hour to fins the cause.
Since I factory reset with my few apps. I haven't had a freeze yet all night and morning long..
I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?
Papa_I said:
I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?
Click to expand...
Click to collapse
Have you tried a factory reset? That might fix it... let us know what you find. I've noticed a couple of freezes as well, but I'm not able to factory reset it just yet because I'm out of town and don't want my phone down for even half an hour.
I have to pull battery a couple of times a day.
I'm having the same issue on 2.2. I have done 2 factory resets. Nothing. N1 call center said slowly reinstall all apps to see if an app may be doing it. No luck.
Is anyone having issues with the screen still being responsive while on a call? My screen will go black but you cant still hit keys when you have up against your face.
I'm betting that you do not have a custom recovery and nandroid backup, or you wouldn't be asking.
I highly doubt that the phone will let you push the old firmware on top of the new one if you don't have a hacked recovery and a test-signed zip. But I don't know - you could try it...
Here is what I would do:
1. Install a custom recovery (like Amon-Ra 1.7.0.1), either by unlocking the bootloader, or by following the directions in the dev forum for doing this without unlocking if you have the fear. If you already a custom recovery, don't worry about this step.
2. Now boot into recovery and make a nand backup!
3. Now go ahead and try this one of two ways - either delete one application at a time until you figure out which one is killing you, OR do a factory reset and then re-add one application or a small number at a time until you figure out what is crashing you.
If it were me, with my 100 applications, I'd probably add 5 or 10 at a time. Once you get crashes after one group, try removing those applications one at a time until the crashes stop. The last removed app when the crashes stop should be the answer.
Of course, since you'll have to have adb running to get a nandroid, you could also just take a logcat of the running, crashing phone and see what app is killing it there.
I did a factory reset today and will report back letting everyone know if that has fixed the issue. Everyone else that is experiencing the freezing issue, did you have Beautiful Widgets installed?
I have that installed, is that whats cousing it?
Beautiful Widgets was killing my N1, too. Freezes, sluggishness, etc. I uninstalled and wiped my cache via stock recovery. No problems since.
I'm on stock FRF91 BTW.
Sent from my Nexus One using XDA App
It appears that's the root of my issue. I would uninstall the application and clear the cache and see if that helps. Report back with your findings.
Sent from my Nexus One using XDA App
I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.
next time something like this happens use adb logcat to figure out what is actually going wrong
exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )
Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.
exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
I know there is a lot of information on this, however my problem appears to be a bit more chronic all of a sudden. If anyone has any idea what this is (especially if it is a possible hardware issue), I would really appreciate it.
This started the past weekend and has been driving me crazy ever since. After uninstalling facebook on Saturday, I got the pop up. Rather than messing with trying to fix it, I went and reflashed the rom. While restoring all my apps, the error popped up again. Convinced there as something up on the phone or the sdcard file system, I restored back to stock 4.4.2 with odin. I rooted, went through the same restore process and after one of my reboots, it came back. Finally I searched and did "restore app defaults" in the application manager. That worked for a while, but came back a few times, until finally that method wouldn't fix it anymore.
Last night I reflashed with odin again. This time I didn't root. Everything was fine all day until I decided to uninstall twitter and the acore message is back. Doing an app reset did fix it again, however I am afraid at this point to reboot the phone or do anything else.
I had this problem maybe once about 3 months ago, now I can't get ride of it no matter what I do. I should also point out that I did not do a TiBu restore or anything, I installed all my apps through the play store.
Thanks in advance guys
Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message
majortaylor said:
Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message
Click to expand...
Click to collapse
I did that, however it usually didn't work. I had to reset all application defaults and the issue usually went away. During one of my reflashes, even that didn't work anymore.
Seems like the issues started when either I turned off one of the bloatware apps, or deleted something. Sometimes the acore would start right away, other's after I rebooted the phone.
This last time, I got the phone setup, I got 2 acore's early on (Clearing app defaults worked both times). I didn't do anything else to the phone for a few days. Last night I finally rooted, installed safestrap and my other root apps and so far everything seems stable. I will just do a twrp backup before removing anything in the event things go bad again.
What still bothers me is don't know what caused this all of a sudden. I've been flashing roms for years and never once had this sort of problem. I will all set to consider this a hardware issue, until it finally settled down.
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
are you using a custom kernel?
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
Did you change your Android password within the past 72 hours?
cam30era said:
Did you change your Android password within the past 72 hours?
Click to expand...
Click to collapse
Nope...
its not that i just cant connect, its like the hardware is broken.
and just did a complete factory image flash.
still broken
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
hackahero said:
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
Click to expand...
Click to collapse
First contacted square trade as that is my insurance, they said contact Moto because it is still under warranty. Did that, Moto said they would replace it. I said i don't want to go without a phone and they said they can charge me 25 and put a 500 hold on my account but they would send the phone first. Said OK phone arrives on Tuesday.
Just as an FYI they did basically say did you factory reset it.... but that is all the trouble shooting.
If anyone is interested in my symptom. Wifi is just always stuck at "turning on" every once in a while it will be off. but when you try to turn it on it just gets stuck again.
When it is stuck you can not turn it off.
paulwoodhouse said:
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
Click to expand...
Click to collapse
Might be worth an RMA. see my previous post.
Don't know if I'm a little too late to this post... .But it happened to my Nexus 6 too, tried everything, wipe cache, factory reset, root, delete /persist/wifi but nothing worked....
However, luck seems to be on my side when I went into Google Connectivity Services under Setting--> Apps... and wipe its cache and tried to disable it (but stopped before I did). Then reboot the phone once i wiped all the data from the Google Connectivity Services Apps and VIOLA! It's working now!
*EDIT... It worked for about an hour (allowing me to dl all the apps) but now it has failed again....
I have the same issue as soon and I unlock the bootloader
any ideas? Im going to root again the device and load a different to see if it makes any difference
I am experiencing this as well. Was working fine yesterday and when I tried to go to Android M Preview 3 this happened. Whats worse is that this is happening right after I switched from Unlimited Data on TMo to Project Fi with 3GB. Making this even more frustrating is that Project Fi support says the preview images are now compatible with Project Fi. Isn't that something they should be telling people up front?!
I'm having the same issue on marshmalow, it suddenly started to happen some weeks ago.
First times was solved with phone reboot.
Then was required to clean cache before restart
Now I've tried reclutance suggestion (delete data from google connectivity services and reboot but the problem persist?
I'm using 6.0.1 stock rom without root
I don't want to perform a factory reset
Any suggestion?
here too...close the wifi
All tried doesn't work,
Wipe cache
Wipe dalvik cache (via fastboot as I do not have a custom recovery neither unlocked the boot or root, my phone is completely original)
Also tried to delete wifi data
Any suggestion?
RMA
I'm continuing to have issues with my Motorola Nexus 6 phone.
It is running stock android 6.0.1
I never unlocked it or rooted (Sadly cause If i do so I were able to backup my apps and settings with titanium backup and restore it before a full device reset )
The problem started some weeks ago.
First symptom was that i was unable to enter on Settings -> Data usage (Every time receives an "unfortunately, settings has stopped" message)
Then some days have difficult to connect to wifi or disconnect (at that moment I didn't investigate the issue, just retry considering the issue was on router side)
After some time I realize that the problem was on the phone, specially cause it started to stuck turning on wifi, but for some days just turning off phone and turning it on again solves the issue.
With the time it becomes more and more frequent and turning it off and on didn't solve anything so I've reboot into recovery mode and perform a clear cache but it doesn't solve the issue.
Looking here and at other forums found that this issue is really common and some people solves it trough ADB with "adb shell pm clear com.android.settings" I've tried it but it didn't solve anything.
Even when many people didn't solve it with a factory reset I want to try it, but I need to be able to backup one app data (If could backup everything will be the best but at least need to backup blockchain app (Also have an issue with them as provider and couldn't log in from another device or website, just this device has a session already approved and open)
Any suggestion?
I've upgraded/downloaded to almost any possible rom and the problem is still here
Looking on forums found that is a very common issue since marshmallow in many devices (Specially Nexus)
Most people couldn't fix it but some could.
the problem is with devices macaddress that shown 02:00:00:00:00:00 and get stuck turning on
there are solutions in forums that seems to be a little bizarre like drain battery to 0 and full recharge (This one works for me once)
,others like deleting Google connectivity services cache, or deleting /persist/wifi folder completely
But I found one for nexus 5 who replaces the full /persist partition with a dump and edit the files and permissions with macaddress information.
This seems to have logic and provides an explanation about why the problem persist after, factory reset or rom changing so I want to try it in nexus 6.
Could someone provide me a dump of it?
There is an app: https://play.google.com/store/apps/d...nam.partitions, that makes the process of making a partition backup easy. The persist partition is on /dev/block/mmcblk0p26
Thanks in advance
Did you solve your problem? Because I have the same. Did you try to change Mac address on device?