I was trying to uninstall some carrier apps through ADB on Windows, via CMD. I wasnt unable to do so, and investigating about my problem, I found that I can uninstall through Titanium Backup . Now I dont have anymore the vodafone apps and trial games that came with my Samsung Galaxy I5510!.
But for what I am writing this, is that for unknown reasons to my, when trying to uninstall through ADB, I always have the problem of READ ONLY FILE SYSTEM. I tried to remount through this command:
mount -o rw,remount /dev/block/stl9 /system
that I found here: http://forum.xda-developers.com/showthread.php?t=872128 , at the ADB Workshop, at deleting files.
this command:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
# chmod 777 /system
from here: http://www.pocketmagic.net/?p=757
I was forgetting other thing, the first time I used ADB was guiding myself with this guide: http://www.thedroiddemos.com/2010/0...how-to-remove-carrier-bloatware-from-android/
Maybe in the future I need to use ADB again, so thats why I am writing this, even though my problem with the carrier apps is solved.
And I have the stock Android 2.2 Froyo rooted with SuperOne Click.
And (again), I dont know where to place this post, my smartphone doesnt have a subforum, and I also ask for the admins to add the subsection
Thanks in advance!
Well, this is interesting, 26 views, and noone answered.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
No one answered because your post is not written very clear and slightly confusing.
To make your /system writeable execute this command as superuser:
mount -o rw,remount /system /system
Click to expand...
Click to collapse
try root explorer it gives r/w and r/o permissions !
I already figured it out how to remove those annoying apps. I used Titanium Backup, I didnt knew it had the ability to remove system apps
Related
Hello, all!
I'm trying edit a file in /etc/ and adb says 'Failed to copy: Read-only filesystem'
Now, is this actually true? Or is this simply a permissions issue? I'm doing this on a non-rooted phone, so I can't 'touch' anything without permission errors, but is it a futile task if the filesystem is read only anyway?
I'm trying to do this from a non-rooted environment as I had intended on making this into an application, but I imagine that if I can't touch or push these files from an adb shell then I won't be able to from the application space either.
It's frustrating not to be able to edit the filesystem of my own phone, I'll be rooting if this is just a permissions problem and not an issue of a non-writable filesystem. Perhaps I could still make an application for rooted-only phones.. hrm..
Any thoughts on this?
/etc is an alias for /system/etc, and /system is a partition mounted as ro (you can confirm this yourself by running mount)
Ah, bugger. So this is hopeless (without modifying and then reflashing)?
Thanks very much.
you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write
try adb remount. if it failes you need root sorry.
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
Click to expand...
Click to collapse
what is the error message? saying it dont work doesnt provide enough info for us to help....
it says sh: cant open aw.sh
so i still have to put the path or cd to where the file is. Is there a way to make /system my home?
no you cant make system your home, system is system, home is home. you can make a symlink if you are familiar with linux - might want to read up about shell commands
korndub said:
you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write
Click to expand...
Click to collapse
Thanks it really worked!! for me i had the same problem as the other guy.
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
Maybe you're typing it in too literally. It should actually read like this:
mount -o remount,rw /dev/block/mtdblock3 /system
There was a typo with -oremount, there should be a space after -o.
Hope that helps.
PS. That command worked for me on a device where everything else failed.
dhkr123 said:
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.
Click to expand...
Click to collapse
actually, / can be mounted rw, but changes are lost on reboot
new user
Firerat said:
actually, / can be mounted rw, but changes are lost on reboot
Click to expand...
Click to collapse
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
I would recommended not posting in the g1 section. The Asus forums would be a lot more helpful.
egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
Download EStrong File Manager and within the settings of it, enable mounting of the system as read/write.
Or, download Terminal Emulator and type this in:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
Or, try typing this in terminal/cmd:
Code:
adb remount
Or, if you plan on doing it all from recovery you could do:
Code:
adb shell "mount system"
and then you could do it all from there.
Next time, please post in the proper forum.
Read-Only /system... i just deleted the file, tich push should update/replace and then it worked... only had this bug when i was trying to modify Trebuchet.apk (homescreen)
Hi guys
Not being a linux expert, i'm stuck with the following problem..
i'm using a program who uses low level adb commands to write on the phone extSdCard...
problem: this extSdcard is seen as a readonly filesystem.
What has to be done to make this FS RW instaed of RO ?
This does not happen under windows where I can write to the extSd without problems
thks in advance for the tip
I have made some modifications and moved this information to my wiki. It is easier to edit, and the good thing is other users can edit it on a wiki unlike here in a forum post. Please check it out at Droidwiki.com
while flashing busybox, i got error, "no signature" can i just put it in the auto signer?
great info
stogchris81 said:
while flashing busybox, i got error, "no signature" can i just put it in the auto signer?
Click to expand...
Click to collapse
I am sorry, but it is people like you who make others not want to help and get rude about stuff. I did NOT ONCE say to flash busybox. If you would read instead of typing, you might see that.
wow. sorry i pissed you off so bad. i miss understood this...
First you need to format your card (No I will not tell you how to do that part) and make sure that the fat partition is FIRST******.
Second, download busybox.zip, unzip the zip file, and place the busybox file in your /sdcard.
Third, flash the rom (dont ask which or how, if you are here, you should know this stuff by now)
Fourth, run "adb remount" (on your desktop), then "adb shell" and then the following commands (to setup busybox): step three says flash the rom right after step 2 says place busybox on sd card. there is no other mention of a rom in your tut so i took that to mean that busybox was a rom. also..."If this does not work, try to give some info as to why, and if I find an error I will update it." this is what you ask people to do and this is what i did.
now, can i ask you a question about a problem i ran into after reading your updated instructions?
nm. i got it. i just needed to unplug the usb, then replug it in without mounting to windows in phone. thank you for the updated tut. i hope we can move on knowing it was a misunderstanding.
good job on this.
:]]
Good instructions.
Alternatively:
Open up the terminal emulator and type:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# dd if=/sdcard/busybox of=/system/xbin/busybox
# chmod 4755 /system/xbin/busybox
stogchris81 said:
now, can i ask you a question about a problem i ran into after reading your updated instructions?
nm. i got it. i just needed to unplug the usb, then replug it in without mounting to windows in phone. thank you for the updated tut. i hope we can move on knowing it was a misunderstanding.
Click to expand...
Click to collapse
Sure, ask your problem instead of wasting a post spot by asking to ask. You guys do not understand but there are 1900 posts in the other thread because a) ppl dont read and ask stupid questions and b) those stupid questions make it to long for others to read, so they dont read and ask stupid questions. Catch22.
Very well done sir, thank you for this
does it matter what type of partion we create? it says like NTFS, FAT32, FAT16
your sdcard should already be formatted to fat32. 2nd partition needs to be ext2.
?????????
sorry for this question please dont yell...
On my CMD I got this error......
C:\Users\Jesus>cd desktop
C:\Users\Jesus\Desktop>cd sdk
C:\Users\Jesus\Desktop\sdk>cd tools
C:\Users\Jesus\Desktop\sdk\tools>adb remount
remount succeeded
C:\Users\Jesus\Desktop\sdk\tools>adb shell
# dd if=/sdcard/busybox of=/system/xbin/busybox
dd if=/sdcard/busybox of=/system/xbin/busybox
/sdcard/busybox: cannot open for read: No such file or directory
can someone please help me without any yelling
Thank You Haykuro & Darkrift
jgu71424 said:
sorry for this question please dont yell...
On my CMD I got this error......
Click to expand...
Click to collapse
You're running 4.9 aren't you.
TheDudeOfLife said:
You're running 4.9 aren't you.
Click to expand...
Click to collapse
no 4.5
what should i do?
is this the same thing....
Good instructions.
Alternatively:
Open up the terminal emulator and type:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# dd if=/sdcard/busybox of=/system/xbin/busybox
# chmod 4755 /system/xbin/busybox
OH
Oh i see why TheDudeOfLife asked me that question about 4.9, its because i ask about the end call thing.
No I got 4.5 it is much more stable...
Still need help though
Thanks
jgu71424 said:
no 4.5
what should i do?
is this the same thing....
Good instructions.
Alternatively:
Open up the terminal emulator and type:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# dd if=/sdcard/busybox of=/system/xbin/busybox
# chmod 4755 /system/xbin/busybox
Click to expand...
Click to collapse
Did you copy the busybox (unzipped) to the sdcard first?
TheDudeOfLife said:
Did you copy the busybox (unzipped) to the sdcard first?
Click to expand...
Click to collapse
yup followed the instructions i just cant get pass that error.
I am running Vista business 32-bit
jgu71424 said:
C:\Users\Jesus\Desktop\sdk\tools>adb shell
# dd if=/sdcard/busybox of=/system/xbin/busybox
dd if=/sdcard/busybox of=/system/xbin/busybox
/sdcard/busybox: cannot open for read: No such file or directory
can someone please help me without any yelling
Thank You Haykuro & Darkrift
Click to expand...
Click to collapse
You need to disconnect your phone from computer.
excellent. worked without an issue.
thanks man!
Im a seasoned flasher. When I originally flashed my G2x I read the entire wiki for CM on my device (http://wiki.cyanogenmod.com/wiki/LG_G2x:_Full_Update_Guide).
Anymore when I see people asking for howtos and guides to flashing their phone, members often reply a short set of steps...more or less
Flash CWM
Backup stock image
Download ROM
Boot into CMW recovery
Wipe
Flash zip
When I did it, i was using ADB to manually push downloaded files (su, psneuter, busybox) and set permissions as instructed by the wiki
Code:
adb push busybox /data/local/
adb push psneuter /data/local/
adb push su /data/local/
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/psneuter
adb shell
/data/local/psneuter
adb shell
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
exit
adb push Superuser.apk /system/app/Superuser.apk
Etc etc...and quite a bit more.
Have i missed something?
Has the flashing process evolved to the point were these steps are no longer needed?
If so, why is the wiki not updated?
More importantly, if not, why are the steps as outlined on the wiki not being included as direction, or more simply, why is not the wiki referenced when people ask for directions?
Any benefit or drawbacks to one method over the other?
Im just asking out of curiosity. Thanks in advance.
I haven't a clue as to why the wiki even has those directions cause if you, say have a bad download, flash a rom get into a boot loop you will need then go back and flash CWM through NVflash as there will be no way to access recovery except through adb probably... So just ignore the wiki page, like I said I wonder why they have it like it that, maybe I'm not seeing something but that way just seems pointless and too much work lol...
Yeah... just read the sticky guide on these forums.
Looks like the steps you have are for rooting your device. The beauty of this device is that it ships with an unlocked bootloader and doesn't need to be rooted in order to flash a custom recovery image and start flashing ROMs. The only way I would think the long method should be used is if you really needed root before flashing new ROMs, such as to backup your apps from your stock ROM with Titanium Backup or a similar situation. But, in terms of just getting to the point of flashing ROMs, there is no reason to root this device.
As well, when I got mine the wiki said to flash CWM via ROM Manager, which is not the way to do it.
you are leaving /system as read write. Should return it to read.
mount -o remount,r -t ext3 /dev/block/mmcblk0p25 /system
Can it be done?
I tried de Superoneclick method and it did not worked.
But also i tried with another program "unclockroot 2.3.1" ad the thing is that after i run it and before i reboot phone i have shell root "#" but nothing of superuser or SU on the phone.
Could it be possible, after i have "#" to change R/W previligies on system folder and install superuser.apk and SU through adb commands?
which ones are the adb commands to perform?
And can anyone send superuser.apk and the proper su to install?
Many thx for all the help.
D_Saint
The method to root Desire S without unlocking bootloader is described at least in 5 places, in General and Development forums, and involves downgrading the firmware. Please read.
did not find any that suites my needs.
And believe me i searched, i have been reading about this in the past 2 weeks....
Can you please send me the links?
I found these commands:
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
Are they correct?
Thx again.
what we are saying is that for now u cant root d latest hboot 2.0.0.xx u have to downgrade 1st or use d XClip hardware to permanently unlock n root ur desire s
cheers
No, the commands are incorrect, because the root you're seeing is only temporary, and the thing that protects /system from being written to is not just R/O mount. There is a HW protection that needs to be unlocked to be able to write to /system, otherwise everything you do will be gone after rebooting. I said - please read, and I meant it. If you want pointers - google "how S-OFF was achieved on G2" and then read.
Index of everything in Development:
http://forum.xda-developers.com/showthread.php?t=1443636
Look for "downgrade HBOOT without using HTCDev unlock". There are 3 guides there.
Hi, this is a blatant crosspost from the android stackexchange site, questions/24081... I posted it there and figured I wouldn't get much help, so I thought I'd try here. Let me know if this is OT or in the wrong place or whatever.
I want to remount a read-only partition in read-write mode, but I want it to be writable for all users.
So far I've got this:
Code:
mount -o bind /someplace /someplace_else
mount -o remount rw /someplace_else
The first command creates a new mount point from a directory. The second one remounts the new mount point as rewritable. This all works.
Problem is, the new mount point has uid=1000,fmask=0222,dmask=0222, so the non-root user still can't write anything, and root can't give it permission.
How do I change the fmask and uid when remounting, or is there something else I can do to make the mount writable for the normal user?
Also, note that the command that worked for me is this:
Code:
mount -o remount rw /someplace_else
...with no comma between "remount" and "rw," as I've seen in almost everything my searches turned up. Does anyone know anything about this discrepancy in syntax?
I'm doing most of this in a terminal emulator on the phone, and in SL4A.