New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for /oem (remount failure) #441

Closed
ghost opened this Issue Jul 18, 2016 · 6 comments

Comments

1 participant
@ghost

ghost commented Jul 18, 2016

Root: yes with superSU 2.76

When trying to delete files in /oem/deletable-app/ sdmaid shows '1 error' and doesn't delete anything (even if I change permissions of that file to 777). Anywhere than there I get '1 error' but sdmaid remove the file (like in /system/vendor/)

@d4rken

This comment has been minimized.

Owner

d4rken commented Jul 19, 2016

/oem is a distinct partition SD Maid is not yet familiar with.
Can you tell me more about it's purpose?

Can you give me a log of its content (e.g. explorer>save directory structure)?
I'm interested in whether there are any symlinks.

We also need to know whether apps are directly sourced from that location or whether /oem is just used to copy back preinstalled apks after a factory reset.

Actual deletion fails because SD Maid doesn't know what to remount.

Error:rm: can't remove '/oem/deletable-app/com.kobobooks.android/com.kobobooks.android.apk': Read-only file system

btw perfect ticket ❤️

@ghost

This comment has been minimized.

ghost commented Jul 19, 2016

Basically the core /system partition is controlled by Google. OEMs are not allowed to customize it.
All OEM customizations go into /oem. For example I have the bootanimation there.

Directory structure: http://hastebin.com/edeveketav.avrasm

@d4rken

This comment has been minimized.

Owner

d4rken commented Jul 19, 2016

Similar to #410.
Support for this would mean adding a module to the storage manager (to add /oem) and module to forensics (to detect when an item is located in that location).

I'll mail you a test version to the mail from this post when I implemented this, ok?

@d4rken

This comment has been minimized.

Owner

d4rken commented Jul 19, 2016

Basically the core /system partition is controlled by Google. OEMs are not allowed to customize it.
All OEM customizations go into /oem. For example I have the bootanimation there.

So apks are directly used from there, like from /system? Meaning it doesn't copy apks from there to /data?

@d4rken d4rken changed the title from Problems with file explorer to Support for /oem (remount failure) Jul 19, 2016

@ghost

This comment has been minimized.

ghost commented Jul 19, 2016

That's not it, apks are also in '/data' but it looks like I'm able to uninstall audiorecorder so I think apps in '/oem/deletable-app' are "system app" which I Can uninstall without root privileges.

For the email yeah, you can use that but I'm actually on holiday so I don't have wifi or a stable connection to test it, sorry :(

@d4rken

This comment has been minimized.

Owner

d4rken commented Jul 19, 2016

No worries, thanks for your contribution.

@d4rken d4rken closed this Jul 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment