I flashed https://forum.xda-developers.com/nexus-5x/development/bullhead-nexus-rom-t3995623 that rom and android setup was stopping. So I changed to other roms but patternlock and passwordlock is crashed. Once it starts to be crashed, it is always crashed when I unlock. It is even crashed in the rom worked well before.
If I delete locksettings.db, locksetting works correctly but few hours later it has same trouble. Wiping Dalvik / ART Cache, system, data, cache and formatting data has no effect.
How can I fix the problem?
TRIPLEFIRST said:
I flashed https://forum.xda-developers.com/nexus-5x/development/bullhead-nexus-rom-t3995623 that rom and android setup was stopping. So I changed to other roms but patternlock and passwordlock is crashed. Once it starts to be crashed, it is always crashed when I unlock. It is even crashed in the rom worked well before.
If I delete locksettings.db, locksetting works correctly but few hours later it has same trouble. Wiping Dalvik / ART Cache, system, data, cache and formatting data has no effect.
How can I fix the problem?
Click to expand...
Click to collapse
After six times deleting locksettings.db, no more problems for 4days. It decreased than 4times crashes in a day.
Related
Hi Guys,
Using Myns Warm Donut.
Since this morning its started really playing up.
I cant launch any program, dialer, contacts, sms, astro etc.
It either comes up closed unexpectedly (for sms, dialer, etc) or like astro, it says its licence has expired?
I havent installed or changed anything on the phone to make it go wrong.
I have tried all the usual ways of resolving, eg, fixing permissions, clearing dalvik cache.
I really dont want to lose my sms, data, etc so dont want to reinstall, please help.
Can anyone help me please?
Thanks,
Tom,
load into boot menu..1. choose backup /data
2. install system again
3. recover data (or something else there)
You could also try clearing Dalvik Cache and Fix Permissions, sometimes helps, and does not clear data, ( apart from the Dalvik Cache itself).
Hi,
Already tried clearing dalvik cache, etc, no effect.
Tried backing up, reinstalling, and restoring, but as soon as I restore it all goes back to how it was and everything starts crashing again.
Ive had to lose all my data and start again. =(
Is there any program I can run to backup sms, mms, emails, etc?
Thanks,
Tom
I've been having this issue for the past couple of weeks and I don't know how to resolve it. At first I thought it might have been my ROM so I wiped everything clean and flashed a new ROM but the problem still exists. I read on a forum that the cache partition could be full so I used Terminal Emulator to check the disk usage and I'm reading that my /cache is 98% full. I also have a dalvik cache in the cache folder as well as a dalvik cache in my /data folder both of which are close to 300mb in size. I tried to clear the cache and dalvik cache in recovery before resorting to the full wipe and each time both cache rebuilt themselves. I'm completely at a loss and I'd really appreciate some help with this issue. Thanks in advance.
So you're out of space? Perhaps you have several backups from CWM taking up all the room. They are pretty large files. I myself keep my stock backup and my most recent, the rest of them rest on my pc.
Sent from my Blazing ET4G
thats not the case here. i dug around a bit and saw that my cache and dalvik cache are 98% full. as stated earlier i tried deleting the dalvik cache but it regenerates itself. i looked around in titanium backup and saw an option to integrate some of the cache to the system. i enabled that and it moved around 150 items around and freed up some space. i'm still around 88% full and i know this problem is gonna rear it's ugly head very soon so I'm trying to install programs like link2sd and as2d+. none of these programs are working though...they all require partitioned sd cards (which i have) but none of these programs are seeing the partitioned card. i've tried repartitioning under recovery but that does absolutely nothing. anyway e4gt users can take advantage of these programs?
I had the same issue and it was driving me crazy. I just downloaded Cache Fixer and ran it and now I am good. Turns out my cache was 95% full, wiped it using that tool and I can now update and download.
I want to add that after it cleared, I could update but some of the other apps on the phone did no work (Google Music and Dolphin Browser to nae a few). I re-boot and the cache is back to pre clearing levels and no other issues. It does temporarily fix the isse bt I do not have a permanent fix.
If anyone has one, I would love to know what that may be.
i just want to say that I am having the same exact issue and performed the same steps the OP did. Only when I wipe the cache with cache fixer it everything forces closes so i can't update anything. So i am really stuck.
The only success that I have temporarily is uninstalling the app then resinstalling it. But thats not a permanent solution and sucks for apps like beautiful widgets.
PLEASE HELP
EDIT: on calkulins 3.0 rom and self updated google play
I recently updated my CM7 rom... I didn't checked the "erase dalvik cache" option...
So everything went fine... But now phone goes white everytime I open Gmail... I tried uninstalling it but then I can't download it from play store because when my PC it says that app is already installed. And I can't access play store from my phone since I need to sync my gmail account.
How to fix it... I mean maybe downloading the right Gmail app
And thanks for taking the time to read and help my problem
I didn't checked the "erase dalvik cache" option...
Click to expand...
Click to collapse
And here lies your problem, wiping dalvik cache is a crucial thing to be done when installing a new ROM or when updating your currently installed ROM.
ALWAYS WIPE BOTH CACHE AND DALVIK CACHE.
So, i've got two solutions for you.
1 - Uninstall Gmail app, clean Play Store's app data, reboot into recovery and wipe both cache AND dalvik cache.
If the solution above does not work, do this:
2 - Format everything (cache, data, boot and everything else) and reinstall your ROM. (this one is fail-proof, I mean, it WILL work but will erase EVERYTHING in your PHONE)
Skyheiser
Was I not supposed to wipe the cache and/or ART cache in TWRP? Because, to try and fix a stupid problem, I did wiped that and created a lot of other problems. STUPID!
Facebook/Messenger keep force closing when opened...
Amplify also keeps force closing when opened...
Xposed no longer works, it says it's installed and active but it does nothing. Tells me to check the log, but there is no error file (it can't create the file).
I get a 404 error when Xposed tries to download the modules list.
I made a System + Data + Boot backup but I've read that since "Data" is encrypted on the HTC 10 with proprietary algorithms, that it's not possible to restore it. I could just restore "System" and "Boot", but will that do anything? And shouldn't I clear Cache and ART Cache after doing that anyway?
What the hell did I do to my phone? Save
I might have fixed this...
I just uninstalled a bunch of root apps (AdAway, Xposed, SuperSU, Greenify), apps that change the "system" (although they were systemless) and restored my boot image. Cleared Cache and ART Cache again, rebooted and reinstalled Facebook/Messenger. They are now working again
I'm going to reinstall everything else back, one by one and see if everything is fixed...
Everything seems to be fixed
Help!
For some reason my A3 started to act weird (maybe because it noticed that I ordered an S9). Almost all my apps aren't accessible anymore. When I click on something it starts the app and then closes it shortly after telling me the app needs a restart.
Only few apps work (Whatsapp, Calendar, Instagram, Calculator for example)
I tried wiping the cache partition (where it says it can't find the /misc partition, don't know if this is normal), wiping app cache directly and reinstalling apps. Nothing helped.
Thanks in advance!
start everything from the beginning,
just wipe your /data from twrp.
and everything will fine.
dont forget to backup your data inside internal memory, because it will be wiped too