Dualboot stuck at SimpleInit on Xiaomi Pad 5

[wochgn]

Prerequisites

• [x] Have you read the wiki?
• [x] Is your device in the supported list?
• [x] Does the device have a Snapdragon SOC which is supported in this repo?

Description

[Description of the bug or feature]

Expected behavior: [What you expected to happen]When selected "Reboot to Android", the system reboots to Android

Actual behavior: [What actually happened]When selected "Reboot to Android", the system rebooted but entered Simpleinit again.

The device that couldn't dualboot is Xiaomi Pad 5 with MIUI 14 for Pad V14.0.23.2.13.DEV. However, on another Xiaomi Pad 5 with MIUI 14 for Pad V14.0.23.1.9.DEV, it works perfectly. It wouldn't boot to Android either...

[leandrofriedrich]

@wochgn lol

[qaz6750]

• In fact, Xiaomi 9 also cannot work on some specific versions, and I think it should not be the reason for Android kernel, which is more like a system problem. At the same time, all this is just speculation, because we can't know what every ROM developer has done

[wochgn]

On my Xiaomi Pad 5 running MIUI 14 for Pad V14.23.1.9.DEV, the dualboot stopped working and I was also stuck at Simpleinit...(While it did work yesterday)

[YiyiPenguin]

Hey, I have already tested this method under Arrow OS 13, it works fine. To test the stability of this new method, I restarted my device for about 7 times, without stucking in the fastboot or any behaviour out of control. I think the main reason of the method failed under miui because miui has the self protect, it will recovery the kernel settings, which caused the device can only boot into windows rather than miui. (Emmmmm, finally, if the uefi support poweroff charging, it will be better.) Sorry for my bad English......

[J0SH1X]

@YiyiPenguin Its known since HTC HD2 days that booting windows will remove power off charging lol

[YiyiPenguin]

After several tests, it was broken under Arrow OS 13. So it needs to be fixed in the future.

[wochgn]

Here are the logs from UEFI.

UefiLog1.txt UefiLog0.txt UefiLog2.txt UefiLog3.txt UefiLog4.txt

[MollySophia]

Hey, I have already tested this method under Arrow OS 13, it works fine. To test the stability of this new method, I restarted my device for about 7 times, without stucking in the fastboot or any behaviour out of control. I think the main reason of the method failed under miui because miui has the self protect, it will recovery the kernel settings, which caused the device can only boot into windows rather than miui. (Emmmmm, finally, if the uefi support poweroff charging, it will be better.) Sorry for my bad English......

Actually on my mipad 5 it works well with miui 14. This method seems to have some natural drawbacks that prevent it to be working on every device, and I haven't found a solution yet...

Sorry for my late response

[qaz6750]

Hey, I have already tested this method under Arrow OS 13, it works fine. To test the stability of this new method, I restarted my device for about 7 times, without stucking in the fastboot or any behaviour out of control. I think the main reason of the method failed under miui because miui has the self protect, it will recovery the kernel settings, which caused the device can only boot into windows rather than miui. (Emmmmm, finally, if the uefi support poweroff charging, it will be better.) Sorry for my bad English......

Actually on my mipad 5 it works well with miui 14. This method seems to have some natural drawbacks that prevent it to be working on every device, and I haven't found a solution yet...

Sorry for my late response

It seems to be true that even though I worked well in my mi9 before, I and it can't work now. Maybe it needs some investigation and improvement

[rodriguezst]

Any advice on a custom ROM or something to make this "Reboot to Android" option work? With official HyperOS Global it does not work on my Xiaomi Pad 5 😭

[graphiks]

@hiprivsid hyper-vsid

[palexdev]

@MollySophia any news on this? Seems like my device has the same issue. Linux + EvoX

[rodriguezst]

As an alternative I was trying to boot a boot.img file stored in the esp partition or the inactive boot partition (boot_b in my case) using simple-init but it's not working either. Is this supposed to work?

For reference, this is my current simpleinit.uefi.cfg file in logfs. Menu items are shown but they don't work yet. I will keep reading the docs!

boot.configs.android-img.mode = "linux"
boot.configs.android-img.desc = "Boot Android From File"
boot.configs.android-img.show = true
boot.configs.android-img.enabled = true
boot.configs.android-img.icon = "distributor-logo-android.svg"
boot.configs.android-img.extra.abootimg = "@part_esp:\\boot.img"
boot.configs.boot-b.mode = "linux"
boot.configs.boot-b.desc = "Boot Android From boot_b"
boot.configs.boot-b.show = true
boot.configs.boot-b.enabled = true
boot.configs.boot-b.icon = "distributor-logo-android.svg"
boot.configs.boot-b.extra.abootimg = "#part_boot_b"
boot.default = "android-img"
locates.part_esp.by_disk_label = "gpt"
locates.part_esp.by_gpt_name = "esp"
locates.part_boot_b.by_disk_label = "gpt"
locates.part_boot_b.by_gpt_name = "boot_b"