[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G Peregrine Stock to Android 9

[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G Peregrine Stock to Android 9 - Moto G Q&A, Help & Troubleshooting

Pi Dark [substratum] - Apps on Google Play
Android Pie like Substratum Theme 🎨
play.google.com
Default Dark Theme for Substratum - Apps on Google Play
Dark material theme for the Substratum Theme Engine
play.google.com
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G Any version to Android 9 Pie/LineageOS 16
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G/LTE 2013 Peregrine XT1039 Any version to Android 9 Pie/LineageOS 16
Complete guide to install Android 9 on your Motorola Moto G 4G/LTE.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About, make sure it is this model: Motorola Moto G 4G 2013 Peregrine XT1039.
We will only use a USB 2.0 port and a phone fully charged (but USB3 works too).
CHANGELOG
v14. TWRP 3.5, Magisk 22, BitGApps
v13. Rework tutorial (TWRP 3.4 manipulation, latest Magisk)
v12. Latest fastboot binary, TWRP 3.4, USB drivers for 32/64 bits, Magisk root, boot logo and simpler tutorial
v11. LOS 16 2020 Septembre update (thx to @sdembiske)
v10. LOS 16 2020 May update
v9. Updated pack with TWRP recovery 3.3.1-0, fix glitches in tutorial
v8. Moved tutorial for Android 9 and updated pack with TWRP recovery 3.3.0-0 and Addonsu 16
v7. Updated pack v5 with newest TWRP and removed outdated custom kernel, added links for newest ROMs
v6. Added Google Mobile Services (GMS) certification
v5. Added custom Bootlogo flash
v4. Recovery TWRP 3.2.1-0, MD5 signature for kernel and recovery
v3. Custom kernel, overclock, recovery TWRP 3.1.1-0, no /cache in F2FS (bootloops)
v2. Moved to Android 7.1 Nougat
v1. Initial release
1 ) WHAT YOU NEED
- djibe Moto G 4G pack (~20 Mo): http://bit.ly/motoGLTEdjibepackv5
(Contains link to Motorola Bootloader unlock + flashable Bootloader unlocked logo + TWRP Recovery 3.5.0_9-0 + Magisk root + Motorola USB drivers x32/64 + fastboot)
+ ROM LineageOS Unofficial 16: https://forum.xda-developers.com/moto-g/4g-development/rom-lineageos-16-0-t3835030
Download latest build available here: https://mega.nz/file/haBkzLCA#Aw4qZ09cKi5Jqs-p6SiUaDpxD_bMOQ8PzXACT1xKhr0
Want older and stable versions ?
Use this if you want to give/sell your phone to someone.
Grab Lineage OS 14.1 for peregrine here: https://forum.xda-developers.com/t/rom-lineageos-14-1-substratum-for-moto-g-lte-peregrine.3967207/
+ BitGApps ARM 9 R13: https://xiaomifirmware.com/download/16147/
For LineageOS 14.1, use this package: https://opengapps.org/?arch=arm&api=7.1&variant=pico
+ a microSD card formatted in FAT32 : copy ROM, GApps, Magisk and logo.zip on it.
You can chose another boot logo from this collection: https://forum.xda-developers.com/showthread.php?t=2686441
And download the file according here: https://androidfilehost.com/?w=files&flid=49201
2 ) INSTALL DRIVERS
Install Motorola 64 bits drivers (32 or 64 bits depending on your Windows version).
Then plug Moto G to PC and let the install go on.
3 ) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4 ) UNLOCK BOOTLOADER
Update your Moto G to the latest official Android 5.1 Lollipop.
In Android, go to Settings > About > Updates. Make sure you have latest version.
Then, go to Motorola website (shortcut in my archive or right below):
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b[/URL]
Subscribe using your Google Account or email.
Shut down phone.
Power it on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
Screen is black with lines of text, starting with AP Fastboot Flash Mode (S).
Connect phone to USB2, wait for fastboot drivers to install.
In Windows, select the /flash subfolder you unzipped from my archive.
On keyboard, make a combo Shift + right click -> Open command windows here.
Write this command in Windows terminal :
Code:
fastboot oem get_unlock_data
confirm using Enter.
Command sends back a message like this :
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
OKAY [ 0.146s]
Select all text -> right click -> select all.
Open a notepad editor, and paste text.
Rework the text to get it on 1 line, and remove all spaces and "(bootloader)" messages.
It should look like this : 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Now, copy this text line and paste it in Motorola website : https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Below, click on Verify Eligibility.
Next, I Agree.
You get the unlock key by email, looking like : 56ITMEJ2BFHX5JVXMA4J
Use this unlock key in the following Windows command :
Code:
fastboot oem unlock YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed : "Unclock Completed, wait to reboot",
don't disconnect it from PC !
phone reboots to Android with a blank screen "Warning, Bootloader unlocked".
Keep Windows command opened.
4 ) FLASH RECOVERY & BOOTLOADER LOGO
Shutdown phone again.
Power on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
In Windows command, use this command:
Code:
fastboot flash recovery twrp-3.5.0_9-0-peregrine.img
confirm with Enter.
Terminal confirms : "Finished. Total time: 0.670s".
### In bootloader screen, you see error "mismatched partition size (recovery)" ? No problem. TWRP is smaller than stock recovery.
### For future TWRP updates, TWRP binary can be flashed from TWRP recovery itself (Install > Install Image)
Now, on the phone in fastboot mode, press Volume- to select the Recovery option. Confirm with Volume+.
Welcome to TWRP 3.5 recovery.
TWRP asks for Keep System Read Only ? -> check "Never show this screen during boot again" and Swipe to Allow Modifications.
### You don't see this waring screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
5 ) WIPE PARTITIONS
In TWRP home screen, go to Wipe > Format data.
Type yes and confirm to format partition.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe,
then back.
### Don't try F2FS, it won't work.
Go to Reboot > Recovery.
Let phone reboot.
6 ) FLASH ROM, OPENGAPPS AND BOOTLOGO
Back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
optional: then Add more Zips > logo*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### Don't flash Magisk now
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
7 ) ROOT ACCESS AND DEVELOPER MENU
With Magisk, you are root once phone is started. No extra manipulation needed.
For developer menu: open the Settings menu > About Phone.
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Now go to Settings menu > System > Developer settings.
Switch Advanced restart on.
Now use menus to Restart > Recovery.
Back to TWRP, go to Install > magisk*.zip
Reboot.
You are root.
8 ) ENHANCE PHONE
Go to Settings > Developer options
In drawing, set Windows animation scale, Transition animation scale to Animation off (or 0.5x).
Install Greenify, grant Superuser privileges and follow tutorial to set as System app.
Switch on:
- Smart hibernation > Enabled
- Light hibernation
- Aggressive sleep
- Automatic hibernation
That's it.
### When I play music, it comes out of the phone speaker but not the headphone jack.
Use stock AudioFX app to fix this.
Enjoy,
djibe

New version to upgrade Moto G to Android 7.1 Nougat

Enhenced tutorial

Updated version with overclocking of the Moto G 4G

Overclocking introduced

Tutorial updated for better performances

TWRP 3.2 and MD5 file verification for Kernel flash

Added : flash bootloader unlocked screen at boot.

New version of tutorial to obtain the Google Play Certification.

Do you think I should upgrade tutorial for Lineage OS 15.1 ?

Thread and pack updated with latest LOS updates.

guide updated

Tutorial updated

Hi guys, tutorial updated to enjoy Android 9 on your old Moto G 4G !!!
Enjoy

Added download links for older Android versions if needed

Checked for newer packages.
Tutorial is up to date.

Works, except no sound from headphone jack
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?

Robert Steed said:
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?
Click to expand...
Click to collapse
I've just found the solution to this which is to disable Audio FX.

@Robert Steed. thx for sharing.

@Robert Steed. thx for sharing.

Related

Cubot King Kong custom ROM or Android go?

Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.

Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.

does anyone have a scatter file or custom recovery for this phone? how did you root?

CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip

aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms

Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s

What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img

i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied

Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16

Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result

LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?

Use an app from google play called Device Info HW

Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)

Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).

Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.

In gt1x its because of this:

So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.

And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.

aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance

please do a read back for boot.img and recovery.img with SP Flash Tool

Rebrand-Update-Tool-HWOTA7-P9-EVA

Rebrand-Update-Tool HWOTA7 for Huawei P9-EVA
German Thread (not updated yet): https://www.android-hilfe.de/forum/...-p9-eva-inoffizielles-oreo-update.884138.html
→ HWOTA7 Tool for P9 Plus VIE is different: https://forum.xda-developers.com/p9...rand-update-tool-hwota7-p9-plus-vie-t3843930/
In 2018, the P9 was still being used by many users. Many were annoyed because Huawei did not provide the Android 8 update for the European models. The Chinese models got Oreo and there was really no reason why European models didn't get it.
HWOTA7 offers the possibility to change the model of the P9. This allows, for example, a Chinese model to be converted into a European one - and a European model into a Chinese one. In order to update the P9 to Android 8, it is necessary to convert the respective European model (EVA-L09 or EVA-L19) to a Chinese model (EVA-AL10).
The instructions for this conversion and the Oreo update can be found in the next post #2:
https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-77161313
Basic information:
→ HWOTA7 for EVA is programmed ONLY for to use on Android 7 (Nougat). It does not work on Android 8 Oreo (and it doesn't work on Android 6). Of course you can update from Android 7 to Android 8, but to go back to Nougat from Oreo this tool cannot be used. There is another solution for this purpose, you can find it in post #3:
https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-77161314
→ The hardware and firmware of the different P9-EVA models is different. For example, if you convert an EVA-L09 (SINGLE-SIM) to an EVA-L19 (DUAL-SIM), you will not get a DUAL-SIM function. If you convert the European P9 to a Chinese P9 - which is necessary to update to Oreo - no mobile network will work at first because the chip is different and the Chinese firmware only addresses the real Chinese models. Therefore it is necessary to flash a network patch after updating to Oreo (see instructions Post #2).
→ With HWOTA7 you can just update your current Firmware with FullOTA-MF Firmware (3 zip files, two of them renamed), but the Firmware you use MUST match your device model and cust (for exampel, if your device ist EVA-L09C432 you cannot use C636 Firmware). For updating your Firmware with HWOTA7 you choose: Using the script /1. Change firmware
→ You can rebrand (convert your phone model) between L09/L19/L29 and all Chinese Brands (remember: your hardware does not change) by choosing in HWOTA7: Using the script /2. Change location. (14 oeminfo files are included for different locations and cust).
With this option you can debrand from Vodafone/Telekom to the open european cust C432 for example (which is not branded to a Cellular Provider) - or you can rebrand a chinese modell (for example EVA-AL00C00, EVA-AL10C00) to EVA-L19C432 (which has also Dual-Sim).
If you own a chinese modell and it is already on Oreo, you have to downgrade first with HiSuite to Android 7, then you can use HWOTA7 Tool to change location for example to EVA-L19C432. Immediately afterwards it is necessary to flash the appropriate firmware for EVA-L19.
→ If your Phone has SIM Lock, Debranding does not unlock mobile network - you can do that with HCU Client by DC Unlocker
→ Before you change anything, make a note of the build-number from the "About phone" settings. This is important to know if you want to go back to the original phone model.
To revert to the original model, the correct oeminfo is required (14 are included in HWOTA7 tool) - if your model is not there, backup the oeminfo with TWRP. If you send me these, I can integrate them into the tool. The oeminfo of the P9 models on Android 7 does not contain any security-related, device-specific information such as IMEI or serial number.
And you need the firmware files corresponding to the model.
Where can I get the model-specific firmwares?
The new HWOTA7 Tool Version 1.2 contains the folder "1.Firmwares" This contains already the starting firmware for EVA-L09C432 and EVA-L19C432, as well as the required Android 7 firmware for EVA-AL10 and the Android 8 update firmware for EVA -AL10. The firmwares are already renamed correctly to work with the HWOTA7 tool.
The "1.Firmwares" folder also contains the "2.Downgrade-EVA-AL10-Andr.8-to-Andr.7" subfolder. It contains a HWOTA.zip that allows you to downgrade from Android 8 to Android 7 by using the SD card + TWRP. After that, the HWOTA7 tool can be used again to return to the original model (Instruction for that see Post #3)
The most important firmwares are already included in the HWOTA7 tool to update from Nougat to Oreo and also to return to Android 7 and EVA-L09/EVA-L19(C432).
Of course I cannot include all firmwares that are available for the different models and locations.
In 2018 and for some time afterwards, it was pretty easy to find the right firmwares with the Firmwarefinder (by Developer MT). This option no longer exists!
If you need a different firmware (than included) for your original model, this is the only way: https://forum.xda-developers.com/t/...geos-16-0-for-huawei-p9.4078383/post-85016053
But for that you must use the new URL: https://professorjtj.github.io/
If you download firmwares from that source, the firmwares must always contain 3 zip files.
And you must rename two of the zip files, because the HWOTA7 is programmed to only work with those names:
update.zip = update.zip (do not rename)
update_full_EVA-XXX_XXX_cn.zip - rename to: update_all_hw.zip
update_data_full_public.zip - rename to: update_data_public.zip
→ You should disable "Hide extensions for known file types" in Windows Explorer's file options under the "View" tab. Because if you unintentionally rename the update_all_hw.zip to "update_all_hw.zip.zip", flashing the firmware will not work.
Requirements:
You need the Bootloader Unlock code for your phone → if you do not have it, it can be read out with HCU Client by DC Unlocker (4 credits = about 4 EUR).
Developer Options must be enabled and inside: → OEM Unlock + ADB Debugging in charging only mode + USB Debugging (in this order) enabled
HiSuite HDB in Settings on the phone should be disabled, HiSuite on PC should be closed in the background
You need a working USB Connection (drivers) between P9-EVA and PC (MTP, ADB and Fastboot → Allow access to the phone, accept RSA key fingerprint)
The battery should be charged.
Backup your important data (folders from internal storage such as WhatsApp, DCIM, Downloads, Music, etc. - as well as user apps with data, contacts, calendars, sms, etc.) → The internal storage is erased several times during this process. Follow the instructions.
HWOT7 is working on Windows 7, 8.1, 10 and 11 by using update_eng.bat (it does not have to be run with administrator rights). The instructions in the thread are formulated for Windows users.
For Linux computers read post from @leodp : https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-83916865
or/and use the tipp by @MSe1969 - which is the contributor of the amazing → Treble ROM based on LinegeOS 16, MicroG and Bromite WebView always up-to-date for Huawei P9 (Update to Oreo-Firmware required):
"A hint for Linux users: The HWOTA tool is in fact a windows wrapper around Linux shell scripts, so there is no real need to use Windows, if you have a working Linux installation ( however, make sure to replace the 'mkdir' commands in hwota_eng.sh with 'mkdir -p' ).
For MacOS computers use: https://github.com/feedsbrain/hwota7
Download P9-EVA-HWOTA7-v1.2.zip:
11,9 GB, MD5: 5e93700221dfd8f2d5083d2cf22706f1
https://mega.nz/folder/XNRjBJAS#7Ne--slFgj0IsFbQwrlaLw
Changelog:
v1.2: Added required Firmwares + HWOTA-SD-Card/TWRP-Downgrade from Oreo Tool + oeminfo for EVA-L29C636
v1.1: Added "cmd-here-exe" in HWOTA7\tools\windows. Run the file as an administrator for general operations using ADB or Fastboot Mode. You can flash an Image (ramdisk, recovery_ramdisk, system.img...) out of this folder. → Same function as "Minimal ADB and Fastboot" . Removed: "archive-recoverys" - no longer necessary.
v1.0 Stable Initial release:
Note: The HWOTA Tool is/was available for many Huawei devices. I do not know which person or group has programmed originally. I just took an "empty one" and modified the existing script to work with Huawei EVA, provided the required images (oeminfos, Recoverys, frp-file for eva..) and tested everything on my own device.
Spoiler: How to use the Tool:
How to use the Tool:
Download P9-EVA-HWOTA7-v1.2.zip, unzipp/extract it on the computer with 7zip. The zip file contains the main folder "HWOTA7" Just place this folder (unzipped) as it is to storage C:\ (means: C:\HWOTA7).
The subfolder "1.Firmwares" is located in the HWOTA7 folder. This contains the most important 3-part firmwares, but each packed in just one zip file (to reduce the upload size).
The firmware that you need must therefore first be unpacked.
The zip files contained therein (= 3-part firmware) must be copied to the "update" subfolder without being unzipped. → C:\HWOTA7\update - this is the main working folder.
With a double click on the "update_eng.bat" the rebrand/update tool "HWOTA7" is executed and a terminal window opens.
If you are on custom ROM, first go back to Stock Firmware ("Using script" and "Change firmware" - use the Firmware that matches your device and cust)
HWOTA7 is self-explanatory. It detects what to do and prompts you to press certain key combinations or enter the unlock code.
→ The USB cable between the phone and PC remains connected throughout the process!
→ The phone is connected to the PC via USB and you start with the key combination: VOL- and Power Button key into Fastboot mode.
→ Only press "Enter" in the terminal if the described step, in the line before, was executed.
→ If you face an error like: "adb: error: connect failed: no devices/emulators found" - close Terminal, reboot phone into Fastboot mode and restart HWOTA7
→ When the Bootloader is locked, the tool will unlock the Bootloader with the code. Thereafter, a factory reset is performed by clearing the internal storage = Lowlevel Wipe.
When the Bootloader is open, the tool automatically flashes TWRP and prompts you to press (and hold) VOL+ and Power Button to start into TWRP.
After you click 2x in the terminal on "Enter"
→ Before you choose: 2. Using the script and 1. Change firmware or 2. Change location - make sure, the 3-part FullOTA-MF Firmware is already in the update folder: C:\HWOTA7\update - and two of the three zip files are correct renamed (included Firmwares are already renamed)
Important difference between four situations:
1) When the Bootloader is closed, HWOTA7 opens it with the code, a "lowlevel" factory reset is performed and the device must then boot into the system. In the setup everything can be skipped (which is possible) - but the developer options must be switched on (1.ADB Debugging + 2.USB Debugging enabled). And HiSuite HDB disabled.
2) If you select "Change firmware" to flash the firmware, the tool copies the ZIP files to the phone in the /data directory, flashes the Nocheck recovery, and installs the firmware. In this case, you also need to boot into the system and check if Developer options with the required settings are enabled.
3) But if you do the step: "Change location" - this step is different! The tool will flash the corresponding "oeminfo", close the Bootloader and request the Unlock code to unlock the device and force a "lowlevel" factory reset → In this case (only), you should NOT boot into the system after the reset. Wait until the EMUI recovery is 100% done with the reset. Then comes the message "Reset succesful, device will restart" Now press (only) the VOL+ button and keep it pressed so that the device starts into TWRP. Now click on "Enter" in the terminal. HWOTA7 now copies the firmware to the device, flashes the Nocheck recovery, reboots and flashes the firmware belonging to the "oeminfo". After this step, the device must be booted into the system.
4) If the device boots into the system and you have a black screen, with an input field in the middle and possibly the keyboard (do not get worried) - the Bootloader was locked by the firmware during rebranding. In this case, press the Power Button to restart and hold down the VOL- button during the restart to start the device into Fastboot mode. Close the Terminal Script and restart update_eng.bat. Click on "Enter" in the Terminal and HWOTA7 will ask you for the Unlock Code and unlock again the Bootloader. Confirm the unlock on the device with the keys, then there is a factory reset followed by a reboot into the system. Now everything is fine.
→ Hint: If you face any error during Firmware will be copied to: /data/update/HWOTA - like: "connect failed, no devices/emulators found" – do following:
Close HWOTA7 Terminal and use menu "Reboot" of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "Enter" in HWOTA7 Terminal - Firmware will now again be copied to: /data/update/HWOTA - "System update should start automatically" - Phone will make reboot and flash the Firmware correctly.
Have fun
Credits:
@Atarii EVA-NoCheck Recovery
@OldDroid Android 7 TWRP for P9-EVA, TWRPs for many Huawei devices, Lead Developer/Maintainer Open Kirin Team
@Pretoriano80 Android 8 TWRP for many Huawei devices
@arshilhonor6x Guide to EMUI 8 for Honor 6
@reynard1 @vampirian @dkionline Thank you for cooperation and exchange
@urbanmec Thanks for many hints and tweaks
@zgfg Thanks for great support and help for users of this Thread
XDA:DevDB Information
HWOTA7-P9-EVA, Tool/Utility for the Huawei P9
Contributors
Tecalote
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2022-06-22
(Old Stable Version: 1.1 / 2018-07-24)
Created: 2018-07-25
Last Updated: 2022-06-22

2022-06-21: This Post is under construction - please wait until the update is ready
Old text:
Unofficial Update for European EVA-models to official OREO
Unofficial method to update European models of Huawei P9 EVA to official Android Oreo
- for EVA-L09 - EVA-L19 - EVA-L29
Originally, all models of the P9 EVA and P9 Plus VIE should receive the Android Oreo update. Unfortunately, Huawei has decided to only supply the Chinese models with Android 8.
For this reason, there is an unofficial way to update to the official Oreo → by rebranding the European models to EVA-AL10.
Note: This Guide is for P9 EVA → P9 VIE HWOTA7 with a separate guide to the Oreo update you can find here: https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
Oreo runs smoothly and well on the P9, the battery last longer and with Android 8 there is Treble Support. Since it is possible to update P9 to Oreo -
Huawei P9 is officially supported by the OpenKirin Team:https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
Here is a small Guide how to go back from OpenKirin to EMUI: https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
Preparation for the update to Oreo:
If you are on any Custom Rom - go back to Stock firmware first - before rebrand to another location!
You should be on the latest approved Firmware for your device - if you have not the latest approved Firmware, use HWOTA7 Tool to update your Firmware.
Do for every case a Backup (TitaniumBackup /Huawei Backup - without System-Apps/Settings) before. TWRP Backup makes no sence, because you can not restore it on Oreo! [/B]Make sure, the Update-Firmware is copied to the folder C:\HWOTA7\update - and two zip files are RENAMED as mentioned in OP → read OP Post#1. Update your Firmware by using the script (HWOTA7 Terminal: 2. Using the script + 1. Change firmware)
Instructions for updating to Oreo by rebranding your phone to EVA-AL10:
Requirements:
A) HWOTA7 Tool
B) Bootloader Unlock Code for your device
C) For rebranding from EVA-L09 or EVA-L19 or EVA-L29 to → EVA-AL10 you need to download the following 2 Firmwares:
EVA-AL10b399Sp17a /Android 7 (this Firmware is required for the Update to Oreo):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v138329/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...29/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo:
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3115/g1699/v208318/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...18/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
Steps:
0) Check: Your original device is updated to the latest Firmware - you had downloaded the two EVA-AL10 Firmwares (Nougat, Oreo) - you made a Backup from personal folders of your internal storage (WhatsApp-DCIM-Download-etc. folders) and a Backup from your (User) apps, contacts, calendar etc. - HiSuite is closed on PC and disabled in settings on the phone - Developer Options are enabled with OEM Unlock and ADB Debugging + USB Debugging enabled - the 3 Firmware zip files for EVA-AL10b399Sp17a are in the C:\HWOTA7\update folder (two files renamed as descriped in OP Post #1)
1) Connect your device with USB to PC and start from HWOTA7 main folder: update_eng.bat - Accept possibly the RSA query on the display of the P9
2) Restart P9 into Fastboot mode (use restart/restart and press VOL- /or shutdown phone and press VOL- and Power Button)
→ Note: During all steps USB Cable stays connected between phone and PC and you hit "Enter" in Terminal only, if the step, which is written before, is already done!
3) HWOTA7-terminal detects if Bootloader is open or closed - if the Bootloader is closed go to 4) - if the Bootloaer is open go to 7)
4) Terminal ask you for the Unlock code - enter the Unlock code and confirm the Unlock on the phone
5) The P9 reboots and an automatic factory reset is done with internal storage wipe (lowlevel reset) - wait until the phone reboot to system. Skip everything during setup (except what can not be skipped) - Important: Enable Developer Options with ADB Debugging and USB Debugging
6) Restart your P9 into Fastboot mode - now hit "Enter" Button - HWOTA7 Terminal will flash automatically TWRP for Android 7 and gives you the order to boot into TWRP by pressing VOL+ and Power Button (dont hit "enter" before this step is done)
7) In TWRP swipe to allow system modification - now hit "enter" (2x) in the Terminal - after a short while you will see: Upgrade Options
8) 2. Using script: 2.Change location - you will see a list of available "oeminfo" - use: 2.EVA-AL10C00
→ Note: The Firmware for EVA-AL10/Nougat must be already in the update folder (and two zip files renamed)!
9) HWOTA7 flashes now oeminfo for AL10, Bootloader is getting closed, confirm the Unlock on device - automatic factory reset is executed, wait until 99% and 100% restarts the phone → NOW PRESS VOL+ to boot the phone into TWRP instead of system!
10) Allow system modification in TWRP and hit "enter" Button for Terminal - HWOTA7 copies now the firmware to the directory: /data/update/HWOTA - restart phone automatically and flashes the Firmware with EVA_RECOVERY_NoCheck.
→ After the P9 has started into the system - you may see a black screen with an input field and a keyboard - if yes, go to 11) - if no, go to 13)
11) Close HWOTA7 Terminal and press Power Button on P9 to restart your Phone, restart phone, in the moment of restart press VOL- Button to boot into Fastboot Mode → Bootloader is closed. BTW: Chinese Brands dont have FRP.
12) Open update_eng.bat, click enter, enter the Unlock code, confirm Unlock on phone, phone makes a Factory reset with lowlevel wipe. Then the P9 starts automatically into the system. Now you have already rebranded to EVA-AL10c00b399sp17a / Nougat. :good:
13) Accept the terms and conditions (Huawei + Google Services) and skip the rest, what can be skipped. Do not be nervous, the P9 has no IMEI at the moment and no mobile network. This is normal. In Settings/Advanced settings menu disable: "Trust Space" and "HiSuite HDB". In Settings/About phone/Build Number/7x click - enable Developer options - go into menu/Developer options and enable ADB-Debugging and USB-Debugging (in this order)
14) Click enter in Terminal, select 2. No, I would not and HWOTA7 will be closed. → Change now the Firmware in the update folder to EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo (remember: two zip files has to be renamed!)
15) Start again update_eng.bat. Reboot phone into Fastbood Mode. Hit "enter" for Terminal - TWRP will be flashed automatically - reboot with VOL+ and Power Button into TWRP - allow system modification - hit "enter" in HWOTA7 Terminal
16) Use Upgrade options: 2.Using the script - 1.Change firmware (Same brand update /but Oreo)
17) Click enter in Terminal, Firmware will be copied to: /data/update/HWOTA - "System update should start automatically" → if you receive any error like: "connect failed, no devices/emulators found" - go to 18) - if everything is okay go to 19)
18) Close HWOTA7 Terminal and use menu of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "enter" in HWOTA7 Terminal - Firmware will be copied to: /data/update/HWOTA - Phone will make reboot and flash the Firmware for Oreo automatically.
19) You have now successfully updated to Android 8. :good: Phone will reboot into EVA-AL10C00B540 (8.0.0.540) Oreo. → You should accept the terms and conditions (Huawei + Google Services) - otherwise Playstore will not work later! Do not enable WLAN and do not set up your phone (Fingerprint etc)right now! - skip, what can be skipped. → You will have "unknown IMEI" and no mobile network at the moment, that is normal.
Open Settings/System and enable again Developer Options/ADB+USB Debugging. In Settings /Security+Privacy you can find "Trust Space" - disable it - and in same menu you find in "More" "Allow HiSuite to use HDB" - disable it!
→ Now we must do some steps that the phone is able to recognize the IMEI and mobile network as well as NFC on L09 and Dual-SIM on L19/L29 and disable Chinese apps, which we do not need in Europe.
20) Downloads:
TWRP for Oreo P9-EVA-8.0.0-TWRP-v4.img: https://www.androidfilehost.com/?fid=1322778262903998750 - we need this to flash the important changes to system without the need of Root
This TWRP is made by @Pretoriano80 for Honor 9 Lite. I made just small changes for hi3650. You can backup and restore everything, except data! There is no access to /data - means: you can not do Factoryreset from TWRP - and decryption of the internal storage for the TWRP session is not working. → For Backkup and restore data you can use HiSuite or Huawei Backup or Titanium Backup. MTP ist working, when you just disable/enable it once.
Network-Patch zip files (new released 03.03.2019):
→ select the zip according to your original model (which you had before rebranding to EVA-AL10)
→ Copy the zip file to the external SD or to the USB Stick, which you connect to P9 after with OTG cable. Since TWRP can currently not access /data (internal storage) - you can not flash this Patches without → external SD or USB OTG
→ The Network Patch zip files can be used for b540. If you are already on Oreo and have an older Firmware (b528, b535), you must update first to b540.
→ Update from older Oreo Firmware to b540: https://forum.xda-developers.com/showpost.php?p=77161303&postcount=5
EVA-L09_b540-SingleSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910447
MD5: 8662c7129945f5bc2236e8f87031b793
EVA-L19_b540-DualSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910449
MD5: 46dc8f974cb345027746d88ac141f6e1
EVA-L29_b540-DualSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910453
MD5: afac13a9e6445b6d5a2beb8289abda6b
VIE-EVA-FaceUnlock-Oreo-v1.5.zip: https://www.androidfilehost.com/?fid=1395089523397898660
MD5: 973d006c55fa812d722b653a57c844c0
Installing NetworkPatch-v2.6 and optional VIE-EVA-FaceUnlock-Oreo-v1.5
→ You just need one Network patch. This must match your original model - which you had before rebranding!
21) Copy the downloaded TWRP into the folder C:\HWOTA7\tools\Windows - connect P9 with USB to PC - right click on cmd-here-exe (run as administrator) - type: adb reboot bootloader (enter, to restart your P9 Plus into Fastboot mode) Flash now TWRP in Fastboot Mode:
Code:
fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img
22) Disconnect the USB cable from P9 and press (with the left hand) VOL+ and Power Button (with the right hand) and keep pressing until the Phone is rebooted into TWRP.
23) On the first Screen click on "Cancle" (because decryption is not working) but swipe to confirm to "Allow System modification"
→ Go to: Install /select storage: Micro SD (or USB-OTG) and choose your downloaded NetworkPatch.zip file. If you like, you can use the function down left "Add zip file" and choose the VIE-EVA-FaceUnlock-Oreo-v1.5.zip
24) Swipe to confirm flashing the Network Patch (and the optional added VIE-EVA-FaceUnlock-Oreo-v1.5.zip file)
25) If you had used an older NetworkPatch before flashing the newest one - go back to the main menu of TWRP, go to wipe → advanced wipe and choose only "cache" (not Dalvik) → but if you are new on Oreo b540 you can skip this step
26) Reboot to the system
27) Finally, Playstore and any keyboard is needed. Download the apks from here (February 2019): https://www.androidfilehost.com/?w=files&flid=290476
28) Install it, enable keyboard, open Playstore and log into your account. After that reboot your phone. Now you can update apps, download and install your favorite apps and additional all other Google apps from Playstore → do not flash GApps instead!
29) After you have installed all required files, you have currently TWRP installed → this is good for Users, which like to have Root and disabled OTA.
Root Guide can be found here: https://forum.xda-developers.com/showpost.php?p=77161300&postcount=4
→ But if you like to enable OTA instead:
A) Download and flash: Enable-Hwota.zip from here: https://www.androidfilehost.com/?w=files&flid=290481
B) Go back to the main menu of TWRP and Reboot to Bootlader
C) flash in Fastboot mode the Stock EMUI Recovery
Code:
fastboot flash recovery_ramdisk EVA-b540-EMUI-RECOVERY_RAMDIS.img
Download from here: https://www.androidfilehost.com/?fid=1395089523397898706
Reboot Phone and enjoy
As Mirror for the Downloads you can use also the Mega folder by @zgfg
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
@zgfg is the official authorized supporter for this thread. He give you a lot of help and support and he do a lot of tests, before we release new Patches.
Many Thanks!
If you search for older files (Network Patches etc) for older Firmwares, you can also search my folder on Android Filehost:
https://www.androidfilehost.com/?w=files&flid=124276
Note: It is not possible to lock the Bootloader on to EVA-AL10 rebranded phone with Network Patch and FaceUnlock! This would revert all the required changes and in the worst case push your phone into a bricked state.
→ But what you can do with installed EMUI Recovery (instead of TWRP): You can do from settings /system /reset a Factoryreset with wipe of the internal storage (to clean up previous instalations) → in this case the Factoryreset lowlevel does not revert the changes! The only difference is: When you get Push notifications, the Badges over the app symbol on Homescreen will change from numbers to points (which is standard on Oreo) → which is currently not change able in settings without Factoryreset.
Known issues:
VoLTE and WiFi-Calling is is visible in the menu - but does not work for now!
If you want synchronisation between Google calendar and EMUI calendar - you need to install Google calendar from Playstore.
If you like to use Google Assistant and have problems to teach this app with your voice "Hello Google" - just open settings /apps & notifications /standard (default) apps - and choose Google Assistant as default app (then it will work).
→ Please read also the next few posts (Root, current firmware with eRecovery, Update Firmware on Oreo with HWOTA8, going back to EVA-AL10 Nougat and rebrand back to original model)

Restore current Firmware - or going back from Oreo to Nougat and rebrand back
2022-06-21: This Post is under construction - please wait until the update is ready
Old text:
Restore current firmware (if you are on EMUI or OpenKirin ROM) → check out following Post:
https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
How to go back from Oreo to Nougat → and rebrand back
A) Method by using HiSuite (on PC):
1) If you have Magisk Root - uninstall Magisk with Magisk Manager (Button Uninstall)
2) Make sure, you have EMUI-Stock-Recovery installed (it does not work with TWRP)
3) Download Huawei HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
4) Update HiSuite on PC to (minimum) version: 8.0.1.302_OVE and connect your Phone with PC and HiSuite.
5) Let HiSuite install HiSuite App on your Phone - accept the Permission requests. Once that is done:
6) Click on "Systemupdate" - a new window pop up and show you your current version, click on the Link "Change version" - then you can downgrade to the latest Android 7 AL10 firmware
7) → then it is possible to use HWOTA7 again for rebranding back...
B) Method by using HuRUpdater → requires external SD or USB OTG:
If you want to go back from unofficial Oreo to Nougat and rebrand back to your original brand, you can do it with simply steps.
→ Note: HuRUpdater can not only be used for Downgrade, it can also be used for Update Firmware - It depends only on which firmware you pack together with HuRUpdater in the folder (which you have created on external SD or USB OTG)
→ The Firmware must be FullOTA-MF (same renaming than with HWOTA7 Tool)
1) Bootloader must be open
2) Flash TWRP for Oreo Download TWRP by Pretoriano80: https://www.androidfilehost.com/?fid=1322778262903998750
3) Backup your data with Huawei Backup (because TWRP can not acces data for now, because it has no encryption/decryption support)
4) Make a folder on your external SD and name it: Downgrade or Update (or however)
5) Copy the 3 Firmware zip files into the folder and make sure, two zip files are renamed (same as you did for HWOTA7)
6) Download HuRUpdater_0.4.zip from here:http://www.mediafire.com/file/r14sor2g4cbugzw/HuRUpdater_0.4.zip
7) Copy HuRUpdater into the same folder together with the firmware zip files. If you have the Nougat AL10 zip files inside, you will downgrade.
The folder contains now 4 files:
HuRUpdater_04.zip
update.zip
update_all_hw.zip
update_data_public.zip
8) Boot into TWRP. It will ask you for password. Just cancle. In TWRP open "Wipe" - but dont wipe anything - you must use the Button on the right Format Data. Confirm with typing: yes. Soon data is formatted, go back to the main menu and open Reboot - but do not reboot System - you must Reboot Recovery
→ Note: Format data is only important until we have TWRP with working data decryption
9) After TWRP is rebooted go "Install".
10) Navigate to the folder which containes the files and flash ONLY HuRUpdater_04.zip In some seconds the Akku vibrates - in this moment press for one second the VOL- Button. Now HuRUpdater will flash automatically the FullOTA-MF Firmware.
11) Once it is done, use on the left: Wipe Cache Button. After go back to the main menu and Reboot RECOVERY.
12) Your device has rebooted now into EMUI Stock Recovery. From there perform Wipe Cache Partition and Factory reset and boot to system.
Once you are back to Nougat - you can use again the HWOTA7 Tool to rebrand back to your original brand. Just use Change location (for your original cust) and make sure, the Firmware is in the update folder..
Credits:
@zxz0O0 Many thanks for HuRUpdater
HuRUpdater Thread: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

2022-06-21: This Post is under construction - please wait until the update is ready
Enable Root Access
Instructions for root access
Root is not required, but if you still wish, here is the guide:
Due to the fact TWRP cannot access the encrypted data partition, you cannot JUST flash Magisk!!
→ A) But you can flash Magisk with TWRP using a workaround
→ B) Alternatively it is possible to flash a Magisk patched ramdisk.img in Fastboot mode
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
1) Download the favorite Magisk version from here (all releases): https://github.com/topjohnwu/Magisk/releases
The actual and newest stable version you can get always from here too: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2) Copy the flashable Magisk-vXX.zip and Magisk Manager apk to external SD – and make sure, you have Developer options with 1) ADB Debugging and 2) USB Debugging (in this order) enabled.
3) Reboot device to TWRP, cancle Password, allow system-modification (swipe to confirm)
4) On the main menu go first to "Mount" - down left click on "Select storage" and choose "Micro SD"
5) Go back to main menu and open "Advanced" and open "Terminal"
NOTE:
If you have got a OTA-Firmware Update with “Patch02” or “Patch01” before flashing the Network Patch (after Network Patch, you will not see this in "About phone"!) or if you don’t remember, then use following both Lines in Terminal, but if you are sure, you have only Firmware without Patch 01 or Patch02, then use just "Keep Force encrypt" Line. Write the Lines in TWRP/Terminal exactly.
6) Write following code with Terminal:
Code:
echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk
→ Confirm each Line with blue/white checkmark on keyboard, before writing the next Line and confirm also the second Line (if you use two)
7) Go back to the main menu to "Install" and flash Magisk - after that reboot phone without wipe of Dalvik/Cache!
8) Search for Magisk Manager on Homescreen - if it is not installed, just install the Magisk Manager apk
9) Open Magisk Manager → everything should be okay
10) Open normal settings /apps & notifications /Magisk Manager /permissions and make sure Magisk Manager has permission for storage.
11) From Magisk Manager menu above left, section “Downloads” – download and install directly “Busybox for Android NDK” by osmosis – save log and reboot phone.
→ If Magisk get a major update, uninstall first Magisk from Magisk Manager and use “uninstall” button. “Uninstall complete” The phone restarts automatically. After that you can flash the new Magisk and reflash the modules.
B) Flashing Magisk with patched ramdisk.img in Fastboot mode:
If you don’t want flash Magisk with the TWRP workaround – you can use a Magisk patched ramdisk.img instead.
1) You can patch ramdiks.img from update.app by yourself, with following method:
Extract the update.zip of the current installed Firmware, because we need the UPDATE.APP.
Download Huawei Extractor v0.9.9.5 from here: https://forum.xda-developers.com/showthread.php?t=2433454
In the settings of the Huawei Extractor disable "verify header checksum" - then put with drag and drop the UDPATE.APP into Huawei Extractor and extract by right click the RAMDISK.img (on earlier Android Versions it would be: BOOT.img)
2) Copy the original RAMDISK.img to your phone to the internal storage in the folder: Download
3) Install the latest Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4) Open Magisk Manager, Magisk Manager ask you "Install Magisk-vx.zip?" - first click on: no thanks
5) Since internal storage is encrypted by default, you must first enable the checkbox: "Preserve force encryption"
5) If you have installed a OTA-Firmware Update with Patch01 or Patch02 – then enable additional the checkbox "Preserve AVB 2.0/dm-verity" in Magisk Manager.
6) Then click on "Install" - "You want to install Magisk-v1x.zip now?" - Install - Patch Boot Image File...
7) Navigate to Download folder, and choose RAMDISK.img
8) Magisk will now patch the RAMDISK.img and and once that's done, Magisk will save the patched ramdisk.img with the new name: patched_boot.img in the "Download" folder on internal storage.
→ Do not be confused - this is just named “patched_boot.img, but it is in fact the patched ramdisk.img !
9) Go to Settings /Apps & notifications/Apps and uninstall Magisk Manager
10) Now you must flash the “patched_boot.img” – Reboot your phone into Fastboot mode
Android 8:
Code:
fastboot flash ramdisk patched_boot.img
10) Reboot phone, install again newest Magisk Manager, open it and you will be asked: "Requires Additional setup - to you want to proceed now" Yes. → This step is required for to work properly.
2) Instead of doing yourself – you can use the already patched ramdisk.img:.
→ important: the right patched ramdisk img must be used for the right Firmware version (example: b540)
Magisk patched ramdisk.img you can download always from @zgfg MEGA folder:
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
And you can download also from my folder: https://www.androidfilehost.com/?w=files&flid=290471
Current version:
→ depending if you have b540 with OTA-Patch02 or b540 without Patch02 (you must know, because after flashing Network Patch you cannot see it in Settings /System /About phone !)
Magisk 18.1 patched ramdisk.img for b540 without OTA-Patch02:
https://www.androidfilehost.com/?fid=1395089523397898715
Magisk 18.1 patched ramdisk.img for b540 Firmware with OTA-Patch02:
https://www.androidfilehost.com/?fid=1395089523397898717
→ if you don’t remember, if you have OTA-Patch02 installed, then use the one for Patch02
Installing patched ramdisk.img:
Reboot your Phone into Fastboot mode and flash the patched ramdisk.img with following command → depending on which version you install:
Code:
fastboot flash ramdisk EVA-b540_Magisk_v18.1_Encrypt-Ramdisk.img
Code:
fastboot flash ramdisk EVA-b540_Patch02-Magisk_v18.1_Encrypt_AVB-Ramdisk.img
Google Playstore certification
You can try it with method by @zgfg:
https://forum.xda-developers.com/showpost.php?p=79070144&postcount=1574
→ If it does not work you can try advanced method:
1) Set your phone into Flight Mode (no network should be connected)
2) Open Settings/Apps & notification/Apps and down right in the dot menu click on: show systemprocessing
3) Go step by step into following Apps (if there): Google - Google Play Store - Google Play Services - Google-Service-Framework - each has the entry: storage - delete ONLY cache /not data
4) Open with Mixplorer the directory:
/data/data/com.android.vending/shared_prefs - search for the xml file: finsky.xml
5) Open finsky.xml with TEXT Mixplorer Text Editor
6) Search inside finsky.xml for: <boolean name="device-google-certified"value="false" - change it to:
Code:
<boolean name="device-google-certified"value="true"
- means, you change only "false" to: "true"
7) click on the save symbol to save the changes! - close Mixplorer and everything in the Background
8) Disable Flight Mode (so Phone search for network connections)
9) Reboot your Phone
10) Open Playstore menu /settings/ =certified
If you have problems with current version of Magisk and using Gpay (Google Pay), try following workaround:
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
How to uninstall Magisk:
A) Before you doing an OTA Update, it is required to uninstall Magisk → and also make sure, to have Stock EMUI Recovery installed (instead of TWRP).
B) In case for a “major” Magisk update it is also sometimes necessary to uninstall Magisk before installing the new version, because with directly update the phone could get a Bootloop. (But normally Magisk updates can be done directly and without uninstalling Magisk before).
C) If your device can not boot into system due to an incompatible Magisk Module.
a + b) If you can boot normally to system, you can uninstall Magisk from Magisk Manager - just use the "Uninstall" button “Uninstall complete”. Magisk will be uninstalled and Magisk files deleted from /data directory. Thereafter, the P9 is restarted automatically.
c) If your device can not boot into system due to an incompatible Magisk Module, you can flash the original EMUI Stock ramdisk.img (which is not patched with Magisk)
→ ramdisk.img must match the Firmware version of your device
For the current Firmware EVA-AL10 b540 you can download the original ramdisk.img here:
EVA-b540-RAMDISK.img:
https://www.androidfilehost.com/?fid=1395089523397898709
You can flash it in Fastboot Mode:
Code:
fastboot flash ramdisk EVA-b540-RAMDISK.img
Alternatively, you can flash the image with TWRP.
In this case you flash the img with TWRP by using: "flash img" - but important is, you must flash it to: ramdisk (and NOT to recovery_ramdisk !!)
Soon you have installed the EMUI ramdisk.img, the device can boot to system again and Magisk is disabled.
Enjoy
Credits:
@osm0sis Busybox for Android NDK
@Didgeridoohan MagiskHidePropsConfig module
@topjohnwu Magisk root

2022-06-21: This Post is under construction - please wait until the update is ready
Manual Firmware-Update on OREO
Manual firmware update – if you are already on Oreo
You can manual update the Firmware - if you are already on Oreo → but you can not update with this method from Android 7 to Oreo!!
→ The manual update is based on a special EMUI Recovery for EMUI 8 which does not check if you have modified your system.
We will post the actual Links here and/or on the actual last pages.
→ you need an external memory card in the device for this method - it does not work with USB OTG
The current firmware is EVA-AL10C00B540 (8.0.0.540):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3115/g1699/v208318/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...18/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
1) Renames:
Enable in Windows Explorer “Show file extension” (to see the extension: zip, doc, docx etc. at the and of the filename) because if one file is named update.zip.zip → it will not work!
update_data_full_public.zip → rename to: update_data_public.zip
update_full_EVA-AL10_all_cn.zip → rename to: update_all_hw.zip
→ do not rename update.zip
2) Required: installed TWRP →see Post #2 how to flash
Download: https://www.androidfilehost.com/?fid=1322778262903998750
3) FirmwareUpdate_onOreo_from-externalSD.zip
Download this zip file and extract (unzip) it:
https://www.androidfilehost.com/?fid=1395089523397898768
The zip file contains the folder HWOTA and inside are two files. Do not rename that files.
4) Create a folder on your external SD with the Name HWOTA in the main directory (don’t use another name!) - or copy the HWOTA folder from unzipped Firmware-Update.zip instead to your external SD
5) You have now the folder HWOTA in the main directory of your external SD (without Subfolders between)
6) The folder HWOTA must contain:
eva_vie_recovery_nocheck.img
ExtSD-FirmwareUpdateScript.zip
update.zip
update_all_hw.zip
update_data_public.zip
7) Reboot phone to TWRP, cancle Password, allow system modification, go to Install, select storage: Micro SD - and flash ONLY the zip file with the name: ExtSD-FirmwareUpdateScript.zip
8) The phone restarts and takes a while to flash automatically the EMUI-NoCheck-Recovery and takes also a while until the Firmware will be flashed automatically as well as Phone reboots after. Just wait, until it boots up.
→ if you have Root, there is no need to Unroot before and you will lose no installed apps, except perhaps Playstore and Keyboard (but if it was updated, you will not lose Playstore and not Keyboard)
→ you have to flash again the Network Patch (for your device) from #2 with TWRP - and for the case you lost Playstore and Keyboard, just install your favorite apk and reboot phone.
Enjoy :good:

this tool can be used for eva-l19c636 asian to update to oreo right? same procedure?

iammitee said:
this tool can be used for eva-l19c636 asian to update to oreo right? same procedure?
Click to expand...
Click to collapse
Yes!

Do I need to be on the latest version of EMUI Nougat (I think it is B399SP01 or something)? It looks promising so far, I hope I can successfully be on Oreo so I can flash Treble ROMS. Thank you so much!

Gilgameshhhhhh said:
Do I need to be on the latest version of EMUI Nougat (I think it is B399SP01 or something)? It looks promising so far, I hope I can successfully be on Oreo so I can flash Treble ROMS. Thank you so much!
Click to expand...
Click to collapse
All information about these questions will be explained in Post # 2.

For new users / P9 terminals - Huawei is still providing Bootloader codes, or they have to be purchased from eg DCUnlocker?
There was also a rumour about alternative methods, bypassing Bootloader codes?
When it settles, are you also planning for MagicRainbow v5 based on Oreo?

zgfg said:
For new users / P9 terminals - Huawei is still providing Bootloader codes, or they have to be purchased from eg DCUnlocker?
There was also a rumour about alternative methods, bypassing Bootloader codes?
When it settles, are you also planning for MagicRainbow v5 based on Oreo?
Click to expand...
Click to collapse
The Huawei Unlock Site is down (since today): https://emui.huawei.com/en/plugin/unlock/detail
Reading the Unlock codes must be purchased for using DC Unlocker Software. https://www.dc-unlocker.com/read-unlock-codes-for-huawei-phones
At the moment there is no technique to bypass the bootloader unlock code.
Yes I am planning MagicRainbow v5 based on Oreo

Nice, waiting all information about rebrand to Chinese for Oreo Update

Necrodaemon said:
Nice, waiting all information about rebrand to Chinese for Oreo Update
Click to expand...
Click to collapse
I do it in the evening and tonight, so it should be ready tomorrow.

When we change from the European version to the Chinese version, would we lose the nfc?
Enviado desde mi EVA-L09 mediante Tapatalk

L09/L19 rebranded to Chinese Oreo - G2/G3/G4 baseband will work?

P9 eva-dl00
Tecalote said:
How to rebrand Huawei P9-EVA European Brand to Chinese Brand and update to Oreo
Under construction
Click to expand...
Click to collapse
Excuse me my friend... P9 EVA-DL00 also updated to Oreo oficially?
Thanks in advance!!
Regards!!

Hi!
Could this script be used to update firmware without loosing root and bootloader?
Thank you.

ironet said:
When we change from the European version to the Chinese version, would we lose the nfc?
Enviado desde mi EVA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Yes, you loose NFC and don't win Dual SIM..
Same as if you rebrand from L09 to L19.
All Chinese Version have Dual SIM and no NFC.

zgfg said:
L09/L19 rebranded to Chinese Oreo - G2/G3/G4 baseband will work?
Click to expand...
Click to collapse
This and related questions will be answered in Post #2 (when it's ready)

Carlos6862 said:
Excuse me my friend... P9 EVA-DL00 also updated to Oreo oficially?
Thanks in advance!!
Regards!!
Click to expand...
Click to collapse
The final version for all Chinese versions is rolling out. To you have DL00?

[Guide] Root Pixel 3 XL Android 10.0 (Q)

[Guide] Root Pixel 3 XL Android 11 (R) Unlock/Lock Bootloader + Install Stock Images/Systemless Root2021
Android Security Bulletin—June 2021
Pixel Update Bulletin—June 2021
Introduction
This Guide is for Pixel 3 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 3 XL'.
This Guide also works for Pixel 3 owners: If, they download the Pixel 3 files.
New
Android 12 Developer Preview - Beta 2
Factory Images: Downloads for Google Pixel 06/09
OTA Images: Apply a device OTA image 06/09
CalyxOS
GrapheneOS
Update(s)
Factory/OTA Images - 06/07
Magisk Stable - Magisk-23.0 05/12
Magisk Beta - Magisk-23.0 05/12
Magisk Canary - Magisk-23xxx
TWRP - Waiting for Android 11 (Q) TWRP
SafetyNet - SafetyNetFix v1.1.1 01/16
SDK Platform-tools - r31.0.2 April
Custom Kernels
ElementalX (Check his Kernel Manager for latest update.)
Kirisakura v3.0.8_R 06/11
Custom ROMs
[ROM][11][OFFICIAL] lineage-18.1 for Pixel 3/XL (blueline/crosshatch) - Nightly by razorloves
[OFFICIAL][11]ScorpionROM v4.x 05/04
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 3 XL phone with an unlocked bootloader.
The latest Android 11 (R) Factory or OTA Image: "crosshatch" for Pixel 3 XL
Factory Image
11.0.0 (RQ3A.210605.005, Jun 2021)
Which one should I use?
OTA Image
11.0.0 (RQ3A.210605.005, Jun 2021)
Which one should I use?
Computer - With the latest SDK Platform-Tools: r31.0.2 installed.
Important: Update Platform Tools, regularly, for optimal performance.
Other Pixel XL Guides
[Guide] Pixel 4 XL Android 11 (R)
Credits/Thanks/Recognitions
@topjohnwu - Magisk Canary
@sliding_billy - His help editing this thread.
Those I may have, inadvertently, forgotten.
Index
(NOTE: Numbers 1-11 are not steps, they are individual sets of instructions).
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, Add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode:
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.
After unlocking your bootloader, every time you reboot you'll see a warning: You will see this warning until, you relock the bootloader.
Important: 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
Do not lock the bootloader until you have returned the phone to stock. Failure to do so causes bricked phones.
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.
Install/Update Factory Image keep or wipe data
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file with the -w (Wipe Data).
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3 XL - crosshatch.
If your phone was rooted, and you want to 'Keep Data'. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images prior flashing the Factory image. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
If you get an error:when flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 3 XL - crosshatch to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder with the extracted the Factory Image and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove -wfrom this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
Note: If you do not remove the -w your Internal Storage will be wiped.
Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
At the Command Promp type: flash-all and press enter.
System will reboot when flashing is complete.
Do #7 to root/reroot.
Flash Factory Image Wipe Data
This will wipe your Internal Storage.
Open the folder with the extracted the Factory Image.
Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
Open a Command Prompt on your computer in the Platform-tools folder.
At the Command Prompt type: flash-all and press enter.
System will reboot when flashing is complete.
Do #7 to root/reroot.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery - TWRP
Important notes:
Charge your device.
Enable USB Debugging on your phone.
Install the latest version of SDK Platform-tools on your computer.
Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
Connect your device to your computer using a USB cable.
Boot T.W.R.P.
T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
When T.W.R.P boots tap Advanced ==> ADB Sideload.
✓ the wipe Dalvik cache box
Swipe to start
On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
You will see the progress of the sideloaded file.
When the file finishes sidloading, reboot your device.
Done!
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (crosshatch-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image...zip' file to and copy 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
At the Command Prompt type: fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Important Notes:
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R). I recommend doing a clean install. What is a clean install?
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
If your phone was rooted. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
Download files:
Magisk App - Download to your phone
Magisk Beta/Stable App
Magisk Canary App
Custom Kernels - Download to your phone - install with Kernel Manager
Important: Unless otherwise directed by Kernel Developer, Flash the Kernel after Magisk.
[Kernel][11.06.2021][4.9.272] Kirisakura_R 3.0.8 for Pixel 3/XL aka Bluecross by Freak07
Kernel Manager - Download to your phone
EX Kernel Manager
Patch the boot.img
Do #6 - Extract boot.img
Install Magisk (Beta, Canary or Stable) App
Open Magisk App
Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode (#1)
Connect the phone to the Computer with USB cord.
Open a Command Prompt (#1) in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important:If your phone boot loops try one of the following options.
Flash the stock boot.img to both slots. fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok == > wait for it to boot ==> Reboot.
Pass SafetyNet: MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Download SafetyNetFix from the link above.
Open Magisk Canary App
Tap Modules icon.
Tap Install from storage
navigate to the SafetyNetFix file
Hightlight the file (tap it)
Tap the check mark (✓) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Open Magisk Canary App
Tap the Setup icon.
Scroll down to Magisk - MagiskHide and enable it.
Tap back arrow => tap Superuser icon => tap MagiskHide => Scroll to the bottom of the page => Tap Search icon => Tap Show system apps (Under Filters) => check (✓): Google play services (com.google.android.gms).
Close Magisk Manager.
Open Settings
Tap Apps & notifications
Tap see all 999 apps
Tap the three dot menu
Tap Show system
Scroll down to Google Play Store
Tap it
Tap Storage & cache
Tap Clear cache
Tap Clear storage
Exit settings
reboot
Open Google Play Store app
Tap Menu
Tap Settings
Scroll down to Play protect certification
check for Device certification.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap menu icon > Settings > 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/MagiskManager/logs/install_log_
Tap, Reboot
Done
Custom ROMs
Need help with a Custom ROM?
Read and follow the Installation Instructions. The installation instructions are in the OP.
If you have a problem Installing the ROM, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
[ROM][OFFICIAL][Android 11]ScorpionROM v4.x[Google Pixel 3/XL][Blueline/Crosshatch] by NepoRood
ROM][11][OFFICIAL] lineage-18.0 for Pixel 3/XL (blueline/crosshatch) by razorloves
Unofficial
None
Mods/Scripts/Themes
Tulsadiver's Mods
Android 10 ADB Installer-Zip Installer, creates magisk module by Tulsadiver
Android 10 Accents Mod by Tulsadiver
Others
[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.3.6 by Didgeridoohan
[Substratum][Magisk]Pixel Launcher Editor for P3XL by eg1122
[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 3 XL Thread
T.W.R.P. Backup/T.W.R.P Update
Waiting for Android 11 (R) T.W.R.P.

Why on earth would anyone go through all these steps AND lock their bootloader when just using flashall.bat with -w intact also wipes your entire phone?!

@Homeboy76 did this work for you? Was getting ready to do a clean install and while researching what the delta of 19 and 20 was, I see talk of sensors not working?

I always appreciate using your guide(s). Thanks a lot!

guide works, thanks for helping me root android 10 on first day of official release

I've Magisk patched the boot.img using the Canary build and flashed.... it's been stuck on the bootscreen for about 20 minutes. Is this normal? How long should I leave it?

Has anyone gotten Adaway working?

Hi,
Great guide, appreciate it.
I'm on Android 9 rooted with magisk. when I try to install Android 10 I get an error below. Latest platform tools, Bonito .20 Any ideas what is wrong? Flashed multiple time through the Pie security updates etc and never had an issue.
_________________________________________________________________________________
F:\platform-tools>flash-all
Sending 'bootloader_a' (8349 KB) OKAY [ 0.298s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) xbl signature verify fail
FAILED (remote: 'Validate packed image fail')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (73196 KB) OKAY [ 1.798s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_a
OKAY [ 0.298s]
Finished. Total time: 2.376s
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 8A5Y0F91G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'crosshatch'.
Update requires 'bonito' or 'sargo'.
fastboot: error: requirements not met!
Press any key to exit...
_________________________________________________________________

Looks like I screwed it up. Now it boots to the spinning G than back to Fastboot - "no valid slot to boot". Now what?
Reflashed Pie, all set -phone boots up. Now to figure out how to get to Android 10.

ginfest said:
Hi,
Great guide, appreciate it.
I'm on Android 9 rooted with magisk. when I try to install Android 10 I get an error below. Latest platform tools, Bonito .20 Any ideas what is wrong? Flashed multiple time through the Pie security updates etc and never had an issue.
........
Device product is 'crosshatch'.
Update requires 'bonito' or 'sargo'.
Click to expand...
Click to collapse
You've downloaded the wrong image. Are you on a 3a XL (Bonito) or regular 3 XL (Crosshatch)??
Download the correct image from here: https://developers.google.com/android/images

krs360 said:
You've downloaded the wrong image. Are you on a 3a XL (Bonito) or regular 3 XL (Crosshatch)??
Download the correct image from here: https://developers.google.com/android/images
Click to expand...
Click to collapse
Oh **** what a dummy I am! I'm on a Pixel 3XL not 3a XL. Sorry, I'll try again
---------- Post added at 08:49 AM ---------- Previous post was at 08:17 AM ----------
Ok, reflashed the correct Crosshatch 0.20, flashed the Magisk patched .img et viola, Android 10 rooted and no loss of data!
Thanks for all the help.

not to be that guy who asks for ETAs but any idea how long TWRP takes for a new version of android to come out? never really been around for a version release like this and just curious. waiting for TWRP to come out before i go through this process.

Homeboy76 said:
OP
Click to expand...
Click to collapse
Great write up! Thank you! I would suggest adding "--slot all" command to the magisk instructions. Root wasn't appearing to be working for me until I added that in.

pr0adam said:
not to be that guy who asks for ETAs but any idea how long TWRP takes for a new version of android to come out? never really been around for a version release like this and just curious. waiting for TWRP to come out before i go through this process.
Click to expand...
Click to collapse
This twrp works
https://forum.xda-developers.com/showpost.php?p=80017781&postcount=1152
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
Has anyone been able to edit build.prop? I have root, but cannot mount the build.prop w/r.

lawtalking said:
This twrp works
https://forum.xda-developers.com/showpost.php?p=80017781&postcount=1152
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
Has anyone been able to edit build.prop? I have root, but cannot mount the build.prop w/r.
Click to expand...
Click to collapse
even though it says its for blueline(pixel 3) and we are on crosshatch(pixel 3xl)?

I'm not able to flash the 10 factory image. I can flash pie just fine, but it always gives an error when trying to push the system image. I can flash Pie just fine. Anyone else have this issue?

jmartin72 said:
I'm not able to flash the 10 factory image. I can flash pie just fine, but it always gives an error when trying to push the system image. I can flash Pie just fine. Anyone else have this issue?
Click to expand...
Click to collapse
Are you getting an error saying that you need to use fastbootd?

airmaxx23 said:
Are you getting an error saying that you need to use fastbootd?
Click to expand...
Click to collapse
No it doesn't say that. I'd have to do it again to get the exact wording, but it makes my phone boot to some screen that says fastboot up at the top

pr0adam said:
even though it says its for blueline(pixel 3) and we are on crosshatch(pixel 3xl)?
Click to expand...
Click to collapse
Yes. The code paths are the same, so it works. Used it myself.

lawtalking said:
Yes. The code paths are the same, so it works. Used it myself.
Click to expand...
Click to collapse
Are you using just the .img each time or flashing an installer after?

[GUIDE]Installation of LineageOS 14.1 in Lenovo Vibe B A2016b30 dual sim al732row

Instructions for Unlock bootloader, Root and Installation of LineageOs 14.1 in Lenovo Vibe B A2016b30 dual sim al732row variant by lexiyuri
Credits to: getdroidtips, EduardaMonteiro and CarlosArriaga
Necessary files are uploaded in my androidhostfile space
MTK Drivers:
https://androidfilehost.com/?fid=4349826312261627234
https://androidfilehost.com/?fid=4349826312261627236
Minimal ADB and TWRP 3.1.1.0 Recovery:
https://androidfilehost.com/?fid=4349826312261627232
Stock ROM for Lenovo Vibe B (just in case) of:
https://www.androidfilehost.com/?w=files&flid=303573
Lineage OS 14.1 ROM (Nougat 7.1.2) :
https://androidfilehost.com/?fid=4349826312261627242
SuperSU Root:
https://androidfilehost.com/?fid=4349826312261627240
Gapps (choose ARM 7.1 Stock package):
download from https://opengapps.org/
Make a entire backup of your device, syncing Google and WhatsApp accounts before doing something.
First part: Unlocking bootloader and installing TWRP 3.1.1.0 recovery.
0. Install necessary MTK Drivers from my uncompressed file.
Windows XP to 8.1: uncompress files, and follow on screen instructions
Windows 10 enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement.
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement. Your computer will restart and you will be able to install non-digitally signed drivers.
Install your mtk unsigned drivers. In this point dont restart computer again. After finishing all the following steps, you can restart your computer again, and the driver signature enforcement will be re-enabled.
Note: Windows XP/7/8 users don't need to do this.
1. Uncompress and pick the minimal adb and twrp provided from the zip file.
Alternatively, you can Download Minimal ADB tool from https://androidmtk.com/download-minimal-adb-and-fastboot-tool
or Download the full setup Android Studio from its official source https://developer.android.com/studio/?gclid=EAIaIQobChMIpdiIlpfh5QIVks13Ch2bUw8REAAYASAAEgJW9PD_BwE
Note: please dont forget do a complete backup of your data before start!
2. In your Lenovo Vibe B, enter Settings and Enable Developer Options:
Settings -> About Phone -> Tap on the Build Number around 7-8 Times until you see a message "Developer option enabled"
Now, you need to enable the OEM Unlock. Go to Settings -> Developer Option and Enable OEM Unlock. Just as simple as you hear!
3. Go to the folder you uncompressed the Adb tools.
Open a command tool right there (CMD or powershell). After that, turn off your phone.
Now press and hold power and volume up button keys at the same time and you'll see three options: Fastboot mode, Normal mode and Recovery mode.
Confirm Fastboot mode pressing Volume up until you point/reach to the fastboot option and confirm pressing volume down to enter, wait for the fastboot message in your phone. Now, connect your phone to the pc using an good usb cable.
4. Type in the cmd screen
Code:
fastboot devices
command and check if the phone is being recognized. This command list the connected devices.
If your phone serial number shows up everything is fine, but if the phone serial number doesn't appear, you must reinstall mtk drivers or choose another usb cable.
5. Check the unlock oem
typing the command
Code:
fastboot oem unlock
and press enter.
Alert: This procedure will erase your data and reset to the default configuration. Be careful! Check unlocked oem confirmation message on your phone screen.
6. Now is the moment of install the TWRP recovery.
To flash, type the following command in the cmd window:
Code:
fastboot flash boot boot.img
Press enter and wait for a confirmation message.
Code:
fastboot flash recovery recovery.img
Press enter and wait for a confirmation message.
7. Turn off the phone. Press and hold power and volume up button keys at the same time and you'll see three options.
With the volume up key, point to the Recovery mode option and confirm with the Volume down key. Wait a little and now you are into twrp 3.1.1.0 recovery. In the finishing touches, configure the twrp recovery and choose power off option.
Second part: install LineageOS 14.1, Gapps and SuperSu to the Lenovo Vibe B
8. Uncompress the LineageOs folder and copy to an external SD the Lineage Os, Gapps and SuperSU zip files.
9.Turn off your phone, pull out the battery, insert your microSD to the phone. Turn on your phone and start it in recovery mode just as stated before in step 7. Now, you are into TWRP
10. Do a wipe in order to delete the Stock rom. Tap Wipe option, then choose advanced wipe and pick the following ones:
Code:
Dalvik /ART Cache
System
Cache
Data
Confirm the wipe option swiping to the right and wait the confirmation message. Press back option and return to the main twrp window
11. In the main twrp window, tap the Install option, locate your microSD as externalSD tapping in the select storage to activate the external SD. Now search the files into the SD, pressing in the "up a level" zone and after you reach it, install the following things in the exact order:
Choose the Lineage OS 14.1 Rom zip file (swipe to confirm) and wait. Dont restart the phone.
After that, choose the Gapps zip file, swipe again to confirm and wait.
Finally, choose the SuperSu zip file included in the folder, do a swipe, wait.
If you want, its possible install all the zip files as a bunch using the "add more zip option" that twrp offers to you, but I prefer do it each one by one.
12. Do a final wipe choosing "wipe Dalvik and Cache".
13. Now choose the restart/reboot option. Wait for the phone initial setup (around a couple of minutes)
14. Configure the phone with your android account preferences. install your favorite apps, sync your info, etc.
15. Configure the SuperSU, install it, and verify the root with the Root checker app (you can found it in the Play store) and you are done!! Enjoy!!

[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.

Database Info

welcome