¶ Overview
Maintainers(was/were): Sophon Wu & TAO_Croatia
Guide author: NeoBlizzard
Status: Supported
The main guide does the job. Multiple installations were done with no issues. However, do note the following information and additional steps before you proceed.
¶ BACKUP! BACKUP! BACKUP!
People don’t do backups, you need them! Seriously!
Backup the modem files as shown in Step 1.3 before you resize the /userdata partition.
In one test case, modem was lost as soon as
/userdatawas reparitioned. Better safe than sorry.
¶ Which image to use
Note that Xiaomi Pocophone F1 comes with two different display panels and touchscreens.
If you observe the edk2-msm releases page, there are two variants of boot images:
-
boot-beryllium-ebbg.imgfor EBBG Panel and Focaltech touchscreen -dsi_ebbg_fhd_ft8719_video_display -
boot-beryllium-tianma.imgfor Tianma Panel and Novatek touchscreen -dsi_tianma_fhd_nt36672a_video_display
Thus, the appropriate version needs to be downloaded to ensure proper functioning of GPU, touchscreen and the whole display after turning it off and on.
For more information about the Xiaomi Pocophone F1 display situation read here
To get your phone variant, run the below command in adb shell:
dmesg | grep dsi_display_bind
This will give you the exact output that we need, it will be either dsi_ebbg_fhd_ft8719_video_display or dsi_tianma_fhd_nt36672a_video_display.
Pay attention to the second word in the output string (ebbg or tianma) and download the appropriate edk2-msm boot image.
If you have your boot image, you are good to go and follow the installation guide!
Don’t forget to come back here after 2.1.4, HOLD YOUR HORSES and do not reboot.
There is still work to do.
¶ Post-boot fixes
The below fixes are applicable as of release
2301.1. If any changes are made in the future, they will be reflected here accordingly.
¶ Touch FixUp
Although the touch drivers have been fixed, it is necessary to do a regedit patch which injects touch screen properties to your device. To do this, there are various methods but I prefer the one below, as it is simple and quick.
All you need to do is to run the .bat file below as an administrator.
Do note that the script assumes the label of your Windows installation as
W:. If it isn’t, edit it accordingly by opening the.batfile in text editor
(Credits to TAO_Croatia and Morc for the original .reg file and NeoBlizzard for editing it to adapt to this guide)
If all is well, you should see an output as shown in the image below.
- Voila! You now have touch working out of the box on your glorified beryllium >:]
Do note that touch does not work when the device wakes up from sleep. It is being worked on, and no ETA can be expected.
Some old guides and YT videos mention flashing a devcfg image. This is NOT necessary anymore.
¶ USB FixUp
Post boot, one would observe that USB accessories do not work out of the box. To fix this, uninstall USB drivers (using DISM++ or DriverStoreExplorer) and load the USB drivers from release 2.0rc2
¶ Dual-booting
Perform the below step ONLY after restoring your modem back as mentioned in the guide here
The internet suggests ridiculous ways to dual boot Windows and Android. However, here is a simple way to get it to work without pendrives and a PC lying around.
If you are comfortable with your Android custom ROM, you can replace the TWRP recovery with the appropriate edk2 boot image for your beryllium.
This allows you to perform a reboot to recovery on Android or holding the Volume Up + Power key to get to Windows. We highly prefer this over other solutions, as it is the most convenient one (for now, at the cost of not having a TWRP recovery)
Note that you will be losing your TWRP recovery, so you’ll need your PC to boot to recovery via fastboot commands, in case you want to flash another ROM.
ROMs boot without recovery just fine, including system_ext ones AND oofgang ports (Derpfest and OOS tested).