I just unlocked and rooted my nexus s. Now im trying to stop the phone from reinstalling the custom recovery image and all im getting is problems.
I put in the command
mount-o rw,remount/dev/block/mtdblock3 /system
And every single time i get
mount-o : permission denied
Anyone have any ideas? im worried about rebooting my phone now cause i don't want to go through the whole process again. After reading around on XDA it doesn't seem like you are required to do this. Does anyone know if it will reinstall the custom recovery image if i don't do this step? I have searched everywhere to figure out the problem. But stilll im coming up with nothing. I have found people with other devices that have this problem. But nothing about fixing it.
If anyone has any ideas i really need help ASAP
try and grant yourself superuser & then try.
"su"
"mount -o rw,remount /dev/block/mtdblock3 /system"
You need a space after mount. -o specifies the mount options. The command is mount
Sent from my Nexus S using XDA App
aye, didn't notice that, couple of needed spaces. I've modified my original post.
Thanks i tried it but now it says mount-o not found.
Sent from my Nexus S using XDA App
If it says mount-o not found there's not a space between mount and -o.
mount -o remount,rw .........
Sent from my Nexus S using XDA App
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
No Android expert but I have experience with the CL. Pretty sure you're going to need to cd into the dir or write the full path to the file.
BTW what are the cool kids using for command line these days? Any of them have tab type features? ex: cd /syst<TAB>/me<TAB> for cd /system/media/
B2L said:
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just used root explorer to rename the install-recovery.sh to install-recovery-no.sh. It disabled it from flashing over the clockwork mod recovery on reboot. After disabling it I flashed clockwork recovery again permanently.
Edit: The file is in the etc folder.
Sent from my Nexus S using XDA App
sarge363 said:
I just used root explorer to rename the install-recovery.sh to install-recovery-no.sh. It disabled it from flashing over the clockwork mod recovery on reboot. After disabling it I flashed clockwork recovery again permanently.
Edit: The file is in the etc folder.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks i tried to just rename it with Root Explorer but it says it's a read only file. I can't figure out how to change it so it's not read only.
B2L said:
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
B2L said:
Thanks i tried to just rename it with Root Explorer but it says it's a read only file. I can't figure out how to change it so it's not read only.
Click to expand...
Click to collapse
you have to include the path
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
mv /etc/install-recovery.sh /etc/install-recovery.sh.bak
or
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
cd /etc
mv install-recovery.sh install-recovery.sh.bak
It's really just a lot easier with Root Explorer. If you use root explorer app, you have to push the little button at the top that says "mount r/w" or something like that. I usually do that rather than run the mount command, because I always forget the syntax for that one.
Yeah just hit the "mount R/W" button on top when u open Root Explorer. It changes to "Mount R/O" and u can rename it after that.
Sent from my Nexus S using XDA App
Related
Hi...does any one knows how to make touchwiz music player on rooted x10
Sent from my X10i using XDA App
I have the apk but it doesn't work...
Sent from my X10i using XDA App
maybe it needs so kind of lib files
So this is dead? Can i have the apk or something?
Sent from my X10i using XDA App
Here is from the leaked Vibrants 2.2 build never tested it.
Edit:
Doesn't work at least not on my end most likely needs a lot of modding to get it working.
urs74 said:
Here is from the leaked Vibrants 2.2 build never tested it.
Edit:
Doesn't work at least not on my end most likely needs a lot of modding to get it working.
Click to expand...
Click to collapse
Awwww...
When u tried it, u pushed with adb? Or copy paste with root explorer?
Sent from my X10i using XDA App
dk2000zx said:
Awwww...
When u tried it, u pushed with adb? Or copy paste with root explorer?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Copy and paste I'll try pushing it.
Edit:
came up failed install for me used these commands not sure if I did them right though.
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push MusicPlayer.apk /system/app
urs74 said:
Copy and paste I'll try pushing it.
Edit:
came up failed install for me used these commands not sure if I did them right though.
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push MusicPlayer.apk /system/app
Click to expand...
Click to collapse
LOL i know nothing about adb so cant help ya, all i do is copy paste then change permission,then reboot
Sent from my X10i using XDA App
dk2000zx said:
LOL i know nothing about adb so cant help ya, all i do is copy paste then change permission,then reboot
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Doesn't look promising since searching on the forums here comes up empty handed on any other phones getting a port of it. Closest music player I've found to it is power amp.
This is not my doing or work, I just found it and am sharing it so please don't blame me for stealing or using anyone elses work
This is the script I found in squidlys rom and it is saved in system/xbin, if I can figure out how to post a file on here through the xda app on my phone I can give you guys the files used to run the fix. You can run the command in terminal emulator but im guessing first you may want to create a folder on the sd card named stock and then move the file battery manager to it and then run the script and restart the phone, that's what I did and it worked.
#!/system/bin/sh
if busybox [ -e /sdcard/stock/BatteryReport.apk ];
then
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
busybox cp /sdcard/stock/BatteryReport.apk /system/app
sync
mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
echo 'battery manager fix'
else
echo 'battery manager not fixed'
echo '1) Place battery report App On The SDCard'
echo '2) Turn Off USB Storage'
echo '3) Rerun Script To Try Again'
fi
Sent from my DROID2 using XDA App
Well I can't figure out how to attach a file through the xda app on my phone and I loaded the actual page on my phone and it wont pull up my phones sd card directory so if you want the file I can post them when I get off work but the txt that I posted above is the actual file, I opened it within txt editor and copied it so if you can save it as the same kind of file that is in system/xbin (I don't know the extentions or what kind of files they are) then you could probably do it without my help, the original file name is battmanfix. Thanks for reading
hmm, just looking at the script i'd say it shouldn't work
not sure what squidlys changed in his rom (if it is for droid 2) but the default d2 mount point for /system is /dev/block/mmcblk1p21 and also file system is ext3...
did you test it?
Well I already had the folder on my sd card from the squidly rom and pretty much coppied the file to my xbin in the system folder and ran the command through the terminal emulator and it seemd to work afterwards...there were no errors in the terminal or anything and when I typed in battmanfix it responded with the whole name battery manager fix and I checked my battery manager and it worked... that's exactly what it did with squidlys so idk...
Sent from my DROID2 using XDA App
ok... so here's something funny... Looking at the script, basically all this is doing is replacing (and reactivating) the batteryreport.apk. So... me thinks to myself - "self; what happens if I just try to click on the apk as if I was gonna install it?" obviosly it didn't install, but after doing that, my battery stats were back. Something is obviously happening to where the batteryreport.apk stops syncing with the system, and anything that "reactivates" it allows it to display again...
Just my observations, yours may vary
Well like I said at the begining I just thought it was interesting and I figured id share what I found..and I don't know a whole lot about linux and codes and scripts so thanks for the info and also I didn't write it, just found it..
Sent from my DROID2 using XDA App
hey guys!
i didn't know where to post this, mods please move it to the appropriate forum.
NOW FOR THE GOOD PART,
GUIDE: HOW TO SET /SYSTEM TO RW
this question has been asked a lot, and i felt a need to post a guide: the easiest method is to use root explorer and on the top right corner is a button saying either ro, or rw. ro means read-only, and rw means read-write.
now some of you may be asking: so what's the point of this thread? i can already set /system to rw in root explorer. and yes, that is true (and much easier than this way), but what if for some reason root explorer refuses to set the /system to rw when you really need to edit that one file? or what if you're in adb, and can't access root explorer? that has happened to me before, and maybe some of you. so instead of panicking and freaking out, try this method:
1) download terminal emulator from market (anyone will work)
2) open and type "su" (NO QUOTES) to make sure you have root access. (if you don't know what root is, then don't read this, it's a waste of time)
3) to remount /system to rw, type EXACTLY: mount -o remount rw /system (enter)
so it should look like this:
Code:
su
mount -o remount rw /system
this method does work on every android phone, and works in terminal emulator as well as in adb
in adb just do:
Code:
adb shell
su
mount -o remount rw /system
as always, i am not responsible for anything that happens to your phone.
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
h22aboi said:
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
There are a few ways to do this. I personally encourage people to learn the ADB end of things. Sometime a nice pretty GUI will not get you out of a pickle.
h22aboi said:
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Good for you. I have confronted this problem before, and just wanted to share my findings. This could be useful in the future.
Sent from my HTC Glacier using xda premium
It's always good to know another way to do things, but I also have never had a problem with ES File Explorer.
Alright I want to move my location spoofer app to /system/app so I can watch my hometown team on MLB.tv. This worked fine on my LG Nitro running CM10, but when I tried on my stock infinity (rooted, not updated), it won't let me. It just says "paste failed" when I try to move it. Anyone have any advice as to how to fix this?
Have y o u tried mounting the directory as rw so you can paste in there?
Sent from my ASUS Transformer Pad TF700T using xda premium
Sinker1345 said:
Have y o u tried mounting the directory as rw so you can paste in there?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
No I haven't, but just to clarify the app is currently installed on the internal memory, not sd card. I am just trying to move it from one folder to a different folder. Is this still necessary?
It may be, if the directory is mounted as read only you won't be able to copy into it
Sent from my SCH-I535 using xda premium
mgoblueno1 said:
No I haven't, but just to clarify the app is currently installed on the internal memory, not sd card. I am just trying to move it from one folder to a different folder. Is this still necessary?
Click to expand...
Click to collapse
In normal operation, /system is mounted read-only, so you need to remount it as writable first. Root-enabled file managers usually have an option for that.
Thanks guys, will try this out tonight
Alright I tried editing permissions on the system folder, the app, and the root manager app, but they were already all checked (read, write, execute). I also tried just cut/pasting a picture i took to /system/app and I didn't work either...
EDIT: I just tried the remount app, and rewrote the /system folder as rw and it still didn't work
If anyone else has any suggestions on how to fix this let me know!
mgoblueno1 said:
If anyone else has any suggestions on how to fix this let me know!
Click to expand...
Click to collapse
mgoblueno1 said:
Alright I tried editing permissions on the system folder, the app, and the root manager app, but they were already all checked (read, write, execute). I also tried just cut/pasting a picture i took to /system/app and I didn't work either...
Click to expand...
Click to collapse
That's not how you do it. Those are chmod permissions for files and directories. That controls which user groups have rwx permissions for access; nothing to do with mounts. To allow for rw access to /system you need to either do it from within a root browser (ES file explorer, tools), the remount app, or type this into the terminal:
Code:
su
mount -o remount,rw /system
Copy your file or directory, then remount the system back as ro (so you don't accidentally delete something - that's why its mounted ro by default)
Code:
su
mount -o remount,ro /system
mgoblueno1 said:
EDIT: I just tried the remount app, and rewrote the /system folder as rw and it still didn't work
Click to expand...
Click to collapse
I just tried this and it works fine. After you made your selections for /system and rw, did you click the top "Remount" button and get a small pop-up "Success!..." notification that it completed its operation? I also verified that I could copy a test file into /system/app after toggling these settings. You are doing something wrong. Read this all again.
[Edit] The only reason I can think of that it might be failing is you are really not rooted or have a corrupt root. If all else fails, run the Root Checker app to see if you really have valid root. Open up your su app and see if it prompts you to update its binaries and let it if it does (superSU).
elfaure said:
That's not how you do it. Those are chmod permissions for files and directories. That controls which user groups have rwx permissions for access; nothing to do with mounts. To allow for rw access to /system you need to either do it from within a root browser (ES file explorer, tools), the remount app, or type this into the terminal:
Code:
su
mount -o remount,rw /system
Copy your file or directory, then remount the system back as ro (so you don't accidentally delete something - that's why its mounted ro by default)
Code:
su
mount -o remount,ro /system
I just tried this and it works fine. After you made your selections for /system and rw, did you click the top "Remount" button and get a small pop-up "Success!..." notification that it completed its operation? I also verified that I could copy a test file into /system/app after toggling these settings. You are doing something wrong. Read this all again.
[Edit] The only reason I can think of that it might be failing is you are really not rooted or have a corrupt root. If all else fails, run the Root Checker app to see if you really have valid root. Open up your su app and see if it prompts you to update its binaries and let it if it does (superSU).
Click to expand...
Click to collapse
Thanks this worked!
mgoblueno1 said:
Thanks this worked!
Click to expand...
Click to collapse
Glad you got it worked out. Which way worked for you?
Please read the problem completely before answering and saying something.
I have S3 Feel os ROM in my HTC Pico.
When i tried to copy any files inside /system/ its saying : Permission denied read only file system.
I tried to use chmod 777 to system through terminal emulator its also given same warning.
Then I tried remounting with the command: mount -o rw,remount /system (using terminal emulator) didn't do the trick for me.
Can you guys tell what should i do to get the write permission. (Its actually showing read and write permission when I saw file/folder properties with a file explorer inside the system directory, but actually its not allowing to write).
It should be fine if you try with some file manager that can get root permissions. (my choice is 'es')
But if you are using the new oc kernel, there things might be different.
What is terminal emulator giving you back?
You also can try by flashing superuser, I have not tryed exactly this rom, but there may be something wrong with su
shortyoko said:
It should be fine if you try with some file manager that can get root permissions. (my choice is 'es')
Click to expand...
Click to collapse
Yes I am using ES File explorer only. Still it says, error permission denied to copy a new file/create a new file/overwrite a file.
shortyoko said:
But if you are using the new oc kernel, there things might be different.
Click to expand...
Click to collapse
I have flashed a oc kernal almost a month back. In between I have changed lot of roms and got back to S3 Feel os rom. I think that won't effect now right?
shortyoko said:
What is terminal emulator giving you back?
Click to expand...
Click to collapse
If I give chmod 777 /system, it's giving permission denied (I have granted super user permission to terminal emulator and i am in su mode)
When I tried mount -o rw,remount /system, it didn't output any thing. Then again I tried to copy a file into system dir, still its the same result.
shortyoko said:
You also can try by flashing superuser, I have not tryed exactly this rom, but there may be something wrong with su
Click to expand...
Click to collapse
Its the last choice I have now, will try.
Try changing mounting
smartksr said:
Please read the problem completely before answering and saying something.
I have S3 Feel os ROM in my HTC Pico.
When i tried to copy any files inside /system/ its saying : Permission denied read only file system.
I tried to use chmod 777 to system through terminal emulator its also given same warning.
Then I tried remounting with the command: mount -o rw,remount /system (using terminal emulator) didn't do the trick for me.
Can you guys tell what should i do to get the write permission. (Its actually showing read and write permission when I saw file/folder properties with a file explorer inside the system directory, but actually its not allowing to write).
Click to expand...
Click to collapse
Had same problem with same ROM. So i go to ES then root explorer then mount R/W then change both path and system to RW and restart.. that solved my problem. try it.
shree15 said:
Had same problem with same ROM. So i go to ES then root explorer then mount R/W then change both path and system to RW and restart.. that solved my problem. try it.
Click to expand...
Click to collapse
Thanks bro, it has solved me the problem.