• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

mounting /system rw problems

B

bamaduc

Member
Hello everyone here's the story. I have a rooted Transform Ultra, running a Rom by interdpth(Star-ScRom), cwm installed. Ok when interdpth released star-scrom I was never able to flash it by using the batch file. I had to manually push the rom via adb every time(different versions). After toying around with it I found out the batch I found out it was getting hung up on mounting the system with rw permissions. If I'm in adb and I _adb remount_ I get operation failed. If I _adb shell_ _su_ _remount. Rw /system_ it tells me it enables r/w but then I get pe:rmission denied when I try to push/pull from the system. _ adb shell -o remount,rw -t ext4 /path here /system_(can't remember that command off the top of my head, but whenever I enter that code correctly) I get permission denied. I have been pouring over forums for weeks but cannot figure this out. Anyone that can help me out with this would be greatly appreciated. Thanks for reading and apologies it is so long.

Mods, I realize this will probably get moved the the transform ultra-all things root forum, but I did ask around a bit with no luck. If it does get moved its no biggie, just feel this is more of a general android/adb question/problem.
 
Greetings bamaduc,

Not familiar with your device, but I wonder, did you check to see that S.U.(Super User) got installed.
 
I'm no coding wizard, but I didn't think Linux liked back slashes ( \ ). Is that maybe your problem? Have you tried those commands using forward slashes ( / )?
 
Thank you both for the quick replies. Yes su is installed, and you are correct jerofld, linux does use foward slashes I'm just a dumb@ss and typed them wrong in the post, ill correct them now, thanks for the catch.
 
I have seen and helped fix this problem twice before, on other phones.

For reasons never discovered, the remount fails just as you describe and the explicit mount needs the low level path, not the logical one.

I recall the fix, finding the low level path, was protracted. I will have to look it up in my post history. (Not going to be quick with my volume, sorry.)

Meanwhile, please try this work around - install EStrongs File Explorer, menu, settings on that, enable root explorer and /system read/write. EStrongs always amazes me at things it can get by.

If that works, consider Fix Permissions, free in the Market.
 
EarlyMon said:
I have seen and helped fix this problem twice before, on other phones.

For reasons never discovered, the remount fails just as you describe and the explicit mount needs the low level path, not the logical one.

I recall the fix, finding the low level path, was protracted. I will have to look it up in my post history. (Not going to be quick with my volume, sorry.)

Meanwhile, please try this work around - install EStrongs File Explorer, menu, settings on that, enable root explorer and /system read/write. EStrongs always amazes me at things it can get by.

If that works, consider Fix Permissions, free in the Market.
Click to expand...
EarlyMon, thanks for reply. apologize its taken so long to get back(family bull, had to go outta town) i tried EStrongs File Explorer and continued digging but unforunately the problem is still here. i have started looking through ur posts to try and find how this was fixed, but i think it will take me roughly a year due to your almost 16,000 posts. :) anyway i appreciate your input and hope you had a good Christmas/New Years.
 
ok thanks a million. i did finda thread about ro.secure=0 causing a similar problem. so i went into
Code: 
adb shell
getprop ro.secure
0
I checked the build.prop file from Interdpths Star-Scrom and ro.secure value was 1. this is weird because that was the same build.prop file that i pushed when i installed star-scrom. so i pushed the build.prop file again and now ro.secures values stays 1. although still having my mounting issue.
Code: 
adb remount
remount failed: operation not permitted
 
adb.exe shell mount -o remount,rw -t ext4 /dev/block/mmcblk0p15 /system
mount: operation not permitted
 
Please do an adb shell to get into the phone.

If presented with a user prompt ($) please enter su to be root.

Then please just issue the command, mount, and post back the line for /system - thanks! :)

Point is to verify your fs type and any other mount options set by default.

PS - if you weren't root by default going in, ok to retry your mount after you are.
 
OK. So your option clause needs to look like this:

-o rw,relatime,remount

I think you can skip the other two clauses but if it fails, go ahead and include them. (barrier=1,data=ordered)

By the way - you're saying that you are already read-write on /system - maybe there is another problem??

And to make read-only when done, substitute ro for rw.

BTW - is BusyBox up to date?
 
I actually just updated busybox yesterday. And how should I input the option clause?
Mount -o rw,relatime, remount?
 
Yes, without the space on remount, of course, and adding the other two parameters as suggested if that fails.

Hope we get you out of these woods soon, I know you feel the same!
 
Mounting with mount :

Code: 
# mount -o rw,remount /system                                    
mount: Permission denied
After installing Busybox
Code: 
# busybox  mount -o rw,remount /system
# # No error
Edit: It donsn't work anymore, I don't know what I did to make it work in the first place ((
 
I am facing same issue on Android 7.0, any help would be appreciated. I am trying to remount system partition on USER build binaries, below are the commands i have tried already

C:\Users\kushal>adb shell
xxx:/ $ su
xxx:/ # toybox mount -o rw,remount /system
mount: '/dev/block/dm-0'->'/system': Operation not permitted
xxx:/ # mount -o rw,remount /system
mount: '/dev/block/dm-0'->'/system': Operation not permitted
 

Attachments

  • Capture23.PNG
    Capture23.PNG
    10.7 KB · Views: 313
You must log in or register to reply here.
Back
Top Bottom