Related
sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
sorry i think its a stupid question but what should i see in superuser permission one time i only saw this +2000-2000 and something else
I was having trouble with super user too. I reverted to a working back up
ampinc said:
sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
Click to expand...
Click to collapse
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.
Framework43 said:
From now on ,it should work for everything.
Click to expand...
Click to collapse
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc
gohamstergo said:
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc
Click to expand...
Click to collapse
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.
Framework43 said:
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.
Click to expand...
Click to collapse
iam sorry but i dont know where adb shell is
ampinc said:
iam sorry but i dont know where adb shell is
Click to expand...
Click to collapse
have you downloaded the Android SDK? If so, open a command prompt and navigate to the SDK's Tools folder. then do adb shell
Framework43 said:
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.
Click to expand...
Click to collapse
no, what i meant was, clicking Always Allow only allows the current process to be always allowed.
ex: if you connect via adb on a computer and Always Allow, then you still have to allow other programs like Terminal Emulator, drocap2, etc also Always Allow isn't universal, only applies to the current app that is requesting the permission.
don't remove this app
and there is no need to run this app manually
if an app requests root-rights, this app will auto popup
i dont know what i did wrong but its not working please some help thanks
jriley60 said:
I was having trouble with super user too. I reverted to a working back up
Click to expand...
Click to collapse
can you please link me to a working backup of superuser.....I am having issues too.
there isn't a fully working one. the version we are using is from another phone completely. Until the author of superuser.apk writes one for us. the only method of getting superuser.apk to work right is.
1. enable usb debugging
2. plug your usb into your phone
3. choose HTC sync and wait for it to fail to connect if not installed.
4. while in sync mode start the app that needs root access and wait for the su prompt
5. select always allow
6. enjoy your app
some root apps like wifi tether require multiple access prompts to be fully functional.
hope this helps
With some help on the cyanogenmod forums, I worked out a way to enable the integrated superuser manager to actually function!
REVISED EDITION:
WARNING! DO NOT ATTEMPT UNLESS YOU KNOW WHAT YOU ARE DOING.
This is an experimental step to bring a feature from regular Cyanogenmod to 11S. You have been warned.
This requires adb and fastboot to be installed.
Please read all the instructions before attempting
1)-- Optional-Flash a custom recovery of your choice. There are threads out there that explain this.
2)Next flash the debuggable kernel, found at the bottom of this post. You can easily flash it via fastboot.
fastboot flash boot ./path/to/boot-debuggable.img
2)Download su.zip I created.
3)Boot into custom recovery(a requirement). This can be done without actually flashing it. Look up how, plenty of threads already.
4)Flash su.zip
8) Reboot.
9)If you didn't before doing this, go to Settings => About Phone and enable developer mode. Under Settings => Developer Options select Root Access and change it to Apps and ADB. Now install any root application or root checker and test it out.
Debuggable Kernel is downloadable here at the bottom:
https://cyngn.com/products/oneplusone/
su.zip
http://www.androidfilehost.com/?fid=23578570567721138
https://mega.co.nz/#!sp8nmL5J!Pj2Z4UI-7vG2YsMwEpIbDLTWOwiyWwu398oLE9edFdk
RESERVED
RESERVED
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
joaocadide said:
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
Click to expand...
Click to collapse
What current superuser manager are you using? SuperSU?
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
How can I get rid of the menu when I use SuperSU instead?
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
That only makes the menu visible. The menu will not actually function as a Superuser manager. For that, you would need the debuggable kernel and the proper compatible su binary which is why I wrote my instructions.
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
jbass350z said:
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
Click to expand...
Click to collapse
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
vladashram said:
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
Click to expand...
Click to collapse
I had this same exact issue with secure settings, and elected to follow the instructions on this page to activate the cyanogenmod root settings - it worked just fine. Interestingly, even after losing the "built in root" after updating to XPNH300, secure settings still seems happy.
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
chenkeikari said:
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
vladashram said:
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Click to expand...
Click to collapse
As of right now, the stock debuggable kernel for 30O is live and available.
Thanks for your work.
But could you please update to the latest version of the SuperSU binaries or could you tell me, what you modified comparing it to the normal SuperSU.zip?
Would you please share how and why would this be different than a straight forward install of SuperSU?
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Not working for me
Titokhan said:
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Click to expand...
Click to collapse
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
remortr said:
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
Click to expand...
Click to collapse
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Pls help me step by step procedure..
sendhiloo7 said:
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Every thing done but fast boot wont work in my case pls help me sir .pls see my attachment...
I've granted su/root access to some apps but want to revoke that now (per app - not globally). Usually there's an option/list to manage this (CM11 and earlier) but i cannot find that in CM12. Anyone know how to revoke su individually for once granted apps? Please note this question is about the built-in Superuser not Chainfires SuperSU.
Isn't there any Superuser option in the settings?
There needs to be something.
Root access is managed in Settings-Privacy-Privacy Guard in cm 12.
Hope it helps.
Yep, thanks. They could at least have given an info on the popups for that.
Anyone tried rooting Pixel XL and how does it works after rooting ? Reviews
Everything works fine here
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
AstroDigital said:
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
Click to expand...
Click to collapse
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Huzaifaamirka said:
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Click to expand...
Click to collapse
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Working fine with ElementalX kernel and root.
hutzdani said:
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Click to expand...
Click to collapse
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
With USB Debuiing enabled open your ADB terminal and type :
"adb shell"
"su"
"mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway"
After this reboot your device and apply ad blocking hosts with the latest ad away build
Thank you for the info!
I wonder if there are plans to update adaway so this procedure will not be needed..
Thanks again great detail
Bryan
Sent from my SM-N900V using XDA-Developers mobile app
Wrong sub forum.
trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
All you have to do is download the 3.2 Dev preview build and enable systemless mode in preferences. Works like a charm.
https://www.androidfilehost.com/?fid=312978532265366394
That's great so with version 3.2 dev no adb procedure is needed?
Hi,
I have a rooted OP8P running Magisk 21.0 (21000), and using Magisk Manager 8.0.2 (307)(11). My OS build is Oxygen OS 10.5.13.IN11AA(enhanced by xXx_NoLimits_ 12.3).
I keep getting the pesky notification to Update to Oxygen OS 11.IN1AA, the one that gives me the option to "Download and Install Now". I have no plans nor any desire to go to Android 11 as of yet, so I would like to do two things, stop this notification from showing up, and ensure that the update doesn't install itself.
Normally, I wouldn't worry about it updating without some user input but just today I got a second notification telling me that "System update installation failed" prompting me to "Try Again"(See attached pic). This is both good and bad I suppose, but it's still troubling since this newest notification indicates that it tried to update without me knowing about it. This simply will not do.
Any advice? I know it's not as simple as disabling the notification, as it doesn't allow me to do so.
Thanks!
KingKazmaOfficial said:
Hi,
I have no plans nor any desire to go to Android 11 as of yet,
Thanks!
Click to expand...
Click to collapse
I'm seeing the same and contemplated the same question. What are your reasons for avoiding the upgrade?
p.s. I can think about a way of disabling system notifications (using root access), but I worry about missing important notifications, so I left this pesky message on.
NYCgirl said:
I'm seeing the same and contemplated the same question. What are your reasons for avoiding the upgrade?
p.s. I can think about a way of disabling system notifications (using root access), but I worry about missing important notifications, so I left this pesky message on.
Click to expand...
Click to collapse
I just don't see any real reason to update, OOS 10 is working fine for me. From what I've seen OOS 11 doesn't bring anything compelling enough to the table to make me to want to upgrade. Also, OOS 10 has been around long enough that there are robust resources and development communities built around it, meaning more reliable troubleshooting and overall easier research. On top of all that, having to factory reset and re-root to avoid potential bugs due to OOS 10 residuals isn't very attractive either.
I mean don't get me wrong, I love the feeling and idea of being on the bleeding edge as much as the next guy, but I'd rather all my ducks be in a row beforehand...if that makes any sense.
Can you freeze the app in titanium??
Freezing System Update 2.2.3... did the trick for me.
---------- Post added at 01:54 AM ---------- Previous post was at 01:51 AM ----------
KingKazmaOfficial said:
On top of all that, having to factory reset and re-root to avoid potential bugs due to OOS 10 residuals isn't very attractive either.
.
Click to expand...
Click to collapse
That makes sense. If you have to factory reset, how would you restore your data? AFAIK, there not yet TWRP for Android 11, which means relying on something else. This make me nervous...
dladz said:
Can you freeze the app in titanium??
Click to expand...
Click to collapse
Don't have the pro version.
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
KingKazmaOfficial said:
Don't have the pro version.
Click to expand...
Click to collapse
VRaju said:
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
Click to expand...
Click to collapse
Use the terminal app on phone or cmd on PC?
You can try either should work.
App to disable is ""com.oneplus.opbackup""
KingKazmaOfficial said:
Use the terminal app on phone or cmd on PC?
Click to expand...
Click to collapse
VRaju said:
You can use the adb command to disable the update as well notification
adb shell pm disable-user --user 0 com.oneplus.opbackup
Click to expand...
Click to collapse
Buy it, they deserve the payment for all they've done
hi, if disable system update then can i enable again ? do you have a cmd comand for enable ?
sefai77 said:
hi, if disable system update then can i enable again ? do you have a cmd comand for enable ?
Click to expand...
Click to collapse
VRaju said:
You can try either should work.
App to disable is ""com.oneplus.opbackup""
Click to expand...
Click to collapse
I'd like to know that as well.
Yes you can re enable if required.
adb shell pm enable com.oneplus.opbackup
KingKazmaOfficial said:
I'd like to know that as well.
Click to expand...
Click to collapse
VRaju said:
Yes you can re enable if required.
adb shell pm enable com.oneplus.opbackup
Click to expand...
Click to collapse
Works for disable and re-enable! Thanks alot!
today i formatted my phone and i try to give this command again but it doesn't work
That's an apk OnePlus released which may help you guys in this situation. If you check news in the Oxygen updater, there's an in depth article about it.
Major failing on OnePlus' part.
Here's the apk they're referring to, apparently it stops the update forcing wipes from OB3 not to go ahead.
https://drive.google.com/file/d/15RO5WSwMZ3PAHktUWMVr4f6sRm-th_he/view
Please check out the article before installing anything.
Edit: actually this is more for the people who were forced to update. Apologies, I'll leave it here as someone may see it.
sefai77 said:
today i formatted my phone and i try to give this command again but it doesn't work
Click to expand...
Click to collapse
Why did you format, did you update to OOS 11?
Also, when running the command line, make sure you open the command prompt within the same folder as your ADB files.
KingKazmaOfficial said:
Why did you format, did you update to OOS 11?
Also, when running the command line, make sure you open the command prompt within the same folder as your ADB files.
Click to expand...
Click to collapse
i formated for cleaning my oneplus8pro and i dont updtae OOS 11. i open command with adb files but i cant do this.
sefai77 said:
i formated for cleaning my oneplus8pro and i dont updtae OOS 11. i open command with adb files but i cant do this.
Click to expand...
Click to collapse
first run the command
Code:
adb devices
to ensure that you phone is connected, and that you have the proper drivers are installed.
Then, make sure that your phone is unlocked (not the bootloader, just actually unlocked so the screen is on). After running that above command, you should see a popup come up on your phone screen asking you to allow permission to your computer. Tap "always allow" checkbox and grant the permissions.
Now try to run the command again.
KingKazmaOfficial said:
first run the command
Code:
adb devices
to ensure that you phone is connected, and that you have the proper drivers are installed.
Then, make sure that your phone is unlocked (not the bootloader, just actually unlocked so the screen is on). After running that above command, you should see a popup come up on your phone screen asking you to allow permission to your computer. Tap "always allow" checkbox and grant the permissions.
Now try to run the command again.
Click to expand...
Click to collapse
i can do it now thanks