Related
I thought I'd just stick this up here as a little warning to others. I have a N9005, stock rom but rooted with cf autoroot. Had phone a month with no issues what so ever, 3 days ago I decided to put xsposed on there and find some some modules. Before I found any I got a warning saying sd card umounted so decided to try sort that out. I then quickly found out the power button had gained a 5 second delay from press to any responses. Next the dialer keeps freezing and when I'm on a call the proximity sensor won't turn the screen back on for 10 seconds after I move phone away from my head. Most annoying of all is the clock app has just totally derpt. Got no alarm clock at all and clock widget keeps saying I'm in Israel!! The sd card seams to be totally dead as neither my sensation, G nexus or pc will read it now and my backups are on it so I guess today's job is finding stock rom and starting from scratch again.
All this may just only happen to me but I thought I'd put it out there as a little warning
shottle said:
I thought I'd just stick this up here as a little warning to others. I have a N9005, stock rom but rooted with cf autoroot. Had phone a month with no issues what so ever, 3 days ago I decided to put xsposed on there and find some some modules. Before I found any I got a warning saying sd card umounted so decided to try sort that out. I then quickly found out the power button had gained a 5 second delay from press to any responses. Next the dialer keeps freezing and when I'm on a call the proximity sensor won't turn the screen back on for 10 seconds after I move phone away from my head. Most annoying of all is the clock app has just totally derpt. Got no alarm clock at all and clock widget keeps saying I'm in Israel!! The sd card seams to be totally dead as neither my sensation, G nexus or pc will read it now and my backups are on it so I guess today's job is finding stock rom and starting from scratch again.
All this may just only happen to me but I thought I'd put it out there as a little warning
Click to expand...
Click to collapse
I have been using xposed for about a month since i got my Note 3. Never had any issues. So this happened even before you installed any modules?
Well xposed had been known to be tricky. Most times it works, sometimes it messes up and sometimes it gets you into a boot loop.
Yeah, was scrolling through the modules to download when the sd warning came on and all the other problems have since followed. Just want to note that I haven't installed anything else since Xposed and had no issues before installing
You installed the latest xposed version right? The previous ones are not compatible with 4.3. I've been using it with no problems.
Sent from my SM-N9005 using Tapatalk
Yeah, the latest version. What is really confusing me is why it's getting my location as Israel constantly. Doesn't matter if I'm on wifi or 4G
shottle said:
Yeah, the latest version. What is really confusing me is why it's getting my location as Israel constantly. Doesn't matter if I'm on wifi or 4G
Click to expand...
Click to collapse
The next logical question would be - Have you tried uninstalling it to see if the issues go away? If they do go away, try reinstalling it and see if you experience the same thing.
I've been using Xposed with the Wanam module and don't have any issues.
Have uninsulated. Made no difference. Factory reset made no difference either. Just had a full wipe and flashed clean stock rom. Will see how that does then will know if all is fixed
Ive had similar issues with xposed myself
~hy from germany~
Not all Xposed module is working in every phone.
You should name which Xposed framework module give you problem.
So far I using Xposed framework till now fine and not much issue.
I only use few module:
App Settings - 100% working.
Wanam Xposed - theming is working, hide smart stay, blocking mode and etc is working but not all example center clock not working since MJ6 firmware as it will give you FC after end call.
Instagram Downloader - 100% working.
Andrewtst said:
Not all Xposed module is working in every phone.
You should name which Xposed framework module give you problem.
So far I using Xposed framework till now fine and not much issue.
I only use few module:
App Settings - 100% working.
Wanam Xposed - theming is working, hide smart stay, blocking mode and etc is working but not all example center clock not working since MJ6 firmware as it will give you FC after end call.
Instagram Downloader - 100% working.
Click to expand...
Click to collapse
I never installed any modules
victorlht88 said:
Sounds more like a hardware issue.
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
It's simple. Your device is hacked by mossad.
Just to say, after a full wipe and clean flash back to stock rom all is normal again. I'm guessing just got unlucky with xposed this time. Not sure if I'll be in any rush to try again for a little while
I have xposed with a lot of modules, but xblast and 3 dot menu modules cause troubles, screen freezes and ui stops working
Mine, if this helps anyone (I've never had any problems):
App Settings
Boot Manager (Amazing)
Disable Clear Defaults Dialog
GravityBox (I disabled for messing something up - tread carefully)
GreenYoutube
NotificationMod
NotifyClean (Amazing)
Per App Hacking
Play Store Fixes
ReceiverStop (Amazing)
Tinted Status Bar (Great)
Wanam Exposed
XBatteryThemer
XBlast Tools (Great, but tread carefully)
XHaloFloatingWindow (I've not managed to get working)
Xposed Recent Tasks
What is the make of the SD card that failed? Was it SanDisk?
shottle said:
Just to say, after a full wipe and clean flash back to stock rom all is normal again. I'm guessing just got unlucky with xposed this time. Not sure if I'll be in any rush to try again for a little while
Click to expand...
Click to collapse
How do you do your full wipe?
columbo said:
What is the make of the SD card that failed? Was it SanDisk?
Click to expand...
Click to collapse
No, was a Samsung
sofes said:
How do you do your full wipe?
Click to expand...
Click to collapse
Through TWRP
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
how?
jamespat93 said:
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
Click to expand...
Click to collapse
Can you tell me how did you solve it w/o reseting your phone?
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
thnx
thnxx got it!
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
All I had to do was reboot my phone and luckily (even though the message was still coming up) I could still use the touchscreen. This allowed me to go to the motoXposed module that caused the problems and undo the options I changed.
Unfortunately the process com android.systemui has stopped. Xposed Installer
Does anyone has any clue about this:
I have been having the same issue with my Galaxy S5.
I am using the rooted stock ROm with touchwhiz.
The issue started after I installed Xposed Installer with Wanam Xposed.
The "unfortunately the process com android.systemui has stopped" message does not come on until I received phone call while the phone is active. If I receive a call when the screen lock is on, the phone behaves normally.
The other issue I'm having with Xposed Installer are
1) a noticeable increase in lagging
2) apps takes close to 10 minutes to install
3) It takes a long time for the computer to see the phone after connecting them with USB....sometimes up to 15 minutes. thereafter it was not taking as long, but it was still being delayed.
I have flashed the phone three times with roughly the same observation after each flashing (i.e. issues cropping up only after installing Xposed Installer and some modules)
I'm going to try system tuner now...
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
edwardciasico said:
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
No I did not. I factory-reset the phone. Did not install xposed installer again and It's been working well since then. However, I'm still going to try it one last time...I'll keep you posted
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
jimnu said:
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
Click to expand...
Click to collapse
Which offending apk please?
ekitiboy said:
Which offending apk please?
Click to expand...
Click to collapse
In my case it was motoxposed.apk but YMMV.
sry for doublepost
To fix the systemui-crash u need to disable the (new):
"Heads up notification" on Wanam !!!
Help
I recently rooted my phone with TWRP using Odin. I did a few small things in customizing (ie: font, rotate screen) and now I get this error message.I've tried to boot in recovery and it just constantly flashes the Teamwin logo screen and i get no where. Could really use some help here, cannot use my phone at the moment
i have this issue too
I have this with Orbot. Simply restarted the phone and made a speed-run to uninstall it. Works to me.
So, the main question is: why this happen?
marc_miranda said:
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm facing the same problem i'm unable to use my phone, kindly explain in details how to flash xposed recovery.
the problem appeared after installing an xposed mod.
[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!
Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.
i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
I have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
After I deleted all the Knox apps my random rebooting quit.
1seniorgeek said:
After I deleted all the Knox apps my random rebooting quit.
Click to expand...
Click to collapse
What Knox apps are there? I didn't download any. What did you use to remove them?
On the sidenote, I seemed to have borked my root by trying to uninstall SuperSU (it hanged) and I did a hard reset. Now I need to find the binary... Assistance greatly appreciated! Or would it be easier to do a factory reset and start from the beginning?
CyberDie21 said:
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
Click to expand...
Click to collapse
Do you mean this one? http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053/post24267797
CyberDie21 said:
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
Click to expand...
Click to collapse
I installed both of which you mentioned. By experimental options, do you mean: Disable resource hooks? If not, I don't see the option... Thank you for your help!
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Makoto1 said:
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Click to expand...
Click to collapse
Drat. It reboot on me this morning. I had it plugged in from charging overnight and I flipped my screen cover open to wake it up and it froze and rebooted.
Anyone have any tips? I would flash the stock USA rom and start from scratch if I could find the rom. Would a factory reset from recovery mode bring me back to stock pre-SU? Should I have SuperSU close root before doing a factory reset? Thanks.
Makoto1 said:
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Click to expand...
Click to collapse
Hello, I solved by deleting the Knox files that are located in some folders of /system.
roys_ said:
Hello, I solved by deleting the Knox files that are located in some folders of /system.
Click to expand...
Click to collapse
Thanks, I'll try that if I still get the reboots. Last night I did a factory reset and was able to get the prompt for SuperSU to ask about disabling Knox (which I hit cancel). So far no reboots. I'll be slowly building my app collection to see if it may be related to an app.
Well, did it work? I am having the same issue and I am not sure if I should go back to stock and not disable Knox with SuperSU or I should remove Knox all together. This is driving me batty. Thanks in advance.
Knox is the problem
Makoto1 said:
I have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
Click to expand...
Click to collapse
I have a Galaxy Tab Pro 12.2 rooted with Chainfire stock rom. I started getting random reboots soon after root and yes I did select yes when super su asked to disable knox. Never had a problem with this on a Note 4, S5, or Note 8.
I tried most of what everyone has discussed except re-flash and factory reset. I also uninstalled super su, enabled knox, re-installed super su. But this time super su did not ask to disable knox.
Re-enabling knox did not stop it. I installed xposed server crash tool and got the following in xposed logs when it would prevent a crash:
0:com.sec.knox.seandroid/1000
I then used terminal emulator to disable:
Su [enter] (this brings up super su authorization window, select enable)
PM disable com.sec.knox.seandroid [enter]
You can also disable in settings > security > device administrators > uncheck knox
This did not work, I was still getting the same crash report. So I decided to completely remove knox, not just disable it since there are several modules that work with the knox app.
I used System App Safe Remover for rooted to remove. It backs the files up on your SD card versus just delete so you can later restore if necessary.
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
Select these files and unistall them.
Reboot and you are done.
Now, no more random reboots. I hope this works for you.
My Fix
Makoto1 said:
I have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
Click to expand...
Click to collapse
I fix the problem by plugging in achager. Looks like it a battery problem. Minestarts rebooting and flikkering when my battery drops below 30%.
same here
tykenicol said:
I fix the problem by plugging in achager. Looks like it a battery problem. Minestarts rebooting and flikkering when my battery drops below 30%.
Click to expand...
Click to collapse
hey there, i Thought i was the only one. when my battery is bellow 30% the tablet begins to constantly reboot after the samsung logo logo. i found that it only happens when is on battery because i do heavy multitasking tests with the charger plugged and works perfectly, but a simple app when in battery makes the device crash. also found a perfect app to make the tablet crash and it is camera fv-5 (when in battery and bellow 30%), currently using ver 2.68. has anybody the same problem. did you fix it tykenicol?
meneses.leonardo said:
hey there, i Thought i was the only one. when my battery is bellow 30% the tablet begins to constantly reboot after the samsung logo logo. i found that it only happens when is on battery because i do heavy multitasking tests with the charger plugged and works perfectly, but a simple app when in battery makes the device crash. also found a perfect app to make the tablet crash and it is camera fv-5 (when in battery and bellow 30%), currently using ver 2.68. has anybody the same problem. did you fix it tykenicol?
Click to expand...
Click to collapse
You can try this: add some thing thick like paper on top of the battery connector and secure it with a tape. A direct pressure from the rear cover to the battery connector stops the problem, then you have a cracked solders of battery connector. A simple re solder this connector will fix your problem.