Database Info

LineageOS 16.0 appears to be live for the Essential Phone. Anybody try it yet?

I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).

jaylittle said:
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
Click to expand...
Click to collapse
I did it and so far looks good

jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !

Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/mata

jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Do you play any games? I'm having issues with touch in games only so far

joha386 said:
https://wiki.lineageos.org/devices/mata
Click to expand...
Click to collapse
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.

MattCB72 said:
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
Click to expand...
Click to collapse
Yes it didn't for me. I used instead:
> fastboot flashing unlock

Not able to install Gapps. Always get Error 70...

dazeone said:
Do you play any games? I'm having issues with touch in games only so far
Click to expand...
Click to collapse
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.

Steps that I followed to get it up and running
Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)

psychic_quark said:
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
Click to expand...
Click to collapse
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !

Another way to use twrp without touch is by using a mouse. If you have one with a type C connector, plug it in and you can flash LOS and the twrp installer. Then boot back to recovery and flash GAPPS. I had to do it this way but I had an adapter for the type C plug so I could use a regular mouse. The adapter came with my Pixel 2XL.

I kept getting error 70, so I used MindTheGapps, which installed fine. Don't know if there's any adverse effects of doing that though, by my phone seems to be working fine.
Wish there was some way to configure fullscreen on the notch though.

theycallmetony said:
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.
Click to expand...
Click to collapse
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…Because of the bad optimization of the kernel, before my phone runs smoothly there is some annoying minutes…
And when I try to flash Neutrino Kernel and reboot, all my PH-1 does is stuck in "phone is starting" with a dialog reminding me that there is an internal error with my system, and it never truly enters the launcher… Has anyone tried yet?

Rachel030219 said:
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…
Click to expand...
Click to collapse
Been running the 20190614 nightly for ~13 hours straight without the need to reboot. Pokémon GO is still running smooth!
Edit: Touch problems started again a couple hours after posting this. Fortunately, a reboot still resolves the issue.

Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.

Hero2457 said:
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
Click to expand...
Click to collapse
Same here, unfortunately. The first time (this was a clean flash after a full wipe), it showed the boot animation for an hour before going back to twrp. I tried flashing it again after another wipe, and this time it stayed in the boot animation overnight, for at least ten hours. I'm not sure where to send a bug report or what info to attach to the bug report.
The regular (non-microG) LOS on the other hand, works fine.

Djalil87 said:
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !
Click to expand...
Click to collapse
I was on Q beta 4 and these steps worked for me:
Here's what worked for me:
fastboot flash boot <twrp image from twrp.me>
<boot into recovery>
Touch isn't working, so instead I do: adb shell twrp sideload
adb sideload <lastest lineage rom>
(again) adb shell twrp sideload
adb sideload <twrp installer zip>
adb reboot recovery
Touch worked in twrp!
Proceeded with installing opengapps/nanodroid and all that jazz.
TBH you don't need touch to achieve most (if not all) functionality of twrp.
To reboot back to recover from within twrp (assuming you have already flashed twrp installer after flashing rom), just do: adb reboot recovery

psychic_quark said:
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)
Click to expand...
Click to collapse
Brillant post @psychic_quark that was the only guide which worked for me, coming from Q beta 3. Thanks.
Step 1.1 was needed for me to flash boot_a or _b in step 2 depending on the result in 1.1.
@jaylittle thanks also for telling us. I also waited for a year to get LOS on my PH-1. I got it from the amazon deal and was ran invisiblisk ROM of Dec.

I ran the June 15 ROM with opengapps pico and magisk in recent version and yestersay I updated via OTA to June 18 ROM without loosing root. Thats very cool. With other ROMs I had to install magisk after update again.
Did anyone tried to install twrp permanently?
And my second question is about removing the red warn during booting which has to be ack-ed. I found this https://mata.readthedocs.io/en/latest/ under topic "Removing the Red Verity Warning" did anyone tried this and will this remove root?
Thanks for your help.

[DEPRECATED] Detailed Installation Guide for Custom Roms (Mi A2 Lite - Daisy)

Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
7) An unlocked Bootloader
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
(If you want to flash PixelExperience Official, continue with this guide by the PE team. If you face any issues, check the NOTES section of this guide)
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-3.4.0-3-unofficial-daisy.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then "Format Data". Type "yes" and press enter. (Keep in mind that all of your data will be wiped and there is no going-back).
9) Go back and press "Advanced Wipe". and select everything except "SD Card". Swipe to confirm the action.
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and swipe to confirm the action)
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
(Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default, although flashing that zip won't hurt anything)
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
(Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.)
(Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.)
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have affected your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernel is Sleepy and it can be found on Telegram (https://t.me/Laciakerneltg). Therefore, there will be no support offered if you are using a 3.18 kernel in a ROM that uses 4.9 kernels (all new UPDATED roms do)
- If your fingerprint doesn't work / partially works, flash this fix in twrp (This issue exists in the official version of pixel experience)
- Android 11 ROMs might require extra steps that are not mentioned here, please follow the respective maintainer's installation guide for now.
CREDITS
tkchn for some parts of the guide
@Offain for FED
@FDoop for some links and guides

Amazing ?

Detailed Guide
LinkBoi said:
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-daisy-3.3.1.0-offain.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then Advanced Wipe and select everything except "SD Card".
9) Go back and press "Format Data".
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and confirm the action) :
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
PSA: Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default.
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
PSA: Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.
PSA2: Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have "hit" your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernels are: Sleepy (can be found in Telegram) and Loki (Link here). Therefore, there will be no support offered if you are using a 3.18 kernel in a rom that uses 4.9 kernels (all new UPDATED roms do)
CREDITS
tkchn for some parts of the guide
@offain for TWRP IMG and FED
@FDoop for some links and guides
@ScaryMen1325 for fixing MTP in @offain's twrp for 4.9 kernels
Everyone who builds Custom Roms
Click to expand...
Click to collapse
Hi LinkBoi,
Hope You're Doing Great.
Detailed Guide...
Really Appreciated For Your Hardwork.
Thanks,
MUHAMMAD Asif Qasim

Wow, so much information in one place. Thanks for spending your time on this.

Pat750 said:
Wow, so much information in one place. Thanks for spending your time on this.
Click to expand...
Click to collapse
Thanks for the positive feedback

Thanks for the great and detailed work..

I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again

mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Not quite the same... But the stock rom .tgz can be flashed using fastboot. That's what I do, since my main system is a Mac.
I think EDL/miflash can fix some things fastboot can't (eg. partition table).
For "flash stock and erase data" it should be fine.

mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Are you on mac or linux? For, mac, I know little about the process. Edl flashing is certainly not possible in mac os. Regarding linux, there is qdl if you wanna try it, but i do not recommend it. For fastboot flashing, you can try the .sh scripts in the stock rom's folder but no support will be given.

Guys thanks for your answers, sorry for being late I have been occupied. I'm on Linux, Ubuntu 18.04. I didn't remember that stock roms come with sh script. Has been a long time since I did this kind stuff and it was with a ZTE Open with Firefox OS :laugh: Maybe I'm gonna try downgrade, I'm testing the last stock version and it is working good so far .

Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?

93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
Yes

93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
depends one which stock version you're on. The ones I have recommended have been tested and work well. Users have reported that latest stock q works well too. From my experience, anything over 10.0.13.0 is good but if you have weird bugs, try to flash any of the recommended stock roms first and see if those bugs persist.

TWRP Recovery Update
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix

LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
Click to expand...
Click to collapse
Original post has been updated aswell

Twrp update 2
If you have the recovery loop issue (the device is always booting to recovery), go to advanced > fix recovery loop, confirm the action and it should be fixed )

Twrp update 2
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Based on @TogoFire's TWRP device tree:
- Updated kernel image in the bootable image to 4.9.234.
- Fixed USB, to be recognised better.
- Added the double-tap-to-wake (dt2w) gesture. (When the screen is off, you can press it twice to open it)
- Remove the reboot to EDL option as it didn't work
Note:
- Decryption doesn't work
- If you have any issues regarding double tap to wake, try to delete the .twrps file in the TWRP folder (can be found in the Internal Storage).
Credits:
- @TogoFire for the device tree (all of the work is his)
- @lslx_22S99176LF, @proxer05 for testing

Awesome guide, thanks a lot!
I have a question, if i want to install some patches and fixes throgth TWRP, is necessary to change the slot before reboot?

LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
Click to expand...
Click to collapse
Is this using some kind of Magisk based stuff to install or something because between this and the Force-enc disabler zip linked in this thread, something is causing my banking app to think my phone is rooted even though it isn't. I'd rather avoid having to install magisk purely for the sake of making my bank app work properly, so what's with this?
EDIT: well, I installed magisk anyway and got safetynet passing + magiskhide set up but the bank app still thinks im rooted so rip me i guess
EDIT 2: "Back in March of 2020, Google made some changes to SafetyNet that permanently trips when your bootloader is unlocked no matter what you do." welp,

Wher can I find "TWRP A/B Retention Script" in Magisk?
There is a new Design with no Download Selection.

[Guide] Root Pixel 4 XL with Magisk Android 13

[Guide] Root Pixel 4 XL With Magisk Android 13
Android Security Bulletin—Feburary 2023
Pixel Update Bulletin—Feburary 2023​
Introduction
This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 4 XL phone with an unlocked bootloader.
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.​
b. Update Platform Tools, regularly, for optimal performance.​
c. Need Google's USB Drivers for your Pixel Phone?​
NEW
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Update(s)
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
Note: If you are using a Custom Kernel, please update using the method in the OP, Index, 4. Install/Update Factory Image keep data or wipe data, • Flash Factory Image Keep Data
Google Pixel 4 XL ROMs, Kernels, Recoveries, & Other
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
bradical711 - Instructions to Pass Safety Net
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot/init_boot.image from the Factory image:
Extract the Factory Image file that you downloaded (coral-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-coral-aa9a.999999.999.zip) into a folder. The stock boot/init_boot.img file should be in this folder.
Patch the boot/init_boot.img:
Open the Magisk Alpha/Beta/Canary/Delta/Stable App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot/init_boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume button up once. The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Run the following command: adb devices check that your device shows up with "sideload" next to its name.
Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type:
adb sideload coral-ota-tq3a.230605.012-f32168af.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should appear on screen.
Access the recovery menu:
Hold the Power button and press Volume up button once.
The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option on the recovery text menu.
[*]Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: adb sideload coral-ota-tq3a.230605.012-f32168af.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash boot/init_boot.img to root
On the phone: Boot bootloader/fastboot mode
Connect the phone to the Computer with USB cord.
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot/init_boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Notes:
This slot is bootable and rooted. The other slot is bootable without root.
Check that the other slot is bootable and not rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
To return to the other slot that is bootable and rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
Done!
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
Flash boot.img
Flashing the boot.img removes root.
Copy/Move the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Pass SafetyNet with Magisk module.
Pass Safety Net with SafetyNet Fix Magisk Module
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread or Try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 4 XL ROMs, Kernels, Recoveries, & Other
Themes, Apps, and Mods
Google Pixel 4 XL Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.

U da man Homeboy76. Really appreciate all the work you did putting this together. Thanks.

fastboot flash boot magisk_patched.img.--slot all
i have to remove the period after the patched.img. if not i get a no such file in directory

mikepopo99 said:
fastboot flash boot magisk_patched.img.--slot all
i have to remove the period after the patched.img. if not i get a no such file in directory
Click to expand...
Click to collapse
:good:

Worked like a charm for me. I did a clean a clean install. No issues. Just like flashing a monthly update.

Bootlooping
no matter what I do I keep bootlooping. I'm doing everything on the instructions list. IM trying to root android 11 on my pixel 4 xl. I just flashed the update with the flash all and wiped everything. But when i try to root it gets stuck at the google logo. i have the Magisk Canary Channel installed and patched the boot image and everything. I get the no valid slot to boot in the bootloader.

mikepopo99 said:
no matter what I do I keep bootlooping. I'm doing everything on the instructions list. IM trying to root android 11 on my pixel 4 xl. I just flashed the update with the flash all and wiped everything. But when i try to root it gets stuck at the google logo. i have the Magisk Canary Channel installed and patched the boot image and everything. I get the no valid slot to boot in the bootloader.
Click to expand...
Click to collapse
Curious
- SDK Platform-tools r 30.0.4?
- What slot did the September 2020 Factory image flash to?

I'm not sure what slot. But yes I am using the newest platform tools. How can I check. I just did the flash all script from Google and did a clean install.

mikepopo99 said:
I'm not sure what slot. But yes I am using the newest platform tools. How can I check. I just did the flash all script from Google and did a clean install.
Click to expand...
Click to collapse
Check: Boot fastboot mode (#1 in the guide) see boot slot.

Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?

Utini said:
Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?
Click to expand...
Click to collapse
I recommend clean flashing.

Utini said:
Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?
Click to expand...
Click to collapse
I would never try to tell anyone which way is the correct way since opinions vary. Having said that, I updated without the -w and have had zero problems thus far. However, I would take all necessary precautions as usual:
1. Update your platform-tools.
2. Remove/disable all magisk modules.
3. Remove your face unlock before starting.
4. You'll need to be on the latest canary magisk if you want to root.
5. If you patch your boot.img, make sure the finished image is 32.55 mb. I personally patch the new boot.img before even starting the update process so it's ready to go.
Again, this is how I like to update my device, and is not the be all end all method that others may like to use. Best of luck to you no matter which method you may choose to use. :good:

Badger50 said:
I would never try to tell anyone which way is the correct way since opinions vary. Having said that, I updated without the -w and have had zero problems thus far. However, I would take all necessary precautions as usual:
1. Update your platform-tools.
2. Remove/disable all magisk modules.
3. Remove your face unlock before starting.
4. You'll need to be on the latest canary magisk if you want to root.
5. If you patch your boot.img, make sure the finished image is 32.55 mb. I personally patch the new boot.img before even starting the update process so it's ready to go.
Again, this is how I like to update my device, and is not the be all end all method that others may like to use. Best of luck to you no matter which method you may choose to use. :good:
Click to expand...
Click to collapse
A second opinion is good.

Any tricks to getting Safetynet to pass? I did a clean install and build updated everything and safetynet is still failing.
Thanks all.

great guide! i almost messed up bad when i flashed first time it froze up and stalled i realised my ssd main drive ran out of space. freed up some space and retried and all worked great! (its a lot bigger than i thought when installing)

Great guide. Boot image is patched and flashed on Android 11.
I can't pass SafetyNet however. Is anyone on Android 11 and passing? Any tips?

madmaverickmatt said:
Any tricks to getting Safetynet to pass? I did a clean install and build updated everything and safetynet is still failing.
Thanks all.
Click to expand...
Click to collapse
ucantescape1992 said:
Great guide. Boot image is patched and flashed on Android 11.
I can't pass SafetyNet however. Is anyone on Android 11 and passing? Any tips?
Click to expand...
Click to collapse
Safetynet
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

Post deleted!

So, I've been out of the flashing game for a long minute but I had to do something about all the ads I was getting. Blockada seemed to work okay but always left something to be desired. I missed Adaway, so....
I had a hard time getting Magisk installed in Android 11 on my Pixel 4xl. I followed this well written tutorial to a tee but when I flashed magisk_patched.img to boot, then "fastboot reboot," it would kick me back to fastboot after the "G" screen and spit out the error "no valid slot to boot." Three times in a row after clean flashing the factory image too!
I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work.
I did not take the OTA update if it matters. I had intended to wipe the device with a clean install of Android 11, then Magisk (just for ad blocker) from the get so, I'm guessing slot b wasn't used? I'm honestly not really sure how it works.
Even then though, I had some trouble getting the order right from flashing the factory image to being rooted, so this is also what I found.
First, unlock the bootloader of your device, then clean install Android 11 and get it set up. Download Magisk manager canary, then adb push the boot.img from your computer to your device. Use Magisk manager to patch it, then adb pull magisk_patched.img back to your computer. From there, fastboot flash boot your magisk_patched.img and you're golden. Fastboot reboot should put you back in to Android and then Magisk manager will recognize root.
I had tried several times to use a boot.img I had already patched some days earlier but it never seemed to work. It would boot okay, once I figured out not to "--slot all," but Magisk would never recognize it was rooted unless Magisk manager patched it and I flashed that particular patched file. If I tried to flash any other patched file, Magisk manager wouldn't recognize root. Even recently patched boot.img's that were flashed to the device (not the days old one I had pre-prepped) wouldn't work. Magisk manager only seemed to recognize patched boot.img's that were made by it in that particular install. If I tried to use a boot.img from any other Magisk Manager install it wouldn't recognize it. Weird? I dunno, but, I got it up and running!
Thanks Homeboy76 for making this tutorial. Without it I would have been lost. :good:

TheDiabolicaL1 said:
...I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work... :good:
Click to expand...
Click to collapse
@TheDiabolicaL1
Thanks for the kind words.
Glad you got it working and, thanks for posting this information: fastboot flash boot magisk_patched.img
It provides an alternative method of flashing the magisk_patched boot.img for the members getting boot loops.
However, fastboot flash boot magisk_patched.img --slot all does work without boot loops:
C:\android-sdk_windows\image-coral-rp1a.200720.009\platform-tools_r30.0.4-windows>fastboot flash boot magisk_patched.img --slot all
Sending 'boot_a' (33336 KB) OKAY [ 0.234s]
Writing 'boot_a' OKAY [ 0.326s]
Sending 'boot_b' (33336 KB) OKAY [ 0.234s]
Writing 'boot_b' OKAY [ 0.335s]
Finished. Total time: 2.509s

[UPDATE/KEEP ROOT GUIDE] FEB 2021 (RQ1A.210205.004) "CORAL" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ1A.210205.004, Feb 2021"!
Magisk v21.4 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145727319
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145727317
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145727318
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.210105.003, Jan 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.210105.003-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145709335
coral-rq1a.210105.003-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145709334
February 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq1a.210205.004-8fe8685c.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.210105.003-factory-boot.img
3. fastboot flash dtbo coral-rq1a.210105.003-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq1a.210205.004-8fe8685c.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq1a.210205.004-magisk_patched-21.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
** As of newer Magisk builds, you can just try booting up in safe mode, which should disable Magisk and allow you to disable whatever needs to be disabled. Haven't needed to try it yet, so I can't go into more detail, but I would recommend trying that instead.

thank you for prompt updates! I use your guide and files every time

Used your files and it worked without a problem. Thank you very much

this method no longer works after i use a new windows installation. All seems normal except phone gets stuck in "Phone is starting" and i have to format userdata for it to work again.
It was working previously and i use the same magisk modules. Ill try from ubuntu next month
Maybe someone could know whats causing the issue because i did not missflash anything and all files were downloaded properly. Im pretty sure its windows but who knows lol

fuarkgl3 said:
this method no longer works after i use a new windows installation. All seems normal except phone gets stuck in "Phone is starting" and i have to format userdata for it to work again.
It was working previously and i use the same magisk modules. Ill try from ubuntu next month
Maybe someone could know whats causing the issue because i did not missflash anything and all files were downloaded properly. Im pretty sure its windows but who knows lol
Click to expand...
Click to collapse
I would check that you're using latest adb / fastboot (Google's Android SDK platform tools) and Google USB drivers, and that when your phone is in bootloader mode and plugged in, Windows' Device Manager shows it as the correct type of device (Portable Devices -> Pixel 4 XL). You may need to update drivers and manually install the Google USB driver package over that device.
Also, maybe bad download, try another cable, etc the usual stuff. And sorry for the late response. =)
edit: oh, and also you can get conflicts if you have other adb / fastboot sets installed. For example, the "minimal adb fastboot" package, or HTC Sync Manager, they may install their own adb / fastboot binaries and set their paths into your environment variables. I know you said new Windows installation, but I figured it was worth mentioning anyway.

So I can do all this just fine, my issue is I can't pass safetynet and I feel like I'm missing something simple. Anyone care to writeup or point me in the direction explaining to a 5 year old (well, one born 40 years ago) how to do the magiskhide deal today? My bank apps and everything work - except for hulu (so even just a modded apk would do.

No need for MagiskHidePropsConfig anymore. Just flash this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.1.1
If you have Xposed installed, you'll have to make sure to enable pass safetynet mode (basically just blacklists certain Google apps from Xposed hooking).

Thanks again @i5lee8bit for this guide!
I updated to the latest February patch alllll the way from Android 10, August 2020 security patch!
It took a couple of hours but everything went smoothly.

Essential Phone PH-1 Daydream support

Hello everyone,
Lately there has been lot talking about Facebook Meta, Virtual reality and stuff like that. I decided I also wanna try some VR experience, so I bought headset for 30 bucks, took my old mata lying around and got Daydream, nowadays unsopported but very good vr platform, working on this phone.
Daydream was interduced alongside first Google Pixel and died with Pixel 3. There wasnt many phones on the market wit official support which caused platform to die. But thanks to our skilled guys, we can enjoy it on pretty much any device.
Im using my PH-1 as a 360 cam so my guide will be showing how to get this working on latest stock firmware.
1. Install adb/fastboot tools
Guide here
2. Unlock bootloader and critical partition ( just to be able flash full firmware in step 5)
You can watch guide here
3. Download necessary files
Download stock factory images from here
And magisk manager app from here
4. Ensure youre on build number QQ1A.200105.032, if you are skip to step 6
5. Updating to latest firmware
Extract downloaded factory images, reboot phone to bootloader mode and doubleclick flashall.sh
Newest firmware should be flashed in a few minutes. then reboot the phone.
6. Rooting the phone
Copy magisk.apk and boot.img from factory images folder into your phone storage.
Install magisk app, open it and click install, select and patch file and choose boot.img you moved to your phone.
Move patched boot image back to your PC
Reboot phone to bootloader mode once again
Flash patched boot.img via command fastboot flash boot_a /location.of.your.file repeat for second slot fastboot flash boot_b /location.of.your.file (some of you may have to use command fastboot flash:raw boot_a). Then reboot the phone.
7. Setting up magisk
Magisk manager should appear in your menu. Open it and it will install its full app. After opening newly installed magisk, phone will restart and magisk will be fully installed.
8. Unlocking Daydream.... finally
Open magisk
Switch to modules (bar at the bottom of screen)
Search for Pix3lify and click install
During installation choose Slim installation otherwise you will end up on bootloop
Restart the phone
9. Fixing Library resolution
Open magisk once again
Open modules
Pick install from storage
Install this module
Restart the phone
10. And thats it, daydream should appear in your google play store after a while. If not just sideload it from apkmirror, but everything should be working nicely.