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.
Related
I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used these commands:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.
I've always used 'mount -o remount,rw /dev/block/mmcblk0p25 /system'
as far as 'correct' code I don't think there is as such. But I think different devices would have different partitions and mount points for system.
-Nipqer
I think it will depend on where your system is mounted, although I don't know why that would vary for the G2. It might be different for the DZ and certainly for other devices.
You can type "mount" in the terminal to see where everything is mounted.
Ditamae said:
I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used the code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.
Click to expand...
Click to collapse
i use this command:
# mount -w -o remount /dev/block/mmcblk0p25 /system
Thanks for the replies... I see now, that the path I should have used is: /dev/block/mmcblk0p25 /system. And that "code" was the wrong word. I was asking about commands & paths not code. Sorry - still learning.
edit: If anyone knows of a good and thorough resource of Terminal commands, I'd love it if you'd share... I've found bits and pieces of info, but something more comprehensive would be great. Thanks again.
Wow you guys are going about it using the long hand method. If you're just deleting a system app, to mount the /system as rw just enter:
Code:
$su
#mount -o remount,rw /system
#rm -f /system/app/xxxx.apk
The -f command isn't really needed but I use it to make sure the job gets done. Not sure if the pm uninstall command is used anymore. I'll have to look into that. I know some phones required you to mount yaffs and mmcblockXX but for just deleting an app I don't believe it's required. Never had an issue not typing that.
Here's the correct way to delete the app:
mount -o rw,remount /system
rm /path/to/app
reboot
Click to expand...
Click to collapse
Or you could use remount,rw. It's the same command. I threw reboot in there to reload the app list in your launcher correctly.
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Antalor said:
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Click to expand...
Click to collapse
omg no no no no.
if you are talking about trying to use "adb push <name of file> <destination file>"
Then you must use "adb remount" if it fails, you are not on an insecure kernel. Thus your only option is to push to the sdcard then use "adb shell" and navigate to your sd card and use "cp <name of file on sdcard> <destination file location>"
as for the commands, it is NOT what you have posted. it is simply
mount -o rw,remount /system
nothing else is needed. You will seriously mess something up if you try mounting it as yaffs2 considering we use ext4 now. FYI, the above command can only be entered AFTER first entering "adb shell" which gives you a command line on the device to execute commands.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Antalor said:
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Then you need to use
adb shell mount -o rw,remount /system
thats it. To uninstall apks, use:
adb uninstall <package name>
And you are getting a read only system error because you are trying to create that "file.txt" file onto your "root" directory.
do this:
adb shell cd /data/media/0
then try to do your list packages.
Hi,
I have rooted my pixel c running android 7 but am unable to remount /system as rw. I get "Device or resource busy" after running mount -o remount,rw /system
Can anyone confirm this? What can I do to resolve this issue?
I am getting the same issue on my Pixel XL
Have a try this way ...
Code:
mount -o rw,remount /system
followmsi said:
Have a try this way ...
Code:
mount -o rw,remount /system
Click to expand...
Click to collapse
Thanks a thousand!
followmsi said:
Have a try this way ...
Code:
mount -o rw,remount /system
Click to expand...
Click to collapse
Thanks mate
Just wanted to know if anyone knows how to disable the virtual cdrom in OOS when you plug in usb to pc. I have looked and there is no cdrom.iso like other phones i had.
Edit: Just overlooked the file.
If anyone is interested in disabling the virtual cdrom upon usb connection, navigate to /system/etc with a root filemanager and rename usb_drivers.iso to usb_drivers.iso.bak and reboot. or enter the following commands in adb shell and reboot. Phone MUST be rooted.
Code:
adb shell
su
mount -o remount,rw /system
mv /system/etc/usb_drivers.iso /system/etc/usb_drivers.iso.bak
mount -o remount,ro /system
Revert
Code:
adb shell
su
mount -o remount,rw /system
mv /system/etc/usb_drivers.iso.bak /system/etc/usb_drivers.iso
mount -o remount,ro /system
Edit: fixed a typo
for everyone getting this Error:
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Click to expand...
Click to collapse
You have to use this Command
mount -o rw,remount /system
Click to expand...
Click to collapse
instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
That worked for my OnePlus 6.
Thanks!
That worked for my OnePlus 7 pro.
Has anyone been able to remount /system as rw? FX File Explorer says it's successful but then switches automatically back to read only
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
ichimei said:
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
Click to expand...
Click to collapse
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Josh McGrath said:
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Click to expand...
Click to collapse
FAILED (remote: 'unknown command')
Finished. Total time: 0.004s
Click to expand...
Click to collapse
It was worth a shot
blackknightavalon said:
It was worth a shot
Click to expand...
Click to collapse
Are you able to flash with TWRP by any chance?
Josh McGrath said:
Are you able to flash with TWRP by any chance?
Click to expand...
Click to collapse
TWRP doesn't mount /system at the moment on anyone's devices
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
WillSmith89 said:
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
Click to expand...
Click to collapse
That's what I'm working on. I tried a workaround but got this
mount -o rw,remount /
'/dev/block/dm-8' is read-only
Click to expand...
Click to collapse
I'm trying other things as I think of them, and I have a few ideas
blackknightavalon said:
That's what I'm working on. I tried a workaround but got this
I'm trying other things as I think of them, and I have a few ideas
Click to expand...
Click to collapse
Do you know if stock Oneplus recovery will flash unsigned zips?
Not sure. Got one I can flash via Fastboot?
blackknightavalon said:
Not sure. Got one I can flash via Fastboot?
Click to expand...
Click to collapse
Maybe, let me go through my old files cause I think I have dmverity disabler for stock recovery zip
Okay, I'm getting closer. Typing in
mount -o rw,remount /system
Click to expand...
Click to collapse
as usual gives me the "not in /proc/mounts" thing, but typing in
mount -o rw,remount /product
Click to expand...
Click to collapse
gives me the "/product is read only" error.
What we need is a kernel that'll let us mount /product in order for us to REALLY start playing with this device
------------------------------------------------------------------------------------
Okay, here's the Terminal results of my latest attempts. Maybe someone can have better luck than me
OnePlus7T:/ $ su
OnePlus7T:/ # mount -o rw,remount /sbin/.magisk/block/system_root
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-11
'/dev/block/dm-11' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-9
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8
'/dev/block/dm-8' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system
mount: '/system' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system/product
mount: '/system/product' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /super
mount: '/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # ls -l /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-01-12 02:43 /dev/block/by-name/super -> /dev/block/sda15
OnePlus7T:/ # mount -o rw,remount /dev/block/sda15
mount: '/dev/block/sda15' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/by-name/super
mount: '/dev/block/by-name/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /init
mount: '/init' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /system/etc/init
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ #
Click to expand...
Click to collapse
Okay, I have an idea but I'll have to wait for the next official build to test it
Any news on this? Really want to uninstall Google Pay and install an older version of it.
blackknightavalon said:
Okay, I have an idea but I'll have to wait for the next official build to test it
Click to expand...
Click to collapse
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Josh McGrath said:
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Click to expand...
Click to collapse
Tried it through Terminal commands via Terminal Emulator AND ADB. Haven't tried it through fastboot. I'm downloading the OTA now (been in Florida on vacation, leaving back for NYC this afternoon)
I tried to change font, but I cant remount system. any idea? ( the mogule font_changer has remove of programmer, my device is root without twrp.
You cant mount system as r/w because android 10 is read only