Related
Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
doublehp said:
Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
Click to expand...
Click to collapse
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
akitten007 said:
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
So, is there a way to install busybox via recovery ?
I did 3 things in recovery: all in /system/xbin
- chmod +s su
- touch t
- mkdir tmp
after reboot to normal mode, SUID bit was removed, but t and tmp are still here.
So, how do I install busybox ?
New issue: /data has the nodev flag; is it possible to remove it ?
I did not found /dev/shm ; was it moved somewhere else ? Any other place for similar use ? (world write temp folder in RAM).
akitten007 said:
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
doublehp said:
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
Click to expand...
Click to collapse
Now you're starting to go over my head. If you want to keep your current kernel, I would try using this method here to manually add the module that disables the protection http://forum.xda-developers.com/showthread.php?t=2702575. I usually just install busybox using rom toolbox or any other busybox app. You could search for a busybox zip, but just disabling the write protection is a better option in my opinion. And I have actually 0.00 idea what flags mean on folders (sorry).
I rooted using TWRP recovery and super su. That guide you posted gives unnecessary instructions. TWRP automatically installs the SU binary and Super su the first time you boot into it. I was able to update Super su via google play, no need for the update zip. Just follow the instructions after rebooting to system from TWRP recovery.
I'm s-off, unlocked, my kernel, firmware and os are stock, only thing that isn't is recovery. I have write access to system and external sd card. All I did was make it writable with root explorer and have installed busy box no problem using this app https://play.google.com/store/apps/details?id=stericson.busybox.
I was given a better fix.
http://forum.xda-developers.com/showthread.php?t=2701816
In short:
adb push /mnt/big/tmp/wp_mod_m8.ko /mnt/sdcard/Download/
insmod /mnt/sdcard/Download/wp_mod_m8.ko
mount -o remount,rw /system
cd /system
touch z
mkdir zz
reboot
[email protected]_m8:/storage/emulated/legacy # cd /system/
[email protected]_m8:/system # ls
app
bin
build.prop
customize
etc
fonts
framework
lib
lost+found
media
priv-app
tts
usr
vendor
xbin
z
zz
[email protected]_m8:/system #
The miror is on maintainance for now. So, the guy on IRC gave me his local backup. I will push it here for 30 days:
http://dl.free.fr/gSha53ljz
(server will delete it after 30d nobody downloads it)
Busybox still fails to install; don't know why.
So i'm trying to create a profile in tasker to enable/disable airplane whenever i'm connected to Wifi and it seems SecureSettings isn't allowing root actions even though it has root privileges. Anyone know an app that works with tasker that can allow me to enable/disable airplane mode?
Thanks!
metpage said:
So i'm trying to create a profile in tasker to enable/disable airplane whenever i'm connected to Wifi and it seems SecureSettings isn't allowing root actions even though it has root privileges. Anyone know an app that works with tasker that can allow me to enable/disable airplane mode?
Thanks!
Click to expand...
Click to collapse
Is there any particular reason you are using systemless root?
Sent from my Nexus 5X using Tapatalk
Mainly for Android Pay to work but I'm not married to systemless root if system root makes this work. However I may have found a workaround using Locale instead.
Sent from my Nexus 5X using Tapatalk
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Thanks I'll give this a shot if Locale doesn't work
Sent from my Nexus 5X using Tapatalk
lightningdude said:
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Click to expand...
Click to collapse
I have the same problem, running CF-Autoroot on my S7 edge. I would like to try your trick but am not sure how to exactly . Could you please explain a little bit more in detail how this is done?
EDIT: nevermind, i solved it my self using THIS method.
Thanks in advance.
Works for Secure settings, but it's broken Titanium backup
When I try to implement this in adb I get the following:
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system'->'/system': Device or resource busy
Can anyone help? Would greatly appreciate it. Thanks!
facted said:
When I try to implement this in adb I get the following:
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system'->'/system': Device or resource busy
Can anyone help? Would greatly appreciate it. Thanks!
Click to expand...
Click to collapse
Try using this command instead:
mount -o rw,remount /system
It worked for me
PiousInquisitor said:
Is there any particular reason you are using systemless root?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
is there system root for 7.0 or is this thread about 6.0.1?
niklus101 said:
is there system root for 7.0 or is this thread about 6.0.1?
Click to expand...
Click to collapse
There are unofficial versions in in the super su section here.
LSI said:
Works for Secure settings, but it's broken Titanium backup
Click to expand...
Click to collapse
Yeh, unfortunately, it does, same with AdAway.
Does it have to do with Android N or is it about the fact that touch /sbun/su fails due to sbin being read only?
If someone knows a solution, that would be great.
LSI said:
Works for Secure settings, but it's broken Titanium backup
Click to expand...
Click to collapse
I have the same problem with this too. It would be great to have a solution, or at least knowing how to reverse it would be great.
lightningdude said:
In either a terminal on your phone, or via adb shell from the computer, enter these commands:
Code:
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
I can't remember if you need to reboot or not, but might as well, just in case. Afterward, run your task and allow Secure Settings root access.
After doing this, Tasker and Secure Settings works for me. If this doesn't fix your problem, I don't know.
Click to expand...
Click to collapse
Do you hit enter at each line?
I'm doing this exact thing with Tasker and Magisk. I just had to add a quick edit to my build.prop, and then Tasker could recognize root with Magisk, and it worked fine.
Fit some reason I'm getting this error when dropping the commands
That's because it's mount -o not -0.
I just got secure settings and tried these commands in terminal. However they don't work. I get device or resource busy.
I'm on PureNexus 7.1.1 root via supersu on my Nexus 5x IF that matters in any way.
Edit: never mind. Solved it by replacing 0 with o. *Facepalm*
I've encountered the same problem in Android 7.1.2 and the above solution didn't work out for me. Secure Settings system+ is unavailable.
Any other solutions?
The first command
mount -o remount,rw /system
gave me the following result:
mount: '/dev/block/platform/msm_sdcc.1/by-name/system' not user mountable in fstab
1|jfltexx:/ $
It seems like an error.
akran said:
I've encountered the same problem in Android 7.1.2 and the above solution didn't work out for me. Secure Settings system+ is unavailable.
Any other solutions?
The first command
mount -o remount,rw /system
gave me the following result:
mount: '/dev/block/platform/msm_sdcc.1/by-name/system' not user mountable in fstab
1|jfltexx:/ $
It seems like an error.
Click to expand...
Click to collapse
Try this:
Code:
mount -o rw,remount /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o ro,remount /system
I'll share how I fixed this problem, which might be a LOT easier for some people.
Install a file manager that has root access (ie Root Explorer).
Navigate to /system/bin
Click whatever button to mount /system as rw.
Create a directory (or file) and call it su
Reboot phone
Open Secure settings and enable root.
At this point (and with above solutions, Android Pay is broken. If you want it back.
Open file manager again.
navigate to /system/bin
mount rw
delete the su folder (or file) you created earlier.
reboot.
Secure Settings only checks for su file the first time. Once it's been granted access, it no longer looks for su, it just tells the system it needs root access. So it will work the way its supposed to, even though it no longer can find the su file in expected location.
Also, for those that don't know, "touch" creates a file. So if you want to pass SafetyNet still, go back and delete the 3 files created from the touch command. And note that you only need to do 1 of them, not all 3, for Secure Settings to work.
Hello, I am using the unofficial Lineage OS 7.1.2, with SuperSU 2.82 and a 3.1.1 TWRP & .160 FW
I'm trying to add some files like sony SoundEnhancement, some lib's files, Walkman, build.prop and stuff from Sony to /system
But I always encounter a problem like "system is read-only" or "you don't have permissions blaaah"
I tried at least 2 days with ADB (haven't tried ADB Sideload yet)
Or the app Mount / System RO/RW from play store
I also tried with Root Browser to change the file but no success
If someone would take some time to explain to me even if I've browse a lot of website I still don't understand why it doesn't work -.-
Thanks in advance
N_A
Use terminal app.
write down below commands
su
mount -o remount,rw /system
Now u can change permissions.
You have to use this command after every reboot if u r going to play with system.
debbuger said:
Use terminal app.
write down below commands
su
mount -o remount,rw /system
Now u can change permissions.
You have to use this command after every reboot if u r going to play with system.
Click to expand...
Click to collapse
Hello, i tried and it failed
I don't have my phone now but I'll try again, thanx for your time
Tried this command on the android command prompt, continuously gives me message that the /system is being used by another resources.
Is there a way to add this statement in some sort of init.d component? Can anyone provide the location of this script file?
Has anyone figured out how to edit the /OEM partition? I've tried through root Explorer and through adb shell Su via terminal
Sent from my Moto Z (2) using Tapatalk
If it's anything like /system it's mounted read-only.
If you're rooted and run Linux:
# adb shell
$ su
# mount -o remount,rw /OEM
... and see what happens.
I don't know if the phone is running SELinux or not, and if so you'll need more special steps. Find out with # getenforce
Quantumstate said:
If it's anything like /system it's mounted read-only.
If you're rooted and run Linux:
# adb shell
$ su
# mount -o remount,rw /OEM
... and see what happens.
I don't know if the phone is running SELinux or not, and if so you'll need more special steps. Find out with # getenforce
Click to expand...
Click to collapse
Aye, I attempted to remount like this but it will not work for some weird reason.
Sent from my Moto Z (2) using Tapatalk
elijahaf97 said:
Aye, I attempted to remount like this but it will not work for some weird reason.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
wipe it using twrp, and dont use it. remove the items from oem you wish to keep and migrate them to the /system where they need to go, set perms and enjoy.
OEM is read only and is mounted to google, and if you delete something it gets put back, just wipe that partition and enjoy lol
Team DevDigitel said:
wipe it using twrp, and dont use it. remove the items from oem you wish to keep and migrate them to the /system where they need to go, set perms and enjoy.
OEM is read only and is mounted to google, and if you delete something it gets put back, just wipe that partition and enjoy lol
Click to expand...
Click to collapse
Last time I wiped it I was unable to boot.
Sent from my Moto Z (2) using Tapatalk
elijahaf97 said:
Last time I wiped it I was unable to boot.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
that shouldnt be the case... again you can just move everything from oem to /system and match the perms 1st then wipe it and essentiall all would be good, may need to wipe cache/dalvik cache to rebuild data for apps after move.
You can't add data to oem, but I was able to remove items from oem in TWRP with a kernel that had verity removed and state still green. (The TWRP custom kernel on Oreo and Pantheon both have this option). I still kept safetynet status green as well doing it through TWRP. Be sure to mount oem first!
Doesn't work on latest stock, OEM r/o. Any thought?
If you're just trying to debloat then you can follow this guide.
Uzephi said:
You can't add data to oem, but I was able to remove items from oem in TWRP with a kernel that had verity removed and state still green. (The TWRP custom kernel on Oreo and Pantheon both have this option). I still kept safetynet status green as well doing it through TWRP. Be sure to mount oem first!
Click to expand...
Click to collapse
Can you explain how to mount /oem partition like you did? I cannot for the life of me mount it in twrp to remove unnecessary apps and keep safetynet good?
Latest Sprint firmware. Latest TWRP. Latest Magisk. Latest Pantheon 8.0 kernel. Any help is greatly appreciated.
Typically I use superSU. But Epic games just made the gamepad Fortnite compatible and I'd like to try it WITH some type of root (Magisk) that won't mess up the safetynet check, yet be able to still have most of my usual root freedom.
gokart2 said:
Can you explain how to mount /oem partition like you did? I cannot for the life of me mount it in twrp to remove unnecessary apps and keep safetynet good?
Latest Sprint firmware. Latest TWRP. Latest Magisk. Latest Pantheon 8.0 kernel. Any help is greatly appreciated.
Typically I use superSU. But Epic games just made the gamepad Fortnite compatible and I'd like to try it WITH some type of root (Magisk) that won't mess up the safetynet check, yet be able to still have most of my usual root freedom.
Click to expand...
Click to collapse
Haven't tried on Oreo. Only got it to work on nougat by forcing verity off and disabling encryption.
deleted ...
Hi everyone I'm trying to make a Tasker task to delete some apps which included in LOS after build update but Tasker or built-in terminal can't mount /system rw ( tried command "mount -o rw,remount /system" command causes no errors or anything but still system is ro ) but apps like Root Explorer can mount it using LOS 15.1 on Xiaomi Mi6 with Magisk v17.1 thanks in advance and sorry for my terrible English :/
Are there any hope for this? For now, my device has only the LOS recovery and so I can't flash a zip. Is there a way to mount /. Set the selinux to moderat didn't do the trick?
Any ideas?
Micha_Btz said:
Are there any hope for this? For now, my device has only the LOS recovery and so I can flash a zip. Is there a way to mount /. Set the selinux to moderat didn't do the trick?
Any ideas?
Click to expand...
Click to collapse
I solved my issue with making a flashable zip for delete apps etc. So, i didn't tried again to mount system RW
A little spelling mistake by me. I can't flash a zip for now.
Micha_Btz said:
A little spelling mistake by me. I can't flash a zip for now.
Click to expand...
Click to collapse
I assume u r using Mi6 right? Did you tried another recovery like THIS?
No, I use a BQ Aquaris X2 Pro
Micha_Btz said:
No, I use a BQ Aquaris X2 Pro
Click to expand...
Click to collapse
Oh, sorry man I couldn't find TWRP for your device. But its must be recovery related so try to find another TWRP besides yours, good luck.
For all that looking for a solution:
enable root for adb
and then
adb root
adb disable-verity
now you can reboot and can remount /
Micha_Btz said:
For all that looking for a solution:
enable root for adb
and then
adb root
adb disable-verity
now you can reboot and can remount /
Click to expand...
Click to collapse
Thanks very much for posting this. Could you explain what this is supposed to do? Is there something that changed in the filesystem structure in Android 8.x that makes `/system` not mountable as an independent partition?
Although your instructions work (I can see that `adb disable-verity` persists across reboots), I still can't do `mount -o remount,rw /` afterwards. I get an error telling me that "device /dev/root[/code] is read-only". Hrm.
Are you sure you did the disable-verity command as root? There should be an answer from adb that is really been disabled.
https://source.android.com/security/verifiedboot/dm-verity