Develop Bugs

Removing Apps - What mode to boot in?

I'm trying to remove some of the stock apps on my Hero, including Rosie (Sense UI) and such. What mode do I boot in before doing this?
I know all of the steps to remove apps using adb (at least I think I do), I'm fully rooted, etc. But I can't seem to get it to work.
This is the command I'm using in adb
Code:
# rm /system/app/something.apk
(replacing something.apk with the actual apk name of course)
When I boot in Recovery, it says "File not found". When I boot in Fastboot, I can't connect to adb it seems. And when I boot into Android, it says "rm failed for something.apk, Read-only file system"
So am I missing a step? What should I be doing differently?

Boot into recovery, then do a "mount -a" to mount the filesystems.

marinierb said:
Boot into recovery, then do a "mount -a" to mount the filesystems.
Click to expand...
Click to collapse
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb

in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk

garok89 said:
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
Click to expand...
Click to collapse
That doesn't seem to work for me. This is what it outputs:
Code:
remount failed: Operation not permitted

If you can't remount it doesn't sound like you've rooted.

callummr said:
If you can't remount it doesn't sound like you've rooted.
Click to expand...
Click to collapse
I've performed other operations that would normally require it, so I should be rooted.
Is there a way I can confirm if it's properly rooted or not?

shell prompt:
$ .. no root
# .. root
..try typing "su" once in the shell (abd shell or adb-windows.exe shell) and see what it brings up

~David said:
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
Click to expand...
Click to collapse
typing only "mount" just list the mounted partitions, it will not mount anything. if your partition is ext4 you need to downgrade it to ext2 or ext3 or set the testflag, see "if you're having issues with ext4" in the first post of the recovery image thread.

Make sure you have run a Nandroid backup first so that if you accidentally remove something important.
Boot into normal mode. (full GUI)
Then:
Code:
C:\ADB MOUNT
C:\ADB SHELL
# rm /system/app/something.apk
reboot
You have to reboot at the end so that the apps are taken out of RAM, you may get FC (errors) if you try to do stuff after removing the apps before rebooting.
I removed (actually moved) *Twit*, Stock*, Launcher*, and a few other things.
HTH,
Unconn

[Q] Unable to mount /sdcard as rw

I'm currently trying to use adb to push a ROM to my sdcard on my Verizon Galaxy Nexus. However, it keeps failing due to /sdcard being a read-only filesystem.
When I adb shell into the phone and type mount, i get this (among others):
Code:
/dev/block/mmcblk0p12 on /sdcard type ext4 <ro,relatime,barrier=1,data=ordered>
Attempting to mount /sdcard as read-write is not proving fruitful:
Code:
mount -o remount rw /sdcard
Can anyone help? I'm just trying to get a rom on there so i can install it. Unfortunately, the phone never leaves the google screen when i try to boot, so recovery and fastboot are my only options.

mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that

DonDizzurp said:
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
Click to expand...
Click to collapse
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.

ttremblay said:
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
Click to expand...
Click to collapse
To make things easier, copy the .zip file to the folder where you have ADB then try
adb push ./rom.zip /sdcard/rom.zip

I never could get things to push to sdcard while in recovery mode no matter what I tried.
adb sideload was how I always did I
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Or maybe instead of using "/sdcard" use "/data/media"?

Hello there, my samsung galaxy s2 i9100's internal sdcard suddenly became read-only shortly after updating it to 4.1. I've tried using the command: ''mount -o remount, rw /sdcard'' which works until i reboot or connect it to an external usb storage device. I'm kindly asking if anyone knows a permanent solution to my problem. P.S- I'm a bit new to this android thing so make your explanations as easy as possible. Please help

adb mount command for rw on Tab Pro

Just got a used Tab Pro 8.4. I've rooted it and now am interested in debloating it. I've always done this manually with adb on my previous devices using a command I always assumed was specific to that particular device (ie. mount -o remount,rw /dev/block/mmcblk0p20 /system for a Note 3) .
I haven't found any references in the Tab Pro forum to the mount command for writing to the system partition. When I list the mount points with the mount command inside the adb shell I see this:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
So would the command really be mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system ? I have seen references elsewhere to a generic "mount -o rw,remount /system" command for Android devices in general.
I'm sure there are pre-built tools that would let me do some debloating without worrying my little head about what's going on under the hood. But please humor me. I enjoy learning the details of how these boxes operate by working with them manually. Any help here will be appreciated. Thanks.

So you are not going to flash the ROM, you could also try Gates Debloater tool. I used on my Note 4 all the time, may Tab I just flashed to a new ROM though.
Sent from my Nexus 6P using Tapatalk

ossito2012 said:
So you are not going to flash the ROM, you could also try Gates Debloater tool.
Click to expand...
Click to collapse
No thank you. I like to see the .apk disappear when I delete it from the command line. Just a thing I've got. I assume I'm looking for something like "mount -o remount,rw /dev/block/?????? /system".

rtfm1777 said:
No thank you. I like to see the .apk disappear when I delete it from the command line. Just a thing I've got. I assume I'm looking for something like "mount -o remount,rw /dev/block/?????? /system".
Click to expand...
Click to collapse
If it's rooted you can use titanium backup to delete.
Sent from my Nexus 6P using Tapatalk

rtfm1777 said:
No thank you. I like to see the .apk disappear when I delete it from the command line. Just a thing I've got. I assume I'm looking for something like "mount -o remount,rw /dev/block/?????? /system".
Click to expand...
Click to collapse
All you should need to do is
# mount -o remount,rw /system
It's in fstab, so you don't need the block device.
When done just issue a sync and reboot.
Sent from my LG-H901 using Tapatalk

toastido said:
All you should need to do is
# mount -o remount,rw /system
It's in fstab, so you don't need the block device.
When done just issue a sync and reboot.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Done. And it does indeed work. Thank you sir.

Nexus 5x Root Not Detected

Hello, new to forums.
Nexus 5x 7.0 rooted system less but iam no android programmer. Rooted by watching youtube tutorials etc. To fix my root not detected issue google says
adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot
but how ? via the terminal emulator app or go into recovery mode first then via the adb shell. Please provide some pointers.
The other option is see on this thread is
echo "BINDSYSTEMXBIN=true">>/data/.supersu and then reflash SU. But from where and how do I do the
echo "BINDSYSTEMXBIN=true">>/data/.supersu ?
Thanks

up_60188 said:
Hello, new to forums.
Nexus 5x 7.0 rooted system less but iam no android programmer. Rooted by watching youtube tutorials etc. To fix my root not detected issue google says
adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot
but how ? via the terminal emulator app or go into recovery mode first then via the adb shell. Please provide some pointers.
The other option is see on this thread is
echo "BINDSYSTEMXBIN=true">>/data/.supersu and then reflash SU. But from where and how do I do the
echo "BINDSYSTEMXBIN=true">>/data/.supersu ?
Thanks
Click to expand...
Click to collapse
Enter echo "BINDSYSTEMXBIN=true">>/data/.supersu in a terminal emulator.
For exaple => https://play.google.com/store/apps/details?id=yarolegovich.materialterminal

sonixdan said:
Enter echo "BINDSYSTEMXBIN=true">>/data/.supersu in a terminal emulator.
worked like a charm. Reflashed SU using flashfire. thanks
Click to expand...
Click to collapse

up_60188 said:
Hello, new to forums.
Nexus 5x 7.0 rooted system less but iam no android programmer. Rooted by watching youtube tutorials etc. To fix my root not detected issue google says
adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot
but how ? via the terminal emulator app or go into recovery mode first then via the adb shell. Please provide some pointers.
The other option is see on this thread is
echo "BINDSYSTEMXBIN=true">>/data/.supersu and then reflash SU. But from where and how do I do the
echo "BINDSYSTEMXBIN=true">>/data/.supersu ?
Thanks
Click to expand...
Click to collapse
You have to download adb command and use it from command line in Windows. Just enter the commands. You have to have correct drivers and USB debugging enabled at your phone.
Or you can use Terminal emulator in your phone

Touching those files is a terrible idea and will likely break root for other apps (it always broke TiBu for me). You can probably make the supersu file in a file explorer too
Sent from my Pixel using Tapatalk

help me please I cannot modify system files despite having root

i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?

lg_g3_d855 said:
i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
Click to expand...
Click to collapse
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.

User699 said:
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
Click to expand...
Click to collapse
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.

lg_g3_d855 said:
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
Click to expand...
Click to collapse
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.

User699 said:
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
Click to expand...
Click to collapse
yes I'm root, output is file system is read only despite adb commands

lg_g3_d855 said:
yes I'm root, output is file system is read only despite adb commands
Click to expand...
Click to collapse
Well, I'm sorry then... I can't help.
Good luck!