-
Notifications
You must be signed in to change notification settings - Fork 124
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
By editing init, how to change some locations of files? #25
Comments
init
, how to change some locations of files?
init
, how to change some locations of files?
make PR if you want :) |
PR? |
Pull request... |
You mean we should leave stock initrd and boot-magisk in |
Yes. |
Work fine for me ¯_(ツ)_/¯ |
I tried ext4. It could work. The kernel+initrd.img can actually mount f2fs. What's the problem? |
What I want is to achieve this picture,
The advantage of this is
android.cfg
over and over again, if Android x86 updates;initrd.img
(initrd-magisk.img
renamed first) to coverinitrd.img
(the real not having been made a backup, yet), by mistake;.img
files into$SRC
are too many to be recognized immediately rightly, only to be deleted or covered by mistake;.img
file should be renamed at first.And then I create a fork to edit,
After building, I download to try.
It can boot, but seems not to mount
boot-magisk.img
.It must be something I haven't edited yet.
Could you tell me what else I should edit?
I will appreciate it if you would help me about that.
The text was updated successfully, but these errors were encountered: