I have SSHDroid Pro installed, as i did on my previous GNex & Note 2, except i can't get root access via my SSH program (WinSCP).
In the options screen, the "Enable Root" tick box is greyed out, and so unable to be ticked.
Unlocked bootloader, TWRP & SuperSU done.
Is there a simple answer to this or is it an app problem?
*bump*
Is anybody else using this on their Nexus 5?
Sent from my Nexus 5 using xda app-developers app
OK, now a new problem has appeared and the old problem has changed.
The app has been updated and according to the play store desription, it has "fixed an issue with root permissions".
The original problem of the box being greyed out is now fixed, and i can tick the root box.
But i am still getting an error when trying to edit/add anything in a root folder.
Is there anybody that can test whether this is an app problem or just a problem on my device?
munkiii said:
But i am still getting an error when trying to edit/add anything in a root folder.
Is there anybody that can test whether this is an app problem or just a problem on my device?
Click to expand...
Click to collapse
It works fine for me. I can copy the file to /, rename it, edit it and delete it.
Related
Anyone know what the fix permissions is not working in rom manager? Anyway to fix this?
Thanks!
Its working fine for me, just checked!
I am running stock rooted rom and and I get
An error occurred while attempting to run privilged commands!
Anyone know why?
Thanks!
fbm111 said:
I am running stock rooted rom and and I get
An error occurred while attempting to run privilged commands!
Anyone know why?
Thanks!
Click to expand...
Click to collapse
Two possibilities are -
1: You did not root properly
2: You did not provide root access for ROM Manager via the Superuser .apk (allow button that pops up)
Go to superuse permissions and see what apps. You allowed to use superuser. The ones you allowed well have. A green box. Next to it.
Ones you denied have a red box next to it.
-Monky_1
I guess it is possible that I didn't root right.
I followed directions to a T, flashed several different roms, kernals, use wifi tether and shootme with no issues.
I do have green dot in superuser.
Could it be possible that I can't fix permissions because it is a stock rooted rom?
I'm assuming you did the 3 step root process? Chances are you need to run step 3 a couple more times until your device restarts itself. Try it out.
Tyler
hellonfire said:
I'm assuming you did the 3 step root process? Chances are you need to run step 3 a couple more times until your device restarts itself. Try it out.
Tyler
Click to expand...
Click to collapse
I had this problem with the 3 step root. You can try booting into cwm choose advance and the choose fox permissions from there.
sent from a sweet paper weight.
Are we calling the three step root the one jcase did? I followed his pretty much the same day he posted it.
Sent from my ADR6400L using XDA Premium App
Same thing here. I get failed tryingto run privileged command.
Also running stock rooted
Sent from my ADR6400L using Tapatalk
Go into Superuser and make sure you didn't miss the Allowance of Rom Manager. Tap it in SU and clear it. Then reopen RM again and hit allow when it asks you for permissions.
If you flashed ROM's and have root permissions in all other apps... There's not much else it could be.
All else fails... Clear data and uninstall RM and reinstall it.
Sent from my ADR6400L using XDA Premium App
I've seen a few threads asking if it is posible to get this working on a rooted S3 so thought I'd share how I got it running.
Software Needed:
Permissions Denied (free from Play Store)
ES File Explorer (free from Play Store)
Barclays Mobile Banking
Steps:
Now, you may be able to just try the last step. I was messing around and managed to get it working after try all the steps without testing in between.
1: After installing Barclays open Permissions Denied and select Banking (the one with the Barclays logo).
2: Deny the 'android.permission.GET_TASKS'
3: Open ES File Explorer, navigate to '/system/app/' and rename SuperSU to anything you want.
4: Navigate to '/system/xbin/' and long press on 'SU' and select 'Hide' from the menu.
NOTE: if you update the SuperSU binary, you will need to do step 4 again!
That's it! I dont know if it will work for everyone but it works for me. I also dont know if Barclays can solve that with an update so I don't plan on updating the app. I'm not a coder and don't know a lot about tje technical details of Android so if you run in to problems I can only TRY to help you.
I've not tried to use any other apps that block rooted phones but feel free to let me know if this works on other things.
Thanks.
Sent from my GT-I9300 using xda premium
Ive been using this for a few days now but just started having FC's.
I just re- enabled the permission and rebooted and it's working again.
Sent from my GT-I9300 using xda premium
Will this work with the Skygo app?
Sent from my Desire HD using xda premium
I'm not sure. This is the only app I use that checks for root privileges so haven't tested it on anything else.
Could you give it a try and let me know please? If it works for others then this could be a very useful work around.
Sent from my GT-I9300 using xda premium
I've just downloaded SkyGo and the app opens and I get to the TV guide and get the option to watch it of I sign in. I don't have Sky so can't test any further.
I'm assuming it checks for root when it opens so I'd class that as a success!
Sent from my GT-I9300 using xda premium
Thanks for testing im unable to do it myself because when I open it it fc straight away wich is probably something to do with my rom
Sent from my Desire HD using xda premium
Hi Faz - Thanks for the info. But when I install permissions, it asks for busybox. I installed busybox but it still says it has not detected busy box please install.
Any advice??
I cant find superSU in system/apps!?. It's not superuser.apk is it?
Sent from my GT-I9300 using Tapatalk 2
Permissions Denied is not free anymore
I've posted here how I got it working on my HTC One S, and I'm pretty sure (or hoping) it'll work on any Android phone.
Didn't paste the post here, unsure on if that's allowed.
+1
This worked for me.
Very happy Galaxy S III user.
Thanks Faz1980.
Thank you so much.
Perfect!
This also works on the Galaxy Note II N7105.
One thing...make sure you use the REBOOT command in Permissions Denied after making the change.
superuser has a temp unroot option, it works to avoid root check on dutch live tv app.. try it
Swapping Out Superuser for SuperSU
Faz1980 said:
I've seen a few threads asking if it is posible to get this working on a rooted S3 so thought I'd share how I got it running.
Software Needed:
Permissions Denied (free from Play Store)
ES File Explorer (free from Play Store)
Barclays Mobile Banking
Steps:
Now, you may be able to just try the last step. I was messing around and managed to get it working after try all the steps without testing in between.
1: After installing Barclays open Permissions Denied and select Banking (the one with the Barclays logo).
2: Deny the 'android.permission.GET_TASKS'
3: Open ES File Explorer, navigate to '/system/app/' and rename SuperSU to anything you want.
4: Navigate to '/system/xbin/' and long press on 'SU' and select 'Hide' from the menu.
NOTE: if you update the SuperSU binary, you will need to do step 4 again!
That's it! I dont know if it will work for everyone but it works for me. I also dont know if Barclays can solve that with an update so I don't plan on updating the app. I'm not a coder and don't know a lot about tje technical details of Android so if you run in to problems I can only TRY to help you.
I've not tried to use any other apps that block rooted phones but feel free to let me know if this works on other things.
Thanks.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Unfortunately since upgrading my SGS3 to zoot1's version of CM10 with 4.2 Gapps, this stopped working for me.
I think this is mainly because zoot1's ROM comes with Superuser and not SuperSU.
However, I followed the instructions on this blog to remove Superuser and replace it with SuperSU.
I still can't get it to work though.
Hi. I've noticed weird things happening with myphone. Few times so far, switch widget pro lost root permissions. I thought that widget was the problem so I uninstalled it, installed.again and the same problem. I downloaded SuperSU from market, and granted SU permissons. Than i happened again, so i uninstalled switch widget, thinking something is wrong with it. Last night, i was using titanium backup, and it was working fine, and.this morning i got a notification than titanium can't do a scheduled task becausebit doesn't have SU permissions. Again I downloaded Super SU,granted permissions and its working. But i know it will happen again. Did anyone had the same issue? Why is this happening?
Sent from my LG-P920 using Tapatalk 2
go to Settings → Applications → Development → USB debugging → select it → DONE
lw_wl said:
go to Settings → Applications → Development → USB debugging → select it → DONE
Click to expand...
Click to collapse
USB debugging was and still is selected.
axlina said:
USB debugging was and still is selected.
Click to expand...
Click to collapse
well, i have no idea. maybe try upgrade the superuser in google play. if you just did, then try install a old one. it must be something wrong with the superuser.apk
Sent from my LG-P920 using xda premium
Make sure you have unknown sources and usb debugging always enabled apart from that i cant help you because mine never lost root.
xbsall said:
Make sure you have unknown sources and usb debugging always enabled apart from that i cant help you because mine never lost root.
Click to expand...
Click to collapse
All of the above was enabled. That afternoon I started Titanium Backup and everything was ok...later that evening I started TB again and i said that it was denied of SU permissions. Than I rooted the phone again. A week later it happened again so I rooted my phone again. Then I upgraded to ICS and it didn't happen since...
Sent from my LG-SU760 using Tapatalk 2
I've noticed that SuperSU (Chainfire) seems to give permissions to specific versions of applications. Every time an application is updated, it loosed its su privileges.
Thats why I use Superuser (ChainsDD) now. Applications may be updated and still not loose its privileges.
Sent from my LG-P920 using xda app-developers app
I rooted my phone with kingroot and while i was using the extra rope, i hung myself. The settings.apk in my phone has become somehow damaged, and will not open. The .apk still exists, but every time i try to open settings (directly or otherwise) it closes with a pop-up saying: unfortunately settings has stopped. I also tried to replace kinguser with superSU and failed leaving myself with confusing root access that is only revealed when certain apps like varied root checkers tell me i'm rooted.
I cannot install non market apps because when settings became damaged, the box was unchecked. All i need is to be able to fix the settings.Apk. I don't have a computer and i can't update superSU binary. I have factory reset my device and tried to find solutions onlinen to no avail. I can access the hidden menu and terminal emulator without root. I need to be able to enable non market installation some how. Can anyone help me?
Sent from my LGMS323 using XDA Free mobile app
Hello!
I need some Help with my Shield Tablet. I own the "Nvidia Shield 32GB LTE" Version and did root it 2 or 3 Days ago. Now i got the Message for the new "4.2 Upgrade" but after trying to install said Upgrade, i get the laying Android with an "Error". I tried the Installation 2 Times with the same Result. Do i have to Factory Reset my Shield to be able to install OTA 4.2?
I have no Experience with anything related to Software modification and got my root with a YouTube Tutorial on the Shield. I'd like to keep the root, and would reroot if necessary.
Any Help is appreciated!
Informations that may be helpfull:
- I have the Nvidia Family Drivers installed
- I have "minimal ADB and Fastboot "
- I own the "32GB LTE P1761" Model
- I have Android 6.0.1 installed with the Security Patch from 1. March 2016 and Shield 4.1 (24.3.67.35) Software
- I used the "TUTORIAL - Root NVIDIA SHIELD Tablet / K1 - Android 6.0" Tutorial on YouTube
Once you're rooted, you cannot update via normal means as the regular OTA update will check the system partition to make sure it is untouched.
The easiest way to update is to simply have the updater download the Full OTA and install. Go to Settings -> About tablet -> System upgrade -> 3 vertical dots on top right -> Advanced -> Check full upgrade (check it).
When it updates, it will remove root and very likely the TWRP recovery.
After it's updated, you can then go back and flash TWRP 3.0.2-2 to the recovery partition and then flash SuperSU 2.76 within TWRP. You may have older versions of TWRP and SuperSU if you used the YouTube tutorial, so be sure to get these newer versions.
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
[email protected] said:
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
Click to expand...
Click to collapse
Your not allowed to discuss LP here so I can't help with that. But if I were you I'd look at enabling compatibility mode in supersu. This helps with programs that haven't been updated to work with systemless su. I think the reason you can't install as a system app is because the program isn't properly calling su.
Sent from my SHIELD Tablet K1 using Tapatalk
I haven't found anything regarding compatability mode in supersu. Hidden option?
[email protected] said:
I haven't found anything regarding compatability mode in supersu. Hidden option?
Click to expand...
Click to collapse
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Exile1975 said:
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Also, do you have busybox installed? If not start there
Sent from my Nexus 5X using Tapatalk
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
[email protected] said:
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=67710325
[BETA][2016.07.05] SuperSU v2.76
Sent from my Nexus 5X using Tapatalk
Thank you Guys for all the Help! \o/ Feel Brofistet from me.
I found the cause for the Error. It was the actual .apk that i tried to install. I went back trough my Chrome History to find the first one i used and it worked flawlessly. I sometimes have to wonder how i survive outside my Room...