I changed absolutely nothing since my last photo,I have no magisk modules to do with the camera,and all the usual won't fix it.cleared cache,restarted phone,used different photo apps..flashlight doesn't work either.retarded 20 times and cleared dalvic too....I went to bed it worked..woke up..no....what the heckerz
jacecrobinson said:
I changed absolutely nothing since my last photo,I have no magisk modules to do with the camera,and all the usual won't fix it.cleared cache,restarted phone,used different photo apps..flashlight doesn't work either.retarded 20 times and cleared dalvic too....I went to bed it worked..woke up..no....what the heckerz
Click to expand...
Click to collapse
OK sorry. I remembered now that I changed viper modules to a newer version and when I deleted its module its working...random...sorry I'll leave this just incase someone runs in to this..I will update later which versions of viper don't cause this.(had viper for weeks no issue)
Related
Hello All, I did some searching for this, but all I can come up with is quite the opposite of my issue. My issue is my phone got stuck in boot loop. Having been on this forum a few times the first thing I did was clear the cache and dalvik and it booted right up. But unfortunately anytime I reboot, it gets stuck on the bootanimation and no matter how many times I reboot, it absolutely will not work unless I clear the dalvik, every time.
Any thoughts on what may be going on, I would really love suggestions that I might can try to see if it's a permanent fix.
Regardless, thanks for your time and effort :fingers-crossed:
T-Mobile C6606
Updated To
[LB] eXistenZ v6.0.0 - Ultra Edition
10.4.1.B.0.101
Kinda hard to help with so little information.
Do you by any chance have xposed framework installed?
If so I know that if you restore app + data from titanium backup for xposed modules it can cause your phone to stick on the boot animation. Clearing dalvik cache would temporarily fix it.
If that's your case then you can go into setting / apps and clear data on all the modules.
If that's not your issue then you may ave flashed something incompatible with your framework. Without much information I can only suggest that you re-flash your rom or firmware.
Trucifix said:
Hello All, I did some searching for this, but all I can come up with is quite the opposite of my issue. My issue is my phone got stuck in boot loop. Having been on this forum a few times the first thing I did was clear the cache and dalvik and it booted right up. But :
Click to expand...
Click to collapse
Do you use gravity box?
If yes,then disable it in xposed modules and reboot
Gravity box has been causing these kind of bootloops for most of us
I had this issue sometimes when i was using advanced power menu with my previous stock rom. When rebooting from advanced power menu i always had bootloop, but when restarting from the xposed menu for example, no bootloop.
Thank you all very much, and I use all three of those, xposed, gravity box, and advanced power menu. I will try all three of those suggestions today and report back which one may have did it.
Most likely gravitybox. There's been a lot of talk about it. Some don't have it at all, some got rid of it in the newer version and some like me has it with all 'newer than 2.8.5' versions. I usually can get it by trying to boot some times but it happens randomly.
Incredibly annoying and there's some things in newer gravitybox versions that I'd really like
SOLVED - Phone won't boot unless Dalvik is cleared
Kocayine said:
Most likely gravitybox. There's been a lot of talk about it. Some don't have it at all, some got rid of it in the newer version and some like me has it with all 'newer than 2.8.5' versions. I usually can get it by trying to boot some times but it happens randomly.
Incredibly annoying and there's some things in newer gravitybox versions that I'd really like
Click to expand...
Click to collapse
It quit doing that after I cleared app data and cache for gravity box. Gravity Box is definitely a factor :silly: If it comes back again I will go through more appropriate channels now that I know the culprit.
Thanks every one !!!
Since Magisk 11 released and even now with 12, rebooting feels like a roll of the dice between flashing something or installing a module. I don't have any real development experience, but had tried building a module or two and troubleshooting another in the past few weeks, which resulted in eventually booting to the error SystemUI has stopped... This has happened several times in a day even. Now today, I push the April security update, install Magisk 12, and slowly start piecing my setup together 1 by one to make sure everything works properly. Then suddenly another SystemUI has stopped error... Only way to fix it is to restore from TWRP or factory reset. A timely process. Flashing zips in TWRP in the past hasn't resulted in this for me ever... That's going back to the Donut days on my Samsung Moment, LG Optimus, HTC One M7, and now my Nexus 6. I really want to love Magisk, but its very frustrating to get so far then to have to restore and start again.
Is it something I'm doing wrong? Is there a better way to resolve this when it occurs? Is there a way to avoid this error? Is this even a Magisk issue and the fact it hasn't happened before is a matter of luck? I don't even know what's causing it...
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
duxishere said:
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
Click to expand...
Click to collapse
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Hm... I did notice this issue a couple of times on my Nexus 6 as well. It did happen a few times when installing modules that weren't quite compatible or otherwise had issues (I was experimenting and it was never quite reproducible), but mainly when trying to do a TWRP backup or restore (completely reproducible, 100% of the times). I figured it was my device acting up and never really connected it with Magisk.
I'm going to do some further testing...
gk1984 said:
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Click to expand...
Click to collapse
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
batmi said:
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
Click to expand...
Click to collapse
I concluded it's a module I was using. Actually, the module I tried writing myself. Stopped using, no more issues. Well, at least not yet.
Hello again XDA!
So this has become much more frustrating that I thought it would. My phone normally operates fine, just a couple minor software issues here and there, latest issue being my alarm not going off, tried disabling amplify in xposed as the issue only occurs if the phone has been idle for the night, figured maybe amplify might be blocking the wakelock or something. Just thought I'd share in case the module could be the root cause of both issues.
The issue I'd really like to ask about has to do with booting. As I said, the phone generally runs fine, but any time I reboot(or my phone dies) I have to wipe the dalvik in TWRP or else android just hangs on bootup indefinitely. Not only is this always a slow process(generally 15 mins of downtime) but it drains about 30% battery in the process. Just wondering if anyone has had this issue and fixed it without wiping and reinstalling a rom from the ground up.
Currently running latest ICE Lollipop build 7.1.3, elementalX 22.4-sense kernel, and latest firmware, 4.19 I believe. Xposed running with just a handful of modules (greenify, snapprefs, xblast, youtube adaway, sense toolbox). I have tried using stock kernel and uninstalling xposed framework and apk to no avail. What does work is a clean install of the same rom with the same basic setup, but I didn't want to have to reconfigure everything if I didn't have to, so I restored my backup in the meantime.
I can't get a logcat ATM, maybe tomorrow after work if I have some time. I'm also not 100% sure how to grab one anymore since its been years since I last posted one, but would be happy to provide one soon.
cheers!
I installed the latest one on my galaxy a5 2017 sm-520f with magisk on rooted phone. ResurrectionosOs 6.2.1 8.1oero. I did it with magisk and I flashed manually. It even says closed version 90 is activate, but when I try the use any of the modules they don't work.
Thanks I'm advance
log
@goodTASte,
Just an FYI. Never paste a long log. Attach it or put it online and post a link. (EDIT: Oh, I see you don't have the ten posts yet.)
There should be no reason to run Amplify on Oreo. No benefits plus I believe it's not totally functional. I suggest disabling/removing it. Couple of other modules I thought weren't quite up to date for Oreo also.
In fact, disable all modules and test them one by one. Ofc rebooting after each activation.
Lots of dalvik related stuff. Maybe a dalvik wipe is in order? Not sure but it doesn't hurt.
LG G3 D851, Candy7 v6.0 ROM, Google free - no microG, MultiROM, XDA Legacy
I did the whole process again. The issue that came up before that "xposed installer is installed, but not active" where the solution seemed to be look for root/data/data/de.robv.android.xposed/config/ and there eliminate (delete) modul list file. where he guy used lollipop i dont know, i only have 4 files there cache, code_cache no_backup and shared_prefs. Previusl i deleted all 4 of these, and after that xposed said its active. What should i do? I
Rebooted it works like charm. Well not exactly i installed minmin guard and its not blocking the ads. It supposed to do that. Guess modules still not work
So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
bigmatt503 said:
So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
Click to expand...
Click to collapse
Yes, after I updated to November it happened. I was browsing google feed on the launcher. It froze then restarted to "pixel is starting". Flashing factory image without the -w didn't work, I had to wipe data. I even tried disabling all magisk modules via adb but still had to wipe data.
Interestingly, I was also using the center clock module. I've stayed away from that and haven't had a problem since.
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
CyberpodS2 said:
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
Click to expand...
Click to collapse
I have uploaded November updates but i run center clock and i haven't had any problems.
Tulsadiver said:
I have uploaded November updates but i run center clock and i haven't had any problems.
Click to expand...
Click to collapse
Center clock is one of my favorite mods.
Now that I think of it I was also running a couple modules to pass safetynet. Now I'm only using center clock and systemless hosts.
Thanks for chiming in
I'm starting to think it could be magisk canary. This has never happened when I was on android 10 using stable magisk. Either way I'm up and running again... rooted and still using center clock mod