Database Users

Cannot for the life of me get system r/w permissions

I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.

You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.

Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.

[Q] rooted a500. can't delete system apps

I rooted my a500 successfully and have super user access. problem is, I still can't rename system apps or uninstall them. I tried using variety of file explorers including root explorer. any suggestions??

anybody? this is driving me nuts

jaya500 said:
anybody? this is driving me nuts
Click to expand...
Click to collapse
Get Titanium Backup and you can uninstall anything on the device. Becareful what you get rid of though.

if you want to give root explorer a shot again, when in the folder there should be a button up top that says "Mount R/W" ... press it, and it should change to "Mount R/O" when its showing mount r/o it means your folder is read/write enabled so at that point you should be able to change / delete / whatever you want on that folder.
give it a whirl, i suspect that was your issue. if not, then give titanium a shot but be careful either way

Hogmeister said:
if you want to give root explorer a shot again, when in the folder there should be a button up top that says "Mount R/W" ... press it, and it should change to "Mount R/O" when its showing mount r/o it means your folder is read/write enabled so at that point you should be able to change / delete / whatever you want on that folder.
give it a whirl, i suspect that was your issue. if not, then give titanium a shot but be careful either way
Click to expand...
Click to collapse
I used root explorer. It is stuck on r/o. I click r/w and no change. I used titanium backup and phone.apk wasn't listed. I really want to fix this battery drain

"Get Titanium Backup and you can uninstall anything on the device. Becareful what you get rid of though."
Does anybody have good suggestions for what apps can safely be removed?

If you don't have busybox installed a lot of "root" apps will fail to operate, since you haven't mentioned it, it is the first thing that springs to my mind...

jaya500 said:
I used root explorer. It is stuck on r/o. I click r/w and no change. I used titanium backup and phone.apk wasn't listed. I really want to fix this battery drain
Click to expand...
Click to collapse
Check superuser applist and see if root explorer is listed
If not, then maybe you denied root access

Alejandrissimo said:
Check superuser applist and see if root explorer is listed
If not, then maybe you denied root access
Click to expand...
Click to collapse
1) You have not actually rooted the device -or-
2) Go to the superuser app and check the deny app list
3) Don't delete system app, instead, rename them is better

[Solved] 2+ Kindle Fires on Same Wifi Router Disrupt Each Other

Me and my best friend both have Kindle Fires now. I rooted & flashed the latest MIUI onto both of them successfully over the past week, so we're running the latest version available. What we've found is that when we both try to attach to his wireless router, they seem to disrupt each other or confused the router and eventually our wifi goes bye-bye on our Kindles. When just one of us is trying to attach to his router, it goes through fine & seems to stay connected well without any issue.
Can anyone offer any recommendations on how to perhaps customize the wifi connection on either the Fire or the wifi router to try and resolve this issue?
Thanks much for your help in advance! Please ask any questions if I left out any details that could help : ]

Does MIUI have the MAC address problem? That'd be the first place I'd check. THen I'd check the router and see exactly what they're trying to do. My thoughts:
Either they have the same MAC, same name, or are vying for the same IP.

http://forum.xda-developers.com/showthread.php?t=1406845

Thanks for the feedback, guys! And thank for that related thread link! I reviewed that post and I have to admit, I'm a lil lost with where to start or what to do with that. I have a feeling both devices may be running the same MAC address, but I'm in the process of confirming that today. I also tried forcing a static IP on the Fire when connecting, but that didn't seem to resolve the problem.
Anyone have any, dare I say, more simple instructions for how I might go about altering my devices MAC address with MIUI? I'm not sure that the information in that post is fully applicable to the MIUI rom, so I'm hesitant to begin trying to give it a go, and plus, I might need something a little more noob-friendly... I could use a little more handle-holding with this, as I'm fairly fresh to rooting & flashing ROMs (but fairly computer literate).

look at post #24 in the linked thread - seems to be a easier solution

Oh, thanks! ... That does look much more manageable Now to just figure out where to get the file from the stock ROM and replace it. I did a backup of my stock stuff via TWRP prior to flashing MIUI, so does anyone know where I can locate this file from the stock amazon ROM after I've completed a backup of stock via TWRP?
I then assume that after locating the stock version of the file, that I would just replace the file in the root directory/system/bin right on the Kindle when it's attached to my PC via USB.
Yah.. I'm a noob, but trying! : \
Stock file I need to find: /system/bin/wlan_loader

there is one attached 2 or 3 posts after #24 - that should do it for your needs

Great! Thanks again!!!
This part of the post gets me a little lost. I assume I need to purchase & download Root Explorer ($3.99 in Market). As for performing the same thing this person did, I'm not quite sure how to go about doing that. One question I have is: Is Root Explorer absolutely necessary to perform this file replacement? It seems a little more involved than just simply replacing the file on the device while it is plugged in to my PC via USB.
I used root explorer, mounted as r/w, made a copy of the original JIC, overwrote the existing file within /system/bin and modified the permissions to appear as the original (rwxr-xr-x) rebooted leaving the system as r/w
Sure enough mac address is the same as when I was in 6.1 Kindle Fire OS.
Click to expand...
Click to collapse
Specifically, here are the things I'm not 100% clear on:
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
3) Can file permission changes as described above be performed in Root Explorer?
I greatly appreciate any insight! This appears to be the solution to my problem, not it's just a matter of execution on my part. Thanks, guys!

would use file explorer from the market - no cost and does the same
if you activate "root explorer" and "mount as root" in the settings all at the bottom
here the link:
https://market.android.com/details?id=com.estrongs.android.pop&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
Click to expand...
Click to collapse
file explorer does this with the above settings automatically
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
Click to expand...
Click to collapse
would mean he means the file to exchange
3) Can file permission changes as described above be performed in Root Explorer?
Click to expand...
Click to collapse
you can also do with file explorer - long tap on file - properties - change permission

Awesome - b63 - you're excellent
Ummmm... But I have to ask a really stupid question. I can't seem to find the /system directory on my Fire. I already had ES File Explorer... and I'm in it now, and I can only look around on my SD card it seems... Is the /system directory on the main internal storage of the device, or on the 'SD card?' Any help in finding this directory on my device would be appreciated! Sorry for the nooby questions n such

are the root settings made in the settings of es ?
then you can set your start directory to / somewhere in the settings
or simply go one directory up
when you are on / then you see the system directory like all the others (sdcard also)

OK... I'M SO CLOSE!
I got up to the root directory ( / ) and found the /system/bin directory... I have the new (well, old stock version) wlan_loader file from the linked thread that I downloaded on my Kindle on the SDCard ready to overwrite the existing file.
I definitely have Root Explorer on in ES File Explorer - it prompted me to allow and I did every time it asked. I then tried to copy the stock version of the file over my current version in /system/bin, but it said that the copy failed. I then went and tried to delete the existing file in /system/bin, but it said something like 'this file cannot be deleted' I'm not sure what is keeping the file locked. Do I need to modify the permissions of the file to be writable or something?
I hard-pressed on the file and tried to play around with it, but the only close option I have is 'Properties,' which didn't seem to allow me to change anything about the file though. So, I'm stuck : \ Help!?

OK, I got it! I didn't flip the 'Mount /, /system as writable option after switching on Root Explorer :\ My bad! But I was able to overlay the file now Let's test my MAC address now after rebooting.

looks promising ...

GET-R-DONE!
Yahoo! I got it!
I rebooted and everything seems to be functioning just fine - I'm connected to Wifi like normal, no big deal... AND, my MAC address is totally different than what it was before, so I think this did the trick!
Now to test it concurrently with my best friend's Kindle to ensure we can sit on the same network / router together. If it doesn't work, then I'll look to replace his wlan_loader file as well
Thanks for all your persistent assistance b63! I really appreciate it : ]
Was fun, and I learned a lot : ]

but take care if you change his one as well not to end up with the same mac again ...
and as allways - glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Help with ADB/Ad Hoc on ICS

Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?
TIA.

tlyonstlyons said:
Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?TIA.
Click to expand...
Click to collapse
You're not missing anything. The root method, does not give you true 100% System R-W access. Not with the stock bootloader. What you can try,
Copy your wpa file to the internal memory (remember where it is) (also long press and select copy)
Then run the included app "a500 Remounter" and select the System R-W option. (this was installed when you rooted) Then quickly go to your file manager, and set /System to R-W and try to paste your wpa file there.
You;ll have to play with this to get it going. Might have to do it a couple of times. This was a big pain, as I had to be very quick when doing things, as the R-W went away quickly.
I know you tried this a couple of times, but try it again. Also, make sure you;re using his version6 root app. It's a little better.
It's the reason why I moved to the ver3 hacked bootloader&kernel combo.
Your R-W usually goes away after you close the file manager app.

Hurray!
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.

tlyonstlyons said:
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.
Click to expand...
Click to collapse
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.

Moscow Desire said:
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.
Click to expand...
Click to collapse
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2

blackthund3r said:
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Maybe on some systems it does. I brought this up a few weeks ago. Maybe it's tablet specific.
After a week or so, the Remounter failed to change System to R-W. It claimed it did, but Root explorer still showed R-O. You couldn't change it. No other changes were made to the OS.
Ver6 did the same under ver2 bootloader with stock kernel. You had to be quick to do the changes, as the other user said. It's not a fluke.
Other known oddities,,,
File Explored HD would not recognize it. Failed to change System to R-W, Updating to Ver3 BL and kernel fixed this.
Of course it's a damn fine tool. It works well for most people. And we're thankful you take a part in development. Wish more would get involved.

[Q] Rooted Stock MDL - ES File not allowing delete

Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.

DevonSloan said:
Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.
Click to expand...
Click to collapse
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out

Goose0121 said:
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out
Click to expand...
Click to collapse
Thanks, but that was actually the first thing I tried - it brings up the rename dialogue, but then after change and "ok", nothing is changed. Same with Astro and Root File Manager.
Thanks, though.
Anyone else?

Try pressing Menu and then going to "Root Explorer" and then "Mount R/W"
From there, make sure the path shows RW instead of RO. Click ok.
Exit out of ES File Manager and come back in and check the Root Explorer Mount R/W again to see if RW stuck. If it did, try to see if you can delete.

apexcell said:
Try pressing Menu and then going to "Root Explorer" and then "Mount R/W".
Click to expand...
Click to collapse
Clicked on root explorer and it gave a (paraphrased) "ES File Explorer has been given superuser privileges for interactive shell" (or something close to that), but I cant find "Mount R/W" anywhere.
And trying various things keeps giving me "device not supported" errors. Again, a paraphrase as the message isnt on screen long enough for me to get the exact wording.
Thanks again for the help.

Is this what comes up when you click on root explorer?

apexcell said:
Is this what comes up when you click on root explorer?
Click to expand...
Click to collapse
No. Nothing opens up. Same settings menu screen, there is just the message that appears below, then disappears, about "superuser permission granted.

I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."

Hmm, that's definitely not right. Try going to the Application manager, to ES File Explorer, Clear data, Uninstall, then re-installing it through Play Store. See if it still does that.
You should definitely get that screen when you go to root explorer.

cap167 said:
I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."
Click to expand...
Click to collapse
That is exactly what is happening with me.
Thanks Apex - doing that now.
UPDATE:
Nope. clear, uninstall, reboot, reinstall, reboot... and still getting the same results. Bah.

Does Solid Explorer also fail to be able to delete?
https://play.google.com/store/apps/details?id=pl.solidexplorer

Thanks Apex. Solid Explorer worked. Thank you for not giving up on the ideas.
While I am glad I found a solution to deleting the files, I remain a bit concerned about the ES File Explorer problem. It make me think other problems exist that I just haven't hit yet.
Case closed!

Great, glad that worked out for you.