I'm trying in every way to edit the file mixer_paths.xml located in vendor -> etc to increase the volume of my phone in capsule and speakerphone (with the headset the volume at maximum is not very high but enough), but I can not get write permissions on the file, any root browser returns an error.
Can someone help me to perform the operation?
HarryCustom said:
I'm trying in every way to edit the file mixer_paths.xml located in vendor -> etc to increase the volume of my phone in capsule and speakerphone (with the headset the volume at maximum is not very high but enough), but I can not get write permissions on the file, any root browser returns an error.
Can someone help me to perform the operation?
Click to expand...
Click to collapse
you could try from TWRP otherwise x-plore with superuser mount writable selected has always worked for me although I'm not sure if I've tried it on this phone.
3mel said:
you could try from TWRP otherwise x-plore with superuser mount writable selected has always worked for me although I'm not sure if I've tried it on this phone.
Click to expand...
Click to collapse
TWRP nothing I've tried, but nothing. Also x-plore: I tried changing the permissions and editing the file, it says it completed the operation, but then recheck or open the file and it didn't do anything at all
Related
I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
If you didn't say you mounted the partition I can only assume it was not mounted as r/w and still at r/o.
copy/paste - visual representation of cp
push - pushing files from computer to phone
They are not the same.
SiNJiN76 said:
I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
Click to expand...
Click to collapse
Yeah, what didn't work? lol.
djmcnz said:
Yeah, what didn't work? lol.
Click to expand...
Click to collapse
the mms app didn't overwrite. But it could have been user error. I'm using Enom's ROM and didn't have the Community Mms Mod checked...so maybe if I had done that first...it would have worked.
Pushing is taking a file from the computer to copy and paste/overwrite the existing file on the phone. What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
SiNJiN76 said:
Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
k?
I didn't try and explain anything (in this thread at least)?
Either way, yes push literally "pushes" a file to a specified location. However that file needs to be written and if the file system is mounted as read only you will get errors.
If it didn't work you must have received an error message (in root explorer for example), what was that message? If you don't get an error message and the file is still not being written then get a better file manager (ES File Explorer).
The suggestion above by 'evilkorn' was to make sure the file system is in read/write mode before you copy the file over... you can do this in Root Explorer or ES File Explorer.
If your file system is in r/w AND you still don't get an error message AND it still doesn't work then I would try an ADB push as a last resort and if that didn't work, reflash and start from step one I think...
SiNJiN76 said:
What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
evilkorn said:
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
Click to expand...
Click to collapse
LoL. You gotta ask a question first before I can answer it. You made assumptions, didn't ask questions. LoL. Anyway, I wasn't trying to crawl under your skin. But maybe next time you can read the OP in addition to just reading the title of the thread? Usually, details are given to accompany the title of the thread on the first post. Either way, I guess I wasn't detailed enough. Thanks for your feedback, tho, appreciate it.
@djmcnz - Sorry, my error in quoting the wrong person. Thanks for you explanation, also.
So, to summarize...Push and Copy/Paste should produce the same outcome, right? Cool...like I said earlier...it was my error in not knowing that I had to use the Spare Parts option in Enom's ROM to enable Community MMS.
I use root explorer all the time when I can't use a computer to use adb. It works fine. Usually if its the system partition you have to click the icon that says r/o and it changes to r/w. This will allow you to write files to the partition. Then from what I noticed a reboot usually fixes any issues of stuff not working.
I am in need of read/write access to my system folder. I am simply trying to copy some ringtones and add a boot animation.
I have SGS tools and ran the r/w script, which allowed me to VIEW the folder with Droid Explorer, however I am unable to actually copy TO the system folder or its subfolders.
Any ideas on what I'm doing wrong?
EDIT - I've also tried to push the files to the phone via ADB, but I get an error telling me "Failed: Operation Not Permitted".
EDIT x2 - I've also got Root Explorer installed on the phone and it showed R/W access, but again, I can't get any files pushed to the phone.
Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App
Did you try fixing permissions through cwm recovery?
try root explorer. and double check superuser permissions
goob1284 said:
Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yup.
Did you try fixing permissions through cwm recovery?
Click to expand...
Click to collapse
I noticed a section for both "mount /system" and also permissions... Both: DONE.
try root explorer. and double check superuser permissions
Click to expand...
Click to collapse
Done & Done...
I've still got no access to R/W in any of the system folders/subs. Any ideas?
I am having the same problem with root explorer..
I have fixed permissions in CWM
It had worked once but now it wont mount r/rw in system folder. Press the icon and it does nothing.
Superuser permission in SGS tools, Root exploer all show active
Any ideas?
Anyone else have any ideas? I'm totally puzzled at this point.
I have sort of fixed the problem..
I go into SGS tools and run the batch file to give r/rw permissions, then I can mount r/rw in system folder, but I loose this each time I reboot and I think when I connect USB..
but it works for the purpose I needed!
I think I've found a work around (or maybe the way it was SUPPOSED to work)...
I rebooted the phone in recovery. Then, selected "mount /system". Then I went to Advanced and "Fix Permissions" (don't know if I had do, just did).
THEN - I was able to FINALLY push the files to the correct folders! I tried it using ADB commands and also with Droid Explorer - Both worked great.
I don't know if the phone was always supposed to be in recovery to do it, but it worked!
adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.
I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!
Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!
This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl
Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works
I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you
hi again
I have small problem that I find quite annoying
Xperia SP on android 4.3 (....1.207 rom)
device is rooted with towelroot + SuperSU,
no matter which file manager with root capability I use and go into SYSTEM folder
and either create new folder and delete it, or copy something from SD to system Audio folder
things get broken...
Folder cannot be deleted even if its newly created, and has nothing init
nothing cannot be copied in Audio folder, as everything gets erased by ... system ?
and my annoyance goes to, if its rooted OS, and I as user have "full access"
why are these things happening ?
is there something I need to learn of how android deals with stuff specially ?
As far as i can remember, i haven't faced this issue in my past (was ages since i last used stock ROM). But i can safely say it might be related to your actual file manager. Can you list me the file managers you used?
I would also recommend trying to use Solid Explorer Classic for the sake of testing, and also Fx File manager.
Basically, when you want to do a change in the system directory, the system partition must be remounted as read-write because the folder resides on a different partition. Android by default mounts system partition as read-only on boot. A file manager is responsible to remount the system partition to read-write before performing an operation on the system partition, and i believe this is where the problem occurs - if the files aren't being copied.
If you can copy the folders but unable to delete, this is most likely a permission issue, and the file manager was probably isn't properly using its root rights.
Please respond with your test with Fx or Solid Explorer classic. You may also try Solid Explorer 2.0 if you wish. NOTE: Please enable Full Logging in SuperSU settings. I'd like to see what is going on (you can too).
Also it is worth to know that although root gives you ultimate rights to modify or alter the OS, there are always technical problems which are caused by various reasons. Plus, there are even barriers of which root power can't even do. For an ultra simple comparison, you can't use root to somewhat modify an app's source code live. But of course, root gives much more freedom to do things compared to no root.
ah yes, you were right, it did depend on file manager after all
tho for unknown reasons 5 of 6 all needed supersu acceess and had root capability, but nothing to operate
I finally found (blue) root explorer, and this one can do it all, sorry for opening this thread
I jumped bit late with whole android thing
I used to do this on my Galaxy S5, way back in the day. I would use Root Explorer to copy a .ogg file that I converted from a .wav file to the root/system/media/ui folder.
I'm trying to do the same on my G6 after rooting. I have full root. Magisk is installed and updated to the latest version. I have Root Explorer and BusyBox installed.
However, this is the issue: when I try to paste the copied file the folder referenced above, it stays on the copying dialog box and never advances. It normally shouldn't take over 5 minutes to copy two files, with a combined file size under 5mb.
If anyone is able to help, it would be greatly appreciated.
Darkness30XX said:
I used to do this on my Galaxy S5, way back in the day. I would use Root Explorer to copy a .ogg file that I converted from a .wav file to the root/system/media/ui folder.
I'm trying to do the same on my G6 after rooting. I have full root. Magisk is installed and updated to the latest version. I have Root Explorer and BusyBox installed.
However, this is the issue: when I try to paste the copied file the folder referenced above, it stays on the copying dialog box and never advances. It normally shouldn't take over 5 minutes to copy two files, with a combined file size under 5mb.
If anyone is able to help, it would be greatly appreciated.
Click to expand...
Click to collapse
I used the total commander apk and I succeeded.
miroo64 said:
I used the total commander apk and I succeeded.
Click to expand...
Click to collapse
I'll give it a shot. Thank you.
Edit: Didn't work. It gave no error message short of saying it didn't work.
Darkness30XX said:
I'll give it a shot. Thank you.
Edit: Didn't work. It gave no error message short of saying it didn't work.
Click to expand...
Click to collapse
After trying different file managers with root access, I found Root Manager. It successfully copied the files over and let's me change their permissions. I confirmed they are the right files by copying back and playing them in a media player.
However, now the system won't play the files during the appropriate action.
It's not playing every system sound, even stock ones, and I don't know why.