I have had this Samsung Vibrant for a couple months. I have a good number of apps and did the one click lag fix sometime ago. Recently, I had experienced a bunch of force closes and overall bugginess. My Pure Calendar widget stopped loading. I emailed the developer. He had me send him the change log and responded to me that my phone had a bunch of problems.
He said that I should have wiped the phone before the lag fix. And that he can't help me until i wipe it.
Here's where I need help. . .How do wipe the phone but back it up in a way where I can get all of my apps and settings back?
Can you give me a step-by-step in "newbie language"?
After I wipe it, i will use the lag-fix and then restore the settings and apps, if that's the way I should do it (once again, what do you think?).
Sorry if I broke any forum rules or ettiquite. If I did, it was unintentional. I just need the help. Thanks in advance!
Generally the first step is to uninstall the lag fix. That may actually fix your problem since the earlier lag fixes were prone to degradation over time. I don't know which lag fix you installed and uninstalling it will take some research on your part.
After uninstalling the lag fix I would try flashing one of the newer roms that fix a lot of bugs and do not need a lagfix. Again, that will take some research on your part. Check out the bible in the development section.
Thanks for the reply, snowdogging.
I did uninstall it (v1). There is an option on the app that I used.
All I want to do is back-up, wipe, get back to original condition, and then restore my apps and settings.
It is not that hard to do with android but you can expect to lose some information. What I usually do is do a Titanium Backup of all my user applications. I then use SMS Backup+ to dump all of my text messages to Gmail. I am rooted so I use SU Explorer to make sure that all of my pictures and other important data is moved to my external SD card.
And then cross my fingers and use Odin to flash the latest rom that I think is worthwhile.
After a successful flash I do all of the first paragraph in reverse to restore my stuff. It is time consuming. As an example, the first time while learning took about 5 hours, while now I can probably do it in one.
Just make sure you can get into download mode while at the powered off green battery indicator BEFORE using ODIN and you should be OK to experiment. I have crashed ODIN and a bunch of other stupid stuff and am still on my original vibrant.
I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?
Moto G4 xt1622 retgb unlocked and rooted with several root apps like twrp, TiBu, File Manager, terminal etc.
Every time I select 'Settings/Apps', Settings force closes with the error in the title. If you google this error most answers tell you to open settings/apps and clear cache for various programs - a bit of a problem for me because opening settings/apps is impossible. However I have tried many things - clearing cache files from within TiBu, wiping the cache partition from twrp, reinstalling anything to do with 'Settings' from Tibu, flashing two different backups from twrp, one of which was taken of the stock phone as soon as I got twrp working , I have even tried a full factory reset - nothing works, the error is always there.
I don't know when this started, so I can't tell you what I was doing at the time, and if it is of any interest although settings/apps doesn't work, 'App Info' still does. Also every other section within 'Settings' works normally, no errors whatsoever, it is only 'Apps' that causes the force close.
Is there anything else I can try?
Edit. Forgot to say, it is stock marshmallow 6.0.1, no custom roms.
Safe mode? Hit the power button, long press power down.
Sent from my Moto G (4) using Tapatalk
matt55555 said:
Safe mode? Hit the power button, long press power down.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Good call, but unfortunately I have already tried that - safe mode won't start, it just gets to the Moto logo screen and no further.
Thanks anyway.
Managed to solve this problem for myself. Mainly thanks to chainfire (for producing flashfire) and no thanks to the originator of this thread http://forum.xda-developers.com/moto-g4/help/xt1622-uk-sim-free-stock-firmware-oem-t3448913 who suggested that it is safe to delete third party apps from the /root/oem/app folder (even though these are apps are not even remotely relevant to my locale). I am not blaming the originator of course, it is my fault for listening to him (especially since he no longer owns the phone in question). But let me warn everyone that you CANNOT delete files from this source - however irrelevant they seem to be - without consequences.
Why didn't reinstalling a TWRP backup solve the problem?
Because TWRP does not backup the /root/oem partition. Luckily flashfire does, so a simple reinstall of that partition and 'Settings/Apps' came back like magic.
I am now off to add my thoughts to the thread in question and to do another flashfire backup.
viking777 said:
Managed to solve this problem for myself. Mainly thanks to chainfire (for producing flashfire) and no thanks to the originator of this thread http://forum.xda-developers.com/moto-g4/help/xt1622-uk-sim-free-stock-firmware-oem-t3448913 who suggested that it is safe to delete third party apps from the /root/oem/app folder (even though these are apps are not even remotely relevant to my locale). I am not blaming the originator of course, it is my fault for listening to him (especially since he no longer owns the phone in question). But let me warn everyone that you CANNOT delete files from this source - however irrelevant they seem to be - without consequences.
Why didn't reinstalling a TWRP backup solve the problem?
Because TWRP does not backup the /root/oem partition. Luckily flashfire does, so a simple reinstall of that partition and 'Settings/Apps' came back like magic.
I am now off to add my thoughts to the thread in question and to do another flashfire backup.
Click to expand...
Click to collapse
So you restored a backup that you luckily made with Flashfire before your settings/apps stopped working? That doesn't really solve the issue if someone doesn't have a Flashfire backup, does it?
Hy everyone
After a lot of searches and flashing I have to open this thread.
No matter which oreo or nougat rom I tried I got constant app crashes and random reboots.
I have tried all oreo roms, nougat Roms and eui roms too.
Sometimes app crashes after one day or instantly after flashing.
I have tried different modems.
Tried without xposed and magisk but still apps start crashes on each rom.
I have clean flashed everytime too. But don't know why this is happening on all roms.
any one can help me out?
Thankyou
Heyyo, have you also tried doing a TWRP format data (by format data I mean format and not wipe) and then not restoring from a Google Cloud backup? There is a small chance that it could be a setting or something from your Google Cloud backup causing the instability.
Bit better
Hey, Thanks a lot for reply and I am sorry that I just read your response right now
First of all I didn't use Google cloud backup
I only restored from Tb.
I have already formatted data as you said and flashed new rom. Didn't even restore data from Tb.
As soon as I installed three to four apps from playstore phone restarted.
After installing all apps and setting up my phone.
Now app crashes are lot less then before but they still crashes like just Google stopped working until I restart phone.
Different app crashes after sometime and I have to restart phone to get them back to Work. Phone also restart sometimes.
Don't know why it's like that...
Is there any way I can check which app causing problems by myself?
Any suggestions?
Thank you
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.