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.
Hi, I recently downloaded Flashify and the TWRP img and used it. However, when I booted the .img into Flashify, my touchscreens input (the action when you tap your phone screen), not the touchscreen orientation. The Input has flipped left-right or horizontally. So lets say there are 4 apps on the dock. If i clicked the 1st one, I get the 4th. 2nd = 3rd, 3rd = 2nd, and 4th = 1st.
Please tell me how to fix this. If there is an easy way like using build.pro to somehow flip the touchscreens input because the hwrotation=180 only changed the orientation.
Any help is appreciated, thank you.
I have rebooted, Settings>Restore, Cleared cache dav cache internal storage, advanced clean through recovery
Reflash with stock 5.1.1 ROM via odin.
Can't Ive been trying. It keeps getting stuck at "Complete(Write) operation failed"
I used Odin successfully before this to update to 5.1.1 from 5.0.2
It's also recognizing my S6 as the S6 Edge
I Dl'd the driver already
Should I also be using the G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar or the G920TUVUCOF6-20150615115627.tar?
Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.
phongle123 said:
Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone
drock212 said:
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone
Click to expand...
Click to collapse
HAHAHHAHAHA!!! I looked at the one that said T-Mobile and instantly clicked it instead of actually looking at the name. It WAS indeed for the Edge, the left - right inverse does not happen anymore. This isn't fixed with a reflash or reboot or changing to correct TWRP. You need to refix it in phone>*#2663#
EDIT: To any others that have this happen. Even if you fix it with the phone>*#2663#, if you go back into the EDGE Variant TWRP it will make it back to left - right inverse. You need to change it to the right TWRP variant first otherwise going back to the wrong TWRP will mess it up again.
Thanks for that, I overlooked it.
Wanted to try Android Pay. Am a SPH-G925P on stock OH1 rooted with UniKernel v8 and TWRP. Disabled SuperSU, downloaded and installed Android Pay. Added my first card and got a message that an app was blocking screen access to the app. Thought it might be my Apex Launcher. Went back to stock TouchWiz launcher, same message. Made sure Adblock was off (it was because it couldn't acquire root). Rebooted and got softbrick.
Figured Android Pay had messed something up. Wiped cache and Dalvik in TWRP, still stuck. Restored my TWRP backup from 2 weeks ago, no joy. Reflashed Unikernel v8, still stuck at Sprint Splash.
Any thoughts on what rebooting with SuperSU disabled messed up? Next up is reflashing stock OH1 and/or factory reset, but thought there might be an easier fix.
dtndvm said:
Wanted to try Android Pay. Am a SPH-G925P on stock OH1 rooted with UniKernel v8 and TWRP. Disabled SuperSU, downloaded and installed Android Pay. Added my first card and got a message that an app was blocking screen access to the app. Thought it might be my Apex Launcher. Went back to stock TouchWiz launcher, same message. Made sure Adblock was off (it was because it couldn't acquire root). Rebooted and got softbrick.
Figured Android Pay had messed something up. Wiped cache and Dalvik in TWRP, still stuck. Restored my TWRP backup from 2 weeks ago, no joy. Reflashed Unikernel v8, still stuck at Sprint Splash.
Any thoughts on what rebooting with SuperSU disabled messed up? Next up is reflashing stock OH1 and/or factory reset, but thought there might be an easier fix.
Click to expand...
Click to collapse
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Soooperstar said:
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Click to expand...
Click to collapse
I'll try that. As expected, flashing stock OH1 fixed it. I'll get TWRP and root (excuse to go to UniKernel v9) back on and update everything and make a fresh backup before I try again. That will make it easier if it softbricks again.
Soooperstar said:
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Click to expand...
Click to collapse
Hey Sooop, just about ready to try Android Pay install again. Searching found that Lux brightness app may be the culprit for blocking screen access. Wanted to check with you. When you disabled su, which version of Unikernel and which firmware were you using? Did you disable su, reboot, install Pay, then re-enable su?
dtndvm said:
Hey Sooop, just about ready to try Android Pay install again. Searching found that Lux brightness app may be the culprit for blocking screen access. Wanted to check with you. When you disabled su, which version of Unikernel and which firmware were you using? Did you disable su, reboot, install Pay, then re-enable su?
Click to expand...
Click to collapse
I'm on OH1 and I did full unroot then setup cards then was able to use. I couldn't get it to work after rerooting. But the good thing is being that the kernel is rooted, you can use it, then simply reboot and you're rooted again. I have to unroot from the su app when I use it
Sent from my SM-G925P using Tapatalk
Soooperstar said:
I'm on OH1 and I did full unroot then setup cards then was able to use. I couldn't get it to work after rerooting. But the good thing is being that the kernel is rooted, you can use it, then simply reboot and you're rooted again. I have to unroot from the su app when I use it
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Got it. That makes sense from what Google posted about the use of their app and why it would never work with rooted devices. With the new chip embedded credit cards, and requirements for merchants to have terminals that accept them, I may just stay old school. Can't see having to unroot and reboot every time I want to use it. Although, I could probably use NFC Retag and Tasker to use my credit card to both initiate unroot and then reboot the device once I had paid.
dtndvm said:
Got it. That makes sense from what Google posted about the use of their app and why it would never work with rooted devices. With the new chip embedded credit cards, and requirements for merchants to have terminals that accept them, I may just stay old school. Can't see having to unroot and reboot every time I want to use it. Although, I could probably use NFC Retag and Tasker to use my credit card to both initiate unroot and then reboot the device once I had paid.
Click to expand...
Click to collapse
Yea I just unroot from su then pay then reboot
Sent from my SM-G925P using Tapatalk
I rooted my device and happily started debloating.
AOD (which I really do not need) also had to go, but it seems this is giving me issues with my lock screen. The issue being that there is no clock widget installed, causing me to have a lock screen only showing an ICE number. There is minimal and not being able to tell the time at a glance...
I tried re-installing, but it keeps force closing on me (cannot modify the settings, device freezes for short times). No permanent damage; but I cannot get it to work.
Tried clearing cache and data for AOD, of no avail.
Anyone know what I am missing in order to get it re-installed?
Thank you!
You'll have to dirty Flash ROM
Sent from my SM-G955F using Tapatalk
Jostian said:
You'll have to dirty Flash ROM
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Still on stock ROM; had to use Odin just yesterday to fix an issue with the Play Store (same thing; issue, had to uninstall, continued force closes).
How can I flash the stock ROM (given it is 3,5 GB)? Put it on my SD card and flash with TWRP?
Thanks.
Just download the stock ROM zip for your device and carrier from sammobile and Flash using odin using download mode on your phone.
If you were rooted is simpler, just download a stock based ROM like SolDier's and flash it through TWRP.
Sent from my SM-G955F using Tapatalk
How about installing AOD and then setting it as a system app with Magisk? There's a mod available to do that. Maybe it'll work then? Definitely worth a try before reflashing stock.
Also make sure you install a compatible version from APK Mirror. Most newer versions aren't compatible with the Galaxy S8. Go ahead and install 3.2.80.4 (that's the one I have installed on my phone right now).
Perhaps try installing that version and then try it out before going through the procedure of installing Magisk.
Hope that works for you.
see whether it disabled or no
James160103 said:
How about installing AOD and then setting it as a system app with Magisk? There's a mod available to do that. Maybe it'll work then? Definitely worth a try before reflashing stock.
Also make sure you install a compatible version from APK Mirror. Most newer versions aren't compatible with the Galaxy S8. Go ahead and install 3.2.80.4 (that's the one I have installed on my phone right now).
Perhaps try installing that version and then try it out before going through the procedure of installing Magisk.
Hope that works for you.
Click to expand...
Click to collapse
This works almost! No continued forced closes; however the screen on action takes forever (in comparison to other actions on the S8),
I am just wondering how come the re-install does not work properly. Titanium removed the APK; I install another one.
Why is AOD acting weird?