Database Develop

[Q] Custom Device Status

I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.

mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Once you rooted you customized the software. That custom padlock logo is a tattle tale telling on you! I believe your using an xposed module to "fake system status" in order to fool certain people. The xposed module is failing when you see this. It's possible an update, or setting was applied to the module making it fail. Or maybe it's losing it's superuser rights. I had the same thing happen to me. I used triangle away and haven't seen it again. It will surely come back on a factory reset I'm sure.

This happened to me as well and I know its not the xposed because I checked it. This has only happened 3 times and has not happen in like 4 days I checked my system and it says everything is official it did say custom the 3 times it happened I did do a factory reset and it still says official my question is has anyone found a way to unroot for warranty porpoises? Su will not unroot towelroot from what im seeing ...but if everything says official would you even need to worry about unrooting lol I mean if u just factory reset and sent it back I shows no sign of root its all official and no knox tripped ..just a thought ..

Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Sent from my SM-N900A using XDA Free mobile app

Freezing "sysscope " on my sgs4 removed the custom unlock boot logo /icon like a charm, however it still bounces back and forth between official and custom on device status when looking.

mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Remove "busy box" file in XBIN system folder. Found this solution on a "Galaxy S4" forum. For a some reason a system keeps some leftovers after the full recovery done. Kinda wrong.

SuperUser no binary

I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!

Muscle Nerd said:
I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!
Click to expand...
Click to collapse
You are not rooted then. Try again.

12MaNy said:
You are not rooted then. Try again.
Click to expand...
Click to collapse
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?

Muscle Nerd said:
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?
Click to expand...
Click to collapse
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.

_Dennis_ said:
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.
Click to expand...
Click to collapse
I don't get that pop up. But my device does reboot.
I tried opening SuperSU prior to PingPong, but it only has the original error 'no binary'. After you press okay, it prompts you to installing SuperSU once again? Odd... Once you install the 'new version' and open that, it'll automatically open PingPong. From there I select 'Download data' then 'Get Root!'. Which then tells me to wait with a popup, and that is when my S6 reboots.

Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)

_Dennis_ said:
Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)
Click to expand...
Click to collapse
Thanks for the prompt response Dennis!
I opened PingPong, canceled the install of SuperSU, then selected 'Get Root!'. Says my device is not supported (Though it is in the thread for PingPong). I select download data, (Says Device updated, please try Get Root again.) then I select get root. Unfortunately it reboots my S6 after about 2-4 seconds. I'll keep trying!

Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.

_Dennis_ said:
Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.
Click to expand...
Click to collapse
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?

Muscle Nerd said:
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?
Click to expand...
Click to collapse
That reminds me, what version are you using? Beta 6 or a different one?

_Dennis_ said:
That reminds me, what version are you using? Beta 6 or a different one?
Click to expand...
Click to collapse
Beta 6
Edit* Uninstalled both applications, and installed the 5.1 beta. When I select download data, it says to retry the Get Root as usual. Then I select Get Root, and it says 'Your device data is still not supported'.
Here's the quote from Idler in the thread. With option C. he says to possible do a factory reset? I have all of my contacts & photos backed up via my pc. Should I possible try and do a reset? Or do you think it's a waste of time.
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.
If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Click to expand...
Click to collapse

Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.

_Dennis_ said:
Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.
Click to expand...
Click to collapse
I have the G925AUCU1AOE2. I've tried all of those aside from the reset

Muscle Nerd said:
I have the G925AUCU1AOE2. I've tried all of those aside from the reset
Click to expand...
Click to collapse
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.

_Dennis_ said:
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.
Click to expand...
Click to collapse
Haha, no worries! I will give that a go.
Yay or nay towards a reset? I have a feeling I'll go through the hassle of resetting my phone & I'll have the same error.

Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately

_Dennis_ said:
Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately
Click to expand...
Click to collapse
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:

Muscle Nerd said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.

_Dennis_ said:
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.
Click to expand...
Click to collapse
Will do, thank you!

Tom Dsgn said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
How do i root my s6 been trying for weeks

Kernel is not seandroid enforcing set warranty bit: kernel

So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT

Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .

This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk

danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made

danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0

Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk

Root won't "stick"

I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??

Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.

Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...

I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app

Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?

Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..

Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?

Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...

Thanks! I'll give that a try when I get home today.

S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!

Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...

Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app

marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.

https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app

Unable to unlock my lock screen after installing xpoosed.

Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.

Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk

bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?

Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk