How to enter safe mode when boot fails about rootavd

[newbit1]

Is this really rootAVD related?

To disable Magisk-Modules, you can place a disable file into its directory.

Or you can just delete them all at once like in the Magisk FAQ mentioned.

You can do both via adb.

To boot your AVD into Safe Mode, you can follow the guide How to boot your device up in android safe mode

Works perfect.

[andronoob]

Is this really rootAVD related?

Yes, I think, without your amazing work I won't be able to install magisk onto AVD.

However I just want to share my experience.

You can do both via adb.

When a problematic module blocks boot process, adb is simply not available at all.

To boot your AVD into Safe Mode, you can follow the guide How to boot your device up in android safe mode

When the AVD simply fails to boot, there's no chance to click that "reboot to safe mode" button.

[andronoob]

I hope that some hints could be added to README and text prompt of this script, so that in the case a problematic module blocks the AVD from normally booting, the user will feel less anxious.

[newbit1]

What exactly do you want in the readme? The primary scope of the script is to install Magisk, everything beyond this is Magisk
related. You can always wipe data or restore the ramdisk.img

[andronoob]

The primary scope of the script is to install Magisk, everything beyond this is Magisk
related.

Of course. However I didn't know Magisk supports safe mode in the beginning either. I think some reminders about this can be helpful.

Maybe just a reminder like "in case a problematic magisk module bricks your AVD, you may try pressing the volume down button to enter safe mode!" is enough.

You can always wipe data or restore the ramdisk.img

Sometimes you don't want to wipe data. To my understanding, although restoring ramdisk.img can make the AVD boot again, it will neither disable any magisk module, nor provide root access, so that safe mode is still useful to quickly fix a "bricked" AVD by disabling all magisk modules.

[newbit1]

Agree! This does definitely elevate the support level, especially the part that avoids wiping the data.
Could you please provide me this "bricking" module? So I can reproduce that issue and a possible way to fix it.

[andronoob]

Could you please provide me this "bricking" module? So I can reproduce that issue and a possible way to fix it.

Thanks, but, actually it was not a ZIP, I wanted to modify some system files, so I just copied & modified the hosts module (inside /data/adb/modules) to achieve this. Other modules (including the hosts module) is working without problem.

[newbit1]

Then send me just this. Or create a module that breaks. Without something, I can't reproduce anything. Sorry

[andronoob]

Or create a module that breaks.

Maybe you could try this (assuming you've already added hosts module), after entering adb shell:

(of course, since this will brick the AVD, you should be prepared for this)

su
cd /data/adb/modules
cp -a hosts badmodule
cd badmodule
rm ./disable
rm ./system/etc/hosts
rmdir ./system/etc/
mkdir ./system/lib/
mkdir ./system/lib64/
touch ./system/lib/libc.so
touch ./system/lib64/libc.so
reboot -p

[newbit1]

thanks! Can't find any module with this name.
Can you provide me a link please?

[andronoob]

Can't find any module with this name.

It can be added by clicking "Systemless hosts" in magisk app settings.

[newbit1]

Thank you for your patience. Readme is updated.