DROID BIONIC
Android Version: 4.0.4 ICS
System Version: 6.7.246.XT875.Verizon.en.US
So i finally rooted my phone and got superuser. But the method didn't give me a safestrap or bootstrap file to download.
I went online and have dowloaded multiple safestrap apk files (1.0, 2.11, 3.1) and they all said they run on ICS. So i install then and when i go to run them it prompts me and says "unfortunately, safestrap has stopped." and it's followed by another little pop-up that says "Safestrap has been denied superuser permissions." So i can't get into recovery to flash any roms. I'm not sure what to do.
I've tried to wipe the data, caches, and restore my phone, nothing helps. And i made sure my USB debugging is on. But after everything i've tired all my recovery apps still force close and don't get permission. I've also tried to flash my roms using the stock recovery and nothing happens.
I also downloaded titanium back-up and when i go to open the app it notifys me that it doesn't get root permissions, that my phones not rooted. Now with the ICS update theres a Root Check in the stock recovery and it reads “qe 1/1″- so that tells me i"m rooted. So i'm not sure there.
I don't know what to do. Maybe i'm missing a few steps. If anyone could help me out and point me in the right direction, i'd appreciate it.
Thanks in advance!
I got same issue
Did you get it resolved. I spent all afternoon only to be rooted but unable to acess recovery. any elder statesman that have any answers?
No, i haven't fixed the problem yet. Was hoping someone could help me out
This is what happens when i try opening any safestrap app i install.
I would suggest PM Hash code, he created the SS apk, if any one has the answer he would
Sent from my BNTV250A using xda app-developers app
I'm sorry, but who is that? Can you give me a link to his profile please? I'm kinda a noob to this rooting stuff. Hence the problems I'm having lol
Safestrap
Which version of Safestrap did you try? I prefer 3.1 as it has touchscreen capabilities. Do you by chance have bootstrap installed? This could be giving the error.
---------- Post added at 08:26 PM ---------- Previous post was at 08:18 PM ----------
For the safestrap failing to be granted super user access error, you should be able to manually 'whitelist' it in your superuser application. If that does not work, you might want to try a different root program. I tend to use SuperSU, as I enjoy the features, and the realiability.
I tried the versions listed- 1.0, 2.11, 3.1
None of those worked. And no, I've never had bootstap installed. And what's the "whitelist"? I've never messed around with the superuser app, I've only just checked the log and see all my root apps get denied (titanium, safestrap, etc.)
And for the other root method: I'm not sure how to do any other methods, or even find any for that matter. I know my phones rooted, it tells me in my stock recovery.
If anyone could help me out by posting links, that'd help A LOT!
SuperSU
Castronova said:
I tried the versions listed- 1.0, 2.11, 3.1
None of those worked. And no, I've never had bootstap installed. And what's the "whitelist"? I've never messed around with the superuser app, I've only just checked the log and see all my root apps get denied (titanium, safestrap, etc.)
And for the other root method: I'm not sure how to do any other methods, or even find any for that matter. I know my phones rooted, it tells me in my stock recovery.
If anyone could help me out by posting links, that'd help A LOT!
Click to expand...
Click to collapse
Has any application that requires Root Access, or Sudo, ever been granted Super User Permissions? If not, I have a feeling that your root was not preformed correctly. If I may ask, do you remember which "root" method you used? I used HoB Linux Edition, as I run Gentoo. HoB Linux Edition stands for House of Bionic Linux Edition. Here is a link for HoB. (Well, apparently I am unable to post links until i have posted atleast ten times. Message me on Google talk for the link. My GT is later on in this message).
There is a version for Windows, Mac, and the best of all, Os/Distros based off of the Linux kernel (which is based off of the Unix Kernel). As for the whitelist, you are able to go in and select which applications you would like to either always deny, grant, or ask for Super User Access. Again, I've mainly only used SuperSU, as i have had problems with most of the others out there currently. I would not go off of the stock recovery, as, for me at least, when I had an incomplete root, the stock recovery said I was rooted, even though I was not. If you could, could you please post a copy of the log from the super user program that you use? Also, which one do you use, again? If you are online/awake currently, message me on Google talk your questions. i will post anything that solves this issue in the morning. This is do to my mother decided that I need to go to bed. My Google talk is ([email protected]). My Google talk is also best to reach me for quick replies during the hours of: 0700 hours through 1530 hours as I am in my classes at that period of time (High School). Another quick question, did you ever go to Az or Fz Fastboot, during your root process? (Been rooted for over 1.5 years now, a little hard to remember). If not, I doubt that the Root was successful. I am sorry for my late response, as I was watching BSG Blood and Chrome, while shining my shoes for the ROTC inspection tomorrow.
Hope we fix this soon,
~NH85
No, so far since i've rooted this phone superuse has denied every application. I use the superuser v3.1.3.
I was thinking just last night that my root was performed incorrectly, so i went to droidbionicroot website and downloaded a un-root method (as well as several root methods) But i haven't done it yet, I've read that it bricked some users phone's and i don't want that.
I'm on a windows and have tried several root methods. I think the one that actually worked for me was called "PetesMotorolaRootTools_v1.07"
Also, what's Az or Fz fastboot? I'm sorry, I'm still kinda new to this rooting stuff so i appreciate the patience.
I don't have a google talk so I'll just email you at the address. My email is [email protected]
Related
//EDIT: Please delete this thread. Titanium Backup installed BusyBox for me after I clicked the "Problem?" button. Sorry!
**Skip to the other asterisked line to skip the long story**
Last night I decided "(vulgarity here) AT&T!" and decided to load FroYo myself.
After reading for hours (on top of reading I've been doing for a few weeks) it seemed it was easier to root on 2.1, then update to 2.2.
I rooted, then installed 2.2 only to find out I was no longer rooted when I tried restoring my apps with MyBackup Pro. After tons of searching and trying 3 "one click" style rooting programs, many times over, the SuperOneClick method worked, only after I did the shell root, and then root button.
Awesome! I had a rooted 2.2 captivate! Restoring my apps with MyBackup Pro let me knew it worked, and then I was also able to install a non-market foreign language pack for the AnySoftKeyboard app. I also installed the MarketAccess app and I'm running the T-Mobile US code, so I'm pretty sure I've got root.
Tonight I wanted to get rid of all the AT&T garbage still on the phone, and a guide I found told me that Titanium Backup would allow me to do so (still not sure if it can all be done from the phone though). I downloaded and installed Titanium Backup, opened it up, clicked the button to allow SuperUser, but I get an error message:
Sorry, I could not acquire root privileges. This application will *not* work ! Please verify that your ROM is rooted and includes BusyBox, and try again.
Pretty sure I'm rooted, I am assuming I only require BusyBox be on the phone?
**I was under the impression that rooting and BusyBox was the same thing, or went hand-in-hand, one needing the other.
After now 4 more hours of searching, I can't seem to find a guide that only installs BusyBox, and I'm hesitant to try any of the Root and BusyBox in one methods for fear of the root not working and potentially messing something up.
I found one posting that requires a bunch of commands, but I have no idea where to do them from/in or what to do with the phone.
If anybody could link me to or tell me how to install BusyBox that would be awesome! I am rooted on FroYo. I have the drivers installed. I have DroidExplorer installed. Not sure of anything else that may have come in the .zip files I downloaded that might be installed, so assume only the drivers and DroidExplorer and installed.
Thanks in advanced!!
Busybox is an app on the market, download, open app, install, profit
Sent from my GT-I9000 using XDA App
Hello everyone. I know I'm a noob, but am hoping I can get some help anyway. Tried searching and not too many people are having the same problem, so I started a new thread.
Anyway, I used the one click root found in this thread:
http://forum.xda-developers.com/showthread.php?t=1348557
( I tried to post in that thread, but can't since I don't have 10 posts )
I'm new to hacking and I'll be honest. I only wanted to root my phone so I could use wireless tether, and then use Titanium Backup to freeze a lot of the bloatware on the phone. I have no desire to install a different ROM. I'm happy with the one it has, and happy to take the updates Verizon pushes. Everything was good until the latest update came through. When it downloaded, and rebooted, instead of updating, it booted in clockwork mod recovery. No matter what I tried, I couldn't get the update to go through.
So I settled on never updating again and froze the updater to prevent my phone from trying to update and going to CMR at random times. About 4 days later, my bluetooth quit working. Couldn't figure out why. Thought I was going to have to send it in for warranty work, so I tried to undo all the mods. I unfroze everything, and then hit the one click unroot button. It said it worked. Problem is, superuser is still installed with no way to uninstall.
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Next I tried to go ahead and get the update since the unrooting process was supposed to have reinstalled stock recovery. Well, it didn't. I still ended up booting up into CMR again. STILL can't update even after unrooting. Double checked, and wireless tether and Titanium backup both say "no root". On a whim, I try the blue tooth and guess what. It worked. May not need to send the phone off for warranty work after all.
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
I know this is a lot of question and I'm a noob, but I'm a noob willing to learn. If this problem has been encountered before, I apologize in advnace for not finding the appropriate thread. I tried.
updater app
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
NewDroidXUser said:
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Click to expand...
Click to collapse
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
NewDroidXUser said:
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Click to expand...
Click to collapse
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
NewDroidXUser said:
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
Click to expand...
Click to collapse
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
brad6360 said:
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
Click to expand...
Click to collapse
Ah, thanks. I'll post again to update how that went. Though, I'd like to keep the stock recovery. I'll try to do it without CWM.
latenighter49 said:
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
Click to expand...
Click to collapse
How did you change permissions in Gemini? I turned off all the autorun features and was able to get Bluetooth working but I didn't see anything about permissions in the settings. I could have missed it though being at work and all. Will turning off all the autorun features of the Software Update app stop it from trying to download the update in the middle of the night when I'm not looking like it sounds like it should?
In gemeni select block app. It's the same as freezing in titanium backup.
Sent from my VS910 4G using XDA
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!
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.