Note
- Formatting data with PE recovery is REQUIRED for clean flash
- DO NOT use any other recovery
- The firmware is included with a different keymaster.img from perseus. DO NOT flash your own firmware.
- Keymaster is bumped to 4.0 for encryption, and cust partition is mounted as /metadata. You WILL NOT be able to boot TWRP/OrangeFox on PE12.
- To switch to other ROMs, format data in PE recovery first, and then install another recovery. You may need to re-flash the required firmware, if the ROM you are going to flash does not include one.
- You can dirty flash from my previous PE 12 builds.
- You cannot upgrade from android 11 directly. Formatting data is required.
PE recovery flash guide
- Download PE recovery from the official PE website
- Boot your phone into fastboot mode. You can either
- hold power + volume down button
- or
adb reboot bootloader
- or use the
Reboot to bootloader
option in TWRP/OrangeFox
- Connect your phone to a computer
- Run
fastboot flash recovery pe_recovery_file_name.img
in your cmd/powershell/terminal - Hold power + volume up to boot into recovery
PE 12 flash guide
- Boot into PE recovery
- Select
Factory reset" --> "Format data/factory reset
. You phone should say that /data, /cache, and /metadata have been formatted. - Go back to main menu and select “Apply update” –> “Apply from ADB”
- Connect your phone to a computer
- Run
adb sideload pe_rom_file_name.zip
in your cmd/powershell/terminal and wait until it finishes - Reboot to system
Device Specific Changes
- Fixed the issue of failed OTA installation in the built-in system updater
- you still need to manually
adb sideload
this build in recovery so that the fix can be applied to your current system’s updater - after that, you will be able to install future OTA updates through the built-in updater
- no need to wipe or format anything if you are using my previous PE 12 builds
- you still need to manually
ROM side updates
- Refer to the previous changelog for this month’s improvements and fixes
Known Issues
- Rounded corners are broken. It does not seem to be an issue on the device side, as debug info reports correct values
Please report issues to jjpprrrr.