I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Looks like Magisk 14.5 might have something to do with it.
Starting on page 452 there are a few posts from there on about it.
Symptoms are a random reboot with a soft boot loop of the SystemUI. The only way to correct it is to hard reboot the device.
I can usually go a few days worth of up time between the bug reappearing.
I was the exact same way on 8.0. Every couple of days, it would start randomly rebooting and/or apps would start crashing. The only fix was to hold the power button until it rebooted. Rebooting by just pressing the power button and selecting reboot would always hang.
I was hoping 8.1 would fix it, but it's quite a bit worse. It's done it at least 4 times so far today. Same symptoms. Apps will start crashing (sometimes the foreground app, sometimes background ones), or the phone will just soft reboot, or both. Sometimes it's while I'm using it, sometimes I'm not using it at the time. No rhyme or reason, that I can tell..
I had one app that crashed immediately every time I tried to start it until I uninstalled it and restored it from backup (with data). That was weird.
If this keeps up, I may have to roll back to 8.0.
theycallmerayj said:
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Click to expand...
Click to collapse
There is a larger thread on this HERE. There is no definitive smoking gun yet but certain root apps seem to be causing it. One way to rule out Magisk would be to simply uninstall the app temporarily (longpress>>App Info>>Uninstall) then fastboot flash the original boot.img and dtbo.img. Run this way long enough to know for sure whether being rooted is causing the issue. There are tons of people rooted who do NOT have this issue, so it is more than likely one of your root apps/themes is causing it.
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
theycallmerayj said:
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
Click to expand...
Click to collapse
Have you tried Adaway? I use very few root apps, but that is the first one I add every time. I've not had any reboots at all and it is very effective. Because you only use the one root app, you may find the culprit was UH, and not Magisk.
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
theycallmerayj said:
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
Click to expand...
Click to collapse
You can use different host files you don't have to use the ones that come with AdAway. Try Steven blacks out
I'm having this same issue with Magisk. I experienced it with an older Magisk on 8.0 as well.
I'm thinking about just getting rid of Magisk altogether. However, I used ES File Explorer to edit my build.prop to add the command to disable the nav bar. I'm nervous that uninstalling Magisk will cause the "your system is corrupt" message and a bootloop. However, I also have Flash Kernel installed. I wonder if the custom kernel will allow me to use the phone with the modified build.prop and without Magisk...
Related
So here is my problem, from time to time the tablet just freezes, only the notification bar is responsive and as soon as I pull it down, It becomes too late and the only wawy I can use the tablet again is to force reboot by holding the power button.
My GT-N5110 being rooted and the Android version is 4.1.2 stock (^^).
If you know where the problem comes from feel free helping me getting ride of it
I've gotten this occasionally. I went through the device the other night and uninstalled a lot of stuff that was in the "maybe works/maybe not, I never use" category, and I've been getting much less of this behavior since.
After installing the multiwindow app (which I like) I found that the camera app would make my device lock up and require a reboot.
Turning off the multiwindow feature (not uninstalling the app) gave me the ability to use the camera again.
Sorry I can't remember what-all I uninstalled.
It happened to me when i rooted with superuser, i unrooted and then re-rooted using SuperSU (same root app, only chose supersu). Never happened to me since.
thank you all,
i'll try uninstalling and unrooting then rerooting it using superSu.
Just for the update : the manipulations above seem to have solved the issue. Thank you again for your help.
So I have been getting random reboots on my Samsung Galaxy Tab Pro 8.4. I only noticed this after I allowed SuperSU to disable KNOX. It said it was enabled, recommended I allow it to disable it, so I said OK, and ever since then I get random reboots. Any help is appreciated. I don't know if I need to find out how to RE-ENABLE KNOX, or somehow totally remove all KNOX services and apps. Thanks again.
Oh and I'm running Stock rooted 4.4.2.
Had the same, fixed
I had the same problem a few months ago, after disabling Knox. Downloaded and installed the Xposed module "Samsung KitKat System Server Crash Fix", not a problem since.
You can get it here http://repo.xposed.info/module/com.thomashofmann.xposed.samsungkitkatsystemservercrashfix
thdervenis said:
I had the same problem a few months ago, after disabling Knox. Downloaded and installed the Xposed module "Samsung KitKat System Server Crash Fix", not a problem since.
You can get it here http://repo.xposed.info/module/com.thomashofmann.xposed.samsungkitkatsystemservercrashfix
Click to expand...
Click to collapse
thdervenis, thank you. I installed the APK at the link you provided and so far I've not experienced the reboots I once was. Weird that this was happening at all but glad someone found a "work around". Would be nice if the root cause was remedied however.
petermg said:
thdervenis, thank you. I installed the APK at the link you provided and so far I've not experienced the reboots I once was. Weird that this was happening at all but glad someone found a "work around". Would be nice if the root cause was remedied however.
Click to expand...
Click to collapse
The root cause is letting supersu disable knox. If you leave Knox enabled everything (root included) works fine and no reboots happen.
dottat said:
The root cause is letting supersu disable knox. If you leave Knox enabled everything (root included) works fine and no reboots happen.
Click to expand...
Click to collapse
Why does SuperSU recommend to disable KNOX? It says that unless I disable KNOX it may cause problems. Very confusing.
Oh, and is there any way to RE-ENABLE KNOX once you've allowed SuperSU to disable it?
I think i solved my problem rebooting prematurely while screen is off and on standby i am not sure if this is applicable to T320 model as i have a T325 the provlem started when i started using power saving mode when i disabled mine it didn't rebooted anymore hope my fix will also help those who are having problems
Sent from my SM-T325 using Tapatalk
petermg said:
Why does SuperSU recommend to disable KNOX? It says that unless I disable KNOX it may cause problems. Very confusing.
Oh, and is there any way to RE-ENABLE KNOX once you've allowed SuperSU to disable it?
Click to expand...
Click to collapse
I'd like to know the answer to both questions too. I also disabled KNOX per SuperSU's recommendation, and now find it difficult to use my tablet now that it constantly reboots. I'd like to just enable KNOX again instead of installing a workaround.
DGenerateKane said:
I'd like to know the answer to both questions too. I also disabled KNOX per SuperSU's recommendation, and now find it difficult to use my tablet now that it constantly reboots. I'd like to just enable KNOX again instead of installing a workaround.
Click to expand...
Click to collapse
I wanted to chime in and state that my T900 started randomly rebooting after freezing all Knox-related apps using Titanium Backup. The device was rooted using the appropriate CF-Auto-Root file from Chainfire's site for KOT49H.T900UeUANI1 several days ago. The reboot problem immediately went away after I defrosted Knox again. There are multiple threads now, including this one, that pretty well establish that disabling or freezing Knox can cause unwanted rebooting. Is there anyone who can identify the underlying problem so we can figure out once and for all whether Knox can, in fact, be safely frozen or deleted on rooted devices? Many thanks in advance!
DGenerateKane said:
I'd like to know the answer to both questions too. I also disabled KNOX per SuperSU's recommendation, and now find it difficult to use my tablet now that it constantly reboots. I'd like to just enable KNOX again instead of installing a workaround.
Click to expand...
Click to collapse
Fortunately, I "stole" the ROM while I reflash the tablet with Kies3, and I just use Odin to flash the "stolen" ROM, restart once, and run CF Auto Root, and leave Knox as is (not disabled) when SuperSU prompted.
Anybody have any luck in re-enabling Knox to get rid of the random reboots? I went into General-->Security-->Device Administrators and checked the checkbox for Samsung KNOX. Did a reboot but I'm still having the reboots.
I even installed the "Samsung KitKat System Server Crash Fix" mentioned above and it still is rebooting.
Any help would be appreciated.
I'm also having the same problem and it seems to be when my battery gets to around 50% or I'm trying to browse. It just started a few weeks ago for me. The tablet just keeps restarting until I plug it in and then it stops.
I am a novice to rooting so I don't have any advice. However, I would certainly appreciate the help!
Does rooting to CM fix the restarting?
cbm76 said:
I'm also having the same problem and it seems to be when my battery gets to around 50% or I'm trying to browse. It just started a few weeks ago for me. The tablet just keeps restarting until I plug it in and then it stops.
I am a novice to rooting so I don't have any advice. However, I would certainly appreciate the help!
Does rooting to CM fix the restarting?
Click to expand...
Click to collapse
any solution . .I have the same problem.
I just bumped my lollipop rom and install xposed then I noticed that my phone shows out "android is upgrading" on every reboot. Is there any way to fix this as it is a little annoying...:crying:
Sorry for my broken English
+1 !
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' is better than, well you know.
kp_q said:
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' and better than, well you know.
Click to expand...
Click to collapse
This activity tends to get lengthier after every reboot. I've found that once it "seems" to loop in the "Android is upgrading" screen, to remove the battery, boot into recovery, wipe the Dalvik cache, and reboot. It will go through the lengthy procedure of updating software, but will boot a WHOLE lot faster after that.
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
alqoshi4life said:
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
Click to expand...
Click to collapse
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
abbey666 said:
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
Click to expand...
Click to collapse
Which Xposed version did you use? I'm on v68 right now which is the latest. I had v67 and it did the same thing.
V66. I tried2 later versions but this one worked for me.
I have a Oneplus One but I have the same issue. Every damn boot. Android is starting. optimizing app 1 of 121.
I also have the latest version of xposed.
I know not the forum for the OPO but just thought I'd let you guys know other phones face it too and hopefully find a solution to this.
I had to make a really important call and my phone restarted all on its own. That's bad enough but add to the random restart sitting for 5 minutes to wait for android to finish optimizing
abbey666 said:
V66. I tried2 later versions but this one worked for me.
Click to expand...
Click to collapse
I tried v66 like you recommended and the same thing happened. So it must be something else that solved your problem. I guess I can live with it though.
have the same problem with my g3.. everybody have data backup ? )
BlackGodRaven said:
have the same problem with my g3.. everybody have data backup ? )
Click to expand...
Click to collapse
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
alqoshi4life said:
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
Click to expand...
Click to collapse
l solved it too ) l transfer backup to sd card )
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
Trying this now...my G3 crashes for whatever reason from time to time after my Tasker that disables bluetooth as soon as the USB power is disconnected from the car.
Currently on version 79. Patched it with Lucky Pater and removed all odex; rebooted (got stuck but battery out & booted normally).
I'll report if there are any further issues
Okay it's very odd it seems like there's an issue with my LG G3 disconnecting bluetooth from the stock head unit in '13 WRX. If I try pushing the power button off on the radio then shut off the engine (Tasker shuts down bluetooth) then I don't seem to have this issue with the phone crashing. I've yet to have the phone crash if it's on A/C power and Tasker performs the same function.
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for
I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful.
Magisk modules installed: Universal Safetynet
Zygisk: Enabled
Rooted apps: Greenify, GoogleDialerMod, Shizuku, Storage Isolation, BBS
fillwithjoy1 said:
I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful
Click to expand...
Click to collapse
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.
Lughnasadh said:
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.
Click to expand...
Click to collapse
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions
If it is a module just type in adb magisk –remove-modules
there's also a magisk module that disables misbehaving modules at boot to protect against bootloop it's called magisk bootloop protector
fillwithjoy1 said:
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions
Click to expand...
Click to collapse
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?
Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?
Click to expand...
Click to collapse
No safe mode is completely fine, but I will look into uninstalling Greenify and see if the problem is fixed.
Thank you! Greenify is the issue!
Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Click to expand...
Click to collapse
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?
fillwithjoy1 said:
Thank you! Greenify is the issue!
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?
Click to expand...
Click to collapse
Excellent! Glad you got it straightened out.
I find Greenify and similar apps aren't really needed these days.