Hi guys, I posted this elsewhere, but hopefully this helps everybody.
After rooting my Verizon SCH-I545 on NG6(I545VRUFNG6), I experienced tons of random crash/reboot issues, and finally found a solution last night!
This requires Xposed Framework to work of course.
Download the Xposed Module- "Samsung KitKat systemserver crash fix". It says it's for a different version but it has stopped every crash/reboot and I'm on the Verizon NG6 update.
The processes that are causing the crash/reboot are the 7 Knox processes. If you would like to remove these, backup your phone, then uninstall all Knox processes with an app like Titanium Backup or a similar app that can delete system apps.
Links:
"Samsung KitKat Systemserver Crash Fix" -http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
Repo Link- goo.gl/K4Po6Y
Download Xposed Framework- http://dl.xposed.info/latest.apk
Big thanks to @thomashofmann for the module.
This is my first thread, so let me know what you think!
Sent from my SCH-I545 using XDA Free mobile app
Any idea how to read the log file, or where it's at. I got two notifications that it stopped the phone from rebooting/crashing. It said it had to do with a Knox process.
Here's the notification.
There is a log feature in Xposed, and you'd just have to look for the details that the notification gave.
Another suggestion for fixing the reboots is to freeze the processes that are causing the crashes, since most of them are Knox related processes.
Sent from my SCH-I545 using XDA Free mobile app
Freezing is not enough! You must deinstall all seven Knox pieces.
MfG/best regards
René
(Send with SM-T805)
BigBugHmb said:
Freezing is not enough! You must deinstall all seven Knox pieces.
MfG/best regards
René
(Send with SM-T805)
Click to expand...
Click to collapse
To uninstall them, I'd recommend using something like NoBloat to backup and uninstall them.
Thanks for the tip.
Samsung Galaxy S4 SCH-I545 Rooted NG6
I used Titanium Backup. That's ok too.
BigBugHmb said:
I used Titanium Backup. That's ok too.
Click to expand...
Click to collapse
Same here. If the reboots are gone I'll let you know tomorrow.
I tried this fix and it seems to help. Three 'modules' appear to still be failing but the patch is at least keeping the fone from rebooting. Can provide additional details (log file) if it would help anyone?
It work for me.... Thw xposed module and delete knox apks from system priv app and then unistall knox apps with root unistaller....
Deleted the 7 knox apps and one com.sec.knox..... also. This has got rid of all reboots.
Used Titanium Backup to delete them.
Sir_Eagle said:
Deleted the 7 knox apps and one com.sec.knox..... also. This has got rid of all reboots.
Used Titanium Backup to delete them.
Click to expand...
Click to collapse
This also seem to work for me. But what i did is freeze all of them wit the called app quarantine.
Edit: reboots continue to happen. Installed xposed and the samsung Kitkat crashserver fixer and problem fix. Thank u for all the links. Phone seems a lot more stable now.
S4 i545
-I updated the OTA NG6 and experienced the random reboots.
-Emailed the Verizon regional President, rcvd callback within hours, they verified I did the FRB so sent me another phone (Factory Refurb).
-Phone arrived with NC5, s I did the OTA again and got the same random reboots.
-Did the ODIN NC5 kernel. Towelroot, Odin NG6 krenel rooting process successfully.
-installed Titanium Backup, FROZE all files having KNOX.
-So far random reboots have stopped.
Thank you Verizon Executive office of the President Eastern states, but the problem seems very clearly associated with the KNOX software...
This was exactly what I did with the exception of getting a new phone. I froze all Knox apps, but continued to get reboots. Odin back to NC5, root, and has been fine for a week.
zakkxx said:
This was exactly what I did with the exception of getting a new phone. I froze all Knox apps, but continued to get reboots. Odin back to NC5, root, and has been fine for a week.
Click to expand...
Click to collapse
Freezing them doesn't work as you found out. If you delete them the reboots go away.
Wrong post sorry
Could someone please list the 7 Knox files to remove in NoBloat? I went through the whole process last week and after deleting every file with "Knox" in it my device was bricked. I had to flash a stock version of NC5 to get it running again, but now Verizon is forcing me to update.
pattysal said:
Could someone please list the 7 Knox files to remove in NoBloat? I went through the whole process last week and after deleting every file with "Knox" in it my device was bricked. I had to flash a stock version of NC5 to get it running again, but now Verizon is forcing me to update.
Click to expand...
Click to collapse
Here's what I deleted:
Sir_Eagle said:
Here's what I deleted:
Click to expand...
Click to collapse
Thanks! I uninstalled exactly as shown in Titanium Backup, powered down, powered back up, and no problems to be seen. I hope it stays that way
My first attempt must have bricked my phone because I just deleted a bunch of files, rather than uninstalling the actual apps. But thanks to the interwebs, I don't have to buy a new phone. Suck on that Verizon/Samsung.
Will simply deleting the KNOX apps in TI backup work or will I need to use the xposed fix as well? I don't have the ability to run nandroid so I got nervous at the prompt xposed gave stating that the device may not boot after it is installed.
Related
Hello there! i'm making my forum debut while extremely confused as to how to proceed with fixing my Verizon Galaxy S3, running the stock android JB 4.3. So there is no custom ROM.
I realize that this may or may not be similar to a plethora of posts about apps crashing around the time android 4.3 was released but i've upgraded to 4.3 less than a month ago. After diving through countless forums, i couldn't find one that addressed the same problems that my device had. They were all similar, but the solutions posed in those threads did not work with my device. Plus the problems i have are not isolated to one app.
I had just recently upgraded to android 4.3 which had unrooted my previously rooted device. After using Chainfire's method of rooting the SCH-I535, utilizing saferoot, i then installed the Xsposed Framework and that was really where my troubles began. A few days had passed while i was tinkering with a few modules like XBlast tools, XHaloFloatingWindow, Xposed Torch, and Wanam Xposed, and i had a good sense of what mods interfered with other mods and it was only last night when the problem first arose.
Without warning, a game that i play all the time stopped working. Literally in the time span of 6 hours (i was sleeping) something happened and the beginning of my problems started. Every time i would open the app, the app itself would close and i would get a message saying, "Unfortunately, Valkyrie Crusade has stopped." It was only a few hours later did i realize that Pandora, an app i use every day, suddenly stopped working and provided me with the same message. There was no error ID, and clearing the cache/data, reinstalling the apps, did not work. Once it became 4-5 apps that i normally use to get the message, i tried uninstalling the mods as well as the xposed framework but that also did not work. I also tried restoring the game as well as the other apps to a backup i'd made just the week prior with Titanium Backup but i still had the message coming up and the apps still did not work.
As a last resort i did a factory wipe/reset. During the initial set up, i opted to allow google to restore my apps (which i'm not sure i should have done) and after everything was restored, i tried using the apps, and i was met with the familiar message "Unfortunately, (app) has stopped.". I have run out of ideas. While i'm more tech savvy than most, i'm really just a novice when it comes to Android. How should i approach my next step? If anyone needs logs or anything like that, if you would be so kind as to walk me through the steps to get them.
Thank you, thank you, thank you in advance.
EDIT - 2/10/14
I have successfully resolved the issue (or at least, removed it) from happening. I bricked my phone but thankfully i was able to get into download mode.
Follow this guide! http://forum.xda-developers.com/showthread.php?t=2586319 - just be aware, this will delete all of your apps. backup all your propers and jump in.
This is the only method that i had success with. Other methods i tried are explained above and in the comments. Good luck and i hope everything works out!
If you had the Xposed frameware installed and you also installed Wanam xposed, this will help if you are experiencing apps crashing. I'm no expert, but i'm really glad to have resolved this as quickly as possible. I couldn't have done it without everyone! You guys literally kept my sanity healthy during this whole ordeal.
*NOTE* - The link to the guide above will lead you to a stock rom of android 4.3 for the SCH-I535. I'm not sure about other samsung devices but one user had success with a SCH-I605 (galaxy note 2) in the comments.
*ANOTHER NOTE*- i'm not in any way explicitly saying that the xposed framework and wanam xposed module are the cause of this glitch. Frankly i have no idea. But they seem to have been problems for a few people, myself included. If you want to explore this further, i'd suggest going to each of the respective forums. For me, i'm going to make sure i have a proper Nandroid before i do anything crazy. Lesson learned.
Again, Thank you!
PS- since i'm newer to this forum, i have no idea how to edit the title of this Q....haha if someone could let me know....that would be great.
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
daoist said:
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
Click to expand...
Click to collapse
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
awstuder said:
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
Click to expand...
Click to collapse
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
ATGkompressor said:
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think i'll try that next. I used to have TWRP but had to flash the stock recovery just to upgrade to 4.3. I'll try to get a clean copy of stock OS, flash and just start over from scratch. I'll be sure to let you guys know if i got it to work.
ran into a bump in the road. flashing a stock copy of android 4.0.4 did not work. Browsing through a few forums informed me that i'm unable to downgrade after i've taken the 4.3 upgrade. so next i tried to flash TWRP to boot into recovery mode and flash a rom from there. That didn't work either. I kept getting an authentification error.
As of now i can't get into download mode anymore. I get the yellow triangle saying Verizon detects unauthorized software. I'm able to get into recovery mode but i'm not sure what i can do with stock android recovery....
what can i do from here?
EDIT: I am able to get into download mode. I'm not sure why i wasn't before and now i am...
EDIT2: I have tried flashing the "official" stock android 4.3 but it fails everytime. I have also tried flashing twrp and cwm but i get a red Secure Check Fail: recovery. I suspect the bootloader has been locked. I'll look into ways of getting it unlocked again...
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
awstuder said:
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
Click to expand...
Click to collapse
Same here. Disabling all xposed modules didn't work. Disabling xposed entirely didn't work. Doing both and then uninstalling didn't work. My guess is that along the way either xposed or wanam xposed made some sort of change that it can't roll-back when it's disabled/uninstalled.
I resorted to taking a TiBu update of everything and reflashing.
Once I get my battlestation fully armed and operational I plan on taking frequent nandroids and seeing if I can replicate the issue. Once I do that, (if I do) I can compare the last known good nandroid to see what messed up.
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't able to do this right away since had class in the morning but as soon as i got home, i did this and it fixed my soft-bricked phone.
thank you thank you!
Now back to the problem at hand......let's see if the problem still persists.
It's completely fixed! No apps (so far :fingers-crossed have crashed and i'm able to happily play my games again! sigh. that was refreshing.
Thank you to everyone! i will edit my first post to outline what i did and how i fixed it, finally....
during saferoot process your suppose to update SU then continue with finishing up the root process..took me several hours to figure this out..no errors now since I figured this out
Sent from my SCH-I535 using XDA Premium 4 mobile app
That... Actually makes sense. When I used safe root I didn't check for any other updates because I assumed the program took care of that for me. That and because when I opened su there were no notifications to update. So maybe that could be a solution as well.
Sent from my SCH-I535 using xda app-developers app
I picked up an AT&T 4G LTE Note Pro (SM-P907a) yesterday and so far I am absolutely loving it. And though this is my first post, I am no stranger to XDA, I currently have Galaxy S4, Note 3, Note 10.1, and now the Note Pro, all are rooted running custom roms, minus the Note Pro. I have never hade to make a post before because I understand how to use the search function and have always been able to find the answersI have needed, until now. I am hoping someone can tell me if it is possible yet to root AT&T's version of the Note Pro 12.2, SM-P907A? Will CF auto root for the Verizon SM-P905 work? Or am I simply to ahead of the game and need to wait for root to become available? Thanks!
Same here. Just got mine. Want to use about 3 apps that require root. It's only been out one day. At&t probably didn't add anything to what Samsung did as far as locking the bootloader. All I really want at this point is root, I don't need a new room yet. Yet
Based on how long the Verizon variant users have been waiting. .. come back in September. In all seriousness though, I hope you folks don't have to wait that long...
Sent from my SM-P900 using Tapatalk
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
thanks
AboveAverage said:
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brilliant!!!! thanks. I am installing busybox as I type this :laugh:
EDIT: haha spoke too soon, SuperSU won't install. Do you know how to get a custom recovery on it when rooted this way?
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
jmedlin said:
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
Click to expand...
Click to collapse
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine has been running smooth, no reboots no freezing nothing. And yes unzip the file and SuperuserSU.apk is inside.
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine is. But it was actually worse before root.
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
I've had a couple of reboots.. what is weird is that it flashes to the at&t logo the my lockscreen. When I unlock it its like it rebooted but it happens so fast.. I am not sure if its a system reboot or just the user session crashing...
phirestalker said:
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
Click to expand...
Click to collapse
When I reboot now I see this custom android and unlocked logo at the bottom of the screen. What I am unsure of is if it had this before I rooted.
If someone who based rooted their 907a reads this please check if you get this on a bootscreen during a restart.
I would like to hear from a couple people how their tabs are doing after root. I'm thinking about doing it.
My AT&T Note Pro 12.2 keeps rebooting. My WiFi only 12.2 restarts when attempting towel root and never patches the necessary files. My AT&T Note 3 was flawless though. 1 out of 3 ain't bad I guess. Really just want the ad block ability. Is there an unroot so I can get my tablet to stay on more than an hour?
Me and my friend both got the att 12.2.
After rooting I've had reboot issues while he hasn't. So I've been slowly uninstalling programs that I use and he doesn't. Thinking it might be one program or another or a combo of programs. First I uninstalled Greenify to no effect. Next I switched back to the Samsung launcher from Nova Launcher Pro. So far its been two days without a reboot since switching back to the touchwiz launcher.
I ran Nova launcher fine before root.. And my friend with the exact tablet rooted the same way has had no issues..
Are you running a launcher different than Samsungs?
Ill report back.. but so far so good.
That's a very good point. I'm using the stock launcher still but I do have a ton of apps. I'll have to try deleting some see if that has any affect.
Ok, some added details on my "rebooting" although it doesn't show the samsung logo, so I don't think it is a full reboot.
I have noticed that the only time it happens is when I lock the screen or when it locks itself. Sometimes it has been locked for a while and it will randomly do it. I don't believe it has ever happened while I was using it. Oh, and a few times it happened while unlocking the screen. So it all seems to be related to the lock screen. I don't have any apps that add functionality to the lock screen. I have a pattern unlock and Smart Stay enabled (although this never worked for me, maybe my face is too weird to be detected? Lol). I am going through the process of turning off things to see what might be causing the problem. The first thing I disabled was the LastPass accessibility extension. I will give it a day or 2 but I have been playing around with locking and unlocking with various apps open as i write this and I haven't had a "reboot" yet.
I noticed that another poster had trouble with a different app and like him this trouble started after I rooted it. The LastPass accessibility extension worked fine before rooting. I will tell you what this extension does and maybe it will help us narrow down what area of the system has been changed to be incompatible with certain software.
The extension "watches" for password entries on apps and webforms and offers to autofill with saved passwords.
Sorry for the long post, hope it is helpful to someone.
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
muzzy996 said:
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
You're right, after a while it started doing it again. I guess it didn't happen as often as I thought. I really hope someone comes along who knows how to diagnose crashes to find out what is causing them.
I've been getting reboots also every once in awhile on my sm-p907a it reboots.I also tried safe strap recovery for the at&t samsung galaxy note 3 version 3.75.It seems to be working I did a nanoid backup and it successfully worked but took awhile. I didn't do a restore because I don't want to mess anything up until there's a stock Odin firmware download to restore if something goes wrong.The dpi is of but u can c almost the whole recovery screen if anyone wants to play around with it
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.
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.
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
The same thing happened to me out of nowhere. I've read elsewhere of this happening to other people. I don't know what causes it. A clean install should fix your problem, but no telling when or if it will happen again.
Sent from my SM-G930T using Tapatalk
MacTheRipperr said:
The same thing happened to me out of nowhere. I've read elsewhere of this happening to other people. I don't know what causes it. A clean install should fix your problem, but no telling when or if it will happen again.
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
You were rooted right? has this ever happened while you were stock?
I was rooted, the only thing that may have been different than the op, was the I had xposed installed. But as I said. After the clean install of the most recent firmware the crashes and boot loop stopped ave battery life improved as well. Also this has never happened to me until I rooted my device.
Sent from my SM-G930T using Tapatalk
btort1 said:
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Click to expand...
Click to collapse
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.
Corwinder said:
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.
Click to expand...
Click to collapse
how long have you been rooted and without any problems? that thread has tons of pages, are you sure this works 100%? its security policy updates 4.1.69 right?
btort1 said:
how long have you been rooted and without any problems? that thread has tons of pages, are you sure this works 100%? its security policy updates 4.1.69 right?
Click to expand...
Click to collapse
lol No I'm not sure it works but someone else is sure it works. I'll be honest with you. This is my third attempt at rooting this phone. I rooted when the option first came out and 1 week later I got bootlooped so I went back to stock and rerooted. A week later bootloops. That's when I gave up until more information surfaced on my problem. And behold it did. That's when I learned about freezing the security policy update. And it makes sense to me too.
Corwinder said:
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.
Click to expand...
Click to collapse
Corwinder is absolutely right. I read through that thread as well. AS SOON as you take that POLICY UPDATE that it tells you to accept, you're done. From that point on its only a matter of time before you experience a BOOTLOOP. NEVER UPDATE THE SECURITY POLICY WHEN IT POPS UP. DISABLE SECURITY POLICY. Haven't had a bootloop in 4 days now.
Corwinder I'm actually on my third root as well, hah. Third time is a charm. I just want to restate that it's not just disabling security policy.... If you accept that security policy update pop up which happens probably ~5mins after you rooted, you're going to bootloop. You can also disable security policy updates in settings. Do this as soon as you root. Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.
Thank you guys for this thread / help.
Woke up today and wanted to see what offers were available on T-Mobiles Tuesday App. Said that the app needed updated, then Google.playstore keep crashing. Reboot phone and ran into the famout bootloader screen / process.
Saw this thread days ago and followed the steps and I "think" im good now.
Step that I took :
Reflashed PG1 through Odin v3.12 (Prince Comsy)
Reapply root / SuperSU
Disabled security policy settings by going to Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.
Downloaded TitaniumBackup / Flashfire
Applied fix+debloat script via Flashfire
Deleted more Bloatware through Titanium Backup.
Enjoying fast, responsive phone
#rooton
Eighthourblink said:
Thank you guys for this thread / help.
Woke up today and wanted to see what offers were available on T-Mobiles Tuesday App. Said that the app needed updated, then Google.playstore keep crashing. Reboot phone and ran into the famout bootloader screen / process.
Saw this thread days ago and followed the steps and I "think" im good now.
Step that I took :
Reflashed PG1 through Odin v3.12 (Prince Comsy)
Reapply root / SuperSU
Disabled security policy settings by going to Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.
Downloaded TitaniumBackup / Flashfire
Applied fix+debloat script via Flashfire
Deleted more Bloatware through Titanium Backup.
Enjoying fast, responsive phone
#rooton
Click to expand...
Click to collapse
It won't remove com.dmpolicy but if you disabled it you're fine.
nwg5817 said:
It won't remove com.dmpolicy but if you disabled it you're fine.
Click to expand...
Click to collapse
its not coming up in Titanium Backup, is there another way to make sure its disable / deleted?
nwg5817 said:
It won't remove com.dmpolicy but if you disabled it you're fine.
Click to expand...
Click to collapse
edit