Good evening,
My phone (T-Mobile Note 4 on stock 4.4.4, rooted) worked just fine until I froze an app I shouldn't have. When I boot up, everything loads just fine, about 20 seconds in, I get two quick vibrations, and I'm back to a "Samsung" startup screen; the process repeats ad infinitum. I attempted dirty flashing the stock ROM, as well as restarting the phone in safe mode, but it still does the same thing. I'm reasonably confident that if I defrost apps (all of them if need be), the phone will stabilize, but the window of opportunity between boot loops is too short to do so within Android.
Is there a way, within TWRP (or another recovery environment), to defrost apps? Since TWRP is still functioning fine, I am thinking that this may be repairable in the recovery environment...or am I stuck doing a full wipe and restoring data using TB or similar?
Thank you for your consideration.
Joey
voyager529 said:
Good evening,
My phone (T-Mobile Note 4 on stock 4.4.4, rooted) worked just fine until I froze an app I shouldn't have. When I boot up, everything loads just fine, about 20 seconds in, I get two quick vibrations, and I'm back to a "Samsung" startup screen; the process repeats ad infinitum. I attempted dirty flashing the stock ROM, as well as restarting the phone in safe mode, but it still does the same thing. I'm reasonably confident that if I defrost apps (all of them if need be), the phone will stabilize, but the window of opportunity between boot loops is too short to do so within Android.
Is there a way, within TWRP (or another recovery environment), to defrost apps? Since TWRP is still functioning fine, I am thinking that this may be repairable in the recovery environment...or am I stuck doing a full wipe and restoring data using TB or similar?
Thank you for your consideration.
Joey
Click to expand...
Click to collapse
Recovery still functions because that's what that is, a way to 'recover' your phone. That said, if you used TiBu within your ROM to freeze an app, that's how you defrost it. I would imagine you are stuck doing another install. That's what I did when I made those mistakes with TiBu.
Basically you can't really run apps in recovery, you run zips that add and remove things to different positions.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Recovery still functions because that's what that is, a way to 'recover' your phone. That said, if you used TiBu within your ROM to freeze an app, that's how you defrost it. I would imagine you are stuck doing another install. That's what I did when I made those mistakes with TiBu.
Basically you can't really run apps in recovery, you run zips that add and remove things to different positions.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I know the recovery environment is a bit of a different animal; I certainly wouldn't expect TiBu to do the job. More what I'm getting at is, the way I understand how app freezing works (and it's entirely possible that I'm wrong in this regard), it effectively sets its chmod to 000, so that the file system prohibits the binaries from being able to be accessed. If it's a matter of recursively running chmod on a particular directory, I know that TWRP makes it possible to run terminal commands, so it would be a matter of running a 'chmod 755' on the correct folder to ultimately do a defrost, which can be done from a shell prompt.
That's more the thought I had, though I'm about ten minutes away from saying "screw it" and reflashing...but I'd rather not, if at all possible.
Joey
voyager529 said:
I know the recovery environment is a bit of a different animal; I certainly wouldn't expect TiBu to do the job. More what I'm getting at is, the way I understand how app freezing works (and it's entirely possible that I'm wrong in this regard), it effectively sets its chmod to 000, so that the file system prohibits the binaries from being able to be accessed. If it's a matter of recursively running chmod on a particular directory, I know that TWRP makes it possible to run terminal commands, so it would be a matter of running a 'chmod 755' on the correct folder to ultimately do a defrost, which can be done from a shell prompt.
That's more the thought I had, though I'm about ten minutes away from saying "screw it" and reflashing...but I'd rather not, if at all possible.
Joey
Click to expand...
Click to collapse
I see what you mean, I tend to forget that because I go the 'up it' route and clean slate it. I've done a ton of freezing and deleting the wrong apps on many different phones. And being the tire of person that used to flash a new ROM every three days, never really bothered me.
Sent from my SM-N910T using Tapatalk
aaldiar said:
I see what you mean, I tend to forget that because I go the 'up it' route and clean slate it. I've done a ton of freezing and deleting the wrong apps on many different phones. And being the tire of person that used to flash a new ROM every three days, never really bothered me.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I loved being able to do that. The reason I've gotten more wary about reflashing ROMs is the fact that I've got about 62,000 text/MMS messages now. I'd like to keep them, but thus far I haven't found an app that will do some sort of "autoarchive" app function where my 200 most recent texts are treated normally, but the rest are stored in an independent database which itself works similar to the 'online' UI. Resultantly, my restore operations take 5-6 hours, and because Google has thus decreed that only one SMS app can write to the database at a time, I'm stuck keeping my phone in airplane mode during that time, otherwise texts that come in will be delivered to /dev/null...so ultimately, if /that/ problem can be solved, I'd love to get back to being able to be flash happy again. At this point, though, I'm clearly stuck...but if anyone else can chime in, I'd greatly appreciate the knowledge!
Joey
voyager529 said:
I loved being able to do that. The reason I've gotten more wary about reflashing ROMs is the fact that I've got about 62,000 text/MMS messages now. I'd like to keep them, but thus far I haven't found an app that will do some sort of "autoarchive" app function where my 200 most recent texts are treated normally, but the rest are stored in an independent database which itself works similar to the 'online' UI. Resultantly, my restore operations take 5-6 hours, and because Google has thus decreed that only one SMS app can write to the database at a time, I'm stuck keeping my phone in airplane mode during that time, otherwise texts that come in will be delivered to /dev/null...so ultimately, if /that/ problem can be solved, I'd love to get back to being able to be flash happy again. At this point, though, I'm clearly stuck...but if anyone else can chime in, I'd greatly appreciate the knowledge!
Joey
Click to expand...
Click to collapse
HA! What a coincidence! I use evolve sms. I backup my texts regularly to the cloud. I use Dropbox but it also allows google drive.
As far as archive goes? It allows you to delete the previous backup add you upload. I don't know if it archives recents vs everything. I delete the backup every time I upload the latest.
Sent from my SM-N910T using Tapatalk
Related
I might be a senior, but we're all still learning
So my question is, when you wipe/reflash something, is there a way to keep all the Protected/Paid apps installed when you start up? Normally, a wipe will break all of your protected/paid apps and list them in the launcher as "com.XXXX.XXXX" or even "org.XXX.XXX". Launching them results in the infamous Force Close box.
This is indeed on Apps2SD and with Cyan's new 3.9
Have you tried running the fix_permissions script?
I'll reboot and run it now
Didn't fix them, unfortunatly :/
lukekirstein said:
Didn't fix them, unfortunatly :/
Click to expand...
Click to collapse
Back up all your apps using MyBackupPro or Backup for Root Users. I have all mine on my sd so they re-install automatically. I don't have to do anything, and they don't load up as com.xxxxx.htc.. blah. But I use Backup for Root Users when I do have to format my ext2 and this brings them back no problem.
Hmm interesting. I've never used Backup for Root Users with apps, just the data. Takes too long for me with all my apps...but I managed to find the spare time to re-install, that was fun . Thanks guys!
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
kusotare said:
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
Click to expand...
Click to collapse
Wouldn't hurt to have a backup unlocked GSM phone too. That's one of the nice things about GSM-based technologies... if your phone dies for whatever reason, pop the sim out and put it in a backup phone. You'll still be able to be contacted while you fix the primary device.
I had this issue too with the same Rom and with the previous version. This is how I solved it.
First I deleted all apps, etc from my SD card while it was connected to my Mac, just made it easier. (I was also running a previous Apps2Sd, not the one built into the mod, which I believe was the root of the issue. I didn't use the old apps2sd once I upgraded the ROM, and I may be way off but I find it suspect.
Then I wiped and reinstalled the ROM. Yea I had to reinstall my apps but...
...before doing all that I had tried removing and then reinstalling an app. A reboot/power cycle of the G1 would result in the icon being gone again and that ugly error message in regards to the app.
When I did the step I mentioned prevously, delete, wipe, etc I've not had any further issues.
I've also since updated by fs from ext2 to ext3 but that was after the fact.
Cyan's mod is by far my favorite and consistently stable and well documented. I'm glad I was able to correct my issues.
kusotare said:
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
Click to expand...
Click to collapse
Have to agree completely with the above. Hope for the best but plan for the worst.
lukekirstein said:
I might be a senior, but we're all still learning
So my question is, when you wipe/reflash something, is there a way to keep all the Protected/Paid apps installed when you start up? Normally, a wipe will break all of your protected/paid apps and list them in the launcher as "com.XXXX.XXXX" or even "org.XXX.XXX". Launching them results in the infamous Force Close box.
This is indeed on Apps2SD and with Cyan's new 3.9
Click to expand...
Click to collapse
Did you manage to find a solution to this problem? If you did, could you please post it. I flash different ROMs often. Having to reinstall my paid apps over and over again is starting to get very annoying.
Haven't tried yet. I might try the MyBackup Pro option, as I heard it's a great app anyways. But I know what you mean
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
Hi:
I have installed the JH7 update found here on xda. My phone is rooted with sideloading enabled. I will be honest, I have a ton of apps on my phone.
I have had SO many problems since the update. I had to re-install the update 3 times, because after HOURS of trying to enable sideloading it still wouldn't work. After the third install I was finally able to enable sideloading.
Now, my problem is, some apps are crashing as soon as I open them. The 2 biggest culprits are e-mail, and Shop Saavy. I click to open them, they open for between 1-5 seconds, then close.
Any thoughts? I am desperately trying to find an answer, I would hate to have to hard reset, since I have already spent in excess of 10 hours trying to get my phone to where it is now.
I did have task manager installed, but the problem persists even after uninstall. Also, I used task manager prior to the update with no problems.
Thanks so much!
PS: If I do have to hard reset, can I simply use Sprite backup to restore everything, or will there still be some things that need configuring (ie. home screen etc)?
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
a.n said:
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
Click to expand...
Click to collapse
Hi:
I tried your suggestion, but sadly, it didn't work
Thanks so much for your suggestion though!!
PS: The apps just close, I do not get an error message. I have found some posts with people with e-mail crashing issues, but it seems that they do get a force close message, and that it is Exchange related. I do not use exchange.
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
swedishcancerboi said:
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
Click to expand...
Click to collapse
Hi:
Sorry to be a dunce, but how do you reflash just the kernel, and will it delete everything (apps, data etc)?
Thanks so much!
My 2 cents:
I don't know why it took hours to enable sideloading, i spent only a few minutes - but that gives me the impression that something might seriously be broken.
I would back up everything you want to save and do a master reset - it will clear all data, but you hould be JH7 fresh. If you want to go further, you can reflash factory JF6 then update to JH7. Either way, make sure you check basic apps first before installing a bunch of stuff.
I don't subscribe to the blind grasping at straws method of fixing things. After to many hours it is just faster to rebuild. If you knew what was wrong, then fix it, but if you don't then rebuild.
I agree. If you are needing this to function properly now, then just reset back to factory and start over. But if you are like me and just have to know what is broken.....that could take a while. I always try to make sure I don't have anything on my phone I couldn't live without just for instances like this.
Flashing just the kernel can be done with Odin (search the forum). There is a "stock captivate kernel" floating around (I'd post it, but I'm sure we don't need files posted multiple times). Instructions are included in that post. Basically you need a computer, USB cable, drivers, and bollocks. However, as mentioned, this is a shot in the dark. Random force closes could be caused by a variety of issues ranging from corrupt software, file system inconsistencies, to hardware failure, phase of the moon, appetite level, etc....
The safest bet is to backup everything, flash stock (if needed) and take it back to AT&T for a replacement.
Good Luck!
Hi:
Thank you so much for the replies, and help.
I decided to go ahead and reflash JH7. This has fixed the entire problem. So, apparently it was software related.
I am now going to install all my apps one at a time, in order to find the culprit. Hopefully it is one I can live without lol.
Anyway, thanks again!
Did you ever figure out what app was causing this? I am starting to get annoyed with my force closes and was going to re-flash and re-add all apps.
Hi:
Well, I MAY have figured it out. I had a million programs installed, and it just seemed like too much work to try to figure it out.
So I just re-installed JH7, and started from scratch, so I'll never really know what the problem was.
However recently I started having the same problem again. Since I started from scratch I have been gradually installing programs, just in case one cased a problem.
Well, it seems my problem was Startup Manager. I did NOT disable any system programs etc..., but it was still causing apps to crash, as soon as I froze it with Titanium Backup Manager, the problem stopped.
So, if you happen to be using Startup Manager, I would try uninstalling/ disabling it. Or, if you use a task manager, try not using it, maybe it is stopping whatever Startup Manager was disabling on mine.
Anyway, I hope this was of some help.
Oops, sorry, the program causing my troubles is actually called Startup Auditor.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, this is getting really, really annoying because i have to wipe data every 1-2 days, luckly i have Titanium Backup...but i can't keep doing this forever!
The issue started using Eclipse ROM, i was using Holo Locker, and one day the phone refused to unlock...i clicked every bloody button on the phone, i tried everything, and i got something only plugging it to a PC... the screen turned on, and what i saw was disheartening: The wallpaper was gone, it was black, and the touchscreen wasn't working...rubbing here and there i managed to make the touch working and managed to unlock the screen...but it didn't unlocked it just stayed...black! Totally surrended to my phone, i wiped everything and patiently i reinstalled some apps... and then it happened again! I initially thought that the issue was caused by Holo Locker, but i was wrong because stock locker was stuck too..but it was messed up, with some elements shifted a little lower...and this time, it didn't unlock!
As of now, i tried this with 3-4 Gingerbread ROMS, SBF'd 2 times, and nothing changed...sometimes, it just freezes...here are my guesses:
- Something messed up with phone itself (dunno what could be, maybe something that didn't get involved in flashing ROMs and SBFing?)
- Something stored into Google Backup (probably, it's this too, because i noticed that if i choose to put backups on the phone, at startup, it freezes after a very few minutes)
- It's something involved with the kernel, because it doesn't happen (for what i tried, it didn't) on ICS/JB ROMs
- I thought it was launcher's fault, but i tried multiiple launchers and it didn't worked anyway so...
Any guesses guys?
This doesn't happen to me, so I'd say it's either the phone or perhaps it's one of your apps. An interesting experiment would be to run the phone stock (i.e., install no apps, do not restore from Google during setup, though Google calendar, contacts, Google+, GMai, etc., sync should be ok) and see if you can get past where you usually see this happening. If so, then it's probably one or more of your apps. So, at that point, rank your apps from most to least important, and then install them in batches of 5 or so apps. If the freezing happens again, then maybe you narrow it down to one of those 5 apps.
Which SBF have you been using?
doogald said:
This doesn't happen to me, so I'd say it's either the phone or perhaps it's one of your apps. An interesting experiment would be to run the phone stock (i.e., install no apps, do not restore from Google during setup, though Google calendar, contacts, Google+, GMai, etc., sync should be ok) and see if you can get past where you usually see this happening. If so, then it's probably one or more of your apps. So, at that point, rank your apps from most to least important, and then install them in batches of 5 or so apps. If the freezing happens again, then maybe you narrow it down to one of those 5 apps.
Which SBF have you been using?
Click to expand...
Click to collapse
Yep, already done this, i ran the phone as stock, but nothing happened, now i flashed once again minimoto, AND restored from google account, and used the titanium backup from earlier...as of now nothing happened...i'll wait...
Thak you anyway
Ok, if anyone could ever have this problem, probably the issue was caused by the application "Wallpaper Changer" that i used to switch wallpaper every 2 hours...it probably got stuck somewhere and freezed the phone...as of now, it didn't freezed yet so i think i found the solution.
As of right now I'm missing pretty much every file on my Internal Storage. No TiBu, no SMS Backups, no pics. However under storage in the settings menu it still shows 9 Gigs Free, which leads me to believe that its there, just not visible... There are some folders, but they are empty or don't contain the files it used to.
I noticed it at 2 AM when SMS backup & Restore notified me that it wouldn't backup because it couldn't find the SMS.xml file. I used Astro and ES File Manager to find it manually and I couldn't, at which point I noticed everything was missing.
Prior to that my phone was plugged into my PC, simply to charge. I was on the phone walking a friend through a Windows update and installing some software, and I plugged into my USB 2.0 port to charge the phone (3 hour phone call), which I've used multiple times. While it was plugged in I didn't really us the PC much other than google searches and reading news\posts\forums. I did however install Avast Antivirus cause I was walking her through it and I've never used it before. I'm hoping that had nothing to do with it. I googled Avast wiped my phone, and various similar phrases and didn't find any similar forum posts.
At this point, I could write a whole book about what might have caused it. I really have no clue. I'm looking for either anyone with a similar experience, or more importantly, anyone with a resolution.
Edit: I have a GSM Dev, Unlocked Rooted. Tmobile 4.4.2 using Faux Kernel.
That sucks dude! I haven't heard of this randomly happening on any phone I've had. Aside from recovery wipe accidents.
Drag!
Sent from my N5 cell phone telephone....
Haven't even been in recovery for a while. Even the backups made in recovery aren't there or aren't visible to the recovery either. I'm not even upset, I've lost things before due to my flashaholic tendencies, but I don't even flash stuff on this phone. That was one of the main reasons I kept this instead of my Nexus5, figured I'd be more productive not having to flash all the time. Might as well get a different phone...
More importantly I want to know the cause so that I and others can avoid it happening again. Almost makes me wish I kept my Nexus5, which now that I think of it, I have a fairly recent backup of on my PC. Who hoo!
Anyone with any thoughts or input, greatly appreciated.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!