I was attempting to use Titanium Backup to prepare for a ROM flash, but unfortunately, every time I try to start a backup, the device goes into "Cool Down Mode" (essentially Airplane Mode + closing apps). This, however, kills Titanium Backup, and when I try to use the device afterwards, the "Cool Down Mode" prompt will keep appearing until I reboot. The case of the phone is cool to the touch when this happens, and I've had the cover become unbearably hot after playing games in a hot car, and all it shows is an "overheating" icon, but no Cool Down Mode. I've looked at other ROMs, which might be able to fix the problem, but I can't really use them, because my stuff is not backed up...
Has anyone else had this problem or a similar one, and knows how to fix it, or at least a possible cause?
Thanks in advance,
<LONGSHOT>
First update your ROM to Gingerbread or ICS, Froyo is too old to be supported properly
Related
Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.
well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.
2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.
I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?
yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.
Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.
Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.
try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...
just a quick one, my X1 with standard software has started to randomly reboot which is getting on my nerves!
Its also losing new messages when it does this. so any ideas before I test its bouncability on the wall
If you have installed an app recently, or can pinpoint something you've done, try to uninstall/undo that.
I would personally hard reset (search on the X1 board for the how to via the hardware keys, or just choose Clear Storage from the Settings/System menu).
Make sure you've at least sync'ed all your data to your PC first. Then connect back up, and contacts etc will be restored.
If you haven't already, try SPB backup (or Resco's , or Sprite's) - they are all time-limited trials so no problem with a quick backup-restore sequence. You can choose just about anything to backup from your device with these.
If you're feeling adventurous, consider trying one of the more popular ROMs, you won't look back!
I've tried the custom ROMs in the past but decided to go back to stock.
Already hard-reset it and was still doing it, and now I've gone to update it (its back to stock) on the SE update service and its still rebooting.
Its now stuck on the four colour screen!!! I am really hating this phone
I've now managed to get the Stock ROM on but when it comes to installing the Stock SPL both my pc brings up a blue screen (never done before) and phone dies again.
I've also noticed when I clear storage it turns off but won't come back on, only way it does come back on is by removing the battery
Any help guys??
mine kept doing this. Sent it to SE and they replaced the mobo.
yeah gone today, see what happens
Had same problem while using stock and custom roms . Then i searched xda for stable & fast rom and i did it. Not advertise but i really like 826x rom =)
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
Wonder if you guys could help me.
I've been using Froyo 2.2 on my Galaxy S for a while with no problems, upgraded through Kies.
All of a sudden today the screen stopped being responsive - ie I could swipe to unlock it but then the screen was that slightly grey/dull colour as if the screen was about to turn off. The touch screen basically became unresponsive with the only button that worked being the main home screen button, which would switch between the zoomed out view all of my homepages and my main homepage. Didn't think much of it so rebooted the phone (also I haven't installed any new apps or made any big setting changes lately).
However, when I rebooted apps like Titanium Backup, LaucherPro, NetCounter, Handcent etc kept force closing automatically making the phone almost unusable. I've tried restarting the phone, taking the battery out but to no avail. I then managed to switch to the default samsung launcher and reinstall some of the problem apps which sort of helped, but the more apps I try the more I find just crash upon starting.
What's the best way to solve this problem, preferably without loosing all my data/settings?
Seems like something has become corrupted, and I'm a bit worried this has happened so out of the blue....
Really don't want to have to a factory reset if possible, but looks like I'll have to
i think wiping the cache may do the trick, it happened to me after installing new theme. couldnt even use it for 5 mins to back up my stuff. i wiped the cache in recovery and that fixed it.
I tired wiping the cache in recovery mode but didn't help much (other than allowing me to use TWLauncher, and hence being able to semi use the phone).
Don't have a backup either , mainly because since upgrading to 2.2 I can't get any rooting methods to work oddly.
Could be in a for a long evening....
What really gets me is that it just happened randomly. I just tried to use the phone after it was in standby and it just wasn't responsive - after the reboot the force closing apps problem occured. I wasn't trying to install anything, bit worrying really.
i think the only way to get back to normal is a factory reset. i dont personally know any other methods. but its upto you to wipe the phone or keep searching for a solution.
the cause is probably through some sort of corruption or wrong setting in an application, i wouldnt panic about the phone dying or anything lol, just a ball ache restoring everything..
Hope you get it sorted remember to make a backup when its fixed. i make backups on a weekly basis as im constantly flashing and modding, and it makes life soooo much easier.
azzledazzle said:
i think the only way to get back to normal is a factory reset. i dont personally know any other methods. but its upto you to wipe the phone or keep searching for a solution.
the cause is probably through some sort of corruption or wrong setting in an application, i wouldnt panic about the phone dying or anything lol, just a ball ache restoring everything..
Hope you get it sorted remember to make a backup when its fixed. i make backups on a weekly basis as im constantly flashing and modding, and it makes life soooo much easier.
Click to expand...
Click to collapse
Yeah I had a feeling that was going to be the outcome , ah well!
I normally do backup, just I haven't been modding or flashing much lately so assumed android wouldn't just die on me! Lesson learnt, always backup!
The phone is still usable, so I should be able to do a backup of my apps.
if you can still do backup... all is not lost then.
I decided to do a reboot just to have a fresh start after adjusting some app. The phone was stuck at the flashing Darky logo for indefinite amount of time. After a minute or so of flashing logo, phone vibrates shortly and continues flashing the logo. That repeats each minute.
Taking out the battery and retrying didn't help, same thing.
In the past 48h since last boot, I've installed a bunch of apps, mostly games, so it's natural to look for a culprit among them. However, right now I can hardly do anything with the phone. I can access the recovery menu, download mode probably as well and that's it.
I'm ready to flash the Resurrection Edition, but first I'd like to exhaust other options for fixing the problem or at least backing up everything I can. I have partial backups but would very much like to access the latest changes that weren't backed up.
My questions are:
1) Is there some kind of boot logging that I could turn on, access and which would point to the problem? I'm comfortable using ADB if it's needed.
2) I did a CWM backup. What did it backup? Primarily, what about contacts, SMS messages?
3) The most important question: If I reflash the ROM and then use CWM restore, will the problem repeat itself? (If an app is the source of the problem and all apps are backed up and then restored, I'm afraid the problem won't go away. I see few big image files in the backup folder which suggests that everything will be restored as it was. Bootloop too?)
Additional hints for experts on what might be causing the problem:
There are only two incidents that come to mind.
First is that I did a wipe flash of darky 9.1, then a regular flash of 9.2. After I discovered my GPS simply doesn't work on 9.2, I did a regular flash back to 9.1. This was about 2 weeks ago. Is there something in this procedure that might leave some problems that would show up in the future?
Second thing is a incident I had 2 days ago (the time last reboot was done and last time I've had a successful boot).
I left the phone ON over night, and in the morning found it turned off. I thought it might be a dead battery so I plugged it in. It wouldn't start for few minutes but then booted normally.
During that day I found it OFF one more time, for no apparent reason. This time battery was nowhere close to low. It turned off while in standby/locked screen mode so I can't say that it was doing anything in particular.
(Even the turning off during the night is suspect. It had sound on, it was near my head, and I'm sure that low battery warnings would wake me up. It might just be the case it turned off for no apparent reason like it did during the day.)
i think, that when you flashed 9.1 over 9.2, it could leave some weird things, because everyone is talking bout updating, and no-one even think about downgrading rom.
Answer 1. If you used SpeedMod kernel, I think you can turn Logging in Tweaks Menu at RM, and start phone with plugged USB cable to computer (running adb).
Dunno bout other kernels.
Darkyy normally turned off logging, because ROM was bit faster without it.
Answer 2. Probably contacts were synced to Google (contacts.google.com) <--- try it
I think SMS messages are backed up together with whole ROM (contacts too).
Answer 3. Probably yes, problem will repeat. I don't know but maybe there is some way you can restore only some things, not whole system.
I think you should make "Backup Everything" in CWM, then try flashing 9.2 again.
Weird that GPS were not working there.
It seems something bad was happening that caused random reboots.
What apps that require root, you were using? Swapper, Galaxy Tuner, Overclocking?