Ok so the Rezound has the bootloader unlocked and rooted with 1click method.
Root Explorer, and Root Checker verify.
Going into adb I am trying to adb rm /system/app/".apk"
It doesnt work.
I tried adb remount and it is not letting me and says operation not permitted.
If I type in adb shell I get the $, then type in su and get #
Titanium Backup. More than worth the money. You can freeze, remove, and backup anything/everything.
Sent from my ADR6425LVW using xda premium
Code:
adb shell
su
busybox mount -o rw,remount -t / rootfs
rm /system/app/NameOfApp.apk
busybox mount -o ro,remount -t / rootfs
adb shell
$ su
su
# busybox mount -o rw,remount -t yaffs2 /rootfs
busybox mount -o rw,remount -t yaffs2 /rootfs
mount: can't find /rootfs in /proc/mounts
# rm /system/app/com.mobitv.client.nfl2010.apk
rm /system/app/com.mobitv.client.nfl2010.apk
rm failed for /system/app/com.mobitv.client.nfl2010.apk, Read-only file system
Try ROM Toolbox. You can find it free in Market.
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Xtreme Outcast said:
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Click to expand...
Click to collapse
I would suggest to drop the extra bits that someone could mis-type and shorten this to
"busybox mount -o remount,rw /system"
It's worked for me and takes a little chance out of the equation. Just my opinion take it for what it's worth.
I Was In A Rush Yesterday That I Typed In The Wrong Code And Just Realized It Now When He Said It Didn't Work. It's All Fixed Thanks For The Suggestions Always Appreciated On My Posts Or Threads.
Related
Trying to push files from adb to my phone but it wont let me because its a read only system.
I've done adb shell mount -o rw,remount /dev/block/mtdblock3 /system but it does not work, I'm running windows 7 could this be a problem?
Make sure that USB Debugging is enabled on the phone.
Settings...Applications...Development
C:\Users\Jake\Desktop\android-sdk-windows\tools>adb shell mount -o rw,remount /d
ev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
C:\Users\Jake\Desktop\android-sdk-windows\tools>
It is enabled.
Are you in recovery mode when you're trying this? Or booted regularly?
If you're in recovery mode you'd mount it like this:
mount -o rw /dev/block/mtdblock3 /system
Jboxen said:
C:\Users\Jake\Desktop\android-sdk-windows\tools>adb shell mount -o rw,remount /d
ev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
C:\Users\Jake\Desktop\android-sdk-windows\tools>
Click to expand...
Click to collapse
follow my tutorial for ADB set-up. http://forum.xda-developers.com/showthread.php?p=6054534#post6054534
I noticed you dont have SDK in C:/ root....
or a simple command like this should mount it as read/write:
adb remount
its what i have been doing and seems to do the same thing with less commands, unless someone can point out the difference for me.
Otherwise, try
mount -o rw,remount /dev/block/mtd3 /system
That should do it. The /dev/block/mtdblock3 is only required in recovery.
ECLIPS3 said:
or a simple command like this should mount it as read/write:
adb remount
its what i have been doing and seems to do the same thing with less commands, unless someone can point out the difference for me.
Click to expand...
Click to collapse
I would also like to know the difference between the two commands:
adb remount
and
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
DeezNotes said:
I would also like to know the difference between the two commands:
adb remount
and
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i believe they both do the same thing. just one uses the same characters
Android22 said:
follow my tutorial for ADB set-up. http://forum.xda-developers.com/showthread.php?p=6054534#post6054534
I noticed you dont have SDK in C:/ root....
Click to expand...
Click to collapse
having the SDK in C:\ root is not a necessity. People do it because it is easy to do it that way.
Hello all,
I am trying to push a file to my system, however I do not seem to be able to mount my system partition.
When I try to execute the following command, I always get the error "Operation not permitted" :
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
My phone is rooted and my USB debugging is on !!
Anyone no what could cause this. It has always worked when I was still on 1.6 (rooted) and now it doesn't allow me access.
When I use Rootexplorer, I have R/W access, so root works.
Anyone has any tips or advise ?
Try...
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Tried that, and get permission denied
Should have added, make sure your screens on on the phone and allow SuperUser access when you type su.
never mind, one sec
OBJECTIVE - Install CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=946354
Obstacle - Failed at INSTALLING A CUSTOM RECOVERY
http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
1. I have successfully root by following this guide
http://forum.xda-developers.com/showthread.php?t=1001713
2. I have placed both flash_image and recovery-RA-GNM-thunderg-1.1.0at the root of sd card
http://forum.xda-developers.com/showthread.php?t=1007244
3. I am stucked at "INSTALLING A CUSTOM RECOVERY" and need help (I am getting error messages of file not found. Pictures attached)
Picture 1:
http://www.flickr.com/photos/[email protected]/5562426547/
Picture 2:
http://www.flickr.com/photos/[email protected]/5563002890/
Picture 3:
http://www.flickr.com/photos/[email protected]/5563002928/
PS: My phone is still locked to Koodo, does it matter I leave it locked ?
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
sondw said:
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
Click to expand...
Click to collapse
Thanks and it works.
I'm stuck in Recovery and trying to push a file to /system to try to fix things, however I'm not able to mount it as read/write using adb
$ mount -o remount,rw /dev/stl12 /system
mount -o remount,rw /dev/stl12 /system
mount: Operation not permitted
su
Permission denied
Any solution?
- Root devices
Code:
adb shell
su
mount -o remount,rw /system
rm /system/csc/language.xml
reboot
Or
Code:
adb shell
su
mount -o remount,rw /system
mv /system/csc/language.xml /system/csc/language.xml.bak
reboot
Done