"This operation requires elevated permission.try changing into root access mode"
I'm running a cm 14.1 on moto g2. i have installed supersu given it superuser permissions and even in the file manager i have changed it into root access mode but still every time when i try to access my external card in the file manager it prompts me this. any suggestions ?? coz i have tried mostly everything
Related
As title, I'm trying to root a development board running 4.2.2. I do have root access and put busybox and su, but my problem is that whenever I start apps that require root access, superuser never gives me prompt asking whether root access is allow (yes, my setting in Superuser is to prompt for every apps that require root), as a result, the app would not run reporting that my device is not rooted. As an example, when I trying to run droidvncserver, it would tell me "could not start server", but if I start it as root on a shell, it would run and start server, this leads me to think that droidvncserver is not requesting root access or Superuser does not know that droidvncserver needs root access. I'm pretty sure I'm missing something in my system, but what is it. All this works on a rooted phone, but not on the development board. I've read through some of the rooting script for other phones, mostly include remounting /system as rw and put busybox and su onto the system, and that's what I've done on the board, but there's just no connection between those root-require apps and superuser. Anyone knows what I'm doing wrong/missing?
Hello, noob question, CM 14.1 says I have to set change to root access mode to access External Card. I did change but the error still says I have to change it to root even its already in Root access mode. What do I do?
my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.
I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?
I have a Blu life one x2 that I recently repaired a charger on, and rooted using a process I found here, but I don't remember which, I know I downloaded Kindle fire USB drivers with it though, anyhow, I managed to adb/fastboot root with twrp recovery. Now however now I use any app, exception bring super user, which requires root my phone crashes and reboots. I cannot install BusyBox due to this. I tried using es file manager to ensure RW but it only crashes too, and doesn't fix the crash. Note my phone admits it has root access via es and cpu-z ( the CPUid program made for Android instead of PC) I cannot find anything to help so I'm posting this with hope someone will know a fix,
Important to note the following about my device
Blu life one x2
Stock rooted rom
Twrp recovery Iso from adb root
Marshmallow 6.0.1
External 32gb SD formatted as internal
System folder according to BusyBox has 25mb free (cannot install to any of the folders due to crash)
Lucky patcher was the first app I tried and it crashes after granting root access, same with BusyBox as soon as it "checks the system" it crashes it.
Es "root explorer" Grant set RW (crash Android) reboot app main menu (crash Android)
Temp fix revoke ROOT to apps apps run fine (except lucky which now NEEEDS BusyBox)