I rooted my realme c21 using mtk client and magisk
I have tried different apps to ensure that's not the apps problem
(And please say how to make /system RW)
Zartazor said:
I rooted my realme c21 using mtk client and magisk
I have tried different apps to ensure that's not the apps problem
(And please say how to make /system RW)
Click to expand...
Click to collapse
Soory for very delayed reply, i never had trouble with sms, so i have no solution.
The way for making system as read/write;
Code:
mount -o rw,remount /
mount -o rw,remount /system
(Note: it technically should work, but i have not tried on this device)
MrMiyamo said:
Soory for very delayed reply, i never had trouble with sms, so i have no solution.
The way for making system as read/write;
Code:
mount -o rw,remount /
mount -o rw,remount /system
(Note: it technically should work, but i have not tried on this device)
Click to expand...
Click to collapse
that code won't work on android 9 and above
Search forums for super_rw v1.32
Super partitions need to have their blocks removed first and that script does it for you, then just flash the new super image it produces.
Used it on my C3 and c21
Related
I have rooted HTC Desire and i tried to remove system app in many ways but nothing worked. Pls give any advice how can i done this.
First i tried with Root Explorer, i mounted R/W mode i deleted the app, the app is deleted from /system/app but present in menu and when i restart the phone it comes back in /system/app
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Third i tried with Titanium Backup Pro, when i Uninstall the app i got the same result but when i try to freeze it that's the only way i can remove from the menu :\
Thanks
Root Explorer only works if you're S-OFF
Easiest way, download the Android SDK and use adb in Recovery to remove them
Remove the apps from the ROM before flashing it?
Be carefull as removing certain apps can make the ROM unstable.
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
EddyOS said:
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
Click to expand...
Click to collapse
I've recently come across two very interesting Windows apps which make the process easy.. Android Commander and QtADB...Both are GUI frontends for ADB, so once rooted, removing it should be easy in these. However, I believe that some may be removable only in Recovery mode, unless you have S-OFF
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
v.pakard said:
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
Click to expand...
Click to collapse
With Alpharev
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Click to expand...
Click to collapse
Did you boot to clockwork recovery first? You must and then run
adb shell
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
rm anythingyouwant.apk
rm anythingyouwant.odex
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot with trackball
This is how I do it in linux. You can boot with live distro linux, connect your desire and start console. I think it should work. I do it from virtualbox.
Thanks alot, S-OFF was the problem, my phone was rooted but not S-OFF. Now everything is fine.
Thanks,
pakard
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.
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.
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
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!