Supersu me free

You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. #1 Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed. BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks. #2 You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that. #3 You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that. Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue. #4 No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the

On the beta build marshmallow's. #5 But can't works on the beta build marshmallow's. Not Tested on Marshmallow.. that's why mentioned that it works on Lollipop.. #6 Some errors on script startKingroot icon is still there and can't removecom.kingroot.kinguser still active, if freezed supersu doesn't work anymore #7 Some errors on script startKingroot icon is still there and can't removecom.kingroot.kinguser still active, if freezed supersu doesn't work anymore You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done... #8 You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done... I'm following your instruction exactly, why not?how can i blame you if i don't follow exactly what you wrote? mrw was in root of sdcard, supersu and su binaries are working (if i don't freeze com.kinroot.kinguser) but what i wrote it's valid.I launched again the script and after a lot of errors this time supersu asked me to reboot, first time didn't; now seems all kingroot trace are gone!EDIT:After testing i see that a lot of times supersu needs to be started manually to have the auth promp for an app, my english isn't so good, i'll write an example:start (first time) an app that requires rootwait for auth prompt by supersuwait a lot, so open supersu, then it shows the request for authorizea second app started just after show immediatly the auth prompWhen com.kingroot.kinguser was active the promp from supersu was everytime immediate.Latest: kngroot unlocks bootloader Last edited: Feb 15, 2016 #9 Is some chance this work in future on

Terms and rules Privacy Security You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. Home Forums OnePlus OnePlus 3 OnePlus 3 Questions & Answers Mar 25, 2017 #1 Hey guys I'm running stock OOS 4.1.0 with franco kernel and supersu. I can't log into snapchat, it gives me the log in temporarily failed error. I've even tried fully unrooting via the supersu app and it still doesn't allow me to log in... Any work arounds? Would be much appreciated, thanks! Mar 25, 2017 #2 Dirty flash OOS 4.1.0, log in to snapchat, then flash SuperSU. You could also try Chainfire's HideSU.Alternatively, root with Magisk and use Magisk Hide. Mar 25, 2017 #3 Dirty flash OOS 4.1.0, log in to snapchat, then flash SuperSU. You could also try Chainfire's HideSU.Alternatively, root with Magisk and use Magisk Hide. Thanks mate! Similar threads Home Forums OnePlus OnePlus 3 OnePlus 3 Questions & Answers

Marshmallow ? thanks #10 Dear saifkhan9187,How to update superSU? I got failure message when SuperSU try updating. Last edited: Feb 16, 2016 #11 Making this I still can get the OTA updates? #12 Is that ota still available? #13 Recently, about a month, I got the b188 update... Android 5.0.1 #14 Dear saifkhan9187,How to update superSU? I got failure message when SuperSU try updating. Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail. #15 @ItalianWolf how did you check for unlocked boot loader? Fastboot? Thanks! #16 @rHycH yes, reboot in fastboot mode and you can see in red that bootloader is unlocked #17 Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail. Thanks, its updated now.--------Waiting for simple way to unlock boot loader of ALE-L21 Attachments Screenshot_2016-02-17-18-26-18.png #18 @aab44 bootloader is unlocked now, you can see in fastboot! #20 Please, is there any way to undo this and use kingroot again ??or at least have an option to use an different busybox ??since this have made Link2sd and foldermount unuseable for me Many Thanks in advance Junst do full unroot from supersu and use again kingroot (install and root) Similar threads

Turning off opendns). With no OTA, I can at least take this out of the house!Future: Hope to get supersu working with real root for apps. omg, I saw logs in SuperSu Log, some asked for root access, but the device never prompt.I then go to superSU setting and set the default access is "grant", then my adb shell and teminal emulator works again.I then tried 2 of the root checkers and both said my device is rooted! It seems the device wont prompt for root access so the root checkers cannot verify the root status. However "always grant root access" is a dangerous behavior I think. Last edited: Jan 14, 2017 #32 omg, I saw logs in SuperSu Log, some asked for root access, but the device never prompt.I then go to superSU setting and set the default access is "grant", then my adb shell and teminal emulator works again.I then tried 2 of the root checkers and both said my device is rooted! It seems the device wont prompt for root access so the root checkers cannot verify the root status. However "always grant root access" is a dangerous behavior I think. I saw my logs with a bunch of red "X" for TB, and other programs where I was trying. I never found any options but maybe did not look. I am fine with no prompt, it is only me using this baby.Now, can I figure out the steps we did again? #33 I saw my logs with a bunch of red "X" for TB, and other programs where I was trying. I never found any options but maybe did not look. I am fine with no prompt, it is only me using this baby.Now, can I figure out the steps we did again? Good idea! A list of conformed steps will make things less complicated. Sent from my Nexus 5X #34 **** wish i could downgrade. #35 **** wish i could downgrade. me too ? #36 **** wish i could downgrade. Yes, that is my problem as well. I am not sure if a reset will go back to 5.1.Sent from my Nexus 5X #37 well,, I re-did steps in thread #15 and this time supsersu declared that the binaries were missing. No idea why it work a different way the second time around. I actually did not get any errors messages about the daemonsu being