[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.
clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.
Hello ppl. So, I was playing with my old phone, Sprint Samsung Galaxy Note II, (it's always a good idea to torture old phones instead of the new ones, right?) and I've done a lot of stuff with it, but for a long time, nothing was happening. So, this is the list of what I did with the phone:
0. I had my original OS rooted, then unrooted it, and I was said to use twrp, if I'm not wrong (can look up, but it will take time).
1. Rooted it. Knox disabled root. (I had the latest, NC2, update)
2. Tried to flash the older OS. It wouldn't. I guess because of Knox.
3. As I was trying to flash older OS, I kind of lost the OS, and had no OS at all. No problem, I thought. I'd just download and flash several other versions of OS, and eventually I'll find one that'll be working
4. It appeared to be the latest, NC2.
5. Back to root. Until restart.
6. Whenever I root, I try to install cwm with ROM Manager. Upon restart, the recovery is <3e>. Not <2e> or cwm. Not even twrp that I had.
7. So now I'm here, and I just don't know what to do. I remember that I somehow disabled the knox, and I'm sure just by updating the SuperSU (or its binaries? But I can't find any in the market), but this CF-AutoRoot installs latest SuperSU, and so there is nothing to update.
Then I finally figured out what to do. I should warn you, it took me 3 days to figure out what to do to install CWM, so if you have any kind of a problem with installing it, just use this tutorial, I guess. Even though it covers just the basics.
1. In SuperSU, choose "Uninstall to install other Superuser application" or similar.
2. It was necessary for my phone to actually update binaries
3. As the Knox was disabled by updating the binaries, I could now use ROM Manager to install Clockworkmod Recovery (Yay!!!)
4. Download the Cyanogenmod ROM, either through ROM Manager or the web site (choose most stable and recent. Otherwise, who knows what problems it might have) and install it:
4.1 In Clockworkmod (CWM, cwm) (if you still haven't copied the Cyanogenmod (CM, cm) and Google Apps to your external SD, please do that. Just restart the phone and copy it from your computer. Download from the web site) (Vol Up, Home, Power from the phone turned off) just choose the right update and press to install. Then do the same for Google Apps.
4.2 In ROM Manager, just choose the CM and don't forget to install Google Apps.
5. When my phone actually installed Cyanogenmod, it loaded forever. As I was sleepy, I don't actually remember what I did, but I reinstalled the ROM several times, and finally, it worked.
6. Now I'm enjoying my old phone that uses Cyanogenmod.
...and don't know what is happening know.
I rooted my phone first with Kingroot and it got its place in my phone. Then I tried to uninstall bloatware. I saw Chrome using about 45MB of space. I was happy that now I'll kick it away and other apps. But when Kingroot shown Chrome, it shown Chrome as using only 10MB and same with other apps. Original space apps were using were not shown but much less than that. Anyway, I uninstalled all of them. About 6 or 7. After uninstallation I checked my Device Storage, it was still 1.45GB as it was before uninstallation. WTF! Even now, as those apps were disabled, I got 6 or 7 Android dummies in my phone like all those are apps.
Then I rebooted my device and those dummies were gone. The Kingroot experience was pathetic. It doesn't even freed up space as expected. Well I proceeded to properly root my device. Found this thread for my upgraded-to-lollipop phone and downloaded and installed as said in that thread. I flashed TWRP via Odin and then flashed SuperSU via TWRP.
Rebooted and came to system to use. Opened SuperSU and it shown error "binaries need updating". I updated this app and used "Use TWRP to install binaries" and even Normal mode too; as said in some other thread here but no luck.
I even get "recovery is not seandroid enforcing" everytime I go to recovery mode but everything seems working fine. As with other users seeing same message, I am getting to TeamWork UI successfully (don't know why that message is displaying). Now All I want is to know is is my device is healthy? And can I install other custom ROMs. I though made a backup using TWRP.
My device: Samsung Grand Prime (SM-G530H). Was Kitkat when purchased but I upgraded to Lollipop 5.0.2.
Thanks for any answers.
Download a custom rom and flash via twrp if u already backup up the stock rom. Most of ur issues will be solved already
Sent from my SM-N920C using Tapatalk
livelife01 said:
...and don't know what is happening know.
I rooted my phone first with Kingroot and it got its place in my phone. Then I tried to uninstall bloatware. I saw Chrome using about 45MB of space. I was happy that now I'll kick it away and other apps. But when Kingroot shown Chrome, it shown Chrome as using only 10MB and same with other apps. Original space apps were using were not shown but much less than that. Anyway, I uninstalled all of them. About 6 or 7. After uninstallation I checked my Device Storage, it was still 1.45GB as it was before uninstallation. WTF! Even now, as those apps were disabled, I got 6 or 7 Android dummies in my phone like all those are apps.
Then I rebooted my device and those dummies were gone. The Kingroot experience was pathetic. It doesn't even freed up space as expected. Well I proceeded to properly root my device. Found this thread for my upgraded-to-lollipop phone and downloaded and installed as said in that thread. I flashed TWRP via Odin and then flashed SuperSU via TWRP.
Rebooted and came to system to use. Opened SuperSU and it shown error "binaries need updating". I updated this app and used "Use TWRP to install binaries" and even Normal mode too; as said in some other thread here but no luck.
I even get "recovery is not seandroid enforcing" everytime I go to recovery mode but everything seems working fine. As with other users seeing same message, I am getting to TeamWork UI successfully (don't know why that message is displaying). Now All I want is to know is is my device is healthy? And can I install other custom ROMs. I though made a backup using TWRP.
My device: Samsung Grand Prime (SM-G530H). Was Kitkat when purchased but I upgraded to Lollipop 5.0.2.
Thanks for any answers.
Click to expand...
Click to collapse
Thanks Mohammad. I'll see into it.
Hey Good Morning folks.. I bought a new phone J6+ and I didn't care for warranty and I decided to void it and root my device. I updated my phone to the latest software from Samsung through Odin and everything went well. I downloaded Magisk Manager after that then pulled the boot image from the stock room I have using 7-zip and patched it then flashed it to my phone through Odin. As in such case it was supposed to work as it worked with all other Samsung devices I rooted.
After that I downloaded Solid Explorer and I tried to remove some apps from my /system/apps as a simple test to see if my root works. it was Youtube it wasn't a dangerous critical app. But then my phone hanged and restarted then I found Youtube is back.
I went to Magisk again and downloaded BusyBox from there and installed an app called "Uninstall System Apps" and I used it to remove Youtube also as a test it removed it and the restarted the phone flawlessly then I went to remove "Facebook" then restarted my phone then Gosh Youtube is back and also Facebook.
I found out if I try to modify anything in /system the phone will restart then undo what I've done.
what is the reason? is it Defex? is it RMM? is it Knox? is it DM-VERITY? I just wanna know what is wrong with it to see how I can fix it.
Edit:
Phone: SM-J610F/DS
Software Build: M1AJQ.J610FXXU1ASA3
Magisk version: 18.1
I keep reading other threads and posts. I can see there is a way using Ashyx Method https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
I just wanna know why it fails if I install Magisk with "Patched Boot method" only.