Hey all, New to this exciting world of Android compiling so forgive the likely simple question:
I have been trying to prove to myself that I can create a directory or file by modifying a ramdisk, repackage it into a boot.img, and flash that image back up to the device. However, when I make any changes to the ramdisk, I notice the changes are not reflected at all when I am looking at the filesystem while I am adb shell'd in the device. From reading the Magisk docs, I get that there's a 2 stage mount process going for my Pixel 4a. However, I would expect that if I were to simply tweak my ramdisk.cpio (extracted via magiskboot), add a file/directory, to say /system, I'd expect that to show up after doing a `fastboot flash boot /tmp/new-boot.img && fastboot reboot` as the /system partition mounts to the rootfs when booting up. I get that there could be other gotchas as play, like A/B partitions for OTA updates and whatnot, but I have tried flashing both partitions, doing a hard reset, and to no avail. I can not get any file modifications to be picked up in my ramdisk... which boots and runs perfectly fine btw, but without the expected mods. What (obvious?) component could I be overlooking? Thank you! -Derek -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/b8ac50c0-b778-4f95-b423-d3906e5f8decn%40googlegroups.com.
