Long story short I deleted my liboemcrypto.so and I didn't make a backup. Can anyone kindly send me of their liboemcrypto.so for the S20 Ultra?
So you somehow had the wherewithal to root your device, mount /vendor read/write, and remove liboemcrypto.so... yet lack the ability to unpack an official image, extract liboemcrypto.so from it, and copy it back to your device?
sjevtic said:
So you somehow had the wherewithal to root your device, mount /vendor read/write, and remove liboemcrypto.so... yet lack the ability to unpack an official image, extract liboemcrypto.so from it, and copy it back to your device?
Click to expand...
Click to collapse
Im just gonna be honest Im too dumb for these things
Related
So I'm taking a Forensics class right now and our teacher challenged us to try and do some forensic work on a phone. I want to try this with my DInc, but I don't know if it's even possible to mount the root directory. Is it or do I have to just do an adb pull to get everything?
And the reason I want to mount the rootdir is so I can make an image of the entire phone's system to try and maintain file integrity.
tiger578 said:
So I'm taking a Forensics class right now and our teacher challenged us to try and do some forensic work on a phone. I want to try this with my DInc, but I don't know if it's even possible to mount the root directory. Is it or do I have to just do an adb pull to get everything?
And the reason I want to mount the rootdir is so I can make an image of the entire phone's system to try and maintain file integrity.
Click to expand...
Click to collapse
In Windows you can use Android Commander
http://www.xda-developers.com/android/android-commander-now-available-updated/
NilsP said:
In Windows you can use Android Commander
http://www.xda-developers.com/android/android-commander-now-available-updated/
Click to expand...
Click to collapse
So......it's just a GUI for adb. It's nice and useful and all, but not what I want. :/
I want to actually mount the root directory and make it appear as a drive. Not just send a request to the phone to pull it.
Question: Is it true that on stock kernel for Arc, any modification make to Vendor folder will be denied? I try to install some apps with cwm, only the apps that has modification to vendor folder wont work. info: i used file manager to access that folder, it can be open, but the files within cant be edited, not even paste a new file or replace any files.
xange said:
Question: Is it true that on stock kernel for Arc, any modification make to Vendor folder will be denied? I try to install some apps with cwm, only the apps that has modification to vendor folder wont work. info: i used file manager to access that folder, it can be open, but the files within cant be edited, not even paste a new file or replace any files.
Click to expand...
Click to collapse
As far as I know, indeed. At least not through CWM, you might be able to edit via ES File Explorer(used myself), make sure to make /system writeable.
Someguyfromhell said:
As far as I know, indeed. At least not through CWM, you might be able to edit via ES File Explorer(used myself), make sure to make /system writeable.
Click to expand...
Click to collapse
You should flash arc S ftf to arc. It might help you
Hey guys, I recently updated my Moto Z Play, retin version to Oreo...Rooted it via magisk and installed xposed.. So far everything seems good and the battery has also improved a lot.. The only thing that bugs me right now is that i am unable to modify /system files... I was trying to change my bootanimation.zip file...Used RootExplorer, FX Explorer, Root Browser but to no avail..All of them were denied RW permission... Tried booting into TWRP and mounting system as RW, moved the bootanimation.zip to system/media and as soon as i rebooted my device, the change was reverted... It seems any change we make to /system is reverted back due to verification at boot... Is there a way to enable RW access so that i can modify /system files... Thanks
mhp1995 said:
Hey guys, I recently updated my Moto Z Play, retin version to Oreo...Rooted it via magisk and installed xposed.. So far everything seems good and the battery has also improved a lot.. The only thing that bugs me right now is that i am unable to modify /system files... I was trying to change my bootanimation.zip file...Used RootExplorer, FX Explorer, Root Browser but to no avail..All of them were denied RW permission... Tried booting into TWRP and mounting system as RW, moved the bootanimation.zip to system/media and as soon as i rebooted my device, the change was reverted... It seems any change we make to /system is reverted back due to verification at boot... Is there a way to enable RW access so that i can modify /system files... Thanks
Click to expand...
Click to collapse
Try looking for a system_root folder that Magisk creates and see if you can change it there.
Milly7 said:
Try looking for a system_root folder that Magisk creates and see if you can change it there.
Click to expand...
Click to collapse
Nope, there is no such folder in my phone... Is it just me without RW /system access or is it with every oreo devices? How do you guys access and modify /system files on oreo?
Idea of Magisk is not to modify system. Please read documentation and questions other peoples asked.
tag68 said:
Idea of Magisk is not to modify system. Please read documentation and questions other peoples asked.
Click to expand...
Click to collapse
I know but on 7.1(nougat) with magisk and xposed installed, I was able to modify system files.. I used to do all kind of build prop edits & other stuff but on oreo I am facing issues with installation of busybox as well as modifying system files...
My problem is the opposite: it is way too easy to mount system rw. One click ona button in TC, and I won't be able to do OTA without flashing system again.
So, I don't want to find out if system is mounting rw on my mobile. These modifications you want to do are better to do in Magisk way. If you do a system update, you keep your Magisk settings, so modifications will stay. OTA will only require uninstall of Magisk. Why do you want to do them the hard, incompatible way?
tag68 said:
My problem is the opposite: it is way too easy to mount system rw. One click ona button in TC, and I won't be able to do OTA without flashing system again.
So, I don't want to find out if system is mounting rw on my mobile. These modifications you want to do are better to do in Magisk way. If you do a system update, you keep your Magisk settings, so modifications will stay. OTA will only require uninstall of Magisk. Why do you want to do them the hard, incompatible way?
Click to expand...
Click to collapse
+1
<deleted>
On some device you can do this function in recovery.....
TWRP can do these changes when you disable the "mount system as RO" in mount settings. But you'll have to flash a zip that removes dm-verity too, otherwise it won't boot up. Magisk will most likely fail to change the bootanimation on many devices because it can't replace it soon enough.
Hello There. I rooted with magisk today. Evrrything worked fine until I tried to change something in /system folder.
I have read in the internet that u wont have access to system folder if you are on root with magisk. It says u need to modify the .mirror folder. In this ./system/media I try to change the bootanimation. zip, but I cant change or delete the stock one. I think I do not have root acess in this folder. But I can use apps like Greenify without problems. Have I done something wrong? I gave different file exporer full root access I am using:
Mi10t Lite
MIUI 12.0.8 (GLOBAL)
Android 10
Gauguin
Magisk Version is the newest: 21.4
Magisk Manager: 8.0.7
I think i found the answer...:
System partition locked to read only in Android 10
Help, I don't know what I did but after installing a custom ROM, I noticed that my system partition cannot be mounted as read/write. I tried "mount -o rw,remount /system" command on a terminal
android.stackexchange.com
Create a Magisk module to modify files in /system partition.
_mysiak_ said:
Create a Magisk module to modify files in /system partition.
Click to expand...
Click to collapse
How do I do that?
Francescohub said:
How do I do that?
Click to expand...
Click to collapse
Either create your own module from scratch following the Magisk guide, or adapt one of the existing ones.
You're trying the mount -o rw,remount as root (means: you did a "su" before the "mount")?
Maybe a "blockdev --setrw /dev/block/dm-X" helps (see which dm- is mounted as system for the X).
Greetz
Kurt
hello
also i tried to modify mixer_paths_cdp.xml in / vendor / etc, but i am not able to get myself a magisk module
You can use for example this very simple Magisk module as a template.
Create desired folder structure in the zip file, add your xml files for modification, remove the AOD overlay apk/folder and try to flash it.
Keep TWRP at hand if you mess up something so you can delete the module from recovery if necessary.
I stumbled upon this solution for RW system partition in Android 10+. Someone brave enough might give it a try. https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
_mysiak_ said:
I stumbled upon this solution for RW system partition in Android 10+. Someone brave enough might give it a try. https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
Click to expand...
Click to collapse
i can't download it
carabot said:
i can't download it
Click to expand...
Click to collapse
Works for me.. Anyway, you should provide your feedback/complaints to the author.
download ok
I hope not to do any damage
Hello! I just rooted my Rog 6 with Magisk to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Well you must be in os12 same issue with me but in different device
senna33 said:
Hello! I just rooted my Rog 6 to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Click to expand...
Click to collapse
did you use a file explorer that supports root and try to change the permission on the file?
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
senna33 said:
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
Click to expand...
Click to collapse
i don't understand how a device is rooted if you can't modifie system files
nadejo said:
i don't understand how a device is rooted if you can't modifie system files
Click to expand...
Click to collapse
That's kinda how I feel about it. Root Checker Pro says I have root, I can run Su in a terminal and I get a popup asking for superuser rights when I use a function that requires root. I attached some screenshots from Root Checker Pro
The problem is that the partitions (system vendor and co) are only integrated as R/O and cannot be easily integrated as R/W
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
senna33 said:
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
Click to expand...
Click to collapse
ChrisFeiveel84 said:
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
Click to expand...
Click to collapse
I converted still same
Mr Hassan said:
I converted still same
Click to expand...
Click to collapse
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
ChrisFeiveel84 said:
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
Click to expand...
Click to collapse
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
If the partitions are not converted from erofs to ext4, it remains with ro because erofs cannot be mounted as rw
Mr Hassan said:
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
Click to expand...
Click to collapse
how did you try to convert the images to ext 4 without write protection?
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
There's thread available on xda but as i told useless
What u think as i said upper if device
Dev block mapper have full root
But not possible to edit system vend or anything
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
see this
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
and still i,m not able to edit these parts
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
ChrisFeiveel84 said:
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
Click to expand...
Click to collapse
Men see upper logs its converted to ext4
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
ChrisFeiveel84 said:
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
Click to expand...
Click to collapse
But in os10 os11 is possible
But don't know how to fix this os12
Is there anyway to remove write protection?