Tried Vanir_101213 (nuklearmistake), runs well, but FC when opening "settings/security" (as in version 101013, dont have this issue in 100713).
Does anybody know how to reset only system settings (no full wipe), cause I installed vanir_101013 as third ROM (MultiRom) once again and the fresh install doesnt FC systemsettings/security. But this is the only issue I have with my fully installed version of Vanir, so I would like to reset only systemsettings (delete wrong settings), may be the issue with "security" could be solved by resetting. Tried to delete data under Apps/Settings/Details, but after that all system settings are as the were before...
Related
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
harry_fine said:
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
Click to expand...
Click to collapse
Took some advice in the S5 developers forum. Backed up my SD card. Formatted all partitions on phone. Re-formatted SD card with FAT32 in Windows. Made sure everything was cleared out. Copied the ROM (in a PC reader) to the newly formatted SD card. Re-inserted card. Installed 9.1, including Xposed Framework and all the modules I use. Restored my backed up files (pictures, music, TB backup files) to my SD card. After boot I did NOT get the systemui closed error that have been plaguing me for 3 days..
So, it may be that there was something in my configuration, either prior to using Omega or on an earlier version of Omega that caused these problems when I installed Xposed. Hoping that's the end of it. Will let you know.
Lesson for everyone, if there is an issue that is not generally being experienced by everyone else, don't just to a full wipe install, delete everything from everywhere with formats, including your SD card.
Hi guys
heres what happened
I flash my device via spf flash tool to stock MM
then flash TWRP_boot_root_s228 then
copy CM13-2016-09-26 build & tron kernel
then I put my device via recovery mode then
flash the cm13 restarted all good then
flashed the tron kernel, all good again
here's the tricky part:
after I install facebook via google play store as soon as it as it is finished installing. there's several apps that stopped working like trebuchet, package installer, calculator and several more and when I check the settings several apps contains 0 bytes, none whatsoever. what am I doing wrong, I have been flashing several times ends up same result.
btw I wipe dalvik cache, system,data,cache,internal storage before flashing.
pls help me guys
There is no need of wiping internal storage
And
The problem you are facing can be solved by changing the rom
Simply download a random Custom Rom and gapps then flash them through your recovery -> this time just wipe dalvik, cache, system and data only.
I faced same problem once and i found solution through this step
I recently got this phone and first thing i tried to do is install new ROM, but everytime i boot into it i get Google Services Framework crash, android.process.media crash, and probably some other ones as well i couldn't see because of overlapping error messages.
I didn't do a "dirty install" - everything except internal storage was wiped, then fresh rom install, gapp install and cache wipe then reboot.
When i don't install gapps, i can boot into system but still android.process.media keeps crashing, and random applications i can open usually crash as well.
Did anyone encounter similiar problem?
I suspect you need to format not just wipe before you flash.
If flashing a custom rom other than miui -
download a new updated package of open gapps with the right android version for rom arm64bit package. I usually go micro.
Flash directly after rom before rebooting. A miui rom has gapps built in obviously so no need to flash
Sounds like you encounter strange issues because data was not wiped.
Try the LOS installation instructions step by step with any ROM you are going to use. Works for me.
Good luck!
Hello guys,
My Huawei Mate 20 lite has just updated to latest firmware (SNE-LX1 8.2.0.138(C432))
Now all application notifications are gone from the drawer and the lock screen. I have tried enabling all possible settings, including ignoring battery saver, allowing to draw over other apps, etc.
All messengers get just a dot on the icon - no banner, no lockscreen notification.
Spotify and Poweramp have no drawer and no lockscreen control as well - to skip a song, I need to unlock the phone and open the actual application.
I did honestly try to google, disabled smart lock (no face unlock present) and smart cover - no luck.
I have tried re-installing Spotify - no result.
Any ideas?
Worked just fine up until the firmware update.
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
CamoAndres said:
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
Click to expand...
Click to collapse
Thanks for suggestion, but I couldn't say it's a fix. I'm rather trying to check if anyone else is having the same issue with the latest firmware and if there is an actual solution (ok, selling this phone and buying a normal one is another considerable option)
hello can anybody help me please
i have forgotten my pin so i used this way to bypass it
rebooted to recovery and selected cancel in decrypt data
Because i don't remember what it was
and deleted what i have found form those files
--------------------------
recoverablekystore.db
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
--------------------------
now my phone opens up but stuck after lock screen at phone is starting
Note: i can enter notification bar and phone settings
could you please guide me how to fix it without wiping the data
ROM: CRDroid 6.13
TWRP: 3.4.0-10 by mauronofrio
@M.WeWe
This sounds like the issue with early Pixel Launcher Mods.
When disabling / removing the module, it caused exactly your problem.
Is your device rooted, did you use such a model and removed it recently?
With a root explorer (or within TWRP File Manager), navigate to:
data/system and delete the "package_cache" folder, then reboot.
This fixed the described issue in the past.
I've been looking for a solution to the same problem for a month.
After installing recovery the memory was encrypted and No os warning came.
It's been in my phone for the last 3 years.
goddamn google
I don't know if I can find a solution without losing the memory.
My nerves are gone now.
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
selaam34 said:
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
Click to expand...
Click to collapse
Whenever you switch the ROM you have to (!) Format Data - it's described in any good guide for how to install a custom ROM to Xiaomi
Formatting Data (that includes also Internal memory) establishes the new filesystem for the new ROM, ie for its encryption - that's why Formatting (not Wiping - wiping wipes the files but keeps the old filesystem) is required