Ok.... I have googled them all and done a search on this website and have found nothing that is similar to my situation. I hate when people ask questions that are found in other forums and would not want to do the same... but I don't feel my situation is in the realm of that.
I followed all the basic ways of rooting and none worked for me. I did the Visionary (ver 14) root and root.zip (/root to sdcard), etc.... didn't work.
Finally Id/l Visionary for temp root.... and I followed http://forum.xda-developers.com/showthread.php?t=858996.
I got S=OFF, but had to 'sync' in terminal 5 or 6 times to be able to get su to work.
I finally get su to work (# instead of $ in terminal) and all the programs that require root to work do as they are supposed to. The main issue I have, is that without running visionary (with R/W access), I cannot delete files without it warning that I have read only access.
I thought if I had root access, I wouldn't need to set up Write access.
Once I run visionary, and delete *.apk files that came with my phone, they do stay away perm.
I just want to know if there is a way to keep the R/W access without visionary since I know I am in root.....
Root access is a separate entity from S-off, and that a separate entity from /system partition read/write mounting. That partition is read/only at boot. You can make it writable with adb, with Root Explorer, or with a linux mount command.
HTC Glacier running CM7 #33
root explorer has a button to push to mount r/w, or if you have adb setup you can plug in your phohne and type
adb remount
and you'll be r/w
or you can use terminal emulator and type
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
option94 said:
...
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
Click to expand...
Click to collapse
I see two typos in the command. There should be a space between mount and -o, and no comma between the -o and remount. Thus:
Code:
# mount -o remount -rw /dev/block/mmcblk0p25 /system
Of course, "adb remount" from a nearby PC is so much easier.
Thanks. I just woke up when i started typing that.
and the , will work with no space. Both methods are fine.
Thanks guys!
On another note, do either one of you know if you can mount the phones system folder as a drive on Vista like you would be able to do with the SD Card?
Im not talking with adb shell... More like using Windows Explorer
Nope. Only the "external" SD card can be mounted via USB, sorry.
This might be what your looking for.
adb commander
option94 said:
This might be what your looking for.
adb commander
Click to expand...
Click to collapse
That is close enough. Thanks option!
Related
I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?
Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?
If anyone else runs into this problem, this solution worked for me:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.
you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.
I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...
So i rooted my vibrant with the hopes of removing some of the bloatware. i rooted with the one click root method, loaded clockwork recovery, i know i am rooted but every time i try adb remount i get remount failed: no such file or directory.
so i tried going into clockwork recovery in the partition menu and mounting system there and trying adb remount and got remount failed: operation not permited. i ran adb root and got root can not run on factory builds (or something close to that)
in adb shell ive tried mounting every which way i can think of and nothing works.
ive searched all over and havent been able to find a fix, please help
root explorer didnt work either
also i tried deleting the system apps with root explorer and it would mount either
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
cojonesx said:
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
Click to expand...
Click to collapse
like i said in my post, i tried shell and couldnt get it to mount. maybe i did it wrong
I just used a guide to root my MT4G with adb and gfree_4 and it worked perfect. loaded up hboot s = off and all, however when I tried the genius button remap guide I couldn't change the system r/w assess using root explorer. what gives?
What happens if you do
adb shell
su
or you can try
adb remount
known issue there is fix, I just downloaded an app "mount /system rw" that works perfectly fine for me
So is the fix just to use mount /system app or is there a perm fix? I can't get metamorph to istall because of this issue. Mine seems to come and go, sometimes Root Explorer can mount r/w in system and sometimes it can't.
I used it as a permanent fix
adb pull /default.prop
open in text editor and make sure that ro.secure=0
then adb push back to /
should allow you RW
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
jdkoren said:
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
Click to expand...
Click to collapse
To be sure you could download a root explorer and see if you can mount R/W
Sent from my HTC Glacier using XDA Premium App
Is there a free application that does this?
Unfortunately, I won't have access to it for the next few days (someone else's phone, and he's going out of town).
the stock rom doesn't except the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
option94 said:
the stock rom doesn't accept the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
Click to expand...
Click to collapse
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
jdkoren said:
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
Click to expand...
Click to collapse
That's correct... I think. all I know is that the stock Rom doesn't usually play well with root lol so yes flash a custom rom
Sent from my HTC Glacier using XDA Premium App
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may br right, but if not it wont do any damage. just give you a syntax error.
option94 said:
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may b right, but if not it wont do any damage. just give you a syntax error.
Click to expand...
Click to collapse
Ah yes, I remember using that once before. I've since forgotten it since I never use it with my own phone. Alrighty, I'll mark this as answered.
I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?
AVanover5 said:
I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?
Click to expand...
Click to collapse
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.
ace7196 said:
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.
Click to expand...
Click to collapse
I realize that. Autonooter does, in fact, root the device. It's my friends.
SOLVED
The NookColor has been sleeping for a while (because I ate dinner) and Ubuntu now works >.< I'm not sure what's up with the apps, but maybe they'll install and launch now. I'll try clearing their caches and what not as well. If anyone has suggestions, feel free to post them.
AVanover5 said:
I realize that. Autonooter does, in fact, root the device. It's my friends.
Click to expand...
Click to collapse
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
No, Ubuntu runs off of the SD through VNC. It's not a ROM. I've fixed it already anyways...
ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
I'm having similar problems with my HTC first But I'm not good w/ coding, so it's a user defect. I can't chmod and so I can't get the device to stay rooted. Some apps can get su and many cannot. Superuser also cannot get su. ??? Any advice?