Just rooted and the whole purpose was to install secure settings with superuser permissions so I can toggle GPS using tasker.
I have granted it superuser permissions but in the secure settings app the 'helper' file needed for GPS toggle wont install
The error whilst installing it is: Unable to mount partition rw
I then tried to go into CWM in recovery mode and select the zip file manually, but that failed also, Im stuck! any ideas?
Related
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
neomagik said:
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
Click to expand...
Click to collapse
As we don't have write access to /system on a normal booted desire, you have to do all your work in recovery-mode.
I can get into recovery mode ok but how do I edit the file I want from there?
The options I have are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Extract the file out of the rom, change it, than push it back to the rom.
You can do that from ADB shell while your phone is in recovery.
You can find commands how to backup files and push/delete them back to ROM on this forums, or you can search it on internet.
dont forget to mount /system
adb shell in a new terminal screen
then mount /system
I can't figure out what I'm doing wrong.
I've tried the method suggested by allla and ivicask ie, using adb commands in recovery mode and I get the same result as using root explorer, the file appears to have copied successfully it reboots but the original file is back again
I've also tried vastlopers method and after lots of reading found that the device needs to be booted normally to 'remount' however when I try to push the file now it says "Directory not empty"
It seems to me that this adb method is just a long winded alternative to root explorer, none of which get the desired result.
Please help?
Bump. Bump.
I've now tried adb file explorer but can't figure out how to install Busybox on my device.
I'm out of ideas. Someone must know how to edit/overwrite the main.conf file.
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
neomagik said:
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
Click to expand...
Click to collapse
Yes it is. It's also written in the root tutorial!
Phone: Incredible 2, running Android 2.3.3 Stock Verizon ROM
S-OFF and Rooted : using revolutionary 0.4pre4
HBoot: 6.13.1002
Recovery: Revolutionary CWM 4.0.1.4
I'm having ROOT Access/SU problems. I need access to some files in the root/System/ directory and am unable to get r/w.
I s-off/rooted my Incredible 2 using the instructions on this tutorial http://forum.xda-developers.com/showthread.php?t=1219246 (The How To Root DInc2) and the instructions on the revolutionary.io website. (Essentially: Get S-Off via revolutionary> flash recovery CWM> flash su.2.3.6.3-efgh)
The revolutionary s-off process was successful and I got s-off.
I flashed Superuser su.2.3.6.3-efgh-signed.zip and seem to have Root. The binaries are upto date according to the app.
I have Titanium Backup, Root Check, BusyBox Installer installed. I had to install Busybox. All these apps run properly. I can wipe, backup, and install system app data via Titanium Backup. Root Check says I have root access and the correct Busybox location.
The Problem
I installed Root Explorer today and I am successfuly able to change from R/O to R/W and back on the root directory and on the SDCard. But when I go to the System directory I cannot change from R/O to R/W.
Tryed to connect to the Inc2 from my PC (winXP) via ADB. ADB Devices command shows my device. When in ADB Shell the default profile is $. When I type in SU I get back the message "SU: permission denied" I do not get a prompt from Superuser on the phone to give access.
(To see if the problem was in the steps I was doing I tried this on my rooted Incredible 1 and in Root Explorer I was successfully able to remount the System directory from R/O to R/W and back. But the same problem with ADB I have on both Inc1 and Inc2. (Inc1 was s-off/rooted with Unrevoked3/Unrevoked Forever, with su.2.3.6.1-ef-signed.zip.)
I'm not sure what went wrong where, since some of the root access is working. Any suggestions? Help?
Thanks,
that happen to me before. and the only way to change the r/o to r/w is going back to stock,if you have a stock back up rom you have to run that one,and then you can install the rom you want,and the you can change with root explorer s/o to r/w.if you dont have a stock back up you have to install the PG32IMG,and then you have to go to revolutionary and install the recovery.dont forget to turn off the fast boot.if you dont know how to do that,setting,power,and then uncheck the fast boot to off.
I dont think your binaries are up to date.
Try installing SuperUser 3.0 and report back - with updated binaries. The binaries should show at least verison 3.
I had issues to with the Root access that came with revolutionary and this worked for me.
You are on the right path though.
I'd like to try and avoid flashing the original Verizon ROM back on the phone. I'll leave that for last resort. There is stuff that I've done to the phone that I would rather not have to go through to do again.
In Superuser I tap on the 'check for binary updates', the respone after checking is that the 'su is up to date'. The version that I'm currently using su.2.3.6.3-efgh-signed.zip the files are modified in 2008 and 2011. So it seems to be upto date.
Is there a place I can download the latest version of Superuser 3.0?
The version of Superuser3.0 that I was able to find, when I open the zip file, shows all the files last modifed in 2008.
You wont have to flash back.
Follow my advice and install the new SuperUser on the market. It is 3.0.
Once in the application go to update binaries and update anyway.
Reboot and let us know how it works.
Those 2.3.6.3 binaries didnt work for me either. Now im fine after following my own advice.
Oh - and also - check to make sure that you have allowed specific permission for the application you are having issues with - within SuperUser.
You will be pleased to see that the new SuperUser can automatically grant Root to all of your apps...dangerous, but speeds things up.
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
gunnyp said:
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
Click to expand...
Click to collapse
Be sure to click thanks if you haven't already. Lol.
Try wiping data...force closing and uninstalling root explorer (thru manage applications...not CWR).
Should take care of it. And because you are rooted you should have full access to filesystem via adb already.
Sent from my Xoom using xda premium
try mount -t ext3 -o remount,rw /dev/block/mmcblk0p25 /system with adb. thatll remount /system as readwrite
Sent from my Incredible 2 using XDA App
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
trust me you will have to do what i said before in the second post...
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
You paid for Root Explorer. It doesn't work for you. I'd be bugging the developer since it's clearly not doing the job.
@android-incredible
yes, i looking more and more like i may have to flash my rom backup that i made right after s-off. let's see, since i can get su in adb shell i can get done what i need to so reflashing is not utmost urgent.
i'm not sure it's rootexplorer since i've not seen other posts with similar issue. if the flash of the rom backup does not do it, that may then point to rootexplorer. lets see...
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one
Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053
Yeh thanks its working now after reflashing the cwm superuser.
stock Android: 4.2.2 rooted
build: JD39.I9192XXUBMK4
kernel: 3.4.0-1961802
knox warraty: 0x1 (void)
SuperSU: 1.8
* I"ve disabled knox on my device
After I've rooted my phone I've got supersu and busybox installed as usual and granted root permissions to ES file explorer but I can not even edit files in my home directory (sdcard0) when trying to move, copy... files I get "EACCESS denied" error. Here are a few observations I've made:
* There is no such problem when using "root browser"
* when setting SELinux mode to permissive the problem is resolved (setenforce 0 via the terminal) but after each reboot the mode changes back to enforcing, so I've tried to enable init.d and setting to permissive on startup, but that did not work either.
I'm a noob so maybe I'm missing something simple. Thanks.
Try this fix...
lawL3ss said:
stock Android: 4.2.2 rooted
build: JD39.I9192XXUBMK4
kernel: 3.4.0-1961802
knox warraty: 0x1 (void)
SuperSU: 1.8
* I"ve disabled knox on my device
After I've rooted my phone I've got supersu and busybox installed as usual and granted root permissions to ES file explorer but I can not even edit files in my home directory (sdcard0) when trying to move, copy... files I get "EACCESS denied" error. Here are a few observations I've made:
* There is no such problem when using "root browser"
* when setting SELinux mode to permissive the problem is resolved (setenforce 0 via the terminal) but after each reboot the mode changes back to enforcing, so I've tried to enable init.d and setting to permissive on startup, but that did not work either.
I'm a noob so maybe I'm missing something simple. Thanks.
Click to expand...
Click to collapse
Hi, try to change the folders' permissions and ownership with Root Explorer from the PlayStore. Once you are in the folder click the r/o (read only) button at the top to make it change to r/w (read/write). You can try this as well with the Terminal App using the "chmod" command but I recommend using Root Explorer since it's waaaay easier... However, this feature should also be covered somewhere within ES File Explorer.
Hello,
I got an OP3 with latest Open Beta installed. It is rooted via SuperSU ZIP.
Most root apps work, for example "Root Essentials". However, every app that modifies the /system partition does not work. "/system/app mover" gives me the error "could not remount /system", for example. AdAway says "Could not copy host file".
This problem occured on earlier Open Beta builds as well.
Mounting /system R/W via "Root Essentials" doesn't work either, it does give me a "successfully mounted" message but modifying /system still doesn't work.
Has anyone got a solution for this problem?
Push
OxygenOS does this to me sometimes. There is one thing that helps (sometimes):
1. Boot into recovery.
2. Go into mount
3. Untick keep system read-only (If it's unticked tick and untick it again)
4. Remount system (tick the box next to /system, if it's ticked, untick and retick it)
5. Reboot
Also which root solution are you using? Magisk or SuperSU?
Which ROM are you on? I have only seen this problem on OxygenOS.
Did not work sadly. I am on latest OOS with SuperSU
Got the same issue, does anyone know how to fix?
Haven't found a solution yet Don't want to change ROM, OOS is so stable and pretty
Any fix for this yet this happen to a buddy on mian .
Use magisk SuperSU is not mantained anymore