Hello,
I have root and busybox on my Pixel, but AdAway is failing to copy the hosts file, and I am unable to modify permissions of the system folder. I just keep getting the error "operation failed" using Solid File Explorer.
Anyone know why? I obviously have root access, why am I being denied?
SubjectGinger said:
Hello,
I have root and busybox on my Pixel, but AdAway is failing to copy the hosts file, and I am unable to modify permissions of the system folder. I just keep getting the error "operation failed" using Solid File Explorer.
Anyone know why? I obviously have root access, why am I being denied?
Click to expand...
Click to collapse
was it working on any other android O developer preview releases ?
my best guess is that android O is using toybox instead of toolbox for mount and it matters in what orders the parameters are passed to the mount command.
mount -o remount,rw /system was working in 7.1.2 , but it is not working on 8.0, it must be mount -o rw,remount /system
the app developers will have to change the command in their apps...
of course this is only a wild guess, because there can be a lot of other reasons, this just something that I stumbled upon and got help with here on XDA. (thanks again @jcmm11 !!!)
Make sure you have the newest version of Chainfires SuperSU for pixel that fixes the system mounting
Just go to preferences and tick " enable systemless mode"
Related
OK. I have been searching all over the place, and there were solutions, but my phone will not listen to me.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
Click to expand...
Click to collapse
On the 2nd part, it will not allow me to mount -o rw,remount /dev/block/stl9 /system.
The terminal emulator is not receiving the "superuser permission", since it's not even asking for the superuser permission.
I did not deny the app nor ignore. I tried reinstalling the terminal emulator, same thing happens.
Also I downloaded ROM Manager. It downloaded me the flashclockworkmod recovery, but it will not reboot into that. Instead it shows the regular recovery mode, and when I try to install the update.zip manually, the error shows again despite the fact that I did all the parts except the 2nd step, because my terminal emulator kept getting denied access when I entered that in.
Please help me. I don't know what hard life my phone is going through.
Asked and answered many times. You could have posted in an existing thread. If your phone is not rooted you will not be able to do this.
My phone is rooted. It has superuser app, along with other apps that require superuser permissions.
How would I have done step 3 without my phone being rooted? if by using root explorer?
I just stated that Terminal Emulator is not receiving the "superuser permission".
I don't know how to manually give Terminal Emulator the "Superuser permission" since, it is not asking me for it, as previously in Eclair.
Are you entering
Su
Sent from my SGH-I897 using XDA Premium App
? I am sorry, I did not understand what you said.
on my Su, I have
Allow
AdFree
ROM Manager
SGS Tools
because they asked for su permission.
But on the terminal emu, it does not even ask for a su permission.
to do unrooted you use adb to push
or root it then use root explorer to drop new 3e fix
try uninstalling terminal em and reinstall. you might have pressed back when it asked the first time, that will screw you
When you mean drop new 3e fix, does that mean to delete file and replace with the updatedone on xda?
I did that previously and rebootseveral times before, but same error came up
Thread closed, already answered.
i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me
How about making an insecure kernel so you can access root without requesting su?
xlSKYFiRElx said:
i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me
Click to expand...
Click to collapse
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)
janekmuric said:
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)
Click to expand...
Click to collapse
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I think the adb insecure app still requires su, you can upload the boot.img and i'll make it insecure (automatically root via adb, no su required)
Oooohh
xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0
janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
3DMapPlayer said:
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0
Click to expand...
Click to collapse
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
persist.mtk.aee.aed=on
ro.debuggable=1
persist.sys.usb.config=mass_storage,mtp
persist.service.acm.enable=0
ro.mount.fs=EXT4
Click to expand...
Click to collapse
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img
Got it!
xlSKYFiRElx said:
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img
Click to expand...
Click to collapse
Flash the attached ZIP. It will reinstall SuperSU and all needed files.
I have a Sony xperia M2 D2303 with kitkat 4.4.4 and compilation number 18.3.1.C.1.17.
I have successfully rooted it using KingRoot v4.9.5.
Also I have checked that system is rooted using tools such as root checker and it says rooted.
Now, I am trying to remount /system partition as RW but without succcess.
I have googled and tried several solutions posted here but nothing works for me.
Access to /sys/kernel/security/sony_ric and try to disable sony ric security using:
problem here is that sony_ric folder is empty, I mean, there is no "enable" file and I cannot create it as partition is RO (read-only).
Using ES file explorer or other file explorers as root I have tried to remount partition as RW but it fails.
Code:
echo 0 > enable
Using ROM Toolbox pro, and then from terminal emulator I have tried some commands:
Code:
su
mount -o remount,rw /system
fails.
Code:
su
system/bin/mount -o remount,rw /system
also fails.
Code:
adb shell
su
mount -o rw,remount /system
also fails...
I have tried to install busybox but it fails as well.
I have tried the method explained here but when executing the command:
sh /sdcard/mrw/root.sh
some errors appear as script tries to do things in /system so since it is read-only (not rw) it fails.
Also I have tried the method using SuperSu-me explained here but without success. It completes ok but then SuperSu is executed automatically. SuperSu says to update binaries so I update binaries, then another screen comes saying that another root app was detected, so I press the button to uninstall it and continue installing SuperSu. SuperSu says "Installing ........" and then it crashes, that is, it appears a screen with two buttons, "How to update" and "Reboot". Kingroot, purify apps continued installed and working, and I cannot replace them with SuperSu.
So at this point I have no idea what to do...
My conclusion is that all these tools need to make changes to / and /system but since I have these two partitions set to read-only (cannot make them rw) then all these tools fail. So I think the main cause is that I have / and /system readonly.
Any help will be highly appreciated.
Please, help!
Hi all,
because there is actually no persistend root on the Huawei Mate 9 (system modifivations are discarded after reboot) i would like to run system modifications directly after booting the device.
To do that i am going to use tasker.
For example i want to delete the "camera_click.ogg" file to avoid sounds when making photos with WhatsApp.
Using root explorer i only have to tap on mount system r/w and delete the file.
So i tried the following code in the android shell (which can be run within tasker):
Code:
su
mount -o rw,remount /system
rm -f /system/media/audio/ui/camera_click.ogg
But the system is still not writeable! And mountimg via root explorer only works again after a reboot...
Once with a similar code i got an error message like "resource busy".
What can cause this Problem and how can i delete this system file?
(note: i am not so familiar with Linux, only Raspberry Pi knowledge )
Thank you for helping in advance!
It is same dm-verity problem.
You have to modify boot to turn dm-verity off.
5[Strogino] said:
It is same dm-verity problem.
You have to modify boot to turn dm-verity off.
Click to expand...
Click to collapse
Thank you for your answer!
I will try this tutorial:
https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590
Hope it works...
Hi all, just updates my Galaxy S7 to the latest firmware (April 2017 security patch). I have rooted the phone with SuperSU and installed BusyBox.
For some reason, no matter what I try, I can't seem to make an app a system app.
/system/app mover gives me a "Could not remount /system" error.
I have used ES File Exlporer to move the app manually but when opening the app I don't have the options which are usually enabled when it's a proper system app.
I have also tried to change directory permissions and tried to run the following command:
mount -o rw,remount,rw /system
Which gives me a "device or resource busy" error.
Please help this is doing my head in.
Did you set the correct permissions on the app once moved?
*Detection* said:
Did you set the correct permissions on the app once moved?
Click to expand...
Click to collapse
Yes, changed permissions so all could read and write.
mick1988 said:
Yes, changed permissions so all could read and write.
Click to expand...
Click to collapse
Set permission 744 (-rwxr–r–) on it and see how it goes
mick1988 said:
Hi all, just updates my Galaxy S7 to the latest firmware (April 2017 security patch). I have rooted the phone with SuperSU and installed BusyBox.
For some reason, no matter what I try, I can't seem to make an app a system app.
/system/app mover gives me a "Could not remount /system" error.
I have used ES File Exlporer to move the app manually but when opening the app I don't have the options which are usually enabled when it's a proper system app.
I have also tried to change directory permissions and tried to run the following command:
mount -o rw,remount,rw /system
Which gives me a "device or resource busy" error.
Please help this is doing my head in.
Click to expand...
Click to collapse
try this and tell me if worked . mount -o rw,remount,rw /
after try this ls > f.txt if give you read only you must set permisive mode by comand setenforce 0