Database Info

[GUIDE] Install Magisk with proper support for OTA updates

Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Here's an alternative method to install Magisk that support OTA updates (copied from the Mi A1 forum and expanded )
You need a PC with Android platform tools (they exist also for MacOS and Linux). When using Windows, you should also install MiFlash tool to get the required drivers to recognize the device.
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options" (on Andoird 9 "About phone" is right at the top of the Settings app).​2. Go back to the previous page (i.e. Settings > System), where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).​3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen You can also use the command "adb reboot-bootloader" if you already connected the phone to the PC.​4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.​
Now you unlocked your phone's bootloader and can continue to the next section.
MAGISK INSTALLATION
5. Download and install on the smartphone the latest version of Magisk Manager's apk available.
You need the smartphone to be connected to the internet, because Magisk won't install and won't work properly without a connection.​
6. Now you can easily download an already patched boot.img from the following list and jump straight to point 10 of this guide, or you can continue to the next point and learn to patch yourself an original boot.img
If you choose the short way, be sure that you select the patched_boot.img with the same "Build number" currently installed on your phone (see point 1 of this guide), and don't flash the file directly on the phone memory, because Magisk will not work properly (do exactly what this guide says, and you will not find problems, hopefully).
For our convenience, extract the patched_boot.img file in the same directory where Android platform tools are located.
patched_boot 9.6.4.0 (2018 July update) - patched with Magisk 17.1
patched_boot 9.6.6.0 (2018 August update) - patched with Magisk 17.1
patched_boot 9.6.8.0 (2018 September update) - patched with Magisk 17.1
patched_boot 9.6.9.0 (2018 October update) - patched with Magisk 17.1
patched_boot 9.6.10.0 (2018 November 1st update) - patched with Magisk 17.1
patched_boot 9.6.11.0 (2018 November 2nd update) - patched with Magisk 17.1
patched_boot 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - patched with Magisk 18.0
patched_boot 10.0.3.0 (2019 January update) - patched with Magisk 18.0
In case you erroneously flash those patched files directly on the phone, flash back the original boot.img via fastboot and follow the guide:
original boot.img 9.6.4.0 (2018 July update) - taken from fastboot ROM
original boot.img 9.6.6.0 (2018 August update) - taken from OTA update
original boot.img 9.6.8.0 (2018 September update) - taken from OTA update
original boot.img 9.6.9.0 (2018 October update) - taken from OTA update
original boot.img 9.6.10.0 (2018 November 1st update) - taken from OTA update
original boot.img 9.6.11.0 (2018 November 2nd update) - taken from OTA update
original boot.img 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - taken from fastboot ROM
original boot.img 10.0.3.0 (2019 January update) - taken from fastboot ROM
7. You need the original boot.img to patch. You can find it inside the official fastboot ROM zip for daisy. Check that the downloaded ROM version is the same as the "Build number" currently installed on your phone (see point 1 of this guide). If the versions are different, update (or downgrade if possible) your phone to that version. You can also download original boot.img elsewhere (for example at the point 6 of this guide), but always pick the same "Build number" of your phone.
After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).​
8. Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you get on the point 7 of this guide.​
9. Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, inside the same folder where the Android platform tools are located, for our convenience.​
10. Reboot the phone in fastboot mode (as already explained in point 3 of this guide), open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
fastboot boot patched_boot.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.​
11. Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates". From now on, you should check manually if a new OTA update is available.​
Now the installation is finished, you can use Magisk Manager to install modules and manage root permissions.
HOW TO APPLY OTA UPDATES
UPDATE 9 February 2019 It seems that with the latest Magisk (v18.1) and Magisk Manager (v7.0.0) the following procedure is working fine again. I didn't test it personally, but some users gave positive feedback.
WARNING! January 2019 Since the arrival of Android 9 Pie, the OTA update with Magisk as described in the following section, doesn't seem to work anymore. It could work, but you could also get a bootloop with the risk of losing your data.
Before upgrading from Android 8 to 9, or doing an OTA update after Android 9 you should:
- backup your data;
- remove any lockscreen password or fingerprint;
- uninstall totally Magisk and reboot.
If after doing this you get a bootloop, you could try to manually flash the vanilla boot.img via fastboot on the current slot (the same version as the last installed OTA). If you managed to fix the bootloop you can then install Magisk anew, from step 5 of this guide.
If the phone wants your PIN or password to proceed after the OTA update or after fixing the bootloop, and your PINs or passwords doesn't work, then you could have to reset the phone (or erasing the data partition, that should be the same thing), losing all your data.
Last chance if everything fails, you can flash the latest fastboot ROM from the official Xiaomi site and the phone will be working again.
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.​
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.​
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".​
After the reboot you will have the updated Android version with Magisk already working.
Thanks to user @jashancheema for the Mi A1 guide and a bigger thanks to @topjohnwu for the OTA part and above all for developing Magisk.

TROUBLESHOOTING
WARNING: before attempting any of the following operations, you must disable any screen lock, PIN or password, because you risk to not get back your data (encryption issues). It is recommended to take a backup, too (as every time a custom modding is involved).
You can get errors when installing OTA updates if you didn't follow meticulously the guide.
Check this list to try to find where the problem lies:
- when a new version is found, the updater will check if all the partitions on the device are untouched. If there is a partition that has been modified, the OTA updater will not proceed with the installation;​- typically, the two partitions commonly modified by user modding are the boot partition (that's where Magisk and TWRP are installed) and the system partition (when you change a config file, add or remove a system app, etc.);​- a system partition modified only by using Magisk modules is effectively untouched, because Magisk register all changes to /system in a file in the /data partition and then trick Android to believe those changes are really applied to /system;​- boot partition instead is really modified, but if you install Magisk following this guide, Magisk will save a copy of the untouched boot partition, and restoring it before applying OTA update will make the update work.​
Now, if you didn't follow this guide to install Magisk and you installed it in other ways, Magisk could alert you that he cannot restore the original boot.img (the boot partition) when you try to apply the OTA update.
To fix this, you can flash directly the vanilla (original, unmodified, untouched) boot.img taken from the point 6 of this guide, using those commands:
Code:
fastboot getvar current-slot
fastboot flash boot_? boot.img
the first command will tell you what is the current slot in use (a or b), the second command will flash the original boot into the phone, but you have to change the "?" in the command with a or b (i.e. the current slot that the first command provided).
Remember that the boot.img file version must correspond to the Android build version currently running in your phone.
If the OTA update will still refuse to apply, probably you changed something directly in the /system partition (for example you changed something in the build.prop without using a Magisk module to do this).
In this case you have to flash the original system.img in the phone with those commands:
Code:
fastboot getvar current-slot
fastboot flash system_? system.img
and as before, the first command will tell you the right slot to use instead of the "?" in the second command.
Here you can find the system.img extracted from the OTA updates zip (along with every other .img file inside that):
9.6.6.0 (August 2018) OTA update dump as .img files
9.6.8.0 (September 2018) OTA update dump as .img files
9.6.9.0 (October 2018) OTA update dump as .img files
9.6.10.0 (November 2018) full fastboot ROM
9.6.11.0 (November 2018) OTA update dump as .img files
If you want to obtain the system.img by yourself, you can find it inside the fastboot images but usually they are not updated monthly like OTA updates. But you can extract the system.img directly from the OTA update zips found in this thread (as I did above with my dumps), using the Python scripts found here.
To make the Python scripts work in Debian/Ubuntu and derivatives, you have to download both "extract_android_ota_payload.py" and "update_metadata_pb2.py", give them execution property and then install the package "python-protobuf". After this you can give this command to unpack the payload.bin file (that you must extract from the OTA update zip):
Code:
./extract_android_ota_payload.py /path/to/payload.bin
This will extract in the current directory all the .img files inside payload.bin, including the system.img
I don't know how to proceed in Windows, probably you only need to install the latest Python2 release and the script will work.​
As the last resort, you can flash directly with MiFlash the latest fastboot image available (even if older than your current version). Use the "flash_all.bat" script but before take a backup of your data, because the phone will be fully reset.
If you don't want to take the risk of not doing a backup, use the script "flash_all_except_storage.bat" when flashing, so you will keep all your data, but be warned that sometimes you will not be able to access the data anymore, because of encryption problems.
Right after the flash, you can start following the guide from point 5 or 6.
It should not be a problem downgrading the build version via fastboot, as long as the Android main version remain the same (Oreo 8.1 at the moment).

Thx, nice work :good:

Thanks to the OP. Great post! Totally noob friendly guide. Nice work.

It should also work on mi a2, thanks!

Lione2 said:
It should also work on mi a2, thanks!
Click to expand...
Click to collapse
Sure, but you can't use the posted patched_boot.img, because they're designed for Mi A2 Lite (daisy) and not for Mi A2 (jasmine).
EDIT: I posted the patched and original boot files for Mi A2 jasmine in the second post. I don't know if I can make a thread in the Mi A2 forum section with an adapted copy of my guide, there are already two guides there (even if not polished like this) and I don't want to create more confusion with a third guide about the same argument...

i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?

krzygaj said:
i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?
Click to expand...
Click to collapse
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.

BubuXP said:
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.
Click to expand...
Click to collapse
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?

krzygaj said:
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?
Click to expand...
Click to collapse
You tampered the system partition? Try flashing also the system.img in that case.
Another case could be that you made an OTA update from the June build to July: in this case the partitions on the other slot (probably only the boot partition) where lost when overwrited with fastboot (and cannot be restored, as we don't have any June build ROM or OTA).
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk, but I suggest after installing Magisk so you can test if the guide works fine).

BubuXP said:
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk).
Click to expand...
Click to collapse
Thanks above worked :good:
Hope the next update will go smoothly

September?

When booting comes a warning message because of the unlocked boot loader. How can I disable this message?

PC295 said:
When booting comes a warning message because of the unlocked boot loader. How can I disable this message?
Click to expand...
Click to collapse
you can't turn that off with open bootloader

Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?

proton242 said:
Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?
Click to expand...
Click to collapse
No

ConradB said:
No
Click to expand...
Click to collapse
ConradB you have some suggestion? Thank you

proton242 said:
ConradB you have some suggestion? Thank you
Click to expand...
Click to collapse
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.

BubuXP said:
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.
Click to expand...
Click to collapse
Ciao BubuXP, provando a rimuovere Magisk (lasciando il bootloader sbloccato) tutto torna alla normalità, cosa dici, crea casino quando patcha il boot.img?

[Umidigi One Max] Custom ROM, Modding, Rooting - Complete guide

Welcome to this guide, where I will guide you through rooting, flashing custom roms, and more, on our little Umidigi One Max !
WARNING : I am not responsible for your phone breaking or exploding during the night under your pillow. Please advice. If you cannot boot anymore, keep reading, your phone is NOT dead.
OFFICIAL ROM (Android 8.1)
The Umidigi One Max comes with Android 8.1 Out of the Box. Manufacturer has no plan on having 9.0 on the phone. That's why we root then ! Let's get into it.
Rooting the phone without unlocking it, or installing TWRP
Everything you'll do on this phone will NOT require a bootloader unlock. Note that this method is only in case you don't want to have your data wiped, or don't have access to an SD card (thus you cannot flash .zip in TWRP, except for ADB Sideloads)
What you'll need
Download the latest ROM from Umidigi's website : https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
Choose the ".rar" file
"E" ROMs are for European versions. It doesn't really matter what you choose.
Download SP Flash Tool on the same thread you opened for the ROM. It's "SPFT" for short
Unzip both
Install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/releases/
Steps
IMAGE COURTESY OF bencebacsi @ Umidigi forums
In the unzipped ROM folder, find boot.img
Copy it to your phone storage using an USB cable or any other method
Open Magisk Manager, press install
Choose "patch boot image file"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let magisk do it's job
Find the boot.img file you just copied
Copy the patched_boot.img back to your computer
Open SP Flash Tool
Open the "Download" tab
In "Scatter-loading file", press the folder icon and browse to the downloaded ROM folder. Choose the only file that shows up
Untick every box except for boot. There is a column called "Location" with a path, click on it to change to file.
Choose patched_boot.img
MAKE SURE YOU UNTICKED EVERYTHING EXCEPT BOOT
Click the "Download" button
Turn off your phone (not reboot) and connect is via USB
wait for the flash to succeed. Once done, unplug, boot, voila ! You got magisk !
Credits to topjohnwu for Magisk, what a great piece of work
Installing TWRP
Note that if you want to access the /data partition (internal storage), you'll have to wipe it ! If you do not need it, keep going, it won't wipe unless you want to.
What you'll need
Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html
Magisk.zip installer (NOT the manager) : https://github.com/topjohnwu/Magisk/releases/
SP Flash Tool : http://www.mediafire.com/file/wxlld9dfywk67jl/SP_Flash_Tool_v5.1916.rar/file
This method is shorter and requires less downloaded files.
Steps
Turn off your phone
Run SP Flash Tool
Load the scatter file (see pictures above) you downloaded from the latest ROM (see above as well)
Untick everything except recovery
Change path to recovery.img to be the TWRP image
Click "Download" and plug your phone
After it's done, unplug, and press Power + Vol Up
You'll see three options appearing. That's how you'll get to the recovery. Use Vol Up to scroll, and Vol Down to select. Choose Recovery Mode !
TWRP should boot by now
EXTRA STEP : Make /data readable. You will need to format data (YOU'LL LOSE ALL YOUR DATA) (Wipe > Format Data > Type "yes") and after that, flash this zip : https://androidfilehost.com/?fid=1322778262904004415
You can now proceed to flash zips, including Magisk.zip. If you made /data readable, you can send it to your internal storage. If not, use an SD CARD or ADB PUSH / SIDELOAD.
Returning to stock to fix issues / brick
Use SP Flash tool but instead of unticking everything, tick everything. Note that USERDATA, if ticked, will clear your data.
Ticking only certain partitions may work if you got issues with magisk or system mods and are still on Official ROM. Flashing boot and system will remove Magisk. If you are on custom ROM, you can flash their system again to fix issues as well. Make sure to choose the right system.img in SPFT !
OTHER ROMS
Installing GSI (Generic System Image) to get Android Pie 9.0
GSI takes advantage of Project Treble to create one system image that will work on most devices without issues due to a separate "vendor" partition. The One Max is Treble-compatible, but only up to 9.0 (No 10 Q for now)
This will allow you to get an AOSP experience, with it comes easy modding and theming, and less bugs, less chinese-spying (that's a thing apparently, but who cares really ? Not me to say the least)
GSI List
You can find a GSI List including bugs and download links in my other thread here : https://forum.xda-developers.com/android/development/gsi-gsi-experiments-t3941194
WARNING : DOWNLOAD GSIs WHICH ARE ARM64-AONLY AND NOT AB !
Installing a GSI
You will need TWRP Installed. Check above if it's not done yet. You'll also need the Magisk.zip, and I highly recommend you getting the disable-force-encryption zip
Start up by wiping /data in twrp (Wipe > Swipe the bar). It will not wipe the files in your internal storage (Music, Download, etc...). If you want to get access to /data in TWRP (which I highly recommend), you'll need to do a full format (Wipe > Format data > type yes).
Download a GSI (.img) and send it to your phone (Either using an SD Card, or adb push [file on computer] [destination folder]). Send Magisk and the disable-force-encryption zip at the same time.
Flash that system image using Install > Install Image > Browse to the .img file
Flash disable-force-encryption if you formatted /data (don't flash it if you didn't do that !)
Flash Magisk.zip
Reboot and profit !
Note that there might be some issues with the GSI you choose. Most GSI suffers issues regarding Wifi Tethering/Hotspot. Other than that, check for my thread for issues regarding GSIs.
Some GSI require installation of GAPPS (Google Apps). Download a GAPPS zip and flash it at : https://opengapps.org/ (Choose ARM64 and 9.0)
If Installation fails, saying that system size is too small, go to (Wipe > Advanced Format > Tick "System" > Repair or change file system > Resize File System) and try flashing again.
INTERESTING MODS FOR ALL ROMS
Magisk FDE.AI
A great system manager. Saves a ton of battery without a performance hit. You need magisk installed. XDA Thread : https://forum.xda-developers.com/apps/magisk/beta-feradroid-engine-v0-19-ultimate-t3284421
Fix SafetyNet not passing on custom ROMs/GSIs
SafetyNet will not pass by default on custom ROMs / GSIs.
Use Magisk Hide Prop Config : https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Run 'su' then 'props' in a terminal emulator. Edit Device fingerprint, choose Pick a certified fingerprint. I recommend using Xiaomi Redmi Note 7, as it changes the status-bar to be notch sized.
Note that you may need to do this next fix to make 'su' work :
Root request not working with Magisk
On some GSIs, root requests will not show up. You need to move some vendor files over to system.
Use TWRP's File Manager (Advanced > File Manager) or Adb shell to copy theses files :
Code:
/vendor/lib/libdirect-coredump.so
COPIED TO
Code:
/system/lib/libdirect-coredump.so
Code:
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
This will fix this issue until GSI / ROM creator fixes it in their ROM;
Enjoy your new phone ! Don't forget to say thanks to all the developers behind every project (not me ! I didn't do anything )
If you have any issues, feel free to ask questions !
See you on the other side

Downloaded phhusson's AOSP ROM
Extracted compressed image. Then...
Wiped Phone from TWRP w/ all three options Swipe, Formatted (Type "Yes"), and advanced wipe.
From TWRP went to:
Install > Install Image > Selected system-arm64-ab-gapp-su.img > Select Partition to flash image
From this screen it lists these partitions for selection:
-recovery
-nvram
-uboot
-boot
-logo
-tee
-System Image
I select System image. It starts flashing. After it has finished, I go to reboot, and that is when TWRP states "No OS installed".
Am I downloading the wrong image file?
*********************EDIT****************************
Nevermind. I downloaded system-arm64-aonly-gapps-su.img.xz and it boots fine with gapps included

Exactly, you downloaded A/B image, not A-only.

Using phhusson's AOSP ROM. I got the root requests show up. However the superuser app is blank. Nothing shows in the list.

Request for a video to install GSI
Hello
I'm using Umidigi One Max Android 8.1 and want to upgrade to 9.0 . Can you please make a YouTube video showing how to install the GSI version I'd gladly appreciate it.

Over the last month or so, I've tried multiple GSI ROMs, and stock. I've rooted stock, and everything runs nicely, I just can't stand the lack of features. Even rooted on stock, Google Pay still works. If I install a GSI ROM like Havok, root it, gpay will not work. Not sure why it works on stock rooted with magisk, but not with other ROMs.
I'm looking for a hacked stock rom for the one max that:
A.) Can be rooted.
B.) Can still run gpay.
C.) Has a advanced restart option to boot directly into recovery.
D.) Displays the battery in the status bar as a percentage rather a symbol, and a clock with seconds option.
If I had those options, I would stick with stock. I can accomplish all those options with Havoc GSI ROM, I just can't get NFC/gpay to work.

su
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works

@ _cab13_
thanks for tutorial
some comments/questions
Image shows MT6739 in phone image and scatter file of mt6739
My phone is MT6363 and appears to agree with online specs site such as
https://www.gsmarena.com/_umidigi_one_max-9525.php
Am I looking at the wrong tutorial or umm have you grabbed images from another phone and forgot to say so?

w1lh3lm3d said:
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
Click to expand...
Click to collapse
You have to mount the folder system and vendor for reading and writing and you can copy it, this is in recovery mount

Very helpfull, thanks)

Has anyone tried dual SIM and SD hack on this phone? I cant get my to work. When I do the hack, phone does not see any sim cards nor SD card.
However if I put only two sims, or sim and SD everything works well.
It is almost like issue w Samsung but no warning message

can i use this process on umidigi one as well
q1. Can i use this process on umidigi one as well?
When i visit "Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html" and search on devices they don't have umidigi one or one pro only the one max option. Other than screen size all three are pretty much spec'd the same. The umidigi one just doesn't have wireless charging or nfc that one pro and one max have and one max has 6.3 waterdrop vs one/one pro 5.9 notch display but all 720x1520 9:19 aspect ratio configurations. I found a umidigi one and one pro twrp recovery image here _https://unofficialtwrp.com/umidigi-one-umidigi-one-pro-root-twrp-recovery/ so if i have that are all the other downloads for doing non-rooted device upgrade to 9 pie non-device specific downloads?
q2. Nice to see this process covers a way to get form 8.1 to 9 w/o rooting device. Having never done so i'm curious why other search hits cover steps that require rooting device if the upgrade can be achieved without doing that, any insights?
q3. Would you say the likelyhood of bricking my device, if trying to follow these instructions using umidigi one vs one max, very low? Trying to determine if i should first line up and have on hand backup phone to use if the chance of that happening is high.

does magisk install allow me to upgrade to android 9 pie?
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?

myusrn said:
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
Click to expand...
Click to collapse
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.

drkiro said:
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
Click to expand...
Click to collapse
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?

myusrn said:
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
Click to expand...
Click to collapse
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.

drkiro said:
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
Click to expand...
Click to collapse
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?

myusrn said:
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
Click to expand...
Click to collapse
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

drkiro said:
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.

myusrn said:
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
Click to expand...
Click to collapse
You can return, to the Originate flashing state, this image, https://community.umidigi.com/forum.php?mod=viewthread&tid=18692&extra=page=1 , can experiment with any image and return it to the original state, the pixel experience does not work with this phone, in Android Q the NFC does not work, and the videos in whastapp, do not work. Android 10 image comes without gapps, you have to flash them. If the twrp you can flash it through fastboot

[Guide][Root Magisk Only][OTA Compatible] Moto G6 Play

* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.

Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!

gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.

UPDATING Pixel 5 Factory Image & Re-Rooting

Why This Thread?
I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for anyone who might still be uncertain about "update" procedures, I've followed thie below method twice now with no issues at all,> None of my data was lost and I kept my EX kernel!.
If You Want To Unlock Your Bootloader and Root Your Pixel 5:
This guide takes you step by step through bootloader unlock, using magic to patch the boot image and get your device rooted.
If You're Already Unlocked & Rooted, and Want To Update The Factory Image And Re-Root:
If you're already rooted and want to update to the next factory image, just follow the standard update factory image routine for the Pixel series of devices, then following the below:
After extracting the primary factory zip, and the secondary zip that is created from the first extraction (all done within the platform tools folder with the fastboot app)
Edit the FLASH-ALL file.... keep the -w for a clean install that wipes everything, or remove the -w to keep your data.
This will install the latest factory image and remove root.
Now, follow these steps here, they're perfect. (these are the same instructions for unlocking bootloader, and initial install of Magisk listed above)
If you were previously rooted, and just updating the next factory image, you can skip the entire sections on installing and hiding Magisk manager in the above instructions, (these settings remained in Magisk Manager when I did this).
And you're done!
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
If you know an easier, shorter, more efficient, or UPDATED method, please share it and I'll make the necessary corrections/adjustments

My method is updating via the OTA packages. Similar to using the factory image but no editing of files.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Turn off magisk modules
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #3 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash boot "path to patched boot.img"
fastboot reboot
Turn on your magisk modules and test
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.

l7777 said:
My method is updating via the OTA packages. Similar to using the factory image but no editing of files.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #3" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #2 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash "path to patched boot.img"
fastboot reboot
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.
Click to expand...
Click to collapse
Thank you. Well-written, just a few minor corrections.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #2 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash boot "path to patched boot.img"
fastboot reboot
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.

zeepzorp said:
Thank you. Well-written, just a few minor corrections.
Click to expand...
Click to collapse
Thanks, updated the original.

Thanks for the instructions. I was able to re-root the device, but I couldn't pass SafetyNet Attestation.
My P5 has updated to: 11.0.0 (RQ1A.210105.003, Jan 2021)
I used MagiskHide Props Config (updated) method. which is:
#su
#props
#1 (edit device fingerprint)
#f (Pick a certified finger print)
#7 (google)
#20 (pixel 3a)
#3 (Android version 11)
#y (restart)
The devices rebooted but still, no SafetyNet pass.

hamooz92 said:
Thanks for the instructions. I was able to re-root the device, but I couldn't pass SafetyNet Attestation.
My P5 has updated to: 11.0.0 (RQ1A.210105.003, Jan 2021)
I used MagiskHide Props Config (updated) method. which is:
#su
#props
#1 (edit device fingerprint)
#f (Pick a certified finger print)
#7 (google)
#20 (pixel 3a)
#3 (Android version 11)
#y (restart)
The devices rebooted but still, no SafetyNet pass.
Click to expand...
Click to collapse
Altering the model prop doesn't work for safety net any longer. There is a safetynet-fix magisk module you can use.

l7777 said:
Altering the model prop doesn't work for safety net any longer. There is a safetynet-fix magisk module you can use.
Click to expand...
Click to collapse
I have also flashed Universal SafetyNet Fix but no luck

hamooz92 said:
I have also flashed Universal SafetyNet Fix but no luck
Click to expand...
Click to collapse
I just flashed the safety net fix myself and it worked like a charm.
I also left the magisk config prop module installed (just because)
Are all your other Magisk settings in order (magisk hide, checking all the boxes under GooglePlay , etc.)?

l7777 said:
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
current build number is RD1A.200810.021.A1
zeepzorp said:
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
one the ota site there's only one "EU carrier" images different than the current one: RD1A.201105.003.B1 (NOV 2020). should i use this one or can i also use the this one f.e. RQ2A.210305.006 (nothing specified)

You may find my video helpfu too but it more pertains to installing the DP1 for Android 12, but the update process is practically the same.. For rooting Android 12, it seems we need to disable verity/verification of boot images, otherwise flashing a modified boot img will just boot immediately to fastboot again.

narf0815 said:
current build number is RD1A.200810.021.A1
one the ota site there's only one "EU carrier" images different than the current one: RD1A.201105.003.B1 (NOV 2020). should i use this one or can i also use the this one f.e. RQ2A.210305.006 (nothing specified)
Click to expand...
Click to collapse
In your case yes I'd probably use RQ2A.210305.006.

zeepzorp said:
Thank you. Well-written, just a few minor corrections.
Click to expand...
Click to collapse
l7777 said:
Thanks, updated the original.
Click to expand...
Click to collapse
Thank you, l7777 and zeepzorp. This is also the way I would have done it. Out of curiosity and to reduce manual steps in between, would it work to restore the original boot.img to unroot and then use the normal OTA updates inside Android? Without a spare phone or a TWRP backup I hesitate to try this.
Also, when following the manual update steps, is it safe to skip versions in between, e.g. update directly from January to March versions? In my past 10 years of manually updating ROMs I have never used any OTA update functionality from inside Android and I noticed that the OTA update process, which was performed in mid January 2021 when unpacking the phone, updated the ROM in the following order, each separated by reboots in between:
Shipped version: 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers)
1st OTA update: 11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
2nd OTA update and at that time current version: 11.0.0 (RQ1A.210105.003, Jan 2021)
Why did it not skip the version in between and directly update to the January version?

dhrv said:
Thank you, l7777 and zeepzorp. This is also the way I would have done it. Out of curiosity and to reduce manual steps in between, would it work to restore the original boot.img to unroot and then use the normal OTA updates inside Android? Without a spare phone or a TWRP backup I hesitate to try this.
Also, when following the manual update steps, is it safe to skip versions in between, e.g. update directly from January to March versions? In my past 10 years of manually updating ROMs I have never used any OTA update functionality from inside Android and I noticed that the OTA update process, which was performed in mid January 2021 when unpacking the phone, updated the ROM in the following order, each separated by reboots in between:
Shipped version: 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers)
1st OTA update: 11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
2nd OTA update and at that time current version: 11.0.0 (RQ1A.210105.003, Jan 2021)
Why did it not skip the version in between and directly update to the January version?
Click to expand...
Click to collapse
As far as skipping monthly updates, I only update every other month (unless there's a massive update for security) and I've had zero issues. Just updated to March from January, no problems.

I'm having a hard time understanding your instructions. I apologize in advance but, could I get a more detailed list of instructions?

philharmon said:
I'm having a hard time understanding your instructions. I apologize in advance but, could I get a more detailed list of instructions?
Click to expand...
Click to collapse
Follow these instructions, they're pretty much step for step.
https://android.gadgethacks.com/how...ide-for-beginners-intermediate-users-0348101/
They're included in my OP (hyperlinked) as well.
If you have a specific question, just ask!

Az Biker said:
Follow these instructions, they're pretty much step for step.
https://android.gadgethacks.com/how...ide-for-beginners-intermediate-users-0348101/
They're included in my OP (hyperlinked) as well.
If you have a specific question, just ask!
Click to expand...
Click to collapse
Be warned, nothing after step 20 in that guide is valid any longer. Passing safetynet requires a different magisk module.
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com

l7777 said:
Be warned, nothing after step 20 in that guide is valid any longer. Passing safetynet requires a different magisk module.
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Click to expand...
Click to collapse
Which is why the following warning has been written in the OP since Feb 2021:
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.

Has anyone tried the Pixel update and software repair tool
Google Pixel - Update and Software Repair
to go from Android 10 to 11?
Then modify the boot image with Magisk and fastbooting that?
ƒ

Az Biker said:
Which is why the following warning has been written in the OP since Feb 2021:
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
Click to expand...
Click to collapse
That assumes that people read the OP.
biTToe said:
Has anyone tried the Pixel update and software repair tool
Google Pixel - Update and Software Repair
to go from Android 10 to 11?
Then modify the boot image with Magisk and fastbooting that?
ƒ
Click to expand...
Click to collapse
It will almost certainly perform a factory reset in the process.

Just sharing how I do it in case someone is interested in a shorter path:
1. Download the new full factory image
2. Extract the file. Then extract boot.img from the image zip file within.
3. Copy boot.img to your pixel 5
4. Patch it with magisk
5. Move back the patched file, rename it to boot.img
6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)
7. Edit flash-all file by removing -w so it won't wipe your device clean
8. Flash with flash-all
No need to unroot and reroot.

[HOW-TO] Install LineageOS 18.1 on the Google Pixel 3a XL (bonito) w/ Google Apps and Magisk (root)

I've been trying to find a good phone for my wife that is officially supported by LineageOS and settled on the Pixel 3a. If you're thinking of purchasing this device, make sure the listing says that it has an UNLOCKED BOOTLOADER. Just "unlocked" doesn't cut it, you'll probably get a phone that works on any carrier but won't allow an OEM unlock. Third time is the charm, we finally ordered from eBay; the listing said unlocked bootloader, and it was.
I had some trouble getting started so hopefully this will help others. This guide will probably work on the Google Pixel 3a (sargo, not XL), and possibly other Pixel devices as well assuming you adjust your release version appropriate to your model.
Note that TWRP doesn't work well (or at all), and don't even try because the Pixel 3 and newer are slot A/B devices so LineageOS uses their own recovery to manage switching between boot slot A/B during update. (Of course, if you do get TWRP working, then I do prefer it so let me know how!)
Enable developer mode
OEM Unlock: method 1, method 2
Unlock the bootloader:
adb reboot bootloader
fastboot flashing unlock
Install the latest android platform tools for fastboot and adb:
https://developer.android.com/studio/releases/platform-tools
Install the official Android 11:
https://developers.google.com/android/images?authuser=3#bonito
Agree to terms and conditions
Download the latest v11 zip (RQ3A.211001.001, Oct 2021)
Unzip and run:
Windows: flash-all.bat
Linux: ./flash-all.sh
Repeat #3 above if necessary
Download and transfer LineageOS 18.1:
https://download.lineageos.org/bonito
Download the latest recovery .img to your desk
Download the latest .zip to your desk
Install the recovery image:
fastboot flash boot_a lineage-18.1-20211023-recovery-bonito.img
fastboot flash boot_b lineage-18.1-20211023-recovery-bonito.img # (might not need this one)
Reboot to recovery (may need to power off first)
From the Phone: In recovery it should show the LineageOS icon:
Advanced->Enable ADB (may not be necessary)
Apply Update
Apply from ADB
From your desk:
adb sideload lineage-18.1-20211023-nightly-bonito-signed.zip
If you get errors like error: protocol fault (no status) then your version of adb is too old.
It should say Total xfer: 1.00x but the official LineageOS installation docs say that it might hang at 47% and that is ok because it is done transferring to the phone at that point.
From your phone:
If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
If so, then tap Apply Update->Apply from ADB and follow Google Apps .zip install notes below in #7.3
If not, then tap the left return arrow and then tap "reboot now"
Optional ZIPs:
If you are already in recovery, go to step #7.2. Otherwise, get into recovery. If you already booted into LineageOS, then I find it easiest to reboot into recovery by enabling "Advanced Restart" :
Systems->Advanced->Gestures->Power->Advanced restart
Then hold down the power button and select Power->Reboot->Recovery
To install zips:
First mount /mnt/system: Adbanced->Mount/Unmount System
This is necessary because the Pixel is a A/B boot slot device and not all .zip's will know how to mount.
Use adb sideload <filename.zip> as in #6.4 above (but with the .zip you want!)
You may be prompted on your phone to install even though the signature is untrusted.
Download the latest Google Apps for arm64. (Do this before booting LineageOS for the first time!)
Most people recommend MindTheGapps,however:
Because the Pixel is a A/B boot slot device, MindTheGapps doesn't know how to mount /mnt/system so it fails.
This is probably a bug in MindTheGapps, if you find a way to fix it let me know.
Others like OpenGApps.
I installed this one, but for some reason it didn't work the first time. It did the second! Maybe I missed something.
Well Play Store is hanging, so trying MindThe Gapps
Root your device with Magisk:
Download the latest Magisk APK:
Note that the .apk is also a .zip, so rename it if you must (but I didn't need to).
Enable adb
Install the apk:
adb install Magisk-v23.0.apk
Troubleshooting:
LineageOS recovery doesn't like to install multiple zips at once. If you get the error adb: sideload connection failed: closed then click the left back arrow, then again folow steps from 6.4
Try factory reset if you have boot issues the first time

In Step 5, sub-step 3 you typed "Download the latest v11 zip (SP1A.210812.015, Oct 2021)". The latest Android 11 image for bonito is "RQ3A.211001.001, Oct 2021". The image you reference is the new Android 12 image for bonito.

Thanks for catching my copy-paste bug! I've updated the article.