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
Related
I installed 3.75 B03 safestrap on my S5A from AT&T. After I backed up my stock rom, I noticed that Safestrap was disabled and I lost my root on my phone. Does anyone know what might of happened? I have no custom roms or that sort of thing on my device. Please keep in mind that I just switched from IOS to Android a few weeks ago and am trying to learn everything via google. Thanks for any input on this matter.
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Rakuu said:
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
citron2k1 said:
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
Click to expand...
Click to collapse
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Rakuu said:
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
citron2k1 said:
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
Click to expand...
Click to collapse
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Rakuu said:
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, I did allow root checker root access. Sorry I missed that question. Further, everything ran smoothly with busybox. I'll just keep an eye on it. I hardly ever have to reboot my phone. Its just a minor hiccup that I have to deal with for now. Thanks for your help in this matter.
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
Hello everyone... I just bought at&t note 3 unlocked version. Problem is that its on kitkat 4.4.2 and doesnt show any ota update so can anyone please provide me a link of stock rooted at&t lollipop rom which i can flash and root method with a proper guide please? I would be very thankful.
What you do is root what you have, install Towelroot https://www.androidfilehost.com/?fid=23991606952593961 (open the app and click "make it rain" and it's rooted). Install Supersu and Busybox, then Safestrap https://www.androidfilehost.com/?fid=23991606952593962, open it and install it and this is rooted lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2. Just one thing, (not saying you will) but flash the OC1 Kernel in Safestrap before you leave Safestrap. " 5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/ "
Hey Rooted, i have a 1.39gb file on my ext sd card called SM-N900A_0C1_Lollipop_Rooted_rom.zip, is it safe to delete this if i already have rooted oc1? or do i need it to flash safestrap? Also, for the past few weeks my oc1 rooted note 3 has been randomly rebooting itself in the middle of me using it, then entering a bootloop until it successfully boots up. Then sometimes when it successfully boots up, it reboots itself right when i put my password into the lockscreen. Sometimes clearing the cache doesnt help, i clear it multiple times for it to work. The other day i clicked the end button on a phone call, and right when i ended the call it rebooted itself. im lucky it didnt reboot during the call, i was on the phone with a towing company lol! Any idea whats going on?
If it's rooted, yea you can delete the file then. Do you have Xposed install, flash anything else with Safestrap, did you do a clean install of the Rom? When did the rebooting start, after you installed an app?
I do not have xposed framework installed, i heard its not compatible with the oc1 root. I never flashed any custom rom, im running just a stock rooted rom. Im not sure exactly when the rebooting started, its been going on for 2-3 weeks, i cant remember what i did before that. Last night i swapped sd cards to make sure it wasnt that, but i already had 1 random restart today. Do you think swapping sim cards is a good idea?
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
I have the same problem?? Did you get any answer from any body? Do I have to re root again?
Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem
Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.
WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.