It is very bad that you are using unofficial site for downloading magisk. The official builds are only on Github - https://github.com/topjohnwu/Magisk/releases
Brilliant thanks mate. For anyone else wondering, the magisk 23.0 zip from the link above works perfectly. TWRP is not required. I was able to reboot into the pixel experience recovery and flash it via adb connected to the pc. Root and magisk hide work perfectly. Safety net passes.
I also tried updating to magisk canary, however this would hard lock the phone 2 minutes after boot no matter what I did. Best to stick with 23.0.
It's true what @dduuch said.
What are the steps for dirty flash. Assuming it is done with trwp and the new image loaded onto USB storage of the phone?
I can't tell compared to Project Elixir, but I can tell compared to A11 PE the difference on battery life and the smoothness is noticeable.
Dirty flash from DotOS 5.2 (Android 11). Everything works fine.
No. Read the Instructions.
You did dirty flash from A11 to A12 PE? Do not ever do that in any ROM.I did a dirty install through TWRP, right now my device is constantly crashing and rebooting to system. Additionally i'm not able to flash into TWRP Recovery anymore, starting my device by holding down the Power button + the volume up button simultaneously flashes it into PixelExperience recovery mode instead. I've kinda reach a dead point as far as my knowledge goes on how to solve this situation.. :O
Anyone has a solution, or any advice? Thank you in advance!!
Thanks, I'll follow the steps you listed here.No. Read the Instructions.
You did dirty flash from A11 to A12 PE? Do not ever do that in any ROM.
Read the instructions of the ROM you flashing.
The ROM is encrypted by default.
TWRP doesn't support decryption of encrypted A12 ROMs yet.
So in order for future OTA updates to work, flashing A12 PE will automatically replace the TWRP with PE recovery which can handle encryption of the ROM and OTA will work normally. If you need to flash anything like magisk you can sidealod it from PE recovery via adb. This is a temporary solution until the TWRP can handle decryption of encrypted A12 ROMs.
Now you need to flash official twrp via fadtboot adb wipe everything, format fata "type yes" (all your files into your internal storage will be lost), connect your device to pc while you are in twrp and transfer the rom. Flash it and done. If u ever need to switch a rom, simply flash twrp by fastboot adb and clean install(format data also) the rom you want.
If you can connect the device to pc while you are booted and you can see Internal folders just take backup of it, to your pc.
I don't know what you did and how you managed to boot and twrp not replaced but if you can boot fine, the ROM is encrypted by default and the TWRP can't decrypt the storage. You will see random names on folders. Unless you flashed DFE but you will not get OTA either.Well, I did a backup in case anything go wrong. So I tried dirty flashing it using TWRP 3.6.0 and everything is working fine for now. I also still have TWRP 3.6.0 which is pretty good imo.
And if someone is too lazy to patch the boot.img for Magisk, I'll upload the patched boot.img here.
All I did is dirty flash the ROM and wipe cache before rebooting like I always do with every update.I don't know what you did and how you managed to boot and twrp not replaced but if you can boot fine, the ROM is encrypted by default and the TWRP can't decrypt the storage. You will see random names on folders. Unless you flashed DFE but you will not get OTA either.
Beside that, it's possible to have errors or crashes so we will not accept reports of these.
In any case, I don't recommend to anyone to dirty flash from A11 to A12 in any rom. Read the instructions the dev wrote.
Also magisk patched boot image no need. Anyone can simply flash Magisk.zip.
Yes, there is already a closed beta version in the internal testing team.